
From nobody Fri Apr  1 00:25:12 2016
Return-Path: <rsk@gsp.org>
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 5721E12D581 for <ietf@ietfa.amsl.com>; Fri,  1 Apr 2016 00:25:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] 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 3uvXAIxNy-RL for <ietf@ietfa.amsl.com>; Fri,  1 Apr 2016 00:25:09 -0700 (PDT)
Received: from taos.firemountain.net (taos.firemountain.net [207.114.3.54]) (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 749EB12D539 for <ietf@ietf.org>; Fri,  1 Apr 2016 00:25:09 -0700 (PDT)
Received: from gsp.org (localhost [127.0.0.1]) by taos.firemountain.net (8.15.1/8.14.9) with SMTP id u317P62p007565 for <ietf@ietf.org>; Fri, 1 Apr 2016 03:25:07 -0400 (EDT)
Date: Fri, 1 Apr 2016 03:25:06 -0400
From: Rich Kulawiec <rsk@gsp.org>
To: ietf@ietf.org
Subject: Re: [Recentattendees] Remote Participation for IETF 95: Meetecho Details
Message-ID: <20160401072506.GA22876@gsp.org>
References: <20160330202243.4795.63685.idtracker@ietfa.amsl.com> <56FC7167.4010409@nomountain.net> <A4B09E64B56CD0B8C4379A99@JcK-HP8200.jck.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <A4B09E64B56CD0B8C4379A99@JcK-HP8200.jck.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/SOSzSj6cCx3tm-F9io3deF_uELs>
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: Fri, 01 Apr 2016 07:25:11 -0000

On Thu, Mar 31, 2016 at 02:29:15PM -0400, John C Klensin wrote:
> A registration requirement for remote participants is a major
> policy change and one for people who merely want to passively
> observe is something I believe the community has several times
> concluded is inappropriate given privacy, etc., concerns.  So,
> who made this decision and how?  Unless the answer involves a
> community discussion and Last Call or equivalent process that I
> missed (and apparently Melinda did too), if the answer to "who
> decided" involves anyone in the IETF Leadership, would they
> please offer to resign?

I strongly concur.  Nobody should have to surrender *any* form
of personal identification merely to passively observe.

---rsk


From nobody Fri Apr  1 02:23:02 2016
Return-Path: <tobias.gondrom@gondrom.org>
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 BA02712D0C5 for <ietf@ietfa.amsl.com>; Fri,  1 Apr 2016 02:23:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.059
X-Spam-Level: 
X-Spam-Status: No, score=-100.059 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_DYNAMIC_IPADDR=1.951, HTML_MESSAGE=0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); domainkeys=pass (1024-bit key) header.from=tobias.gondrom@gondrom.org header.d=gondrom.org
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 UxqoGZsn_na3 for <ietf@ietfa.amsl.com>; Fri,  1 Apr 2016 02:22:55 -0700 (PDT)
Received: from lvps5-35-241-16.dedicated.hosteurope.de (www.gondrom.org [5.35.241.16]) (using TLSv1.1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 486DE12D09D for <ietf@ietf.org>; Fri,  1 Apr 2016 02:22:55 -0700 (PDT)
Received: from [192.168.43.211] (ip-2-206-1-207.web.vodafone.de [2.206.1.207]) by lvps5-35-241-16.dedicated.hosteurope.de (Postfix) with ESMTPSA id 10FFD62F35; Fri,  1 Apr 2016 11:22:52 +0200 (CEST)
DomainKey-Signature: a=rsa-sha1;  q=dns; c=nofws; s=default; d=gondrom.org; b=sSFAdae+Ai9V/9+S7LvRiHRKALRtWjfKgT1p/UEFio4nY+1hROARWcYguVehYrR6lwJNVKNfYJAvZqzzHjrG+iGMcSC2F2Rz2WayhuYYahhNTbXznlnH+U7CiFicX22xV8dT6gmAscPUES6ZVCf5pK2YaeC1m9yEptNsmozwwc0=; h=Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:References:In-Reply-To:Content-Type;
Message-ID: <56FE3DEB.4060600@gondrom.org>
Date: Fri, 01 Apr 2016 11:22:51 +0200
From: Tobias Gondrom <tobias.gondrom@gondrom.org>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: rsk@gsp.org, ietf@ietf.org
Subject: Re: [Recentattendees] Remote Participation for IETF 95: Meetecho Details
References: <20160330202243.4795.63685.idtracker@ietfa.amsl.com> <56FC7167.4010409@nomountain.net> <A4B09E64B56CD0B8C4379A99@JcK-HP8200.jck.com> <20160401072506.GA22876@gsp.org>
In-Reply-To: <20160401072506.GA22876@gsp.org>
Content-Type: multipart/alternative; boundary="------------010801070105030902060009"
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/rNhWHqL-6lpUU9tLEZBuQz4P5UI>
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: Fri, 01 Apr 2016 09:23:00 -0000

This is a multi-part message in MIME format.
--------------010801070105030902060009
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit

On 01/04/16 09:25, Rich Kulawiec wrote:
> On Thu, Mar 31, 2016 at 02:29:15PM -0400, John C Klensin wrote:
>> A registration requirement for remote participants is a major
>> policy change and one for people who merely want to passively
>> observe is something I believe the community has several times
>> concluded is inappropriate given privacy, etc., concerns.  So,
>> who made this decision and how?  Unless the answer involves a
>> community discussion and Last Call or equivalent process that I
>> missed (and apparently Melinda did too), if the answer to "who
>> decided" involves anyone in the IETF Leadership, would they
>> please offer to resign?
> I strongly concur.  Nobody should have to surrender *any* form
> of personal identification merely to passively observe.
>
> ---rsk
>

Dear rsk and John,

please excuse my brevity, as I am currently in transit to BA with only 
very limited Internet. So I will need to answer in more detail later.

At first to the question who is responsible: as the chair of the IAOC, 
in the end I am responsible for the actions of the IAOC which includes 
the implementation of the registration for Meetecho (all other remote 
participation tools do not require registration). But I hope you will 
allow for some conversations before you call for my head.

As you know over the last few years, we have made great strides in 
enhancing the remote participation capability to give remote attendees a 
full mirror of local attendees, to a level where you can have full 
active attendance through meetecho, incl. remote presentations, 
comments, questions and so on. With the goal to allow full active remote 
participation capabilities mirroring what we have now for the people who 
attend in person. Is it perfect yet, no, but we are moving towards that 
goal.

The registration of _active_ remote participants has been discussed 
within the IAOC for operational purposes and also to mirror the existing 
IETF process for remote contributions. However, it was not clear when 
this would be feasible from a technical standpoint.
I admit that the current implementation is not as as intended and in 
fact while voicing the intent we did not know when in the timeframe of 
2016 - 2018 it would be possible. And it would have been good to consult 
the community beforehand we execute this step. In some ways our 
operations team did move on the intent a bit faster than expected for 
Meetecho, which can also be considered my fault as I did not explicitly 
halt them and require and spell out the process to do before we take 
this step and did not push for explicitly mandate strong testing of the 
interface before it goes live.

Once I arrive in Buenos Aires, I will review the situation with our IAD 
and the Meetecho team about what they implemented the last few days.

To rsk's comment: please understand that the registration intent is for 
active remote participants. All standalone audio streams are still 
available during sessions. I understand that the current implementation 
for the Meetecho registration may deviate from the intent to sign-up the 
active remote participants. I will need to talk with the Meetecho and 
operations team to understand the scope.

I shall come back to you on all the details as soon as I arrive in 
Buenos Aires and get a chance to discuss with our tech teams.

I apologies for any inconveniences and will be looking forward to seeing 
you all in BA.

Best regards, Tobias (IAOC chair)







--------------010801070105030902060009
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta content="text/html; charset=windows-1252"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">On 01/04/16 09:25, Rich Kulawiec wrote:<br>
    </div>
    <blockquote cite="mid:20160401072506.GA22876@gsp.org" type="cite">
      <pre wrap="">On Thu, Mar 31, 2016 at 02:29:15PM -0400, John C Klensin wrote:
</pre>
      <blockquote type="cite">
        <pre wrap="">A registration requirement for remote participants is a major
policy change and one for people who merely want to passively
observe is something I believe the community has several times
concluded is inappropriate given privacy, etc., concerns.  So,
who made this decision and how?  Unless the answer involves a
community discussion and Last Call or equivalent process that I
missed (and apparently Melinda did too), if the answer to "who
decided" involves anyone in the IETF Leadership, would they
please offer to resign?
</pre>
      </blockquote>
      <pre wrap="">
I strongly concur.  Nobody should have to surrender *any* form
of personal identification merely to passively observe.

---rsk

</pre>
    </blockquote>
    <font face="Arial"><br>
      Dear rsk and John, <br>
      <br>
      please excuse my brevity, as I am currently in transit to BA with
      only very limited Internet. So I will need to answer in more
      detail later. <br>
      <br>
      At first to the question who is responsible: as the chair of the
      IAOC, in the end I am responsible for the actions of the IAOC
      which includes the implementation of the registration for Meetecho
      (all other remote participation tools do not require
      registration). But I hope you will allow for some conversations
      before you call for my head. <br>
      <br>
      As you know over the last few years, we have made great strides in
      enhancing the remote participation capability to give remote
      attendees a full mirror of local attendees, to a level where you
      can have full active attendance through meetecho, incl. remote
      presentations, comments, questions and so on. With the goal to
      allow full active remote participation capabilities mirroring what
      we have now for the people who attend in person. Is it perfect
      yet, no, but we are moving towards that goal. <br>
      <br>
      The registration of _active_ remote participants has been
      discussed within the IAOC for operational purposes and also to
      mirror the existing IETF process for remote contributions.
      However, it was not clear when this would be feasible from a
      technical standpoint. <br>
      I admit that the current implementation is not as as intended and
      in fact while voicing the intent we did not know when in the
      timeframe of 2016 - 2018 it would be possible. And it would have
      been good to consult the community beforehand we execute this
      step. In some ways our operations team did move on the intent a
      bit faster than expected for Meetecho, which can also be
      considered my fault as I did not explicitly halt them and require
      and spell out the process to do before we take this step and did
      not push for explicitly mandate strong testing of the interface
      before it goes live. <br>
      <br>
      Once I arrive in Buenos Aires, I will review the situation with
      our IAD and the Meetecho team about what they implemented the last
      few days. <br>
      <br>
      To rsk's comment: please understand that the registration intent
      is for active remote participants. All standalone audio streams
      are still available during sessions. I understand that the current
      implementation for the Meetecho registration may deviate from the
      intent to sign-up the active remote participants. I will need to
      talk with the Meetecho and operations team to understand the
      scope. <br>
      <br>
      I shall come back to you on all the details as soon as I arrive in
      Buenos Aires and get a chance to discuss with our tech teams. <br>
      <br>
      I apologies for any inconveniences and will be looking forward to
      seeing you all in BA. <br>
      <br>
      Best regards, Tobias (IAOC chair)<br>
      <br>
      <br>
      <br>
      <br>
      <br>
      <br>
    </font>
  </body>
</html>

--------------010801070105030902060009--


From nobody Fri Apr  1 02:57:27 2016
Return-Path: <alexandre.petrescu@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 9C59C12D121 for <ietf@ietfa.amsl.com>; Fri,  1 Apr 2016 02:57:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.333
X-Spam-Level: 
X-Spam-Status: No, score=-5.333 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, SPF_SOFTFAIL=0.665] 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 hqL9W7caIAuw for <ietf@ietfa.amsl.com>; Fri,  1 Apr 2016 02:57:23 -0700 (PDT)
Received: from sainfoin-out.extra.cea.fr (sainfoin-out.extra.cea.fr [132.167.192.145]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 84F8E12D0EA for <ietf@ietf.org>; Fri,  1 Apr 2016 02:57:23 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by sainfoin.extra.cea.fr (8.15.2/8.15.2/CEAnet-Internet-out-2.4) with ESMTP id u319vL4w009184 for <ietf@ietf.org>; Fri, 1 Apr 2016 11:57:21 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id C709520688C for <ietf@ietf.org>; Fri,  1 Apr 2016 11:58:22 +0200 (CEST)
Received: from muguet1.intra.cea.fr (muguet1.intra.cea.fr [132.166.192.6]) by pisaure.intra.cea.fr (Postfix) with ESMTP id BEE9420324D for <ietf@ietf.org>; Fri,  1 Apr 2016 11:58:22 +0200 (CEST)
Received: from [10.8.34.184] (is227335.intra.cea.fr [10.8.34.184]) by muguet1.intra.cea.fr (8.15.2/8.15.2/CEAnet-Intranet-out-1.4) with ESMTP id u319vK0n028918 for <ietf@ietf.org>; Fri, 1 Apr 2016 11:57:20 +0200
Subject: Re: [Recentattendees] Remote Participation for IETF 95: Meetecho Details
To: ietf@ietf.org
References: <20160330202243.4795.63685.idtracker@ietfa.amsl.com> <56FC7167.4010409@nomountain.net> <87EEBBC0-123C-438E-A314-FD2965B092EB@isoc.org>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <56FE4600.9030701@gmail.com>
Date: Fri, 1 Apr 2016 11:57:20 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0
MIME-Version: 1.0
In-Reply-To: <87EEBBC0-123C-438E-A314-FD2965B092EB@isoc.org>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/c5MVjn3MNeoYN8JmUes8J3NC8SM>
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: Fri, 01 Apr 2016 09:57:25 -0000

Le 31/03/2016 20:17, Ray Pelletier a écrit :
> Melinda
>
>> On Mar 30, 2016, at 8:37 PM, Melinda Shore
>> <melinda.shore@nomountain.net> wrote:
>>
>>> On 3/30/16 12:22 PM, IETF Secretariat wrote: 1. Individuals are
>>> required to register for the meeting to observe or participate
>>> via Meetecho.
>>
>> I'm not sure I understand this correctly.  Does this mean that
>> somebody is going to have to register after the meeting to be able
>> to watch archived recordings?
>
> No. All sessions will be available on YouTube, likely within a day or
> so after the session.

If you (meetecho) are able to make it available as it is recorded
without any further delay, I can ensure that many TV VOD services will
be interested (first TV archives were week-after, then day-after, and
recently hour-after).

People in the room, but behind language fences, too can take advantage
of such an immediate archive.  Oftentimes they dont understand at first
what's said, but have connected equipment at hand such as laptop
computers and cameras - ability to replay the last 3 seconds, or so, can
enhance their participation experience, and not last relieve the scribe
efforts.

The network supports it.

Alex

>
>> That doesn't seem correct.  If it's not correct, why does someone
>> have to register to passively watch a session?
>
> All onsite attendees register, even those who passively watching a
> session.  It will also provide an opportunity to survey remote
> attendees to improve the service.
>
>> Will the standalone audio streams still be available during
>> sessions?
>
> Yes, no changes there.
>
> Ray
>>
>> Melinda
>>
>
>


From nobody Fri Apr  1 03:12:58 2016
Return-Path: <stephen.farrell@cs.tcd.ie>
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 B628C12D0FC for <ietf@ietfa.amsl.com>; Fri,  1 Apr 2016 03:12:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.311
X-Spam-Level: 
X-Spam-Status: No, score=-4.311 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cs.tcd.ie
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 yU-wwamsK6HM for <ietf@ietfa.amsl.com>; Fri,  1 Apr 2016 03:12:56 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 192C712D0EA for <ietf@ietf.org>; Fri,  1 Apr 2016 03:12:56 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id D7EC3BE39; Fri,  1 Apr 2016 11:12:54 +0100 (IST)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5BP1EdvcItHZ; Fri,  1 Apr 2016 11:12:53 +0100 (IST)
Received: from [10.87.49.100] (unknown [86.46.30.32]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 227B9BE3F; Fri,  1 Apr 2016 11:12:50 +0100 (IST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; s=mail; t=1459505570; bh=u9Briv4GyYLIPLVDf6bSjfvpFK01aRyTeNAkFN0l4IQ=; h=Subject:To:References:From:Date:In-Reply-To:From; b=0NzjTEG6VNviKyapfhIB5nSMPLOGImm85klkUzRoZQnKxAdoOk+ctXuegPLrjwgxQ qVmxa118adQ9EKLaYJti5NkqowdQMjHy/l7IhPic0YKA8/uyboCPpA6xHwtUESruv6 5A41FFrafjlsb0tazvRCbbWnEUEx1LigCAt+JKlc=
Subject: Re: [Recentattendees] Remote Participation for IETF 95: Meetecho Details
To: John C Klensin <john-ietf@jck.com>, joel jaeggli <joelja@bogus.com>, Melinda Shore <melinda.shore@nomountain.net>, ietf@ietf.org
References: <20160330202243.4795.63685.idtracker@ietfa.amsl.com> <56FC7167.4010409@nomountain.net> <A4B09E64B56CD0B8C4379A99@JcK-HP8200.jck.com> <b982c83c-7de7-516e-11be-0fe7522a93ed@bogus.com> <4C79795B5F7E7C8345C9DC31@JcK-HP8200.jck.com>
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Openpgp: id=D66EA7906F0B897FB2E97D582F3C8736805F8DA2; url=
Message-ID: <56FE49A1.2030607@cs.tcd.ie>
Date: Fri, 1 Apr 2016 11:12:49 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0
MIME-Version: 1.0
In-Reply-To: <4C79795B5F7E7C8345C9DC31@JcK-HP8200.jck.com>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha-256; boundary="------------ms080704060108090101080905"
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/KOQRu36qBdl2KJfqa9ebe8YMbmQ>
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: Fri, 01 Apr 2016 10:12:57 -0000

This is a cryptographically signed message in MIME format.

--------------ms080704060108090101080905
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


John,

On 01/04/16 01:28, John C Klensin wrote:
> However, I think
> there has been a significant breach of community norms and
> expectations about openness, consultation, and transparence.=20

I agree that requiring registration of remote attendees
without having announced that was a mistake.

I agree with those who've said that it might be reasonable
to require remote attendees who want to be in the meetecho
queue-thing to have registered. But even so, that ought be
a thing gets announced ahead of time. Personally I doubt
that such registration is really needed even for the queue
thing, but I'm willing to believe there may be an anti-DoS
benefit there somewhere. That one can ask questions in the
jabber room without registering for the IETF meeting is IMO
just fine.)

So yeah, I think someone (I dunno who) made a mistake. I
expect it's not fixable for this meeting, but can be fixed
for next time.

Having an easier registration experience for those who do
want to register as remote attendees is also something to
fix.

>  I
> also don't know if that failure was by "the community selected
> committee members" or if some staff member is making decisions
> without adequate supervision, but it is a problem either way and
> I hope that whomever is involved will take the situation
> seriously, explain the source or reason for the disconnect to
> the community, and evaluate (along with the community) whether
> they really want to do whatever job they are doing.

That last is just over-reaction and nowhere near justified. I
figure someone made a smallish mistake, nobody died, it can be
and will be fixed. IMO taking the situation seriously requires
us to not over-react in such ways.

Cheers,
S.



--------------ms080704060108090101080905
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIAGCSqGSIb3DQEHAqCAMIACAQExDzANBglghkgBZQMEAgEFADCABgkqhkiG9w0BBwEAAKCC
CvIwggUIMIID8KADAgECAhBPzaE7pzYviUJyhmHTFBdnMA0GCSqGSIb3DQEBCwUAMHUxCzAJ
BgNVBAYTAklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSkwJwYDVQQLEyBTdGFydENvbSBD
ZXJ0aWZpY2F0aW9uIEF1dGhvcml0eTEjMCEGA1UEAxMaU3RhcnRDb20gQ2xhc3MgMSBDbGll
bnQgQ0EwHhcNMTYwMjA5MDkyODE1WhcNMTcwMjA5MDkyODE1WjBOMSIwIAYDVQQDDBlzdGVw
aGVuLmZhcnJlbGxAY3MudGNkLmllMSgwJgYJKoZIhvcNAQkBFhlzdGVwaGVuLmZhcnJlbGxA
Y3MudGNkLmllMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAtuC0rYze/2JinSra
C9F2RjGdQZjNALLcW9C3WKTwYII3wBslobmHuPEYE5JaGItmzuKnAW619R1rD/kfoNWC19N3
rBZ6UX9Cmb9D9exCwYIwVuSwjrCQWGxgCtNQTrwKzCCpI790GRiMTvxvO7UmzmBrCaBLiZW5
R0fBjK5Yn6hUhAzGBkNbkIEL28cLJqH0yVz7Kl92OlzrQqTPEts5m6cDnNdY/ADfeAX18c1r
dxZqcAxhLotrCqgsVA4ilbQDMMXGTLlB5TP35HeWZuGBU7xu003rLcFLdOkD8xvpJoYZy9Kt
3oABXPS5yqtMK+XCNdqmMn+4mOtLwQSMmPCSiQIDAQABo4IBuTCCAbUwCwYDVR0PBAQDAgSw
MB0GA1UdJQQWMBQGCCsGAQUFBwMCBggrBgEFBQcDBDAJBgNVHRMEAjAAMB0GA1UdDgQWBBQJ
QhvwQ5Fl372Z6xqo6fdn8XejTTAfBgNVHSMEGDAWgBQkgWw5Yb5JD4+3G0YrySi1J0htaDBv
BggrBgEFBQcBAQRjMGEwJAYIKwYBBQUHMAGGGGh0dHA6Ly9vY3NwLnN0YXJ0c3NsLmNvbTA5
BggrBgEFBQcwAoYtaHR0cDovL2FpYS5zdGFydHNzbC5jb20vY2VydHMvc2NhLmNsaWVudDEu
Y3J0MDgGA1UdHwQxMC8wLaAroCmGJ2h0dHA6Ly9jcmwuc3RhcnRzc2wuY29tL3NjYS1jbGll
bnQxLmNybDAkBgNVHREEHTAbgRlzdGVwaGVuLmZhcnJlbGxAY3MudGNkLmllMCMGA1UdEgQc
MBqGGGh0dHA6Ly93d3cuc3RhcnRzc2wuY29tLzBGBgNVHSAEPzA9MDsGCysGAQQBgbU3AQIE
MCwwKgYIKwYBBQUHAgEWHmh0dHA6Ly93d3cuc3RhcnRzc2wuY29tL3BvbGljeTANBgkqhkiG
9w0BAQsFAAOCAQEArzrSv2C8PlBBmGuiGrzm2Wma46/KHtXmZYS0bsd43pM66Pc/MsqPE0HD
C1GzMFfwB6BfkJn8ijNSIhlgj898WzjvnpM/SO8KStjlB8719ig/xKISrOl5mX55XbFlQtX9
U6MrqRgbDIATxhD9IDr+ryvovDzChqgQj7mt2jYr4mdlRjsjod3H1VY6XglRmaaNGZfsCARM
aE/TU5SXIiqauwt5KxNGYAY67QkOBs7O1FkSXpTk7+1MmzJMF4nP8QQ5n8vhVNseF+/Wm7ai
9mtnrkLbaznMsy/ULo/C2yuLUWTbZZbf4EKNmVdme6tUDgYkFjAFOblfA7W1fSPiQGagYzCC
BeIwggPKoAMCAQICEGunin0K14jWUQr5WeTntOEwDQYJKoZIhvcNAQELBQAwfTELMAkGA1UE
BhMCSUwxFjAUBgNVBAoTDVN0YXJ0Q29tIEx0ZC4xKzApBgNVBAsTIlNlY3VyZSBEaWdpdGFs
IENlcnRpZmljYXRlIFNpZ25pbmcxKTAnBgNVBAMTIFN0YXJ0Q29tIENlcnRpZmljYXRpb24g
QXV0aG9yaXR5MB4XDTE1MTIxNjAxMDAwNVoXDTMwMTIxNjAxMDAwNVowdTELMAkGA1UEBhMC
SUwxFjAUBgNVBAoTDVN0YXJ0Q29tIEx0ZC4xKTAnBgNVBAsTIFN0YXJ0Q29tIENlcnRpZmlj
YXRpb24gQXV0aG9yaXR5MSMwIQYDVQQDExpTdGFydENvbSBDbGFzcyAxIENsaWVudCBDQTCC
ASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAL192vfDon2D9luC/dtbX64eG3XAtRmv
mCSsu1d52DXsCR58zJQbCtB2/A5uFqNxWacpXGGtTCRk9dEDBlmixEd8QiLkUfvHpJX/xKnm
VkS6Iye8wUbYzMsDzgnpazlPg19dnSqfhM+Cevdfa89VLnUztRr2cgmCfyO9Otrh7LJDPG+4
D8ZnAqDtVB8MKYJL6QgKyVhhaBc4y3bGWxKyXEtx7QIZZGxPwSkzK3WIN+VKNdkiwTubW5PI
dopmykwvIjLPqbJK7yPwFZYekKE015OsW6FV+s4DIM8UlVS8pkIsoGGJtMuWjLL4tq2hYQuu
N0jhrxK1ljz50hH23gA9cbMCAwEAAaOCAWQwggFgMA4GA1UdDwEB/wQEAwIBBjAdBgNVHSUE
FjAUBggrBgEFBQcDAgYIKwYBBQUHAwQwEgYDVR0TAQH/BAgwBgEB/wIBADAyBgNVHR8EKzAp
MCegJaAjhiFodHRwOi8vY3JsLnN0YXJ0c3NsLmNvbS9zZnNjYS5jcmwwZgYIKwYBBQUHAQEE
WjBYMCQGCCsGAQUFBzABhhhodHRwOi8vb2NzcC5zdGFydHNzbC5jb20wMAYIKwYBBQUHMAKG
JGh0dHA6Ly9haWEuc3RhcnRzc2wuY29tL2NlcnRzL2NhLmNydDAdBgNVHQ4EFgQUJIFsOWG+
SQ+PtxtGK8kotSdIbWgwHwYDVR0jBBgwFoAUTgvvGqRAW6UXaYcwyjRoQ9BBrvIwPwYDVR0g
BDgwNjA0BgRVHSAAMCwwKgYIKwYBBQUHAgEWHmh0dHA6Ly93d3cuc3RhcnRzc2wuY29tL3Bv
bGljeTANBgkqhkiG9w0BAQsFAAOCAgEAi+P3h+wBi4StDwECW5zhIycjBL008HACblIf26HY
0JdOruKbrWDsXUsiI0j/7Crft9S5oxvPiDtVqspBOB/y5uzSns1lZwh7sG96bYBZpcGzGxpF
NjDmQbcM3yl3WFIRS4WhNrsOY14V7y2IrUGsvetsD+bjyOngCIVeC/GmsmtbuLOzJ606tEc9
uRbhjTu/b0x2Fo+/e7UkQvKzNeo7OMhijixaULyINBfCBJb+e29bLafgu6JqjOUJ9eXXj20p
6q/CW+uVrZiSW57+q5an2P2i7hP85jQJcy5j4HzA0rSiF3YPhKGAWUxKPMAVGgcYoXzWydOv
Z3UDsTDTagXpRDIKQLZo02wrlxY6iMFqvlzsemVf1odhQJmi7Eh5TbxI40kDGcBOBHhwnaOu
mZhLP+SWJQnjpLpSlUOj95uf1zo9oz9e0NgIJoz/tdfrBzez76xtDsK0KfUDHt1/q59BvDI7
RX6gVr0fQoCyMczNzCTcRXYHY0tq2J0oT+bsb6sH2b4WVWAiJKnSYaWDjdA70qHX4mq9MIjO
/ZskmSY8wtAk24orAc0vwXgYanqNsBX5Yv4sN4Z9VyrwMdLcusP7HJgRdAGKpkR2I9U4zEsN
JQJewM7S4Jalo1DyPrLpL2nTET8ZrSl5Utp1UeGp/2deoprGevfnxWB+vHNQiu85o6MxggPM
MIIDyAIBATCBiTB1MQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRDb20gTHRkLjEpMCcG
A1UECxMgU3RhcnRDb20gQ2VydGlmaWNhdGlvbiBBdXRob3JpdHkxIzAhBgNVBAMTGlN0YXJ0
Q29tIENsYXNzIDEgQ2xpZW50IENBAhBPzaE7pzYviUJyhmHTFBdnMA0GCWCGSAFlAwQCAQUA
oIICEzAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0xNjA0MDEx
MDEyNDlaMC8GCSqGSIb3DQEJBDEiBCD+dqpZoQzg6pyhB8Z0VMns8+YoEmqLF0bWgDmd+bXi
dzBsBgkqhkiG9w0BCQ8xXzBdMAsGCWCGSAFlAwQBKjALBglghkgBZQMEAQIwCgYIKoZIhvcN
AwcwDgYIKoZIhvcNAwICAgCAMA0GCCqGSIb3DQMCAgFAMAcGBSsOAwIHMA0GCCqGSIb3DQMC
AgEoMIGaBgkrBgEEAYI3EAQxgYwwgYkwdTELMAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0
Q29tIEx0ZC4xKTAnBgNVBAsTIFN0YXJ0Q29tIENlcnRpZmljYXRpb24gQXV0aG9yaXR5MSMw
IQYDVQQDExpTdGFydENvbSBDbGFzcyAxIENsaWVudCBDQQIQT82hO6c2L4lCcoZh0xQXZzCB
nAYLKoZIhvcNAQkQAgsxgYyggYkwdTELMAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0Q29t
IEx0ZC4xKTAnBgNVBAsTIFN0YXJ0Q29tIENlcnRpZmljYXRpb24gQXV0aG9yaXR5MSMwIQYD
VQQDExpTdGFydENvbSBDbGFzcyAxIENsaWVudCBDQQIQT82hO6c2L4lCcoZh0xQXZzANBgkq
hkiG9w0BAQEFAASCAQBQbqUj+CrAL8xzoMlA2DtRJlURHstdNk8CM497iut4dj3Y+nrz2mJc
8TVwoLNGozkMGRVSDtaifjy08EJNzIITWmVbor6uYaHH+f5eANwlItMmMuRg+MrlSWnhKggn
gzpkqyQl1szPZKFUk84QT00+v/OEuD0YceoJdqyKBu3wtM4ZwTWx8L+86nArRl+VtYfPbQ83
3vilnF4i1kuOvq5qyjnW38fuZiVQSUbrm4iZMcebeKefvUxywyGYpMep3+PgGH/IgSaqSmPh
2MWZufGQ78Z+N0lSGNeUU/O6Omfsscswwnpx6c1co0Q9c09bnDCC936fnrEIOuNkpwxYd8wo
AAAAAAAA
--------------ms080704060108090101080905--


From nobody Fri Apr  1 03:37:13 2016
Return-Path: <daedulus@btconnect.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 7999B12D6AD for <ietf@ietfa.amsl.com>; Fri,  1 Apr 2016 03:37:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=btconnect.onmicrosoft.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 4fy4NXmIHxgo for <ietf@ietfa.amsl.com>; Fri,  1 Apr 2016 03:37:09 -0700 (PDT)
Received: from emea01-am1-obe.outbound.protection.outlook.com (mail-am1on0734.outbound.protection.outlook.com [IPv6:2a01:111:f400:fe00::734]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 48EB812D674 for <ietf@ietf.org>; Fri,  1 Apr 2016 03:36:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=btconnect.onmicrosoft.com; s=selector1-btconnect-com; h=From:To:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=ocyyMEfbWlwGqb6sjKc27mmfswcqLlBVftKHKgs+e58=; b=F0kx/E4elLDdxShrChdMIY0gIzwBnwS3kYJqrEi2+EmRzomNFjIZCbi4jMVaP8O5vVMBITJ9ELXfNUcOZON4c6Z7zSUjdBcvg+8VEUQGPwgKDHDpBsAzW0435Llhkz+AWS3qmA4BZ5ngCHP5o76kK4FGtg133Uamij2OiDfe1pI=
Authentication-Results: cridland.net; dkim=none (message not signed) header.d=none; cridland.net; dmarc=none action=none header.from=btconnect.com; 
Received: from pc6 (81.132.199.159) by DB5PR07MB1557.eurprd07.prod.outlook.com (10.165.212.135) with Microsoft SMTP Server (TLS) id 15.1.447.10; Fri, 1 Apr 2016 10:36:20 +0000
Message-ID: <018501d18c01$f04402e0$4001a8c0@gateway.2wire.net>
From: tom p. <daedulus@btconnect.com>
To: Dave Cridland <dave@cridland.net>
References: <20160320223116.8946.76840.idtracker@ietfa.amsl.com> <949EF20990823C4C85C18D59AA11AD8BADEAFFC7@FR712WXCHMBA11.zeu.alcatel-lucent.com> <CA+9kkMCsT43ZCSdq8gdKXu1k4pJgbf0ab5tE=dDiFfrTT2gtkA@mail.gmail.com> <949EF20990823C4C85C18D59AA11AD8BADEB0D16@FR712WXCHMBA11.zeu.alcatel-lucent.com> <56F79D05.8070004@alvestrand.no> <326E6502-28E5-4D09-BB99-4A5D80625EB0@stewe.org> <56F88E18.2060506@it.aoyama.ac.jp> <20160328104731.GO88304@verdi> <CALaySJ+hYMMsKE7Ws-NJbyqH55E-mQM-duTEcJGc0TWvTP88Ew@mail.gmail.com> <20160328132859.GP88304@verdi> <28975138-9EA1-4A9F-A6C0-BC1416B8EA44@sobco.com> <CALaySJJkNj2jfm0gJpuDzq8oFDjTNn-uQ5MHdmEOLwTiFZUyQQ@mail.gmail.com> <56FBDE33.5000706@nostrum.com> <56FBE3F2.10507@dcrocker.net> <CAKHUCzyhUwxvk3sQzZGHHZf-vh8B9wtp4DQ9qRcJ0sdi3o1UNw@mail.gmail.com> <CALaySJJkTEc3xPA_V3yHauq8vSM_hwG-1nQCAPNUThORqm-vpw@mail.gmail.com> <CAKHUCzwxnypwL7Fv=GUKvvkAWt4kzBt=msjSWEDsq=d=pP+2WA@mail.gmail.com>
Subject: Re: [rtcweb] Uppercase question for RFC2119 words
Date: Fri, 1 Apr 2016 11:33:19 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Originating-IP: [81.132.199.159]
X-ClientProxiedBy: DB4PR06CA0052.eurprd06.prod.outlook.com (10.160.40.180) To DB5PR07MB1557.eurprd07.prod.outlook.com (10.165.212.135)
X-MS-Office365-Filtering-Correlation-Id: b7f5078d-1b01-482d-3064-08d35a19772c
X-Microsoft-Exchange-Diagnostics: 1; DB5PR07MB1557; 2:uvEjfRwWncEoQbC09e+2kyrYV6aNz5ZujcIp1/7h6vM83RoAndf5F5+djLUVvlpE9d/0Yxwiy3Fpzy2MC8WG3zOpkt4XlM0VAR+QryiEsl84osYK4V1c75SJcMGCkYDJC38pasqzBUUFnLz/lQDQX7xrkbfeYhXCuxYP9HJtsruXm+YMYewTTZeAfdFn/5jD; 3:5gf+IQkiBz/qO8/lkWS6/CYp9CpehPeW1Anw7BImI9IJzsihH1Og5zEDgQxleR+SYYByeysYhRQsgTIQSnxEkb+6b0/iVDLF+YKHYc3bnsATRmiizPg2bw0y/Cy/P6c+; 25:04oqbl6X/vFf8ekZVD50SSSFTHrywkgNm3pCPa4u9pswTxOe/6cgFeD2Oe+7Q0ctigSsHIVTozsvpMuIUu4feEHnmK2MWCzchpr60CFAklMYnwbT0xTjuAaOKY/KvSNHseRiFjijC1ONtastja+X4rO84gaHw9dQGEkl22KCdKUdI9yTM4prUkws+TfSwWduawI4E39ni2OeCAD879z6TaKXhfW6SsGf/yFERHg2Uld8okj+Ydpcv3asxV8Rd6OZW4YVPgbSe1nM9CYu/xZySJ8c+meSuSs6axiRSAm9VknFU5BA6ZbGPF+czhGFqNrXF8QfzyGUL5AmUsBtkiKQa7A0b1eIWOWWR34l8ryJYBI=
X-Microsoft-Antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:DB5PR07MB1557;
X-Microsoft-Antispam-PRVS: <DB5PR07MB1557BEA26CA220EE323A6B78C69A0@DB5PR07MB1557.eurprd07.prod.outlook.com>
X-Exchange-Antispam-Report-Test: UriScan:;
X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(601004)(2401047)(8121501046)(5005006)(3002001)(10201501046); SRVR:DB5PR07MB1557; BCL:0; PCL:0; RULEID:; SRVR:DB5PR07MB1557; 
X-Microsoft-Exchange-Diagnostics: 1; DB5PR07MB1557; 4:rdYq5P62TEMT21GI2pd3Y9N2LFP+70/oXyIiaLmhKVUREPG7Vdg1VHENRAkkrvoBQf72yw78vbGVB68bvLCbIn5zqfPXe0pr8OO9yeJncIa18x9VDDYFcsCKWAR/pHsU9m9fhWjcC1T3aYj6h+qI3VWFJOZ1cZodXjEJDf4azBzMlpN3lm1r8os1PaXEQJsuTjugWKGdcy9zFOQ7+UzyT5bNBBlFhhDlCyZ68BrIOz380O0CSJZJPooJOWjyoB2R9R2Cdqt20ElwX1ejHtCrMaXUICu1G5PbHGoMKDsTDLF/siSD2vvzWkyUswbO6662vKkU3byAouoo2vVszAO5MqBhxpCUP4T1t2NeKfpd1U2CvRtjHhaOa3u8Gbb1y3Qp
X-Forefront-PRVS: 0899B47777
X-Forefront-Antispam-Report: SFV:NSPM; SFS:(10019020)(4630300001)(6009001)(377454003)(13464003)(51444003)(24454002)(5004730100002)(42186005)(86362001)(189998001)(92566002)(19580395003)(66066001)(23676002)(81816999)(33646002)(81686999)(19580405001)(77096005)(76176999)(50986999)(47776003)(50466002)(50226001)(44716002)(61296003)(3846002)(6116002)(81166005)(1096002)(93886004)(5008740100001)(230700001)(586003)(2906002)(62236002)(4326007)(110136002)(4720700001); DIR:OUT; SFP:1102; SCL:1; SRVR:DB5PR07MB1557; H:pc6; FPR:; SPF:None; MLV:sfv;  LANG:en; 
X-Microsoft-Exchange-Diagnostics: =?utf-8?B?MTtEQjVQUjA3TUIxNTU3OzIzOm56UWNPSFNpdG1wZFgvYzBhVFBmWHVnbkYx?= =?utf-8?B?T0Y0Vmp2WkR2MlRsSS94RFJ2Qlp4amFDQ0s1a3BkM2hlWTVRZG91WkZuazhZ?= =?utf-8?B?QTJWNDVzcG1XU2JTOFJzT0dsQ2dQSnNpOVR4ajZQd0tuS0lIZUdZK2Yyblpv?= =?utf-8?B?QUNHNjI4TkFpT1I5WXhFdWJSZytiaDZxNlFBeitMd1pHK1paWWRPS0czcHRP?= =?utf-8?B?K3h0NnUyU2NVV3Brdklmbld4WTVVMTJ6OW1hNkRrQVpDVTFXcktYNDFNNm9h?= =?utf-8?B?bFFwTm93ZVhrTnZTQ01oaWcrdVd6dEdkZFl2ZFZLMFJwY085ZlpINWc3QXZS?= =?utf-8?B?dmgxcXBUakh0ODlCOUFwSDJndllrZVJTNzE1QkpOZTl3OG0xK0t4Zms5N2hN?= =?utf-8?B?cFBEbWFBdGpSUGNJdmcwdWJocGtORDBUUjFUdStYSmRZbE1NRFdKV05hV0hR?= =?utf-8?B?cnIxMEJkRHk3OXcrekhTTzZ5dm5CWXg0QkFmcVJzNEora0VTNUdVcTMzRWdx?= =?utf-8?B?WXpJcXdRaWRqeXE4eDhWTllJT3o3UXFUdXhHeTg5Ly9WODREcVJ4S1Q5R2FB?= =?utf-8?B?QTJ4VC80QmtPSjNCMzR3Sks3UnBjMEVaYVd5QlBKQWxYcXBKZmkybFZ3dmtw?= =?utf-8?B?YmVKYzN5UHNVRWVMTWJkZUo5cHJYNFR3UU1jR1NmUnFBbGd0a2Z6Wk5CTXpG?= =?utf-8?B?N1NXOG45YVNRRkZRclUyWmN3WFYwZExiZXYvS2t6STJDcng3U1FvNVlEQXBS?= =?utf-8?B?VUIvMXd4RVJJa3owc1pHQXluNVF4ZTViMEpCWVZ0QTk0L1JXQ1dTQlJqZWFW?= =?utf-8?B?cS9mVGU4K1J6UUk1M21mOUJHNHBuaVN5a29EcWMrQVY3cVVWZmlhMEFBQ0hL?= =?utf-8?B?OWdKWlJBbUZmM0krMThGT3ByR1ExS0NpSWdvYjlSYkYweFY5YTdzWGt0RWhT?= =?utf-8?B?b2N0Z2VPWG50UEVkL09vb2o5cjg2S1NOb3lycE85MW1pYzZnSkp1Umc0Z1Jr?= =?utf-8?B?ZGh1My9Kdm11OHhQNGg5bVc4Ukl1Qi9QcXdDRkNjVFJtelJtZlhSUjU4SzVW?= =?utf-8?B?eGp0cVJSWStsQy9tMDNQSEp1VFdMUkhhTUVFbzQvL1ByQ0JrVzd1Q3ZWVnVI?= =?utf-8?B?NXR5djRvZDI2TVFYYXozKzVMY1pzMzByOVRjU1R3VnlSMDVIYzRndnpHaUtF?= =?utf-8?B?VmhSMitWYUEvMDdLZks1eDRKWVdGcUJYSTlyN3czQ2ViT3lILy9JV08rQ0t3?= =?utf-8?B?ek56QlJWNHJQWHVNZnZEazU4VE5qdWQ1MnZCbXBiSENqT2dlMXFsajhwUksw?= =?utf-8?B?Q2dqS1FOZkNiVHZPKzRsRW1KeksxaUZmcGM0SlhxUmg5a01OR3VROC9NODM4?= =?utf-8?B?ZlZpSWhWTThDVDJobDN6cm5GRS9tbmc3ZitmQTR3PT0=?=
X-Microsoft-Exchange-Diagnostics: 1; DB5PR07MB1557; 5:cdPA/+ntrnVv9jt3ZzuCjMsTL5qCyioQTy1n76TLHv1F1bMMWbAGPc2t7+13LGFdh9KsCs+Ua/qLVVg8aZhA75YZEWan3mXzalPL/EHPVwPtuKF1h3KFpdXzrJlq8J50BnGRCCV+G6NhnwuwqTV0Lw==; 24:cFxT1a02QbphwBHtELwSYzO8KKhwtEwsZ1Il9EIQnbNEa8EqNE3G9UEOO8zROWBYoBwlxFn+ILEAAMYpmLgqtvIyCS7/5bvDM0W4o9CB2vY=
SpamDiagnosticOutput: 1:23
SpamDiagnosticMetadata: NSPM
X-OriginatorOrg: btconnect.com
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 01 Apr 2016 10:36:20.7407 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB5PR07MB1557
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/qgvNcD3rKPNgq5Ew-Ivrib3OSUo>
Cc: "Heather Flanagan \(RFC Series Editor\)" <rse@rfc-editor.org>, IETF discussion list <ietf@ietf.org>, Dave Crocker <dcrocker@bbiw.net>
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: Fri, 01 Apr 2016 10:37:11 -0000

----- Original Message -----
From: "Dave Cridland" <dave@cridland.net>
Sent: Wednesday, March 30, 2016 8:00 PM


> On 30 March 2016 at 18:59, Barry Leiba <barryleiba@computer.org>
wrote:
>
> For future reference, I tend not to zero-index my sentences. ;-)
>
> I think that MUST/SHOULD/MAY (the former two tempered by NOT) are
> well-understood, although the strength of SHOULD is usually
underestimated.
> OPTIONAL is probably obvious enough (though its implications may not
be),
> and SHALL/RECOMMENDED are uncommon enough that they're probably not
> understood nearly as well.

I would echo Brian's earlier comment that it is SHOULD and MAY that are
troublesome, while MUST and SHALL mean what they usually do and so do
not require further thought.  I read an I-D for a protocol using HTTP as
transport that said that if the server found the client not authorised
to access a resource, then it SHOULD return a 404 but MAY return a 403.

I think that that usage is ok but I also think it not compliant with
RFC2119 and it is the kind of scenario that the RFC ought to address.
The underlying issue I see for this case is that 'we are using HTTP and
have no control over what it says and you will be using an off the shelf
HTTP package and so will have no control over what it generates so like
it or lump it (strictly a personal interpretation of this).

Also, I see a number of ADs pushing for a SHOULD to be accompanied in
the I-D by the valid reasons why it will not happen, as opposed to
leaving it up to the implementor, and again, I see this as not
compliant, but again, I see it as a good idea.

Tom Petch

> > As a complete side thing, I wonder how this all seems to
> > German-speakers, as German uses initial caps for all nouns.  I
wonder
> > if anyone even notices if someone fails to do that.  I wonder if it
> > becomes puzzling, perhaps in some instances.
> >
> > Barry
> >
>


From nobody Fri Apr  1 08:47:39 2016
Return-Path: <john-ietf@jck.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 A19F312D69D for <ietf@ietfa.amsl.com>; Fri,  1 Apr 2016 08:47:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] 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 9X7U3godyxwA for <ietf@ietfa.amsl.com>; Fri,  1 Apr 2016 08:47:36 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E306C12D64E for <ietf@ietf.org>; Fri,  1 Apr 2016 08:47:35 -0700 (PDT)
Received: from [198.252.137.10] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1am1IG-00085q-HW; Fri, 01 Apr 2016 11:47:28 -0400
Date: Fri, 01 Apr 2016 11:47:23 -0400
From: John C Klensin <john-ietf@jck.com>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Subject: Re: [Recentattendees] Remote Participation for IETF 95: Meetecho Details
Message-ID: <6E69E3CBF10E406DF7EB72B0@JcK-HP8200.jck.com>
In-Reply-To: <56FE49A1.2030607@cs.tcd.ie>
References: <20160330202243.4795.63685.idtracker@ietfa.amsl.com> <56FC7167.4010409@nomountain.net> <A4B09E64B56CD0B8C4379A99@JcK-HP8200.jck.com> <b982c83c-7de7-516e-11be-0fe7522a93ed@bogus.com> <4C79795B5F7E7C8345C9DC31@JcK-HP8200.jck.com> <56FE49A1.2030607@cs.tcd.ie>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/OT3LwMUhpigaavurk2PBpc1utWg>
Cc: Melinda Shore <melinda.shore@nomountain.net>, 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: Fri, 01 Apr 2016 15:47:37 -0000

--On Friday, April 01, 2016 11:12 +0100 Stephen Farrell
<stephen.farrell@cs.tcd.ie> wrote:

>...
> I agree that requiring registration of remote attendees
> without having announced that was a mistake.

See below.  However, some of this (and my reaction) is OBE given
Tobias's note, so I'll save a longer and more detailed response
for another time.
 
> I agree with those who've said that it might be reasonable
> to require remote attendees who want to be in the meetecho
> queue-thing to have registered. But even so, that ought be
> a thing gets announced ahead of time. Personally I doubt
> that such registration is really needed even for the queue
> thing, but I'm willing to believe there may be an anti-DoS
> benefit there somewhere. That one can ask questions in the
> jabber room without registering for the IETF meeting is IMO
> just fine.)

To reprise part of the discussion the last time the community
discussed this, there are IPR and (while the IETF continues to
ignore them and hope there will never be a problem)
competitiveness/ antitrust issues that suggest that we should,
to the extent possible, know who is participating in and
influencing our decisions (see the recent threads about IPR/Note
Well revisions).   That point of view suggests registration for
Jabber participants too.  There are tradeoffs with that line of
reasoning (presumably including those that cause your doubts),
but they are exactly why an open community discussion is needed.

> So yeah, I think someone (I dunno who) made a mistake. I
> expect it's not fixable for this meeting, but can be fixed
> for next time.

See below.  Because of the tradeoffs, I'm less worried about
what the decision is than that we discuss it openly and
carefully.

> Having an easier registration experience for those who do
> want to register as remote attendees is also something to
> fix.

As Dave Crocker pointed out, fine-tuning the details is a
different problem and something we can improve as we go along.
Certainly I would have preferred that things have been
sufficiently thought out to get them closer to right the first
time, but so it goes.  On the other hand, it is clearly the
IAD's and IAOC's responsibility to be sure that a change is
really ready before deploying it.  As Tobias acknowledges, that
didn't work this time.

>>  I
>> also don't know if that failure was by "the community selected
>> committee members" or if some staff member is making decisions
>> without adequate supervision, but it is a problem either way
>> and I hope that whomever is involved will take the situation
>> seriously, explain the source or reason for the disconnect to
>> the community, and evaluate (along with the community) whether
>> they really want to do whatever job they are doing.

> That last is just over-reaction and nowhere near justified. I
> figure someone made a smallish mistake, nobody died, it can be
> and will be fixed. IMO taking the situation seriously requires
> us to not over-react in such ways.

Well, maybe. I think we should probably defer the rest of this
discussion until Tobias gets to BA and is able to consider the
situation and explain in more detail.  However, I recall a long
series of difficulties with the IASA failing to come up to
expectations for transparency and disclosure that seemed very
clear when BCP 101 was deployed.  That pattern can't be blamed
on Tobias because it started long before he go onto the IAOC.
However, I believe that every IAOC member appointed by the IETF
community has two sets of responsibilities -- to be sure the
administrative side of things is run properly and responsibly
and to operate a transparent process with the community kept
informed and that is responsive to community discussions and
conclusions.   

It is a huge oversimplification, but, whether we are talking
about this issue with changes in registration policy, questions
about meeting site selection and criteria, late and/or
uninformative minutes, posting of contracts, or other issues, it
appears to me that there has been enough of a pattern that it
really is time for IAOC members to carefully examine whether
they, and the people and systems for whom they are responsible,
are really as committed to the transparency, openness,
consultation, and responsiveness of their role as they are to
simple prudent financial management... and for the community to
start requiring that they be accountable if IASA behavior is not
consistent with those principles.

If you think _that_ is an overreaction, I suppose we will just
have to disagree.

    best,
     john


From nobody Fri Apr  1 09:08:00 2016
Return-Path: <Lee@asgard.org>
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 1B56F12D1A3 for <ietf@ietfa.amsl.com>; Fri,  1 Apr 2016 09:07:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.258
X-Spam-Level: 
X-Spam-Status: No, score=-0.258 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DATE_IN_PAST_03_06=1.592, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RCVD_IN_SORBS_WEB=0.77] autolearn=no 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 p5k4GOiUgC02 for <ietf@ietfa.amsl.com>; Fri,  1 Apr 2016 09:07:57 -0700 (PDT)
Received: from atl4mhob11.myregisteredsite.com (atl4mhob11.myregisteredsite.com [209.17.115.49]) by ietfa.amsl.com (Postfix) with ESMTP id AD68312D18C for <ietf@ietf.org>; Fri,  1 Apr 2016 09:07:57 -0700 (PDT)
Received: from mailpod.hostingplatform.com ([10.30.71.203]) by atl4mhob11.myregisteredsite.com (8.14.4/8.14.4) with ESMTP id u31G7rTT032205 for <ietf@ietf.org>; Fri, 1 Apr 2016 12:07:53 -0400
Received: (qmail 32574 invoked by uid 0); 1 Apr 2016 16:07:53 -0000
X-TCPREMOTEIP: 200.61.9.66
X-Authenticated-UID: lee@asgard.org
Received: from unknown (HELO ?172.16.5.211?) (lee@asgard.org@200.61.9.66) by 0 with ESMTPA; 1 Apr 2016 16:07:52 -0000
User-Agent: Microsoft-MacOutlook/14.6.1.160122
Date: Fri, 01 Apr 2016 13:07:43 +0100
Subject: Re: [rtcweb] Uppercase question for RFC2119 words
From: Lee Howard <Lee@asgard.org>
To: "tom p." <daedulus@btconnect.com>, Dave Cridland <dave@cridland.net>
Message-ID: <D32422B8.DC13D%Lee@asgard.org>
Thread-Topic: [rtcweb] Uppercase question for RFC2119 words
References: <20160320223116.8946.76840.idtracker@ietfa.amsl.com> <949EF20990823C4C85C18D59AA11AD8BADEAFFC7@FR712WXCHMBA11.zeu.alcatel-lucent.com> <CA+9kkMCsT43ZCSdq8gdKXu1k4pJgbf0ab5tE=dDiFfrTT2gtkA@mail.gmail.com> <949EF20990823C4C85C18D59AA11AD8BADEB0D16@FR712WXCHMBA11.zeu.alcatel-lucent.com> <56F79D05.8070004@alvestrand.no> <326E6502-28E5-4D09-BB99-4A5D80625EB0@stewe.org> <56F88E18.2060506@it.aoyama.ac.jp> <20160328104731.GO88304@verdi> <CALaySJ+hYMMsKE7Ws-NJbyqH55E-mQM-duTEcJGc0TWvTP88Ew@mail.gmail.com> <20160328132859.GP88304@verdi> <28975138-9EA1-4A9F-A6C0-BC1416B8EA44@sobco.com> <CALaySJJkNj2jfm0gJpuDzq8oFDjTNn-uQ5MHdmEOLwTiFZUyQQ@mail.gmail.com> <56FBDE33.5000706@nostrum.com> <56FBE3F2.10507@dcrocker.net> <CAKHUCzyhUwxvk3sQzZGHHZf-vh8B9wtp4DQ9qRcJ0sdi3o1UNw@mail.gmail.com> <CALaySJJkTEc3xPA_V3yHauq8vSM_hwG-1nQCAPNUThORqm-vpw@mail.gmail.com> <CAKHUCzwxnypwL7Fv=GUKvvkAWt4kzBt=msjSWEDsq=d=pP+2WA@mail.gmail.com> <018501d18c01$f04402e0$4001a8c0@gateway.2wire.net>
In-Reply-To: <018501d18c01$f04402e0$4001a8c0@gateway.2wire.net>
Mime-version: 1.0
Content-type: text/plain; charset="ISO-8859-1"
Content-transfer-encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/CLjiZ5BP_JN9k2Yc8CrOprI9LH4>
Cc: "Heather Flanagan \(RFC Series Editor\)" <rse@rfc-editor.org>, IETF discussion list <ietf@ietf.org>, Dave Crocker <dcrocker@bbiw.net>
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: Fri, 01 Apr 2016 16:07:59 -0000

On 4/1/16, 11:33 AM, "ietf on behalf of tom p." <ietf-bounces@ietf.org on
behalf of daedulus@btconnect.com> wrote:

>
>Also, I see a number of ADs pushing for a SHOULD to be accompanied in
>the I-D by the valid reasons why it will not happen, as opposed to
>leaving it up to the implementor, and again, I see this as not
>compliant, but again, I see it as a good idea.


The above is what I would expect.

"there
   may exist valid reasons in particular circumstances to ignore a
   particular item, but the full implications must be understood and
   carefully weighed before choosing a different course.=B2

Some examples of those cases is useful in understanding why =B3SHOULD=B2 is
used. It might not be an exhaustive list.

Lee


>
>Tom Petch
>
>> > As a complete side thing, I wonder how this all seems to
>> > German-speakers, as German uses initial caps for all nouns.  I
>wonder
>> > if anyone even notices if someone fails to do that.  I wonder if it
>> > becomes puzzling, perhaps in some instances.
>> >
>> > Barry
>> >
>>
>
>



From nobody Fri Apr  1 09:13:08 2016
Return-Path: <jari.arkko@piuha.net>
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 4161D12D0D8 for <ietf@ietfa.amsl.com>; Fri,  1 Apr 2016 09:13:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] 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 2YoGECAiJHmM for <ietf@ietfa.amsl.com>; Fri,  1 Apr 2016 09:13:05 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 9444912D0CC for <ietf@ietf.org>; Fri,  1 Apr 2016 09:13:04 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 297622CCBF; Fri,  1 Apr 2016 19:13:03 +0300 (EEST) (envelope-from jari.arkko@piuha.net)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id os72hoOxRnTH; Fri,  1 Apr 2016 19:13:02 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 7FC1F2CC9A; Fri,  1 Apr 2016 19:13:01 +0300 (EEST) (envelope-from jari.arkko@piuha.net)
Subject: Re: [Recentattendees] Remote Participation for IETF 95: Meetecho Details
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Content-Type: multipart/signed; boundary="Apple-Mail=_E3A2DB1C-0239-4F30-AF6D-D54126C2A754"; protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail 2.5.2
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <6E69E3CBF10E406DF7EB72B0@JcK-HP8200.jck.com>
Date: Fri, 1 Apr 2016 13:12:58 -0300
Message-Id: <73558EB2-C193-4976-80DE-A988DE1BE7AE@piuha.net>
References: <20160330202243.4795.63685.idtracker@ietfa.amsl.com> <56FC7167.4010409@nomountain.net> <A4B09E64B56CD0B8C4379A99@JcK-HP8200.jck.com> <b982c83c-7de7-516e-11be-0fe7522a93ed@bogus.com> <4C79795B5F7E7C8345C9DC31@JcK-HP8200.jck.com> <56FE49A1.2030607@cs.tcd.ie> <6E69E3CBF10E406DF7EB72B0@JcK-HP8200.jck.com>
To: John C Klensin <john-ietf@jck.com>, Stephen Farrell <stephen.farrell@cs.tcd.ie>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/e8YP0Qz2m3diPMQlYb7FZQ_Omrk>
Cc: IETF discussion list <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: Fri, 01 Apr 2016 16:13:07 -0000

--Apple-Mail=_E3A2DB1C-0239-4F30-AF6D-D54126C2A754
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252

For what it is worth, I do think changing the registration requirement =
without discussion or even an announcement was a mistake. I=92m sorry.

I do have a personal opinion in this topic, and it is that just like in =
the physical meeting, I mostly want to know who I am talking to. That =
shouldn=92t be a hard requirement, however, just like it isn=92t in, =
say, list discussion. And I certainly agree that when you are only =
observing there=92s even less requirement to do so. However, this is a =
complex matter involving, for instance, IPR, note wells, ability to get =
feedback from participants, understand who participates in the IETF, =
possibly an evolving IETF meeting fee model (see =
draft-arkko-ietf-trends-and-observations), privacy, and probably a few =
other aspects as well.

I think we should have that discussion (again, but the world is =
evolving), and see where we end up. And the above was just my opinion, =
I=92m sure we=92ll have other opinions.

In the meantime (and with most of my leadership team members on =
airplanes), I=92ve asked if we can change the requirement to a =
recommendation, and no longer require registration. Meetecho is working =
on it. Also, the secretariat  is changing the registration page so that =
it doesn=92t ask unnecessary questions from remote participants from =
those that want to register.

Overall IAOC transparency question is worth another thread, I think.

Jari


--Apple-Mail=_E3A2DB1C-0239-4F30-AF6D-D54126C2A754
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQIcBAEBCgAGBQJW/p4LAAoJEM80gCTQU46qk1YP/Awba1MIxI4LJ7tq1cNnEJtw
7aKEFGxBF0qYjt06bNminQUb/QQgAU1O3fUSkRhngEBnZTT5VtNNVFhsEdSDzptD
WuD4vmyK575m72Foy4SDOelpONxaLqezUkooVE+B7GPcOqWV+dwrbEAJ3IYjf3MK
9/GixGsMV9qLWuQhrnA1hM9XN5qZ5184+MRInt4ZY5JvCwu/18sgevnr5C20l6fV
qyK5vSQzzNRy8RjZcmwq8QcSjEoopBit/CiRJ17uCtDqAJJzDZbIw6aiYFICyL4Z
swFXv8RQmslyQQ2mPtchEIMiA892VBEUaTQ0QpB15a53CWqiABoTodP57aJmuZ1D
hak+Ubq1ede4gwT+TmmHtilg4M+KUkS6ehcxlVzfH24Fe7tEyXUfZ4LlJTqdTNSV
MU+mvJLx5tcPH74WOUlNo5e4US3NFvGSNPVEUieM4u5l9YJUykL5bBhRtpIGyZrY
J+kuoY2bxZIuqPWoBaU2tSS3JD3Qj0rDk8+Xd1+He6iorAQI+TF9mastA7w9/gFO
bkM0gnA4g0FAGnh3JRfjJLMMsBOd9CTi4Sz4C9i5WDKL76TQd/s7PuHDc1L7Kq+J
qJtcp2+NeRUs+eXlZCpsiTgYp0tX1IKDjoyJOTogGYxekR98ms0yj4SAqoi1T0+o
JoEpyVBygyyyEQ+IY10K
=A28O
-----END PGP SIGNATURE-----

--Apple-Mail=_E3A2DB1C-0239-4F30-AF6D-D54126C2A754--


From nobody Fri Apr  1 09:52:18 2016
Return-Path: <chair@ietf.org>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from [172.20.7.224] (200-127-148-163.net.prima.net.ar [200.127.148.163]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPSA id D838712D5BC; Fri,  1 Apr 2016 09:52:10 -0700 (PDT)
Content-Type: text/plain; charset=windows-1252
Subject: RFC 7776 and the team that can be reached for help regarding harassment concerns
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: IETF Chair <chair@ietf.org>
Date: Fri, 1 Apr 2016 13:52:07 -0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <16A28658-0ADD-43BD-832A-2BD37D921653@ietf.org>
To: IETF Announcement List <ietf-announce@ietf.org>, 95all@ietf.org
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/e4eZNU4KT3WS8NkSwRyLLruqq3M>
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: chair@ietf.org, IETF discussion list <ietf@ietf.org>
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: Fri, 01 Apr 2016 16:52:12 -0000

In 2013, the IESG set the IETF anti-harassment policy. Last year, we =
concluded the process to write a BCP that defines the anti-harassment =
procedures. That BCP has now been published as RFC 7776. The RFC =
specifies that there shall be a specialist team that can be reached for =
help, advice, and possible actions regarding harassment concerns.

I=92m happy to announce that Allison Mankin, Pete Resnick, and Linda =
Klieforth have accepted to become the initial members in this team. They =
are preparing for this role, working on their operating practices as =
defined by the RFC, and we are setting up additional training for them. =
I am though happy to have them serving in this role, given that they =
have a lot of experience. Allison and Pete of course have a long =
experience about the IETF culture, topics, and leadership roles. In =
addition, Pete has volunteer experience from violence and discrimination =
related tasks. Linda Klieforth has been the acting ombudsperson for the =
IETF since 2013, and is the head of HR at ISOC. And Allison has a lot of =
experience about the way IETF selects leadership.

Please welcome Linda, Allison, and Pete to this role. Feel free to =
contact them if you have any concerns, they are a very easy set of =
people to talk to, they will be here in Buenos Aires, and obviously =
everything you tell them will be kept in confidence as requested, as =
defined in the RFC.

Links:

RFC http://tools.ietf.org/html/rfc7776
Policy =
https://www.ietf.org/iesg/statement/ietf-anti-harassment-policy.html
Team page and contact information https://www.ietf.org/ombudsteam

Jari Arkko, IETF Chair

P.S. Also, while this addition isn=92t strictly about harassment, this =
seems like a good moment to remind everyone about behaving nicely. =
Please pay attention to how you interact with other people in the =
meeting and elsewhere. Think how you present criticism, for instance, =
and behave otherwise in a professional manner. I know you will, but =
sometimes spending a few seconds to think about how you go about a =
situation can make the experience so much better for everyone.

P.P.S. As with other announcements, if you reply to mail sent to =
ietf-announce or 95all lists, please make sure that your reply goes to =
the appropriate discussion list such as ietf@ietf.org or =
95attendees@ietf.org. Posting to the announcement lists is restricted, =
and we want discussions on other lists.


From nobody Fri Apr  1 10:25:37 2016
Return-Path: <john-ietf@jck.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 7B03812D669 for <ietf@ietfa.amsl.com>; Fri,  1 Apr 2016 10:25:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] 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 Kxg0d_ZxI4XF for <ietf@ietfa.amsl.com>; Fri,  1 Apr 2016 10:25:35 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F2D4112D0F3 for <ietf@ietf.org>; Fri,  1 Apr 2016 10:25:34 -0700 (PDT)
Received: from [198.252.137.10] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1am2p7-0008Np-Pc; Fri, 01 Apr 2016 13:25:29 -0400
Date: Fri, 01 Apr 2016 13:25:24 -0400
From: John C Klensin <john-ietf@jck.com>
To: Jari Arkko <jari.arkko@piuha.net>, Stephen Farrell <stephen.farrell@cs.tcd.ie>
Subject: Re: [Recentattendees] Remote Participation for IETF 95: Meetecho Details
Message-ID: <F8FFEEC0FC510D99538C57D4@JcK-HP8200.jck.com>
In-Reply-To: <73558EB2-C193-4976-80DE-A988DE1BE7AE@piuha.net>
References: <20160330202243.4795.63685.idtracker@ietfa.amsl.com> <56FC7167.4010409@nomountain.net> <A4B09E64B56CD0B8C4379A99@JcK-HP8200.jck.com> <b982c83c-7de7-516e-11be-0fe7522a93ed@bogus.com> <4C79795B5F7E7C8345C9DC31@JcK-HP8200.jck.com> <56FE49A1.2030607@cs.tcd.ie> <6E69E3CBF10E406DF7EB72B0@JcK-HP8200.jck.com> <73558EB2-C193-4976-80DE-A988DE1BE7AE@piuha.net>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/T08FLSAfTMYm_xVq0U0o1O2qpvM>
Cc: IETF discussion list <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: Fri, 01 Apr 2016 17:25:36 -0000

Jari,

Many thanks, both for your note generally and for the request to
undo the registration requirement for this meeting if that is
possible.   Given that and as the person whose outrage at the
situation touched off these threads, I'd like to suggest that we
dial back the discussion now and trust Jari (and, as
appropriate, Tobias) to organize a more focused discussion as
soon as they consider appropriate and feasible.  

Unfortunately, it sometimes does require a mistake and
mini-crisis to bring fundamental issues to the front of the
queue.

thanks again,
    john


--On Friday, April 01, 2016 13:12 -0300 Jari Arkko
<jari.arkko@piuha.net> wrote:

> For what it is worth, I do think changing the registration
> requirement without discussion or even an announcement was a
> mistake. I'm sorry.
> 
> I do have a personal opinion in this topic, and it is that
> just like in the physical meeting, I mostly want to know who I
> am talking to. That shouldn't be a hard requirement,
> however, just like it isn't in, say, list discussion. And I
> certainly agree that when you are only observing there's
> even less requirement to do so. However, this is a complex
> matter involving, for instance, IPR, note wells, ability to
> get feedback from participants, understand who participates in
> the IETF, possibly an evolving IETF meeting fee model (see
> draft-arkko-ietf-trends-and-observations), privacy, and
> probably a few other aspects as well.
> 
> I think we should have that discussion (again, but the world
> is evolving), and see where we end up. And the above was just
> my opinion, I'm sure we'll have other opinions.
> 
> In the meantime (and with most of my leadership team members
> on airplanes), I've asked if we can change the requirement
> to a recommendation, and no longer require registration.
> Meetecho is working on it. Also, the secretariat  is changing
> the registration page so that it doesn't ask unnecessary
> questions from remote participants from those that want to
> register.
> 
> Overall IAOC transparency question is worth another thread, I
> think.
> 
> Jari
> 





From nobody Fri Apr  1 11:31:18 2016
Return-Path: <stephen.farrell@cs.tcd.ie>
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 7A69312D65F for <ietf@ietfa.amsl.com>; Fri,  1 Apr 2016 11:31:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.311
X-Spam-Level: 
X-Spam-Status: No, score=-4.311 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cs.tcd.ie
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 9W2Hz81nEvgv for <ietf@ietfa.amsl.com>; Fri,  1 Apr 2016 11:31:15 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 253B012D52E for <ietf@ietf.org>; Fri,  1 Apr 2016 11:31:15 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id DEA2DBE35; Fri,  1 Apr 2016 19:31:13 +0100 (IST)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pX9TEVju0Fyz; Fri,  1 Apr 2016 19:31:12 +0100 (IST)
Received: from [10.12.8.12] (unknown [37.205.61.206]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 575B0BE29; Fri,  1 Apr 2016 19:31:12 +0100 (IST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; s=mail; t=1459535472; bh=bbuVOITuLFSoJsa1lSSCnLanQ6RajYfF6A/EkOG1/c0=; h=Subject:To:References:Cc:From:Date:In-Reply-To:From; b=2YJJAk+wntlivBEUIpDcpag5uCVQE93qtbwmXvmZdI3He5Bh6CpdYg+6BafPzlLLL 0h8GRoZBO/jv/qKvGVJ/LN2xWYSFIFPIrmoypCUxxxVTtAOTo2AEqEBETr84nnCw6y 7L2FMbc63o1LLK/FKkFbyv+2ikmbTz8cp5guTrAk=
Subject: Re: [Recentattendees] Remote Participation for IETF 95: Meetecho Details
To: Jari Arkko <jari.arkko@piuha.net>, John C Klensin <john-ietf@jck.com>
References: <20160330202243.4795.63685.idtracker@ietfa.amsl.com> <56FC7167.4010409@nomountain.net> <A4B09E64B56CD0B8C4379A99@JcK-HP8200.jck.com> <b982c83c-7de7-516e-11be-0fe7522a93ed@bogus.com> <4C79795B5F7E7C8345C9DC31@JcK-HP8200.jck.com> <56FE49A1.2030607@cs.tcd.ie> <6E69E3CBF10E406DF7EB72B0@JcK-HP8200.jck.com> <73558EB2-C193-4976-80DE-A988DE1BE7AE@piuha.net>
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Openpgp: id=D66EA7906F0B897FB2E97D582F3C8736805F8DA2; url=
Message-ID: <56FEBE6F.8050308@cs.tcd.ie>
Date: Fri, 1 Apr 2016 19:31:11 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0
MIME-Version: 1.0
In-Reply-To: <73558EB2-C193-4976-80DE-A988DE1BE7AE@piuha.net>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="CgeII4isxRbsxeRh4EDQnR4nfFcir6r0w"
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/HuL3bnyW1h2D2otYhZGDQQizgCk>
Cc: IETF discussion list <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: Fri, 01 Apr 2016 18:31:16 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--CgeII4isxRbsxeRh4EDQnR4nfFcir6r0w
Content-Type: multipart/mixed; boundary="X8Xs87DKEeqP0QjQffUeFRg4u2tts1QgM"
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
To: Jari Arkko <jari.arkko@piuha.net>, John C Klensin <john-ietf@jck.com>
Cc: IETF discussion list <ietf@ietf.org>
Message-ID: <56FEBE6F.8050308@cs.tcd.ie>
Subject: Re: [Recentattendees] Remote Participation for IETF 95: Meetecho
 Details
References: <20160330202243.4795.63685.idtracker@ietfa.amsl.com>
 <56FC7167.4010409@nomountain.net>
 <A4B09E64B56CD0B8C4379A99@JcK-HP8200.jck.com>
 <b982c83c-7de7-516e-11be-0fe7522a93ed@bogus.com>
 <4C79795B5F7E7C8345C9DC31@JcK-HP8200.jck.com> <56FE49A1.2030607@cs.tcd.ie>
 <6E69E3CBF10E406DF7EB72B0@JcK-HP8200.jck.com>
 <73558EB2-C193-4976-80DE-A988DE1BE7AE@piuha.net>
In-Reply-To: <73558EB2-C193-4976-80DE-A988DE1BE7AE@piuha.net>

--X8Xs87DKEeqP0QjQffUeFRg4u2tts1QgM
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable



On 01/04/16 17:12, Jari Arkko wrote:
> Overall IAOC transparency question is worth another thread, I think.

I reckon I do agree with you and John on that. It's pretty
easy for well intended folks to end up not being transparent
and well worth spending a bit of time/effort on seeing if
we can match current expectations met elsewhere whilst also
being efficient with all the myriad of IAOC stuff that is being
done well.

S.



--X8Xs87DKEeqP0QjQffUeFRg4u2tts1QgM--

--CgeII4isxRbsxeRh4EDQnR4nfFcir6r0w
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQEcBAEBCAAGBQJW/r5wAAoJEC88hzaAX42iXWQH/RFRq5D8q1PixHUmJbNWhqeH
W2mj1vvDhC7FM5yP1TocE12mCxEQvTZhAcqQ++68Ebf6xC3NYDzmr60mosU6lgPz
f5FebmspGQ/JMXuEVHZ1/Va5TuVEoNBIcOguMd3k1FBVXUfxq3hUlaPwUmQt4e5I
Z/35Zj3MMtoQKZTRKF+DvPcDhFa/w90WpcVRKzVLLT40nwjcEWpcxrwFOsPSa4OZ
YCv0QwE2s7GxEhWPks+S922j1Rct0nYTJAl963faiX+k4eFlHVdIlrlJU6HNZjRD
Td2iqhWku/8DiMBZBvTaPchQRAivd0g5DBa6TKU/3PTZwN2CZTzPqTeEznntvps=
=MeU8
-----END PGP SIGNATURE-----

--CgeII4isxRbsxeRh4EDQnR4nfFcir6r0w--


From nobody Fri Apr  1 23:24:40 2016
Return-Path: <oej@edvina.net>
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 D901612D673; Fri,  1 Apr 2016 23:24:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] 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 jqgokYLKiosl; Fri,  1 Apr 2016 23:24:36 -0700 (PDT)
Received: from smtp7.webway.se (smtp7.webway.se [212.3.14.205]) by ietfa.amsl.com (Postfix) with ESMTP id 5EFA612D642; Fri,  1 Apr 2016 23:24:36 -0700 (PDT)
Received: from [192.168.40.18] (h87-96-134-129.dynamic.se.alltele.net [87.96.134.129]) by smtp7.webway.se (Postfix) with ESMTPA id 9717793C2A2; Sat,  2 Apr 2016 06:23:49 +0000 (UTC)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 9.2 \(3112\))
Subject: Re: RFC 7776 and the team that can be reached for help regarding harassment concerns
From: "Olle E. Johansson" <oej@edvina.net>
In-Reply-To: <16A28658-0ADD-43BD-832A-2BD37D921653@ietf.org>
Date: Sat, 2 Apr 2016 08:24:32 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <31DF410E-615B-4F9F-B814-4ED35D9A773E@edvina.net>
References: <16A28658-0ADD-43BD-832A-2BD37D921653@ietf.org>
To: ietf@ietf.org, chair@ietf.org
X-Mailer: Apple Mail (2.3112)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/EZdrERn10v7d54DHmwgtBD_MVGk>
Cc: Olle E Johansson <oej@edvina.net>, IETF Announcement List <ietf-announce@ietf.org>, 95all@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: Sat, 02 Apr 2016 06:24:39 -0000

> On 01 Apr 2016, at 18:52, IETF Chair <chair@ietf.org> wrote:
>=20
>=20
> In 2013, the IESG set the IETF anti-harassment policy. Last year, we =
concluded the process to write a BCP that defines the anti-harassment =
procedures. That BCP has now been published as RFC 7776. The RFC =
specifies that there shall be a specialist team that can be reached for =
help, advice, and possible actions regarding harassment concerns.
>=20
> I=92m happy to announce that Allison Mankin, Pete Resnick, and Linda =
Klieforth have accepted to become the initial members in this team. They =
are preparing for this role, working on their operating practices as =
defined by the RFC, and we are setting up additional training for them. =
I am though happy to have them serving in this role, given that they =
have a lot of experience. Allison and Pete of course have a long =
experience about the IETF culture, topics, and leadership roles. In =
addition, Pete has volunteer experience from violence and discrimination =
related tasks. Linda Klieforth has been the acting ombudsperson for the =
IETF since 2013, and is the head of HR at ISOC. And Allison has a lot of =
experience about the way IETF selects leadership.
>=20
> Please welcome Linda, Allison, and Pete to this role. Feel free to =
contact them if you have any concerns, they are a very easy set of =
people to talk to, they will be here in Buenos Aires, and obviously =
everything you tell them will be kept in confidence as requested, as =
defined in the RFC.
>=20
It makes me proud that the IETF has done this. It=92s a big step forward =
and hopefully sets the standard for other groups.=20

A big thank you to everyone involved!

/Olle


From nobody Sat Apr  2 07:52:57 2016
Return-Path: <goi-ietf@m.gmane.org>
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 A691812D111 for <ietf@ietfa.amsl.com>; Sat,  2 Apr 2016 07:52:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.611
X-Spam-Level: 
X-Spam-Status: No, score=-2.611 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 fYFZ_zUY4T9P for <ietf@ietfa.amsl.com>; Sat,  2 Apr 2016 07:52:51 -0700 (PDT)
Received: from plane.gmane.org (plane.gmane.org [80.91.229.3]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BCB4D12D0A0 for <ietf@ietf.org>; Sat,  2 Apr 2016 07:52:51 -0700 (PDT)
Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from <goi-ietf@m.gmane.org>) id 1amMuu-00005G-Bg for ietf@ietf.org; Sat, 02 Apr 2016 16:52:48 +0200
Received: from smtp.adb-centralen.se ([193.10.5.129]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for <ietf@ietf.org>; Sat, 02 Apr 2016 16:52:48 +0200
Received: from linus by smtp.adb-centralen.se with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for <ietf@ietf.org>; Sat, 02 Apr 2016 16:52:48 +0200
X-Injected-Via-Gmane: http://gmane.org/
To: ietf@ietf.org
From: Linus Nordberg <linus@nordberg.se>
Subject: Re: Changes regarding IETF website CDN settings and TOR networks
Date: Sat, 02 Apr 2016 16:52:27 +0200
Lines: 59
Message-ID: <87a8lc9i6s.fsf@nordberg.se>
References: <3BD5282D-8E06-4DC5-B64F-D577326E2A5E@ietf.org> <CABtrr-XHZoO9T5hK1piy4y0zW6pxGMXfRFGcccXAMtFDrFg3fw@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain
X-Complaints-To: usenet@ger.gmane.org
X-Gmane-NNTP-Posting-Host: smtp.adb-centralen.se
User-Agent: Gnus/5.13 (Gnus v5.13)
Cancel-Lock: sha1:RpnR8O5LRJToW2rg+7iIkZxzaHo=
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/LXES7aNZDelaEkYA6ZYdkSwd42Y>
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, 02 Apr 2016 14:52:55 -0000

Those of you who read the CloudFlare post might also be interested in
Tor Project's recent post questioning the 94% figure:
https://blog.torproject.org/blog/trouble-cloudflare

Joseph Lorenzo Hall <joe@cdt.org> wrote
Thu, 31 Mar 2016 22:32:57 -0700:

| IETF folks may be interested in this recent cloudflare post that outlines
| some potential changes to Tor -- SHA-256 hashes for hidden service certs,
| move proof-of-work into TorBrowser -- that could make this a bit more
| robust against automated malicious activity (unfortunate title IMO):
| 
| http://blog.cloudflare.com/the-trouble-with-tor/
| 
| On Monday, March 28, 2016, IETF Chair <chair@ietf.org> wrote:
| 
| > Based on earlier feedback on IETF discussion list, the IAOC has decided to
| > ask the IETF network admins to make a change with regards to how our CDN
| > serves clients coming from TOR networks.
| >
| > For background, our website uses a number of techniques to help combat
| > denial-of-service attacks.  One of these mechanisms was based on CAPTCHAs
| > that were triggered, in particular, for some users when accessing the IETF
| > web site for the first time and heuristically identified as coming from a
| > TOR exit node.  Once the CAPTCHA is passed, the user was able to browse
| > normally.  However, in the process of performing the CAPTCHA and accessing
| > the IETF website, cookies and scripts are used, which was a concern for
| > some users.
| >
| > Information on the IETF website is meant to be public, and should be
| > openly accessible for as broad consumption as technically and practically
| > possible. When there are groups of people whose access to the website is
| > for some reason problematic, we try to accommodate better access, no matter
| > who makes such request, within the bounds of what is practical, of course,
| > and considering the potential effects of denial-of-service attacks and
| > other issues.
| >
| > The change in our settings is to no longer perform CAPTCHAs or other extra
| > mechanisms for clients coming from TOR networks.  Behaviour for other users
| > should not be affected, though it is an open question whether any
| > significant denial-of-service attacks could be launched from these networks.
| >
| > Please note that the our admins are monitoring the situation, and have the
| > ability to change this configuration at any time. So if the TOR exit nodes
| > are the source of an attack, for instance, the configuration could be
| > adjusted again. And of course, further actions regarding how the IETF
| > website is run are based on our experiences from current and past setups,
| > and your feedback.
| >
| > Jari Arkko, IETF Chair
| >
| 
| 
| -- 
| Joseph Lorenzo Hall
| Chief Technologist, Center for Democracy & Technology [https://www.cdt.org]e: joe@cdt.org, p: 202.407.8825, pgp: https://josephhall.org/gpg-keyFingerprint: 3CA2 8D7B 9F6D DBD3 4B10  1607 5F86 6987 40A9 A871
| 
| CDT's annual dinner, Tech Prom, is April 6, 2016!
| https://cdt.org/annual-dinner


From nobody Sat Apr  2 12:32:04 2016
Return-Path: <worley@alum.mit.edu>
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 94F0112D62E for <ietf@ietfa.amsl.com>; Fri,  1 Apr 2016 12:54:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.934
X-Spam-Level: 
X-Spam-Status: No, score=-1.934 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_SOFTFAIL=0.665] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=comcast.net
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 j2QMybhBgR7R for <ietf@ietfa.amsl.com>; Fri,  1 Apr 2016 12:54:19 -0700 (PDT)
Received: from resqmta-po-04v.sys.comcast.net (resqmta-po-04v.sys.comcast.net [IPv6:2001:558:fe16:19:96:114:154:163]) (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 4DE4012D5E3 for <ietf@ietf.org>; Fri,  1 Apr 2016 12:54:19 -0700 (PDT)
Received: from resomta-po-08v.sys.comcast.net ([96.114.154.232]) by comcast with SMTP id m58haO1bcIY3Mm598a5OSs; Fri, 01 Apr 2016 19:54:18 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1459540458; bh=GoW6J3I9err2ltKCUd6AnI5ywkPWKqbPR94nmE4wv4k=; h=Received:Received:Received:Received:From:To:Subject:Date: Message-ID; b=E20Ard82d1DdyD1h6v7Z3NuGvAtpFvnkAnwX6JStLnppzzMhxc06wE7GepOsRoQz5 91QrH5IPXBicLrY0+VAao24HRlOhTorsk927bsBeR7VmA2mdUDLJFhM5knWUhkTGSq NpCwtZFpU38xdFdqSoU8TGojGE/ELQG5uHMLsBZKqnzxO6fBwMcsAGDXxiTe+9YMNr BOjDLhtZy/EF3m+0EhAHX6oM0w9maRrNMKZymRywu1VdQwabxFaKkeSmxUB+qk8W4u uFVZyRgchYOVabXrE0rXi/oydtUVP3tJN5ZPxkRoNYbU0HiabgVijWD+b7jfv4kPjj lVyYXlh2pAXfQ==
Received: from hobgoblin.ariadne.com ([73.143.237.82]) by resomta-po-08v.sys.comcast.net with comcast id d7uH1s00G1nMCLR017uH4G; Fri, 01 Apr 2016 19:54:18 +0000
Received: from hobgoblin.ariadne.com (hobgoblin.ariadne.com [127.0.0.1]) by hobgoblin.ariadne.com (8.14.7/8.14.7) with ESMTP id u31JsHx4001003; Fri, 1 Apr 2016 15:54:17 -0400
Received: (from worley@localhost) by hobgoblin.ariadne.com (8.14.7/8.14.7/Submit) id u31JsGna001000; Fri, 1 Apr 2016 15:54:16 -0400
X-Authentication-Warning: hobgoblin.ariadne.com: worley set sender to worley@alum.mit.edu using -f
From: worley@ariadne.com (Dale R. Worley)
To: gen-art@ietf.org, draft-ietf-bfd-seamless-use-case.all@ietf.org, ietf@ietf.org, rtg-bfd@ietf.org
Subject: Gen-ART IETF Last Call review of draft-ietf-bfd-seamless-use-case-04
Sender: worley@ariadne.com (Dale R. Worley)
Date: Fri, 01 Apr 2016 15:54:16 -0400
Message-ID: <87pou9p0k7.fsf@hobgoblin.ariadne.com>
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/GA5q3AlpibnQ-mk297tGuHxcsdQ>
X-Mailman-Approved-At: Sat, 02 Apr 2016 12:32:02 -0700
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: Fri, 01 Apr 2016 19:54:21 -0000

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please treat these comments just
like any other last call comments.

For more information, please see the FAQ at

<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Document: draft-ietf-bfd-seamless-use-case-04
Reviewer: Dale R. Worley
Review Date: 2016-04-01
IETF LC End Date: 2016-04-12
IESG Telechat date: 2016-05-05

Summary:

This draft is on the right track but has open issues, described in the
review.

Major issues:

In various places the description needs to be made clearer.  I believe
that the authors have a good idea of what is intended, but in some
places the descriptions are not clear to the general reader.

Nits/editorial comments:

There are various problems with English usage (e.g., missing articles)
and punctuation (e.g., excessive commas), which can be taken care of
by the Editor.  But the overall structure and clarity of several
paragraphs needs improvement.

----------------------------------------------------------------------

General

What is the meaning of "seamless"?  The term "seamless BFD" is used in
the title and in the title of section 2, "Introduction to Seamless
BFD", and in exactly one other place in the document:

   If this information is already known to the end-points of a potential
   BFD session, the initial handshake including an exchange of this
   node-specific information is unnecessary and it is possible for the
   end points to begin BFD messaging seamlessly.

At no point is "seamless BFD" or the specific meaning of "seamless"
defined.

I suspect that the authors have a strong intuitive sense of the
behaviors they identify as "seamless", and it would be helpful if that
could be stated in the Introduction.

Abstract

The Abstract reads:

   This document provides various use cases for Bidirectional Forwarding
   Detection (BFD) and various requirements such that extensions could
   be developed to allow for simplified detection of forwarding
   failures.

It seems unlikely that adding extensions to a protocol will "simplify"
it (other than in the case of "MPLS BFD Session Per ECMP Path"), so it
seems that the Abstract could be phrased better.

It seems like a major goal of the draft is making it possible to
accelerate the establishment of a BFD session.  But that is not
mentioned in the Abstract.

Section 1

   Bidirectional Forwarding Detection (BFD) is a lightweight protocol,
   as defined in [RFC5880], used to detect forwarding failures.  Various
   protocols and applications rely on BFD for failure detection.  Even
   though the protocol is simple, there are certain use cases, where
   faster setting up of sessions and continuity check of the data
   forwarding paths is necessary.  This document identifies various use
   cases and requirements related to those, such that necessary
   enhancements could be made to BFD protocol.

The phrase "Even though the protocol is simple" is not relevant to the
remainder of the sentence it appears in and probably can be deleted.

"This document..." would better be "This document identifies these use
cases and the consequent requirements for extensions to the BFD
protocol."

The phrase "continuity check of the data forwarding paths" seems to be
disconnected.  I suspect the problem is a lack of parallelism, due to
"setting up" and "check".  You probably want to say "faster setting up
of sessions and faster continuity checking of the data forwarding
paths".

The phrase "complexity, not only from an operations point of view, but
also in terms of the speed at which these sessions could be
established or deleted" attaches "speed" to "complexity", which isn't
quite correct.  Better would be "creates operational complexity, but
also causes undesirable delay in establishing or deleting sessions"

Section 2

The second paragraph says:

   In order for BFD to be able to initially verify that a
   connection is valid and that it connects the expected set of end
   points, it is necessary to provide the node information associated
   with the connection at each end point prior to initiating BFD
   sessions, such that this information can be used to verify that the
   connection is up and verifiable.

I think it would help if the nature of the "node information" was made
explicit.  It seems like this paragraph strongly related to the
aspect of BFD that is *not* defined in RFC 5880:

   The method of demultiplexing the initial packets (in which Your
   Discriminator is zero) is application dependent, and is thus outside
   the scope of this specification.

Presumably the "node information" is what is used to perform the
demultiplexing of the initial packets.  Explaining this in more detail
might make the design problem(s) clearer to the inexperienced reader.

The third paragraph seems to be about accelerating the establishment
of a BFD session between two nodes.  With baseline BFD, establishing a
session requires the two nodes to exchange BFD packets, which include
the discriminators assigned by each node to the session.  It seems
that a goal of this draft is to avoid needing to exchange the initial
packets before the BFD session is established, with the goal of
getting to the established state more quickly.  But this is not
explicitly stated, nor is the manner in which "seamless BFD" would
avoid it.  As far as I can tell, the problem is that before a session
is established, BFD is limited to sending one packet per second, and
so the establishment of a session requires one or two seconds,
regardless of the speed of the link.

If the time to establish a BFD session is of central concern, it would
be helpful to present an analysis of how long it takes baseline BFD to
establish a session, and how long it might take an alternative BFD
startup method to establish a session.

In addition to the discriminators, the initial BFD packets also
include the BFD packet interval parameters, "Detect Mult", "Desired
Min TX Interval", "Required Min RX Interval", and "Required Min Echo
RX Interval".  What allows BFD to have a very short Detection Time
in favorable situations is that the interval parameters can be much
shorter than one second.  But that implies that any system for
quick-starting a BFD session has to transmit the interval parameters
as well as the discriminators, or the BFD startup process still has to
exchange packets before the full sending rate has been established.

Then again, perhaps the phrase "node information" in this paragraph
includes the interval parameters, instead of just the discriminators
mentioned in the previous paragraph, in which case that should be made
clearer.

Is the fourth paragraph a description of the proposed "seamless BFD"
and how it differs from baseline BFD?

The fourth paragraph contains "Each of those network entities is
assigned a BFD discriminator, to establish a BFD session."  But this
seems to be incorrect -- each network entity is assigned a BFD
discriminator for each BFD session that the entity will participate in
(RFC 5880 section 6.3).  I can't tell whether this is a fundamental
misunderstanding on the part of the authors, merely incorrect wording,
or if S-BFD includes a technique by which a node can use the same
discriminator for all of its BFD sessions -- that should be clarified.

Section 3.1

This section isn't clear about the distinction between "verifying
forwarding in one direction only" and "not needing to provision the
target node, only the source node" -- the first is a relaxation on the
requirements on what BFD detects, the second is a strengthening on the
requirements on how BFD can be configured.

Despite saying that the target would not need to be configured, as
discussed in this section, BFD would still need to be configured at
the target node to know the discriminator of the source node:  "When
the targeted network entity receives the packet, it knows that BFD
packet, based on the discriminator and processes it."

I am not understanding the sense in which "unidirectional" is being
used.  It seems that the only need is to verify transmission in one
direction between the two nodes.  The target node can verify
successful transmission if it receives the control packets from the
source node.  But the source node can only know that transmission is
working if it receives reply nodes from the target node.  So despite
that only needing to test transmission in one direction, transmission
must be done in both directions.  Or the purpose to send the live/dead
determination to the "centralized controller", and it is not required
that the source know the state of the path?

Section 3.2

The first paragraph is

   BFD provides data delivery confidence when reachability validation is
   performed prior to traffic utilizing specific paths/LSPs.  However
   this comes with a cost, where, traffic is prevented to use such
   paths/LSPs until BFD is able to validate the reachability, which
   could take seconds due to BFD session bring-up sequences [RFC5880],
   LSP ping bootstrapping [RFC5884], etc.  This use case could be well
   supported by eliminating the need for session negotiation and
   discriminator exchanges in order to establish the BFD session.

As far as I can tell, the use case is "when reachability validation is
performed prior to traffic utilizing specific paths/LSPs".  But the
first sentence isn't structured to emphasize that, so it's difficult
to tell what "This use case" means.  Better would be some thing like

   This use case is when BFD is used to verify reachability before
   sending traffic via a path/LSP.  This comes with a cost, which is
   that traffic is prevented to use the path/LSP until BFD is able to
   validate the reachability, which could take seconds ... .  This use
   case would be better supported by eliminating the need for the
   initial BFD session negotiation.

The second paragraph says "All it takes is for the network entities to
know what the discriminator values to be used for the session."  But
as in section 2, the interval parameters must be configured as well
before a BFD session is functioning.

Section 3.3

The last two paragraphs are

   Traditional BFD session establishment and validation of the
   forwarding path must not become a bottleneck in the case of
   centralized traffic engineering.  If the controller or other
   centralized entity is able to instantly verify a forwarding path of
   the TE tunnel , it could steer the traffic onto the traffic
   engineered tunnel very quickly thus minimizing adverse effect on a
   service.  This is especially useful and needed when the scale of the
   network and number of TE tunnels is very high.

Don't use the word "instantly":  Nothing happens "instantly" if it
involves events at two or more physically distinct locations.
(299,792,458 metres per second -- It's not just a good idea, it's the
law!)

   The cost associated with BFD session negotiation and establishment of
   BFD sessions to identify valid paths is very high and providing
   network redundancy becomes a critical issue.

It would help to specify that the "cost" is primarily due to the time
delay:  "The cost associated with the time required for BFD session
negotiation and ... is very high when providing network redundancy is
a critical issue."

Section 3.4

The final paragraph is:

   To support this use case, BFD MUST be able to perform liveness
   detection initated from centralized controller for any given segment
   under its domain.

This isn't a requirement on BFD per se, it's a requirement on the
agents that implement BFD in nodes.  But that is not a protocol
requirement either, since this document isn't specifying a protocol
between a centralized controller and a BFD agent.  I think what is
intended is that there should be a standard way by which a centralized
controller can instruct the two BFD agents in two nodes to initiate a
BFD session along a path, and then can then monitor whether the BFD
session determines that the path between the nodes is working.  But if
so, that should be stated clearly.

Section 3.5

The final paragraph is:

   The established BFD session parameters and attributes like
   transmission interval, receiver interval, etc., MUST be modifiable
   without changing the state of the session.

Unfortunately, the term "state" has this definition (RFC 5880 section
4.1):

   State (Sta)

      The current BFD session state as seen by the transmitting system.
      Values are:

         0 -- AdminDown
         1 -- Down
         2 -- Init
         3 -- Up

It seems to me that the requirement is better captured by the last
sentence of the preceding paragraph:  "In these scenarios, it is
desirable for BFD to slow down, speed up, stop or resume at will witho
minimal [sic] additional BFD packets exchanged to establish a new or
modified session."  But that sentence is not quite good enough, since
what the preceding part of the paragraph asked for was "... with no
additional BFD packets exchanged", whereas the final sentence says
"minimal".

What is the requirement?  If it is "no additional packets", that's
clear.  If what is needed is a reduction in the additional packets, it
would help if there was an analysis of how many additional packets are
now needed and what potential reduction might be obtained, so that the
reader has some idea what "minimal" means.

Section 3.6

First, this use case needs to make it clear what it is testing:  That
a source node can send a packet to an anycast address, and that the
target node to which the packet is delivered can send a response
packet to the source node.  Of course, baseline BFD doesn't verify
that, because it does not provide for a set of BFD agents to
collectively form one endpoint of a BFD session.

Within that goal, there is an additional requirement that there is no
need to establish separate BFD sessions between the source node and
every node that receives for the anycast address.  But there is an
ambiguity -- is it required that target nodes that do not happen to
receive any of the BFD packets do not need to maintain any state, or
is it that the source node does not need to maintain separate state
for each target node?

Section 3.7

This section talks about fault isolation very abstractly.  Is there a
definition as to what constitutes fault isolation?  (Or is this
definition well-known in the routing world?)

Section 3.8

   With distributed architectures of BFD implementations, this can be
   protected, if a node was to run multiple BFD sessions to targets,
   hosted on different parts of the system (ex: different CPU
   instances).  This can reduce BFD false failures, resulting in more
   stable network.

This is true, but it is not clear what the new requirements are.  I
see in RFC 5880 section 6.3

   Since multiple BFD sessions may be running between two systems, there
   needs to be a mechanism for demultiplexing received BFD packets to
   the proper session.
   ...
   The method of demultiplexing the initial packets (in which Your
   Discriminator is zero) is application dependent, and is thus outside
   the scope of this specification.

Is the question one of how to demultiplex the initial packets from
multiple BFD sessions in the same source device?

Section 3.9

[no complaints]

Section 4

It would help if there were cross-references between the scenarios/use
cases and the requirements.

REQ#1

"MUST start processing for the discriminator" is unclear.  Does this
mean "MUST establish a session", "MUST be able to send a response", or
what?

REQ#2

See comments on section 3.1.

REQ#3

Does this include not needing to exchange interval parameters as well?

REQ#4

I suspect this requirement is only operational in the scenario of
section 3.4, a Segment Routed network.  It might be useful to qualify
the requirement this way, since otherwise "centralized controller" and
"segment" don't have a context.  Or is S-BFD only intended for
situations with a centralized controller?

REQ#5

See comments for section 3.5.

REQ#6

"This requirement does not require BFD session establishment with
every node hosting the anycast address." is not what is intended.
Rather, it should be something like appending "... without
establishing a separate BFD session with every node hosing the anycast
address" to the first session.  As written, the requirement "does not
require session establishment with every node" whereas the intention
is to "require that there not be session establishment with every
node".

REQ#7

See comments for section 3.7.


From nobody Sat Apr  2 13:56:14 2016
Return-Path: <joelja@bogus.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 6AFC112D156; Sat,  2 Apr 2016 13:56:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.91
X-Spam-Level: 
X-Spam-Status: No, score=-6.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, T_RP_MATCHES_RCVD=-0.01] 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 qIxyBuuqziCH; Sat,  2 Apr 2016 13:56:11 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) (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 1047012D0BB; Sat,  2 Apr 2016 13:56:11 -0700 (PDT)
Received: from dhcp-b257.meeting.ietf.org ([IPv6:2001:67c:370:176:51ca:6ceb:88d2:12]) (authenticated bits=0) by nagasaki.bogus.com (8.14.9/8.14.9) with ESMTP id u32Ku7u1065871 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Sat, 2 Apr 2016 20:56:09 GMT (envelope-from joelja@bogus.com)
Subject: Re: RFC 7776 and the team that can be reached for help regarding harassment concerns
To: IETF Chair <chair@ietf.org>, IETF Announcement List <ietf-announce@ietf.org>, 95all@ietf.org
References: <16A28658-0ADD-43BD-832A-2BD37D921653@ietf.org>
From: joel jaeggli <joelja@bogus.com>
Message-ID: <785eec9c-6a03-2a68-de8c-120992f1567c@bogus.com>
Date: Sat, 2 Apr 2016 17:56:06 -0300
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.0
MIME-Version: 1.0
In-Reply-To: <16A28658-0ADD-43BD-832A-2BD37D921653@ietf.org>
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="E8hAb135BihJ7pK9M2oCfd6JN9LaG9D11"
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/gRSHuedHJTqX3-W4zSlzV_K1ZDw>
Cc: IETF <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: Sat, 02 Apr 2016 20:56:12 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--E8hAb135BihJ7pK9M2oCfd6JN9LaG9D11
Content-Type: multipart/mixed; boundary="hwP9hDombesNx0iiDbJa28Nwn2t4klqn8"
From: joel jaeggli <joelja@bogus.com>
To: IETF Chair <chair@ietf.org>,
 IETF Announcement List <ietf-announce@ietf.org>, 95all@ietf.org
Cc: IETF <ietf@ietf.org>
Message-ID: <785eec9c-6a03-2a68-de8c-120992f1567c@bogus.com>
Subject: Re: RFC 7776 and the team that can be reached for help regarding
 harassment concerns
References: <16A28658-0ADD-43BD-832A-2BD37D921653@ietf.org>
In-Reply-To: <16A28658-0ADD-43BD-832A-2BD37D921653@ietf.org>

--hwP9hDombesNx0iiDbJa28Nwn2t4klqn8
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

On 4/1/16 1:52 PM, IETF Chair wrote:
>=20
> In 2013, the IESG set the IETF anti-harassment policy. Last year, we
> concluded the process to write a BCP that defines the anti-harassment
> procedures. That BCP has now been published as RFC 7776. The RFC
> specifies that there shall be a specialist team that can be reached
> for help, advice, and possible actions regarding harassment
> concerns.

Arriving at the point was not easy task. I would like to believe that
the ietf community and the individuals that make it up will be well
served by it.



--hwP9hDombesNx0iiDbJa28Nwn2t4klqn8--

--E8hAb135BihJ7pK9M2oCfd6JN9LaG9D11
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2
Comment: GPGTools - http://gpgtools.org

iEYEARECAAYFAlcAMeYACgkQ8AA1q7Z/VrLaBQCfVrN+dEDzFL+JDtrKcAue8/1X
jO8An2fZ9rgk0bEEyDeg0udaKxWOwFSx
=YGFy
-----END PGP SIGNATURE-----

--E8hAb135BihJ7pK9M2oCfd6JN9LaG9D11--


From nobody Sat Apr  2 17:59:39 2016
Return-Path: <brian.e.carpenter@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 C64AE12D143 for <ietf@ietfa.amsl.com>; Sat,  2 Apr 2016 17:59:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 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, RCVD_IN_DNSWL_LOW=-0.7, 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 st_6KyN3kVyo for <ietf@ietfa.amsl.com>; Sat,  2 Apr 2016 17:59:36 -0700 (PDT)
Received: from mail-pf0-x234.google.com (mail-pf0-x234.google.com [IPv6:2607:f8b0:400e:c00::234]) (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 4D35612D12F for <ietf@ietf.org>; Sat,  2 Apr 2016 17:59:36 -0700 (PDT)
Received: by mail-pf0-x234.google.com with SMTP id e128so96304815pfe.3 for <ietf@ietf.org>; Sat, 02 Apr 2016 17:59:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=subject:to:references:cc:from:organization:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=5vYaxF3bm7inYQhCH1OWZ4U7UVWRpLNDPHhNuUMIQSs=; b=EQFAHz5bHRuJTuAGoJKh7WtV8M1Au0YtghdPuw1TS2DyEAFfip0LBP9vPOJ6mwqjlq 0Gdgl3NfA16w0GN5rZGnCNGweOKghpfLcJ/ig0ubElmTprNK2WwDyV46WmFkcdhZnCyN xPW1a+cJNDQn25N2V4sX5lAi1sC4WKugZdivX3wvaSNchL/IGxfF0b/eFxZc71NixcTG NJ85pmWqN7dL8TDjP50QJ3X1/YL6R1YGXMcb6XOx2/zzBhZ8x/Z41CW0nOF+L5f5XNkh NZf/o9GO9XD1Xqvcwr0Ht/gwuB7VgycbSyBqq8jL86Vm4b89Sf54rv3arwfRNOmjIEzz BeiQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:cc:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=5vYaxF3bm7inYQhCH1OWZ4U7UVWRpLNDPHhNuUMIQSs=; b=UTk9wYCwp27sCe0v3KYINcQLrkbf9ejZQNqo6qF8Fk6HmzUYXbuY61IgsQfyuwaL4h P/kOAmiRsNimiXqoVhupLiai9KXpSbwWamNtBH+RR7eABBf+XllZwjAgZ0bfavRZJCQm 0XEAwkyDq2SmfItQ47DzPnXpku6hD8kUCFMCcXyMdlKNcBwIr91Zlk6XTaH3EZ6sUQEe D2ezEk4LDYAvtVPn7wEA1Va5u+xD1HfHBwN+zNHDo5kbmV1rMvM16LddlaQbHLSR45Wp hxyzZnwz1IeAQ+FmVLkA7lhz6A3N1nTx0WukqX1Saa8wsUAC8Jw+DzF7h9MxVKuDmBTx X7KA==
X-Gm-Message-State: AD7BkJJXrNFAjp4Pdb1v8d/E5c/H7MpVIzZwXNMjPgoV900F2j6LWDlP2afKVJo14L5cAg==
X-Received: by 10.98.32.23 with SMTP id g23mr9539197pfg.74.1459645175892; Sat, 02 Apr 2016 17:59:35 -0700 (PDT)
Received: from ?IPv6:2406:e007:7971:1:28cc:dc4c:9703:6781? ([2406:e007:7971:1:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id wy7sm31614446pab.5.2016.04.02.17.59.31 (version=TLSv1/SSLv3 cipher=OTHER); Sat, 02 Apr 2016 17:59:34 -0700 (PDT)
Subject: Re: Last Call on draft-bradner-rfc3979bis-08.txt ("Intellectual Property Rights in IETF Technology")
To: Alissa Cooper <alissa@cooperw.in>, Jari Arkko <jari.arkko@piuha.net>
References: <0000431F-F977-4A24-BA4D-064F740977A0@piuha.net> <7A6961E0-CCA6-4D1D-878A-176004AE2BAE@cooperw.in>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <57006AF2.7020400@gmail.com>
Date: Sun, 3 Apr 2016 12:59:30 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.7.0
MIME-Version: 1.0
In-Reply-To: <7A6961E0-CCA6-4D1D-878A-176004AE2BAE@cooperw.in>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/iH1y_2kVgdCdR966lUED7qA3q0w>
Cc: IETF <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: Sun, 03 Apr 2016 00:59:38 -0000

Alissa,
On 01/04/2016 11:38, Alissa Cooper wrote:
...
> 1) I agree with other commenters' concerns about the definition of "participating" with respect to WG chairs and ADs. In particular in the context of section 6, this seems like it could limit the pool of people who can stand for AD roles, because you're not allowed to participate in cases where you won't be able to disclose, but you have no idea a priori what WGs will get chartered in your area and what work items they might take up.

I don't see what's new about this - it's always been an awkward point. I worked for
a major patent-generating company while I was in the IESG ten years ago, and I had
to pay attention to this. I'm not saying it isn't a problem, but I don't see that
tightening up the language really makes the problem any worse. (However, I still
don't see any need to state the obvious, i.e. that WG Chairs and ADs are
participants, unless they recuse themselves on a particular matter.)

    Brian


From nobody Sat Apr  2 19:57:14 2016
Return-Path: <joelja@bogus.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 214E712D0BE for <ietf@ietfa.amsl.com>; Sat,  2 Apr 2016 19:57:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.91
X-Spam-Level: 
X-Spam-Status: No, score=-6.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, T_RP_MATCHES_RCVD=-0.01] 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 HHbPNj7htQmA for <ietf@ietfa.amsl.com>; Sat,  2 Apr 2016 19:57:09 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) (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 31C8412D1AA for <ietf@ietf.org>; Sat,  2 Apr 2016 19:57:09 -0700 (PDT)
Received: from mb-2.local (201-250-63-56.speedy.com.ar [201.250.63.56] (may be forged)) (authenticated bits=0) by nagasaki.bogus.com (8.14.9/8.14.9) with ESMTP id u332uvf6068032 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Sun, 3 Apr 2016 02:57:01 GMT (envelope-from joelja@bogus.com)
Subject: Re: Last Call on draft-bradner-rfc3979bis-08.txt ("Intellectual Property Rights in IETF Technology")
To: Scott Bradner <sob@sobco.com>, Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
References: <0000431F-F977-4A24-BA4D-064F740977A0@piuha.net> <56FBF599.9080605@ericsson.com> <ACC702C9-C33F-4D38-B47A-8BC293D24621@sobco.com>
From: joel jaeggli <joelja@bogus.com>
Message-ID: <456159d9-6a8e-4e8b-64fa-e37d71a7eb0f@bogus.com>
Date: Sat, 2 Apr 2016 23:56:51 -0300
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.0
MIME-Version: 1.0
In-Reply-To: <ACC702C9-C33F-4D38-B47A-8BC293D24621@sobco.com>
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="MVKtDfJC6bKoxFaictgkBMc33qc1c1GIk"
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/i-VH-6Y1ykbr9EBbyCz3MyX5tfQ>
Cc: IETF <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: Sun, 03 Apr 2016 02:57:12 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--MVKtDfJC6bKoxFaictgkBMc33qc1c1GIk
Content-Type: multipart/mixed; boundary="OdldmeR8q474BAr08bPTxwp2Pt2Ol43ws"
From: joel jaeggli <joelja@bogus.com>
To: Scott Bradner <sob@sobco.com>,
 Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
Cc: IETF <ietf@ietf.org>
Message-ID: <456159d9-6a8e-4e8b-64fa-e37d71a7eb0f@bogus.com>
Subject: Re: Last Call on draft-bradner-rfc3979bis-08.txt ("Intellectual
 Property Rights in IETF Technology")
References: <0000431F-F977-4A24-BA4D-064F740977A0@piuha.net>
 <56FBF599.9080605@ericsson.com>
 <ACC702C9-C33F-4D38-B47A-8BC293D24621@sobco.com>
In-Reply-To: <ACC702C9-C33F-4D38-B47A-8BC293D24621@sobco.com>

--OdldmeR8q474BAr08bPTxwp2Pt2Ol43ws
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

On 3/30/16 1:28 PM, Scott Bradner wrote:
> this was the (strong?) consensus of the IPR BOF

It's reasonable to characterize the AD as involved in the working groups
in their area.

I don't really find fault in the characterization of old 6.1.2 current
5.1.2.

If you're aware of IPR meeting the conditions of 5.1.2 with respect to
work in your areas of engagement you disclose it. If you aren't you
don't. if you become aware you disclose it even if it's inconvenient or
later then desirable.

> Scott
>=20
>> On Mar 30, 2016, at 11:49 AM, Gonzalo Camarillo <Gonzalo.Camarillo@eri=
csson.com> wrote:
>>
>> Hi,
>>
>> Section 1 (Definitions), subsection k says the following:
>>
>>>      Without limiting the generality of the
>>>      foregoing, acting as a working group chair or Area Director
>>>      constitutes "Participating" in all activities of the relevant
>>>      working group or area.
>>
>> The AD of a large area may not get to read all individual I-Ds or all
>> email messages sent in all the WGs of the area. We may want to define
>> this a bit more explicitly.
>>
>> Cheers,
>>
>> Gonzalo
>>
>> On 22/03/2016 2:17 PM, Jari Arkko wrote:
>>>
>>> All,
>>>
>>> RFC 3979 was published in 2005. Since then we=92ve gathered a lot of =
experience, and we=92d like to update the RFC with that experience. This =
isn=92t a revolution of the IETF IPR approach, it is mostly about clarifi=
cation, better documentation, and recognising some other new RFCs and cha=
nges. But the document itself has changed quite a lot and structured diff=
erently than RFC 3979 was.
>>>
>>> Some of the main issues (such as how to define participation) were di=
scussed in the IETF-87 meeting, but there are also a number of other chan=
ges in this document. Please give this document a careful read, and let u=
s know your feedback.
>>>
>>> I am starting a last call on this document today, but gave a longer l=
ast call period to make sure everyone has enough time to comment after IE=
TF-95 as well. And thanks for the comments that some of you have already =
sent after the document was published; we=92ve observed them and will mak=
e them part of the feedback from the Last Call.
>>>
>>> The document is available here:
>>>
>>>   https://datatracker.ietf.org/doc/draft-bradner-rfc3979bis/
>>>   https://tools.ietf.org/html/draft-bradner-rfc3979bis-08
>>>
>>> Jari Arkko (as the responsible AD for this document)
>>>
>>
>=20
>=20



--OdldmeR8q474BAr08bPTxwp2Pt2Ol43ws--

--MVKtDfJC6bKoxFaictgkBMc33qc1c1GIk
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2
Comment: GPGTools - http://gpgtools.org

iEYEARECAAYFAlcAhnMACgkQ8AA1q7Z/VrKG1wCeJj1yYunndOC7GlBEUySnVWcb
k8EAn20k1Eh8Jwlkp50TnsnuffD/dVPr
=48qc
-----END PGP SIGNATURE-----

--MVKtDfJC6bKoxFaictgkBMc33qc1c1GIk--


From nobody Sun Apr  3 05:58:14 2016
Return-Path: <jhildebr@cisco.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 125AC12D1A3; Sun,  3 Apr 2016 05:58:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.531
X-Spam-Level: 
X-Spam-Status: No, score=-14.531 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 HLvzgGTVUVpU; Sun,  3 Apr 2016 05:58:11 -0700 (PDT)
Received: from alln-iport-4.cisco.com (alln-iport-4.cisco.com [173.37.142.91]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9C96F12D535; Sun,  3 Apr 2016 05:58:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=6254; q=dns/txt; s=iport; t=1459688290; x=1460897890; h=from:to:cc:subject:date:message-id:content-id: content-transfer-encoding:mime-version; bh=V+ZZBkSJSLFdi3/jxLVzGEVarplcCLpMwcQtsRAaQGY=; b=OAUKop5S8k4QcUk8tEgOEfw2TeAtMe2Oer/K+UNiDgaR1cH/IZbvNQBy E/EJUL+4CLjH+6rnoGPuE5tHJtxpOeaOtK4Dh5AknYaw4Ix9bNK4TctOs Oaf6cTz3N+h7RdhmUMZzIlOGtAijUY2UDEyUuGsJGX2+d5qqR6yIu5rWb U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AJAgBkEgFX/4sNJK1dgzdTfQa7GwENg?= =?us-ascii?q?XIXCoUiSh6BBTgUAQEBAQEBAWUnhEMBBAEBASARMRQSARoIAggeAgQlCxUCEAQ?= =?us-ascii?q?BDQUUCIgLDqlYkQoBAQEBAQEBAQEBAQEBAQEBAQEBAQERBHyFJIF1glWHPyuCK?= =?us-ascii?q?wWNTYo0AYEqhEiCcoUjgWiETYhajxkBHgEBQoNnbIcMfgEBAQ?=
X-IronPort-AV: E=Sophos;i="5.24,436,1454976000"; d="scan'208";a="256017884"
Received: from alln-core-6.cisco.com ([173.36.13.139]) by alln-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 03 Apr 2016 12:58:09 +0000
Received: from XCH-RTP-005.cisco.com (xch-rtp-005.cisco.com [64.101.220.145]) by alln-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id u33Cw9xW006009 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Sun, 3 Apr 2016 12:58:09 GMT
Received: from xch-rtp-001.cisco.com (64.101.220.141) by XCH-RTP-005.cisco.com (64.101.220.145) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Sun, 3 Apr 2016 08:58:08 -0400
Received: from xch-rtp-001.cisco.com ([64.101.220.141]) by XCH-RTP-001.cisco.com ([64.101.220.141]) with mapi id 15.00.1104.009; Sun, 3 Apr 2016 08:58:08 -0400
From: "Joe Hildebrand (jhildebr)" <jhildebr@cisco.com>
To: "architecture-discuss@ietf.org" <architecture-discuss@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Subject: Remote participation in IAB workshops
Thread-Topic: Remote participation in IAB workshops
Thread-Index: AQHRjah4kcLD23/qI0CAnNsEkCbc7w==
Date: Sun, 3 Apr 2016 12:58:08 +0000
Message-ID: <F653319B-B971-4D30-9E8F-E9E556BCF7DD@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/0.0.0.160212
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.24.8.48]
Content-Type: text/plain; charset="utf-8"
Content-ID: <6C69854DE6F0614CA8649B19A5C8A932@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/wxWtUFjhxbDIoirjRdPBHRq_zVw>
Cc: IAB <iab@iab.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: Sun, 03 Apr 2016 12:58:13 -0000

VGhlIElBQiBoYXMgaGVhcmQgZnJvbSB0aGUgY29tbXVuaXR5IGEgZGVzaXJlIGZvciBtb3JlIG9w
ZW5uZXNzIGluIG91ciB3b3Jrc2hvcHMsIGluY2x1ZGluZyByZW1vdGUgYWNjZXNzLiAgQWZ0ZXIg
YSBnb29kIGFtb3VudCBvZiBkaXNjdXNzaW9uLCB3ZSBjb250aW51ZSB0byBiZWxpZXZlIHRoYXQg
Zm9yIElBQiB3b3Jrc2hvcHMsIHRoZXJlIGFyZSBzb21ldGltZXMgZ29vZCByZWFzb25zIG5vdCB0
byBkZWZhdWx0IHRvIHRoZSBJRVRGJ3MgdXN1YWwgc3RhbmNlIG9mIGZ1bGwgcmVhbHRpbWUgcmVt
b3RlIGFjY2VzcyBmb3IgYW55b25lIHRoYXQgd2FudHMgdG8gcGFydGljaXBhdGUuICBPdXIgcHJh
Y3RpY2Ugd2lsbCBjb250aW51ZSB0byBiZSB0byBhbGxvdyB0aGUgUHJvZ3JhbSBDb21taXR0ZWUg
KFBDKSBmb3IgYSBnaXZlbiB3b3Jrc2hvcCB0byBkZWNpZGUgaG93IGJlc3QgdG8gaW5jbHVkZSB0
aGUgY29tbXVuaXR5IGluIG9yZGVyIHRvIGFjY29tcGxpc2ggdGhlIHRlY2huaWNhbCBnb2FscyBv
ZiBhIGdpdmVuIHdvcmtzaG9wLg0KDQpXZSBhcmUgdXBkYXRpbmcgb3VyIGludGVybmFsIGRvY3Vt
ZW50YXRpb24gb24gaG93IHRvIHJ1biBhIHdvcmtzaG9wIHdpdGggdHJhZGVvZmZzIGZvciB0aGUg
UEMgdG8gY29uc2lkZXIsIHBhcnRpY3VsYXJseSBhcm91bmQgaG93IG9wZW4gdG8gbWFrZSB0aGUg
ZGlzY3Vzc2lvbi4gIEhlcmUgYXJlIHNvbWUgb2YgdGhvc2UgY29uc2lkZXJhdGlvbnMsIGZvciBj
b21tdW5pdHkgY29tbWVudDoNCg0KS2VlcGluZyBpbiBtaW5kIHRoYXQgYW4gSUFCIHdvcmtzaG9w
IGlzIG9mdGVuIGhlbGQgYXQgdGhlIHZlcnkgYmVnaW5uaW5nIG9mIG91ciBjb21tdW5pdHkncyBk
aXNjdXNzaW9uIG9mIGEgZ2l2ZW4gdG9waWMsIGl0IGlzIHNvbWV0aW1lcyBpbXBvcnRhbnQgZm9y
IHRoZSBkaXNjdXNzaW9uIHRvIGJlIGFzIHVuZW5jdW1iZXJlZCBhcyBwb3NzaWJsZSBieSBBdWRp
by9WaXN1YWwgb3ZlcmhlYWQgKFN0YW5kIFRoZXJlISBTcGVhayBpbnRvIHRoZSBtaWMhIFNheSB5
b3VyIG5hbWUhKSBpbiBvcmRlciB0byBnZXQgdG8gdGhlIGhlYXJ0IG9mIGFuDQphcmNoaXRlY3R1
cmFsIGRpc2N1c3Npb24gaW4gdGhlIHNob3J0IHRpbWUgd2UgaGF2ZSBmb3IgdGhlIHdvcmtzaG9w
LiAgQWxsb3dpbmcgZnVsbCByZW1vdGUgcGFydGljaXBhdGlvbiAoSmFiYmVyIHJlbGF5ISBNdXRl
IHlvdXIgbGluZSEpIHdvdWxkIGNhdXNlIGV2ZW4gbW9yZSBpbXBhY3QgdG8gdGhlIGluLXJvb20g
ZGlzY3Vzc2lvbiwgd2l0aCB0b2RheSdzIHR5cGljYWwgdGVjaG5vbG9neS4NCg0KRm9yIHNvbWUg
d29ya3Nob3BzLCBhdCBsZWFzdCBhIHBvcnRpb24gb2YgdGhlIGRpc2N1c3Npb24gaXMgaGVsZCB1
c2luZyB0aGUgQ2hhdGhhbSBIb3VzZSBSdWxlIChodHRwczovL3d3dy5jaGF0aGFtaG91c2Uub3Jn
L2Fib3V0L2NoYXRoYW0taG91c2UtcnVsZSksIGluIGFuIGF0dGVtcHQgdG8gZWxpY2l0IGlucHV0
IHRoYXQgcGFydGljaXBhbnRzIHdvdWxkIG5vdCBiZSBhYmxlIHRvIG9mZmVyIGluIGEgc2Vzc2lv
biB3aGVyZSBhbGwgaW5wdXQgaXMgYXR0cmlidXRlZC4gIEluIHRob3NlIGNhc2VzLCByZW1vdGUg
cGFydGljaXBhbnRzIHdvdWxkIG5lZWQgdG8gYWNjZXB0IHRoZSBSdWxlIGV4cGxpY2l0bHksIG9y
IGJlIGRyb3BwZWQgZm9yIHRoYXQgcG9ydGlvbiBvZiB0aGUgY29udmVyc2F0aW9uLiAgV2l0aCBy
ZW1vdGUgcGFydGljaXBhbnRzLCBDaGF0aGFtIEhvdXNlIFJ1bGUgY29udHJpYnV0aW9ucyBjYW4g
YmUgbW9yZSBkaWZmaWN1bHQgdG8gZWxpY2l0IGJlY2F1c2UgaXQgaXMgbW9yZSBkaWZmaWN1bHQg
dG8gYnVpbGQgdGhlIHBlcnNvbmFsIHRydXN0IHJlcXVpcmVkLiAgVGhlIHVzZSBvZiB0aGUgQ2hh
dGhhbSBIb3VzZSBSdWxlICpoYXMqIGJlZW4gdXNlZnVsIGluIHNldmVyYWwgcHJldmlvdXMgd29y
a3Nob3BzLg0KDQpGb3IgbWFueSB3b3Jrc2hvcHMsIGEgdm9pY2Ugb3IgdmlkZW8gcmVjb3JkaW5n
IGlzIG1hZGUgdG8gYXNzaXN0IGluIGxhdGVyIHByZXBhcmF0aW9uIG9mIG5vdGVzLiAgUmVjb3Jk
aW5nIGRldmljZXMgYXJlIHN0b3BwZWQgZHVyaW5nIGFueSBwb3J0aW9uIG9mIHRoZSBkaXNjdXNz
aW9uIHRoZSBoYXBwZW5zIHVuZGVyIHRoZSBDaGF0aGFtIEhvdXNlIFJ1bGUsIGluIG9yZGVyIHRv
IGhlbHAgc2hpZWxkIHRoZSBhbm9ueW1pdHkgb2YgdGhlIHBhcnRpY2lwYW50cyBpbiB0aG9zZSBk
aXNjdXNzaW9ucy4NCg0KRm9yIHNvbWUgd29ya3Nob3BzLCBpbmRpdmlkdWFsIGludml0ZWQgcmVt
b3RlIGNvbnRyaWJ1dG9ycyBtaWdodCBiZSBhY2NvbW1vZGF0ZWQuICBUaGlzIGFwcHJvYWNoIGNh
biBhdm9pZCAqc29tZSogb2YgdGhlIHByZXZpb3VzIGlzc3VlcyBieSB0cmFpbmluZyB0aGUgcmVt
b3RlIHBhcnRpY2lwYW50IGFoZWFkIG9mIHRoZSBtZWV0aW5nIChjaGVjayBoYXJkd2FyZSwgZW5z
dXJlIHRoZXkgYXJlIGFsd2F5cyBvbiBtdXRlIHVubGVzcyBzcGVha2luZywgZXRjKSwgYW5kIGVu
c3VyaW5nIHRoYXQgdGhlIHJlbW90ZSBwYXJ0aWNpcGFudCBoYXMgZXhwbGljaXRseSBhZ3JlZWQg
dG8gd2hhdGV2ZXIgb3BlcmF0aW5nIHJ1bGVzIGFyZSBjaG9zZW4gYnkgdGhhdCB3b3Jrc2hvcC4g
IFN1Y2ggaW52aXRhdGlvbnMgYXJlIGF0IHRoZSBkaXNjcmV0aW9uIG9mIHRoZSBQQywgYW5kIHdp
bGwgYmUgYmFsYW5jZWQgYmV0d2VlbiB0aGUgdXNlZnVsbmVzcyBvZiB0aGUgcmVtb3RlIGNvbnRy
aWJ1dGlvbiBhbmQgdGhlIGNvc3QvY29tcGxleGl0eS9kaXNjdXNzaW9uIG92ZXJoZWFkIGNyZWF0
ZWQuDQoNCkZvciBhbGwgd29ya3Nob3BzLCB0aGUgUEMgd2lsbCBzdHJpdmUgdG8gbWFrZSByYXcg
bWludXRlcyBhdmFpbGFibGUgYXMgcXVpY2tseSBhcyBwb3NzaWJsZSBhZnRlciB0aGUgd29ya3No
b3AuICBGb3Igc2V2ZXJhbCBvZiB0aGUgb2YgdGhlIHJlY2VudCB3b3Jrc2hvcHMsIHRyYW5zY3Jp
cHRzIGhhdmUgYmVlbiBhdmFpbGFibGUgd2l0aGluIGEgd2VlayBvciBzby4gIFRoZSBJQUItc3Ry
ZWFtIFJGQyB3aXRoIHRoZSBmdWxsIHdvcmtzaG9wIHJlcG9ydCBvZiBjb3Vyc2UgdGFrZXMgbG9u
Z2VyIHRvIHByZXBhcmUsIGFuYWx5emUsIGFuZCBhcHByb3ZlLg0KDQpUaGUgUEMgd2lsbCB0aGVy
ZWZvcmUgbmVlZCB0byBkZWNpZGUgdGhlIHZhbHVlIG9mIGdldHRpbmcgdGhlIGxhcmdlciBjb21t
dW5pdHkgaW5mb3JtYXRpb24gaW4gbmVhciByZWFsIHRpbWUgdnMgd2FpdGluZyBhIHdlZWsgb3Ig
c28gZm9yIHRyYW5zY3JpcHRzLiAgSWYgdGhleSBkZWNpZGUgbW9yZSByZW1vdGUgcGFydGljaXBh
dGlvbiBpcyBkZXNpcmVkLCB0aGV5IHdpbGwgaGF2ZSB0byBidWRnZXQgYXBwcm9wcmlhdGVseSBm
b3IgZXF1aXBtZW50LCB3ZWIgbWVldGluZyBzZXJ2aWNlcywgdGVjaG5pY2lhbnMsIGV0Yy4NCg0K
SW4gdGhlIGNhc2Ugb2YgdGhlIE1hUk5FVyB3b3Jrc2hvcCwgdGhlIFBDIGRlY2lkZWQgdGhhdCB3
ZSB3YW50ZWQgYSByb2J1c3QgaW4tcGVyc29uIGRpc2N1c3Npb24gd2l0aCBhIHBvcnRpb24gYmVp
bmcgdW5kZXIgdGhlIENoYXRoYW0gSG91c2UgUnVsZS4gIFdlIGZ1cnRoZXIgY29tbWl0dGVkIHRv
IGdldHRpbmcgbWludXRlcyBwdWJsaXNoZWQgYXMgcXVpY2tseSBhcyBwb3NzaWJsZSAoaGVyZTog
aHR0cHM6Ly9naXRodWIuY29tL01hUk5FVy9NaW51dGVzKS4gIEFzIHN1Y2gsIHdlIGRlY2lkZWQg
dGhhdCByZW1vdGUgcGFydGljaXBhdGlvbiB3YXMgbm90IGEgcHJpb3JpdHkgZm9yIHRoaXMgd29y
a3Nob3AuDQoNCkluIHRoZSBjYXNlIG9mIHRoZSBJT1RTSSB3b3Jrc2hvcCwgdGhlIHB1cnBvc2Ug
d2FzIHRvIGdldCBwYXJ0aWNpcGFudHMgZnJvbSBtYW55IFNET3MgYW5kIG9yZ2FuaXphdGlvbnMg
d2l0aCBkaWZmZXJlbnQgSVBSIHJ1bGVzLiAgKEluZGVlZCwgYXMgZGlzY3Vzc2VkIGF0IHRoZSBJ
RVRGIDkyIHRlY2ggcGxlbmFyeSwgdGhlIElvVCBzZW1hbnRpYyBpbnRlcm9wZXJhYmlsaXR5IHBy
b2JsZW0gaXMgbGFyZ2VseSBvdXRzaWRlIHRoZSBzY29wZSBvZiB0aGUgSUVURi4pICBBcyBzdWNo
LCB0aGUgUEMgZGVjaWRlZCB0aGF0IHRoZSBJRVRGIE5vdGUgV2VsbCB3b3VsZCBiZSBpbmFwcHJv
cHJpYXRlLCBhbmQgdGhhdCBpdCB3b3VsZCBiZSB1cCB0byB0aGUgcGFydGljaXBhbnRzIHdoZXRo
ZXIgQ2hhdGhhbSBIb3VzZSBydWxlcyB3b3VsZCBhcHBseS4gIFRoZXJlZm9yZSwgdGhlIFBDIGRl
Y2lkZWQgdGhhdCByZW1vdGUgcGFydGljaXBhdGlvbiB3YXMgbm90IGEgcHJpb3JpdHkgZm9yIHRo
aXMgd29ya3Nob3AuDQoNCg0KSWYgeW91IHdvdWxkIGxpa2UgdG8gZGlzY3VzcyB0aGlzIGZ1cnRo
ZXIgaW4gcHVibGljLCBwbGVhc2UgdXNlIGFyY2hpdGVjdHVyZS1kaXNjdXNzQGlldGYub3JnIChz
dWJzY3JpYmUgYXQgaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9hcmNoaXRl
Y3R1cmUtZGlzY3VzcykuICBDb25maWRlbnRpYWwgbm90ZXMgY2FuIGJlIHNlbnQgdG8gdGhlIElB
QiBhdCBpYWJAaWFiLm9yZy4NCg0KDQotLSANCkpvZSBIaWxkZWJyYW5kDQpPbiBiZWhhbGYgb2Yg
dGhlIElBQg0K


From nobody Sun Apr  3 06:19:04 2016
Return-Path: <abdussalambaryun@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 AF4FB12D55B; Sun,  3 Apr 2016 06:19:01 -0700 (PDT)
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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 UMgFUC1HIyvu; Sun,  3 Apr 2016 06:18:58 -0700 (PDT)
Received: from mail-qg0-x232.google.com (mail-qg0-x232.google.com [IPv6:2607:f8b0:400d:c04::232]) (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 52BD112D0BA; Sun,  3 Apr 2016 06:18:58 -0700 (PDT)
Received: by mail-qg0-x232.google.com with SMTP id f52so34094512qga.3; Sun, 03 Apr 2016 06:18:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=FkfW/cNL6xZUOOKupjKwv9VnooIzsuTlDUBGB+TiTkU=; b=Wrnyc5W1nrSicck8VvCWjM/ZKmACwwrq2ZikcFGT8rHSeIETPXFpuF0qbtt0mDQpn0 NS85UkfOBv5JEdyRPZmBsGSssOCJhNpMmOCFSfXfemziX2Hti6UbVnBs10ZcQIHtAAtp rcMHMPNN8+OJvCKqZguLbMeTOYITOqCsJxwh6lPbyvihotRjR/OF1DesNUunH9S6mIf9 kRI00VYwqpoKQo/d0tV6ZYVGEME3cHB7bV20XM529JPZkhEjttfRZ/daZTkyH5gzASJC Dz/xpu1qTFN9zkSnAVX7K+FPksg5pm0otUi98OH7eHDdpUdnTKfIcyaGfMyJOsFpDbzj qgRg==
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:date :message-id:subject:from:to:cc; bh=FkfW/cNL6xZUOOKupjKwv9VnooIzsuTlDUBGB+TiTkU=; b=PxjUJLn5mdTYnnBQc1yMPks2J019pv3Y7ofteITqJ60w1tvOFTqKIw8mdF6IV1ZkyI MPCacdaragh5Q/GKf3q8vbYaFONR3r4UvuNmbZ0ipVoDGUdRN7ncmHz5fVFUYjHWY3nN DUXUyNxUZQydlU93jLZwnQg0FeZONUDCLop2dUMJKqA0bWtDAc7TBm9FKpzpQ5atbXck Tfjwx/DM7JdTmcVbStor+lVdZwEG2P3xzzLYgcoXzX17TLXfI40BIVx0Zk28ZH27D1Gs rHJYYfum76QZhGyB179TE3B5yApbF8oHBc4V7grRdHvJHi+pUv+sB5BnQXYi1NOhmlLk Z7Gw==
X-Gm-Message-State: AD7BkJLFLqhB/85qT05MamWXkEsw/dnP1BOwKg9W8xrybeyVAoMpUUtaQLjbH3pDpJm/dQV1wE9sjGvWNfD2zQ==
MIME-Version: 1.0
X-Received: by 10.140.169.4 with SMTP id p4mr36605517qhp.71.1459689537477; Sun, 03 Apr 2016 06:18:57 -0700 (PDT)
Received: by 10.140.43.131 with HTTP; Sun, 3 Apr 2016 06:18:57 -0700 (PDT)
In-Reply-To: <56F98CD1.10706@gmail.com>
References: <20160320223116.8946.76840.idtracker@ietfa.amsl.com> <949EF20990823C4C85C18D59AA11AD8BADEAFFC7@FR712WXCHMBA11.zeu.alcatel-lucent.com> <CA+9kkMCsT43ZCSdq8gdKXu1k4pJgbf0ab5tE=dDiFfrTT2gtkA@mail.gmail.com> <949EF20990823C4C85C18D59AA11AD8BADEB0D16@FR712WXCHMBA11.zeu.alcatel-lucent.com> <56F79D05.8070004@alvestrand.no> <326E6502-28E5-4D09-BB99-4A5D80625EB0@stewe.org> <56F88E18.2060506@it.aoyama.ac.jp> <20160328104731.GO88304@verdi> <CALaySJ+hYMMsKE7Ws-NJbyqH55E-mQM-duTEcJGc0TWvTP88Ew@mail.gmail.com> <20160328132859.GP88304@verdi> <28975138-9EA1-4A9F-A6C0-BC1416B8EA44@sobco.com> <CALaySJJkNj2jfm0gJpuDzq8oFDjTNn-uQ5MHdmEOLwTiFZUyQQ@mail.gmail.com> <8975F15F-5C4C-4D02-98CD-BF4FDF104D35@sobco.com> <56F98CD1.10706@gmail.com>
Date: Sun, 3 Apr 2016 15:18:57 +0200
Message-ID: <CADnDZ88mpAcx8tQ+btwxs-Rdn_=6RMQ2y3_bDm8MPx+4xxk-Yw@mail.gmail.com>
Subject: Re: Fuzzy words [was Uppercase question for RFC2119 words]
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Content-Type: multipart/alternative; boundary=001a113b4cc45d2419052f9474e2
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/CliIYoYoDLuKmkfZyYEPb2PVk0k>
Cc: IETF discussion list <ietf@ietf.org>, "Heather Flanagan \(RFC Series Editor\)" <rse@rfc-editor.org>, "rtcweb@ietf.org" <rtcweb@ietf.org>, IESG <iesg@ietf.org>, Barry Leiba <barryleiba@computer.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: Sun, 03 Apr 2016 13:19:01 -0000

--001a113b4cc45d2419052f9474e2
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

The confusion if occured between English authors may mean that we can get
confusions among non-English authors as well, I recommend if a guidance
draft is written we will need many non-Enlish native speekers involved.


AB

On Mon, Mar 28, 2016 at 9:58 PM, Brian E Carpenter <
brian.e.carpenter@gmail.com> wrote:

> There are times when I think RFC2119 was a really bad idea, despite it
> having
> become probably the most frequently cited RFC (inside and outside the
> IETF).
> It seems to create as much confusion as it avoids.
>
> There are four words whose RFC2119 meaning is different from the dictiona=
ry
> meaning: should, recommended, may and optional. Having special typography
> for them is useful, because it signals the RFC2119 meanings. But if a spe=
c
> uses, for example, a mixture of SHOULD and should, who knows what the
> authors
> intended? To that extent, the proposed clarification is helpful.
>
> The other words (must, shall, required, not) mean what they always mean.
> The only argument for upper-casing them is aesthetic symmetry. If a spec
> uses alternatives like mandatory, necessary or forbidden, they are just a=
s
> powerful.
>
> So
> > these definitions are only meaningful if the words are capitalized
> can be applied to should, recommended, may and optional if we want,
> but strictly doesn't apply to must, shall, required, not, mandatory,
> necessary, forbidden, need, or any other such words.
>
> Where we can get into real trouble is if a spec contains should,
> recommended,
> may and optional *plus* other non-categorical (fuzzy) words like ought,
> encourage, suggest, can, might, allowed, permit (and I did not pull those
> words out of the air, but out of draft-hansen-nonkeywords-non2119). What =
do
> they mean? It can be very unclear. If a node receives a message containin=
g
> an element covered in the spec by "allowed" instead of "OPTIONAL", is the
> receiver supposed to interoperate or to reject the message?
>
> If we are issuing guidance, it should probably include a specific warning
> to use any such fuzzy words with extreme care.
>
>    Brian
> On 29/03/2016 03:13, Scott O. Bradner wrote:
> > one minor tweak
> >
> >> On Mar 28, 2016, at 10:09 AM, Barry Leiba <barryleiba@computer.org>
> wrote:
> >>
> >>> The wishy washy descriptive rather than proscriptive language in the
> abstract was because I,
> >>> the IESG and the community were not of one mind to say that the use o=
f
> such capitalized
> >>> terms should be mandatory - quite a few people felt that the english
> language was at
> >>> least good enough to convey  the writer=E2=80=99s intent without havi=
ng to
> aggrandize specific words.
> >>> Thus the abstract basically was saying: if you want to use capitalize=
d
> words here is a standard
> >>> way to say what they mean
> >>
> >> Ah.  Then perhaps the clarification needs to go a little further and
> >> make this clear:
> >> - We're defining specific terms that specifications can use.
> >> - These terms are always capitalized when these definitions are used.
> >
> > these definitions are only meaningful if the words are capitalized
> >
> >> - You don't have to use them.  If you do, they're capitalized and
> >> their meanings are as specified here.
> >> - There are similar-looking English words that are not capitalized,
> >> and they have their normal English meanings; this document has nothing
> >> to do with them.
> >>
> >> ...and I'd like to add one more, because so many people think that
> >> text isn't normative unless it has 2119 key words in all caps in it:
> >>
> >> - Normative text doesn't require the use of these key words.  They're
> >> used for clarity and consistency when you want that, but lots of
> >> normative text doesn't need to use them, and doesn't use them.
> >>
> >> Barry
> >
> >
>
>

--001a113b4cc45d2419052f9474e2
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>The confusion if occured between English authors may =
mean that we can get confusions among non-English authors as well, I recomm=
end if a guidance draft is written we will need many non-Enlish native spee=
kers involved. <br><br><br></div><div>AB</div></div><div class=3D"gmail_ext=
ra"><br><div class=3D"gmail_quote">On Mon, Mar 28, 2016 at 9:58 PM, Brian E=
 Carpenter <span dir=3D"ltr">&lt;<a href=3D"mailto:brian.e.carpenter@gmail.=
com" target=3D"_blank">brian.e.carpenter@gmail.com</a>&gt;</span> wrote:<br=
><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1=
px #ccc solid;padding-left:1ex">There are times when I think RFC2119 was a =
really bad idea, despite it having<br>
become probably the most frequently cited RFC (inside and outside the IETF)=
.<br>
It seems to create as much confusion as it avoids.<br>
<br>
There are four words whose RFC2119 meaning is different from the dictionary=
<br>
meaning: should, recommended, may and optional. Having special typography<b=
r>
for them is useful, because it signals the RFC2119 meanings. But if a spec<=
br>
uses, for example, a mixture of SHOULD and should, who knows what the autho=
rs<br>
intended? To that extent, the proposed clarification is helpful.<br>
<br>
The other words (must, shall, required, not) mean what they always mean.<br=
>
The only argument for upper-casing them is aesthetic symmetry. If a spec<br=
>
uses alternatives like mandatory, necessary or forbidden, they are just as<=
br>
powerful.<br>
<br>
So<br>
&gt; these definitions are only meaningful if the words are capitalized<br>
can be applied to should, recommended, may and optional if we want,<br>
but strictly doesn&#39;t apply to must, shall, required, not, mandatory,<br=
>
necessary, forbidden, need, or any other such words.<br>
<br>
Where we can get into real trouble is if a spec contains should, recommende=
d,<br>
may and optional *plus* other non-categorical (fuzzy) words like ought,<br>
encourage, suggest, can, might, allowed, permit (and I did not pull those<b=
r>
words out of the air, but out of draft-hansen-nonkeywords-non2119). What do=
<br>
they mean? It can be very unclear. If a node receives a message containing<=
br>
an element covered in the spec by &quot;allowed&quot; instead of &quot;OPTI=
ONAL&quot;, is the<br>
receiver supposed to interoperate or to reject the message?<br>
<br>
If we are issuing guidance, it should probably include a specific warning<b=
r>
to use any such fuzzy words with extreme care.<br>
<br>
=C2=A0 =C2=A0Brian<br>
On 29/03/2016 03:13, Scott O. Bradner wrote:<br>
&gt; one minor tweak<br>
&gt;<br>
&gt;&gt; On Mar 28, 2016, at 10:09 AM, Barry Leiba &lt;<a href=3D"mailto:ba=
rryleiba@computer.org">barryleiba@computer.org</a>&gt; wrote:<br>
&gt;&gt;<br>
&gt;&gt;&gt; The wishy washy descriptive rather than proscriptive language =
in the abstract was because I,<br>
&gt;&gt;&gt; the IESG and the community were not of one mind to say that th=
e use of such capitalized<br>
&gt;&gt;&gt; terms should be mandatory - quite a few people felt that the e=
nglish language was at<br>
&gt;&gt;&gt; least good enough to convey=C2=A0 the writer=E2=80=99s intent =
without having to aggrandize specific words.<br>
&gt;&gt;&gt; Thus the abstract basically was saying: if you want to use cap=
italized words here is a standard<br>
&gt;&gt;&gt; way to say what they mean<br>
&gt;&gt;<br>
&gt;&gt; Ah.=C2=A0 Then perhaps the clarification needs to go a little furt=
her and<br>
&gt;&gt; make this clear:<br>
&gt;&gt; - We&#39;re defining specific terms that specifications can use.<b=
r>
&gt;&gt; - These terms are always capitalized when these definitions are us=
ed.<br>
&gt;<br>
&gt; these definitions are only meaningful if the words are capitalized<br>
&gt;<br>
&gt;&gt; - You don&#39;t have to use them.=C2=A0 If you do, they&#39;re cap=
italized and<br>
&gt;&gt; their meanings are as specified here.<br>
&gt;&gt; - There are similar-looking English words that are not capitalized=
,<br>
&gt;&gt; and they have their normal English meanings; this document has not=
hing<br>
&gt;&gt; to do with them.<br>
&gt;&gt;<br>
&gt;&gt; ...and I&#39;d like to add one more, because so many people think =
that<br>
&gt;&gt; text isn&#39;t normative unless it has 2119 key words in all caps =
in it:<br>
&gt;&gt;<br>
&gt;&gt; - Normative text doesn&#39;t require the use of these key words.=
=C2=A0 They&#39;re<br>
&gt;&gt; used for clarity and consistency when you want that, but lots of<b=
r>
&gt;&gt; normative text doesn&#39;t need to use them, and doesn&#39;t use t=
hem.<br>
&gt;&gt;<br>
&gt;&gt; Barry<br>
&gt;<br>
&gt;<br>
<br>
</blockquote></div><br></div>

--001a113b4cc45d2419052f9474e2--


From nobody Sun Apr  3 07:33:20 2016
Return-Path: <stewe@stewe.org>
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 9A84312D127 for <ietf@ietfa.amsl.com>; Sun,  3 Apr 2016 07:33:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.903
X-Spam-Level: 
X-Spam-Status: No, score=-1.903 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] 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 er94fGv0t1LP for <ietf@ietfa.amsl.com>; Sun,  3 Apr 2016 07:33:17 -0700 (PDT)
Received: from na01-by2-obe.outbound.protection.outlook.com (mail-by2on0112.outbound.protection.outlook.com [207.46.100.112]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CFF7D12D105 for <ietf@ietf.org>; Sun,  3 Apr 2016 07:33:16 -0700 (PDT)
Received: from BLUPR17MB0275.namprd17.prod.outlook.com (10.162.235.146) by BLUPR17MB0273.namprd17.prod.outlook.com (10.162.235.144) with Microsoft SMTP Server (TLS) id 15.1.447.15; Sun, 3 Apr 2016 14:33:13 +0000
Received: from BLUPR17MB0275.namprd17.prod.outlook.com ([10.162.235.146]) by BLUPR17MB0275.namprd17.prod.outlook.com ([10.162.235.146]) with mapi id 15.01.0447.027; Sun, 3 Apr 2016 14:33:13 +0000
From: Stephan Wenger <stewe@stewe.org>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, Alissa Cooper <alissa@cooperw.in>, Jari Arkko <jari.arkko@piuha.net>
Subject: Re: Last Call on draft-bradner-rfc3979bis-08.txt ("Intellectual Property Rights in IETF Technology")
Thread-Topic: Last Call on draft-bradner-rfc3979bis-08.txt ("Intellectual Property Rights in IETF Technology")
Thread-Index: AQHRhDTbKR9yu1RueEWA9RrAiHSISp90M8+AgANL7gCAAG3+AA==
Date: Sun, 3 Apr 2016 14:33:13 +0000
Message-ID: <4DC1ED89-32FB-4B73-8922-C24713AEEC21@stewe.org>
References: <0000431F-F977-4A24-BA4D-064F740977A0@piuha.net> <7A6961E0-CCA6-4D1D-878A-176004AE2BAE@cooperw.in> <57006AF2.7020400@gmail.com>
In-Reply-To: <57006AF2.7020400@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: gmail.com; dkim=none (message not signed) header.d=none;gmail.com; dmarc=none action=none header.from=stewe.org;
x-ms-exchange-messagesentrepresentingtype: 1
x-originating-ip: [200.127.146.76]
x-ms-office365-filtering-correlation-id: 4d6975a4-2e20-447c-94dd-08d35bcce36a
x-microsoft-exchange-diagnostics: 1; BLUPR17MB0273; 5:o5f/0TROaLWT4mCaSDBnzLfjBHE9fmy6zz1S/DxbsitdfQyd3SkytIRmOjd4GIOSl5Modj24fnTHeH/suqkbEX2Umjj/Sk/wYtdyRb4VKhN/aGS90fM7O0PcoRbmALgI1PDS7VXRbtySHBcEP2/+eQ==; 24:kZK2+HOQSPGKQfnxLj3DzJZR5KAj6AjOllihdhDYyjpox5394D67ZvPqbNB3bFlOgDSrLeNc/QCDz9vxAmR4tEoLIMkiY18koxFRpE810Aw=
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:BLUPR17MB0273;
x-microsoft-antispam-prvs: <BLUPR17MB02737037844F61BA2E9FE811AE9C0@BLUPR17MB0273.namprd17.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040046)(601004)(2401047)(8121501046)(5005006)(3002001)(10201501046)(6041046)(6043046); SRVR:BLUPR17MB0273; BCL:0; PCL:0; RULEID:; SRVR:BLUPR17MB0273; 
x-forefront-prvs: 09011458FC
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(24454002)(92566002)(3280700002)(1096002)(1220700001)(586003)(3846002)(5008740100001)(6116002)(102836003)(2906002)(10400500002)(4326007)(3660700001)(19580405001)(19580395003)(33656002)(5001770100001)(81166005)(77096005)(2900100001)(87936001)(36756003)(11100500001)(189998001)(83716003)(82746002)(106116001)(99286002)(50986999)(86362001)(76176999)(54356999)(230783001)(5004730100002)(66066001)(122556002)(2950100001)(5002640100001)(42262002); DIR:OUT; SFP:1102; SCL:1; SRVR:BLUPR17MB0273; H:BLUPR17MB0275.namprd17.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en; 
spamdiagnosticoutput: 1:23
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
Content-ID: <7749EA2E6ACB2F49874E692BF739E649@namprd17.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: stewe.org
X-MS-Exchange-CrossTenant-originalarrivaltime: 03 Apr 2016 14:33:13.2178 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 865fc51c-5fae-4322-98ef-0121a85df0b6
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BLUPR17MB0273
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/d_YWbODEeku6PPYebrZSG22mdS4>
Cc: IETF <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: Sun, 03 Apr 2016 14:33:18 -0000

SGksDQoNCg0KDQpPbiA0LzIvMTYsIDIxOjU5LCAiaWV0ZiBvbiBiZWhhbGYgb2YgQnJpYW4gRSBD
YXJwZW50ZXIiIDxpZXRmLWJvdW5jZXNAaWV0Zi5vcmcgb24gYmVoYWxmIG9mIGJyaWFuLmUuY2Fy
cGVudGVyQGdtYWlsLmNvbT4gd3JvdGU6DQoNCj5BbGlzc2EsDQo+T24gMDEvMDQvMjAxNiAxMToz
OCwgQWxpc3NhIENvb3BlciB3cm90ZToNCj4uLi4NCj4+IDEpIEkgYWdyZWUgd2l0aCBvdGhlciBj
b21tZW50ZXJzJyBjb25jZXJucyBhYm91dCB0aGUgZGVmaW5pdGlvbiBvZiAicGFydGljaXBhdGlu
ZyIgd2l0aCByZXNwZWN0IHRvIFdHIGNoYWlycyBhbmQgQURzLiBJbiBwYXJ0aWN1bGFyIGluIHRo
ZSBjb250ZXh0IG9mIHNlY3Rpb24gNiwgdGhpcyBzZWVtcyBsaWtlIGl0IGNvdWxkIGxpbWl0IHRo
ZSBwb29sIG9mIHBlb3BsZSB3aG8gY2FuIHN0YW5kIGZvciBBRCByb2xlcywgYmVjYXVzZSB5b3Un
cmUgbm90IGFsbG93ZWQgdG8gcGFydGljaXBhdGUgaW4gY2FzZXMgd2hlcmUgeW91IHdvbid0IGJl
IGFibGUgdG8gZGlzY2xvc2UsIGJ1dCB5b3UgaGF2ZSBubyBpZGVhIGEgcHJpb3JpIHdoYXQgV0dz
IHdpbGwgZ2V0IGNoYXJ0ZXJlZCBpbiB5b3VyIGFyZWEgYW5kIHdoYXQgd29yayBpdGVtcyB0aGV5
IG1pZ2h0IHRha2UgdXAuDQo+DQo+SSBkb24ndCBzZWUgd2hhdCdzIG5ldyBhYm91dCB0aGlzIC0g
aXQncyBhbHdheXMgYmVlbiBhbiBhd2t3YXJkIHBvaW50LiBJIHdvcmtlZCBmb3INCj5hIG1ham9y
IHBhdGVudC1nZW5lcmF0aW5nIGNvbXBhbnkgd2hpbGUgSSB3YXMgaW4gdGhlIElFU0cgdGVuIHll
YXJzIGFnbywgYW5kIEkgaGFkDQo+dG8gcGF5IGF0dGVudGlvbiB0byB0aGlzLiBJJ20gbm90IHNh
eWluZyBpdCBpc24ndCBhIHByb2JsZW0sIGJ1dCBJIGRvbid0IHNlZSB0aGF0DQo+dGlnaHRlbmlu
ZyB1cCB0aGUgbGFuZ3VhZ2UgcmVhbGx5IG1ha2VzIHRoZSBwcm9ibGVtIGFueSB3b3JzZS4gKEhv
d2V2ZXIsIEkgc3RpbGwNCj5kb24ndCBzZWUgYW55IG5lZWQgdG8gc3RhdGUgdGhlIG9idmlvdXMs
IGkuZS4gdGhhdCBXRyBDaGFpcnMgYW5kIEFEcyBhcmUNCj5wYXJ0aWNpcGFudHMsIHVubGVzcyB0
aGV5IHJlY3VzZSB0aGVtc2VsdmVzIG9uIGEgcGFydGljdWxhciBtYXR0ZXIuKQ0KDQpNeSBmZWVs
aW5nIGlzIHRoYXQgYSBXRyBjaGFpciBhYnNvbHV0ZWx5IHNob3VsZCBiZSBpbiB0aGUgbG9vcCBv
ZiBldmVyeXRoaW5nIGdvaW5nIG9uIGluIGl0cyBXRywgYW5kIHRoZXJlZm9yZSBzaG91bGQgYmUg
dmlld2VkIGFzIOKAnHBhcnRpY2lwYXRpbmfigJ0gd2l0aCByZXNwZWN0IHRvIGFueSBDb250cmli
dXRpb24gbWFkZSB0byB0aGUgV0cgb3IgcmVsYXRlZCB0byB0aGUgV0cuDQoNCldpdGggcmVzcGVj
dCB0byBBRHMsIEkgZmluZCBCcmlhbuKAmXMgYXJndW1lbnQgZ2VuZXJhbGx5IGNvbXBlbGxpbmcu
ICBIb3dldmVyLCBJIGRvbuKAmXQga25vdyBob3cgYW4gQUQgY2FuIG9yIHNob3VsZCByZWN1c2Ug
aGltc2VsZi9oZXJzZWxmIGZyb20gYSBwYXJ0aWN1bGFyIG1hdHRlciBpbiB0aGUgc2Vuc2Ugb2Yg
c2hlZGRpbmcgaGlzL2hlciBwb3NzaWJsZSBvYmxpZ2F0aW9ucyB1bmRlciBCQ1A3OS4gIEFGQUlD
VCwgaGlzdG9yaWNhbGx5LCB3aGVuIGFuIEFEIHJlY3VzZXMgaGltc2VsZi9oZXJzZWxmLCBpdCB3
YXMgb2Z0ZW4gYmFzZWQgb24gdG9vIG11Y2gga25vd2xlZGdlIGFuZCBpbnRlcmVzdCBpbiBhIGNl
cnRhaW4gdGVjaG5vbG9neSwgd2l0aCByZXNwZWN0IHRvIHBlcnNvbm5lbCBiZWhpbmQgdGhlIHRl
Y2hub2xvZ3ksIGFuZCBzbyBvbi4gIEluIHN1Y2ggYSBjYXNlLCBhIHJlY3VzZSBmcm9tIElQUiBv
YmxpZ2F0aW9ucyBvZiBhbnkgdHlwZSB3b3VsZCBub3QgYmUgZGVzaXJhYmxlLiAgVGhlIG1vcmUg
d2UgcmVsYXggdGhlIGRpc2Nsb3N1cmUgcmVxdWlyZW1lbnRzLCB0aGUgbW9yZSB3ZSBlbmFibGUg
Z2FtaW5nIHRoZSBwb2xpY3kgYnkgYSDigJxjb21wYW55IG1hbuKAnS0tYW5kIHRoYXQgZm9ybSBv
ZiBnYW1pbmcgbWF5IG5vdCBjb21lIHVwIHVudGlsIHllYXJzIGFmdGVyIHRoZSBwZXJzb24gaGFz
IHJlc2lnbmVkIGZyb20gdGhlIEFEIHBvc2l0aW9uLCByZW5kZXJpbmcgdGhlIElFVEbigJlzIGlu
dGVybmFsIHNhbmN0aW9uIG1lY2hhbmlzbSBpbmVmZmljaWVudC4NCg0KU3RlcGhhbg0KDQo+DQo+
ICAgIEJyaWFuDQo+DQo=


From nobody Sun Apr  3 08:29:40 2016
Return-Path: <john-ietf@jck.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 79A1312D139; Sun,  3 Apr 2016 08:29:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 9tWGukPI6Yhr; Sun,  3 Apr 2016 08:29:37 -0700 (PDT)
Received: from bsa3.jck.com (static-65-175-133-137.cpe.metrocast.net [65.175.133.137]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8845112D119; Sun,  3 Apr 2016 08:29:37 -0700 (PDT)
Received: from hp5.int.jck.com ([198.252.137.153] helo=JcK-HP5.jck.com) by bsa3.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1amjy3-000L1J-6S; Sun, 03 Apr 2016 11:29:35 -0400
Date: Sun, 03 Apr 2016 11:29:30 -0400
From: John C Klensin <john-ietf@jck.com>
To: 95attendees@ietf.org
Subject: Remote participants, registration, and mailing lists -- unintended consequences
Message-ID: <A7B0E0D5DE4C72D2729D44A8@JcK-HP5.jck.com>
In-Reply-To: <57012A74.1060400@alvestrand.no>
References: <57012A74.1060400@alvestrand.no>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/SM4pdZtQD-cem6HnUqSxVGZ_FjI>
Cc: 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: Sun, 03 Apr 2016 15:29:39 -0000

Hi.

Not to complain but to add to whatever consideration occurs this
week about getting remote participants, more evidence that these
things need to be thought through carefully has turned up in the
last 24 hours.

* Apparently, remote participants who have registered are listed
on the "registered attendees" list without any differentiation
from face to face attendees.  That has resulted in my getting
several "when can we meet up" messages and some confused people.
Not a big deal, but an unnecessary waste of people's time.  More
important, if questions arose in the future about who was, or
was not, at a particular meeting, it could lead to even more
confusion and inconvenience (e.g., IIR, registration records
have sometimes been the subject of subpoenas).

* When we register, we apparently automatically signed up for
the [95all] and allowed to check the box that gets us on the
[95attendees] mailing lists.  That is fine -- I used to have to
try to monitor the archives of [NNall] to be sure I didn't miss,
e.g., important schedule changes (although most of those are
copied to IETF-announce and/or the IETF discussion list).
Announcements of specially-formatted agendas, workshop and lunch
seminar announcements, and the like are as useful to those of us
who are remote as those who are present (even if relevant
sessions are not supported remotely, we know what we are
missing).  But the N/S ratio is incredible -- I really don't
need the regular extended  discussions of plug converters,
nearby restaurants, SIM cards, laundry, nearby ATMs, and so on.

So, for the future, if we are really going to do this remote
participant registration thing, it would be nice if someone
would really take responsibility for thinking through all of the
implications and take action on them.

To all who are in Buenos Aires, best wishes for a successful
meeting.  And to all who are participating remotely, let's hope
that these difficulties with registration are the last problems
of the week and that everything else --the actual feeds and
connections-- will go really smoothly.

    john


From nobody Sun Apr  3 08:53:33 2016
Return-Path: <rpelletier@isoc.org>
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 4BB8112D0E2; Sun,  3 Apr 2016 08:53:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.902
X-Spam-Level: 
X-Spam-Status: No, score=-101.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=isoc.onmicrosoft.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 CO-r8oKLMgti; Sun,  3 Apr 2016 08:53:30 -0700 (PDT)
Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1on0656.outbound.protection.outlook.com [IPv6:2a01:111:f400:fc10::656]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BD4C212D0A0; Sun,  3 Apr 2016 08:53:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=isoc.onmicrosoft.com;  s=selector1-isoc-org; h=From:To:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=RbbkCRBiC073zPCJ03V6JTwdPdon3OJctLfD6cVsuY4=; b=ulcFb0Ya5p604Iq5IbStLQBO8iR9SrfUdmfUmBxuL2Cl6O+HUThYB7R3t/ChaSHgP6OvGRSMLVp1FugJ+bDa0mk0nFdSRRoXJKKwOAvt+SVbBaI9cgLJgSsqdQC3IJWS46D3q537fzTQoxPjbcBB3W19tj583+eFXKyGiuMNQ8I=
Authentication-Results: jck.com; dkim=none (message not signed) header.d=none;jck.com; dmarc=none action=none header.from=isoc.org;
Received: from [IPv6:2001:67c:370:176:b8e6:cbb6:d842:643e] (2001:67c:370:176:b8e6:cbb6:d842:643e) by BY2PR0601MB1558.namprd06.prod.outlook.com (10.163.107.140) with Microsoft SMTP Server (TLS) id 15.1.447.15; Sun, 3 Apr 2016 15:53:06 +0000
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0 (Mac OS X Mail 9.2 \(3112\))
Subject: Re: Remote participants, registration, and mailing lists -- unintended consequences
From: Ray Pelletier <rpelletier@isoc.org>
In-Reply-To: <A7B0E0D5DE4C72D2729D44A8@JcK-HP5.jck.com>
Date: Sun, 3 Apr 2016 12:54:43 -0300
Content-Transfer-Encoding: quoted-printable
Message-ID: <297ADFD7-8581-42EE-8C5C-358EE8DC322F@isoc.org>
References: <57012A74.1060400@alvestrand.no> <A7B0E0D5DE4C72D2729D44A8@JcK-HP5.jck.com>
To: John C Klensin <john-ietf@jck.com>
X-Mailer: Apple Mail (2.3112)
X-Originating-IP: [2001:67c:370:176:b8e6:cbb6:d842:643e]
X-ClientProxiedBy: SN1PR15CA0016.namprd15.prod.outlook.com (10.163.200.26) To BY2PR0601MB1558.namprd06.prod.outlook.com (10.163.107.140)
X-MS-Office365-Filtering-Correlation-Id: 9231c75b-3b00-4af6-0a41-08d35bd80cde
X-Microsoft-Exchange-Diagnostics: 1; BY2PR0601MB1558; 2:41PmaEtQhChfs6t14xyc0iPR48HJyi/CrLVNym/WwbRTv9Gg+Vl6AWrdi3g7EJ9WC58rq3n6jN5yB8mZ3bkXwKXw5DM45HZ14mcMdh/GuaKUYKm/g02/LxbliNWa5GzIvfWfnm9Rc6rtjdyA/MX396pccqpsa5Qfc4klTERBZmk0t7WgWCUj7lzIoZbjfIWA; 3:PZ+tGEk2orEbgCuekQB/BVD89T5+1moygStOgmwuuq/u+p1UIRHwN+Aw7lIol/EG2hS+dSeQfXwKwZehif2A0CG68GNeGqiNGq3plt66MBdniivdfOa2qh1amyoKEyhM; 25:BNhnE6sWwUqQeowkVIHntvfoQZUpbaMUngll8ztMHEqPcTc+AtunIJuqK7LPXpH1u5qJwGGICqRQfW7NxaMXMfFwnRJ/pxRPj9benYMWmz8BmMqyq1m5uwI279jIu9fSfI1H4t02faJ4/29mgdWDnrQS7Fw2Lv3vafVmaNMbe174lZkhfkfS0qq4veQlJHw5zA1P3hw3mUQfYNKnA+vnaM3Cj2Urns9wqPN6ocxqw2jHtB4/gdk5sQyg/0P+djkk0ybn1eG4nk0y1HGHYqNlp3rvhrgAdYyDWbieqeKTePvIZwMuvXflXhH2/d76411xOWJ8MsvNK7cJJ9DWlPDOS1y6BQDx5M5SRSWJnEjCXo8=
X-Microsoft-Antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:BY2PR0601MB1558;
X-Microsoft-Exchange-Diagnostics: 1; BY2PR0601MB1558; 20:eHnvas/vxfFw8jb6ntA0oyfY5X8TBX5szmyU2FZfreMqr0CMxSX1PZjussG849UIlt6abmJYN1mPZbJ2Ox/yQB/kEL7iIoOeNC++I9lEnwpC6xwqOMt15tKj064iWcWjclXctNY1INA+xVPbySflzcSLYNvx4LYdKp4hcP8yTsAUiCkKKHBZtsROe7onUQX2UcWOBflsNqGML+pCcPms/T2BHMssxhdZWRiOFrBmKL4I6OZcinnh3t8e2TTz6+SlccdUscvB3OxNnhOVMT5ZwZK1IId7ghmjBxFfLeq+MbzJfJxL+S7KC8M30gKTPSM1S12z3CaEPIH/WWHQxNIUk1Ly1eAzDj6HmqKcWp38cmhucNNx3Ygx1Mj9Zfcc+vLwImK2KvWMuLx2SjmwsE8VS+x1MJ/xxsEMdjrs47AWFgN+7KKyOYCgPwlz8sIsvNuFWqsNfwCsVFsOTMufOE/aDMChDLam+XBnpCYEolwG1QXf4MAYXLgrleKOkb/k/ht1; 4:Ia2XzMH3Lo6vCf317MS2JfUcOCYxxOeIaT92DxOY2ret1aQ3QqSDIeMjKtj9v/TmIzjE2GfH0AgdasVBbBYjsBkoUpvR4AXu3aEYoeLfAv7RWconUPKKKcpuLBxAujAGhX5YfzD8Elk7Q70a+8fa5IkpRSj4JLV1ksGDo8SZfHyEWHFNF9T9atUAHi8pwpw5pyqcpMNFIfkBVQ8dopI+q1qlFJvQo2U5KShnv1svulb0u1JAlyYjyeXs8nzjbraQDnIWavY9au4QBr1lB/UDX9OqZ445Sn7AgJ5bdGs34pIR7RrE69CE+360syajZOLxbmkgNKzadHdtQ5HRKZE4QRx/IHiw4712qZ44YNNSk8xzx++Fwb1karuOd5GOFXKb
X-Microsoft-Antispam-PRVS: <BY2PR0601MB1558CF17FDC5D6301FBC3A5AB09C0@BY2PR0601MB1558.namprd06.prod.outlook.com>
X-Exchange-Antispam-Report-Test: UriScan:;
X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(601004)(2401047)(5005006)(8121501046)(10201501046)(3002001); SRVR:BY2PR0601MB1558; BCL:0; PCL:0; RULEID:; SRVR:BY2PR0601MB1558; 
X-Forefront-PRVS: 09011458FC
X-Forefront-Antispam-Report: SFV:NSPM; SFS:(10009020)(4630300001)(6009001)(24454002)(377454003)(23676002)(57306001)(189998001)(82746002)(4326007)(47776003)(36756003)(110136002)(2950100001)(1096002)(6116002)(2906002)(15975445007)(81166005)(77096005)(19580405001)(19580395003)(92566002)(86362001)(586003)(50986999)(83716003)(76176999)(5004730100002)(5008740100001)(33656002)(50466002)(42186005)(50226001)(3826002); DIR:OUT; SFP:1101; SCL:1; SRVR:BY2PR0601MB1558; H:[IPv6:2001:67c:370:176:b8e6:cbb6:d842:643e]; FPR:; SPF:None; MLV:sfv; LANG:en; 
X-Microsoft-Exchange-Diagnostics: 1; BY2PR0601MB1558; 23:9KPBubFFWxhIcFfOsMrW+MS9CTqobts9oLkJg+VYCdG4IagxFtS9CaDsIoqcuTEGMr9uGdCcU4OV/bQHj3IOVimVJIiv4lELR282c7MH1v4elOTFJjO9ivvLczx7KZs6md9d6iTQbQVzX6iHB4xPi3rmFrYBckjonOQd0Xkoc0ndPPwh9+xsDB79h52iUFIkUx566KXWLwq7gdMh8kWqmLJqzn2J7Osw7VKXWx9BgdG0AC19RWVZzbsc++cEt3Ud8gF8oKqcW+YD7eXzNVXdBhgoSP9++Ytc+pI9S7zM+BGahVADMQtgNXoEMkFSd0/muyMxJCTYOrIrN8XtaaLj4y9IMeJgCQIFUHQjRVp38c8OsXOjbhET00JUf1BzYLMPvqXhCqw7cZGGgD+Js7tImhOL+S+BGPAjcFoEClC7+r2UUmbfpQNNxl6f+tg2oLRX8xXT6e8sgvaKhaYIubN6YlmwiEwAAXTlDLY0kY1DrR6eiNKzX7Q9qu1ZKk3wyvSY/nqIrADo8CDoTNf6wcVj6pk57v67HFy+jGXOqL2mFHUh05G6vKx8GkggjaRvuxhr1jEZBDMiYoy3+ix3JqBgSYIcwxN3ztF9GPC4s3YkgNoBb/EJ2b8kp9v8MgpwhwpdPD/UR56uQiPYBpbeKgF+DqTGJuf0cJ2OtsBHW2z+EeTe+VA13amN8/KkGHMKvbMetVCwvwwO5IYCqJ0cYOMX8OzemZb+ATO+4xE3IjsUtuflRF+yY4F8EOmd79iFxHOcFE5AVxbVPvxTq5U4RmQuXIIqmPsMCn9GYqhD3G8QILYJp4JRh5QVICXfwIeXu01v19xbSFh2fDiGGkAtl6cjVniHy0175fvX/3pXY6sgS8fDlCAJdQ9ciVotkPqQ4tDjL3I5QsDXrbAy4yAmH8MGcUOcHRQtSXN99p/yPn33/Wk=
X-Microsoft-Exchange-Diagnostics: 1; BY2PR0601MB1558; 5:oL2RNljBtKyF6hYE2viU+BBCGQJaxafDPeMd1tXBsuwJBbKtG5JYN3S0MEdcBzkQBrsvA92x4EwD27TXC171GoGy+JEJyr8KWquVjuCYsBVdT438DaDF7wo4OcOK74+cykHLhbEmSi1LZwkFJtsPpg==; 24:+GFAh9+oTg7KXuEvab7Av9uWGAQ2pV3ItDNuKZzypVjbBuNgz9PaSGcn0sIGG2iFKhpBt1p1I1JesJ2aaLU3/qDQ21mC4ks+Jm3ifZ32dP4=
SpamDiagnosticOutput: 1:23
SpamDiagnosticMetadata: NSPM
X-OriginatorOrg: isoc.org
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 03 Apr 2016 15:53:06.3032 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BY2PR0601MB1558
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/C2kG9M0vY4QiHPpiKhKTGwFYLOA>
Cc: 95attendees@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: Sun, 03 Apr 2016 15:53:32 -0000

John,

> On Apr 3, 2016, at 12:29 PM, John C Klensin <john-ietf@jck.com> wrote:
>=20
> Hi.
>=20
> Not to complain but to add to whatever consideration occurs this
> week about getting remote participants, more evidence that these
> things need to be thought through carefully has turned up in the
> last 24 hours.
>=20
> * Apparently, remote participants who have registered are listed
> on the "registered attendees" list without any differentiation
> from face to face attendees.

Thanks.  It has been noticed and will be changed.

>  That has resulted in my getting
> several "when can we meet up" messages and some confused people.
> Not a big deal, but an unnecessary waste of people's time.

This is not clear to me.  This traffic wouldn=E2=80=99t be passed on the=20=

95All list.  It could be on the 95Attendees list.

>  More
> important, if questions arose in the future about who was, or
> was not, at a particular meeting, it could lead to even more
> confusion and inconvenience (e.g., IIR, registration records
> have sometimes been the subject of subpoenas).

When asked it=E2=80=99s usually the Blue Sheet, which now includes=20
remote attendance "eBlue Sheets=E2=80=9D at WG sessions.

>=20
> * When we register, we apparently automatically signed up for
> the [95all]

Yes, administrative matters related to the meeting, e.g. schedule
changes.

> and allowed to check the box that gets us on the
> [95attendees] mailing lists.

Correct, that is optional. =20

>  That is fine -- I used to have to
> try to monitor the archives of [NNall] to be sure I didn't miss,
> e.g., important schedule changes (although most of those are
> copied to IETF-announce and/or the IETF discussion list).
> Announcements of specially-formatted agendas, workshop and lunch
> seminar announcements, and the like are as useful to those of us
> who are remote as those who are present (even if relevant
> sessions are not supported remotely, we know what we are
> missing).  But the N/S ratio is incredible -- I really don't
> need the regular extended  discussions of plug converters,
> nearby restaurants, SIM cards, laundry, nearby ATMs, and so on.

We=E2=80=99ve tried to decrease this by having a wiki for each meeting =
so that
these matters can be addressed there, some by staff, but much of it
by locals and experienced travelers.  So far, the use of the wiki
has been disappointing. =20

https://www.ietf.org/registration/MeetingWiki/wiki/ietf95

>=20
> So, for the future, if we are really going to do this remote
> participant registration thing, it would be nice if someone
> would really take responsibility for thinking through all of the
> implications and take action on them.

We are going to do this remote participation thing  and=20
welcome all suggestions to making it a better experience for=20
all - remotees,local attendees, WG Chairs, etc.

>=20
> To all who are in Buenos Aires, best wishes for a successful
> meeting.  And to all who are participating remotely, let's hope
> that these difficulties with registration are the last problems
> of the week and that everything else --the actual feeds and
> connections-- will go really smoothly.

Amen.

Best
Ray
>=20
>    john
>=20


From nobody Sun Apr  3 08:54:00 2016
Return-Path: <alexandre.petrescu@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 A4E8712D605 for <ietf@ietfa.amsl.com>; Sun,  3 Apr 2016 08:53:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.932
X-Spam-Level: 
X-Spam-Status: No, score=-3.932 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, SPF_SOFTFAIL=0.665] 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 kdJB-qi89Pel for <ietf@ietfa.amsl.com>; Sun,  3 Apr 2016 08:53:58 -0700 (PDT)
Received: from sainfoin-out.extra.cea.fr (sainfoin-out.extra.cea.fr [132.167.192.145]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 94DDB12D595 for <ietf@ietf.org>; Sun,  3 Apr 2016 08:53:50 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by sainfoin.extra.cea.fr (8.15.2/8.15.2/CEAnet-Internet-out-2.4) with ESMTP id u33FrmGJ025339 for <ietf@ietf.org>; Sun, 3 Apr 2016 17:53:48 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 549D5202113 for <ietf@ietf.org>; Sun,  3 Apr 2016 17:54:53 +0200 (CEST)
Received: from muguet2.intra.cea.fr (muguet2.intra.cea.fr [132.166.192.7]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 40AAB200EC5 for <ietf@ietf.org>; Sun,  3 Apr 2016 17:54:53 +0200 (CEST)
Received: from [132.166.84.167] ([132.166.84.167]) by muguet2.intra.cea.fr (8.15.2/8.15.2/CEAnet-Intranet-out-1.4) with ESMTP id u33FrlBc006267 for <ietf@ietf.org>; Sun, 3 Apr 2016 17:53:48 +0200
To: IETF Discussion <ietf@ietf.org>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Subject: storage space at meeting (wardrobe)?
Message-ID: <57013C8A.4010704@gmail.com>
Date: Sun, 3 Apr 2016 12:53:46 -0300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="------------020608050406020101070809"
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/8bwQ-6Wpc66aF51c4SyJyminXCw>
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: Sun, 03 Apr 2016 15:53:59 -0000

This is a multi-part message in MIME format.
--------------020608050406020101070809
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit

Hi, IETFers in Buenos Aires,

I stay at another hotel, and I think it is good to have storage space at 
the meeting for carry-on items, or a wardrobe for coats.

Hilton provides such but only for guests.  Does Hilton delegate such 
service to IETF?

Such storage space is good for things like:
- wet coat
- umbrella
- scooter

Alex


--------------020608050406020101070809
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit

<html>
  <head>

    <meta http-equiv="content-type" content="text/html; charset=utf-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <font face="Courier New">Hi, IETFers in Buenos Aires,<br>
      <br>
      I stay at another hotel, and I think it is good to have storage
      space at the meeting for carry-on items, or a wardrobe for coats.<br>
      <br>
      Hilton provides such but only for guests.Â  Does Hilton delegate
      such service to IETF?<br>
      <br>
      Such storage space is good for things like:<br>
      - wet coat<br>
      - umbrella<br>
      - scooter<br>
      <br>
      Alex<br>
      <br>
    </font>
  </body>
</html>

--------------020608050406020101070809--


From nobody Sun Apr  3 09:56:57 2016
Return-Path: <dhc@dcrocker.net>
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 A552E12D104; Sun,  3 Apr 2016 09:56:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] 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 XgJm2shE70V5; Sun,  3 Apr 2016 09:56:54 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 449D812D102; Sun,  3 Apr 2016 09:56:54 -0700 (PDT)
Received: from [192.168.1.168] (76-218-10-206.lightspeed.sntcca.sbcglobal.net [76.218.10.206]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id u33Gurrm031637 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Sun, 3 Apr 2016 09:56:53 -0700
Subject: Re: Remote participants, registration, and mailing lists -- unintended consequences
To: 95attendees@ietf.org
References: <57012A74.1060400@alvestrand.no> <A7B0E0D5DE4C72D2729D44A8@JcK-HP5.jck.com>
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
Message-ID: <57014B51.9050909@dcrocker.net>
Date: Sun, 3 Apr 2016 09:56:49 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.7.1
MIME-Version: 1.0
In-Reply-To: <A7B0E0D5DE4C72D2729D44A8@JcK-HP5.jck.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Sun, 03 Apr 2016 09:56:53 -0700 (PDT)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/Mjh9md_-XUdV_0f3z1daDakU8OA>
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: dcrocker@bbiw.net
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: Sun, 03 Apr 2016 16:56:55 -0000

On 4/3/2016 8:29 AM, John C Klensin wrote:
> So, for the future, if we are really going to do this remote
> participant registration thing, it would be nice if someone
> would really take responsibility for thinking through all of the
> implications and take action on them.


The complexities and subtleties of this task are significant.

I suggest creating a wiki page for collaboratively developing a list og 
issues, requirements, preferences, fears, etc.  We can add to it (or 
delete from it) as we gain experience.  This will be a long process. 
Eventually the page might get relatively stable, but I suspect only 
relatively.

An obscure example of the challenge:  Being able to see the posters that 
are put up for viewing during the social, since remote attendees aren't 
at the social.  But the posters are worth reviewing.

The rather daunting meta-issue is learning to think and plan for IETF 
Meeting details much as the universal access folks have had to train 
architects to think:  At every decision-point, think about the decision 
in terms of remote attendees and make explicit functionality and 
usability decisions about them.  (Obviously deciding not to accommodate 
remote attendees can be an entirely justifiable choice, depending on the 
topic.)


d/
-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net


From nobody Sun Apr  3 11:36:38 2016
Return-Path: <iab-chair@iab.org>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from iab.org (dhcp-b2a2.meeting.ietf.org [31.133.178.162]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPSA id BF8F012D0D8; Sun,  3 Apr 2016 11:36:34 -0700 (PDT)
Date: Sun, 3 Apr 2016 14:36:30 -0400
From: IAB Chair <iab-chair@iab.org>
To: ietf@ietf.org, ietf-announce@ietf.org, architecture-discuss@ietf.org
Subject: Report from the IAB before IETF 95
Message-ID: <20160403183629.GB540@iab.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
User-Agent: Mutt/1.5.23 (2014-03-12)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/bC4PcEQ8ClHu2D_mKRqL4UYP52Y>
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: Sun, 03 Apr 2016 18:36:36 -0000

Dear colleagues,

This is the report to the community from the IAB about our activities
since IETF 94 (which was in Yokohama). We used to go over much of this
sort of material in the plenary sessions. Shorter time for plenary
sessions in the weekly agenda led us to try this form of report, and
it was popular. So we are continuing with it. We hope that this form
allows you to prepare topics you might want to discuss during the open
mic. But of course, if you have views you want to make known by email,
we're easy to reach: send mail to architecture-discuss@iab.org to
reach our public discussion list, and iab@iab.org to reach just the
IAB

The IAB has a few chartered roles. We confirm the appointments to the
IESG and perform standards process oversight and handle appeals. We
also perform architectural oversight, we manage the RFC series and the
IETF's relationship with IANA, and we handle liaisons both to ISOC and
to other organizations. We try to ensure that anything we do is part
of one of these areas of responsibility, and we try to make sure these
are all covered.

Since IETF 94, here is what we've done:

    â€˘ RFC 7720, "DNS Root Name Service Protocol and Deployment
    Requirements".  This is a BCP and therefore ended up an AD
    sponsored RFC.  The purpose of this was to modernize RFC 2870 and
    take out the parts that are not really the IETF's or IAB's job.
    (External liaisons)

    â€˘ RFC 7687, "Report from the Strengthening the Internet (STRINT)
    Workshop".   More on workshops below.  (Architectural oversight)

    â€˘ RFC 7749, "The 'xml2rfc' Version 2 Vocabulary".  More about
    documents about the RFC series below.  (Manage the RFC series)

    â€˘ RFC 7754, "Technical Considerations for Internet Service
    Blocking and Filtering".  This is the sort of architectural
    analysis document that is a big part of the IAB's job.  It is fair
    to say that most of us prefer this sort of work over the
    administrative pieces. (Architectural oversight)

    â€˘ RFC 7827, "The Role of the IRTF Chair".  This is an IAB stream
    document because the IAB appoints the IRTF Chair.

    â€˘ Internet Of Things Semantic Interoperability (IOTSI) workshop.
    The IAB gratefully acknowledges the sponsorship of Ericsson in
    holding this workshop.  (Architectural oversight)

    â€˘ Comments on the ICANN CCWG-Accountability third draft report.
    (External liaison)

    â€˘ Comments on ICANN's â€śRegistration Data Access Protocol (RDAP)
    Operational Profile for gTLD Registries and Registrarsâ€ť. (External
    liaison)

    â€˘ Confirmed the IESG appointments from the Nomcom, for members
    whose term will start at IETF 95. (Confirm IESG)

    â€˘ Selected Adam Roach as a new member for the RFC Series Oversight
    Committee. (Manage the RFC series)

    â€˘ Selected a new appointment to the ISOC Board of Trustees.  As of
    this writing, the new appointment hasn't been announced.  The
    IAB's selection is to be confirmed by the IESG.  (ISOC liaison)

    WELCOME TO NEW MEMBERS AND THANKS TO DEPARTING MEMBERS

The first IETF meeting of the year is when the new IAB is seated.
This also means we sometimes have to say good-bye to departing IAB
members.

This year, we wish our colleagues Mary Barnes and Marc Blanchet a fond
farewell. Mary joined the IAB in 2014 after serving from 2012 to 2014
as the IAB Executive Director. Marc joined the IAB in 2012. The IAB
and the Internet community have benefitted greatly from their insights
and service, and we thank them both.

This year, we are pleased to welcome Lee Howard and Martin Thomson. We
know that they will both bring their usual sharp observations and
vigour to the IAB's activities. We thank them for being willing to
serve the community this way, and thank the Nomcom for their
appointment.

    DOCUMENTS

The IAB has several documents in flight. Find the current list of
every IAB document in the datatracker, at
https://datatracker.ietf.org/stream/iab/. Architectural oversight
makes up an important chunk of the current documents:

draft-iab-privsec-confidentiality-mitigations-06 
    Confidentiality in the Face of Pervasive Surveillance
draft-iab-protocol-transitions-01 
    Out With the Old and In With the New: Planning for Protocol Transitions
draft-iab-rfc3677bis-00 
    IETF ISOC Board of Trustee Appointment Procedures
draft-iab-web-pki-problems-01 
    Problems with the Public Key Infrastructure (PKI) for the World Wide Web

Currently, there are also quite a few documents related to the planned
RFC series format change:

draft-iab-html-rfc-02 
    HyperText Markup Language Request For Comments Format
draft-iab-rfc-css-00 
    CSS Requirements for RFCs
draft-iab-rfc-framework-04 
    RFC Format Framework
draft-iab-rfc-nonascii-01 
    The Use of Non-ASCII Characters in RFCs
draft-iab-rfc-plaintext-02 
    Requirements for Plain-Text RFCs
draft-iab-rfc-use-of-pdf-01 
    PDF for an RFC Series Output Document Format
draft-iab-rfc5741bis-02 
    On RFC Streams, Headers, and Boilerplates
draft-iab-rfcv3-preptool-01 
    RFC v3 Prep Tool Description
draft-iab-svg-rfc-02 
    SVG Drawings for RFCs: SVG 1.2 RFC
draft-iab-xml2rfc-03 
    The "xml2rfc" version 3 Vocabulary

These have been out for public comment.  As we said previously, the
way these are getting handled is that they all note that they're
likely to change.  We'll publish them, then get some experience.
Later, we might find that some of our choices turn out to be less than
ideal, so we'll have a chance to adjust the final implementation.

    WORKSHOPS

As noted above, the IAB held the IOTSI workshop in March. We've
decided to continue using the mailing list for further follow-on
discussion; you can join iotsi@iab.org at
https://www.iab.org/mailman/listinfo/iotsi.

An issue came up with this workshop that has come up before and that
we mentioned last time: workshop transparency and remote
participation.

As part of the IAB's job of architectural oversight, we try to convene
workshops to inform observations. These are usually about gaps or
issues we see, in an effort to draw attention to those things from the
wider IETF community. Workshops of this sort work best when the group
is somewhat small and informal, because that tends to encourage
informal discussion and easy exploration of the issues.

But of course, the IAB is often not the only group that notices the
issues or gaps, and others often want to participate. Some people
can't make the trip to a workshop; others just want to follow along.
Yet the necessary style to support remote participation is probably
more formal and presentation-oriented than may always be good.

The IAB's current policies about this are reflected in a note we
posted at
https://mailarchive.ietf.org/arch/msg/architecture-discuss/Vns0-GWYOHqP9wq7uic0DS331co.
The short version is that we are not going to commit to remote
participation generally, but it will be something we ask workshop
organizers to consider in designing workshops. Please have a look at
the full posting for all the considerations on this topic.

    PROGRAMS

The IAB organizes its work, for the most part, into programs.  There
are basically two classes: management programs and architectural
programs.  The former are how we handle the oversight of various
things, and the latter are where we do architectural work.  The former
are expected to last as long as the IAB continues to have that
oversight function; the latter last until the IAB has come to a
conclusion on the relevant group of topics, and we expect them to wind
down afterwards.

Since IETF 94, we have taken to reviewing the programs as part of our
regular teleconferences. The goal is to perform one review of every
program between every IETF meeting, though that won't always be
possible. We'd noticed that program reviews were too infrequent
(historically, just once a year, at the IAB retreat). More regular
review allows us to adjust program priorities and membership more
often, and we hope that it will ensure that programs remain vital (or
else close down). Minutes of the reviews appear in the regular IAB
meeting minutes, which you can find at
https://www.iab.org/documents/minutes/. Every program has an
associated discussion list where topics relevant to the program can be
discussed by anyone who wants to join. You can find the lists at
https://www.iab.org/iab-mailing-lists/.

Management programs:
    IANA Evolution    
    IETF Protocol Registries Oversight Committee (IPROC, with IAOC)

            These programs have been attending to the anticipated
            change to the IANA's relationship to the US Government.
            The former of these is responsible to keep track of the
            IETF's use of IANA, and the latter ensures that the IANA
            Memorandum of Understanding with ICANN is administered
            effectively.  Participants in this area have been,
            perhaps unfortunately, extremely busy as a result of the
            IANA changes. IPROC was reviewed on 2016-01-27 and IANA
            oversight was reviewed on 2016-02-10.
            
    Liaison Oversight

            Reviewed on 2016-03-23.

    RFC Editor (includes RSOC)

            This program has of course been at the centre of the RFC
            series format changes; it was reviewed 2016-02-24.

Architectural issues:
    Emergency Services

            Reviewed 2016-02-03, closed as of 2016-04-03

    Internationalization

            This program is up for review soon.  At a previous
            technical plenary we had some discussion of the state of
            affairs with internationalization, and there is still
            reason to be concerned that this topic is in serious
            trouble around the IETF.  

    IP Stack Evolution

            Reviewed 2016-03-02

    Names and Identifiers

            The Names and Identifiers program has not been reviewed
            yet (it is up next), but it has been generating quite a
            bit of discussion on inip-discuss@iab.org.  The arcing BoF
            at IETF 95 was inspired in part by some of those discussions.  

    Privacy and Security
    
            Reviewed 2016-01-13.

    INTERNET RESEARCH TASK FORCE

The IAB appoints the IRTF Chair. Lars Eggert, the current IRTF Chair,
has announced that he will not seek re-appointment, having served
since March of 2011. The IAB is starting its search for a new Chair.
We are grateful for Lars's tremendous service in this role, and we'll
have our work cut out for us. We will be making announcements soon
about our search, so look for those. In the meantime, if you are
interested or know someone who you think might be a good candidate,
have a look at RFC 7827 to see what the job entails.

Respectfully submitted,
Andrew Sullivan
For the IAB


-- 
IAB Chair (Andrew Sullivan)
iab-chair@iab.org


From nobody Sun Apr  3 12:04:33 2016
Return-Path: <Francis.Dupont@fdupont.fr>
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 AD58B12D171 for <ietf@ietfa.amsl.com>; Sun,  3 Apr 2016 12:04:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.912
X-Spam-Level: 
X-Spam-Status: No, score=-1.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 lvUaZAer1VQC for <ietf@ietfa.amsl.com>; Sun,  3 Apr 2016 12:04:30 -0700 (PDT)
Received: from givry.fdupont.fr (givry.fdupont.fr [IPv6:2001:41d0:1:6d55:211:5bff:fe98:d51e]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7FB4012D0F3 for <ietf@ietf.org>; Sun,  3 Apr 2016 12:04:29 -0700 (PDT)
Received: from givry.fdupont.fr (localhost [IPv6:::1]) by givry.fdupont.fr (8.14.7/8.14.7) with ESMTP id u33ItEcb032923; Sun, 3 Apr 2016 20:55:15 +0200 (CEST) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201604031855.u33ItEcb032923@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: ietf@ietf.org
Subject: Re: Uppercase question for RFC2119 words
In-reply-to: Your message of Mon, 28 Mar 2016 09:28:59 -0400. <20160328132859.GP88304@verdi>
Date: Sun, 03 Apr 2016 20:55:14 +0200
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/pYeMb9pedSmBKyvOUZX2dy-wBFo>
Cc: Barry Leiba <barryleiba@computer.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: Sun, 03 Apr 2016 19:04:32 -0000

As a draft reviewer I often found the RFC 2119 really needs a small
update about this particulat point so I STRONGLY support your idea!

Thanks

Francis.Dupont@fdupont.fr

PS: I am for option 2: only uppercase keywords are keywords, others
simply belong to the English language.


From nobody Sun Apr  3 14:38:13 2016
Return-Path: <david.black@emc.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 66B6312D646; Sun,  3 Apr 2016 14:38:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.312
X-Spam-Level: 
X-Spam-Status: No, score=-4.312 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=emc.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 Xtt1liHUzoKj; Sun,  3 Apr 2016 14:38:11 -0700 (PDT)
Received: from mailuogwhop.emc.com (mailuogwhop.emc.com [168.159.213.141]) (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 DC81012D5FE; Sun,  3 Apr 2016 14:38:10 -0700 (PDT)
Received: from maildlpprd03.lss.emc.com (maildlpprd03.lss.emc.com [10.253.24.35]) by mailuogwprd03.lss.emc.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.0) with ESMTP id u33Lc70O005347 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sun, 3 Apr 2016 17:38:07 -0400
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd03.lss.emc.com u33Lc70O005347
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=emc.com; s=jan2013; t=1459719488; bh=Utr270PHcC+15W8uDEcsPH3ROr4=; h=From:To:CC:Subject:Date:Message-ID:References:In-Reply-To: Content-Type:Content-Transfer-Encoding:MIME-Version; b=hKk+niErKWgZaLgkcjbxoNBmQkmnr0g5PlB5Q9FBY2NC1k2I0oz2HnBptexu4EZxh mNvCYEtNnxopnLg00HGjZKBqD1+VLA2CAoxCRCe9Qp/9DWLbdL7c1keB7a0yA7uRz6 tWbeNcRXsvL8DjWooePz9ur5Sa2nCf5KGhWPBmuY=
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd03.lss.emc.com u33Lc70O005347
Received: from mailusrhubprd51.lss.emc.com (mailusrhubprd51.lss.emc.com [10.106.48.24]) by maildlpprd03.lss.emc.com (RSA Interceptor); Sun, 3 Apr 2016 17:36:32 -0400
Received: from MXHUB220.corp.emc.com (MXHUB220.corp.emc.com [10.253.68.90]) by mailusrhubprd51.lss.emc.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.0) with ESMTP id u33LbtK4028819 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=FAIL); Sun, 3 Apr 2016 17:37:56 -0400
Received: from MX104CL02.corp.emc.com ([169.254.8.70]) by MXHUB220.corp.emc.com ([10.253.68.90]) with mapi id 14.03.0266.001; Sun, 3 Apr 2016 17:37:55 -0400
From: "Black, David" <david.black@emc.com>
To: Magnus Westerlund <magnus.westerlund@ericsson.com>, Cullen Jennings <fluffy@iii.ca>
Subject: RE: [tsvwg] Last Call: <draft-ietf-tsvwg-rtcweb-qos-15.txt> (DSCP and other packet markings for WebRTC QoS) to Proposed Standard
Thread-Topic: [tsvwg] Last Call: <draft-ietf-tsvwg-rtcweb-qos-15.txt> (DSCP and other packet markings for WebRTC QoS) to Proposed Standard
Thread-Index: AQHRg5nK94t/8iR5sU+B/9y+8LxFIp9nE2eAgADT/gCACkcQgIAGp9UQ
Date: Sun, 3 Apr 2016 21:37:54 +0000
Message-ID: <CE03DB3D7B45C245BCA0D243277949362E92B245@MX104CL02.corp.emc.com>
References: <20160321174750.31944.71903.idtracker@ietfa.amsl.com> <56F26AD3.3010403@ericsson.com> <5BB71158-3530-47A2-9A33-811F65B2F677@iii.ca> <56FBBBC1.5060902@ericsson.com>
In-Reply-To: <56FBBBC1.5060902@ericsson.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.250.47.120]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Sentrion-Hostname: mailusrhubprd51.lss.emc.com
X-RSA-Classifications: public
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/11kb1zNwCWy1wMnQoi8Pqa6kQGY>
Cc: "tsvwg@ietf.org" <tsvwg@ietf.org>, "draft-ietf-tsvwg-rtcweb-qos@ietf.org" <draft-ietf-tsvwg-rtcweb-qos@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "Black, David" <david.black@emc.com>, "tsvwg-chairs@ietf.org" <tsvwg-chairs@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: Sun, 03 Apr 2016 21:38:12 -0000

I see a couple of Magnus's points that appear to need additional text
in the draft:

[1] Flow Type in application-facing browser API:

> >>>> o Flow Type: The browser provides this input as it knows if
> >>>> the flow is audio, interactive video with or without audio,
> >>>> non-interactive video with or without audio, or data.

[... snip ...]

> The main issue here is that to me it was not clear that "Interactive
> Video with or without audio" allows for setting these DSCP values also
> for the RTP stream containing audio also. This, I do see a need for
> clarification on.

Propose an additional sentence:
OLD
   o  Flow Type: The browser provides this input as it knows if the flow
      is audio, interactive video with or without audio, non-interactive
      video with or without audio, or data.
NEW
   o  Flow Type: The browser provides this input as it knows if the flow
      is audio, interactive video with or without audio, non-interactive
      video with or without audio, or data.  For audio that is associated
      with a video flow, the flow type of the associated video MAY
      be used instead of the associated audio type.

I hesitate to say anything stronger than "MAY" here.

[2] What does "interactive" mean in an implementation?:

> The issue is that this document is called: DSCP and other packet
> markings for WebRTC QoS. Then this document define something that is not
> immediately mappable onto what is being defined in the other WebRTC
> specifications. That is why I am raising that there need to be more
> clear coupling. If that coupling is to mostly happen in another
> document, can we at least then have a proposal on the table for that
> change to ensure that the result is understandable.

Well, this TSVWG draft is definitely not the right place for a discussion o=
f
when a video flow is interactive or non-interactive - I hope we can agree
on that.

Beyond that, as Cullen (Jennings) is both an author of this document and
one of the chairs of the rtcweb WG, I'd suggest that he and/or the rtcweb
WG propose an appropriate location for discussion of when a video flow
is interactive or non-interactive.  This TSVWG draft would then have an
additional sentence added, e.g.,

	See [TBD] for further discussion of how to determine
	whether a video flow is interactive vs. non-interactive.

I believe that the added reference here ([TBD] above) would be normative.

Cullen?

Thanks, --David (as document  shepherd)

> -----Original Message-----
> From: Magnus Westerlund [mailto:magnus.westerlund@ericsson.com]
> Sent: Wednesday, March 30, 2016 7:43 AM
> To: Cullen Jennings
> Cc: ietf@ietf.org; tsvwg-chairs@ietf.org; draft-ietf-tsvwg-rtcweb-qos@iet=
f.org;
> tsvwg@ietf.org
> Subject: Re: [tsvwg] Last Call: <draft-ietf-tsvwg-rtcweb-qos-15.txt> (DSC=
P and
> other packet markings for WebRTC QoS) to Proposed Standard
>=20
> Den 2016-03-23 kl. 23:46, skrev Cullen Jennings:
> >
> >> On Mar 23, 2016, at 3:07 AM, Magnus Westerlund
> >> <magnus.westerlund@ericsson.com> wrote:
> >>
> >> Hi,
> >>
> >> Below is the first round on a question, that looks like it needs to
> >> be addressed, thus I bring it into a public discussion.
> >>
> >> Den 2016-03-22 kl. 19:48, skrev Paul E. Jones:
> >>>> The other comment I have is the following:
> >>>>
> >>>> o Flow Type: The browser provides this input as it knows if
> >>>> the flow is audio, interactive video with or without audio,
> >>>> non-interactive video with or without audio, or data.
> >>>>
> >>>> Yes, a browser knows if a MediaStreamTrack's source is a live
> >>>> source, i.e. camera or microphone or a file. Which would
> >>>> indicate the difference between interactive or non. However, I
> >>>> don't understand what the Flow Type description for video
> >>>> contains "with or without audio" as the flow definitions in
> >>>> RTCWEB transport document all indicate flows as containing a
> >>>> single media type. Can you please clarify?
> >>>
> >>> This relates to the table that follows. The intent is that if a
> >>> WebRTC application is sending audio and video (e.g., a
> >>> videoconference call), then the same DSCP values might be used
> >>> for both the audio and video flows. On the other hand, if only a
> >>> video flow is sent alone (perhaps the audio source is an entirely
> >>> different device), then the browser can still use the same packet
> >>> marking.
> >>>
> >>
> >> So, I started commenting on this because, the "Flow Types" in the
> >> table are not really defined. And my interpretation was not that
> >> the audio could be given the same markings as the Video. I only
> >> interpreted it as being valid for the video flow. Thus, I think the
> >> actual "flow type" values in Table 1 needs to be better defined. To
> >> my knowledge these types are not defined in any other RTCWeb
> >> document.
> >
> > Which codec it came from make is pretty clear if it is audio or video
> > in the browser implementation. The word "flow"  has many meanings in
> > all the different contexts but it seems like section 4 is pretty
> > clear on breaking flow down into media and data types then breaking
> > media down into the various types in the table and defining them.
> >
> > Are you getting at the issue of it a audio stream that is with a
> > synchronized video stream can use the same markings as the video
> > stream ? This tries to leave the options open and let people read
> > things like  Section 4 of RFC 7657.
>=20
> The main issue here is that to me it was not clear that "Interactive
> Video with or without audio" allows for setting these DSCP values also
> for the RTP stream containing audio also. This, I do see a need for
> clarification on.
>=20
> The Interactive vs Non-Interactive I do have an interpretation of what
> it means. However, I fail to see how a WebRTC browser implementation is
> going to be able to make that determination, and there are no API point
> for indicating this distinction for the moment. But, I am fine to let
> that through.
>=20
> >>
> >> I think what is needed is a definition list for what is meant. I
> >> can see that pointers for example into RFC 4594 may help making
> >> these definitions more compact.
> >>
> >> One thing that might be a bit tricky is actually the difference
> >> between interactive and non-interactive (streaming) usages of
> >> WebRTC RTP streams. It becomes a question if the WebRTC endpoint
> >> actually accurately can classify these differences.
> >
> > We decided at some point that if the browser is using SRTP, it is
> > assumed to be interactive and the webrtc specs point at using this.
> > If it is streamed over HTTP with something like DASH then it is non
> > interactive and browsers could use the non interactive markings but I
> > don't think any of the streaming media docs have been updated yet to
> > point that out.
>=20
> I agree with that. I also think there could be a potential development
> where one could use video over RTP in a PeerConnection with a tweaked
> configuration, much more delay tolerant that could be used also for
> non-interactive delivery. But, that is just a potential future
> modification or extension.
>=20
> >
> >> Yes, a live media source, like an camera or microphone can on first
> >> order be used for classification as interactive, while a file
> >> source is non-interactive. But even the first, can in the
> >> application context be non-interactive. An example would be an
> >> lecturer application. Relaxing the delay from the lecturer to the
> >> audience is likely fine, especially if one have a "raise hand"
> >> mechanism and only explicitly invites participants to ask
> >> questions. To my knowledge there are no API surface to indicate
> >> these preferences on the MediaStream or MediaStreamTrack level.
> >>
> >> I think this document have a potential valuable difference for the
> >> interactive vs non-interactive, but the rest of the current
> >> solution has difficulties to utilize this difference. From my
> >> perspective I am fine with retaining the difference, but the
> >> definition must be clear so that implementers select the right one.
> >> And likely the non-interactive will not be much utilized until
> >> additional API knobs are created.
> >
> > Agree but I think it is the WebRTC spec that needs to be clear on
> > that, not this draft.
>=20
> The issue is that this document is called: DSCP and other packet
> markings for WebRTC QoS. Then this document define something that is not
> immediately mappable onto what is being defined in the other WebRTC
> specifications. That is why I am raising that there need to be more
> clear coupling. If that coupling is to mostly happen in another
> document, can we at least then have a proposal on the table for that
> change to ensure that the result is understandable.
>=20
> cheers
>=20
> Magnus Westerlund
>=20
> ----------------------------------------------------------------------
> Services, Media and Network features, Ericsson Research EAB/TXM
> ----------------------------------------------------------------------
> Ericsson AB                 | Phone  +46 10 7148287
> F=E4r=F6gatan 6                 | Mobile +46 73 0949079
> SE-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
> ----------------------------------------------------------------------


From nobody Sun Apr  3 15:01:04 2016
Return-Path: <christopher.morrow@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 C2B4312D198 for <ietf@ietfa.amsl.com>; Sun,  3 Apr 2016 15:01:02 -0700 (PDT)
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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 K5k4k7RgaDtW for <ietf@ietfa.amsl.com>; Sun,  3 Apr 2016 15:01:01 -0700 (PDT)
Received: from mail-yw0-x231.google.com (mail-yw0-x231.google.com [IPv6:2607:f8b0:4002: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 57E8A12D156 for <ietf@ietf.org>; Sun,  3 Apr 2016 15:01:01 -0700 (PDT)
Received: by mail-yw0-x231.google.com with SMTP id t10so43628407ywa.0 for <ietf@ietf.org>; Sun, 03 Apr 2016 15:01:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc; bh=XS9EPMD98AlioVs+jrAHhai5TD9PGQR3wZLx6thGTRs=; b=sO+SDJcRSdDt9MUgH+WF6V7D3+dzv1bHn+OQrDYuP+tU6ihR+PSMc7Ef96FjaV+kcb wZUj2s1bgfZUmyMqvD4sB2oo6yjmyyMi47s+S6jQ7G4xY2kD+nPs22C73NrE6dZQKyDF LPIUs8L37prNQT2SkTVNj0Ds+IpTZhZsALkasRk0FhS3GMLyNBnuzmQyhFG2e78YWTs+ rKE9PT4S4/QejKwjsBlBOKQhbFX6DLxmgQiCBTOmtEu9fp4KD6RjH3T36pSfvcQ+NZXr MLPc0Oc+NSA5rs70rg8e7AI6/fmVKWZ+wg0nQlNDvetyCuCRjNsF3M7vLx4UozWrYgew RZXw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:date :message-id:subject:from:to:cc; bh=XS9EPMD98AlioVs+jrAHhai5TD9PGQR3wZLx6thGTRs=; b=T3vkISZPpzx+OLQFr812h+3uBVwgSZc6I+GR6vVUZEizkUEvHi93dU8AdV/3clI6wr J5ZR91pD8NGVA6PRqyFTfLOfQh2DA1l59qZu4wECtYKAXz2tChuJWFfsWBpapqZ9pblL ScaiAGDD7JnZ437g++g0dkQKy1PFEi83deJCqxnJjf+CnwLNII32OzNyubnJw9dUdnYO tmiztdzt6jVpe0Ws+ijf9bDE562qhbDDEqD3AkhUN36vaksplxz35amPmZ25zfThvQPb WdVH0uzvUDCmpxklFUuQtiS7SkCad/FFQPTVf8FgYv5b9Evk4l0Ov8H91mr8lRFd9HmG xCcQ==
X-Gm-Message-State: AD7BkJJFd+fSbuOMhDGCTMb3VxQqOcnSiMuu4X1mJx5MSSCxZnKXS17gug2TjNgkgHsNymciT6qgE/NHr/mR2w==
MIME-Version: 1.0
X-Received: by 10.129.120.23 with SMTP id t23mr18086439ywc.45.1459720860512; Sun, 03 Apr 2016 15:01:00 -0700 (PDT)
Sender: christopher.morrow@gmail.com
Received: by 10.13.209.198 with HTTP; Sun, 3 Apr 2016 15:01:00 -0700 (PDT)
In-Reply-To: <57013C8A.4010704@gmail.com>
References: <57013C8A.4010704@gmail.com>
Date: Sun, 3 Apr 2016 18:01:00 -0400
X-Google-Sender-Auth: cuEFzB5QA_wkvJlYLZ5ppZD9NfU
Message-ID: <CAL9jLaaMjP=7BLxM0Him6cCaxh3mzYDChwpGv6D2dhRthoZC9Q@mail.gmail.com>
Subject: Re: storage space at meeting (wardrobe)?
From: Christopher Morrow <morrowc.lists@gmail.com>
To: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Content-Type: multipart/alternative; boundary=94eb2c0b038c5cb8e3052f9bbfc2
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/FXiT9CoQhQH_BbqXxmx2gdYnd3M>
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: Sun, 03 Apr 2016 22:01:03 -0000

--94eb2c0b038c5cb8e3052f9bbfc2
Content-Type: text/plain; charset=UTF-8

I always thought this was: "Hi bell desk person, I'd like to drop something
off for a few hours, is that ok? Yes, I'm a guest, I am waiting on my ride
to the airport in 7 hrs time.."

On Sun, Apr 3, 2016 at 11:53 AM, Alexandre Petrescu <
alexandre.petrescu@gmail.com> wrote:

> Hi, IETFers in Buenos Aires,
>
> I stay at another hotel, and I think it is good to have storage space at
> the meeting for carry-on items, or a wardrobe for coats.
>
> Hilton provides such but only for guests.  Does Hilton delegate such
> service to IETF?
>
> Such storage space is good for things like:
> - wet coat
> - umbrella
> - scooter
>
> Alex
>
>

--94eb2c0b038c5cb8e3052f9bbfc2
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-size:small">I a=
lways thought this was: &quot;Hi bell desk person, I&#39;d like to drop som=
ething off for a few hours, is that ok? Yes, I&#39;m a guest, I am waiting =
on my ride to the airport in 7 hrs time..&quot;</div></div><div class=3D"gm=
ail_extra"><br><div class=3D"gmail_quote">On Sun, Apr 3, 2016 at 11:53 AM, =
Alexandre Petrescu <span dir=3D"ltr">&lt;<a href=3D"mailto:alexandre.petres=
cu@gmail.com" target=3D"_blank">alexandre.petrescu@gmail.com</a>&gt;</span>=
 wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bor=
der-left:1px #ccc solid;padding-left:1ex">
 =20

   =20
 =20
  <div text=3D"#000000" bgcolor=3D"#FFFFFF">
    <font face=3D"Courier New">Hi, IETFers in Buenos Aires,<br>
      <br>
      I stay at another hotel, and I think it is good to have storage
      space at the meeting for carry-on items, or a wardrobe for coats.<br>
      <br>
      Hilton provides such but only for guests.=C2=A0 Does Hilton delegate
      such service to IETF?<br>
      <br>
      Such storage space is good for things like:<br>
      - wet coat<br>
      - umbrella<br>
      - scooter<br>
      <br>
      Alex<br>
      <br>
    </font>
  </div>

</blockquote></div><br></div>

--94eb2c0b038c5cb8e3052f9bbfc2--


From nobody Sun Apr  3 15:25:17 2016
Return-Path: <aallen@blackberry.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 54B1C12D65C for <ietf@ietfa.amsl.com>; Sun,  3 Apr 2016 15:25:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.63
X-Spam-Level: 
X-Spam-Status: No, score=-2.63 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 v6thwZsjBN6X for <ietf@ietfa.amsl.com>; Sun,  3 Apr 2016 15:25:04 -0700 (PDT)
Received: from smtp-p01.blackberry.com (smtp-p01.blackberry.com [208.65.78.88]) by ietfa.amsl.com (Postfix) with ESMTP id 74B7312D658 for <ietf@ietf.org>; Sun,  3 Apr 2016 15:25:04 -0700 (PDT)
Received: from xct102cnc.rim.net ([10.65.161.202]) by mhs212cnc.rim.net with ESMTP/TLS/AES256-SHA; 03 Apr 2016 19:56:22 -0400
Received: from XCT116CNC.rim.net (10.65.161.216) by XCT102CNC.rim.net (10.65.161.202) with Microsoft SMTP Server (TLS) id 14.3.210.2; Sun, 3 Apr 2016 18:25:03 -0400
Received: from XMB122CNC.rim.net ([fe80::28c6:fa1c:91c6:2e23]) by XCT116CNC.rim.net ([::1]) with mapi id 14.03.0210.002; Sun, 3 Apr 2016 18:25:02 -0400
From: Andrew Allen <aallen@blackberry.com>
To: Christopher Morrow <morrowc.lists@gmail.com>, Alexandre Petrescu <alexandre.petrescu@gmail.com>
Subject: Re: storage space at meeting (wardrobe)?
Thread-Topic: storage space at meeting (wardrobe)?
Thread-Index: AQHRjcErSHdHEG4wV0GZdFQMfOQPjp95ECgA///DqgE=
Date: Sun, 3 Apr 2016 22:25:02 +0000
Message-ID: <20160403222454.6283348.40594.9269@blackberry.com>
References: <57013C8A.4010704@gmail.com>, <CAL9jLaaMjP=7BLxM0Him6cCaxh3mzYDChwpGv6D2dhRthoZC9Q@mail.gmail.com>
In-Reply-To: <CAL9jLaaMjP=7BLxM0Him6cCaxh3mzYDChwpGv6D2dhRthoZC9Q@mail.gmail.com>
Accept-Language: en-CA, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: multipart/alternative; boundary="_000_201604032224546283348405949269blackberrycom_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/XWe213d4PSzHqUiTli1bm3OwG1A>
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: Sun, 03 Apr 2016 22:25:09 -0000

--_000_201604032224546283348405949269blackberrycom_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Since meeting block was so limited that seems a reasonable request.

Sent from my BlackBerry 10 smartphone.
From: Christopher Morrow
Sent: Sunday, April 3, 2016 19:01
To: Alexandre Petrescu
Cc: IETF Discussion
Subject: Re: storage space at meeting (wardrobe)?


I always thought this was: "Hi bell desk person, I'd like to drop something=
 off for a few hours, is that ok? Yes, I'm a guest, I am waiting on my ride=
 to the airport in 7 hrs time.."

On Sun, Apr 3, 2016 at 11:53 AM, Alexandre Petrescu <alexandre.petrescu@gma=
il.com<mailto:alexandre.petrescu@gmail.com>> wrote:
Hi, IETFers in Buenos Aires,

I stay at another hotel, and I think it is good to have storage space at th=
e meeting for carry-on items, or a wardrobe for coats.

Hilton provides such but only for guests.  Does Hilton delegate such servic=
e to IETF?

Such storage space is good for things like:
- wet coat
- umbrella
- scooter

Alex



--_000_201604032224546283348405949269blackberrycom_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
</head>
<body>
<div style=3D"width:100%; font-size:initial; font-family:Calibri,'Slate Pro=
',sans-serif,sans-serif; color:rgb(31,73,125); text-align:initial; backgrou=
nd-color:rgb(255,255,255)">
Since meeting block was so limited that seems a reasonable request.</div>
<div style=3D"width:100%; font-size:initial; font-family:Calibri,'Slate Pro=
',sans-serif,sans-serif; color:rgb(31,73,125); text-align:initial; backgrou=
nd-color:rgb(255,255,255)">
<br style=3D"display:initial">
</div>
<div style=3D"font-size:initial; font-family:Calibri,'Slate Pro',sans-serif=
,sans-serif; color:rgb(31,73,125); text-align:initial; background-color:rgb=
(255,255,255)">
Sent&nbsp;from&nbsp;my&nbsp;BlackBerry&nbsp;10&nbsp;smartphone.</div>
<table width=3D"100%" style=3D"background-color:white; border-spacing:0px">
<tbody>
<tr>
<td colspan=3D"2" style=3D"font-size:initial; text-align:initial; backgroun=
d-color:rgb(255,255,255)">
<div style=3D"border-style:solid none none; border-top-color:rgb(181,196,22=
3); border-top-width:1pt; padding:3pt 0in 0in; font-family:Tahoma,'BB Alpha=
 Sans','Slate Pro'; font-size:10pt">
<div><b>From: </b>Christopher Morrow</div>
<div><b>Sent: </b>Sunday, April 3, 2016 19:01</div>
<div><b>To: </b>Alexandre Petrescu</div>
<div><b>Cc: </b>IETF Discussion</div>
<div><b>Subject: </b>Re: storage space at meeting (wardrobe)?</div>
</div>
</td>
</tr>
</tbody>
</table>
<div style=3D"border-style:solid none none; border-top-color:rgb(186,188,20=
9); border-top-width:1pt; font-size:initial; text-align:initial; background=
-color:rgb(255,255,255)">
</div>
<br>
<div>
<div dir=3D"ltr">
<div class=3D"gmail_default" style=3D"font-size:small">I always thought thi=
s was: &quot;Hi bell desk person, I'd like to drop something off for a few =
hours, is that ok? Yes, I'm a guest, I am waiting on my ride to the airport=
 in 7 hrs time..&quot;</div>
</div>
<div class=3D"gmail_extra"><br>
<div class=3D"gmail_quote">On Sun, Apr 3, 2016 at 11:53 AM, Alexandre Petre=
scu <span dir=3D"ltr">
&lt;<a href=3D"mailto:alexandre.petrescu@gmail.com" target=3D"_blank">alexa=
ndre.petrescu@gmail.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex; border-left:1=
px #ccc solid; padding-left:1ex">
<div bgcolor=3D"#FFFFFF"><font face=3D"Courier New">Hi, IETFers in Buenos A=
ires,<br>
<br>
I stay at another hotel, and I think it is good to have storage space at th=
e meeting for carry-on items, or a wardrobe for coats.<br>
<br>
Hilton provides such but only for guests.&nbsp; Does Hilton delegate such s=
ervice to IETF?<br>
<br>
Such storage space is good for things like:<br>
- wet coat<br>
- umbrella<br>
- scooter<br>
<br>
Alex<br>
<br>
</font></div>
</blockquote>
</div>
<br>
</div>
</div>
</body>
</html>

--_000_201604032224546283348405949269blackberrycom_--


From nobody Sun Apr  3 21:26:37 2016
Return-Path: <lists@digitaldissidents.org>
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 B61E312D196 for <ietf@ietfa.amsl.com>; Sun,  3 Apr 2016 21:26:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] 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 lr3CZiqzVvhl for <ietf@ietfa.amsl.com>; Sun,  3 Apr 2016 21:26:33 -0700 (PDT)
Received: from smarthost1.greenhost.nl (smarthost1.greenhost.nl [195.190.28.81]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9594112D0CF for <ietf@ietf.org>; Sun,  3 Apr 2016 21:26:33 -0700 (PDT)
Received: from smtp.greenhost.nl ([213.108.104.138]) by smarthost1.greenhost.nl with esmtps (TLS1.0:DHE_RSA_AES_128_CBC_SHA1:16) (Exim 4.72) (envelope-from <lists@digitaldissidents.org>) id 1amw5v-0001xL-9z for ietf@ietf.org; Mon, 04 Apr 2016 06:26:31 +0200
Subject: Re: RFC 7776 and the team that can be reached for help regarding harassment concerns
To: ietf@ietf.org
References: <16A28658-0ADD-43BD-832A-2BD37D921653@ietf.org> <31DF410E-615B-4F9F-B814-4ED35D9A773E@edvina.net>
From: Niels ten Oever <lists@digitaldissidents.org>
Message-ID: <5701ECEB.9080205@digitaldissidents.org>
Date: Mon, 4 Apr 2016 06:26:19 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Icedove/38.7.0
MIME-Version: 1.0
In-Reply-To: <31DF410E-615B-4F9F-B814-4ED35D9A773E@edvina.net>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 8bit
X-Authenticated-As-Hash: 29cc722430e8f1f6ed904119444c0d49b0f3ee91
X-Virus-Scanned: by clamav at smarthost1.samage.net
X-Scan-Signature: 919fae14bc17c74543a025539baad412
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/WBwQmhlu9WdtANF7K9eqNMr174Y>
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: Mon, 04 Apr 2016 04:26:35 -0000

+100

On 04/02/2016 08:24 AM, Olle E. Johansson wrote:
> 
>> On 01 Apr 2016, at 18:52, IETF Chair <chair@ietf.org> wrote:
>>
>>
>> In 2013, the IESG set the IETF anti-harassment policy. Last year, we concluded the process to write a BCP that defines the anti-harassment procedures. That BCP has now been published as RFC 7776. The RFC specifies that there shall be a specialist team that can be reached for help, advice, and possible actions regarding harassment concerns.
>>
>> I’m happy to announce that Allison Mankin, Pete Resnick, and Linda Klieforth have accepted to become the initial members in this team. They are preparing for this role, working on their operating practices as defined by the RFC, and we are setting up additional training for them. I am though happy to have them serving in this role, given that they have a lot of experience. Allison and Pete of course have a long experience about the IETF culture, topics, and leadership roles. In addition, Pete has volunteer experience from violence and discrimination related tasks. Linda Klieforth has been the acting ombudsperson for the IETF since 2013, and is the head of HR at ISOC. And Allison has a lot of experience about the way IETF selects leadership.
>>
>> Please welcome Linda, Allison, and Pete to this role. Feel free to contact them if you have any concerns, they are a very easy set of people to talk to, they will be here in Buenos Aires, and obviously everything you tell them will be kept in confidence as requested, as defined in the RFC.
>>
> It makes me proud that the IETF has done this. It’s a big step forward and hopefully sets the standard for other groups. 
> 
> A big thank you to everyone involved!
> 
> /Olle
> 

-- 
Niels ten Oever
Head of Digital

Article 19
www.article19.org

PGP fingerprint    8D9F C567 BEE4 A431 56C4
                   678B 08B5 A0F2 636D 68E9


From nobody Sun Apr  3 21:55:59 2016
Return-Path: <brian.e.carpenter@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 9845512D10A for <ietf@ietfa.amsl.com>; Sun,  3 Apr 2016 21:55:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 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, RCVD_IN_DNSWL_LOW=-0.7, 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 h4E8gYcULH1F for <ietf@ietfa.amsl.com>; Sun,  3 Apr 2016 21:55:56 -0700 (PDT)
Received: from mail-pf0-x22f.google.com (mail-pf0-x22f.google.com [IPv6:2607:f8b0:400e:c00::22f]) (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 C100512D0F9 for <ietf@ietf.org>; Sun,  3 Apr 2016 21:55:56 -0700 (PDT)
Received: by mail-pf0-x22f.google.com with SMTP id e128so114166505pfe.3 for <ietf@ietf.org>; Sun, 03 Apr 2016 21:55:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=subject:to:references:cc:from:organization:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=1TEa3H+rvfEAYnzNXlQh5SU7eTv+1KfdkngxyUcpLlE=; b=hg2XWQ557eVFJFv0Med+2LVmgvl+S258sQ1m7hrDexFXxkEAL1vfYq8L6CgXMWIkAQ 4KmOrO/KjjYtjtmOp1rqYyVayZFPb6AAuPMP95BLE8CVYaPgAUQwGiNlnhP9P2VyZ0mD PBVa38hnZHkdztyp9PF4rbIvRHXxVLNIEdQoIbMP8HX6g8IHl4r+viMg6v6J603ngP64 yboVjT7cKvAQctCtMoQdSXYAjxfj9J1hYC1a7QlObG05SxaMCsEkXq4p6ozxHZqEwE+t KF+YSbmA/TZ8VFesUiwBbFUZBOBaWdZwiX2/zbPjuhT9DPoGLv4Vc6wcgRtC4bMTKyGi R7xg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:cc:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=1TEa3H+rvfEAYnzNXlQh5SU7eTv+1KfdkngxyUcpLlE=; b=MGWENNApO9b6x0N/UpkWP3+S9Jq8rMdsTLzEgvGksezg44lDPv42OujxV/X/+x7xF4 Rd5GbQ1llHP8ip67mCbbfhFk60qKnPqVUcnlF4M1sBFjflThD83Mxd9svJXwJR1DO0os zNLPKWozcd/wRw9InnfLhjgck8G68uxfsBq1MV4Q4NWrKe6/cY4OwtrvarSgmu5+iRja X8hrAWFGWn4E8QkDWxg9CC1kHmzbASm5w89dTg6C/wZml1/KyyanidPL7unyVSEK05uV jCx9RhMJdJYo3mf6iqqLws33B8XXpCDY/rJ//b6kgwhoQQQVIe7kd+8wRabvcVRDUSsy 1ioA==
X-Gm-Message-State: AD7BkJI3lQCZ7Z7Z3obuc5VlDZ8uN1Yu8lIlfEgePmaQUi+5Nhe1Xg0V5dLvX05UPwP7UQ==
X-Received: by 10.98.72.83 with SMTP id v80mr17760276pfa.113.1459745756333; Sun, 03 Apr 2016 21:55:56 -0700 (PDT)
Received: from ?IPv6:2406:e007:483d:1:28cc:dc4c:9703:6781? ([2406:e007:483d:1:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id 27sm35690217pfo.58.2016.04.03.21.55.52 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 03 Apr 2016 21:55:54 -0700 (PDT)
Subject: Re: Last Call on draft-bradner-rfc3979bis-08.txt ("Intellectual Property Rights in IETF Technology")
To: Stephan Wenger <stewe@stewe.org>, Alissa Cooper <alissa@cooperw.in>, Jari Arkko <jari.arkko@piuha.net>
References: <0000431F-F977-4A24-BA4D-064F740977A0@piuha.net> <7A6961E0-CCA6-4D1D-878A-176004AE2BAE@cooperw.in> <57006AF2.7020400@gmail.com> <4DC1ED89-32FB-4B73-8922-C24713AEEC21@stewe.org>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <5701F3D7.5090107@gmail.com>
Date: Mon, 4 Apr 2016 16:55:51 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.7.0
MIME-Version: 1.0
In-Reply-To: <4DC1ED89-32FB-4B73-8922-C24713AEEC21@stewe.org>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/HcGApPP60gqW1vfkyhFDdsSMBEU>
Cc: IETF <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: Mon, 04 Apr 2016 04:55:58 -0000

On 04/04/2016 02:33, Stephan Wenger wrote:
> Hi,
>=20
>=20
>=20
> On 4/2/16, 21:59, "ietf on behalf of Brian E Carpenter" <ietf-bounces@i=
etf.org on behalf of brian.e.carpenter@gmail.com> wrote:
>=20
>> Alissa,
>> On 01/04/2016 11:38, Alissa Cooper wrote:
>> ...
>>> 1) I agree with other commenters' concerns about the definition of "p=
articipating" with respect to WG chairs and ADs. In particular in the con=
text of section 6, this seems like it could limit the pool of people who =
can stand for AD roles, because you're not allowed to participate in case=
s where you won't be able to disclose, but you have no idea a priori what=
 WGs will get chartered in your area and what work items they might take =
up.
>>
>> I don't see what's new about this - it's always been an awkward point.=
 I worked for
>> a major patent-generating company while I was in the IESG ten years ag=
o, and I had
>> to pay attention to this. I'm not saying it isn't a problem, but I don=
't see that
>> tightening up the language really makes the problem any worse. (Howeve=
r, I still
>> don't see any need to state the obvious, i.e. that WG Chairs and ADs a=
re
>> participants, unless they recuse themselves on a particular matter.)
>=20
> My feeling is that a WG chair absolutely should be in the loop of every=
thing going on in its WG, and therefore should be viewed as =E2=80=9Cpart=
icipating=E2=80=9D with respect to any Contribution made to the WG or rel=
ated to the WG.
>=20
> With respect to ADs, I find Brian=E2=80=99s argument generally compelli=
ng.  However, I don=E2=80=99t know how an AD can or should recuse himself=
/herself from a particular matter in the sense of shedding his/her possib=
le obligations under BCP79.  AFAICT, historically, when an AD recuses him=
self/herself, it was often based on too much knowledge and interest in a =
certain technology, with respect to personnel behind the technology, and =
so on.  In such a case, a recuse from IPR obligations of any type would n=
ot be desirable.

Agreed, but an AD might have no choice but to abstain "for cause" if s/he=
 is caught
between the IETF rules and an employer rule that patent applications are =
not published.
If we don't accept that reality, we would be reducing our volunteer pool =
even more.

   Brian

> The more we relax the disclosure requirements, the more we enable gamin=
g the policy by a =E2=80=9Ccompany man=E2=80=9D--and that form of gaming
may not come up until years after the person has resigned from the AD pos=
ition, rendering the IETF=E2=80=99s internal sanction mechanism
inefficient.
>=20
> Stephan
>=20
>>
>>    Brian
>>


From nobody Mon Apr  4 05:42:10 2016
Return-Path: <lars@netapp.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 E085A12D520 for <ietf@ietfa.amsl.com>; Mon,  4 Apr 2016 05:42:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.931
X-Spam-Level: 
X-Spam-Status: No, score=-6.931 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 rkG-dKXW5kz5 for <ietf@ietfa.amsl.com>; Mon,  4 Apr 2016 05:42:06 -0700 (PDT)
Received: from mx141.netapp.com (mx141.netapp.com [216.240.21.12]) (using TLSv1.2 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BC09012D5CA for <ietf@ietf.org>; Mon,  4 Apr 2016 05:42:06 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="5.24,440,1455004800";  d="asc'?scan'208";a="110366566"
Received: from hioexcmbx03-prd.hq.netapp.com ([10.122.105.36]) by mx141-out.netapp.com with ESMTP; 04 Apr 2016 05:37:05 -0700
Received: from HIOEXCMBX07-PRD.hq.netapp.com (10.122.105.40) by hioexcmbx03-prd.hq.netapp.com (10.122.105.36) with Microsoft SMTP Server (TLS) id 15.0.1156.6; Mon, 4 Apr 2016 05:37:05 -0700
Received: from HIOEXCMBX07-PRD.hq.netapp.com ([::1]) by hioexcmbx07-prd.hq.netapp.com ([fe80::c07c:8fcd:f7e4:f32b%21]) with mapi id 15.00.1156.000; Mon, 4 Apr 2016 05:37:05 -0700
From: "Eggert, Lars" <lars@netapp.com>
To: Jari Arkko <jari.arkko@piuha.net>
Subject: Re: Last Call on draft-bradner-rfc3979bis-08.txt ("Intellectual Property Rights in IETF Technology")
Thread-Topic: Last Call on draft-bradner-rfc3979bis-08.txt ("Intellectual Property Rights in IETF Technology")
Thread-Index: AQHRhDTaY75yXT30okCzmxElqsDSFp96SlCA
Date: Mon, 4 Apr 2016 12:37:04 +0000
Message-ID: <4A755FC7-6E3F-4787-B5B1-464F29D675FD@netapp.com>
References: <0000431F-F977-4A24-BA4D-064F740977A0@piuha.net>
In-Reply-To: <0000431F-F977-4A24-BA4D-064F740977A0@piuha.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-mailer: Apple Mail (2.3124)
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.120.60.35]
Content-Type: multipart/signed; boundary="Apple-Mail=_72E2329F-0DE9-452A-B19D-6AEC8AAC1D13"; protocol="application/pgp-signature"; micalg=pgp-sha256
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/N6gb93K_pn8j5oT38xZWd4BEcIQ>
Cc: IETF <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: Mon, 04 Apr 2016 12:42:09 -0000

--Apple-Mail=_72E2329F-0DE9-452A-B19D-6AEC8AAC1D13
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252

Hi,

I mostly ready this from the perspective of the IRTF, since this is =
intended to also apply to us. I found that that wasn't terribly clear =
from the current text.

Lars

Section 1., paragraph 0:
> 1. Definitions

  Sorting these definitions alphabetically is not really helpful to the
  reader. Could you order them such that terms are defined before being
  referred to, or at least try?


Section 1., paragraph 3:
>    b. "Contribution": any submission to the IETF intended by the
>       Contributor for publication as all or part of an Internet-Draft =
or
>       RFC and any statement made within the context of an IETF =
activity,
>       in each case that is intended to affect the IETF Standards =
Process
>       or that is related to the activity of an Alternate Stream that =
has
>       adopted this definition.

 What do you mean by "this definition"? Also, it's not clear what
 "activity of an Alternate Stream" is supposed to convey. I think this
 intends to capture work occurring in IRTF RGs, but it's a pretty
 indirect way of stating this.


Section 1., paragraph 4:
>       Such statements include oral statements, as well as written and
>       electronic communications, which are addressed to:

  The list below does not include IRTF mailing lists or meetings.


Section 1., paragraph 9:
>    e. "IETF": In the context of this document, the IETF includes all
>       individuals who participate in meetings, working groups, mailing
>       lists, functions and other activities which are organized or
>       initiated by ISOC, the IESG or the IAB under the general
>       designation of the Internet Engineering Task Force or IETF, but
>       solely to the extent of such participation.

  For clarity, I would also call out the IRTF and its RGs here.


Section 1., paragraph 10:

>    f. "IETF Documents": RFCs and Internet-Drafts that are published as
>       part of the IETF Standards Process.  These are also referred to =
as
>       "IETF Stream Documents" as defined in Section 5.1.1 of RFC 4844.

  What about RFCs and Internet-Drafts that are intended as contributions
  to IRTF activities? It would be useful to maybe add "...part of the
  IETF Standards Process and related activities" to make this clearer.


Section 1., paragraph 11:
>    g. "IETF Standards Process": the activities undertaken by the IETF =
in
>       any of the settings described in the above definition of
>       Contribution.  The IETF Standards Process may include
>       participation in activities and publication of documents that =
are
>       not directed toward the development of IETF standards or
>       specifications, such as the development and publication of
>       informational documents.

  I'd again explicitly call out the alternate streams here. And maybe
  this document is meant for lawyers and I am not one, but having a
  definition called "IETF Standards Process" that also includes all of
  our non-standard-setting activities is confusing.


Section 1., paragraph 17:
>    m. "RFC": the basic publication series for the IETF.  RFCs are
>       published by the RFC Editor and once published are never =
modified.
>       (See [RFC2026] Section 2.1)

  Might want to mention the existence of errata.


Section 5.5., paragraph 0:
> 5.5. Licensing Information in an IPR Disclosure

  It's been running code on the IRTF side to be very OK with not having
  license terms included, esp. if it significantly delays the official
  filing of the disclosure, since RGs don't set standards and therefore
  don't really need to consider licensing terms. Not clear if that
  should be discussed here.


Section 11., paragraph 2:
>    The legal rules that apply to documents in Alternate Streams are
>    established by the managers of those Alternate Streams as defined =
in
>    [RFC 4844]. (i.e., the Internet Architecture Board (IAB), Internet
>    Research Steering Group (IRSG) and Independent Submission Editor).

  Is the IRSG really the manager of the IRTF stream? I thought it was
  the IRTF chair, but I can't find the definitive answer in either 4844,
  5742 or 5743...



--Apple-Mail=_72E2329F-0DE9-452A-B19D-6AEC8AAC1D13
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="signature.asc"
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----

iQIcBAEBCAAGBQJXAl/wAAoJEFS1wwm/cMFXbs8P/jXZnzsjaD2bdVJd3kjQ4uqo
F53ypWXBS8+reOExncuqax+IUf0Wl3g671A18OayyqvivoZdFTc8ma0Dxrno16iR
kb4C1hfOyntnP6MSVRO7tvWYxTNAUnhqBxyPbZf3AfYonWTIC30HDUavbg4Z4SxR
0/2UPwCt2wSeRt7q2UJ8yhtAZ/oCMNdjAXWWBN0uoPRca4mvWU52RxHIOhuh5uW+
AyHo/ObOL0qEI7Nm3yKZQTKhFrm04hJRBmTltyU9pZ/88dGLmwF/VpWvdmudJcYV
zR2mpGVa+L0ZqccxRfTf8x9SiHjUSEzffkWKdT+OAdn6Y1Gy/xPtMvQCuE2ddvbE
PyjvLYzpz4CHo09IXy/OekyjwrEhufiR/H/QZbakyRGTc8Vtz7sITo0oxL83oX7V
AuRuix58SsyTcy36tK0QGDeuBaIij/J+5RVhoZ4aM8KZ/4qwVpIkjfGvmKwyorUC
/0z4t+cGm3c2FxJwwaiABKVyP57F8Ekrqd/CadtMp+7NHe6HgFj7SDzYU2mCwQyz
6KRQ4wfKU8n1I+F2KnYwkJ5OzlOHJ54WHUuPIl/JbiHxcv6BqTB1v/Zh3Nwme5ow
9ncTV8hM9ZrgndVZIoyREWcAQjBQHyRC5YUlNNDkVsQhnzHIF3fCzsAvdSCi+jSJ
pMPJ6YeZYS5LyBBBc04s
=Rg62
-----END PGP SIGNATURE-----

--Apple-Mail=_72E2329F-0DE9-452A-B19D-6AEC8AAC1D13--


From nobody Mon Apr  4 06:14:24 2016
Return-Path: <stewe@stewe.org>
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 5597912D1E5 for <ietf@ietfa.amsl.com>; Mon,  4 Apr 2016 06:14:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.903
X-Spam-Level: 
X-Spam-Status: No, score=-1.903 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] 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 hUTYHeEwHZVM for <ietf@ietfa.amsl.com>; Mon,  4 Apr 2016 06:14:15 -0700 (PDT)
Received: from na01-bl2-obe.outbound.protection.outlook.com (mail-bl2on0141.outbound.protection.outlook.com [65.55.169.141]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AD5FF12D0CA for <ietf@ietf.org>; Mon,  4 Apr 2016 06:14:14 -0700 (PDT)
Received: from BLUPR17MB0275.namprd17.prod.outlook.com (10.162.235.146) by BLUPR17MB0274.namprd17.prod.outlook.com (10.162.235.145) with Microsoft SMTP Server (TLS) id 15.1.447.15; Mon, 4 Apr 2016 13:14:12 +0000
Received: from BLUPR17MB0275.namprd17.prod.outlook.com ([10.162.235.146]) by BLUPR17MB0275.namprd17.prod.outlook.com ([10.162.235.146]) with mapi id 15.01.0447.027; Mon, 4 Apr 2016 13:14:12 +0000
From: Stephan Wenger <stewe@stewe.org>
To: "Eggert, Lars" <lars@netapp.com>, Jari Arkko <jari.arkko@piuha.net>
Subject: Re: Last Call on draft-bradner-rfc3979bis-08.txt ("Intellectual Property Rights in IETF Technology")
Thread-Topic: Last Call on draft-bradner-rfc3979bis-08.txt ("Intellectual Property Rights in IETF Technology")
Thread-Index: AQHRhDTbKR9yu1RueEWA9RrAiHSISp951PgA///YEwA=
Date: Mon, 4 Apr 2016 13:14:11 +0000
Message-ID: <9EC16EBD-78D2-414B-8169-AFEB76FC8960@stewe.org>
References: <0000431F-F977-4A24-BA4D-064F740977A0@piuha.net> <4A755FC7-6E3F-4787-B5B1-464F29D675FD@netapp.com>
In-Reply-To: <4A755FC7-6E3F-4787-B5B1-464F29D675FD@netapp.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: netapp.com; dkim=none (message not signed) header.d=none;netapp.com; dmarc=none action=none header.from=stewe.org;
x-ms-exchange-messagesentrepresentingtype: 1
x-originating-ip: [2001:67c:370:176:ac9a:9cf5:6d8b:e22c]
x-ms-office365-filtering-correlation-id: 57592136-7626-4834-6556-08d35c8b03ae
x-microsoft-exchange-diagnostics: 1; BLUPR17MB0274; 5:/aQHQeDedQZBzTvS72OYXUew/D9jvw1v4s0BA5qnTtauf7+I31D0IAVlx/Tb+wlyPkCHjNbXyGz+voo/rSUGC2EG+J4Qb+C67xoLcpDqYehv6huo+txHumxWMN4zkCnO7VseECcgOUEs6H8xBGSZ8Q==; 24:w7mVqbzr6mMvo+KRuQG2Qhh8Qxepfxhvt7BRkJuAkxj0GqJ5Q9K7k7JEZnhA2YXH2YbZE1t2sL08z/T78zsM6XmR/Agx1O6ZL/CZbCGII2o=
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:BLUPR17MB0274;
x-microsoft-antispam-prvs: <BLUPR17MB0274AD21480562E8F53DD444AE9D0@BLUPR17MB0274.namprd17.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040046)(601004)(2401047)(5005006)(8121501046)(10201501046)(3002001)(6041046)(6043046); SRVR:BLUPR17MB0274; BCL:0; PCL:0; RULEID:; SRVR:BLUPR17MB0274; 
x-forefront-prvs: 0902222726
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(24454002)(5004730100002)(82746002)(33656002)(5001770100001)(19580405001)(19580395003)(83716003)(3660700001)(106116001)(86362001)(230783001)(5002640100001)(122556002)(189998001)(36756003)(2900100001)(76176999)(2950100001)(54356999)(4326007)(50986999)(2906002)(3280700002)(5008740100001)(10400500002)(81166005)(92566002)(1096002)(11100500001)(6116002)(77096005)(102836003)(586003)(87936001)(1220700001)(3826002)(42262002)(104396002); DIR:OUT; SFP:1102; SCL:1; SRVR:BLUPR17MB0274; H:BLUPR17MB0275.namprd17.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en; 
spamdiagnosticoutput: 1:23
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
Content-ID: <225C9A0E01CA8C4D90B1E99158D2AC27@namprd17.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: stewe.org
X-MS-Exchange-CrossTenant-originalarrivaltime: 04 Apr 2016 13:14:11.8685 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 865fc51c-5fae-4322-98ef-0121a85df0b6
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BLUPR17MB0274
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/6blsHypDavOYITkY7VvMLu_lPTg>
Cc: IETF <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: Mon, 04 Apr 2016 13:14:22 -0000

SGkgTGFycywNClJlYWRpbmcgdHJvdWdoIHRoaXMsIEkgdGhpbmsgaXQgbWF5IGJlIHdvcnRod2hp
bGUgdGhhdCB0aGUgSVJURiBjcmVhdGVzIGFuIFJGQyB0aGF0IGluY2x1ZGVzIGFuIGFwcGxpY2Fi
aWxpdHkgc3RhdGVtZW50IG9mIEJDUDc5IHRvIElSVEYgYWN0aXZpdGllcywgaW5zdGVhZCBvZiB0
cnlpbmcgdG8gaW5jbHVkZSB0aGUgSVJTRyBhbmQgaXRzIHRlcm1pbm9sb2d5IGludG8gdGhpcyBh
bHJlYWR5IGNvbmZ1c2luZyBkb2N1bWVudC4NCihtaW5vciBwb2ludDogSSBwcmVmZXIgdG8ga2Vl
cCB0aGUgZGVmaW5pdGlvbnMgaW4gYWxwaGFiZXRpYyBvcmRlcjoganVtcGluZyBhcm91bmQgb24g
YW4gaW5pdGlhbCByZWFkIGlzIGEgc21hbGwgYnVyZGVuIGNvbXBhcmVkIHRvIHRoZSBkaWZmaWN1
bHR5IG9mIGZpbmRpbmcgYSBkZWZpbml0aW9uIGluIGFuIHVub3JkZXJlZCBsaXN0IHdoZW4gcmVh
ZGluZyBkZWVwLWRvd24gZGV0YWlscy4pDQpTdGVwaGFuDQoNCg0KDQoNCg0KT24gNC80LzE2LCAw
OTozNywgImlldGYgb24gYmVoYWxmIG9mIEVnZ2VydCwgTGFycyIgPGlldGYtYm91bmNlc0BpZXRm
Lm9yZyBvbiBiZWhhbGYgb2YgbGFyc0BuZXRhcHAuY29tPiB3cm90ZToNCg0KPkhpLA0KPg0KPkkg
bW9zdGx5IHJlYWR5IHRoaXMgZnJvbSB0aGUgcGVyc3BlY3RpdmUgb2YgdGhlIElSVEYsIHNpbmNl
IHRoaXMgaXMgaW50ZW5kZWQgdG8gYWxzbyBhcHBseSB0byB1cy4gSSBmb3VuZCB0aGF0IHRoYXQg
d2Fzbid0IHRlcnJpYmx5IGNsZWFyIGZyb20gdGhlIGN1cnJlbnQgdGV4dC4NCj4NCj5MYXJzDQo+
DQo+U2VjdGlvbiAxLiwgcGFyYWdyYXBoIDA6DQo+PiAxLiBEZWZpbml0aW9ucw0KPg0KPiAgU29y
dGluZyB0aGVzZSBkZWZpbml0aW9ucyBhbHBoYWJldGljYWxseSBpcyBub3QgcmVhbGx5IGhlbHBm
dWwgdG8gdGhlDQo+ICByZWFkZXIuIENvdWxkIHlvdSBvcmRlciB0aGVtIHN1Y2ggdGhhdCB0ZXJt
cyBhcmUgZGVmaW5lZCBiZWZvcmUgYmVpbmcNCj4gIHJlZmVycmVkIHRvLCBvciBhdCBsZWFzdCB0
cnk/DQo+DQo+DQo+U2VjdGlvbiAxLiwgcGFyYWdyYXBoIDM6DQo+PiAgICBiLiAiQ29udHJpYnV0
aW9uIjogYW55IHN1Ym1pc3Npb24gdG8gdGhlIElFVEYgaW50ZW5kZWQgYnkgdGhlDQo+PiAgICAg
ICBDb250cmlidXRvciBmb3IgcHVibGljYXRpb24gYXMgYWxsIG9yIHBhcnQgb2YgYW4gSW50ZXJu
ZXQtRHJhZnQgb3INCj4+ICAgICAgIFJGQyBhbmQgYW55IHN0YXRlbWVudCBtYWRlIHdpdGhpbiB0
aGUgY29udGV4dCBvZiBhbiBJRVRGIGFjdGl2aXR5LA0KPj4gICAgICAgaW4gZWFjaCBjYXNlIHRo
YXQgaXMgaW50ZW5kZWQgdG8gYWZmZWN0IHRoZSBJRVRGIFN0YW5kYXJkcyBQcm9jZXNzDQo+PiAg
ICAgICBvciB0aGF0IGlzIHJlbGF0ZWQgdG8gdGhlIGFjdGl2aXR5IG9mIGFuIEFsdGVybmF0ZSBT
dHJlYW0gdGhhdCBoYXMNCj4+ICAgICAgIGFkb3B0ZWQgdGhpcyBkZWZpbml0aW9uLg0KPg0KPiBX
aGF0IGRvIHlvdSBtZWFuIGJ5ICJ0aGlzIGRlZmluaXRpb24iPyBBbHNvLCBpdCdzIG5vdCBjbGVh
ciB3aGF0DQo+ICJhY3Rpdml0eSBvZiBhbiBBbHRlcm5hdGUgU3RyZWFtIiBpcyBzdXBwb3NlZCB0
byBjb252ZXkuIEkgdGhpbmsgdGhpcw0KPiBpbnRlbmRzIHRvIGNhcHR1cmUgd29yayBvY2N1cnJp
bmcgaW4gSVJURiBSR3MsIGJ1dCBpdCdzIGEgcHJldHR5DQo+IGluZGlyZWN0IHdheSBvZiBzdGF0
aW5nIHRoaXMuDQo+DQo+DQo+U2VjdGlvbiAxLiwgcGFyYWdyYXBoIDQ6DQo+PiAgICAgICBTdWNo
IHN0YXRlbWVudHMgaW5jbHVkZSBvcmFsIHN0YXRlbWVudHMsIGFzIHdlbGwgYXMgd3JpdHRlbiBh
bmQNCj4+ICAgICAgIGVsZWN0cm9uaWMgY29tbXVuaWNhdGlvbnMsIHdoaWNoIGFyZSBhZGRyZXNz
ZWQgdG86DQo+DQo+ICBUaGUgbGlzdCBiZWxvdyBkb2VzIG5vdCBpbmNsdWRlIElSVEYgbWFpbGlu
ZyBsaXN0cyBvciBtZWV0aW5ncy4NCj4NCj4NCj5TZWN0aW9uIDEuLCBwYXJhZ3JhcGggOToNCj4+
ICAgIGUuICJJRVRGIjogSW4gdGhlIGNvbnRleHQgb2YgdGhpcyBkb2N1bWVudCwgdGhlIElFVEYg
aW5jbHVkZXMgYWxsDQo+PiAgICAgICBpbmRpdmlkdWFscyB3aG8gcGFydGljaXBhdGUgaW4gbWVl
dGluZ3MsIHdvcmtpbmcgZ3JvdXBzLCBtYWlsaW5nDQo+PiAgICAgICBsaXN0cywgZnVuY3Rpb25z
IGFuZCBvdGhlciBhY3Rpdml0aWVzIHdoaWNoIGFyZSBvcmdhbml6ZWQgb3INCj4+ICAgICAgIGlu
aXRpYXRlZCBieSBJU09DLCB0aGUgSUVTRyBvciB0aGUgSUFCIHVuZGVyIHRoZSBnZW5lcmFsDQo+
PiAgICAgICBkZXNpZ25hdGlvbiBvZiB0aGUgSW50ZXJuZXQgRW5naW5lZXJpbmcgVGFzayBGb3Jj
ZSBvciBJRVRGLCBidXQNCj4+ICAgICAgIHNvbGVseSB0byB0aGUgZXh0ZW50IG9mIHN1Y2ggcGFy
dGljaXBhdGlvbi4NCj4NCj4gIEZvciBjbGFyaXR5LCBJIHdvdWxkIGFsc28gY2FsbCBvdXQgdGhl
IElSVEYgYW5kIGl0cyBSR3MgaGVyZS4NCj4NCj4NCj5TZWN0aW9uIDEuLCBwYXJhZ3JhcGggMTA6
DQo+DQo+PiAgICBmLiAiSUVURiBEb2N1bWVudHMiOiBSRkNzIGFuZCBJbnRlcm5ldC1EcmFmdHMg
dGhhdCBhcmUgcHVibGlzaGVkIGFzDQo+PiAgICAgICBwYXJ0IG9mIHRoZSBJRVRGIFN0YW5kYXJk
cyBQcm9jZXNzLiAgVGhlc2UgYXJlIGFsc28gcmVmZXJyZWQgdG8gYXMNCj4+ICAgICAgICJJRVRG
IFN0cmVhbSBEb2N1bWVudHMiIGFzIGRlZmluZWQgaW4gU2VjdGlvbiA1LjEuMSBvZiBSRkMgNDg0
NC4NCj4NCj4gIFdoYXQgYWJvdXQgUkZDcyBhbmQgSW50ZXJuZXQtRHJhZnRzIHRoYXQgYXJlIGlu
dGVuZGVkIGFzIGNvbnRyaWJ1dGlvbnMNCj4gIHRvIElSVEYgYWN0aXZpdGllcz8gSXQgd291bGQg
YmUgdXNlZnVsIHRvIG1heWJlIGFkZCAiLi4ucGFydCBvZiB0aGUNCj4gIElFVEYgU3RhbmRhcmRz
IFByb2Nlc3MgYW5kIHJlbGF0ZWQgYWN0aXZpdGllcyIgdG8gbWFrZSB0aGlzIGNsZWFyZXIuDQo+
DQo+DQo+U2VjdGlvbiAxLiwgcGFyYWdyYXBoIDExOg0KPj4gICAgZy4gIklFVEYgU3RhbmRhcmRz
IFByb2Nlc3MiOiB0aGUgYWN0aXZpdGllcyB1bmRlcnRha2VuIGJ5IHRoZSBJRVRGIGluDQo+PiAg
ICAgICBhbnkgb2YgdGhlIHNldHRpbmdzIGRlc2NyaWJlZCBpbiB0aGUgYWJvdmUgZGVmaW5pdGlv
biBvZg0KPj4gICAgICAgQ29udHJpYnV0aW9uLiAgVGhlIElFVEYgU3RhbmRhcmRzIFByb2Nlc3Mg
bWF5IGluY2x1ZGUNCj4+ICAgICAgIHBhcnRpY2lwYXRpb24gaW4gYWN0aXZpdGllcyBhbmQgcHVi
bGljYXRpb24gb2YgZG9jdW1lbnRzIHRoYXQgYXJlDQo+PiAgICAgICBub3QgZGlyZWN0ZWQgdG93
YXJkIHRoZSBkZXZlbG9wbWVudCBvZiBJRVRGIHN0YW5kYXJkcyBvcg0KPj4gICAgICAgc3BlY2lm
aWNhdGlvbnMsIHN1Y2ggYXMgdGhlIGRldmVsb3BtZW50IGFuZCBwdWJsaWNhdGlvbiBvZg0KPj4g
ICAgICAgaW5mb3JtYXRpb25hbCBkb2N1bWVudHMuDQo+DQo+ICBJJ2QgYWdhaW4gZXhwbGljaXRs
eSBjYWxsIG91dCB0aGUgYWx0ZXJuYXRlIHN0cmVhbXMgaGVyZS4gQW5kIG1heWJlDQo+ICB0aGlz
IGRvY3VtZW50IGlzIG1lYW50IGZvciBsYXd5ZXJzIGFuZCBJIGFtIG5vdCBvbmUsIGJ1dCBoYXZp
bmcgYQ0KPiAgZGVmaW5pdGlvbiBjYWxsZWQgIklFVEYgU3RhbmRhcmRzIFByb2Nlc3MiIHRoYXQg
YWxzbyBpbmNsdWRlcyBhbGwgb2YNCj4gIG91ciBub24tc3RhbmRhcmQtc2V0dGluZyBhY3Rpdml0
aWVzIGlzIGNvbmZ1c2luZy4NCj4NCj4NCj5TZWN0aW9uIDEuLCBwYXJhZ3JhcGggMTc6DQo+PiAg
ICBtLiAiUkZDIjogdGhlIGJhc2ljIHB1YmxpY2F0aW9uIHNlcmllcyBmb3IgdGhlIElFVEYuICBS
RkNzIGFyZQ0KPj4gICAgICAgcHVibGlzaGVkIGJ5IHRoZSBSRkMgRWRpdG9yIGFuZCBvbmNlIHB1
Ymxpc2hlZCBhcmUgbmV2ZXIgbW9kaWZpZWQuDQo+PiAgICAgICAoU2VlIFtSRkMyMDI2XSBTZWN0
aW9uIDIuMSkNCj4NCj4gIE1pZ2h0IHdhbnQgdG8gbWVudGlvbiB0aGUgZXhpc3RlbmNlIG9mIGVy
cmF0YS4NCj4NCj4NCj5TZWN0aW9uIDUuNS4sIHBhcmFncmFwaCAwOg0KPj4gNS41LiBMaWNlbnNp
bmcgSW5mb3JtYXRpb24gaW4gYW4gSVBSIERpc2Nsb3N1cmUNCj4NCj4gIEl0J3MgYmVlbiBydW5u
aW5nIGNvZGUgb24gdGhlIElSVEYgc2lkZSB0byBiZSB2ZXJ5IE9LIHdpdGggbm90IGhhdmluZw0K
PiAgbGljZW5zZSB0ZXJtcyBpbmNsdWRlZCwgZXNwLiBpZiBpdCBzaWduaWZpY2FudGx5IGRlbGF5
cyB0aGUgb2ZmaWNpYWwNCj4gIGZpbGluZyBvZiB0aGUgZGlzY2xvc3VyZSwgc2luY2UgUkdzIGRv
bid0IHNldCBzdGFuZGFyZHMgYW5kIHRoZXJlZm9yZQ0KPiAgZG9uJ3QgcmVhbGx5IG5lZWQgdG8g
Y29uc2lkZXIgbGljZW5zaW5nIHRlcm1zLiBOb3QgY2xlYXIgaWYgdGhhdA0KPiAgc2hvdWxkIGJl
IGRpc2N1c3NlZCBoZXJlLg0KPg0KPg0KPlNlY3Rpb24gMTEuLCBwYXJhZ3JhcGggMjoNCj4+ICAg
IFRoZSBsZWdhbCBydWxlcyB0aGF0IGFwcGx5IHRvIGRvY3VtZW50cyBpbiBBbHRlcm5hdGUgU3Ry
ZWFtcyBhcmUNCj4+ICAgIGVzdGFibGlzaGVkIGJ5IHRoZSBtYW5hZ2VycyBvZiB0aG9zZSBBbHRl
cm5hdGUgU3RyZWFtcyBhcyBkZWZpbmVkIGluDQo+PiAgICBbUkZDIDQ4NDRdLiAoaS5lLiwgdGhl
IEludGVybmV0IEFyY2hpdGVjdHVyZSBCb2FyZCAoSUFCKSwgSW50ZXJuZXQNCj4+ICAgIFJlc2Vh
cmNoIFN0ZWVyaW5nIEdyb3VwIChJUlNHKSBhbmQgSW5kZXBlbmRlbnQgU3VibWlzc2lvbiBFZGl0
b3IpLg0KPg0KPiAgSXMgdGhlIElSU0cgcmVhbGx5IHRoZSBtYW5hZ2VyIG9mIHRoZSBJUlRGIHN0
cmVhbT8gSSB0aG91Z2h0IGl0IHdhcw0KPiAgdGhlIElSVEYgY2hhaXIsIGJ1dCBJIGNhbid0IGZp
bmQgdGhlIGRlZmluaXRpdmUgYW5zd2VyIGluIGVpdGhlciA0ODQ0LA0KPiAgNTc0MiBvciA1NzQz
Li4uDQo+DQo+DQo=


From nobody Mon Apr  4 06:43:34 2016
Return-Path: <barryleiba.mailing.lists@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 A26EC12D586 for <ietf@ietfa.amsl.com>; Mon,  4 Apr 2016 06:43:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.4
X-Spam-Level: 
X-Spam-Status: No, score=-2.4 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.199, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 EOzHlV5nTTnm for <ietf@ietfa.amsl.com>; Mon,  4 Apr 2016 06:43:27 -0700 (PDT)
Received: from mail-ig0-x243.google.com (mail-ig0-x243.google.com [IPv6:2607:f8b0:4001:c05::243]) (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 1C47612D576 for <ietf@ietf.org>; Mon,  4 Apr 2016 06:43:22 -0700 (PDT)
Received: by mail-ig0-x243.google.com with SMTP id nt3so15652352igb.0 for <ietf@ietf.org>; Mon, 04 Apr 2016 06:43:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc; bh=O+2E1kwr4XzAB4UrlqT8ro8G4+nq47qZWwB9AM3ROv8=; b=eVWjOdzfewOryaMGE5EU+dlyqSB2typR9lf04oki0+RjM1cH4OOcu6kPSTd3UWiV1A iiszpKhtcBd2hnlPpm5zIzvqEtFSvc8uv31Xu4JyPDTrbOf7SxtWqOsZ+5zVvWq532aJ k92KfFQMcD5JTGuAiwrNraO8tR1so2QsVESn40PATBxmrm6U9FyOBeT7dggpAAcubTqV K5wBExnYq05nSOp2mudzSmxof6tPd+tnbXR/fdKTlKdn0AT7UCDdnNUj8zfK3bbCd/pu cOJkZP0Xb5kJ4rA9wKgbovbNTK3+er/zo4STKSE/HJ3dkjVlgde9qFJXsDYb5bR8JlPw wANw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:date :message-id:subject:from:to:cc; bh=O+2E1kwr4XzAB4UrlqT8ro8G4+nq47qZWwB9AM3ROv8=; b=akIHhhHBybbtVgErJITHgselmxfaz/2Neyb84hs1KOAlb8ZodQ6ppxvQ3mHy/8JIRd t1h7gXTh2y82L7PDq8TUDtJ6IkJta1zoa1+8BhVxZkBn9nq2a+qy3m7VTp74Jd5MchMe ahgJtkpEs5wIzko8GOievrx4hRuVgBYhnnrYz6A82wTaR6bhzLhac9jP4KYV5r3JuFJv xNzQ5kpiJtsiP1aiwvtzr2fqEiWGeTHpP9iIDrJHWqc8qvqraLmNcxtXjRSufEB4tY7I jvIfJndxoORZNua4nxBsEWnByLSy9Pf/IQ4KBzxC0phm37PU46ohv3bOBal+u/AnILeU IJmA==
X-Gm-Message-State: AD7BkJKDx6MgveiX+nYMj/Q1Vn0eCgvFfLCbnsXY/uPaAd8o/l8pVsj4MYmFLPNRu+17RhRirDXPHiomZwdlbQ==
MIME-Version: 1.0
X-Received: by 10.50.92.70 with SMTP id ck6mr9961141igb.80.1459777401463; Mon, 04 Apr 2016 06:43:21 -0700 (PDT)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.107.26.130 with HTTP; Mon, 4 Apr 2016 06:43:21 -0700 (PDT)
In-Reply-To: <56FC90E5.1050908@gmail.com>
References: <0000431F-F977-4A24-BA4D-064F740977A0@piuha.net> <56FBF599.9080605@ericsson.com> <ACC702C9-C33F-4D38-B47A-8BC293D24621@sobco.com> <DCA1B6AC-6221-4CF5-A726-E1E98DBFAC27@vigilsec.com> <56FC90E5.1050908@gmail.com>
Date: Mon, 4 Apr 2016 09:43:21 -0400
X-Google-Sender-Auth: 1nL_OsVsaGjEX2G4S2VtdP_LJJE
Message-ID: <CAC4RtVD3Pxm_vZgdCCgPgDwNfnYeKFJ5_Ys3QQPezrHzTGJE+Q@mail.gmail.com>
Subject: Re: Last Call on draft-bradner-rfc3979bis-08.txt ("Intellectual Property Rights in IETF Technology")
From: Barry Leiba <barryleiba@computer.org>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/uXjhfxyxk2nV_KfbFJSvCTv_qDk>
Cc: IETF <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: Mon, 04 Apr 2016 13:43:32 -0000

>> So, one might argue that an AD can be unaware that a particular
>> document includes something that needs to be disclosed up to the
>> point that they take some action on that document, such as sponsoring it.
>
> Yes, but is that an issue? The AD is only required to disclose when
> she is "reasonably and personally aware" of the need for a disclosure,
> which will presumably become the case when she actually reads the draft
> (or sees the slides that describe the technology in question).

Be careful here: I think it is an issue.

The "reasonably and personally aware" applies to the IPR, not to the
participation.  If I'm participating in active discussion about
Section 4 of document X, and I should be reasonably and personally
aware of IPR my employer holds with respect to Section 3 of document
X, we aren't going to happily accept that I didn't read Section 3 so I
don't have a responsibility to disclose.

If we're saying that, say, ADs are considered to be Participants with
respect to every document and discussion in every working group in the
area -- and I see why some people think that's wise and appropriate --
then we're saying that I have a responsibility to disclose whether or
not I've read the documents, and waiting until AD Evaluation state
would be a late disclosure.  Consider that the working group might
have been proceeding for a couple of years and many I-D revisions
under the assumption that the technology is unencumbered... and then I
dump an IPR statement on them just as they've finished.

This really is a tough one: it would be nice if the late disclosure
didn't happen, but ADs can't reasonably be expected to read every
draft in every working group early on... and, as others have said, it
would be very bad if this disclosure requirement gave us even fewer AD
candidates than we have now.

Barry


From nobody Mon Apr  4 07:15:42 2016
Return-Path: <stewe@stewe.org>
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 2500912D6F9 for <ietf@ietfa.amsl.com>; Mon,  4 Apr 2016 07:15:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] 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 iNoc0QeEHqzS for <ietf@ietfa.amsl.com>; Mon,  4 Apr 2016 07:15:40 -0700 (PDT)
Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1bon0709.outbound.protection.outlook.com [IPv6:2a01:111:f400:fc10::1:709]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C366F12D52A for <ietf@ietf.org>; Mon,  4 Apr 2016 07:15:39 -0700 (PDT)
Received: from BLUPR17MB0275.namprd17.prod.outlook.com (10.162.235.146) by BLUPR17MB0276.namprd17.prod.outlook.com (10.162.235.147) with Microsoft SMTP Server (TLS) id 15.1.447.15; Mon, 4 Apr 2016 14:15:21 +0000
Received: from BLUPR17MB0275.namprd17.prod.outlook.com ([10.162.235.146]) by BLUPR17MB0275.namprd17.prod.outlook.com ([10.162.235.146]) with mapi id 15.01.0447.027; Mon, 4 Apr 2016 14:15:21 +0000
From: Stephan Wenger <stewe@stewe.org>
To: Barry Leiba <barryleiba@computer.org>, Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: Last Call on draft-bradner-rfc3979bis-08.txt ("Intellectual Property Rights in IETF Technology")
Thread-Topic: Last Call on draft-bradner-rfc3979bis-08.txt ("Intellectual Property Rights in IETF Technology")
Thread-Index: AQHRhDTbKR9yu1RueEWA9RrAiHSISp9yLyaAgAAKyYCAAE/KAIAAXo6AgAb/NoD//9ajAA==
Date: Mon, 4 Apr 2016 14:15:21 +0000
Message-ID: <C5F35DA9-C530-4EC6-B175-C4B0A18872D7@stewe.org>
References: <0000431F-F977-4A24-BA4D-064F740977A0@piuha.net> <56FBF599.9080605@ericsson.com> <ACC702C9-C33F-4D38-B47A-8BC293D24621@sobco.com> <DCA1B6AC-6221-4CF5-A726-E1E98DBFAC27@vigilsec.com> <56FC90E5.1050908@gmail.com> <CAC4RtVD3Pxm_vZgdCCgPgDwNfnYeKFJ5_Ys3QQPezrHzTGJE+Q@mail.gmail.com>
In-Reply-To: <CAC4RtVD3Pxm_vZgdCCgPgDwNfnYeKFJ5_Ys3QQPezrHzTGJE+Q@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: computer.org; dkim=none (message not signed) header.d=none;computer.org; dmarc=none action=none header.from=stewe.org;
x-ms-exchange-messagesentrepresentingtype: 1
x-originating-ip: [31.133.179.232]
x-ms-office365-filtering-correlation-id: 3d3b96dd-2a94-465f-aabc-08d35c938ecf
x-microsoft-exchange-diagnostics: 1; BLUPR17MB0276; 5:YP9S33FfM4q4HXLcAVKneOfhEQJm2Wn1pXsA4h+sEXCK5iIbiR0IDfHS6YJprsvBETy/+5szJJTixNL/nxJX7gdFYv/6u/N5mYDROv2K0nhwPwsNrrZ+s7nNsswvP/pVfeF7amNvF6u/MnmLrGlnrw==; 24:It6V64i6JU2T+0MzEHnNwPn6ER1q6k37ja4zceUX9WlG6EXHRJPXN+znU2gG6/5FZX8bXIhYcRnJ0hCizxyYeZ5GepLzEs9wG5b98OcdLAA=
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:BLUPR17MB0276;
x-microsoft-antispam-prvs: <BLUPR17MB0276959D197C6922435F6F03AE9D0@BLUPR17MB0276.namprd17.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040046)(601004)(2401047)(8121501046)(5005006)(3002001)(10201501046)(6041046)(6043046); SRVR:BLUPR17MB0276; BCL:0; PCL:0; RULEID:; SRVR:BLUPR17MB0276; 
x-forefront-prvs: 0902222726
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(24454002)(3280700002)(106116001)(92566002)(2906002)(11100500001)(4326007)(1096002)(1220700001)(586003)(50986999)(54356999)(76176999)(230783001)(86362001)(3660700001)(189998001)(36756003)(5004730100002)(5001770100001)(5002640100001)(87936001)(3846002)(82746002)(77096005)(102836003)(6116002)(2900100001)(93886004)(19580405001)(33656002)(66066001)(10400500002)(5008740100001)(19580395003)(81166005)(83716003)(2950100001)(122556002)(104396002)(42262002); DIR:OUT; SFP:1102; SCL:1; SRVR:BLUPR17MB0276; H:BLUPR17MB0275.namprd17.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en; 
spamdiagnosticoutput: 1:23
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
Content-ID: <8735DF8692CF8948A46CD65ED9768290@namprd17.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: stewe.org
X-MS-Exchange-CrossTenant-originalarrivaltime: 04 Apr 2016 14:15:21.3106 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 865fc51c-5fae-4322-98ef-0121a85df0b6
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BLUPR17MB0276
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/2Na6J3ac5m3X6D1lgnTjAoErUGI>
Cc: IETF <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: Mon, 04 Apr 2016 14:15:42 -0000

SGkgQmFycnksDQoNCg0KDQpPbiA0LzQvMTYsIDEwOjQzLCAiaWV0ZiBvbiBiZWhhbGYgb2YgQmFy
cnkgTGVpYmEiIDxpZXRmLWJvdW5jZXNAaWV0Zi5vcmcgb24gYmVoYWxmIG9mIGJhcnJ5bGVpYmFA
Y29tcHV0ZXIub3JnPiB3cm90ZToNCg0KPj4+IFNvLCBvbmUgbWlnaHQgYXJndWUgdGhhdCBhbiBB
RCBjYW4gYmUgdW5hd2FyZSB0aGF0IGEgcGFydGljdWxhcg0KPj4+IGRvY3VtZW50IGluY2x1ZGVz
IHNvbWV0aGluZyB0aGF0IG5lZWRzIHRvIGJlIGRpc2Nsb3NlZCB1cCB0byB0aGUNCj4+PiBwb2lu
dCB0aGF0IHRoZXkgdGFrZSBzb21lIGFjdGlvbiBvbiB0aGF0IGRvY3VtZW50LCBzdWNoIGFzIHNw
b25zb3JpbmcgaXQuDQo+Pg0KPj4gWWVzLCBidXQgaXMgdGhhdCBhbiBpc3N1ZT8gVGhlIEFEIGlz
IG9ubHkgcmVxdWlyZWQgdG8gZGlzY2xvc2Ugd2hlbg0KPj4gc2hlIGlzICJyZWFzb25hYmx5IGFu
ZCBwZXJzb25hbGx5IGF3YXJlIiBvZiB0aGUgbmVlZCBmb3IgYSBkaXNjbG9zdXJlLA0KPj4gd2hp
Y2ggd2lsbCBwcmVzdW1hYmx5IGJlY29tZSB0aGUgY2FzZSB3aGVuIHNoZSBhY3R1YWxseSByZWFk
cyB0aGUgZHJhZnQNCj4+IChvciBzZWVzIHRoZSBzbGlkZXMgdGhhdCBkZXNjcmliZSB0aGUgdGVj
aG5vbG9neSBpbiBxdWVzdGlvbikuDQo+DQo+QmUgY2FyZWZ1bCBoZXJlOiBJIHRoaW5rIGl0IGlz
IGFuIGlzc3VlLg0KPg0KPlRoZSAicmVhc29uYWJseSBhbmQgcGVyc29uYWxseSBhd2FyZSIgYXBw
bGllcyB0byB0aGUgSVBSLCBub3QgdG8gdGhlDQo+cGFydGljaXBhdGlvbi4gIA0KDQpJIHRoaW5r
IHRoaXMgaXMgaW5jb3JyZWN0LiAgDQoNCkFjY29yZGluZyB0byBzZWN0aW9uIDUuMS4yIChkaXNj
bG9zdXJlIHJlcXVpcmVtZW50IGJhc2VkIG9uIFBhcnRpY2lwYXRpb24sIG5vdCBvd24gSVBSKSwg
YSBkaXNjbG9zdXJlIG9ibGlnYXRpb24gZXhpc3RzIGlmIOKAnHRoZSBQYXJ0aWNpcGFudCBiZWxp
ZXZlcyBDb3ZlcnMgb3IgbWF5IHVsdGltYXRlbHkgQ292ZXIgdGhhdCBDb250cmlidXRpb27igJ0u
ICBJIGRvbuKAmXQgdGhpbmsgYW55b25lIGNvdWxkIGFyZ3VlIHRoYXQgYW4gQUQgaGFzIGEg4oCc
YmVsaWV2ZeKAnSBpbiBhIHBhdGVudCBvciBhcHBsaWNhdGlvbiBoZS9zaGUgaXMgYXdhcmUgb2Yg
Q292ZXJzIGEgQ29udHJpYnV0aW9uIHdoZW4gaGUgaGFzIG5ldmVyIHNlZW4gdGhlIENvbnRyaWJ1
dGlvbi4gIA0KDQo+SWYgSSdtIHBhcnRpY2lwYXRpbmcgaW4gYWN0aXZlIGRpc2N1c3Npb24gYWJv
dXQNCj5TZWN0aW9uIDQgb2YgZG9jdW1lbnQgWCwgYW5kIEkgc2hvdWxkIGJlIHJlYXNvbmFibHkg
YW5kIHBlcnNvbmFsbHkNCj5hd2FyZSBvZiBJUFIgbXkgZW1wbG95ZXIgaG9sZHMgd2l0aCByZXNw
ZWN0IHRvIFNlY3Rpb24gMyBvZiBkb2N1bWVudA0KPlgsIHdlIGFyZW4ndCBnb2luZyB0byBoYXBw
aWx5IGFjY2VwdCB0aGF0IEkgZGlkbid0IHJlYWQgU2VjdGlvbiAzIHNvIEkNCj5kb24ndCBoYXZl
IGEgcmVzcG9uc2liaWxpdHkgdG8gZGlzY2xvc2UuDQo+DQo+SWYgd2UncmUgc2F5aW5nIHRoYXQs
IHNheSwgQURzIGFyZSBjb25zaWRlcmVkIHRvIGJlIFBhcnRpY2lwYW50cyB3aXRoDQo+cmVzcGVj
dCB0byBldmVyeSBkb2N1bWVudCBhbmQgZGlzY3Vzc2lvbiBpbiBldmVyeSB3b3JraW5nIGdyb3Vw
IGluIHRoZQ0KPmFyZWEgLS0gYW5kIEkgc2VlIHdoeSBzb21lIHBlb3BsZSB0aGluayB0aGF0J3Mg
d2lzZSBhbmQgYXBwcm9wcmlhdGUgLS0NCj50aGVuIHdlJ3JlIHNheWluZyB0aGF0IEkgaGF2ZSBh
IHJlc3BvbnNpYmlsaXR5IHRvIGRpc2Nsb3NlIHdoZXRoZXIgb3INCj5ub3QgSSd2ZSByZWFkIHRo
ZSBkb2N1bWVudHMsIGFuZCB3YWl0aW5nIHVudGlsIEFEIEV2YWx1YXRpb24gc3RhdGUNCj53b3Vs
ZCBiZSBhIGxhdGUgZGlzY2xvc3VyZS4gIENvbnNpZGVyIHRoYXQgdGhlIHdvcmtpbmcgZ3JvdXAg
bWlnaHQNCj5oYXZlIGJlZW4gcHJvY2VlZGluZyBmb3IgYSBjb3VwbGUgb2YgeWVhcnMgYW5kIG1h
bnkgSS1EIHJldmlzaW9ucw0KPnVuZGVyIHRoZSBhc3N1bXB0aW9uIHRoYXQgdGhlIHRlY2hub2xv
Z3kgaXMgdW5lbmN1bWJlcmVkLi4uIGFuZCB0aGVuIEkNCj5kdW1wIGFuIElQUiBzdGF0ZW1lbnQg
b24gdGhlbSBqdXN0IGFzIHRoZXkndmUgZmluaXNoZWQuDQoNCkEgbGF0ZSBkaXNjbG9zdXJlIGlz
IGJldHRlciB0aGFuIG5vIGRpc2Nsb3N1cmUsIGFuZCwgY2xlYXJseSwgYW4gQUQgaGFzIGEgbXVj
aCBiZXR0ZXIganVzdGlmaWNhdGlvbiBvZiBtYWtpbmcgc3VjaCBhIGxhdGUgZGlzY2xvc3VyZS4g
IEkgd291bGQgaG9wZSB0aGF0IG5vIG9uZSB3b3VsZCBjb21wbGFpbiBpZiBhbiBBRCBtYWtlcyBh
IGxhdGUgZGlzY2xvc3VyZSBhbmQsIHdoZW4gYXNrZWQgZm9yIHRoZSByZWFzb24gb2YgbGF0ZW5l
c3MsIGhlIHNheXMg4oCcSSB3YXMgbm90IHJlc3BvbnNpYmxlIEFEOyBJIGNhbWUgYWNyb3NzIHRo
aXMgZHVyaW5nIGZpbmFsIHJldmlldyBpbiBJRVRGIGxhc3QgY2FsbCwgYW5kIGp1c3QgaWRlbnRp
ZmllZCB0aGlzLiDigJwgIEluIGZhY3QsIHBlb3BsZSBzaG91bGQgYXBwcmVjaWF0ZSB0aGlzLg0K
DQpTdGVwaGFuDQoNCj4NCj5UaGlzIHJlYWxseSBpcyBhIHRvdWdoIG9uZTogaXQgd291bGQgYmUg
bmljZSBpZiB0aGUgbGF0ZSBkaXNjbG9zdXJlDQo+ZGlkbid0IGhhcHBlbiwgYnV0IEFEcyBjYW4n
dCByZWFzb25hYmx5IGJlIGV4cGVjdGVkIHRvIHJlYWQgZXZlcnkNCj5kcmFmdCBpbiBldmVyeSB3
b3JraW5nIGdyb3VwIGVhcmx5IG9uLi4uIGFuZCwgYXMgb3RoZXJzIGhhdmUgc2FpZCwgaXQNCj53
b3VsZCBiZSB2ZXJ5IGJhZCBpZiB0aGlzIGRpc2Nsb3N1cmUgcmVxdWlyZW1lbnQgZ2F2ZSB1cyBl
dmVuIGZld2VyIEFEDQo+Y2FuZGlkYXRlcyB0aGFuIHdlIGhhdmUgbm93Lg0KPg0KPkJhcnJ5DQo+
DQo=


From nobody Mon Apr  4 07:27:28 2016
Return-Path: <barryleiba@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 872A612D52A for <ietf@ietfa.amsl.com>; Mon,  4 Apr 2016 07:27:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.4
X-Spam-Level: 
X-Spam-Status: No, score=-2.4 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.199, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 vQu6jH53sUzq for <ietf@ietfa.amsl.com>; Mon,  4 Apr 2016 07:27:25 -0700 (PDT)
Received: from mail-yw0-x231.google.com (mail-yw0-x231.google.com [IPv6:2607:f8b0:4002: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 9141812D68E for <ietf@ietf.org>; Mon,  4 Apr 2016 07:27:24 -0700 (PDT)
Received: by mail-yw0-x231.google.com with SMTP id g127so253012465ywf.2 for <ietf@ietf.org>; Mon, 04 Apr 2016 07:27:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-transfer-encoding; bh=FTrnpEC7Y28iLQ0UldhY7ALWbFWdMxMkY2g6Wdours4=; b=Xh2oC8X6+xmXj31Jvgw1y36P8dZgj2XkFZD3G2xEX93f5rDM3A0DTtsuCmv0Azvdav WWLhZIr1nRSN9hCTpOYvbwXuFJRA+gZY/SSzLzVMTyNp8TKL8/T84EB8v27gzHZr72m1 oyZwzEM4jb3kYhdjL2CoqJTpeREIKkRBHrDGZLX7Uml5yaYfgsI6WPHq08rEKMR19QOO xOqp2C/q7ZMqRVmqD1nutz8IFGAWqTb1zSNk43oDb+neL+lwjKk5xs8boFZEWwmV0+Yo gUmvnBMlXtFgWMcO9rMVq0pCpSaGKgV5hM8jaBuKnAVGIyuBsTfEOdXrsliT+oYE2TRw 6YPA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:date :message-id:subject:from:to:cc:content-transfer-encoding; bh=FTrnpEC7Y28iLQ0UldhY7ALWbFWdMxMkY2g6Wdours4=; b=Qk+iI9CgKisq2EDJAhdUFG0JP1z/iLFwUejrKpdZpzWry8w7xObqOe1gf/zjF35ya1 5bMS0ZhZTtwg7Y7V6deMb3FXYaKnbnQnf/GlXqZrD87Gbhh40vMnDr1r+OkOzRjbAtQg BFed/5/0jdppWyo2ClPxEezT7CiJid3vUb9IXRF8hODbvcuqw6XY3//nw2mZOxHxYt6s /01TCAsUDLB8d7jMkDmG2FeeOK/FcNVDeoB6PejiLGvPexYDfUvYxTGpfPHkY09HfKc+ 8MBjSzyqnDVJUYukeZM6VyP0VukpUDO8bg3DK7uNA37+EuAX461KIi8721xiVk3kBJ86 /YvQ==
X-Gm-Message-State: AD7BkJKDJElnJEXo13KdMBncLq+v1WpqVUQPeO74o8tBHXkzywCst2PsM7nNsyB95vEgoaVgq5tMOFss7n0GLg==
MIME-Version: 1.0
X-Received: by 10.37.0.66 with SMTP id 63mr5557490yba.134.1459780043752; Mon, 04 Apr 2016 07:27:23 -0700 (PDT)
Sender: barryleiba@gmail.com
Received: by 10.83.28.67 with HTTP; Mon, 4 Apr 2016 07:27:23 -0700 (PDT)
In-Reply-To: <C5F35DA9-C530-4EC6-B175-C4B0A18872D7@stewe.org>
References: <0000431F-F977-4A24-BA4D-064F740977A0@piuha.net> <56FBF599.9080605@ericsson.com> <ACC702C9-C33F-4D38-B47A-8BC293D24621@sobco.com> <DCA1B6AC-6221-4CF5-A726-E1E98DBFAC27@vigilsec.com> <56FC90E5.1050908@gmail.com> <CAC4RtVD3Pxm_vZgdCCgPgDwNfnYeKFJ5_Ys3QQPezrHzTGJE+Q@mail.gmail.com> <C5F35DA9-C530-4EC6-B175-C4B0A18872D7@stewe.org>
Date: Mon, 4 Apr 2016 10:27:23 -0400
X-Google-Sender-Auth: v8giCcW5lNkqDqvzJAL_UiasGMs
Message-ID: <CALaySJ+1rvxXnXmLxk1UJ88t-e2p24OyMhR3f6P0peA5fLhRGA@mail.gmail.com>
Subject: Re: Last Call on draft-bradner-rfc3979bis-08.txt ("Intellectual Property Rights in IETF Technology")
From: Barry Leiba <barryleiba@computer.org>
To: Stephan Wenger <stewe@stewe.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/n9j5XT5DlpTt4QvosIJ2d9oH7C0>
Cc: IETF <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: Mon, 04 Apr 2016 14:27:26 -0000

>>The "reasonably and personally aware" applies to the IPR, not to the
>>participation.
>
> I think this is incorrect.
>
> According to section 5.1.2 (disclosure requirement based on
> Participation, not own IPR), a disclosure obligation exists if =E2=80=9Ct=
he
> Participant believes Covers or may ultimately Cover that
> Contribution=E2=80=9D.  I don=E2=80=99t think anyone could argue that an =
AD has a
> =E2=80=9Cbelieve=E2=80=9D in a patent or application he/she is aware of C=
overs a
> Contribution when he has never seen the Contribution.

Would you accept "I didn't read the draft" as an acceptable reason
that someone engaged in active discussion on a draft didn't disclose?

We don't have different levels of Contributor here.  Someone making a
Contribution has an obligation to disclose, even if s/he was one of
those who said, "I didn't read the draft, but...."  If we declare the
ADs to be Contributors, why does the same not apply to them?

> A late disclosure is better than no disclosure

I hope we all agree on that!

> clearly, an AD
> has a much better justification of making such a late disclosure.  I
> would hope that no one would complain if an AD makes a late disclosure
> and, when asked for the reason of lateness, he says =E2=80=9CI was not
> responsible AD; I came across this during final review in IETF last
> call, and just identified this. =E2=80=9C  In fact, people should appreci=
ate
> this.

Maybe so, but as it stands now in the document, it's still a late
disclosure, and there might still be backlash, legal concerns by
employers, and reluctance to put people in that position.

If that's the consensus, then there we have it... but I think we
should be very careful about unintended consequences of this one.

Barry


From nobody Mon Apr  4 07:39:25 2016
Return-Path: <barryleiba@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 74A1E12D721 for <ietf@ietfa.amsl.com>; Mon,  4 Apr 2016 07:39:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.4
X-Spam-Level: 
X-Spam-Status: No, score=-2.4 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.199, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 lHSfPqI9s4e4 for <ietf@ietfa.amsl.com>; Mon,  4 Apr 2016 07:39:17 -0700 (PDT)
Received: from mail-yw0-x233.google.com (mail-yw0-x233.google.com [IPv6:2607:f8b0:4002:c05::233]) (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 CC5CC12D72D for <ietf@ietf.org>; Mon,  4 Apr 2016 07:39:07 -0700 (PDT)
Received: by mail-yw0-x233.google.com with SMTP id g3so254921906ywa.3 for <ietf@ietf.org>; Mon, 04 Apr 2016 07:39:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-transfer-encoding; bh=dSyB7w+gPYBZffNDOQLanK7cCsOm9BWYkgkbEhNUzok=; b=fIqeWX0XbdZwZyA13WLpBIMRj3T1Mp/ADINmENvD8U1ccVD4IShBRGKDvQrCHi9J/9 espfAGnMZ98o2X3aiXlZKNTL5NQDlOZKPPcleoY+DU00hovNjO0af7MZE2XeYNudigH0 ZBvql+DDnxagqDE3OGH62WDwsQwVSwP1dKcbgMQCuPZjD6Ha6qdg3Eteabv/qPR4lcK1 88DPpGmp/UinGfzB0w05h/Zhexzt2F4O+rXs2mmnQwKQNkiMNPHPySunOossMPoStbE7 Q1FtcTTdrFqkoUkdDMzTrMkQ2DPCcFlucDLjy7Hb2u8nRhEQ0H4iy9Ue/Zw2svgm5gHs 8haA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:date :message-id:subject:from:to:cc:content-transfer-encoding; bh=dSyB7w+gPYBZffNDOQLanK7cCsOm9BWYkgkbEhNUzok=; b=G3hLJkGCjYkFfTU1Ld10QYo5OhhVP01w6aepQqfMEMakKNg9WmFcm2OvP+xVBfpq3p C3FlNyIuiskpIr4kyTMtXmXlZuK77rN+4YXDtBPYVo3vSlQiNFlLc+FSthOQGPkFyWAD cHm/ClFXU/RBon6Yc8R6uAyYLe06ROp4ImmuvBzGKlhk92HcysFGaxuCoYCP7IAjfORv BgjG8mYq+az/x2DuUnPJ4a06wnAgOzanYgaudFYjAlJ3mw+2224Dr1Qhs/pBFv7odOuQ 33nqg7SOXiSNCKoz6KhrPF0PlYcAAA19nw3zoeu6dL+hgx5KcfsB8c8d9JLv7q+X2L8J SP/Q==
X-Gm-Message-State: AD7BkJLglTL5N77neKTUxbLqOD2VU/aje1Ou9Prrkwe9iF6NZZ/cwtQxGsdkCgiRygPkVG4B0dELreHrlodFuw==
MIME-Version: 1.0
X-Received: by 10.13.221.140 with SMTP id g134mr10591954ywe.59.1459780747091;  Mon, 04 Apr 2016 07:39:07 -0700 (PDT)
Sender: barryleiba@gmail.com
Received: by 10.83.28.67 with HTTP; Mon, 4 Apr 2016 07:39:06 -0700 (PDT)
In-Reply-To: <CALaySJ+1rvxXnXmLxk1UJ88t-e2p24OyMhR3f6P0peA5fLhRGA@mail.gmail.com>
References: <0000431F-F977-4A24-BA4D-064F740977A0@piuha.net> <56FBF599.9080605@ericsson.com> <ACC702C9-C33F-4D38-B47A-8BC293D24621@sobco.com> <DCA1B6AC-6221-4CF5-A726-E1E98DBFAC27@vigilsec.com> <56FC90E5.1050908@gmail.com> <CAC4RtVD3Pxm_vZgdCCgPgDwNfnYeKFJ5_Ys3QQPezrHzTGJE+Q@mail.gmail.com> <C5F35DA9-C530-4EC6-B175-C4B0A18872D7@stewe.org> <CALaySJ+1rvxXnXmLxk1UJ88t-e2p24OyMhR3f6P0peA5fLhRGA@mail.gmail.com>
Date: Mon, 4 Apr 2016 10:39:06 -0400
X-Google-Sender-Auth: pNKm7unVPOVVa1I1oZq-eNTgGUs
Message-ID: <CALaySJKBrjKEdu-qd067Eb7A+nZFObB3TdwSV=od9GDjhDOecQ@mail.gmail.com>
Subject: Re: Last Call on draft-bradner-rfc3979bis-08.txt ("Intellectual Property Rights in IETF Technology")
From: Barry Leiba <barryleiba@computer.org>
To: Stephan Wenger <stewe@stewe.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/0VANgZPXLFpuuM0KDj7E5x4QEoc>
Cc: IETF <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: Mon, 04 Apr 2016 14:39:24 -0000

A follow-up here:

I'd be more comfortably with something more waffly, something more like thi=
s:

Without limiting the generality of the foregoing, acting as a working
group chair or Area Director can often be considered "Participating"
in all activities of the relevant working group or area; as such,
working group chairs and Area Directors are expected to make a best,
good-faith effort to carry out the responsibilities of Participants.

Or perhaps we want to separate WGCs from ADs here, and the text needs
more work in any case, but I hope people see the general point.

Barry

On Mon, Apr 4, 2016 at 10:27 AM, Barry Leiba <barryleiba@computer.org> wrot=
e:
>>>The "reasonably and personally aware" applies to the IPR, not to the
>>>participation.
>>
>> I think this is incorrect.
>>
>> According to section 5.1.2 (disclosure requirement based on
>> Participation, not own IPR), a disclosure obligation exists if =E2=80=9C=
the
>> Participant believes Covers or may ultimately Cover that
>> Contribution=E2=80=9D.  I don=E2=80=99t think anyone could argue that an=
 AD has a
>> =E2=80=9Cbelieve=E2=80=9D in a patent or application he/she is aware of =
Covers a
>> Contribution when he has never seen the Contribution.
>
> Would you accept "I didn't read the draft" as an acceptable reason
> that someone engaged in active discussion on a draft didn't disclose?
>
> We don't have different levels of Contributor here.  Someone making a
> Contribution has an obligation to disclose, even if s/he was one of
> those who said, "I didn't read the draft, but...."  If we declare the
> ADs to be Contributors, why does the same not apply to them?
>
>> A late disclosure is better than no disclosure
>
> I hope we all agree on that!
>
>> clearly, an AD
>> has a much better justification of making such a late disclosure.  I
>> would hope that no one would complain if an AD makes a late disclosure
>> and, when asked for the reason of lateness, he says =E2=80=9CI was not
>> responsible AD; I came across this during final review in IETF last
>> call, and just identified this. =E2=80=9C  In fact, people should apprec=
iate
>> this.
>
> Maybe so, but as it stands now in the document, it's still a late
> disclosure, and there might still be backlash, legal concerns by
> employers, and reluctance to put people in that position.
>
> If that's the consensus, then there we have it... but I think we
> should be very careful about unintended consequences of this one.
>
> Barry


From nobody Mon Apr  4 08:24:19 2016
Return-Path: <spencerdawkins.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 89BA212D625 for <ietf@ietfa.amsl.com>; Mon,  4 Apr 2016 08:24:17 -0700 (PDT)
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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 pHW5cp5Dqw5t for <ietf@ietfa.amsl.com>; Mon,  4 Apr 2016 08:24:16 -0700 (PDT)
Received: from mail-yw0-x22a.google.com (mail-yw0-x22a.google.com [IPv6:2607:f8b0:4002:c05::22a]) (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 093E212D5A7 for <ietf@ietf.org>; Mon,  4 Apr 2016 08:24:16 -0700 (PDT)
Received: by mail-yw0-x22a.google.com with SMTP id g3so256875845ywa.3 for <ietf@ietf.org>; Mon, 04 Apr 2016 08:24:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=WrBZKBlwlEWzZy9FnLrfKtI5m5nG36d7E0ruGxX8yMQ=; b=YxvsI5jdlBIMY42s9liQtb3CsahYvy9KQv70L8zDpVmSsx2tNEl2xTDx6b+DFYDHjz wyMBLVFujXTjokIw70CSBozWW8VAYZOy2HWmQnqgDNHAgLWlGpzeea+29WTj+yIGBU9K XGaT4jE1IHm1RHe7LAHg9ykllc3uA0XBuNmr0bKhx0So5ZTtN+GZ8Kcy3woSf4Kp1G6I i74vK1AQippTNde+QTKaqzOnR6XdyUXCopxm2yFz+YjPNtwnh0iky+Ega7J99QVCPZ+A epADX9gKUmB71+vGmgVv+2JpuYY7zHH9v6ha9GMQkeroG57uaV8JVEAR492RqSc0ohqs qfeg==
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:date :message-id:subject:from:to:cc; bh=WrBZKBlwlEWzZy9FnLrfKtI5m5nG36d7E0ruGxX8yMQ=; b=T4c1X9YXppMnNcIMbOEKomFmkOMDx1xlaZ/eqONqzTwWVaNEA22C7plM6HACe2kPeU oCiBwi/ytW2Q8mBukV4AQo7SbIvspQoiCkHciU6MMuxEXrg14dI24AwJbUjEVV9BitWz 7oT3lEAqQ8S+fHQPnkFNpZegwaxQvmH3GLhE9lq8QrbPQwCsIaW1DrVxY++75EGjJBL+ fYfMrzzWj3BW6wd7cmC8+Vco+h1x3NqxOuk/VhCZRFDcKSUAalHsE6TFp9UTSzFUF6Ca +MFDTcLUtHmK3/EGU7VvBh9PbGvjv313ziwGAw+uzWy6l7jWuPJDjt9XIs1NMXmQcBvf 5m0w==
X-Gm-Message-State: AD7BkJKrR3oSQzhH4eb9Igyz2TD9p5UIEbU7O2Oi7FWx7vc60thecGg2wOMrIAIp24FEw7UIETqnAgE6GUJGxA==
MIME-Version: 1.0
X-Received: by 10.129.155.137 with SMTP id s131mr5028878ywg.24.1459783455315;  Mon, 04 Apr 2016 08:24:15 -0700 (PDT)
Received: by 10.37.207.211 with HTTP; Mon, 4 Apr 2016 08:24:15 -0700 (PDT)
Received: by 10.37.207.211 with HTTP; Mon, 4 Apr 2016 08:24:15 -0700 (PDT)
In-Reply-To: <CALaySJKBrjKEdu-qd067Eb7A+nZFObB3TdwSV=od9GDjhDOecQ@mail.gmail.com>
References: <0000431F-F977-4A24-BA4D-064F740977A0@piuha.net> <56FBF599.9080605@ericsson.com> <ACC702C9-C33F-4D38-B47A-8BC293D24621@sobco.com> <DCA1B6AC-6221-4CF5-A726-E1E98DBFAC27@vigilsec.com> <56FC90E5.1050908@gmail.com> <CAC4RtVD3Pxm_vZgdCCgPgDwNfnYeKFJ5_Ys3QQPezrHzTGJE+Q@mail.gmail.com> <C5F35DA9-C530-4EC6-B175-C4B0A18872D7@stewe.org> <CALaySJ+1rvxXnXmLxk1UJ88t-e2p24OyMhR3f6P0peA5fLhRGA@mail.gmail.com> <CALaySJKBrjKEdu-qd067Eb7A+nZFObB3TdwSV=od9GDjhDOecQ@mail.gmail.com>
Date: Mon, 4 Apr 2016 12:24:15 -0300
Message-ID: <CAKKJt-ev-TbYBxtJv-tgddPf+bNuKAPCuRC8r0rhsVT8xU+FdQ@mail.gmail.com>
Subject: Re: Last Call on draft-bradner-rfc3979bis-08.txt ("Intellectual Property Rights in IETF Technology")
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
To: Barry Leiba <barryleiba@computer.org>
Content-Type: multipart/alternative; boundary=94eb2c0b927c4d9e83052faa5260
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/_EKkjNOR7vH4YWQy3ZrmoQ9m9NI>
Cc: 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: Mon, 04 Apr 2016 15:24:17 -0000

--94eb2c0b927c4d9e83052faa5260
Content-Type: text/plain; charset=UTF-8

Just chiming in ...

On Apr 4, 2016 11:39 AM, "Barry Leiba" <barryleiba@computer.org> wrote:
> Or perhaps we want to separate WGCs from ADs here, and the text needs
> more work in any case, but I hope people see the general point.

I made the point previously that I am a TSV AD, but when I'm following work
in one of Martin's TSV working groups, that's the exception, rather than
the rule.

I would hope that all of the chairs in a working group are following all of
the work in their own working group fairly closely.

So I think Barry's suggestion to consider ADs and WG chairs separately
makes sense (even if it turns out that the distinction is required).

Spencer

--94eb2c0b927c4d9e83052faa5260
Content-Type: text/html; charset=UTF-8

<p dir="ltr">Just chiming in ...</p>
<p dir="ltr">On Apr 4, 2016 11:39 AM, &quot;Barry Leiba&quot; &lt;<a href="mailto:barryleiba@computer.org">barryleiba@computer.org</a>&gt; wrote:<br>
&gt; Or perhaps we want to separate WGCs from ADs here, and the text needs<br>
&gt; more work in any case, but I hope people see the general point.</p>
<p dir="ltr">I made the point previously that I am a TSV AD, but when I&#39;m following work in one of Martin&#39;s TSV working groups, that&#39;s the exception, rather than the rule.</p>
<p dir="ltr">I would hope that all of the chairs in a working group are following all of the work in their own working group fairly closely.</p>
<p dir="ltr">So I think Barry&#39;s suggestion to consider ADs and WG chairs separately makes sense (even if it turns out that the distinction is required).</p>
<p dir="ltr">Spencer</p>

--94eb2c0b927c4d9e83052faa5260--


From nobody Mon Apr  4 09:00:02 2016
Return-Path: <john-ietf@jck.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 9009F12D75E for <ietf@ietfa.amsl.com>; Mon,  4 Apr 2016 09:00:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] 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 02yez3P0-Gl5 for <ietf@ietfa.amsl.com>; Mon,  4 Apr 2016 08:59:58 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 09EBE12D720 for <ietf@ietf.org>; Mon,  4 Apr 2016 08:59:57 -0700 (PDT)
Received: from [198.252.137.10] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1an6uu-000JsJ-0V; Mon, 04 Apr 2016 11:59:52 -0400
Date: Mon, 04 Apr 2016 11:59:46 -0400
From: John C Klensin <john-ietf@jck.com>
To: Barry Leiba <barryleiba@computer.org>, Stephan Wenger <stewe@stewe.org>
Subject: Re: Last Call on draft-bradner-rfc3979bis-08.txt ("Intellectual Property Rights in IETF Technology")
Message-ID: <CEAF2AC89B6C8515496D0216@JcK-HP8200.jck.com>
In-Reply-To: <CALaySJKBrjKEdu-qd067Eb7A+nZFObB3TdwSV=od9GDjhDOecQ@mail.gmail.com>
References: <0000431F-F977-4A24-BA4D-064F740977A0@piuha.net> <56FBF599.9080605@ericsson.com> <ACC702C9-C33F-4D38-B47A-8BC293D24621@sobco.com> <DCA1B6AC-6221-4CF5-A726-E1E98DBFAC27@vigilsec.com> <56FC90E5.1050908@gmail.com> <CAC4RtVD3Pxm_vZgdCCgPgDwNfnYeKFJ5_Ys3QQPezrHzTGJE+Q@mail.gmail.com> <C5F35DA9-C530-4EC6-B175-C4B0A18872D7@stewe.org> <CALaySJ+1rvxXnXmLxk1UJ88t-e2p24OyMhR3f6P0peA5fLhRGA@mail.gmail.com> <CALaySJKBrjKEdu-qd067Eb7A+nZFObB3TdwSV=od9GDjhDOecQ@mail.gmail.c om>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/PY0HSZP3FMH00D2R3bFF4xgLJOY>
Cc: IETF <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: Mon, 04 Apr 2016 16:00:00 -0000

--On Monday, April 04, 2016 10:39 -0400 Barry Leiba
<barryleiba@computer.org> wrote:

> A follow-up here:
> 
> I'd be more comfortably with something more waffly, something
> more like this:
> 
> Without limiting the generality of the foregoing, acting as a
> working group chair or Area Director can often be considered
> "Participating" in all activities of the relevant working
> group or area; as such, working group chairs and Area
> Directors are expected to make a best, good-faith effort to
> carry out the responsibilities of Participants.
> 
> Or perhaps we want to separate WGCs from ADs here, and the
> text needs more work in any case, but I hope people see the
> general point.

FWIW, I agree with Barry about the general point, but let me go
a step further.  I think we have two main goals in all of this:
preventing someone from sneaking encumbered technology into a
standard (or other IETF specification) without the community
being aware of the encumbrance and avoiding the waste of time
associated with someone letting the specification development
process continue almost to the end before someone says "hey, we
have a patent on that, do you really want to go back and start
over?".   The other thing that is important to remember is that,
at least for a patent-holding organization, there is one
sanction far more serious than anything the IETF can impose, and
that is to try to enforce the patent and have a judge say "you
acted in a deceitful fashion, inconsistent with the intent of
patent laws, in getting people to use your technology, so the
patent is unenforceable".  That has actually occurred, multiple
times, in situations where IPR claims have met standards bodies.
I've been told that, in some cases, it has even resulted in
nasty sanctions against the patent-holder, sanctions that go
beyond invalidation or non-enforceability of the patent.

At least from the point of view of that kind of sanction --one
which many patent-holding organizations and their legal
departments are likely to take more seriously than the risk of
having to throw an IETF participant to the wolves-- it is very
important that our intent be as clear as possible.  If that
means saying something I think should be obvious, which is that
WG Chairs and ADs have extra decision-making authority and hence
bear responsibility for being extra-careful, I think that is
fine.

If someone really wants to Participate, Contribute, and
influence decisions while hiding IPR, or just to be
systematically careless about disclosures, they will find
loopholes to use as a basis for saying "I didn't _really_
violate the rules".  Ironically, if we really try to specify
every case and situation, we may create more such loopholes by
creating a basis for someone to say "they were really specific
about the cases that apply, this isn't an exact match for any of
those, so I didn't have to disclose". 

So let's try to step back a bit, be sure that the draft reflects
our intent as well as possible, and maybe even try to treat the
specific cases we do define as illustrative examples rather than
as rules that can be interpreted as more important than the
intent.

best,
    john
 



From nobody Mon Apr  4 09:46:11 2016
Return-Path: <michael.cameron@ericsson.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 8F68412D7BA for <ietf@ietfa.amsl.com>; Mon,  4 Apr 2016 09:46:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.202
X-Spam-Level: 
X-Spam-Status: No, score=-4.202 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001] 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 rutX19dRuOSU for <ietf@ietfa.amsl.com>; Mon,  4 Apr 2016 09:46:08 -0700 (PDT)
Received: from usplmg21.ericsson.net (usplmg21.ericsson.net [198.24.6.65]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7C44212D7A1 for <ietf@ietf.org>; Mon,  4 Apr 2016 09:46:02 -0700 (PDT)
X-AuditID: c6180641-f79fa6d0000057a9-c3-57029a24bf1d
Received: from EUSAAHC002.ericsson.se (Unknown_Domain [147.117.188.78]) by usplmg21.ericsson.net (Symantec Mail Security) with SMTP id 28.D4.22441.42A92075; Mon,  4 Apr 2016 18:45:24 +0200 (CEST)
Received: from EUSAAMB101.ericsson.se ([147.117.188.118]) by EUSAAHC002.ericsson.se ([147.117.188.78]) with mapi id 14.03.0248.002; Mon, 4 Apr 2016 12:46:00 -0400
From: Michael Cameron <michael.cameron@ericsson.com>
To: John C Klensin <john-ietf@jck.com>, Barry Leiba <barryleiba@computer.org>,  Stephan Wenger <stewe@stewe.org>
Subject: RE: Last Call on draft-bradner-rfc3979bis-08.txt ("Intellectual Property Rights in IETF Technology")
Thread-Topic: Last Call on draft-bradner-rfc3979bis-08.txt ("Intellectual Property Rights in IETF Technology")
Thread-Index: AQHRjnfzmax8zcYcXU2c7vOCh1JumZ96HvaAgAADXICAAANHAIAAFokA///B3YA=
Date: Mon, 4 Apr 2016 16:46:00 +0000
Message-ID: <36BAA6A693139D4BBCB37CCCA660E08A14FBFE94@eusaamb101.ericsson.se>
References: <0000431F-F977-4A24-BA4D-064F740977A0@piuha.net> <56FBF599.9080605@ericsson.com> <ACC702C9-C33F-4D38-B47A-8BC293D24621@sobco.com> <DCA1B6AC-6221-4CF5-A726-E1E98DBFAC27@vigilsec.com> <56FC90E5.1050908@gmail.com> <CAC4RtVD3Pxm_vZgdCCgPgDwNfnYeKFJ5_Ys3QQPezrHzTGJE+Q@mail.gmail.com> <C5F35DA9-C530-4EC6-B175-C4B0A18872D7@stewe.org> <CALaySJ+1rvxXnXmLxk1UJ88t-e2p24OyMhR3f6P0peA5fLhRGA@mail.gmail.com> <CALaySJKBrjKEdu-qd067Eb7A+nZFObB3TdwSV=od9GDjhDOecQ@mail.gmail.c om> <CEAF2AC89B6C8515496D0216@JcK-HP8200.jck.com>
In-Reply-To: <CEAF2AC89B6C8515496D0216@JcK-HP8200.jck.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [147.117.188.9]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFupjkeLIzCtJLcpLzFFi42KZXLrHT1dlFlO4wYS34haHFl9itXi2cT6L ReulP2wW1xs3sTuweLSs6mX2WLLkJ5PH5ZWvmT0Wr3/PGMASxWWTkpqTWZZapG+XwJUxcedx 9oJ/HBUL7s1lbmBcwd7FyMkhIWAi0du8nwXCFpO4cG89WxcjF4eQwFFGiVNTlrGBJIQEljFK bOiv6mLk4GADanj+DKxeRKBQ4uq3CUwgNrOAhMT1Ce/AbGGBfIn7N3pZIWoKJM7/PcgC0ioi 4CfxfGUOSJhFQEVi7uZuRhCbV8BXYt/Pu1Br57NIPJy2lhkkwSlgJfF3XRuYzQh02/dTa6B2 iUvcejKfCeJmAYkle84zQ9iiEi8f/2OFsBUl9vVPZ4eo15FYsPsTG4StLbFs4WtmiMWCEidn PmGZwCg2C8nYWUhaZiFpmYWkZQEjyypGjtLigpzcdCPDTYzAWDomwea4g3Fvr+chRgEORiUe 3gWnGMOFWBPLiitzDzFKcDArifBunsYULsSbklhZlVqUH19UmpNafIhRmoNFSZzXO/JfmJBA emJJanZqakFqEUyWiYNTqoFxW8fpmbz7ppzhLWVbx5ZWGfd3AZdC2DfWyIZYUYbbT77OOSpe uit366/Ktt0+uecXXP0iyqV5tnHVl6s7qu05CxL5LQSVQ5RkY55P/ezSwfV3S+3PP2+3znlw rHWqs+Zp8fN+YrdCHe8entfxa/OtDDvOi3uv7W/aYeBivSVKzmSR5olvH2ZxK7EUZyQaajEX FScCALlD+eChAgAA
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/F2gyrb3Cq5CNE2pX1kTLZh3J928>
Cc: IETF <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: Mon, 04 Apr 2016 16:46:09 -0000

"A best, good faith effort" would place on Participants the highest legal s=
tandard of care--possibly requiring an AD or WG chair to affirmatively sear=
ch their IP portfolio and map the claims (~20 claims per patent) of each re=
levant patent against each IETF draft in their domain. Is it realistic to t=
hink that Cisco, Juniper, Huawei and others similarly situated would retain=
 an army of IP professionals just to ensure that the AD/WG chair can meet t=
his standard? Or will these companies just require that their employees no =
longer "Participate" in IETF activities?

As far as non-IETF sanctions, you are probably thinking of the Rambus-JEDEC=
 matter. I am not aware of any situation where an IETF Participant has cons=
ciously hidden patents while pushing an IETF standard, and then, once the s=
tandard has been adopted, asserted the patents.  So long as a Participant i=
s an active participant, that is, someone actively pushing the Contribution=
 in some fashion, and not someone who "should have known", and is then cons=
ciously aware of possible IPR, only then does the duty to disclose arise.=20

Best, Mike


From nobody Mon Apr  4 10:52:48 2016
Return-Path: <ben@nostrum.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 1C78112D173 for <ietf@ietfa.amsl.com>; Mon,  4 Apr 2016 10:52:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] 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 os_uuVhvVX1i for <ietf@ietfa.amsl.com>; Mon,  4 Apr 2016 10:52:45 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (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 0D31B12D13D for <ietf@ietf.org>; Mon,  4 Apr 2016 10:52:45 -0700 (PDT)
Received: from [31.133.176.150] (dhcp-b096.meeting.ietf.org [31.133.176.150]) (authenticated bits=0) by nostrum.com (8.15.2/8.14.9) with ESMTPSA id u34HqdE0070371 (version=TLSv1 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Mon, 4 Apr 2016 12:52:41 -0500 (CDT) (envelope-from ben@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host dhcp-b096.meeting.ietf.org [31.133.176.150] claimed to be [31.133.176.150]
From: "Ben Campbell" <ben@nostrum.com>
To: "Barry Leiba" <barryleiba@computer.org>
Subject: Re: Last Call on draft-bradner-rfc3979bis-08.txt ("Intellectual Property Rights in IETF Technology")
Date: Mon, 04 Apr 2016 14:52:33 -0300
Message-ID: <0E61E57B-BC17-40A9-AB36-D74AD1B0C070@nostrum.com>
In-Reply-To: <CAC4RtVD3Pxm_vZgdCCgPgDwNfnYeKFJ5_Ys3QQPezrHzTGJE+Q@mail.gmail.com>
References: <0000431F-F977-4A24-BA4D-064F740977A0@piuha.net> <56FBF599.9080605@ericsson.com> <ACC702C9-C33F-4D38-B47A-8BC293D24621@sobco.com> <DCA1B6AC-6221-4CF5-A726-E1E98DBFAC27@vigilsec.com> <56FC90E5.1050908@gmail.com> <CAC4RtVD3Pxm_vZgdCCgPgDwNfnYeKFJ5_Ys3QQPezrHzTGJE+Q@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; format=flowed
X-Mailer: MailMate (1.9.4r5234)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/1oy3bHxwXaLfCf-0MagHCDezsbw>
Cc: IETF <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: Mon, 04 Apr 2016 17:52:47 -0000

On 4 Apr 2016, at 10:43, Barry Leiba wrote:

>>> So, one might argue that an AD can be unaware that a particular
>>> document includes something that needs to be disclosed up to the
>>> point that they take some action on that document, such as 
>>> sponsoring it.
>>
>> Yes, but is that an issue? The AD is only required to disclose when
>> she is "reasonably and personally aware" of the need for a 
>> disclosure,
>> which will presumably become the case when she actually reads the 
>> draft
>> (or sees the slides that describe the technology in question).
>
> Be careful here: I think it is an issue.
>
> The "reasonably and personally aware" applies to the IPR, not to the
> participation.  If I'm participating in active discussion about
> Section 4 of document X, and I should be reasonably and personally
> aware of IPR my employer holds with respect to Section 3 of document
> X, we aren't going to happily accept that I didn't read Section 3 so I
> don't have a responsibility to disclose.
>
> If we're saying that, say, ADs are considered to be Participants with
> respect to every document and discussion in every working group in the
> area -- and I see why some people think that's wise and appropriate --
> then we're saying that I have a responsibility to disclose whether or
> not I've read the documents, and waiting until AD Evaluation state
> would be a late disclosure.  Consider that the working group might
> have been proceeding for a couple of years and many I-D revisions
> under the assumption that the technology is unencumbered... and then I
> dump an IPR statement on them just as they've finished.
>
> This really is a tough one: it would be nice if the late disclosure
> didn't happen, but ADs can't reasonably be expected to read every
> draft in every working group early on... and, as others have said, it
> would be very bad if this disclosure requirement gave us even fewer AD
> candidates than we have now.

I think it's a bit worse than that. IIUC, the document also says that 
the act of participating asserts that the participant has the authority 
to disclose any related IPR. That seems to mean that, by accepting an AD 
role, one asserts they have authority to disclose IPR on any draft or 
discussion that anyone might ever have in their area. I think its highly 
likely that some sponsors would object to such an open-ended assertion 
if they understood it.

Ben.


From nobody Mon Apr  4 11:44:42 2016
Return-Path: <john-ietf@jck.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 A67EF12D7A5 for <ietf@ietfa.amsl.com>; Mon,  4 Apr 2016 11:44:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] 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 sgBjdQFxJQbu for <ietf@ietfa.amsl.com>; Mon,  4 Apr 2016 11:44:39 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B8B2A12D76F for <ietf@ietf.org>; Mon,  4 Apr 2016 11:44:39 -0700 (PDT)
Received: from [198.252.137.10] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1an9UF-000KP1-Hk; Mon, 04 Apr 2016 14:44:31 -0400
Date: Mon, 04 Apr 2016 14:44:26 -0400
From: John C Klensin <john-ietf@jck.com>
To: Michael Cameron <michael.cameron@ericsson.com>, Barry Leiba <barryleiba@computer.org>, Stephan Wenger <stewe@stewe.org>
Subject: RE: Last Call on draft-bradner-rfc3979bis-08.txt ("Intellectual Property Rights in IETF Technology")
Message-ID: <7BAD31C4390960DB0C577B05@JcK-HP8200.jck.com>
In-Reply-To: <36BAA6A693139D4BBCB37CCCA660E08A14FBFE94@eusaamb101.ericsson.se>
References: <0000431F-F977-4A24-BA4D-064F740977A0@piuha.net> <56FBF599.9080605@ericsson.com> <ACC702C9-C33F-4D38-B47A-8BC293D24621@sobco.com> <DCA1B6AC-6221-4CF5-A726-E1E98DBFAC27@vigilsec.com> <56FC90E5.1050908@gmail.com> <CAC4RtVD3Pxm_vZgdCCgPgDwNfnYeKFJ5_Ys3QQPezrHzTGJE+Q@mail.gmail.com> <C5F35DA9-C530-4EC6-B175-C4B0A18872D7@stewe.org> <CALaySJ+1rvxXnXmLxk1UJ88t-e2p24OyMhR3f6P0peA5fLhRGA@mail.gmail.com> <CALaySJKBrjKEdu-qd067Eb7A+nZFObB3TdwSV=od9GDjhDOecQ@mail.gmail.c om> <CEAF2AC89B6C8515496D0216@JcK-HP8200.jck.com> <36BAA6A693139D4BBCB37CCCA660E08A14FBFE94@eusaamb101.ericsson.se>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/KFz4ll16DbN5MErYMm1lDwx2BfU>
Cc: IETF <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: Mon, 04 Apr 2016 18:44:41 -0000

--On Monday, April 04, 2016 16:46 +0000 Michael Cameron
<michael.cameron@ericsson.com> wrote:

> "A best, good faith effort" would place on Participants the
> highest legal standard of care--possibly requiring an AD or WG
> chair to affirmatively search their IP portfolio and map the
>...

Which is exactly why I did not suggest that or any other wording
that has specific legal implications.

> As far as non-IETF sanctions, you are probably thinking of the
> Rambus-JEDEC matter.

No, actually, I wasn't.   For some years, I sat on ANSI's
Information Systems Standards Board which, at the time, oversaw
ANSI SDOs in the general IT area (including IEEE and what was
then X3) and the US TAG to ISO TC 97 and then ISO/IEC JTC1.  In
that role, I got a major earful about these issues (in both US
and "international" flavors) from professionals and attorneys
with specific specialties in the area.

> I am not aware of any situation where an
> IETF Participant has consciously hidden patents while pushing
> an IETF standard, and then, once the standard has been
> adopted, asserted the patents.

Nor am I.  But I'm not sure what "hasn't happened so far"
implies.  The consensus in the community has been that we
shouldn't wait for something bad to happen before we put good
policies in place.   I don't think "hasn't happened" it is an
argument for hair-splitting rules which is all I'm arguing
against.

>  So long as a Participant is an
> active participant, that is, someone actively pushing the
> Contribution in some fashion, and not someone who "should have
> known", and is then consciously aware of possible IPR, only
> then does the duty to disclose arise. 

But that is not the current, consensus, judgment and 3979 rule
although that category of people is the most clear.  In
particular, if someone is going to make decisions about, e.g.,
whether consensus exists about a particular issue or document,
and they are aware of relevant IPR (or, by the way, anything
that might constitute a broadly-construed conflict of interest),
I want to be absolutely sure they are obligated to disclose,
even if they have not publicly said a word consistent with
"actively pushing the contribution".

For the case of ADs, being very clear about that might result in
more situations in which someone who hasn't read a document
"voting" "I haven't read this and therefore abstain" rather than
voting "no objection" on the grounds that, having not read the
document and not seen anything bad in reviews, they don't see a
reason to object.   IMO, that might actually be a desirable side
effect.

To be explicit given Ben's note, I'd consider it entirely
reasonable for an AD who suspects a particular document or WG
work area might, if reviewed and understood, require an IPR
disclosure that other commitments (like day job obligations)
would not permit to isolate herself from the specification, and
discussions of and decisions about it and then not disclose.
That is not "recuse" in the sense sometimes used of
participating in discussions but not voting.  It is complete
isolation.  I'd hope it would also be explicit, perhaps in the
form of a statement like "I don't know or cannot discuss if my
organization has IPR that would interact with that WG or not
but, if were to have such IPR, I couldn't disclose it and
therefore do no want to participate in or contribute to any
aspect of that work or evaluation of it".  If a given AD avoided
work by making statements like that too often, I'd expect
Nomcoms to take notice in evaluating performance (or possibly
calls for resignation), but that is really a different matter.

Again, I think it is lots more important that we be clear about
intent -- and allow ADs ways to avoid being crushed between IETF
and employer rules by stepping back-- than it is that we try to
make specific rules covering every case.

    john




From nobody Mon Apr  4 12:15:52 2016
Return-Path: <john-ietf@jck.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 71FB012D806 for <ietf@ietfa.amsl.com>; Mon,  4 Apr 2016 12:15:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] 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 gfPBJP_D6Tg2 for <ietf@ietfa.amsl.com>; Mon,  4 Apr 2016 12:15:48 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6670012D80E for <ietf@ietf.org>; Mon,  4 Apr 2016 12:15:48 -0700 (PDT)
Received: from [198.252.137.10] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1an9yS-000KYU-Go; Mon, 04 Apr 2016 15:15:44 -0400
Date: Mon, 04 Apr 2016 15:15:39 -0400
From: John C Klensin <john-ietf@jck.com>
To: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>, Jari Arkko <jari.arkko@piuha.net>, IETF <ietf@ietf.org>
Subject: Re: Last Call on draft-bradner-rfc3979bis-08.txt ("Intellectual Property Rights in IETF Technology")
Message-ID: <F99F459688AAAFCDCD5D9CC1@JcK-HP8200.jck.com>
In-Reply-To: <56FBF599.9080605@ericsson.com>
References: <0000431F-F977-4A24-BA4D-064F740977A0@piuha.net> <56FBF599.9080605@ericsson.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/6ZK4clQ_FO7iY1lggd0gzhCu95k>
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: Mon, 04 Apr 2016 19:15:50 -0000

--On Wednesday, March 30, 2016 18:49 +0300 Gonzalo Camarillo
<Gonzalo.Camarillo@ericsson.com> wrote:

>>       Without limiting the generality of the
>>       foregoing, acting as a working group chair or Area
>>       Director constitutes "Participating" in all activities
>>       of the relevant working group or area.
> 
> The AD of a large area may not get to read all individual I-Ds
> or all email messages sent in all the WGs of the area. We may
> want to define this a bit more explicitly.

Gonzalo,

This seems to be the most useful recent comment to which to
respond, after which I'm going back to lurking...

Following up on my response to Michael, I'd like to suggest
drawing the line in a different place and, if necessary, doing
it very explicitly.   While, as you point out, the AD in a large
area may not read every document, I think it is reasonable for
the community to assume that every AD reads every draft charter.
I think it is reasonable for an AD to be expected to have a
general sense of when a particular set a tasks or work area
might interact with work, and actual or potential IPR claims,
about which he or she is at least generally aware, at charter
time.  I think it is entirely appropriate for such an AD to take
a role in focusing a charter to explicitly include or exclude
particular work that might be relevant in either IPR or more
general conflict of interest terms.  But then I think the
community should want such ADs, if they are not in a position to
disclose should such IPR claims actually arise, to be completely
and formally isolated from the relevant work.  I'd prefer, but
not require, that the reasons for such an isolation decision be
explicitly disclosed to the community.   From one point of view,
this is why we have a moderately large IESG and more than one AD
in most areas.

FWIW, I note that undisclosed IPR is only one of the reasons for
such an isolation principle.  If an AD works for an organization
that has not announced, but is about to release, a product that
would interact with a WG's proposed work and could not disclose
the planned product (even if no IPR claims were intended and
whether the WG ultimately produced a standard that aligned with
the product or not), I'd want that AD isolated from influence
over decisions about that WG too.  In a way, that makes the rule
for ADs just like that for ordinary WG participants: the price
of contributing or otherwise participating in a way that could
influence decisions is disclosure.

Another aspect of my reaction to Barry's comment is that, given
other changes in the IETF in the last 11 years, I'd really like
to see 3979bis recast as a matter of ethical obligations to the
IETF and fellow participants, with specific legal (or other)
requirements stated as corollaries to those ethical principles
rather than as standalone rules. 

FWIW, that view is very much influenced by Sam Hartman's
comments a week or two ago in which he focused, it seemed to me,
on what he as a participant wants or needs to know rather than
on conformance to specific legalistic rules.  It certainly did
not occur to me when 3668 and 3979 were being developed, but,
especially in the context of our current collection of rules for
good behavior (and prohibitions on various sorts of bad
behavior), concentrating on defining and encouraging ethical
behavior seems a better approach now.

    john



From nobody Mon Apr  4 13:07:19 2016
Return-Path: <stewe@stewe.org>
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 D341B12D75E for <ietf@ietfa.amsl.com>; Mon,  4 Apr 2016 13:07:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] 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 LoCPSrkMuPh9 for <ietf@ietfa.amsl.com>; Mon,  4 Apr 2016 13:07:15 -0700 (PDT)
Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1bon0707.outbound.protection.outlook.com [IPv6:2a01:111:f400:fc10::1:707]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 620F612D14B for <ietf@ietf.org>; Mon,  4 Apr 2016 13:07:15 -0700 (PDT)
Received: from BLUPR17MB0275.namprd17.prod.outlook.com (10.162.235.146) by BLUPR17MB0274.namprd17.prod.outlook.com (10.162.235.145) with Microsoft SMTP Server (TLS) id 15.1.447.15; Mon, 4 Apr 2016 20:06:56 +0000
Received: from BLUPR17MB0275.namprd17.prod.outlook.com ([10.162.235.146]) by BLUPR17MB0275.namprd17.prod.outlook.com ([10.162.235.146]) with mapi id 15.01.0447.027; Mon, 4 Apr 2016 20:06:56 +0000
From: Stephan Wenger <stewe@stewe.org>
To: Barry Leiba <barryleiba@computer.org>
Subject: Re: Last Call on draft-bradner-rfc3979bis-08.txt ("Intellectual Property Rights in IETF Technology")
Thread-Topic: Last Call on draft-bradner-rfc3979bis-08.txt ("Intellectual Property Rights in IETF Technology")
Thread-Index: AQHRhDTbKR9yu1RueEWA9RrAiHSISp9yLyaAgAAKyYCAAE/KAIAAXo6AgAb/NoD//9ajAIAANauAgAADRgCAAClHgA==
Date: Mon, 4 Apr 2016 20:06:56 +0000
Message-ID: <972C83CB-99B7-4278-9962-9AF67CFE890E@stewe.org>
References: <0000431F-F977-4A24-BA4D-064F740977A0@piuha.net> <56FBF599.9080605@ericsson.com> <ACC702C9-C33F-4D38-B47A-8BC293D24621@sobco.com> <DCA1B6AC-6221-4CF5-A726-E1E98DBFAC27@vigilsec.com> <56FC90E5.1050908@gmail.com> <CAC4RtVD3Pxm_vZgdCCgPgDwNfnYeKFJ5_Ys3QQPezrHzTGJE+Q@mail.gmail.com> <C5F35DA9-C530-4EC6-B175-C4B0A18872D7@stewe.org> <CALaySJ+1rvxXnXmLxk1UJ88t-e2p24OyMhR3f6P0peA5fLhRGA@mail.gmail.com> <CALaySJKBrjKEdu-qd067Eb7A+nZFObB3TdwSV=od9GDjhDOecQ@mail.gmail.com>
In-Reply-To: <CALaySJKBrjKEdu-qd067Eb7A+nZFObB3TdwSV=od9GDjhDOecQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: computer.org; dkim=none (message not signed) header.d=none;computer.org; dmarc=none action=none header.from=stewe.org;
x-ms-exchange-messagesentrepresentingtype: 1
x-originating-ip: [31.133.179.232]
x-ms-office365-filtering-correlation-id: 26541a95-90be-4bea-b04a-08d35cc4ac5f
x-microsoft-exchange-diagnostics: 1; BLUPR17MB0274; 5:k6bLnRZIYBq74pSBDNNk0y/3XT5vfCI1cDn8/baJXKzCWZIs/v9pO/o2UdgAK0L1iFQlzwDQyYHwywmxso9i32vroVlDnhH8YHGPxuuH96sZ9kCNWqsQHB1lkDsa5ARtzqNRLOkpuXbJFgM2cDds1A==; 24:CdIQrb2Lk3scapAQdVw6s8FAPuiZUJ3OSArNSLDHLvlUnsk5KFEwVt6SjzQmRvrqxVpmUscFvMsZcs7yp56UNVrTmsxJ2fvcYfCry3mGbdI=
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:BLUPR17MB0274;
x-microsoft-antispam-prvs: <BLUPR17MB02747FB7C9AC5B99CA0CB85AAE9D0@BLUPR17MB0274.namprd17.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040046)(601004)(2401047)(5005006)(8121501046)(3002001)(10201501046)(6041046)(6043046); SRVR:BLUPR17MB0274; BCL:0; PCL:0; RULEID:; SRVR:BLUPR17MB0274; 
x-forefront-prvs: 0902222726
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(53754006)(377454003)(24454002)(50986999)(2950100001)(76176999)(4326007)(54356999)(3280700002)(5008740100001)(2906002)(2900100001)(66066001)(36756003)(87936001)(1220700001)(81166005)(1096002)(10400500002)(77096005)(3846002)(92566002)(102836003)(586003)(11100500001)(6116002)(19580395003)(19580405001)(99286002)(16236675004)(83716003)(82746002)(33656002)(122556002)(5004730100002)(110136002)(189998001)(86362001)(3660700001)(106116001)(5002640100001)(230783001)(42262002)(104396002); DIR:OUT; SFP:1102; SCL:1; SRVR:BLUPR17MB0274; H:BLUPR17MB0275.namprd17.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en; 
spamdiagnosticoutput: 1:23
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_972C83CB99B7427899629AF67CFE890Esteweorg_"
MIME-Version: 1.0
X-OriginatorOrg: stewe.org
X-MS-Exchange-CrossTenant-originalarrivaltime: 04 Apr 2016 20:06:56.2481 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 865fc51c-5fae-4322-98ef-0121a85df0b6
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BLUPR17MB0274
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/icR2koD2u45x-5ZF6EfedlSR3nQ>
Cc: IETF <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: Mon, 04 Apr 2016 20:07:18 -0000

--_000_972C83CB99B7427899629AF67CFE890Esteweorg_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

SGkgYWxsLA0KDQpCYXJyeSBhbmQgSSBoYWQgYSBjaGF0IGFib3V0IHRoaXMuICBJIGFsc28gaGFk
IG9mZmxpbmUgY29udmVyc2F0aW9ucyB3aXRoIE1pa2UgQ2FtZXJvbiBhbmQgYSBjaGF0IHdpdGgg
Sm9lbC4gIEJhcnJ5IGFuZCBJIGF0IGxlYXN0IGFncmVlIG9uIHRoZSBwcm9ibGVtcy4gIFRoZSBz
b2x1dGlvbnMgYXJlIG1pbmUgZm9yIG5vdywgYW5kIHRoZXkgYWJzb2x1dGVseSBhcmUgaW4gbmVl
ZCBvZiB3b3Jkc21pdGhpbmcuLi4NCg0KQmFzZWQgb24gdGhlIGRpc2N1c3Npb24gc28gZmFyLCB0
aGVyZSBzZWVtIHRvIGJlIGEgbmVlZCBmb3IgdGhlIGZvbGxvd2luZzoNCg0KMS4gQSBjbGFyaWZp
Y2F0aW9uIHRoYXQgYW4gQUQsIGJ5IHRoZSBuYXR1cmUgb2YgaGlzL2hlciBvZmZpY2UsIHJlZ3Vs
YXJseSBiZWNvbWVzIGF3YXJlIG9mIENvbnRyaWJ1dGlvbnMgbGF0ZSBpbiB0aGUgcHJvY2VzcyAo
Zm9yIGV4YW1wbGUgYXQgSUVURiBMYXN0IENhbGwpIGFuZCwgdGhlcmVmb3JlLCBjYW5ub3QgYmUg
ZXhwZWN0ZWQgdG8gZGlzY2xvc2UgYW55IElQUiBDb3ZlcmluZyB0aG9zZSBDb250cmlidXRpb25z
IHVudGlsIHN1Y2ggbGF0ZSB0aW1lIGluIHRoZSBwcm9jZXNzLg0KVG8gZml4IHRoaXMgcG9pbnQs
IGEgc2ltcGxlIGV4cGxhbmF0b3J5IHNlbnRlbmNlIHNvbWV3aGVyZSBpbiBzZWN0aW9uIDUuMi4y
IHdvdWxkIHN1ZmZpY2UuICBGb3IgZXhhbXBsZSDigJxCeSB0aGUgbmF0dXJlIG9mIHRoZWlyIG9m
ZmljZSwgSUVURiBhcmVhIGRpcmVjdG9ycyByZWd1bGFybHkgYmVjb21lIGF3YXJlIG9mIENvbnRy
aWJ1dGlvbnMgbGF0ZSBpbiB0aGUgcHJvY2VzcyAoZm9yIGV4YW1wbGUgYXQgSUVURiBMYXN0IENh
bGwpIGFuZCwgdGhlcmVmb3JlIGFuZCBpbiBzdWNoIGNhc2VzLCBjYW5ub3QgYmUgZXhwZWN0ZWQg
dG8gZGlzY2xvc2UgYW55IElQUiBDb3ZlcmluZyB0aG9zZSBDb250cmlidXRpb25zIHVudGlsIHN1
Y2ggbGF0ZSB0aW1lIGluIHRoZSBwcm9jZXNzLuKAnQ0KDQpUaGUgcHVycG9zZSBvZiB0aGlzIHNl
bnRlbmNlIGlzIHRvIHByb3RlY3QgYW4gQUQgYW5kIGl0cyBzcG9uc29yaW5nIGNvbXBhbnkgZnJv
bSBhbGxlZ2F0aW9ucywgYm90aCB3aXRoaW4gdGhlIElFVEYgYW5kIGluIGNvdXJ0cywgdGhhdCB0
aGV5IGRpc2Nsb3NlZCBsYXRlIGFnYWluc3QgcG9saWN5Lg0KDQoyLiBBIGNsYXJpZmljYXRpb24g
b3IsIG1vcmUgbGlrZWx5LCBhIHN1YnN0YW50aWFsIGNoYW5nZSB0aGF0LCBsaWtlIGFueSBvdGhl
ciBpbmRpdmlkdWFsIGluIHRoZSBJRVRGLCBhbHNvIGFuIEFEIGhhcyB0aGUgb3B0aW9uIHRvIHJl
Y3VzZSBoaW1zZWxmIGZyb20gaW52b2x2aW5nIGhpbXNlbGYvaGVyc2VsZiBpbiB0aGUgZGVjaXNp
b24gbWFraW5nIHByb2Nlc3Mgb2YgYSBkb2N1bWVudCwgZXZlbiBhIGRvY3VtZW50IGluIGhpcyBv
d24gYXJlYS4gRm9yIGV4YW1wbGUsIGFuIEFEIHRoYXQgZGlkIG5ldmVyIGNvbW1lbnQgb24gYSBk
b2N1bWVudCBhbmQgYWJzdGFpbmVkIGR1cmluZyB0aGUgSUVURiBMYXN0IENhbGwgd291bGQgbm90
IGluY3VyIGEgZGlzY2xvc3VyZSBvYmxpZ2F0aW9uLCBldmVuIGlmIHRoZSBDb250cmlidXRpb24g
d2VyZSBpbiBoaXMvaGVyIG93biBhcmVhLg0KDQpUaGlzIHNlY29uZCBwb2ludCBpcyBtb3JlIHRy
aWNreS4gIElzIHRoZSBmb3JtdWxhdGlvbiBjdXJyZW50bHkgaW4gdGhlIGRyYWZ0LCB3aGljaCBk
ZWZpbmVzIEFEcyBhcyBQYXJ0aWNpcGFudHMsIGlubGluZSB3aXRoIHdoYXTigJlzIHdyaXR0ZW4g
aW4gcG9pbnQgMj8gIEnigJltIGNvbWluZyBhcm91bmQgdG8gdGhpbmsgdGhhdCBpdCBkb2VzIG5v
dC4gIEluc3RlYWQsIEkgdGhpbmsgd2UgaGF2ZSBhIGNvbnRyYWRpY3Rpb24gaW4gdGhlIGN1cnJl
bnQgZHJhZnTigJRvbiBvbmUgaGFuZCwgYW4gQUQgd2hvIGludGVudGlvbmFsbHkgc3RheXMgYXdh
eSBmcm9tIGluZmx1ZW5jaW5nIHRoZSBkZWNpc2lvbiBwcm9jZXNzIHJlZ2FyZGluZyBhIENvbnRy
aWJ1dGlvbiBzaG91bGQgbm90IGluY3VyIGFuIG9ibGlnYXRpb24gYmFzZWQgb24gdGhlIHVuZGVy
bHlpbmcgcHJpbmNpcGxlIG9mIHRoZSBwb2xpY3nigJRubyBtb3JlIHRoYW4gYW55b25lIGVsc2U7
IGJ1dCB0aGUgdGV4dCBhYm91dCBBRHMgYmVpbmcgUGFydGljaXBhbnRzIHJ1bGVzIG91dCB0aGF0
IGludGVycHJldGF0aW9uLiAgSGF2aW5nIGNvbnRyYWRpY3Rpb25zIGluIHBhdGVudCBwb2xpY2ll
cyBpcyBhIFZlcnkgQmFkIElkZWEgc2luY2UgYXQgbGVhc3QgUmFtYnVzIChjYS4gMjAwMykuICBJ
cyB0aGF0IGNvcnJlY3Qgc28gZmFyPw0KDQpCYXNlZCBvbiB0aGUgY3VycmVudCBmb3JtdWxhdGlv
biwgYW5kIHdpdGhvdXQgdmlvbGF0aW5nIHRoZSBwb2xpY3ksIGFuIEFEIHdobyBpcyB1bmRlciB0
aGUgZ3VuIG9mIGhpcyBJUFIgZGVwYXJ0bWVudCBub3QgdG8gZGlzY2xvc2UgYSBzcGVjaWZpYyBJ
UFIgaGFzIG9ubHkgdGhlIG9wdGlvbiB0byBzdGVwIGRvd24uICBJcyB0aGlzIHdoYXQgd2Ugd2Fu
dCBpbiBlYWNoIGFuZCBldmVyeSBjYXNlPyAgT3Igd291bGQgd2UgcmF0aGVyIGJlIHByYWdtYXRp
YyBhbmQgYWxsb3cgYW4gQUQgdG8gcmVjdXNlIGhpbXNlbGYvaGVyc2VsZiBvY2Nhc2lvbmFsbHk/
ICBJZiB5ZXMsIEkgdGhpbmsgd2UgbmVlZCBsYW5ndWFnZSBpbmRpY2F0aW5nIHRoYXQgc3VjaCBh
IG1lY2hhbmlzbSBpcyBhdmFpbGFibGUsIGJ1dCBhbHNvIGlzIG1lYW50IHRvIGJlIHVzZWQgc3Bh
cnNlbHksIGFuZCBhdCBsZWFzdCBpbXBseWluZyB0aGF0IEFEcyB3aG8gYXJlIGZvcmNlZCB0byB1
c2UgaXQgbW9yZSB0aGFuIHVuZGVyIGV4Y2VwdGlvbmFsIGNpcmN1bXN0YW5jZXMgYXJlIGluZGVl
ZCB0byBzdGVwIGRvd24uDQoNClRoZSBwYXJhZ3JhcGggYmVsb3cgdHJpZXMgdG8gZXhwcmVzcyB0
aGlzLiAgVGhlIG1hcmt1cCB3aWxsIHByb2JhYmx5IG9ubHkgYmUgdmlzaWJsZSBpZiB5b3UgY2hv
b3NlIHRvIHZpZXcgdGhlIEhUTUwgdmVyc2lvbiBvZiB0aGlzIGVtYWlsLg0KDQrigJwNCmsuICJQ
YXJ0aWNpcGF0aW5nIGluIGFuIElFVEYgZGlzY3Vzc2lvbiBvciBhY3Rpdml0eSI6IG1lYW5zIG1h
a2luZyBhDQpDb250cmlidXRpb24sIGFzIGRlc2NyaWJlZCBhYm92ZSwgb3IgaW4gYW55IG90aGVy
IHdheSBhY3RpbmcgaW4NCm9yZGVyIHRvIGluZmx1ZW5jZSB0aGUgb3V0Y29tZSBvZiBhIGRpc2N1
c3Npb24gcmVsYXRpbmcgdG8gdGhlDQpJRVRGIFN0YW5kYXJkcyBQcm9jZXNzLiBXaXRob3V0IGxp
bWl0aW5nIHRoZSBnZW5lcmFsaXR5IG9mIHRoZQ0KZm9yZWdvaW5nLCBhY3RpbmcgYXMgYSB3b3Jr
aW5nIGdyb3VwIGNoYWlyIG9yIEFyZWEgRGlyZWN0b3INCmNvbnN0aXR1dGVzICJQYXJ0aWNpcGF0
aW5nIiBpbiBhbGwgYWN0aXZpdGllcyBvZiB0aGUgcmVsZXZhbnQNCndvcmtpbmcgZ3JvdXAgb3Ig
YXJlYS4gIlBhcnRpY2lwYW50IiBhbmQgIklFVEYgUGFydGljaXBhbnQiIG1lYW4NCmFueSBpbmRp
dmlkdWFsIFBhcnRpY2lwYXRpbmcgaW4gYW4gSUVURiBkaXNjdXNzaW9uIG9yIGFjdGl2aXR5LiAg
VW5kZXINCmV4dHJhb3JkaW5hcnkgY2lyY3Vtc3RhbmNlcyBvbmx5LCBhbiBBRCBtYXkgY2hvb3Nl
IG5vdCB0byBQYXJ0aWNpcGF0ZQ0KaW4gdGhlIGRpc2N1c3Npb24gb3IgYWN0aXZpdHkgb2YgaGlz
L2hlciBhcmVhLCByZWN1c2UgaGltc2VsZi9oZXJzZWxmDQpmcm9tIElFU0cgZGVsaWJlcmF0aW9u
cyBvZiByZWxhdGVkIGRvY3VtZW50cywgYW5kIGFic3RhaW4gZHVyaW5nDQp0aGUgSUVTRyBiYWxs
b3QgcHJvY2VzcywgdGhlcmVieSBub3QgaW5jdXJyaW5nIHRoZSBvYmxpZ2F0aW9ucyBiYXNlZA0K
b24gUGFydGljaXBhdGluZy4NCiINCg0KU3RlcGhhbg0KDQoNCk9uIDQvNC8xNiwgMTE6MzksICJi
YXJyeWxlaWJhQGdtYWlsLmNvbTxtYWlsdG86YmFycnlsZWliYUBnbWFpbC5jb20+IG9uIGJlaGFs
ZiBvZiBCYXJyeSBMZWliYSIgPGJhcnJ5bGVpYmFAZ21haWwuY29tPG1haWx0bzpiYXJyeWxlaWJh
QGdtYWlsLmNvbT4gb24gYmVoYWxmIG9mIGJhcnJ5bGVpYmFAY29tcHV0ZXIub3JnPG1haWx0bzpi
YXJyeWxlaWJhQGNvbXB1dGVyLm9yZz4+IHdyb3RlOg0KDQpBIGZvbGxvdy11cCBoZXJlOg0KDQpJ
J2QgYmUgbW9yZSBjb21mb3J0YWJseSB3aXRoIHNvbWV0aGluZyBtb3JlIHdhZmZseSwgc29tZXRo
aW5nIG1vcmUgbGlrZSB0aGlzOg0KDQpXaXRob3V0IGxpbWl0aW5nIHRoZSBnZW5lcmFsaXR5IG9m
IHRoZSBmb3JlZ29pbmcsIGFjdGluZyBhcyBhIHdvcmtpbmcNCmdyb3VwIGNoYWlyIG9yIEFyZWEg
RGlyZWN0b3IgY2FuIG9mdGVuIGJlIGNvbnNpZGVyZWQgIlBhcnRpY2lwYXRpbmciDQppbiBhbGwg
YWN0aXZpdGllcyBvZiB0aGUgcmVsZXZhbnQgd29ya2luZyBncm91cCBvciBhcmVhOyBhcyBzdWNo
LA0Kd29ya2luZyBncm91cCBjaGFpcnMgYW5kIEFyZWEgRGlyZWN0b3JzIGFyZSBleHBlY3RlZCB0
byBtYWtlIGEgYmVzdCwNCmdvb2QtZmFpdGggZWZmb3J0IHRvIGNhcnJ5IG91dCB0aGUgcmVzcG9u
c2liaWxpdGllcyBvZiBQYXJ0aWNpcGFudHMuDQoNCk9yIHBlcmhhcHMgd2Ugd2FudCB0byBzZXBh
cmF0ZSBXR0NzIGZyb20gQURzIGhlcmUsIGFuZCB0aGUgdGV4dCBuZWVkcw0KbW9yZSB3b3JrIGlu
IGFueSBjYXNlLCBidXQgSSBob3BlIHBlb3BsZSBzZWUgdGhlIGdlbmVyYWwgcG9pbnQuDQoNCkJh
cnJ5DQoNCk9uIE1vbiwgQXByIDQsIDIwMTYgYXQgMTA6MjcgQU0sIEJhcnJ5IExlaWJhIDxiYXJy
eWxlaWJhQGNvbXB1dGVyLm9yZzxtYWlsdG86YmFycnlsZWliYUBjb21wdXRlci5vcmc+PiB3cm90
ZToNClRoZSAicmVhc29uYWJseSBhbmQgcGVyc29uYWxseSBhd2FyZSIgYXBwbGllcyB0byB0aGUg
SVBSLCBub3QgdG8gdGhlDQpwYXJ0aWNpcGF0aW9uLg0KDQpJIHRoaW5rIHRoaXMgaXMgaW5jb3Jy
ZWN0Lg0KDQpBY2NvcmRpbmcgdG8gc2VjdGlvbiA1LjEuMiAoZGlzY2xvc3VyZSByZXF1aXJlbWVu
dCBiYXNlZCBvbg0KUGFydGljaXBhdGlvbiwgbm90IG93biBJUFIpLCBhIGRpc2Nsb3N1cmUgb2Js
aWdhdGlvbiBleGlzdHMgaWYg4oCcdGhlDQpQYXJ0aWNpcGFudCBiZWxpZXZlcyBDb3ZlcnMgb3Ig
bWF5IHVsdGltYXRlbHkgQ292ZXIgdGhhdA0KQ29udHJpYnV0aW9u4oCdLiAgSSBkb27igJl0IHRo
aW5rIGFueW9uZSBjb3VsZCBhcmd1ZSB0aGF0IGFuIEFEIGhhcyBhDQrigJxiZWxpZXZl4oCdIGlu
IGEgcGF0ZW50IG9yIGFwcGxpY2F0aW9uIGhlL3NoZSBpcyBhd2FyZSBvZiBDb3ZlcnMgYQ0KQ29u
dHJpYnV0aW9uIHdoZW4gaGUgaGFzIG5ldmVyIHNlZW4gdGhlIENvbnRyaWJ1dGlvbi4NCg0KV291
bGQgeW91IGFjY2VwdCAiSSBkaWRuJ3QgcmVhZCB0aGUgZHJhZnQiIGFzIGFuIGFjY2VwdGFibGUg
cmVhc29uDQp0aGF0IHNvbWVvbmUgZW5nYWdlZCBpbiBhY3RpdmUgZGlzY3Vzc2lvbiBvbiBhIGRy
YWZ0IGRpZG4ndCBkaXNjbG9zZT8NCg0KV2UgZG9uJ3QgaGF2ZSBkaWZmZXJlbnQgbGV2ZWxzIG9m
IENvbnRyaWJ1dG9yIGhlcmUuICBTb21lb25lIG1ha2luZyBhDQpDb250cmlidXRpb24gaGFzIGFu
IG9ibGlnYXRpb24gdG8gZGlzY2xvc2UsIGV2ZW4gaWYgcy9oZSB3YXMgb25lIG9mDQp0aG9zZSB3
aG8gc2FpZCwgIkkgZGlkbid0IHJlYWQgdGhlIGRyYWZ0LCBidXQuLi4uIiAgSWYgd2UgZGVjbGFy
ZSB0aGUNCkFEcyB0byBiZSBDb250cmlidXRvcnMsIHdoeSBkb2VzIHRoZSBzYW1lIG5vdCBhcHBs
eSB0byB0aGVtPw0KDQpBIGxhdGUgZGlzY2xvc3VyZSBpcyBiZXR0ZXIgdGhhbiBubyBkaXNjbG9z
dXJlDQoNCkkgaG9wZSB3ZSBhbGwgYWdyZWUgb24gdGhhdCENCg0KY2xlYXJseSwgYW4gQUQNCmhh
cyBhIG11Y2ggYmV0dGVyIGp1c3RpZmljYXRpb24gb2YgbWFraW5nIHN1Y2ggYSBsYXRlIGRpc2Ns
b3N1cmUuICBJDQp3b3VsZCBob3BlIHRoYXQgbm8gb25lIHdvdWxkIGNvbXBsYWluIGlmIGFuIEFE
IG1ha2VzIGEgbGF0ZSBkaXNjbG9zdXJlDQphbmQsIHdoZW4gYXNrZWQgZm9yIHRoZSByZWFzb24g
b2YgbGF0ZW5lc3MsIGhlIHNheXMg4oCcSSB3YXMgbm90DQpyZXNwb25zaWJsZSBBRDsgSSBjYW1l
IGFjcm9zcyB0aGlzIGR1cmluZyBmaW5hbCByZXZpZXcgaW4gSUVURiBsYXN0DQpjYWxsLCBhbmQg
anVzdCBpZGVudGlmaWVkIHRoaXMuIOKAnCAgSW4gZmFjdCwgcGVvcGxlIHNob3VsZCBhcHByZWNp
YXRlDQp0aGlzLg0KDQpNYXliZSBzbywgYnV0IGFzIGl0IHN0YW5kcyBub3cgaW4gdGhlIGRvY3Vt
ZW50LCBpdCdzIHN0aWxsIGEgbGF0ZQ0KZGlzY2xvc3VyZSwgYW5kIHRoZXJlIG1pZ2h0IHN0aWxs
IGJlIGJhY2tsYXNoLCBsZWdhbCBjb25jZXJucyBieQ0KZW1wbG95ZXJzLCBhbmQgcmVsdWN0YW5j
ZSB0byBwdXQgcGVvcGxlIGluIHRoYXQgcG9zaXRpb24uDQoNCklmIHRoYXQncyB0aGUgY29uc2Vu
c3VzLCB0aGVuIHRoZXJlIHdlIGhhdmUgaXQuLi4gYnV0IEkgdGhpbmsgd2UNCnNob3VsZCBiZSB2
ZXJ5IGNhcmVmdWwgYWJvdXQgdW5pbnRlbmRlZCBjb25zZXF1ZW5jZXMgb2YgdGhpcyBvbmUuDQoN
CkJhcnJ5DQoNCg==

--_000_972C83CB99B7427899629AF67CFE890Esteweorg_
Content-Type: text/html; charset="utf-8"
Content-ID: <96245A707D5076488406C7AA805AD96A@namprd17.prod.outlook.com>
Content-Transfer-Encoding: base64

PGh0bWw+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIgY29udGVudD0i
dGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjwvaGVhZD4NCjxib2R5IHN0eWxlPSJ3b3JkLXdy
YXA6IGJyZWFrLXdvcmQ7IC13ZWJraXQtbmJzcC1tb2RlOiBzcGFjZTsgLXdlYmtpdC1saW5lLWJy
ZWFrOiBhZnRlci13aGl0ZS1zcGFjZTsiPg0KPGRpdj4NCjxkaXYgc3R5bGU9ImNvbG9yOiByZ2Io
MCwgMCwgMCk7IGZvbnQtZmFtaWx5OiBDYWxpYnJpLCBzYW5zLXNlcmlmOyBmb250LXNpemU6IDE0
cHg7Ij4NCkhpIGFsbCw8L2Rpdj4NCjxkaXYgc3R5bGU9ImNvbG9yOiByZ2IoMCwgMCwgMCk7IGZv
bnQtZmFtaWx5OiBDYWxpYnJpLCBzYW5zLXNlcmlmOyBmb250LXNpemU6IDE0cHg7Ij4NCjxicj4N
CjwvZGl2Pg0KPGRpdiBzdHlsZT0iY29sb3I6IHJnYigwLCAwLCAwKTsgZm9udC1mYW1pbHk6IENh
bGlicmksIHNhbnMtc2VyaWY7IGZvbnQtc2l6ZTogMTRweDsiPg0KQmFycnkgYW5kIEkgaGFkIGEg
Y2hhdCBhYm91dCB0aGlzLiAmbmJzcDtJIGFsc28gaGFkIG9mZmxpbmUgY29udmVyc2F0aW9ucyB3
aXRoIE1pa2UgQ2FtZXJvbiBhbmQgYSBjaGF0IHdpdGggSm9lbC4gJm5ic3A7QmFycnkgYW5kIEkg
YXQgbGVhc3QgYWdyZWUgb24gdGhlIHByb2JsZW1zLiAmbmJzcDtUaGUgc29sdXRpb25zIGFyZSBt
aW5lIGZvciBub3csIGFuZCB0aGV5IGFic29sdXRlbHkgYXJlIGluIG5lZWQgb2Ygd29yZHNtaXRo
aW5nLi4uPC9kaXY+DQo8ZGl2IHN0eWxlPSJjb2xvcjogcmdiKDAsIDAsIDApOyBmb250LWZhbWls
eTogQ2FsaWJyaSwgc2Fucy1zZXJpZjsgZm9udC1zaXplOiAxNHB4OyI+DQo8YnI+DQo8L2Rpdj4N
CjxkaXYgc3R5bGU9ImNvbG9yOiByZ2IoMCwgMCwgMCk7IGZvbnQtZmFtaWx5OiBDYWxpYnJpLCBz
YW5zLXNlcmlmOyBmb250LXNpemU6IDE0cHg7Ij4NCkJhc2VkIG9uIHRoZSBkaXNjdXNzaW9uIHNv
IGZhciwgdGhlcmUgc2VlbSB0byBiZSBhIG5lZWQgZm9yIHRoZSBmb2xsb3dpbmc6PC9kaXY+DQo8
ZGl2IHN0eWxlPSJjb2xvcjogcmdiKDAsIDAsIDApOyBmb250LWZhbWlseTogQ2FsaWJyaSwgc2Fu
cy1zZXJpZjsgZm9udC1zaXplOiAxNHB4OyI+DQo8YnI+DQo8L2Rpdj4NCjxkaXY+DQo8ZGl2IHN0
eWxlPSJjb2xvcjogcmdiKDAsIDAsIDApOyBmb250LWZhbWlseTogQ2FsaWJyaSwgc2Fucy1zZXJp
ZjsgZm9udC1zaXplOiAxNHB4OyI+DQoxLiBBIGNsYXJpZmljYXRpb24gdGhhdCBhbiBBRCwgYnkg
dGhlIG5hdHVyZSBvZiBoaXMvaGVyIG9mZmljZSwgcmVndWxhcmx5IGJlY29tZXMgYXdhcmUgb2Yg
Q29udHJpYnV0aW9ucyBsYXRlIGluIHRoZSBwcm9jZXNzIChmb3IgZXhhbXBsZSBhdCBJRVRGIExh
c3QgQ2FsbCkgYW5kLCB0aGVyZWZvcmUsIGNhbm5vdCBiZSBleHBlY3RlZCB0byBkaXNjbG9zZSBh
bnkgSVBSIENvdmVyaW5nIHRob3NlIENvbnRyaWJ1dGlvbnMgdW50aWwgc3VjaCBsYXRlDQogdGlt
ZSBpbiB0aGUgcHJvY2Vzcy48L2Rpdj4NCjxkaXYgc3R5bGU9ImNvbG9yOiByZ2IoMCwgMCwgMCk7
IGZvbnQtZmFtaWx5OiBDYWxpYnJpLCBzYW5zLXNlcmlmOyBmb250LXNpemU6IDE0cHg7Ij4NCjxk
aXY+VG8gZml4IHRoaXMgcG9pbnQsIGEgc2ltcGxlIGV4cGxhbmF0b3J5IHNlbnRlbmNlIHNvbWV3
aGVyZSBpbiBzZWN0aW9uIDUuMi4yIHdvdWxkIHN1ZmZpY2UuICZuYnNwO0ZvciBleGFtcGxlIOKA
nEJ5IHRoZSBuYXR1cmUgb2YgdGhlaXIgb2ZmaWNlLCBJRVRGIGFyZWEgZGlyZWN0b3JzJm5ic3A7
cmVndWxhcmx5IGJlY29tZSBhd2FyZSBvZiBDb250cmlidXRpb25zIGxhdGUgaW4gdGhlIHByb2Nl
c3MgKGZvciBleGFtcGxlIGF0IElFVEYgTGFzdCBDYWxsKSBhbmQsDQogdGhlcmVmb3JlIGFuZCBp
biBzdWNoIGNhc2VzLCBjYW5ub3QgYmUgZXhwZWN0ZWQgdG8gZGlzY2xvc2UgYW55IElQUiBDb3Zl
cmluZyB0aG9zZSBDb250cmlidXRpb25zIHVudGlsIHN1Y2ggbGF0ZSB0aW1lIGluIHRoZSBwcm9j
ZXNzLuKAnTwvZGl2Pg0KPGRpdj48YnI+DQo8L2Rpdj4NCjxkaXY+VGhlIHB1cnBvc2Ugb2YgdGhp
cyBzZW50ZW5jZSBpcyB0byBwcm90ZWN0IGFuIEFEIGFuZCBpdHMgc3BvbnNvcmluZyBjb21wYW55
IGZyb20gYWxsZWdhdGlvbnMsIGJvdGggd2l0aGluIHRoZSBJRVRGIGFuZCBpbiBjb3VydHMsIHRo
YXQgdGhleSBkaXNjbG9zZWQgbGF0ZSBhZ2FpbnN0IHBvbGljeS48L2Rpdj4NCjwvZGl2Pg0KPGRp
diBzdHlsZT0iY29sb3I6IHJnYigwLCAwLCAwKTsgZm9udC1mYW1pbHk6IENhbGlicmksIHNhbnMt
c2VyaWY7IGZvbnQtc2l6ZTogMTRweDsiPg0KPGJyPg0KPC9kaXY+DQo8ZGl2IHN0eWxlPSJjb2xv
cjogcmdiKDAsIDAsIDApOyBmb250LWZhbWlseTogQ2FsaWJyaSwgc2Fucy1zZXJpZjsgZm9udC1z
aXplOiAxNHB4OyI+DQoyLiBBIGNsYXJpZmljYXRpb24gb3IsIG1vcmUgbGlrZWx5LCBhIHN1YnN0
YW50aWFsIGNoYW5nZSB0aGF0LCBsaWtlIGFueSBvdGhlciBpbmRpdmlkdWFsIGluIHRoZSBJRVRG
LCBhbHNvIGFuIEFEIGhhcyB0aGUgb3B0aW9uIHRvIHJlY3VzZSBoaW1zZWxmIGZyb20gaW52b2x2
aW5nIGhpbXNlbGYvaGVyc2VsZiBpbiB0aGUgZGVjaXNpb24gbWFraW5nIHByb2Nlc3Mgb2YgYSBk
b2N1bWVudCwgZXZlbiBhIGRvY3VtZW50IGluIGhpcyBvd24gYXJlYS4gRm9yDQogZXhhbXBsZSwg
YW4gQUQgdGhhdCBkaWQgbmV2ZXIgY29tbWVudCBvbiBhIGRvY3VtZW50IGFuZCBhYnN0YWluZWQg
ZHVyaW5nIHRoZSBJRVRGIExhc3QgQ2FsbCB3b3VsZCBub3QgaW5jdXIgYSBkaXNjbG9zdXJlIG9i
bGlnYXRpb24sIGV2ZW4gaWYgdGhlIENvbnRyaWJ1dGlvbiB3ZXJlIGluIGhpcy9oZXIgb3duIGFy
ZWEuICZuYnNwOzwvZGl2Pg0KPGRpdiBzdHlsZT0iY29sb3I6IHJnYigwLCAwLCAwKTsgZm9udC1m
YW1pbHk6IENhbGlicmksIHNhbnMtc2VyaWY7IGZvbnQtc2l6ZTogMTRweDsiPg0KPGJyPg0KPC9k
aXY+DQo8ZGl2IHN0eWxlPSJjb2xvcjogcmdiKDAsIDAsIDApOyBmb250LWZhbWlseTogQ2FsaWJy
aSwgc2Fucy1zZXJpZjsgZm9udC1zaXplOiAxNHB4OyI+DQpUaGlzIHNlY29uZCBwb2ludCBpcyBt
b3JlIHRyaWNreS4gJm5ic3A7SXMgdGhlIGZvcm11bGF0aW9uIGN1cnJlbnRseSBpbiB0aGUgZHJh
ZnQsIHdoaWNoIGRlZmluZXMgQURzIGFzIFBhcnRpY2lwYW50cywgaW5saW5lIHdpdGggd2hhdOKA
mXMgd3JpdHRlbiBpbiBwb2ludCAyPyAmbmJzcDtJ4oCZbSBjb21pbmcgYXJvdW5kIHRvIHRoaW5r
IHRoYXQgaXQgZG9lcyBub3QuICZuYnNwO0luc3RlYWQsIEkgdGhpbmsgd2UgaGF2ZSBhIGNvbnRy
YWRpY3Rpb24gaW4gdGhlIGN1cnJlbnQgZHJhZnTigJRvbg0KIG9uZSBoYW5kLCBhbiBBRCB3aG8g
aW50ZW50aW9uYWxseSBzdGF5cyBhd2F5IGZyb20gaW5mbHVlbmNpbmcgdGhlIGRlY2lzaW9uIHBy
b2Nlc3MgcmVnYXJkaW5nIGEgQ29udHJpYnV0aW9uIHNob3VsZCBub3QgaW5jdXIgYW4gb2JsaWdh
dGlvbiBiYXNlZCBvbiB0aGUgdW5kZXJseWluZyBwcmluY2lwbGUgb2YgdGhlIHBvbGljeeKAlG5v
IG1vcmUgdGhhbiBhbnlvbmUgZWxzZTsgYnV0IHRoZSB0ZXh0IGFib3V0IEFEcyBiZWluZyBQYXJ0
aWNpcGFudHMgcnVsZXMNCiBvdXQgdGhhdCBpbnRlcnByZXRhdGlvbi4gJm5ic3A7SGF2aW5nIGNv
bnRyYWRpY3Rpb25zIGluIHBhdGVudCBwb2xpY2llcyBpcyBhIFZlcnkgQmFkIElkZWEgc2luY2Ug
YXQgbGVhc3QgUmFtYnVzIChjYS4gMjAwMykuICZuYnNwO0lzIHRoYXQgY29ycmVjdCBzbyBmYXI/
PC9kaXY+DQo8ZGl2IHN0eWxlPSJjb2xvcjogcmdiKDAsIDAsIDApOyBmb250LWZhbWlseTogQ2Fs
aWJyaSwgc2Fucy1zZXJpZjsgZm9udC1zaXplOiAxNHB4OyI+DQo8YnI+DQo8L2Rpdj4NCjxkaXYg
c3R5bGU9ImNvbG9yOiByZ2IoMCwgMCwgMCk7IGZvbnQtZmFtaWx5OiBDYWxpYnJpLCBzYW5zLXNl
cmlmOyBmb250LXNpemU6IDE0cHg7Ij4NCkJhc2VkIG9uIHRoZSBjdXJyZW50IGZvcm11bGF0aW9u
LCBhbmQgd2l0aG91dCB2aW9sYXRpbmcgdGhlIHBvbGljeSwgYW4gQUQgd2hvIGlzIHVuZGVyIHRo
ZSBndW4gb2YgaGlzIElQUiBkZXBhcnRtZW50IG5vdCB0byBkaXNjbG9zZSBhIHNwZWNpZmljIElQ
UiBoYXMgb25seSB0aGUgb3B0aW9uIHRvIHN0ZXAgZG93bi4gJm5ic3A7SXMgdGhpcyB3aGF0IHdl
IHdhbnQgaW4gZWFjaCBhbmQgZXZlcnkgY2FzZT8gJm5ic3A7T3Igd291bGQgd2UgcmF0aGVyIGJl
IHByYWdtYXRpYw0KIGFuZCBhbGxvdyBhbiBBRCB0byByZWN1c2UgaGltc2VsZi9oZXJzZWxmIG9j
Y2FzaW9uYWxseT8gJm5ic3A7SWYgeWVzLCBJIHRoaW5rIHdlIG5lZWQgbGFuZ3VhZ2UgaW5kaWNh
dGluZyB0aGF0IHN1Y2ggYSBtZWNoYW5pc20gaXMgYXZhaWxhYmxlLCBidXQgYWxzbyBpcyBtZWFu
dCB0byBiZSB1c2VkIHNwYXJzZWx5LCBhbmQgYXQgbGVhc3QgaW1wbHlpbmcgdGhhdCBBRHMgd2hv
IGFyZSBmb3JjZWQgdG8gdXNlIGl0IG1vcmUgdGhhbiB1bmRlciBleGNlcHRpb25hbA0KIGNpcmN1
bXN0YW5jZXMgYXJlIGluZGVlZCB0byBzdGVwIGRvd24uICZuYnNwOzwvZGl2Pg0KPGRpdiBzdHls
ZT0iY29sb3I6IHJnYigwLCAwLCAwKTsgZm9udC1mYW1pbHk6IENhbGlicmksIHNhbnMtc2VyaWY7
IGZvbnQtc2l6ZTogMTRweDsiPg0KPGJyPg0KPC9kaXY+DQo8ZGl2IHN0eWxlPSJjb2xvcjogcmdi
KDAsIDAsIDApOyBmb250LWZhbWlseTogQ2FsaWJyaSwgc2Fucy1zZXJpZjsgZm9udC1zaXplOiAx
NHB4OyI+DQpUaGUgcGFyYWdyYXBoIGJlbG93IHRyaWVzIHRvIGV4cHJlc3MgdGhpcy4gJm5ic3A7
VGhlIG1hcmt1cCB3aWxsIHByb2JhYmx5IG9ubHkgYmUgdmlzaWJsZSBpZiB5b3UgY2hvb3NlIHRv
IHZpZXcgdGhlIEhUTUwgdmVyc2lvbiBvZiB0aGlzIGVtYWlsLjwvZGl2Pg0KPGRpdiBzdHlsZT0i
Y29sb3I6IHJnYigwLCAwLCAwKTsgZm9udC1mYW1pbHk6IENhbGlicmksIHNhbnMtc2VyaWY7IGZv
bnQtc2l6ZTogMTRweDsiPg0KPGJyPg0KPC9kaXY+DQo8ZGl2IHN0eWxlPSJjb2xvcjogcmdiKDAs
IDAsIDApOyBmb250LWZhbWlseTogQ2FsaWJyaSwgc2Fucy1zZXJpZjsgZm9udC1zaXplOiAxNHB4
OyI+DQrigJw8L2Rpdj4NCjxkaXY+DQo8ZGl2IHN0eWxlPSJjb2xvcjogcmdiKDAsIDAsIDApOyBm
b250LWZhbWlseTogQ2FsaWJyaSwgc2Fucy1zZXJpZjsgZm9udC1zaXplOiAxNHB4OyI+DQo8c3Bh
biBjbGFzcz0iQXBwbGUtdGFiLXNwYW4iIHN0eWxlPSJ3aGl0ZS1zcGFjZTpwcmUiPjwvc3Bhbj5r
LiAmcXVvdDtQYXJ0aWNpcGF0aW5nIGluIGFuIElFVEYgZGlzY3Vzc2lvbiBvciBhY3Rpdml0eSZx
dW90OzogbWVhbnMgbWFraW5nIGE8L2Rpdj4NCjxkaXYgc3R5bGU9ImNvbG9yOiByZ2IoMCwgMCwg
MCk7IGZvbnQtZmFtaWx5OiBDYWxpYnJpLCBzYW5zLXNlcmlmOyBmb250LXNpemU6IDE0cHg7Ij4N
CjxzcGFuIGNsYXNzPSJBcHBsZS10YWItc3BhbiIgc3R5bGU9IndoaXRlLXNwYWNlOnByZSI+PC9z
cGFuPkNvbnRyaWJ1dGlvbiwgYXMgZGVzY3JpYmVkIGFib3ZlLCBvciBpbiBhbnkgb3RoZXIgd2F5
IGFjdGluZyBpbjwvZGl2Pg0KPGRpdiBzdHlsZT0iY29sb3I6IHJnYigwLCAwLCAwKTsgZm9udC1m
YW1pbHk6IENhbGlicmksIHNhbnMtc2VyaWY7IGZvbnQtc2l6ZTogMTRweDsiPg0KPHNwYW4gY2xh
c3M9IkFwcGxlLXRhYi1zcGFuIiBzdHlsZT0id2hpdGUtc3BhY2U6cHJlIj48L3NwYW4+b3JkZXIg
dG8gaW5mbHVlbmNlIHRoZSBvdXRjb21lIG9mIGEgZGlzY3Vzc2lvbiByZWxhdGluZyB0byB0aGU8
L2Rpdj4NCjxkaXYgc3R5bGU9ImNvbG9yOiByZ2IoMCwgMCwgMCk7IGZvbnQtZmFtaWx5OiBDYWxp
YnJpLCBzYW5zLXNlcmlmOyBmb250LXNpemU6IDE0cHg7Ij4NCjxzcGFuIGNsYXNzPSJBcHBsZS10
YWItc3BhbiIgc3R5bGU9IndoaXRlLXNwYWNlOnByZSI+PC9zcGFuPklFVEYgU3RhbmRhcmRzIFBy
b2Nlc3MuIFdpdGhvdXQgbGltaXRpbmcgdGhlIGdlbmVyYWxpdHkgb2YgdGhlPC9kaXY+DQo8ZGl2
IHN0eWxlPSJjb2xvcjogcmdiKDAsIDAsIDApOyBmb250LWZhbWlseTogQ2FsaWJyaSwgc2Fucy1z
ZXJpZjsgZm9udC1zaXplOiAxNHB4OyI+DQo8c3BhbiBjbGFzcz0iQXBwbGUtdGFiLXNwYW4iIHN0
eWxlPSJ3aGl0ZS1zcGFjZTpwcmUiPjwvc3Bhbj5mb3JlZ29pbmcsIGFjdGluZyBhcyBhIHdvcmtp
bmcgZ3JvdXAgY2hhaXINCjxzdHJpa2U+b3IgQXJlYSBEaXJlY3Rvcjwvc3RyaWtlPjwvZGl2Pg0K
PGRpdiBzdHlsZT0iY29sb3I6IHJnYigwLCAwLCAwKTsgZm9udC1mYW1pbHk6IENhbGlicmksIHNh
bnMtc2VyaWY7IGZvbnQtc2l6ZTogMTRweDsiPg0KPHNwYW4gY2xhc3M9IkFwcGxlLXRhYi1zcGFu
IiBzdHlsZT0id2hpdGUtc3BhY2U6cHJlIj48L3NwYW4+Y29uc3RpdHV0ZXMgJnF1b3Q7UGFydGlj
aXBhdGluZyZxdW90OyBpbiBhbGwgYWN0aXZpdGllcyBvZiB0aGUgcmVsZXZhbnQ8L2Rpdj4NCjxk
aXYgc3R5bGU9ImNvbG9yOiByZ2IoMCwgMCwgMCk7IGZvbnQtZmFtaWx5OiBDYWxpYnJpLCBzYW5z
LXNlcmlmOyBmb250LXNpemU6IDE0cHg7Ij4NCjxzcGFuIGNsYXNzPSJBcHBsZS10YWItc3BhbiIg
c3R5bGU9IndoaXRlLXNwYWNlOnByZSI+PC9zcGFuPndvcmtpbmcgZ3JvdXA8c3RyaWtlPiBvciBh
cmVhPC9zdHJpa2U+LiAmcXVvdDtQYXJ0aWNpcGFudCZxdW90OyBhbmQgJnF1b3Q7SUVURiBQYXJ0
aWNpcGFudCZxdW90OyBtZWFuPC9kaXY+DQo8ZGl2IHN0eWxlPSJjb2xvcjogcmdiKDAsIDAsIDAp
OyBmb250LWZhbWlseTogQ2FsaWJyaSwgc2Fucy1zZXJpZjsgZm9udC1zaXplOiAxNHB4OyI+DQo8
c3BhbiBjbGFzcz0iQXBwbGUtdGFiLXNwYW4iIHN0eWxlPSJ3aGl0ZS1zcGFjZTpwcmUiPjwvc3Bh
bj5hbnkgaW5kaXZpZHVhbCBQYXJ0aWNpcGF0aW5nIGluIGFuIElFVEYgZGlzY3Vzc2lvbiBvciBh
Y3Rpdml0eS4gJm5ic3A7PHU+VW5kZXImbmJzcDs8L3U+PC9kaXY+DQo8ZGl2IHN0eWxlPSJjb2xv
cjogcmdiKDAsIDAsIDApOyBmb250LWZhbWlseTogQ2FsaWJyaSwgc2Fucy1zZXJpZjsgZm9udC1z
aXplOiAxNHB4OyI+DQo8dT48c3BhbiBjbGFzcz0iQXBwbGUtdGFiLXNwYW4iIHN0eWxlPSJ3aGl0
ZS1zcGFjZTpwcmUiPjwvc3Bhbj5leHRyYW9yZGluYXJ5IGNpcmN1bXN0YW5jZXMgb25seSwgYW4g
QUQgbWF5IGNob29zZSBub3QgdG8gUGFydGljaXBhdGUmbmJzcDs8L3U+PC9kaXY+DQo8ZGl2IHN0
eWxlPSJjb2xvcjogcmdiKDAsIDAsIDApOyBmb250LWZhbWlseTogQ2FsaWJyaSwgc2Fucy1zZXJp
ZjsgZm9udC1zaXplOiAxNHB4OyI+DQo8dT48c3BhbiBjbGFzcz0iQXBwbGUtdGFiLXNwYW4iIHN0
eWxlPSJ3aGl0ZS1zcGFjZTpwcmUiPjwvc3Bhbj5pbiB0aGUgZGlzY3Vzc2lvbiBvciBhY3Rpdml0
eSBvZiBoaXMvaGVyIGFyZWEsIHJlY3VzZSBoaW1zZWxmL2hlcnNlbGYmbmJzcDs8L3U+PC9kaXY+
DQo8ZGl2IHN0eWxlPSJjb2xvcjogcmdiKDAsIDAsIDApOyBmb250LWZhbWlseTogQ2FsaWJyaSwg
c2Fucy1zZXJpZjsgZm9udC1zaXplOiAxNHB4OyI+DQo8dT48c3BhbiBjbGFzcz0iQXBwbGUtdGFi
LXNwYW4iIHN0eWxlPSJ3aGl0ZS1zcGFjZTpwcmUiPjwvc3Bhbj5mcm9tIElFU0cgZGVsaWJlcmF0
aW9ucyBvZiByZWxhdGVkIGRvY3VtZW50cywgYW5kIGFic3RhaW4gZHVyaW5nJm5ic3A7PC91Pjwv
ZGl2Pg0KPGRpdiBzdHlsZT0iY29sb3I6IHJnYigwLCAwLCAwKTsgZm9udC1mYW1pbHk6IENhbGli
cmksIHNhbnMtc2VyaWY7IGZvbnQtc2l6ZTogMTRweDsiPg0KPHU+PHNwYW4gY2xhc3M9IkFwcGxl
LXRhYi1zcGFuIiBzdHlsZT0id2hpdGUtc3BhY2U6cHJlIj48L3NwYW4+dGhlIElFU0cgYmFsbG90
IHByb2Nlc3MsIHRoZXJlYnkgbm90IGluY3VycmluZyB0aGUgb2JsaWdhdGlvbnMgYmFzZWQ8L3U+
PC9kaXY+DQo8ZGl2Pjx1PjxzcGFuIGNsYXNzPSJBcHBsZS10YWItc3BhbiIgc3R5bGU9ImNvbG9y
OiByZ2IoMCwgMCwgMCk7IGZvbnQtZmFtaWx5OiBDYWxpYnJpLCBzYW5zLXNlcmlmOyBmb250LXNp
emU6IDE0cHg7IHdoaXRlLXNwYWNlOiBwcmU7Ij48L3NwYW4+bzxmb250IGZhY2U9IkNhbGlicmks
c2Fucy1zZXJpZiI+biBQYXJ0aWNpcGF0aW5nLjwvZm9udD48L3U+PC9kaXY+DQo8L2Rpdj4NCjxk
aXYgc3R5bGU9ImNvbG9yOiByZ2IoMCwgMCwgMCk7IGZvbnQtZmFtaWx5OiBDYWxpYnJpLCBzYW5z
LXNlcmlmOyBmb250LXNpemU6IDE0cHg7Ij4NCiZxdW90OyAmbmJzcDs8L2Rpdj4NCjxkaXYgc3R5
bGU9ImNvbG9yOiByZ2IoMCwgMCwgMCk7IGZvbnQtZmFtaWx5OiBDYWxpYnJpLCBzYW5zLXNlcmlm
OyBmb250LXNpemU6IDE0cHg7Ij4NCjxicj4NCjwvZGl2Pg0KPGRpdiBzdHlsZT0iY29sb3I6IHJn
YigwLCAwLCAwKTsgZm9udC1mYW1pbHk6IENhbGlicmksIHNhbnMtc2VyaWY7IGZvbnQtc2l6ZTog
MTRweDsiPg0KU3RlcGhhbjwvZGl2Pg0KPC9kaXY+DQo8ZGl2IHN0eWxlPSJjb2xvcjogcmdiKDAs
IDAsIDApOyBmb250LWZhbWlseTogQ2FsaWJyaSwgc2Fucy1zZXJpZjsgZm9udC1zaXplOiAxNHB4
OyI+DQo8ZGl2IGlkPSJNQUNfT1VUTE9PS19TSUdOQVRVUkUiPg0KPGRpdj48YnI+DQo8L2Rpdj4N
CjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjxkaXYgc3R5bGU9ImNvbG9yOiByZ2IoMCwgMCwgMCk7
IGZvbnQtZmFtaWx5OiBDYWxpYnJpLCBzYW5zLXNlcmlmOyBmb250LXNpemU6IDE0cHg7Ij4NCjxi
cj4NCjwvZGl2Pg0KPGRpdiBzdHlsZT0iY29sb3I6IHJnYigwLCAwLCAwKTsgZm9udC1mYW1pbHk6
IENhbGlicmksIHNhbnMtc2VyaWY7IGZvbnQtc2l6ZTogMTRweDsiPg0KT24gNC80LzE2LCAxMToz
OSwgJnF1b3Q7PGEgaHJlZj0ibWFpbHRvOmJhcnJ5bGVpYmFAZ21haWwuY29tIj5iYXJyeWxlaWJh
QGdtYWlsLmNvbTwvYT4gb24gYmVoYWxmIG9mIEJhcnJ5IExlaWJhJnF1b3Q7ICZsdDs8YSBocmVm
PSJtYWlsdG86YmFycnlsZWliYUBnbWFpbC5jb20iPmJhcnJ5bGVpYmFAZ21haWwuY29tPC9hPiBv
biBiZWhhbGYgb2YNCjxhIGhyZWY9Im1haWx0bzpiYXJyeWxlaWJhQGNvbXB1dGVyLm9yZyI+YmFy
cnlsZWliYUBjb21wdXRlci5vcmc8L2E+Jmd0OyB3cm90ZTo8L2Rpdj4NCjxkaXYgc3R5bGU9ImNv
bG9yOiByZ2IoMCwgMCwgMCk7IGZvbnQtZmFtaWx5OiBDYWxpYnJpLCBzYW5zLXNlcmlmOyBmb250
LXNpemU6IDE0cHg7Ij4NCjxicj4NCjwvZGl2Pg0KPGJsb2NrcXVvdGUgaWQ9Ik1BQ19PVVRMT09L
X0FUVFJJQlVUSU9OX0JMT0NLUVVPVEUiIHN0eWxlPSJjb2xvcjogcmdiKDAsIDAsIDApOyBmb250
LWZhbWlseTogQ2FsaWJyaSwgc2Fucy1zZXJpZjsgZm9udC1zaXplOiAxNHB4OyBib3JkZXItbGVm
dC1jb2xvcjogcmdiKDE4MSwgMTk2LCAyMjMpOyBib3JkZXItbGVmdC13aWR0aDogNXB4OyBib3Jk
ZXItbGVmdC1zdHlsZTogc29saWQ7IHBhZGRpbmc6IDBweCAwcHggMHB4IDVweDsgbWFyZ2luOiAw
cHggMHB4IDBweCA1cHg7Ij4NCjxkaXY+QSBmb2xsb3ctdXAgaGVyZTo8L2Rpdj4NCjxkaXY+PGJy
Pg0KPC9kaXY+DQo8ZGl2PkknZCBiZSBtb3JlIGNvbWZvcnRhYmx5IHdpdGggc29tZXRoaW5nIG1v
cmUgd2FmZmx5LCBzb21ldGhpbmcgbW9yZSBsaWtlIHRoaXM6PC9kaXY+DQo8ZGl2Pjxicj4NCjwv
ZGl2Pg0KPGRpdj5XaXRob3V0IGxpbWl0aW5nIHRoZSBnZW5lcmFsaXR5IG9mIHRoZSBmb3JlZ29p
bmcsIGFjdGluZyBhcyBhIHdvcmtpbmc8L2Rpdj4NCjxkaXY+Z3JvdXAgY2hhaXIgb3IgQXJlYSBE
aXJlY3RvciBjYW4gb2Z0ZW4gYmUgY29uc2lkZXJlZCAmcXVvdDtQYXJ0aWNpcGF0aW5nJnF1b3Q7
PC9kaXY+DQo8ZGl2PmluIGFsbCBhY3Rpdml0aWVzIG9mIHRoZSByZWxldmFudCB3b3JraW5nIGdy
b3VwIG9yIGFyZWE7IGFzIHN1Y2gsPC9kaXY+DQo8ZGl2PndvcmtpbmcgZ3JvdXAgY2hhaXJzIGFu
ZCBBcmVhIERpcmVjdG9ycyBhcmUgZXhwZWN0ZWQgdG8gbWFrZSBhIGJlc3QsPC9kaXY+DQo8ZGl2
Pmdvb2QtZmFpdGggZWZmb3J0IHRvIGNhcnJ5IG91dCB0aGUgcmVzcG9uc2liaWxpdGllcyBvZiBQ
YXJ0aWNpcGFudHMuPC9kaXY+DQo8ZGl2Pjxicj4NCjwvZGl2Pg0KPGRpdj5PciBwZXJoYXBzIHdl
IHdhbnQgdG8gc2VwYXJhdGUgV0dDcyBmcm9tIEFEcyBoZXJlLCBhbmQgdGhlIHRleHQgbmVlZHM8
L2Rpdj4NCjxkaXY+bW9yZSB3b3JrIGluIGFueSBjYXNlLCBidXQgSSBob3BlIHBlb3BsZSBzZWUg
dGhlIGdlbmVyYWwgcG9pbnQuPC9kaXY+DQo8ZGl2Pjxicj4NCjwvZGl2Pg0KPGRpdj5CYXJyeTwv
ZGl2Pg0KPGRpdj48YnI+DQo8L2Rpdj4NCjxkaXY+T24gTW9uLCBBcHIgNCwgMjAxNiBhdCAxMDoy
NyBBTSwgQmFycnkgTGVpYmEgJmx0OzxhIGhyZWY9Im1haWx0bzpiYXJyeWxlaWJhQGNvbXB1dGVy
Lm9yZyI+YmFycnlsZWliYUBjb21wdXRlci5vcmc8L2E+Jmd0OyB3cm90ZTo8L2Rpdj4NCjxibG9j
a3F1b3RlIGlkPSJNQUNfT1VUTE9PS19BVFRSSUJVVElPTl9CTE9DS1FVT1RFIiBzdHlsZT0iQk9S
REVSLUxFRlQ6ICNiNWM0ZGYgNSBzb2xpZDsgUEFERElORzowIDAgMCA1OyBNQVJHSU46MCAwIDAg
NTsiPg0KPGJsb2NrcXVvdGUgaWQ9Ik1BQ19PVVRMT09LX0FUVFJJQlVUSU9OX0JMT0NLUVVPVEUi
IHN0eWxlPSJCT1JERVItTEVGVDogI2I1YzRkZiA1IHNvbGlkOyBQQURESU5HOjAgMCAwIDU7IE1B
UkdJTjowIDAgMCA1OyI+DQo8YmxvY2txdW90ZSBpZD0iTUFDX09VVExPT0tfQVRUUklCVVRJT05f
QkxPQ0tRVU9URSIgc3R5bGU9IkJPUkRFUi1MRUZUOiAjYjVjNGRmIDUgc29saWQ7IFBBRERJTkc6
MCAwIDAgNTsgTUFSR0lOOjAgMCAwIDU7Ij4NCjxkaXY+VGhlICZxdW90O3JlYXNvbmFibHkgYW5k
IHBlcnNvbmFsbHkgYXdhcmUmcXVvdDsgYXBwbGllcyB0byB0aGUgSVBSLCBub3QgdG8gdGhlPC9k
aXY+DQo8ZGl2PnBhcnRpY2lwYXRpb24uPC9kaXY+DQo8L2Jsb2NrcXVvdGU+DQo8ZGl2Pjxicj4N
CjwvZGl2Pg0KPGRpdj5JIHRoaW5rIHRoaXMgaXMgaW5jb3JyZWN0LjwvZGl2Pg0KPGRpdj48YnI+
DQo8L2Rpdj4NCjxkaXY+QWNjb3JkaW5nIHRvIHNlY3Rpb24gNS4xLjIgKGRpc2Nsb3N1cmUgcmVx
dWlyZW1lbnQgYmFzZWQgb248L2Rpdj4NCjxkaXY+UGFydGljaXBhdGlvbiwgbm90IG93biBJUFIp
LCBhIGRpc2Nsb3N1cmUgb2JsaWdhdGlvbiBleGlzdHMgaWYg4oCcdGhlPC9kaXY+DQo8ZGl2PlBh
cnRpY2lwYW50IGJlbGlldmVzIENvdmVycyBvciBtYXkgdWx0aW1hdGVseSBDb3ZlciB0aGF0PC9k
aXY+DQo8ZGl2PkNvbnRyaWJ1dGlvbuKAnS4mbmJzcDsmbmJzcDtJIGRvbuKAmXQgdGhpbmsgYW55
b25lIGNvdWxkIGFyZ3VlIHRoYXQgYW4gQUQgaGFzIGE8L2Rpdj4NCjxkaXY+4oCcYmVsaWV2ZeKA
nSBpbiBhIHBhdGVudCBvciBhcHBsaWNhdGlvbiBoZS9zaGUgaXMgYXdhcmUgb2YgQ292ZXJzIGE8
L2Rpdj4NCjxkaXY+Q29udHJpYnV0aW9uIHdoZW4gaGUgaGFzIG5ldmVyIHNlZW4gdGhlIENvbnRy
aWJ1dGlvbi48L2Rpdj4NCjwvYmxvY2txdW90ZT4NCjxkaXY+PGJyPg0KPC9kaXY+DQo8ZGl2Pldv
dWxkIHlvdSBhY2NlcHQgJnF1b3Q7SSBkaWRuJ3QgcmVhZCB0aGUgZHJhZnQmcXVvdDsgYXMgYW4g
YWNjZXB0YWJsZSByZWFzb248L2Rpdj4NCjxkaXY+dGhhdCBzb21lb25lIGVuZ2FnZWQgaW4gYWN0
aXZlIGRpc2N1c3Npb24gb24gYSBkcmFmdCBkaWRuJ3QgZGlzY2xvc2U/PC9kaXY+DQo8ZGl2Pjxi
cj4NCjwvZGl2Pg0KPGRpdj5XZSBkb24ndCBoYXZlIGRpZmZlcmVudCBsZXZlbHMgb2YgQ29udHJp
YnV0b3IgaGVyZS4mbmJzcDsmbmJzcDtTb21lb25lIG1ha2luZyBhPC9kaXY+DQo8ZGl2PkNvbnRy
aWJ1dGlvbiBoYXMgYW4gb2JsaWdhdGlvbiB0byBkaXNjbG9zZSwgZXZlbiBpZiBzL2hlIHdhcyBv
bmUgb2Y8L2Rpdj4NCjxkaXY+dGhvc2Ugd2hvIHNhaWQsICZxdW90O0kgZGlkbid0IHJlYWQgdGhl
IGRyYWZ0LCBidXQuLi4uJnF1b3Q7Jm5ic3A7Jm5ic3A7SWYgd2UgZGVjbGFyZSB0aGU8L2Rpdj4N
CjxkaXY+QURzIHRvIGJlIENvbnRyaWJ1dG9ycywgd2h5IGRvZXMgdGhlIHNhbWUgbm90IGFwcGx5
IHRvIHRoZW0/PC9kaXY+DQo8ZGl2Pjxicj4NCjwvZGl2Pg0KPGJsb2NrcXVvdGUgaWQ9Ik1BQ19P
VVRMT09LX0FUVFJJQlVUSU9OX0JMT0NLUVVPVEUiIHN0eWxlPSJCT1JERVItTEVGVDogI2I1YzRk
ZiA1IHNvbGlkOyBQQURESU5HOjAgMCAwIDU7IE1BUkdJTjowIDAgMCA1OyI+DQo8ZGl2PkEgbGF0
ZSBkaXNjbG9zdXJlIGlzIGJldHRlciB0aGFuIG5vIGRpc2Nsb3N1cmU8L2Rpdj4NCjwvYmxvY2tx
dW90ZT4NCjxkaXY+PGJyPg0KPC9kaXY+DQo8ZGl2PkkgaG9wZSB3ZSBhbGwgYWdyZWUgb24gdGhh
dCE8L2Rpdj4NCjxkaXY+PGJyPg0KPC9kaXY+DQo8YmxvY2txdW90ZSBpZD0iTUFDX09VVExPT0tf
QVRUUklCVVRJT05fQkxPQ0tRVU9URSIgc3R5bGU9IkJPUkRFUi1MRUZUOiAjYjVjNGRmIDUgc29s
aWQ7IFBBRERJTkc6MCAwIDAgNTsgTUFSR0lOOjAgMCAwIDU7Ij4NCjxkaXY+Y2xlYXJseSwgYW4g
QUQ8L2Rpdj4NCjxkaXY+aGFzIGEgbXVjaCBiZXR0ZXIganVzdGlmaWNhdGlvbiBvZiBtYWtpbmcg
c3VjaCBhIGxhdGUgZGlzY2xvc3VyZS4mbmJzcDsmbmJzcDtJPC9kaXY+DQo8ZGl2PndvdWxkIGhv
cGUgdGhhdCBubyBvbmUgd291bGQgY29tcGxhaW4gaWYgYW4gQUQgbWFrZXMgYSBsYXRlIGRpc2Ns
b3N1cmU8L2Rpdj4NCjxkaXY+YW5kLCB3aGVuIGFza2VkIGZvciB0aGUgcmVhc29uIG9mIGxhdGVu
ZXNzLCBoZSBzYXlzIOKAnEkgd2FzIG5vdDwvZGl2Pg0KPGRpdj5yZXNwb25zaWJsZSBBRDsgSSBj
YW1lIGFjcm9zcyB0aGlzIGR1cmluZyBmaW5hbCByZXZpZXcgaW4gSUVURiBsYXN0PC9kaXY+DQo8
ZGl2PmNhbGwsIGFuZCBqdXN0IGlkZW50aWZpZWQgdGhpcy4g4oCcJm5ic3A7Jm5ic3A7SW4gZmFj
dCwgcGVvcGxlIHNob3VsZCBhcHByZWNpYXRlPC9kaXY+DQo8ZGl2PnRoaXMuPC9kaXY+DQo8L2Js
b2NrcXVvdGU+DQo8ZGl2Pjxicj4NCjwvZGl2Pg0KPGRpdj5NYXliZSBzbywgYnV0IGFzIGl0IHN0
YW5kcyBub3cgaW4gdGhlIGRvY3VtZW50LCBpdCdzIHN0aWxsIGEgbGF0ZTwvZGl2Pg0KPGRpdj5k
aXNjbG9zdXJlLCBhbmQgdGhlcmUgbWlnaHQgc3RpbGwgYmUgYmFja2xhc2gsIGxlZ2FsIGNvbmNl
cm5zIGJ5PC9kaXY+DQo8ZGl2PmVtcGxveWVycywgYW5kIHJlbHVjdGFuY2UgdG8gcHV0IHBlb3Bs
ZSBpbiB0aGF0IHBvc2l0aW9uLjwvZGl2Pg0KPGRpdj48YnI+DQo8L2Rpdj4NCjxkaXY+SWYgdGhh
dCdzIHRoZSBjb25zZW5zdXMsIHRoZW4gdGhlcmUgd2UgaGF2ZSBpdC4uLiBidXQgSSB0aGluayB3
ZTwvZGl2Pg0KPGRpdj5zaG91bGQgYmUgdmVyeSBjYXJlZnVsIGFib3V0IHVuaW50ZW5kZWQgY29u
c2VxdWVuY2VzIG9mIHRoaXMgb25lLjwvZGl2Pg0KPGRpdj48YnI+DQo8L2Rpdj4NCjxkaXY+QmFy
cnk8L2Rpdj4NCjwvYmxvY2txdW90ZT4NCjxkaXY+PGJyPg0KPC9kaXY+DQo8L2Jsb2NrcXVvdGU+
DQo8L2JvZHk+DQo8L2h0bWw+DQo=

--_000_972C83CB99B7427899629AF67CFE890Esteweorg_--


From nobody Mon Apr  4 13:16:41 2016
Return-Path: <brian.e.carpenter@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 A1E2E12D858 for <ietf@ietfa.amsl.com>; Mon,  4 Apr 2016 13:16:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 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, RCVD_IN_DNSWL_LOW=-0.7, 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 14CXGHthMtwy for <ietf@ietfa.amsl.com>; Mon,  4 Apr 2016 13:16:39 -0700 (PDT)
Received: from mail-pa0-x235.google.com (mail-pa0-x235.google.com [IPv6:2607:f8b0:400e:c03::235]) (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 10C0512D852 for <ietf@ietf.org>; Mon,  4 Apr 2016 13:16:39 -0700 (PDT)
Received: by mail-pa0-x235.google.com with SMTP id fe3so150809699pab.1 for <ietf@ietf.org>; Mon, 04 Apr 2016 13:16:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=subject:to:references:from:organization:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=nuY53Xt1Ov43UVw/VdBNr425SPh56dBq44RfuD6tQgI=; b=DIsHSW+jXiBTmnMyBVYElAHMlf3JUAQouh8SPkRgtag1qiXiHzNhrcD1kjO9y8lx4x Kr+JAZjA3jt4XTGVBduc9DgothW/V6dmfVYBRemcgS8CrjQactcaEeVwbABgdDIN58y4 R6obPZS2+cyYDmWBZQIdYQtfvnV+835N9ZdRuEzRNCv4KYa1WITikAprzvBHT03zYw9s iuH4bAn243pyoi0X3ttJ6Djurni2Q6XvWdOOTqh54lOLwqA5GCd3SVKE5WblX7WWeXgG irS5fQug0uyM7RnO/fMb213IEvnkXjcX2v0xIzlLKXJJ/ZVlfmoJsMOusYKI87EB+p1Y qGxg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=nuY53Xt1Ov43UVw/VdBNr425SPh56dBq44RfuD6tQgI=; b=j8CYEx+8t2nQNLTfV9A510bMqrmZpED3YRcDA8aNd8uSH5xVDWV5R+yWE4Ktv1hSCI F1hB7CK7C96HvPIQNdjhKZ6E0R8ET90qV86mgBbDbr7Ur63Ic1P68BgCHZBoNBe7gP09 eiitmutH2Mwl1NKFQsVZRjX71byhJxW2dxxHZOtKOV5BH9GUNz5RlXUFYoCtg/XQrAH5 lQi7zzwT+t2qMAwC0EoUEFOYxF+U897/sSrvucrJ8Cby+N1JgtE0Y96sEAQEozWv8qDp 6dGlWhPEhyE3jTOp7T3x/qoSF0SwSh6JQdON6hDeihS63ER49dt1wGOCNsXtaiD4bdh5 cutg==
X-Gm-Message-State: AD7BkJLo86plZ0D1Tgdz9KkAnTL+FT6Alyr7itMP2G3Se7eg25HhdHvoIastZzHYZOQXMQ==
X-Received: by 10.66.231.73 with SMTP id te9mr7193316pac.62.1459800998605; Mon, 04 Apr 2016 13:16:38 -0700 (PDT)
Received: from ?IPv6:2406:e007:6365:1:28cc:dc4c:9703:6781? ([2406:e007:6365:1:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id tn5sm2263960pac.32.2016.04.04.13.16.34 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 04 Apr 2016 13:16:37 -0700 (PDT)
Subject: Re: Last Call on draft-bradner-rfc3979bis-08.txt ("Intellectual Property Rights in IETF Technology")
To: John C Klensin <john-ietf@jck.com>, Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>, Jari Arkko <jari.arkko@piuha.net>, IETF <ietf@ietf.org>
References: <0000431F-F977-4A24-BA4D-064F740977A0@piuha.net> <56FBF599.9080605@ericsson.com> <F99F459688AAAFCDCD5D9CC1@JcK-HP8200.jck.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <5702CBA2.2060802@gmail.com>
Date: Tue, 5 Apr 2016 08:16:34 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.7.0
MIME-Version: 1.0
In-Reply-To: <F99F459688AAAFCDCD5D9CC1@JcK-HP8200.jck.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/ewbaYfmVhwyAswa9eLA0d3ceJX4>
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: Mon, 04 Apr 2016 20:16:40 -0000

On 05/04/2016 07:15, John C Klensin wrote:

...
> FWIW, I note that undisclosed IPR is only one of the reasons for
> such an isolation principle.  If an AD works for an organization
> that has not announced, but is about to release, a product that
> would interact with a WG's proposed work and could not disclose
> the planned product (even if no IPR claims were intended and
> whether the WG ultimately produced a standard that aligned with
> the product or not), I'd want that AD isolated from influence
> over decisions about that WG too.  In a way, that makes the rule
> for ADs just like that for ordinary WG participants: the price
> of contributing or otherwise participating in a way that could
> influence decisions is disclosure.

Well, *exactly*. That's why I don't think that ADs or WGCs need to
be called out in any particular way: they participate and therefore
if they are reasonably and personally aware of IPR, they must disclose
(and if they can't disclose, they need to stop participating in
that particular case).

> Another aspect of my reaction to Barry's comment is that, given
> other changes in the IETF in the last 11 years, I'd really like
> to see 3979bis recast as a matter of ethical obligations to the
> IETF and fellow participants, with specific legal (or other)
> requirements stated as corollaries to those ethical principles
> rather than as standalone rules.

I'm sympathetic with that idea, but not being a lawyer I don't know
if it's feasible to truly separate them.

   Brian


From nobody Mon Apr  4 13:28:57 2016
Return-Path: <jari.arkko@piuha.net>
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 C9E7612D870 for <ietf@ietfa.amsl.com>; Mon,  4 Apr 2016 13:28:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] 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 meSerhQFx1hM for <ietf@ietfa.amsl.com>; Mon,  4 Apr 2016 13:28:53 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id A06CE12D182 for <ietf@ietf.org>; Mon,  4 Apr 2016 13:28:52 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 316D92CCE2; Mon,  4 Apr 2016 23:28:51 +0300 (EEST) (envelope-from jari.arkko@piuha.net)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id R8762RFcQtCK; Mon,  4 Apr 2016 23:28:50 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 4A2362CC9A; Mon,  4 Apr 2016 23:28:48 +0300 (EEST) (envelope-from jari.arkko@piuha.net)
Subject: Re: Last Call on draft-bradner-rfc3979bis-08.txt ("Intellectual Property Rights in IETF Technology")
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Content-Type: multipart/signed; boundary="Apple-Mail=_D09FE3C4-77A8-4C98-840C-177717C41293"; protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail 2.5.2
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <5702CBA2.2060802@gmail.com>
Date: Mon, 4 Apr 2016 17:28:46 -0300
Message-Id: <19FD9771-D4A1-4D1A-87BF-A11F2BEC3E6A@piuha.net>
References: <0000431F-F977-4A24-BA4D-064F740977A0@piuha.net> <56FBF599.9080605@ericsson.com> <F99F459688AAAFCDCD5D9CC1@JcK-HP8200.jck.com> <5702CBA2.2060802@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/AexnehTBHDvKrocb0R3PBzEWR5s>
Cc: John C Klensin <john-ietf@jck.com>, IETF <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: Mon, 04 Apr 2016 20:28:56 -0000

--Apple-Mail=_D09FE3C4-77A8-4C98-840C-177717C41293
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252


> Well, *exactly*. That's why I don't think that ADs or WGCs need to
> be called out in any particular way: they participate and therefore
> if they are reasonably and personally aware of IPR, they must disclose
> (and if they can't disclose, they need to stop participating in
> that particular case).

Right, and I think we all are actually in agreement over this.

Personally, I=92d love to see the draft talk about AD participation just =
like it talks about other people's participation. If I really haven=92t =
participated in WG X, well, I haven=92t, even if my co-AD owns the group =
:-) And if I did participate, well, I should declare the IPR that I know =
of :-)

Jari


--Apple-Mail=_D09FE3C4-77A8-4C98-840C-177717C41293
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQIcBAEBCgAGBQJXAs5/AAoJEM80gCTQU46qIfoQAKwAhccNH76E76HH7KZidw0T
g90A6kfPm6OahjPKsYBtSVGEZZBLZlFzeiIKL9qiK8SsgRwhXkCbZYAvUwSzMPct
8rkQanU7cU2/WpaBze5ar/ZnQlXc84mjuVpmjRk9eP2wJUau6s9DRQ2FmzJeQT/H
EsNe4I5udrTco1JrBwWzDwrun8pQqguA9hHtbo6ropKZzHZdjoODTwCslzYSO/p9
+qG0z99aU76swbH2B9PYQNmZ1KDjuOPWYbxVf0LqrEEKmrfKKGgz480XJFcg9jDN
IBvpB57HEqEy1EI53iuO6G05AbpKCnTB8m6Gxoe6+Bg7E4eKhyzjpl67Ijka4t8W
UvV6csRMAe11eOEr98/K0a1C30cfJjTc30OqMPvHZ0TRwcdb25R6TynvmP+oVR/u
+6gbY6i3v7YC1QZoaZ3eEzvZI1zrOcaANmP8AwHyXJxCWjXruonM9apO57RNjlT2
nueRemlMSkAiVq/JSnMpa0BAno9eqwzoQ+aGeRKPC0R5IZgrFtSIqcBDM+L8gWg/
0igtW0eMmfSWvAt3ZAa965uAf62kgnddJk7QphZZFykjbExx1hUfsFW6ZrbyvDXh
rQWtZ+8vqkTI0O25z0EroLJyDnYHb9SMjtXRmWkqWhKQ3KhArFc6FBf4AHxMkRRR
+QrAHhvTdievA15iTpPS
=K7w7
-----END PGP SIGNATURE-----

--Apple-Mail=_D09FE3C4-77A8-4C98-840C-177717C41293--


From nobody Mon Apr  4 13:47:01 2016
Return-Path: <sob@sobco.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 0409312D645 for <ietf@ietfa.amsl.com>; Mon,  4 Apr 2016 13:47:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.108
X-Spam-Level: 
X-Spam-Status: No, score=-1.108 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RDNS_NONE=0.793, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=no 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 axlF6x9bvBLQ for <ietf@ietfa.amsl.com>; Mon,  4 Apr 2016 13:46:58 -0700 (PDT)
Received: from sobco.sobco.com (unknown [136.248.127.164]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7D29612D0A2 for <ietf@ietf.org>; Mon,  4 Apr 2016 13:46:58 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by sobco.sobco.com (Postfix) with ESMTP id 8167C1AD0344; Mon,  4 Apr 2016 16:46:57 -0400 (EDT)
X-Virus-Scanned: amavisd-new at sobco.com
Received: from sobco.sobco.com ([127.0.0.1]) by localhost (sobco.sobco.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xGIqZFs6Dmme; Mon,  4 Apr 2016 16:46:56 -0400 (EDT)
Received: from dhcp-891f.meeting.ietf.org (unknown [31.133.138.31]) by sobco.sobco.com (Postfix) with ESMTPSA id A2C9F1AD0323; Mon,  4 Apr 2016 16:46:52 -0400 (EDT)
Content-Type: multipart/alternative; boundary="Apple-Mail=_8491FE47-1152-4610-BE8F-CDC12CF38CC0"
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Subject: Re: Last Call on draft-bradner-rfc3979bis-08.txt ("Intellectual Property Rights in IETF Technology")
From: Scott Bradner <sob@sobco.com>
In-Reply-To: <972C83CB-99B7-4278-9962-9AF67CFE890E@stewe.org>
Date: Mon, 4 Apr 2016 16:46:49 -0400
Message-Id: <1306B092-8C50-4916-88A1-0BC5F5FD51D1@sobco.com>
References: <0000431F-F977-4A24-BA4D-064F740977A0@piuha.net> <56FBF599.9080605@ericsson.com> <ACC702C9-C33F-4D38-B47A-8BC293D24621@sobco.com> <DCA1B6AC-6221-4CF5-A726-E1E98DBFAC27@vigilsec.com> <56FC90E5.1050908@gmail.com> <CAC4RtVD3Pxm_vZgdCCgPgDwNfnYeKFJ5_Ys3QQPezrHzTGJE+Q@mail.gmail.com> <C5F35DA9-C530-4EC6-B175-C4B0A18872D7@stewe.org> <CALaySJ+1rvxXnXmLxk1UJ88t-e2p24OyMhR3f6P0peA5fLhRGA@mail.gmail.com> <CALaySJKBrjKEdu-qd067Eb7A+nZFObB3TdwSV=od9GDjhDOecQ@mail.gmail.com> <972C83CB-99B7-4278-9962-9AF67CFE890E@stewe.org>
To: Stephan Wenger <stewe@stewe.org>
X-Mailer: Apple Mail (2.3124)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/nZebJiMaquMCYS5eGVafmbCwEs8>
Cc: Barry Leiba <barryleiba@computer.org>, IETF <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: Mon, 04 Apr 2016 20:47:00 -0000

--Apple-Mail=_8491FE47-1152-4610-BE8F-CDC12CF38CC0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8


> On Apr 4, 2016, at 4:06 PM, Stephan Wenger <stewe@stewe.org> wrote:
>=20
> Hi all,
>=20
> Barry and I had a chat about this.  I also had offline conversations =
with Mike Cameron and a chat with Joel.  Barry and I at least agree on =
the problems.  The solutions are mine for now, and they absolutely are =
in need of wordsmithing...
>=20
> Based on the discussion so far, there seem to be a need for the =
following:
>=20
> 1. A clarification that an AD, by the nature of his/her office, =
regularly becomes aware of Contributions late in the process (for =
example at IETF Last Call) and, therefore, cannot be expected to =
disclose any IPR Covering those Contributions until such late time in =
the process.
> To fix this point, a simple explanatory sentence somewhere in section =
5.2.2 would suffice.  For example =E2=80=9CBy the nature of their =
office, IETF area directors regularly become aware of Contributions late =
in the process (for example at IETF Last Call) and, therefore and in =
such cases, cannot be expected to disclose any IPR Covering those =
Contributions until such late time in the process.=E2=80=9D

this does not seem right

why not say=20
By the nature of their office, IETF area directors may become aware of =
Contributions late in the process (for example at IETF Last Call or =
during IESG review) and, therefore and in such cases, cannot be expected =
to disclose any IPR Covering those Contributions until they become aware =
of them.=E2=80=9D



--Apple-Mail=_8491FE47-1152-4610-BE8F-CDC12CF38CC0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D""><br class=3D""><div><blockquote type=3D"cite" class=3D""><div =
class=3D"">On Apr 4, 2016, at 4:06 PM, Stephan Wenger &lt;<a =
href=3D"mailto:stewe@stewe.org" class=3D"">stewe@stewe.org</a>&gt; =
wrote:</div><br class=3D"Apple-interchange-newline"><div class=3D"">

<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dutf-8" =
class=3D"">

<div style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space;" class=3D"">
<div class=3D"">
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px;" =
class=3D"">
Hi all,</div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px;" =
class=3D"">
<br class=3D"">
</div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px;" =
class=3D"">
Barry and I had a chat about this. &nbsp;I also had offline =
conversations with Mike Cameron and a chat with Joel. &nbsp;Barry and I =
at least agree on the problems. &nbsp;The solutions are mine for now, =
and they absolutely are in need of wordsmithing...</div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px;" =
class=3D"">
<br class=3D"">
</div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px;" =
class=3D"">
Based on the discussion so far, there seem to be a need for the =
following:</div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px;" =
class=3D"">
<br class=3D"">
</div>
<div class=3D"">
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px;" =
class=3D"">
1. A clarification that an AD, by the nature of his/her office, =
regularly becomes aware of Contributions late in the process (for =
example at IETF Last Call) and, therefore, cannot be expected to =
disclose any IPR Covering those Contributions until such late
 time in the process.</div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px;" =
class=3D"">
<div class=3D"">To fix this point, a simple explanatory sentence =
somewhere in section 5.2.2 would suffice. &nbsp;For example =E2=80=9CBy =
the nature of their office, IETF area directors&nbsp;regularly become =
aware of Contributions late in the process (for example at IETF Last =
Call) and,
 therefore and in such cases, cannot be expected to disclose any IPR =
Covering those Contributions until such late time in the =
process.=E2=80=9D</div></div></div></div></div></div></blockquote><div><br=
 class=3D""></div>this does not seem right</div><div><br =
class=3D""></div><div>why not say&nbsp;</div><div><div style=3D"margin: =
0px; font-size: 11px; line-height: normal; font-family: Menlo;" =
class=3D""><span style=3D"font-variant-ligatures: no-common-ligatures" =
class=3D"">By the nature of their office, IETF area directors may become =
aware of Contributions late in the process (for example at IETF Last =
Call or during IESG review) and, therefore and in such cases, cannot be =
expected to disclose any IPR Covering those Contributions until they =
become aware of them.=E2=80=9D</span></div></div><div><br =
class=3D""></div><br class=3D""></body></html>=

--Apple-Mail=_8491FE47-1152-4610-BE8F-CDC12CF38CC0--


From nobody Mon Apr  4 13:48:14 2016
Return-Path: <stewe@stewe.org>
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 6AE7412D815 for <ietf@ietfa.amsl.com>; Mon,  4 Apr 2016 13:48:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] 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 kvcwTNXCQDF2 for <ietf@ietfa.amsl.com>; Mon,  4 Apr 2016 13:48:09 -0700 (PDT)
Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1bon0758.outbound.protection.outlook.com [IPv6:2a01:111:f400:fc10::1:758]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3F03012D869 for <ietf@ietf.org>; Mon,  4 Apr 2016 13:48:09 -0700 (PDT)
Received: from BLUPR17MB0275.namprd17.prod.outlook.com (10.162.235.146) by BLUPR17MB0274.namprd17.prod.outlook.com (10.162.235.145) with Microsoft SMTP Server (TLS) id 15.1.447.15; Mon, 4 Apr 2016 20:47:49 +0000
Received: from BLUPR17MB0275.namprd17.prod.outlook.com ([10.162.235.146]) by BLUPR17MB0275.namprd17.prod.outlook.com ([10.162.235.146]) with mapi id 15.01.0447.027; Mon, 4 Apr 2016 20:47:49 +0000
From: Stephan Wenger <stewe@stewe.org>
To: Scott Bradner <sob@sobco.com>
Subject: Re: Last Call on draft-bradner-rfc3979bis-08.txt ("Intellectual Property Rights in IETF Technology")
Thread-Topic: Last Call on draft-bradner-rfc3979bis-08.txt ("Intellectual Property Rights in IETF Technology")
Thread-Index: AQHRhDTbKR9yu1RueEWA9RrAiHSISp9yLyaAgAAKyYCAAE/KAIAAXo6AgAb/NoD//9ajAIAANauAgAADRgCAAClHgIAAPXaA///N+wA=
Date: Mon, 4 Apr 2016 20:47:49 +0000
Message-ID: <B17E5970-1F1D-485D-ACD5-A64FEA7DF225@stewe.org>
References: <0000431F-F977-4A24-BA4D-064F740977A0@piuha.net> <56FBF599.9080605@ericsson.com> <ACC702C9-C33F-4D38-B47A-8BC293D24621@sobco.com> <DCA1B6AC-6221-4CF5-A726-E1E98DBFAC27@vigilsec.com> <56FC90E5.1050908@gmail.com> <CAC4RtVD3Pxm_vZgdCCgPgDwNfnYeKFJ5_Ys3QQPezrHzTGJE+Q@mail.gmail.com> <C5F35DA9-C530-4EC6-B175-C4B0A18872D7@stewe.org> <CALaySJ+1rvxXnXmLxk1UJ88t-e2p24OyMhR3f6P0peA5fLhRGA@mail.gmail.com> <CALaySJKBrjKEdu-qd067Eb7A+nZFObB3TdwSV=od9GDjhDOecQ@mail.gmail.com> <972C83CB-99B7-4278-9962-9AF67CFE890E@stewe.org> <1306B092-8C50-4916-88A1-0BC5F5FD51D1@sobco.com>
In-Reply-To: <1306B092-8C50-4916-88A1-0BC5F5FD51D1@sobco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: sobco.com; dkim=none (message not signed) header.d=none;sobco.com; dmarc=none action=none header.from=stewe.org;
x-ms-exchange-messagesentrepresentingtype: 1
x-originating-ip: [31.133.179.232]
x-ms-office365-filtering-correlation-id: 80643684-9555-4371-6a6c-08d35cca62a4
x-microsoft-exchange-diagnostics: 1; BLUPR17MB0274; 5:6UjaLOvK0xKhloolv8fM6kzrpf9YHOrdTJagJXIgFFVNopYFPzhxjzeS/aegnNsgEZ0vSOjZbF3CUfNiRtJhUPqxSNLmfYPoHeKeZMG4x9HLFbmFRvqyofxFtViAZ7FP0ld7OB+zeaWQ2vUOXFdqXQ==; 24:m4GdDqUYqi4TlZ4WUvllffuCcp3PIIQLV/Ced1xHwNzL4T3LUfZJV3mPWhXjz5UzVPt6PVh+g93EHLXp4Zjb/uI0bHUCm/ab9g53tolQDtU=
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:BLUPR17MB0274;
x-microsoft-antispam-prvs: <BLUPR17MB027460F4F0BB311E0C7E2953AE9D0@BLUPR17MB0274.namprd17.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040046)(601004)(2401047)(5005006)(8121501046)(3002001)(10201501046)(6041046)(6043046); SRVR:BLUPR17MB0274; BCL:0; PCL:0; RULEID:; SRVR:BLUPR17MB0274; 
x-forefront-prvs: 0902222726
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(377454003)(53754006)(24454002)(122556002)(5004730100002)(82746002)(33656002)(19580395003)(99286002)(19580405001)(83716003)(16236675004)(3660700001)(106116001)(86362001)(230783001)(5002640100001)(110136002)(189998001)(66066001)(2900100001)(36756003)(76176999)(2950100001)(4326007)(54356999)(50986999)(2906002)(3280700002)(5008740100001)(10400500002)(77096005)(81166005)(1096002)(11100500001)(6116002)(3846002)(586003)(102836003)(92566002)(87936001)(1220700001)(104396002)(42262002); DIR:OUT; SFP:1102; SCL:1; SRVR:BLUPR17MB0274; H:BLUPR17MB0275.namprd17.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en; 
spamdiagnosticoutput: 1:23
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_B17E59701F1D485DACD5A64FEA7DF225steweorg_"
MIME-Version: 1.0
X-OriginatorOrg: stewe.org
X-MS-Exchange-CrossTenant-originalarrivaltime: 04 Apr 2016 20:47:49.5900 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 865fc51c-5fae-4322-98ef-0121a85df0b6
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BLUPR17MB0274
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/7s-3cQ35c1Cz-o0rv-79EXOT31Q>
Cc: Barry Leiba <barryleiba@computer.org>, IETF <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: Mon, 04 Apr 2016 20:48:12 -0000

--_000_B17E59701F1D485DACD5A64FEA7DF225steweorg_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

RmluZS4gIEFjY291bnQgaXQgdW5kZXIgd29yZHNtaXRoaW5nIDotKQ0KU3RlcGhhbg0KDQpGcm9t
OiBTY290dCBCcmFkbmVyIDxzb2JAc29iY28uY29tPG1haWx0bzpzb2JAc29iY28uY29tPj4NCkRh
dGU6IE1vbmRheSwgQXByaWwgNCwgMjAxNiBhdCAxNzo0Ng0KVG86IFN0ZXBoYW4gV2VuZ2VyIDxz
dGV3ZUBzdGV3ZS5vcmc8bWFpbHRvOnN0ZXdlQHN0ZXdlLm9yZz4+DQpDYzogQmFycnkgTGVpYmEg
PGJhcnJ5bGVpYmFAY29tcHV0ZXIub3JnPG1haWx0bzpiYXJyeWxlaWJhQGNvbXB1dGVyLm9yZz4+
LCBJRVRGIDxpZXRmQGlldGYub3JnPG1haWx0bzppZXRmQGlldGYub3JnPj4NClN1YmplY3Q6IFJl
OiBMYXN0IENhbGwgb24gZHJhZnQtYnJhZG5lci1yZmMzOTc5YmlzLTA4LnR4dCAoIkludGVsbGVj
dHVhbCBQcm9wZXJ0eSBSaWdodHMgaW4gSUVURiBUZWNobm9sb2d5IikNCg0KDQpPbiBBcHIgNCwg
MjAxNiwgYXQgNDowNiBQTSwgU3RlcGhhbiBXZW5nZXIgPHN0ZXdlQHN0ZXdlLm9yZzxtYWlsdG86
c3Rld2VAc3Rld2Uub3JnPj4gd3JvdGU6DQoNCkhpIGFsbCwNCg0KQmFycnkgYW5kIEkgaGFkIGEg
Y2hhdCBhYm91dCB0aGlzLiAgSSBhbHNvIGhhZCBvZmZsaW5lIGNvbnZlcnNhdGlvbnMgd2l0aCBN
aWtlIENhbWVyb24gYW5kIGEgY2hhdCB3aXRoIEpvZWwuICBCYXJyeSBhbmQgSSBhdCBsZWFzdCBh
Z3JlZSBvbiB0aGUgcHJvYmxlbXMuICBUaGUgc29sdXRpb25zIGFyZSBtaW5lIGZvciBub3csIGFu
ZCB0aGV5IGFic29sdXRlbHkgYXJlIGluIG5lZWQgb2Ygd29yZHNtaXRoaW5nLi4uDQoNCkJhc2Vk
IG9uIHRoZSBkaXNjdXNzaW9uIHNvIGZhciwgdGhlcmUgc2VlbSB0byBiZSBhIG5lZWQgZm9yIHRo
ZSBmb2xsb3dpbmc6DQoNCjEuIEEgY2xhcmlmaWNhdGlvbiB0aGF0IGFuIEFELCBieSB0aGUgbmF0
dXJlIG9mIGhpcy9oZXIgb2ZmaWNlLCByZWd1bGFybHkgYmVjb21lcyBhd2FyZSBvZiBDb250cmli
dXRpb25zIGxhdGUgaW4gdGhlIHByb2Nlc3MgKGZvciBleGFtcGxlIGF0IElFVEYgTGFzdCBDYWxs
KSBhbmQsIHRoZXJlZm9yZSwgY2Fubm90IGJlIGV4cGVjdGVkIHRvIGRpc2Nsb3NlIGFueSBJUFIg
Q292ZXJpbmcgdGhvc2UgQ29udHJpYnV0aW9ucyB1bnRpbCBzdWNoIGxhdGUgdGltZSBpbiB0aGUg
cHJvY2Vzcy4NClRvIGZpeCB0aGlzIHBvaW50LCBhIHNpbXBsZSBleHBsYW5hdG9yeSBzZW50ZW5j
ZSBzb21ld2hlcmUgaW4gc2VjdGlvbiA1LjIuMiB3b3VsZCBzdWZmaWNlLiAgRm9yIGV4YW1wbGUg
4oCcQnkgdGhlIG5hdHVyZSBvZiB0aGVpciBvZmZpY2UsIElFVEYgYXJlYSBkaXJlY3RvcnMgcmVn
dWxhcmx5IGJlY29tZSBhd2FyZSBvZiBDb250cmlidXRpb25zIGxhdGUgaW4gdGhlIHByb2Nlc3Mg
KGZvciBleGFtcGxlIGF0IElFVEYgTGFzdCBDYWxsKSBhbmQsIHRoZXJlZm9yZSBhbmQgaW4gc3Vj
aCBjYXNlcywgY2Fubm90IGJlIGV4cGVjdGVkIHRvIGRpc2Nsb3NlIGFueSBJUFIgQ292ZXJpbmcg
dGhvc2UgQ29udHJpYnV0aW9ucyB1bnRpbCBzdWNoIGxhdGUgdGltZSBpbiB0aGUgcHJvY2Vzcy7i
gJ0NCg0KdGhpcyBkb2VzIG5vdCBzZWVtIHJpZ2h0DQoNCndoeSBub3Qgc2F5DQpCeSB0aGUgbmF0
dXJlIG9mIHRoZWlyIG9mZmljZSwgSUVURiBhcmVhIGRpcmVjdG9ycyBtYXkgYmVjb21lIGF3YXJl
IG9mIENvbnRyaWJ1dGlvbnMgbGF0ZSBpbiB0aGUgcHJvY2VzcyAoZm9yIGV4YW1wbGUgYXQgSUVU
RiBMYXN0IENhbGwgb3IgZHVyaW5nIElFU0cgcmV2aWV3KSBhbmQsIHRoZXJlZm9yZSBhbmQgaW4g
c3VjaCBjYXNlcywgY2Fubm90IGJlIGV4cGVjdGVkIHRvIGRpc2Nsb3NlIGFueSBJUFIgQ292ZXJp
bmcgdGhvc2UgQ29udHJpYnV0aW9ucyB1bnRpbCB0aGV5IGJlY29tZSBhd2FyZSBvZiB0aGVtLuKA
nQ0KDQoNCg==

--_000_B17E59701F1D485DACD5A64FEA7DF225steweorg_
Content-Type: text/html; charset="utf-8"
Content-ID: <6953085A5BAA2B4383BA269B4341926D@namprd17.prod.outlook.com>
Content-Transfer-Encoding: base64

PGh0bWw+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIgY29udGVudD0i
dGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjwvaGVhZD4NCjxib2R5IHN0eWxlPSJ3b3JkLXdy
YXA6IGJyZWFrLXdvcmQ7IC13ZWJraXQtbmJzcC1tb2RlOiBzcGFjZTsgLXdlYmtpdC1saW5lLWJy
ZWFrOiBhZnRlci13aGl0ZS1zcGFjZTsgY29sb3I6IHJnYigwLCAwLCAwKTsgZm9udC1zaXplOiAx
NHB4OyBmb250LWZhbWlseTogQ2FsaWJyaSwgc2Fucy1zZXJpZjsiPg0KPGRpdj4NCjxkaXY+DQo8
ZGl2PkZpbmUuICZuYnNwO0FjY291bnQgaXQgdW5kZXIgd29yZHNtaXRoaW5nIDotKTwvZGl2Pg0K
PGRpdj5TdGVwaGFuPC9kaXY+DQo8ZGl2Pg0KPGRpdiBpZD0iTUFDX09VVExPT0tfU0lHTkFUVVJF
Ij48L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjxkaXY+PGJyPg0KPC9kaXY+DQo8c3Bh
biBpZD0iT0xLX1NSQ19CT0RZX1NFQ1RJT04iPg0KPGRpdiBzdHlsZT0iZm9udC1mYW1pbHk6Q2Fs
aWJyaTsgZm9udC1zaXplOjEycHQ7IHRleHQtYWxpZ246bGVmdDsgY29sb3I6YmxhY2s7IEJPUkRF
Ui1CT1RUT006IG1lZGl1bSBub25lOyBCT1JERVItTEVGVDogbWVkaXVtIG5vbmU7IFBBRERJTkct
Qk9UVE9NOiAwaW47IFBBRERJTkctTEVGVDogMGluOyBQQURESU5HLVJJR0hUOiAwaW47IEJPUkRF
Ui1UT1A6ICNiNWM0ZGYgMXB0IHNvbGlkOyBCT1JERVItUklHSFQ6IG1lZGl1bSBub25lOyBQQURE
SU5HLVRPUDogM3B0Ij4NCjxzcGFuIHN0eWxlPSJmb250LXdlaWdodDpib2xkIj5Gcm9tOiA8L3Nw
YW4+U2NvdHQgQnJhZG5lciAmbHQ7PGEgaHJlZj0ibWFpbHRvOnNvYkBzb2Jjby5jb20iPnNvYkBz
b2Jjby5jb208L2E+Jmd0Ozxicj4NCjxzcGFuIHN0eWxlPSJmb250LXdlaWdodDpib2xkIj5EYXRl
OiA8L3NwYW4+TW9uZGF5LCBBcHJpbCA0LCAyMDE2IGF0IDE3OjQ2PGJyPg0KPHNwYW4gc3R5bGU9
ImZvbnQtd2VpZ2h0OmJvbGQiPlRvOiA8L3NwYW4+U3RlcGhhbiBXZW5nZXIgJmx0OzxhIGhyZWY9
Im1haWx0bzpzdGV3ZUBzdGV3ZS5vcmciPnN0ZXdlQHN0ZXdlLm9yZzwvYT4mZ3Q7PGJyPg0KPHNw
YW4gc3R5bGU9ImZvbnQtd2VpZ2h0OmJvbGQiPkNjOiA8L3NwYW4+QmFycnkgTGVpYmEgJmx0Ozxh
IGhyZWY9Im1haWx0bzpiYXJyeWxlaWJhQGNvbXB1dGVyLm9yZyI+YmFycnlsZWliYUBjb21wdXRl
ci5vcmc8L2E+Jmd0OywgSUVURiAmbHQ7PGEgaHJlZj0ibWFpbHRvOmlldGZAaWV0Zi5vcmciPmll
dGZAaWV0Zi5vcmc8L2E+Jmd0Ozxicj4NCjxzcGFuIHN0eWxlPSJmb250LXdlaWdodDpib2xkIj5T
dWJqZWN0OiA8L3NwYW4+UmU6IExhc3QgQ2FsbCBvbiBkcmFmdC1icmFkbmVyLXJmYzM5NzliaXMt
MDgudHh0ICgmcXVvdDtJbnRlbGxlY3R1YWwgUHJvcGVydHkgUmlnaHRzIGluIElFVEYgVGVjaG5v
bG9neSZxdW90Oyk8YnI+DQo8L2Rpdj4NCjxkaXY+PGJyPg0KPC9kaXY+DQo8ZGl2Pg0KPGRpdiBz
dHlsZT0id29yZC13cmFwOiBicmVhay13b3JkOyAtd2Via2l0LW5ic3AtbW9kZTogc3BhY2U7IC13
ZWJraXQtbGluZS1icmVhazogYWZ0ZXItd2hpdGUtc3BhY2U7IiBjbGFzcz0iIj4NCjxiciBjbGFz
cz0iIj4NCjxkaXY+DQo8YmxvY2txdW90ZSB0eXBlPSJjaXRlIiBjbGFzcz0iIj4NCjxkaXYgY2xh
c3M9IiI+T24gQXByIDQsIDIwMTYsIGF0IDQ6MDYgUE0sIFN0ZXBoYW4gV2VuZ2VyICZsdDs8YSBo
cmVmPSJtYWlsdG86c3Rld2VAc3Rld2Uub3JnIiBjbGFzcz0iIj5zdGV3ZUBzdGV3ZS5vcmc8L2E+
Jmd0OyB3cm90ZTo8L2Rpdj4NCjxiciBjbGFzcz0iQXBwbGUtaW50ZXJjaGFuZ2UtbmV3bGluZSI+
DQo8ZGl2IGNsYXNzPSIiPg0KPGRpdiBzdHlsZT0id29yZC13cmFwOiBicmVhay13b3JkOyAtd2Vi
a2l0LW5ic3AtbW9kZTogc3BhY2U7IC13ZWJraXQtbGluZS1icmVhazogYWZ0ZXItd2hpdGUtc3Bh
Y2U7IiBjbGFzcz0iIj4NCjxkaXYgY2xhc3M9IiI+DQo8ZGl2IHN0eWxlPSJmb250LWZhbWlseTog
Q2FsaWJyaSwgc2Fucy1zZXJpZjsgZm9udC1zaXplOiAxNHB4OyIgY2xhc3M9IiI+SGkgYWxsLDwv
ZGl2Pg0KPGRpdiBzdHlsZT0iZm9udC1mYW1pbHk6IENhbGlicmksIHNhbnMtc2VyaWY7IGZvbnQt
c2l6ZTogMTRweDsiIGNsYXNzPSIiPjxiciBjbGFzcz0iIj4NCjwvZGl2Pg0KPGRpdiBzdHlsZT0i
Zm9udC1mYW1pbHk6IENhbGlicmksIHNhbnMtc2VyaWY7IGZvbnQtc2l6ZTogMTRweDsiIGNsYXNz
PSIiPkJhcnJ5IGFuZCBJIGhhZCBhIGNoYXQgYWJvdXQgdGhpcy4gJm5ic3A7SSBhbHNvIGhhZCBv
ZmZsaW5lIGNvbnZlcnNhdGlvbnMgd2l0aCBNaWtlIENhbWVyb24gYW5kIGEgY2hhdCB3aXRoIEpv
ZWwuICZuYnNwO0JhcnJ5IGFuZCBJIGF0IGxlYXN0IGFncmVlIG9uIHRoZSBwcm9ibGVtcy4gJm5i
c3A7VGhlIHNvbHV0aW9ucyBhcmUgbWluZSBmb3Igbm93LA0KIGFuZCB0aGV5IGFic29sdXRlbHkg
YXJlIGluIG5lZWQgb2Ygd29yZHNtaXRoaW5nLi4uPC9kaXY+DQo8ZGl2IHN0eWxlPSJmb250LWZh
bWlseTogQ2FsaWJyaSwgc2Fucy1zZXJpZjsgZm9udC1zaXplOiAxNHB4OyIgY2xhc3M9IiI+PGJy
IGNsYXNzPSIiPg0KPC9kaXY+DQo8ZGl2IHN0eWxlPSJmb250LWZhbWlseTogQ2FsaWJyaSwgc2Fu
cy1zZXJpZjsgZm9udC1zaXplOiAxNHB4OyIgY2xhc3M9IiI+QmFzZWQgb24gdGhlIGRpc2N1c3Np
b24gc28gZmFyLCB0aGVyZSBzZWVtIHRvIGJlIGEgbmVlZCBmb3IgdGhlIGZvbGxvd2luZzo8L2Rp
dj4NCjxkaXYgc3R5bGU9ImZvbnQtZmFtaWx5OiBDYWxpYnJpLCBzYW5zLXNlcmlmOyBmb250LXNp
emU6IDE0cHg7IiBjbGFzcz0iIj48YnIgY2xhc3M9IiI+DQo8L2Rpdj4NCjxkaXYgY2xhc3M9IiI+
DQo8ZGl2IHN0eWxlPSJmb250LWZhbWlseTogQ2FsaWJyaSwgc2Fucy1zZXJpZjsgZm9udC1zaXpl
OiAxNHB4OyIgY2xhc3M9IiI+MS4gQSBjbGFyaWZpY2F0aW9uIHRoYXQgYW4gQUQsIGJ5IHRoZSBu
YXR1cmUgb2YgaGlzL2hlciBvZmZpY2UsIHJlZ3VsYXJseSBiZWNvbWVzIGF3YXJlIG9mIENvbnRy
aWJ1dGlvbnMgbGF0ZSBpbiB0aGUgcHJvY2VzcyAoZm9yIGV4YW1wbGUgYXQgSUVURiBMYXN0IENh
bGwpIGFuZCwgdGhlcmVmb3JlLCBjYW5ub3QgYmUgZXhwZWN0ZWQNCiB0byBkaXNjbG9zZSBhbnkg
SVBSIENvdmVyaW5nIHRob3NlIENvbnRyaWJ1dGlvbnMgdW50aWwgc3VjaCBsYXRlIHRpbWUgaW4g
dGhlIHByb2Nlc3MuPC9kaXY+DQo8ZGl2IHN0eWxlPSJmb250LWZhbWlseTogQ2FsaWJyaSwgc2Fu
cy1zZXJpZjsgZm9udC1zaXplOiAxNHB4OyIgY2xhc3M9IiI+DQo8ZGl2IGNsYXNzPSIiPlRvIGZp
eCB0aGlzIHBvaW50LCBhIHNpbXBsZSBleHBsYW5hdG9yeSBzZW50ZW5jZSBzb21ld2hlcmUgaW4g
c2VjdGlvbiA1LjIuMiB3b3VsZCBzdWZmaWNlLiAmbmJzcDtGb3IgZXhhbXBsZSDigJxCeSB0aGUg
bmF0dXJlIG9mIHRoZWlyIG9mZmljZSwgSUVURiBhcmVhIGRpcmVjdG9ycyZuYnNwO3JlZ3VsYXJs
eSBiZWNvbWUgYXdhcmUgb2YgQ29udHJpYnV0aW9ucyBsYXRlIGluIHRoZSBwcm9jZXNzIChmb3Ig
ZXhhbXBsZSBhdCBJRVRGIExhc3QgQ2FsbCkNCiBhbmQsIHRoZXJlZm9yZSBhbmQgaW4gc3VjaCBj
YXNlcywgY2Fubm90IGJlIGV4cGVjdGVkIHRvIGRpc2Nsb3NlIGFueSBJUFIgQ292ZXJpbmcgdGhv
c2UgQ29udHJpYnV0aW9ucyB1bnRpbCBzdWNoIGxhdGUgdGltZSBpbiB0aGUgcHJvY2Vzcy7igJ08
L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Jsb2NrcXVv
dGU+DQo8ZGl2PjxiciBjbGFzcz0iIj4NCjwvZGl2Pg0KdGhpcyBkb2VzIG5vdCBzZWVtIHJpZ2h0
PC9kaXY+DQo8ZGl2PjxiciBjbGFzcz0iIj4NCjwvZGl2Pg0KPGRpdj53aHkgbm90IHNheSZuYnNw
OzwvZGl2Pg0KPGRpdj4NCjxkaXYgc3R5bGU9Im1hcmdpbjogMHB4OyBmb250LXNpemU6IDExcHg7
IGxpbmUtaGVpZ2h0OiBub3JtYWw7IGZvbnQtZmFtaWx5OiBNZW5sbzsiIGNsYXNzPSIiPg0KPHNw
YW4gc3R5bGU9ImZvbnQtdmFyaWFudC1saWdhdHVyZXM6IG5vLWNvbW1vbi1saWdhdHVyZXMiIGNs
YXNzPSIiPkJ5IHRoZSBuYXR1cmUgb2YgdGhlaXIgb2ZmaWNlLCBJRVRGIGFyZWEgZGlyZWN0b3Jz
IG1heSBiZWNvbWUgYXdhcmUgb2YgQ29udHJpYnV0aW9ucyBsYXRlIGluIHRoZSBwcm9jZXNzIChm
b3IgZXhhbXBsZSBhdCBJRVRGIExhc3QgQ2FsbCBvciBkdXJpbmcgSUVTRyByZXZpZXcpIGFuZCwg
dGhlcmVmb3JlIGFuZCBpbiBzdWNoIGNhc2VzLA0KIGNhbm5vdCBiZSBleHBlY3RlZCB0byBkaXNj
bG9zZSBhbnkgSVBSIENvdmVyaW5nIHRob3NlIENvbnRyaWJ1dGlvbnMgdW50aWwgdGhleSBiZWNv
bWUgYXdhcmUgb2YgdGhlbS7igJ08L3NwYW4+PC9kaXY+DQo8L2Rpdj4NCjxkaXY+PGJyIGNsYXNz
PSIiPg0KPC9kaXY+DQo8YnIgY2xhc3M9IiI+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9zcGFuPg0KPC9i
b2R5Pg0KPC9odG1sPg0K

--_000_B17E59701F1D485DACD5A64FEA7DF225steweorg_--


From nobody Mon Apr  4 13:57:38 2016
Return-Path: <randy@psg.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 4C6E012D645 for <ietf@ietfa.amsl.com>; Mon,  4 Apr 2016 13:57:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.91
X-Spam-Level: 
X-Spam-Status: No, score=-6.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, T_RP_MATCHES_RCVD=-0.01] 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 TILXJiD8z96S for <ietf@ietfa.amsl.com>; Mon,  4 Apr 2016 13:57:36 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 25B1412D51B for <ietf@ietf.org>; Mon,  4 Apr 2016 13:57:36 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com) by ran.psg.com with esmtp (Exim 4.82) (envelope-from <randy@psg.com>) id 1anBZ1-000108-0R for ietf@ietf.org; Mon, 04 Apr 2016 20:57:35 +0000
Date: Mon, 04 Apr 2016 17:57:34 -0300
Message-ID: <m2wpodhz29.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: IETF Disgust List <ietf@ietf.org>
Subject: Re: [95all] IETF 95 Agenda Changes
In-Reply-To: <20160404203827.15696.67299.idtracker@ietfa.amsl.com>
References: <20160404203827.15696.67299.idtracker@ietfa.amsl.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/srhqSxbQqUFXaKpfJFC_X-qEQag>
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: Mon, 04 Apr 2016 20:57:37 -0000

> V6OPS - Tuesday 1000 - CANCELED

CGN WG will be held in its place


From nobody Mon Apr  4 13:58:37 2016
Return-Path: <barryleiba@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 BCEC512D8AA for <ietf@ietfa.amsl.com>; Mon,  4 Apr 2016 13:58:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.4
X-Spam-Level: 
X-Spam-Status: No, score=-2.4 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.199, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 HG04bal_ZhwN for <ietf@ietfa.amsl.com>; Mon,  4 Apr 2016 13:58:34 -0700 (PDT)
Received: from mail-yw0-x22d.google.com (mail-yw0-x22d.google.com [IPv6:2607:f8b0:4002:c05::22d]) (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 5917512D889 for <ietf@ietf.org>; Mon,  4 Apr 2016 13:58:34 -0700 (PDT)
Received: by mail-yw0-x22d.google.com with SMTP id g127so267599501ywf.2 for <ietf@ietf.org>; Mon, 04 Apr 2016 13:58:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-transfer-encoding; bh=vxdPpANQeViPCqqsDM+FuwYVNjzvmBNZSUAZwQEJg1w=; b=icSTvQOybkeVpp2XCalEjKpRlE/rbtIIQC5aN5E2YfhPnYYN86LYEqMxpUwy/sV9ZT lNfa+vFj/qRFJt485BtO9ptJ4JjcYdNLRLRotTocHBAQeo8A8buPIyn0g49bdaoC8Es5 wiSSfM4ofgqwBQ7z5U9Ch3BPhvXY51aN+WWa1f6Ap1SWSTn+1DhhtjezzScDDbZoCw62 3wFz6uU97DAzFmgED2xY4/CSW43+yU191piQLKsii6Nh5xnzRPohw1lA9huF9ax80z/p IXfTyDfKtSddrH2OCB74YIkmN1wVbNAwOlXOs6lof1b+YnX76IkHW/mehBhd5rq8wTAi oxfw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:date :message-id:subject:from:to:cc:content-transfer-encoding; bh=vxdPpANQeViPCqqsDM+FuwYVNjzvmBNZSUAZwQEJg1w=; b=Y1sTtmFGM8y9R+5nxiDyk8z5u9eH8W5rrLyJaCfgusjFIf2hO12dx/BPeQUkvbSr+s 3G8q9TUlrbm5eRVl2qqcsmpIBWY/e39EodkAB+tRdHx0girZJxULcsiOv8zO3Blylbht p/IrYMQO4JmDw9tXJlxBkGGHQARQEkzqHAgRdW8KtQ7dsmPzBBeJKlKZGRCROEERfw/o sCQd+dxEh5PQ0qEBSRIfrrryoAKmrdmlR3qh/xCLUTHu4f9uhz/64HLGCSGuEs4Ke7H6 CPcTd3n11d+rO7TU2Le53ueCYynLrENbcd67zrlKxhnrfAcU734NFNwrhzZjFvHBmzcQ JfqA==
X-Gm-Message-State: AD7BkJJAnfZ6nk0dBW0CtOjOyKfTEIAXu+vOhTiBpz0GmfTe9UwHa48EPf9lygOnjZGJwp1JJ91cJY3SDt5B0w==
MIME-Version: 1.0
X-Received: by 10.37.231.198 with SMTP id e189mr1466351ybh.129.1459803513550;  Mon, 04 Apr 2016 13:58:33 -0700 (PDT)
Sender: barryleiba@gmail.com
Received: by 10.83.28.67 with HTTP; Mon, 4 Apr 2016 13:58:33 -0700 (PDT)
In-Reply-To: <B17E5970-1F1D-485D-ACD5-A64FEA7DF225@stewe.org>
References: <0000431F-F977-4A24-BA4D-064F740977A0@piuha.net> <56FBF599.9080605@ericsson.com> <ACC702C9-C33F-4D38-B47A-8BC293D24621@sobco.com> <DCA1B6AC-6221-4CF5-A726-E1E98DBFAC27@vigilsec.com> <56FC90E5.1050908@gmail.com> <CAC4RtVD3Pxm_vZgdCCgPgDwNfnYeKFJ5_Ys3QQPezrHzTGJE+Q@mail.gmail.com> <C5F35DA9-C530-4EC6-B175-C4B0A18872D7@stewe.org> <CALaySJ+1rvxXnXmLxk1UJ88t-e2p24OyMhR3f6P0peA5fLhRGA@mail.gmail.com> <CALaySJKBrjKEdu-qd067Eb7A+nZFObB3TdwSV=od9GDjhDOecQ@mail.gmail.com> <972C83CB-99B7-4278-9962-9AF67CFE890E@stewe.org> <1306B092-8C50-4916-88A1-0BC5F5FD51D1@sobco.com> <B17E5970-1F1D-485D-ACD5-A64FEA7DF225@stewe.org>
Date: Mon, 4 Apr 2016 16:58:33 -0400
X-Google-Sender-Auth: C_k51rzvZYfkRMVIcjZtwS6r1c4
Message-ID: <CALaySJ+f8oWeeGNC-W7vNf-vXsGWJfaDanKiU21ZeeHAw=+hFw@mail.gmail.com>
Subject: Re: Last Call on draft-bradner-rfc3979bis-08.txt ("Intellectual Property Rights in IETF Technology")
From: Barry Leiba <barryleiba@computer.org>
To: Stephan Wenger <stewe@stewe.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/1papPo2wYS-0vaYjK0PbedjPORU>
Cc: IETF <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: Mon, 04 Apr 2016 20:58:35 -0000

> Barry and I had a chat about this.  I also had offline conversations with
> Mike Cameron and a chat with Joel.  Barry and I at least agree on the
> problems.  The solutions are mine for now, and they absolutely are in nee=
d
> of wordsmithing...

Indeed, and Stephan's captured my concerns well, and I agree with the
proposed solutions.

>> why not say
>> By the nature of their office, IETF area directors may become aware of
>> Contributions late in the process (for example at IETF Last Call or duri=
ng
>> IESG review) and, therefore and in such cases, cannot be expected to
>> disclose any IPR Covering those Contributions until they become aware of
>> them.=E2=80=9D
>
> Fine.  Account it under wordsmithing :-)

Yes, that wordsmithing looks good.

Barry


From nobody Mon Apr  4 14:08:13 2016
Return-Path: <joelja@bogus.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 F10E712D87F for <ietf@ietfa.amsl.com>; Mon,  4 Apr 2016 14:08:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.91
X-Spam-Level: 
X-Spam-Status: No, score=-6.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, T_RP_MATCHES_RCVD=-0.01] 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 2PxUwD_OGsLw for <ietf@ietfa.amsl.com>; Mon,  4 Apr 2016 14:08:10 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) (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 5231312D7E6 for <ietf@ietf.org>; Mon,  4 Apr 2016 14:08:10 -0700 (PDT)
Received: from dhcp-b257.meeting.ietf.org ([IPv6:2001:67c:370:176:cdf5:5ee7:c354:d084]) (authenticated bits=0) by nagasaki.bogus.com (8.14.9/8.14.9) with ESMTP id u34L85wR087693 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Mon, 4 Apr 2016 21:08:07 GMT (envelope-from joelja@bogus.com)
Subject: Re: Last Call on draft-bradner-rfc3979bis-08.txt ("Intellectual Property Rights in IETF Technology")
To: Stephan Wenger <stewe@stewe.org>, Barry Leiba <barryleiba@computer.org>
References: <0000431F-F977-4A24-BA4D-064F740977A0@piuha.net> <56FBF599.9080605@ericsson.com> <ACC702C9-C33F-4D38-B47A-8BC293D24621@sobco.com> <DCA1B6AC-6221-4CF5-A726-E1E98DBFAC27@vigilsec.com> <56FC90E5.1050908@gmail.com> <CAC4RtVD3Pxm_vZgdCCgPgDwNfnYeKFJ5_Ys3QQPezrHzTGJE+Q@mail.gmail.com> <C5F35DA9-C530-4EC6-B175-C4B0A18872D7@stewe.org> <CALaySJ+1rvxXnXmLxk1UJ88t-e2p24OyMhR3f6P0peA5fLhRGA@mail.gmail.com> <CALaySJKBrjKEdu-qd067Eb7A+nZFObB3TdwSV=od9GDjhDOecQ@mail.gmail.com> <972C83CB-99B7-4278-9962-9AF67CFE890E@stewe.org>
From: joel jaeggli <joelja@bogus.com>
Message-ID: <dec483cf-5ee1-49dd-83a4-da2005211130@bogus.com>
Date: Mon, 4 Apr 2016 18:08:04 -0300
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.0
MIME-Version: 1.0
In-Reply-To: <972C83CB-99B7-4278-9962-9AF67CFE890E@stewe.org>
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="qLJ8940XbkvAFCPxbq1FUuc5V0pBLN58o"
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/2LULCQJw2Zt7DmGbpda1LlB2mCY>
Cc: IETF <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: Mon, 04 Apr 2016 21:08:12 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--qLJ8940XbkvAFCPxbq1FUuc5V0pBLN58o
Content-Type: multipart/mixed; boundary="78w1jmXkWSrdJfGtO7ss5OAAW2cQ9B4uv"
From: joel jaeggli <joelja@bogus.com>
To: Stephan Wenger <stewe@stewe.org>, Barry Leiba <barryleiba@computer.org>
Cc: IETF <ietf@ietf.org>
Message-ID: <dec483cf-5ee1-49dd-83a4-da2005211130@bogus.com>
Subject: Re: Last Call on draft-bradner-rfc3979bis-08.txt ("Intellectual
 Property Rights in IETF Technology")
References: <0000431F-F977-4A24-BA4D-064F740977A0@piuha.net>
 <56FBF599.9080605@ericsson.com>
 <ACC702C9-C33F-4D38-B47A-8BC293D24621@sobco.com>
 <DCA1B6AC-6221-4CF5-A726-E1E98DBFAC27@vigilsec.com>
 <56FC90E5.1050908@gmail.com>
 <CAC4RtVD3Pxm_vZgdCCgPgDwNfnYeKFJ5_Ys3QQPezrHzTGJE+Q@mail.gmail.com>
 <C5F35DA9-C530-4EC6-B175-C4B0A18872D7@stewe.org>
 <CALaySJ+1rvxXnXmLxk1UJ88t-e2p24OyMhR3f6P0peA5fLhRGA@mail.gmail.com>
 <CALaySJKBrjKEdu-qd067Eb7A+nZFObB3TdwSV=od9GDjhDOecQ@mail.gmail.com>
 <972C83CB-99B7-4278-9962-9AF67CFE890E@stewe.org>
In-Reply-To: <972C83CB-99B7-4278-9962-9AF67CFE890E@stewe.org>

--78w1jmXkWSrdJfGtO7ss5OAAW2cQ9B4uv
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

On 4/4/16 5:06 PM, Stephan Wenger wrote:
> Hi all,
>=20
> Barry and I had a chat about this.  I also had offline conversations
> with Mike Cameron and a chat with Joel.  Barry and I at least agree on
> the problems.  The solutions are mine for now, and they absolutely are
> in need of wordsmithing...
>=20
> Based on the discussion so far, there seem to be a need for the followi=
ng:
>=20
> 1. A clarification that an AD, by the nature of his/her office,
> regularly becomes aware of Contributions late in the process (for
> example at IETF Last Call) and, therefore, cannot be expected to
> disclose any IPR Covering those Contributions until such late time in
> the process.
> To fix this point, a simple explanatory sentence somewhere in section
> 5.2.2 would suffice.  For example =E2=80=9CBy the nature of their offic=
e, IETF
> area directors regularly become aware of Contributions late in the
> process (for example at IETF Last Call) and, therefore and in such
> cases, cannot be expected to disclose any IPR Covering those
> Contributions until such late time in the process.=E2=80=9D
>=20
> The purpose of this sentence is to protect an AD and its sponsoring
> company from allegations, both within the IETF and in courts, that they=

> disclosed late against policy.
>=20
> 2. A clarification or, more likely, a substantial change that, like any=

> other individual in the IETF, also an AD has the option to recuse
> himself from involving himself/herself in the decision making process o=
f
> a document, even a document in his own area. For example, an AD that di=
d
> never comment on a document and abstained during the IETF Last Call
> would not incur a disclosure obligation, even if the Contribution were
> in his/her own area. =20


I kind of have a problem with this point. it signals that you would have
to make a disclosure if you did participate. which is tantamount to
disclosing but with an extraordinarily incomplete statement.

> This second point is more tricky.  Is the formulation currently in the
> draft, which defines ADs as Participants, inline with what=E2=80=99s wr=
itten in
> point 2?  I=E2=80=99m coming around to think that it does not.  Instead=
, I think
> we have a contradiction in the current draft=E2=80=94on one hand, an AD=
 who
> intentionally stays away from influencing the decision process regardin=
g
> a Contribution should not incur an obligation based on the underlying
> principle of the policy=E2=80=94no more than anyone else; but the text =
about ADs
> being Participants rules out that interpretation.  Having contradiction=
s
> in patent policies is a Very Bad Idea since at least Rambus (ca. 2003).=

>  Is that correct so far?
>=20
> Based on the current formulation, and without violating the policy, an
> AD who is under the gun of his IPR department not to disclose a specifi=
c
> IPR has only the option to step down.  Is this what we want in each and=

> every case?  Or would we rather be pragmatic and allow an AD to recuse
> himself/herself occasionally?  If yes, I think we need language
> indicating that such a mechanism is available, but also is meant to be
> used sparsely, and at least implying that ADs who are forced to use it
> more than under exceptional circumstances are indeed to step down. =20
>=20
> The paragraph below tries to express this.  The markup will probably
> only be visible if you choose to view the HTML version of this email.
>=20
> =E2=80=9C
> k. "Participating in an IETF discussion or activity": means making a
> Contribution, as described above, or in any other way acting in
> order to influence the outcome of a discussion relating to the
> IETF Standards Process. Without limiting the generality of the
> foregoing, acting as a working group chair or Area Director
> constitutes "Participating" in all activities of the relevant
> working groupor area. "Participant" and "IETF Participant" mean
> any individual Participating in an IETF discussion or activity.  _Under=
 _
> _extraordinary circumstances only, an AD may choose not to Participate =
_
> _in the discussion or activity of his/her area, recuse himself/herself =
_
> _from IESG deliberations of related documents, and abstain during _
> _the IESG ballot process, thereby not incurring the obligations based_
> _on Participating._
> " =20
>=20
> Stephan
>=20
>=20
> On 4/4/16, 11:39, "barryleiba@gmail.com <mailto:barryleiba@gmail.com> o=
n
> behalf of Barry Leiba" <barryleiba@gmail.com
> <mailto:barryleiba@gmail.com> on behalf of barryleiba@computer.org
> <mailto:barryleiba@computer.org>> wrote:
>=20
>     A follow-up here:
>=20
>     I'd be more comfortably with something more waffly, something more
>     like this:
>=20
>     Without limiting the generality of the foregoing, acting as a worki=
ng
>     group chair or Area Director can often be considered "Participating=
"
>     in all activities of the relevant working group or area; as such,
>     working group chairs and Area Directors are expected to make a best=
,
>     good-faith effort to carry out the responsibilities of Participants=
=2E
>=20
>     Or perhaps we want to separate WGCs from ADs here, and the text nee=
ds
>     more work in any case, but I hope people see the general point.
>=20
>     Barry
>=20
>     On Mon, Apr 4, 2016 at 10:27 AM, Barry Leiba
>     <barryleiba@computer.org <mailto:barryleiba@computer.org>> wrote:
>=20
>                 The "reasonably and personally aware" applies to the
>                 IPR, not to the
>                 participation.
>=20
>=20
>             I think this is incorrect.
>=20
>             According to section 5.1.2 (disclosure requirement based on=

>             Participation, not own IPR), a disclosure obligation exists=

>             if =E2=80=9Cthe
>             Participant believes Covers or may ultimately Cover that
>             Contribution=E2=80=9D.  I don=E2=80=99t think anyone could =
argue that an AD
>             has a
>             =E2=80=9Cbelieve=E2=80=9D in a patent or application he/she=
 is aware of Covers a
>             Contribution when he has never seen the Contribution.
>=20
>=20
>         Would you accept "I didn't read the draft" as an acceptable rea=
son
>         that someone engaged in active discussion on a draft didn't
>         disclose?
>=20
>         We don't have different levels of Contributor here.  Someone
>         making a
>         Contribution has an obligation to disclose, even if s/he was on=
e of
>         those who said, "I didn't read the draft, but...."  If we
>         declare the
>         ADs to be Contributors, why does the same not apply to them?
>=20
>             A late disclosure is better than no disclosure
>=20
>=20
>         I hope we all agree on that!
>=20
>             clearly, an AD
>             has a much better justification of making such a late
>             disclosure.  I
>             would hope that no one would complain if an AD makes a late=

>             disclosure
>             and, when asked for the reason of lateness, he says =E2=80=9C=
I was not
>             responsible AD; I came across this during final review in
>             IETF last
>             call, and just identified this. =E2=80=9C  In fact, people =
should
>             appreciate
>             this.
>=20
>=20
>         Maybe so, but as it stands now in the document, it's still a la=
te
>         disclosure, and there might still be backlash, legal concerns b=
y
>         employers, and reluctance to put people in that position.
>=20
>         If that's the consensus, then there we have it... but I think w=
e
>         should be very careful about unintended consequences of this on=
e.
>=20
>         Barry
>=20
>=20



--78w1jmXkWSrdJfGtO7ss5OAAW2cQ9B4uv--

--qLJ8940XbkvAFCPxbq1FUuc5V0pBLN58o
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2
Comment: GPGTools - http://gpgtools.org

iEYEARECAAYFAlcC17QACgkQ8AA1q7Z/VrI05QCfXJRBV6fjDJGyObsFR+kSufcn
yi4An0B9uvuWuyprvCG8pKiiiLc1uKHu
=ol1q
-----END PGP SIGNATURE-----

--qLJ8940XbkvAFCPxbq1FUuc5V0pBLN58o--


From nobody Mon Apr  4 16:23:23 2016
Return-Path: <john-ietf@jck.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 5576412D724 for <ietf@ietfa.amsl.com>; Mon,  4 Apr 2016 16:23:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] 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 ym4cbGjnCOVI for <ietf@ietfa.amsl.com>; Mon,  4 Apr 2016 16:23:20 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9501812D126 for <ietf@ietf.org>; Mon,  4 Apr 2016 16:23:20 -0700 (PDT)
Received: from [198.252.137.10] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1anDpy-000L9C-01; Mon, 04 Apr 2016 19:23:14 -0400
Date: Mon, 04 Apr 2016 19:23:08 -0400
From: John C Klensin <john-ietf@jck.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: Last Call on draft-bradner-rfc3979bis-08.txt ("Intellectual Property Rights in IETF Technology")
Message-ID: <5ABAE5DB070828F14822B6FD@JcK-HP8200.jck.com>
In-Reply-To: <5702CBA2.2060802@gmail.com>
References: <0000431F-F977-4A24-BA4D-064F740977A0@piuha.net> <56FBF599.9080605@ericsson.com> <F99F459688AAAFCDCD5D9CC1@JcK-HP8200.jck.com> <5702CBA2.2060802@gmail.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/zllg79DbK_qYvixZgmMURhIrkSA>
Cc: IETF <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: Mon, 04 Apr 2016 23:23:22 -0000

--On Tuesday, April 05, 2016 08:16 +1200 Brian E Carpenter
<brian.e.carpenter@gmail.com> wrote:

>> Another aspect of my reaction to Barry's comment is that,
>> given other changes in the IETF in the last 11 years, I'd
>> really like to see 3979bis recast as a matter of ethical
>> obligations to the IETF and fellow participants, with
>> specific legal (or other) requirements stated as corollaries
>> to those ethical principles rather than as standalone rules.
> 
> I'm sympathetic with that idea, but not being a lawyer I don't
> know if it's feasible to truly separate them.

Brian,

I suggest that every legislator or minister in the world who has
had to write an introduction that justifies what a particular
law or regulation is about (or to get it passed), and every
lawyer who has started a sentence with the word "Whereas..." (or
its equivalent in other languages) understands how to do that.

In our case, the Abstract and Introduction to 3979bis say some
nice words about design and intentions, but it is hard to
understand the relationships between those statements and the
actual rules.  It would require a massive reorganization
/rewrite to the document and I'm not at all sure the community
(much less Scott and Jorge) are up to it, but I think we would
be better off if we outlined expectations for disclosure of IPR
(and other involvements that might complicate IETF actions) as a
professional and ethical matter.  I'd think it could be linked
to RFC 7154 and similar discussions and clearly focused on what
people need to know to develop good-quality standards and
related documents in an environment requiring a lot of trust in
colleagues.  With that set of principles in place, it could then
say that some specific rules exist in support of those
principles but that other behavior that would violate the
principles isn't allowed either.  Then it could go on to lay out
the rule themselves, in as much legalese as is needed and more
or less copying what is now in 3979bis-08, modified to reflect
the two weeks of discussions since it was posted.

I believe that would have at least two advantages: (i) it would
reduce the need to split every last possible hair and cover
every possible edge case because badly-intentioned behavior
would be considered bad (and sanction-able) in the IETF whether
some particular rule clearly applied or not and (ii) it _might_
permit us to have more focused discussions in the future by
differentiating disagreement with the principles from
disagreement about how particular rules were specified, or
whether those specifications adequately reflected, those
principles.

IMO, the document needs a change of organization and tone, and a
way to deal with the edge cases without having to try to
identify and specify the handling for each one, much more than
it needs major conceptual reform.   But changing organization
and tone would still represent a significant effort and, again,
it isn't clear to me that folks are up to it.

    john




From nobody Mon Apr  4 17:30:52 2016
Return-Path: <michael.cameron@ericsson.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 C7D9912D151 for <ietf@ietfa.amsl.com>; Mon,  4 Apr 2016 17:30:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] 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 ejfX785E9_6N for <ietf@ietfa.amsl.com>; Mon,  4 Apr 2016 17:30:49 -0700 (PDT)
Received: from usplmg20.ericsson.net (usplmg20.ericsson.net [198.24.6.45]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 062A712D173 for <ietf@ietf.org>; Mon,  4 Apr 2016 17:30:48 -0700 (PDT)
X-AuditID: c618062d-f79216d00000767f-c0-5703011753cc
Received: from EUSAAHC003.ericsson.se (Unknown_Domain [147.117.188.81]) by usplmg20.ericsson.net (Symantec Mail Security) with SMTP id 71.08.30335.71103075; Tue,  5 Apr 2016 02:04:39 +0200 (CEST)
Received: from EUSAAMB101.ericsson.se ([147.117.188.118]) by EUSAAHC003.ericsson.se ([147.117.188.81]) with mapi id 14.03.0248.002; Mon, 4 Apr 2016 20:30:47 -0400
From: Michael Cameron <michael.cameron@ericsson.com>
To: John C Klensin <john-ietf@jck.com>, Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: RE: Last Call on draft-bradner-rfc3979bis-08.txt ("Intellectual Property Rights in IETF Technology")
Thread-Topic: Last Call on draft-bradner-rfc3979bis-08.txt ("Intellectual Property Rights in IETF Technology")
Thread-Index: AQHRjskGamWQN+s8KkavsxfeJkItdZ96e9QQ
Date: Tue, 5 Apr 2016 00:30:46 +0000
Message-ID: <36BAA6A693139D4BBCB37CCCA660E08A14FC1914@eusaamb101.ericsson.se>
References: <0000431F-F977-4A24-BA4D-064F740977A0@piuha.net> <56FBF599.9080605@ericsson.com> <F99F459688AAAFCDCD5D9CC1@JcK-HP8200.jck.com> <5702CBA2.2060802@gmail.com> <5ABAE5DB070828F14822B6FD@JcK-HP8200.jck.com>
In-Reply-To: <5ABAE5DB070828F14822B6FD@JcK-HP8200.jck.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [147.117.188.10]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFmphkeLIzCtJLcpLzFFi42KZXLonUFeckTnc4O4udYu2i/uYLJ5tnM9i 0XrpD5sDs8fOWXfZPZYs+cnkcXnla+YA5igum5TUnMyy1CJ9uwSujKOXVrMV/BWumNxynr2B cbFAFyMnh4SAicTMuRdZIWwxiQv31rN1MXJxCAkcZZSYsuMZG0hCSGAZo8S7u9FdjBwcbEAN z5+xgIRFBCIl/r+fBNbLLCAhcX3COyYQW1ggX+L+jV5WiJoCifN/D0LVG0mcnjmNEcRmEVCR uHr6OzvISF4BX4mTR8Ig1t5mlNg+uYsZpIZTwEri9IFWsJmMQLd9P7WGCWKXuMStJ/OZIG4W kFiy5zwzhC0q8fLxP6hflCQmLT0HdZuOxILdn9ggbG2JZQtfg9XzCghKnJz5hGUCo9gsJGNn IWmZhaRlFpKWBYwsqxg5SosLcnLTjQw2MQLj5pgEm+4OxvvTPQ8xCnAwKvHwLjjFGC7EmlhW XJl7iFGCg1lJhDfjJ1O4EG9KYmVValF+fFFpTmrxIUZpDhYlcd7G4H9hQgLpiSWp2ampBalF MFkmDk6pBsZQ1qCImga5M/IxfxSPmLj/vuKtq9gl0eI/R7740Ie5Uz+/fx4d+ompY7JIyuWk txyTZxvuXX5uc9XNz/uF7i3d6LVtnmJ3bVX/L12JdWtnai2tmjtHarM146JJdbvVdYXrFu0o 3/WzYHJg5cOLD+eyRhfd7ts3i3f2wdXL8uW/lVcbKzmfqdFVYinOSDTUYi4qTgQAwTFaSJcC AAA=
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/87l0do1y77W2vwkLEW5nGGP83cE>
Cc: IETF <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: Tue, 05 Apr 2016 00:30:51 -0000

We all have the best interests of the community in mind, but invariably, th=
e individual views and objectives of the members of a diverse organization =
may not always align. Hence this civil and respectful dialogue has been hel=
pful in understanding the various positions of the participants (lower "p"!=
). The position that I have taken is that the community is best served when=
 the ADs and WG chairs are provided certainty when doing their jobs.  While=
 it is good to have guideposts (Do the right thing), ultimately they have t=
o have easy to understand rules.  That being said, I would continue to prop=
ose the removal of the words "reasonably and" from 5.1.2 to conform it to t=
he consensus that one need not undertake an IP search prior to acting on a =
Contribution. Also, because no-one should be expected to predict the outcom=
e of the uncertain patent prosecution process, the phrase "may ultimately C=
over that Contribution" should be deleted in Section 5.1.2.=20

Thus, I would propose Section 5.1.2 be amended as follows:

If an individual Participates relative to a written Contribution (other tha=
n a Contribution that is not intended to be used as an input into the IETF =
Standards Process) made by another person and such Participant    personall=
y knows of IPR meeting the conditions of Section 5.6 which the Participant =
believes Covers, or which the Participant personally knows his or her emplo=
yer or sponsor may assert against Implementing Technologies based on such w=
ritten Contribution, then such Participant must make a disclosure in accord=
ance with this Section 5.

The changes to "Participating in an IETF discussion or activity" and "Parti=
cipating" are good:

k. Participating in an IETF discussion or activity": means making a Contrib=
ution, as described above, or in any other way acting in order to influence=
 the outcome of a discussion relating to the IETF Standards Process. Withou=
t limiting the generality of the foregoing, acting as a working group chair=
 constitutes "Participating" in all activities of the relevant working grou=
p. "Participant" and "IETF Participant" mean any individual Participating i=
n an IETF discussion or activity. By the nature of their office, IETF area =
directors may become aware of Contributions late in the process (for exampl=
e at IETF Last Call or during IESG review) and, therefore and in such cases=
, cannot be expected to disclose any IPR Covering those Contributions until=
 they become aware of them.

Mike


From nobody Tue Apr  5 00:46:21 2016
Return-Path: <john-ietf@jck.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 DF75E12D53F for <ietf@ietfa.amsl.com>; Tue,  5 Apr 2016 00:46:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] 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 xX-BL1WHe32j for <ietf@ietfa.amsl.com>; Tue,  5 Apr 2016 00:46:17 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8C0C312D0E5 for <ietf@ietf.org>; Tue,  5 Apr 2016 00:46:17 -0700 (PDT)
Received: from [198.252.137.10] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1anLgj-000MRg-Ut; Tue, 05 Apr 2016 03:46:13 -0400
Date: Tue, 05 Apr 2016 03:46:08 -0400
From: John C Klensin <john-ietf@jck.com>
To: Michael Cameron <michael.cameron@ericsson.com>
Subject: RE: Last Call on draft-bradner-rfc3979bis-08.txt ("Intellectual Property Rights in IETF Technology")
Message-ID: <33C7B5EB4839C4AEEF6CF5BA@JcK-HP8200.jck.com>
In-Reply-To: <36BAA6A693139D4BBCB37CCCA660E08A14FC1914@eusaamb101.ericsson.se>
References: <0000431F-F977-4A24-BA4D-064F740977A0@piuha.net> <56FBF599.9080605@ericsson.com> <F99F459688AAAFCDCD5D9CC1@JcK-HP8200.jck.com> <5702CBA2.2060802@gmail.com> <5ABAE5DB070828F14822B6FD@JcK-HP8200.jck.com> <36BAA6A693139D4BBCB37CCCA660E08A14FC1914@eusaamb101.ericsson.se>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/bNf5jNdCEfJga-llUFZzPnuXZCw>
Cc: IETF <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: Tue, 05 Apr 2016 07:46:20 -0000

Mike,

We may just need to agree to disagree but, as Scott pointed out
and I remember from discussions at the time, the "reasonably"
language was the result of a long set of discussions and
negotiations with attorneys representing several organizations
that were active in supporting the IETF and a non-trivial number
of its participants.   I can't remember whether anyone from
Ericsson or any company that has since been absorbed by it were
included -- Scott would probably remember or could reconstruct
that if it were important.   My recollection is that the term
went in to avoid a potential loophole involving the need to
evaluate plausible deniability about what someone did or did not
know or believe.  Scott would probably remember (I don't and I'm
not sure I ever knew) if anyone made it a condition, e.g.,
indicated that they would, corporately, be uncomfortable about
having employees participate in the IETF unless that wording was
present.

These things are often a delicate balance and I think we need to
be careful about taking it out without, at least, going back and
consulting the original organizations to be sure that it
wouldn't result in their reducing participation in and/or
support for the IETF.

More generally, in a climate in which there are increasing
questions being asked about the effect of cross-licensing
agreements and "we won't sue you if you don't sue us, but, if
you do, all bets are off" provisions on competition (not a legal
opinion, just what I read in the press), I'm reluctant to start
making changes to text and policies that have been around for
some time except as dictated by questions of clarity (I put my
suggestions about reorganization to stress principles in that
category) or as dictated by experience (the claim I've
understood Scott and Jorge to make for this revision).  

Along those lines, I don't see any text that requires people to
predict the outcome of the patent prosecution process.  Any text
that required that would definitely be unacceptable, but the
text to which you refer (carried forward from Section 6.1.1 of
RFC 3979) says "_believes_ Covers or may ultimately Cover..."
(emphasis mine) and not "knows", "predicts" or any other term
involving the future.  

Finally, no matter what one does, there are no certain rules for
ADs or WG Chairs in this or almost any other area.  Not only are
the positions very much about the exercise of good judgment,
but, as soon as text introduces wording about beliefs
(reasonable or not), there is going to be uncertainty and the
possibility of abuse.  That is actually part of the reason I'd
like to see more introductory and rationale material based on
professional ethics rather than trying to specify things only
via a collection of rules that are subjective and tied to
people's assertions about what they believe or might have
believed at some time in the past.  If certainty were really our
goal, we would have gone for RAND or FRAND rules, not disclosure
ones.   It has regularly suggested that we drop all of this
disclosure complexity and uncertainty and go to that but the
community, including many of the companies who have been
involved, have rejected that idea every time it has come up. 

best,
    john



--On Tuesday, April 05, 2016 00:30 +0000 Michael Cameron
<michael.cameron@ericsson.com> wrote:

> We all have the best interests of the community in mind, but
> invariably, the individual views and objectives of the members
> of a diverse organization may not always align. Hence this
> civil and respectful dialogue has been helpful in
> understanding the various positions of the participants (lower
> "p"!). The position that I have taken is that the community is
> best served when the ADs and WG chairs are provided certainty
> when doing their jobs.  While it is good to have guideposts
> (Do the right thing), ultimately they have to have easy to
> understand rules.  That being said, I would continue to
> propose the removal of the words "reasonably and" from 5.1.2
> to conform it to the consensus that one need not undertake an
> IP search prior to acting on a Contribution. Also, because
> no-one should be expected to predict the outcome of the
> uncertain patent prosecution process, the phrase "may
> ultimately Cover that Contribution" should be deleted in
> Section 5.1.2. 
> 
> Thus, I would propose Section 5.1.2 be amended as follows:
> 
> If an individual Participates relative to a written
> Contribution (other than a Contribution that is not intended
> to be used as an input into the IETF Standards Process) made
> by another person and such Participant    personally knows of
> IPR meeting the conditions of Section 5.6 which the
> Participant believes Covers, or which the Participant
> personally knows his or her employer or sponsor may assert
> against Implementing Technologies based on such written
> Contribution, then such Participant must make a disclosure in
> accordance with this Section 5.
> 
> The changes to "Participating in an IETF discussion or
> activity" and "Participating" are good:
> 
> k. Participating in an IETF discussion or activity": means
> making a Contribution, as described above, or in any other way
> acting in order to influence the outcome of a discussion
> relating to the IETF Standards Process. Without limiting the
> generality of the foregoing, acting as a working group chair
> constitutes "Participating" in all activities of the relevant
> working group. "Participant" and "IETF Participant" mean any
> individual Participating in an IETF discussion or activity. By
> the nature of their office, IETF area directors may become
> aware of Contributions late in the process (for example at
> IETF Last Call or during IESG review) and, therefore and in
> such cases, cannot be expected to disclose any IPR Covering
> those Contributions until they become aware of them.
> 
> Mike





From nobody Tue Apr  5 06:29:05 2016
Return-Path: <stewe@stewe.org>
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 D2FD312D94B for <ietf@ietfa.amsl.com>; Tue,  5 Apr 2016 06:28:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.903
X-Spam-Level: 
X-Spam-Status: No, score=-1.903 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] 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 iy8oMejUyeTG for <ietf@ietfa.amsl.com>; Tue,  5 Apr 2016 06:28:55 -0700 (PDT)
Received: from na01-by2-obe.outbound.protection.outlook.com (mail-by2on0141.outbound.protection.outlook.com [207.46.100.141]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 478E312D949 for <ietf@ietf.org>; Tue,  5 Apr 2016 06:28:53 -0700 (PDT)
Received: from BLUPR17MB0275.namprd17.prod.outlook.com (10.162.235.146) by BLUPR17MB0273.namprd17.prod.outlook.com (10.162.235.144) with Microsoft SMTP Server (TLS) id 15.1.447.15; Tue, 5 Apr 2016 13:28:51 +0000
Received: from BLUPR17MB0275.namprd17.prod.outlook.com ([10.162.235.146]) by BLUPR17MB0275.namprd17.prod.outlook.com ([10.162.235.146]) with mapi id 15.01.0447.028; Tue, 5 Apr 2016 13:28:51 +0000
From: Stephan Wenger <stewe@stewe.org>
To: Michael Cameron <michael.cameron@ericsson.com>, John C Klensin <john-ietf@jck.com>, Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: Last Call on draft-bradner-rfc3979bis-08.txt ("Intellectual Property Rights in IETF Technology")
Thread-Topic: Last Call on draft-bradner-rfc3979bis-08.txt ("Intellectual Property Rights in IETF Technology")
Thread-Index: AQHRhDTbKR9yu1RueEWA9RrAiHSISp9yLyaAgAgVL4CAABEFAIAANCAAgAAS5gCAAKcXAA==
Date: Tue, 5 Apr 2016 13:28:50 +0000
Message-ID: <07C199A9-6072-4ECA-8CFF-D0BF782DAF20@stewe.org>
References: <0000431F-F977-4A24-BA4D-064F740977A0@piuha.net> <56FBF599.9080605@ericsson.com> <F99F459688AAAFCDCD5D9CC1@JcK-HP8200.jck.com> <5702CBA2.2060802@gmail.com> <5ABAE5DB070828F14822B6FD@JcK-HP8200.jck.com> <36BAA6A693139D4BBCB37CCCA660E08A14FC1914@eusaamb101.ericsson.se>
In-Reply-To: <36BAA6A693139D4BBCB37CCCA660E08A14FC1914@eusaamb101.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: ericsson.com; dkim=none (message not signed) header.d=none;ericsson.com; dmarc=none action=none header.from=stewe.org;
x-ms-exchange-messagesentrepresentingtype: 1
x-originating-ip: [2001:67c:370:176:a1d4:971e:488a:a5e2]
x-ms-office365-filtering-correlation-id: a46acee8-c5b2-4656-d66b-08d35d5639fb
x-microsoft-exchange-diagnostics: 1; BLUPR17MB0273; 5:2IoqDu6W1ugnlwJ+QUE5J5HzJDNEwQ0CfUQa+PTLGzxth9ba02LYTT0NWGhUyOvCp3Erii+bWV3Scl6GVd7t6YrxUqyXjw/DHSf33SXJoCrlymNIe477iKtx+WUx4rP6uyfYgPVGTNyQiWHTTZoXsQ==; 24:bRgVk6RnmejSAY6euLaycpP2saTZxsXffai1m9B4YRsymKr4a0YPBo+anem3P4TyQhv/PcOASlzUOawfYDfPE4XT3lmOLK+JT+VOQfW6FwY=
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:BLUPR17MB0273;
x-microsoft-antispam-prvs: <BLUPR17MB0273B068450F2D4ACC1A4368AE9E0@BLUPR17MB0273.namprd17.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040046)(601004)(2401047)(5005006)(8121501046)(10201501046)(3002001)(6041046)(6043046); SRVR:BLUPR17MB0273; BCL:0; PCL:0; RULEID:; SRVR:BLUPR17MB0273; 
x-forefront-prvs: 0903DD1D85
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(24454002)(83716003)(1220700001)(1096002)(4326007)(76176999)(54356999)(10400500002)(5008740100001)(6116002)(586003)(102836003)(87936001)(2950100001)(2900100001)(5001770100001)(189998001)(33656002)(50986999)(5004730100002)(77096005)(93886004)(5002640100001)(230783001)(106116001)(36756003)(122556002)(86362001)(99286002)(81166005)(11100500001)(92566002)(2906002)(19580405001)(82746002)(3280700002)(19580395003)(3660700001)(3826002)(42262002)(104396002); DIR:OUT; SFP:1102; SCL:1; SRVR:BLUPR17MB0273; H:BLUPR17MB0275.namprd17.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en; 
spamdiagnosticoutput: 1:23
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
Content-ID: <8F9EE72A444F284195018E55F93AB615@namprd17.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: stewe.org
X-MS-Exchange-CrossTenant-originalarrivaltime: 05 Apr 2016 13:28:50.7310 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 865fc51c-5fae-4322-98ef-0121a85df0b6
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BLUPR17MB0273
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/WO8Kd5cDeDB0C1tdXuZJ5TLerXw>
Cc: IETF <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: Tue, 05 Apr 2016 13:28:58 -0000

TWlrZSwgYWxsLA0KUmVmZXJyaW5nIG9ubHkgdG8gdGhpczoNCg0KDQoNCg0KDQpPbiA0LzQvMTYs
IDIxOjMwLCAiaWV0ZiBvbiBiZWhhbGYgb2YgTWljaGFlbCBDYW1lcm9uIiA8aWV0Zi1ib3VuY2Vz
QGlldGYub3JnIG9uIGJlaGFsZiBvZiBtaWNoYWVsLmNhbWVyb25AZXJpY3Nzb24uY29tPiB3cm90
ZToNCg0KPlsuLi5dDQo+QWxzbywgYmVjYXVzZSBuby1vbmUgc2hvdWxkIGJlIGV4cGVjdGVkIHRv
IHByZWRpY3QgdGhlIG91dGNvbWUgb2YgdGhlIHVuY2VydGFpbiBwYXRlbnQgcHJvc2VjdXRpb24g
cHJvY2VzcywgdGhlIHBocmFzZSAibWF5IHVsdGltYXRlbHkgQ292ZXIgdGhhdCBDb250cmlidXRp
b24iIHNob3VsZCBiZSBkZWxldGVkIGluIFNlY3Rpb24gNS4xLjIuIA0KPg0KPlRodXMsIEkgd291
bGQgcHJvcG9zZSBTZWN0aW9uIDUuMS4yIGJlIGFtZW5kZWQgYXMgZm9sbG93czoNCj4NCj5JZiBh
biBpbmRpdmlkdWFsIFBhcnRpY2lwYXRlcyByZWxhdGl2ZSB0byBhIHdyaXR0ZW4gQ29udHJpYnV0
aW9uIChvdGhlciB0aGFuIGEgQ29udHJpYnV0aW9uIHRoYXQgaXMgbm90IGludGVuZGVkIHRvIGJl
IHVzZWQgYXMgYW4gaW5wdXQgaW50byB0aGUgSUVURiBTdGFuZGFyZHMgUHJvY2VzcykgbWFkZSBi
eSBhbm90aGVyIHBlcnNvbiBhbmQgc3VjaCBQYXJ0aWNpcGFudCAgICBwZXJzb25hbGx5IGtub3dz
IG9mIElQUiBtZWV0aW5nIHRoZSBjb25kaXRpb25zIG9mIFNlY3Rpb24gNS42IHdoaWNoIHRoZSBQ
YXJ0aWNpcGFudCBiZWxpZXZlcyBDb3ZlcnMsIG9yIHdoaWNoIHRoZSBQYXJ0aWNpcGFudCBwZXJz
b25hbGx5IGtub3dzIGhpcyBvciBoZXIgZW1wbG95ZXIgb3Igc3BvbnNvciBtYXkgYXNzZXJ0IGFn
YWluc3QgSW1wbGVtZW50aW5nIFRlY2hub2xvZ2llcyBiYXNlZCBvbiBzdWNoIHdyaXR0ZW4gQ29u
dHJpYnV0aW9uLCB0aGVuIHN1Y2ggUGFydGljaXBhbnQgbXVzdCBtYWtlIGEgZGlzY2xvc3VyZSBp
biBhY2NvcmRhbmNlIHdpdGggdGhpcyBTZWN0aW9uIDUuDQo+Wy4uLl0NCg0KTXkgY3VycmVudCBm
ZWVsaW5nIGlzIHRoYXQgdGhlIHJlbW92YWwgb2YgdGhlIOKAnHVsdGltYXRlbHkgY292ZXJlZOKA
nSBwaHJhc2Ugd291bGQgaGF2ZSB0aGUgb3Bwb3NpdGUgZWZmZWN0IHlvdSBhcHBhcmVudGx5IGRl
c2lyZS4gIEl0IHdvdWxkIGxlYWQgdG8gbW9yZSBpcnJlbGV2YW50IGRpc2Nsb3N1cmVzLCBub3Qg
bGVzcy4NCg0KVGhlIGRlZmluaXRpb24gb2Yg4oCcQ292ZXLigJ0gaXMgZmFpcmx5IGJyb2FkLCBh
bmQgaW5jbHVkZXMgbm90IG9ubHkgImNsYWltcyBvZiBwYXRlbnQgYW5kIGFwcGxpY2F0aW9ucyAo
aW5jbHVkaW5nIHByb3Zpc2lvbmFsIGFwcGxpY2F0aW9ucynigJ0sIGJ1dCBhbHNvIOKAnG90aGVy
IElQUuKAnSwgYW5kIHRoYXQgSVBSLCBpbiBteSBpbnRlcnByZXRhdGlvbiwgd291bGQgYWxzbyBj
b3ZlciBwcm92aXNpb25hbCBhcHBsaWNhdGlvbnMgd2l0aG91dCBjbGFpbXMuICBJbiBvdGhlciB3
b3JkcywgZnJvbSB0aGUgZGVmaW5pdGlvbiBvZiDigJxDb3ZlcuKAnSBhbG9uZSBpdCBpcyBhbHJl
YWR5IGNsZWFyIHRvIG1lIHRoYXQgYSBkaXNjbG9zZXIgbXVzdCB0YWtlIGludG8gYWNjb3VudCBh
cHBsaWNhdGlvbnMgd2l0aCBhbGwgdGhlIHVuY2VydGFpbnR5IG9mIHRoZSBwcm9zZWN1dGlvbiBw
cm9jZXNzIHRoYXQgZW50YWlscy4gIFRoYXTigJlzIGludGVudGlvbmFsLCBhbmQgaG9wZWZ1bGx5
IG5vdCBzdWJqZWN0IG9mIHRoaXMgZGlzY3Vzc2lvbi4gIFdlIGRlZmluaXRlbHkgd2FudCBwZW9w
bGUgdG8gZGlzY2xvc2UgYXBwbGljYXRpb25zLCBhcyBlYXJseSBpbiB0aGVpciByZXNwZWN0aXZl
IHByb2Nlc3MgYXMgcG9zc2libGUuICANCg0KVGhlIHBocmFzZSDigJx1bHRpbWF0ZWx5IGNvdmVy
c+KAnSBnaXZlcyBzb21lIHdpZ2dsZSByb29tIHRvIGN1dCBkb3duIG9uIGRpc2Nsb3N1cmVzIG9m
IGFwcGxpY2F0aW9ucyB0aGF0IHVsdGltYXRlbHkgbWF5IG5vdCBjb3ZlciB0aGUgQ29udHJpYnV0
aW9uLCBidXQgd291bGQgYmFzZWQgb24gdGhlIGNsYWltcyBjdXJyZW50bHkgb24gZmlsZS4gIEks
IGF0IGxlYXN0LCBoYXZlIGludGVycHJldGVkIHRoYXQgcGhyYXNlIGluIHRoZSBwYXN0ICh5ZXMs
IGl0IGlzIHByZXNlbnQgaW4gUkZDIDM5NzkpIHN1Y2ggdGhhdCBpZiBJIHdlcmUgY2VydGFpbiB0
aGF0IGFuIG92ZXJicm9hZCBjbGFpbS0tbGlrZSB0aG9zZSByb3V0aW5lbHkgZmlsZWQgYnkgRXVy
b3BlYW4tdHJhaW5lZCBsYXd5ZXJzIHdoZW4gZmlsaW5nIFVTIHByb3Zpc2lvbmFscy0td2lsbCBu
b3Qgc3Vydml2ZSBwcm9zZWN1dGlvbiB1bmFtZW5kZWQsIEkgd291bGQgZGV0ZXJtaW5lIG15IGRp
c2Nsb3N1cmUgcmVxdWlyZW1lbnQgYmFzZWQgb24gbXkgaW50ZXJwb2xhdGlvbiBvZiBhIGNsYWlt
IHRoYXQgSSB0aGluayBjYW4gcmVhbGlzdGljYWxseSBzdXJ2aXZlLiAgSSBoYXBwZW4gdG8ga25v
dyB0aGF0IGF0IGxlYXN0IHR3byBJUFIgZGVwYXJ0bWVudHMgYWR2aXNlZCB0aGVpciBJRVRGIGRl
bGVnYXRlcyB0byBhY3Qgc2ltaWxhcmx5LiAgRG9pbmcgc28gY3V0cyBkb3duIG9uIHRoZSBkaXNj
bG9zdXJlIG9mIGFwcGxpY2F0aW9ucyB0aGF0IGFyZSBub3QgbGlrZWx5IHJlbGV2YW50IHRvIHRo
ZSBDb250cmlidXRpb24sIHdoaWxlIHN0aWxsIHByZXNlcnZpbmcgdGltZWxpbmVzcyBvZiBkaXNj
bG9zdXJlcywgaW5jbHVkaW5nIGRpc2Nsb3N1cmVzIGFnYWluc3QgcHJvdmlzaW9uYWxzLiAgDQoN
ClRoaXMgaXMg4oCccnVubmluZyBjb2Rl4oCdLCBhcyB3ZSBjYWxsIGl0IGluIHRoZSBJRVRGLiAg
VW5sZXNzIEkgc2VlIGEgdmVyeSBjbGVhciwgdmVyeSBkZXRhaWxlZCBleHBsYW5hdGlvbiAoaW5j
bHVkaW5nIGNhc2UgbGF3IGlmIGF2YWlsYWJsZSkgd2h5IGl0IGlzIGJhZCwgSSB3b3VsZCBiZSB2
ZXJ5IHJlbHVjdGFudCB0byBzdXBwb3J0IGEgY2hhbmdlLg0KDQpTdGVwaGFuDQoNCg0KDQoNCiAN
Cg0KDQoNCg0KDQo=


From nobody Tue Apr  5 08:22:11 2016
Return-Path: <joelja@bogus.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 01DB712D55E for <ietf@ietfa.amsl.com>; Tue,  5 Apr 2016 08:22:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.91
X-Spam-Level: 
X-Spam-Status: No, score=-6.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, T_RP_MATCHES_RCVD=-0.01] 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 y5vttooA5TPb for <ietf@ietfa.amsl.com>; Tue,  5 Apr 2016 08:22:06 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) (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 23ABB12D106 for <ietf@ietf.org>; Tue,  5 Apr 2016 08:22:04 -0700 (PDT)
Received: from dhcp-b257.meeting.ietf.org (dhcp-b257.meeting.ietf.org [31.133.178.87]) (authenticated bits=0) by nagasaki.bogus.com (8.14.9/8.14.9) with ESMTP id u35FLwl0094575 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Tue, 5 Apr 2016 15:22:00 GMT (envelope-from joelja@bogus.com)
Subject: Re: Last Call on draft-bradner-rfc3979bis-08.txt ("Intellectual Property Rights in IETF Technology")
To: Barry Leiba <barryleiba@computer.org>, Brian E Carpenter <brian.e.carpenter@gmail.com>
References: <0000431F-F977-4A24-BA4D-064F740977A0@piuha.net> <56FBF599.9080605@ericsson.com> <ACC702C9-C33F-4D38-B47A-8BC293D24621@sobco.com> <DCA1B6AC-6221-4CF5-A726-E1E98DBFAC27@vigilsec.com> <56FC90E5.1050908@gmail.com> <CAC4RtVD3Pxm_vZgdCCgPgDwNfnYeKFJ5_Ys3QQPezrHzTGJE+Q@mail.gmail.com>
From: joel jaeggli <joelja@bogus.com>
Message-ID: <8c3803d0-9ee6-650f-d1e4-87ace3c443ff@bogus.com>
Date: Tue, 5 Apr 2016 12:21:56 -0300
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.0
MIME-Version: 1.0
In-Reply-To: <CAC4RtVD3Pxm_vZgdCCgPgDwNfnYeKFJ5_Ys3QQPezrHzTGJE+Q@mail.gmail.com>
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="aDWBa7UQT3nPOImecqjkr4LNeejAVJ8dg"
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/TjMSRhMVmhG4JNHQiQPjH-CF5Zo>
Cc: IETF <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: Tue, 05 Apr 2016 15:22:09 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--aDWBa7UQT3nPOImecqjkr4LNeejAVJ8dg
Content-Type: multipart/mixed; boundary="74rJa8vWiR1XlgI6P6Dk7ExqhThlgofQd"
From: joel jaeggli <joelja@bogus.com>
To: Barry Leiba <barryleiba@computer.org>,
 Brian E Carpenter <brian.e.carpenter@gmail.com>
Cc: IETF <ietf@ietf.org>
Message-ID: <8c3803d0-9ee6-650f-d1e4-87ace3c443ff@bogus.com>
Subject: Re: Last Call on draft-bradner-rfc3979bis-08.txt ("Intellectual
 Property Rights in IETF Technology")
References: <0000431F-F977-4A24-BA4D-064F740977A0@piuha.net>
 <56FBF599.9080605@ericsson.com>
 <ACC702C9-C33F-4D38-B47A-8BC293D24621@sobco.com>
 <DCA1B6AC-6221-4CF5-A726-E1E98DBFAC27@vigilsec.com>
 <56FC90E5.1050908@gmail.com>
 <CAC4RtVD3Pxm_vZgdCCgPgDwNfnYeKFJ5_Ys3QQPezrHzTGJE+Q@mail.gmail.com>
In-Reply-To: <CAC4RtVD3Pxm_vZgdCCgPgDwNfnYeKFJ5_Ys3QQPezrHzTGJE+Q@mail.gmail.com>

--74rJa8vWiR1XlgI6P6Dk7ExqhThlgofQd
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

On 4/4/16 10:43 AM, Barry Leiba wrote:
>>> So, one might argue that an AD can be unaware that a particular
>>> document includes something that needs to be disclosed up to the
>>> point that they take some action on that document, such as sponsoring=
 it.
>>
>> Yes, but is that an issue? The AD is only required to disclose when
>> she is "reasonably and personally aware" of the need for a disclosure,=

>> which will presumably become the case when she actually reads the draf=
t
>> (or sees the slides that describe the technology in question).
>=20
> Be careful here: I think it is an issue.
>=20
> The "reasonably and personally aware" applies to the IPR, not to the
> participation.  If I'm participating in active discussion about
> Section 4 of document X, and I should be reasonably and personally
> aware of IPR my employer holds with respect to Section 3 of document
> X, we aren't going to happily accept that I didn't read Section 3 so I
> don't have a responsibility to disclose.
>=20
> If we're saying that, say, ADs are considered to be Participants with
> respect to every document and discussion in every working group in the
> area -- and I see why some people think that's wise and appropriate --
> then we're saying that I have a responsibility to disclose whether or
> not I've read the documents, and waiting until AD Evaluation state
> would be a late disclosure.  Consider that the working group might
> have been proceeding for a couple of years and many I-D revisions
> under the assumption that the technology is unencumbered... and then I
> dump an IPR statement on them just as they've finished.
>=20
> This really is a tough one: it would be nice if the late disclosure
> didn't happen, but ADs can't reasonably be expected to read every
> draft in every working group early on... and, as others have said, it
> would be very bad if this disclosure requirement gave us even fewer AD
> candidates than we have now.

Late disclosure might look bad, but we don't generally try and punish
people for attempting to correct situations that they reasonably might
be unaware of.

It is much more important that the late disclosure happen then that no
disclosure occur when one is warranted.

> Barry
>=20



--74rJa8vWiR1XlgI6P6Dk7ExqhThlgofQd--

--aDWBa7UQT3nPOImecqjkr4LNeejAVJ8dg
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2
Comment: GPGTools - http://gpgtools.org

iEYEARECAAYFAlcD2BUACgkQ8AA1q7Z/VrLFsgCeOQAG53H9pOrpDW8LX5G6J3rD
xuMAn19yK/iuq1fbbEfNda/NiuWVx9tr
=A+8D
-----END PGP SIGNATURE-----

--aDWBa7UQT3nPOImecqjkr4LNeejAVJ8dg--


From nobody Tue Apr  5 08:26:54 2016
Return-Path: <adrian@olddog.co.uk>
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 B051512D1C1 for <ietf@ietfa.amsl.com>; Tue,  5 Apr 2016 08:26:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.62
X-Spam-Level: 
X-Spam-Status: No, score=-2.62 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01] 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 HhISL4xhgtcj for <ietf@ietfa.amsl.com>; Tue,  5 Apr 2016 08:26:51 -0700 (PDT)
Received: from asmtp1.iomartmail.com (asmtp1.iomartmail.com [62.128.201.248]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A7DD312D157 for <ietf@ietf.org>; Tue,  5 Apr 2016 08:26:50 -0700 (PDT)
Received: from asmtp1.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp1.iomartmail.com (8.13.8/8.13.8) with ESMTP id u35FQmcF021450; Tue, 5 Apr 2016 16:26:48 +0100
Received: from 950129200 (dhcp-b176.meeting.ietf.org [31.133.177.118]) (authenticated bits=0) by asmtp1.iomartmail.com (8.13.8/8.13.8) with ESMTP id u35FQiKo021442 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO); Tue, 5 Apr 2016 16:26:46 +0100
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: <draft-leiba-cotton-iana-5226bis.all@tools.ietf.org>
References: <20160405133227.25939.47740.idtracker@ietfa.amsl.com>
In-Reply-To: <20160405133227.25939.47740.idtracker@ietfa.amsl.com>
Subject: FW: I-D Action: draft-leiba-cotton-iana-5226bis-12.txt
Date: Tue, 5 Apr 2016 16:26:41 +0100
Message-ID: <049e01d18f4f$904a45b0$b0ded110$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQDUrZL7Ep9u/D4LkqTUWDcSII0yHaF1Qe3w
Content-Language: en-gb
X-TM-AS-MML: disable
X-TM-AS-Product-Ver: IMSS-7.1.0.1679-8.0.0.1202-22240.007
X-TM-AS-Result: No--12.153-10.0-31-10
X-imss-scan-details: No--12.153-10.0-31-10
X-TMASE-MatchedRID: uIXscqjWAPlCBQieSpAGz3BRIrj8R47Fh8Ytn75ClDM9APipIEm6xP62 cy+dCX5TaMQFL6nCTW02c6uDK/rF8/H/rEyV9ntVibD9NG8qYdP6gI/+ywuCj11d55ms0luCrWV wOu7Bu1vVsXfkupVIqRar2jEX1DCkXSJ4c3nT+QdoMLOoNHsM9s9ZbgogvG8ExaQNbiRXdZohOd waoiaUInzvHCKIwjZeIx2isBen1esO0G36v8LMKszWN98iBBeGDZlTFg+eXzsLNAv/WTKB/liqA yk7LkbkdS/l9fGXMz0fzXumXQL3DAzyMxeMEX6wOX/V8P8ail3Yr6U3ZlQkdsRB0bsfrpPIfiAq rjYtFiQev05iH2BBogfdS2trjeLApSzXyni4ojivpy7uZTPpWH7cGd19dSFd
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/Oxv-JVaQ9XmD-F_9qN6p-mWLDlI>
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: adrian@olddog.co.uk
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: Tue, 05 Apr 2016 15:26:52 -0000

Michelle and Barry,

Thanks for resurrecting this document. It's been a while and IIRC the document
was somewhere in the IESG process post IETF last call. You seem to have made
some pretty substantial changes: I wonder if you could post a summary. I also
wonder whether the Shepherding AD could let us know whether this will come back
for a further IETF last call (I can relax and read it later) or plans to go for
approval with only IESG sign-off (I need to read it urgently and scream if there
are issues).

FWIW, I noticed that section 1.2 now has some text in double square brackets
that seeks to (temporarily?) describe what material should go on the first
version of https://iana.org/help/protocol-registration. Can I suggest that you
make the RFC-to-be stable and future-proof by converting this to a description
of a minimal subset of information that should be on the web page in the first
and all subsequent versions (i.e., information that should be on the page,
period) and then you can remove the brackets.

Thanks,
Adrian

> -----Original Message-----
> From: I-D-Announce [mailto:i-d-announce-bounces@ietf.org] On Behalf Of
> internet-drafts@ietf.org
> Sent: 05 April 2016 14:32
> To: i-d-announce@ietf.org
> Subject: I-D Action: draft-leiba-cotton-iana-5226bis-12.txt
> 
> 
> A New Internet-Draft is available from the on-line Internet-Drafts
directories.


From nobody Tue Apr  5 09:42:14 2016
Return-Path: <barryleiba@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 A56D712D769 for <ietf@ietfa.amsl.com>; Tue,  5 Apr 2016 09:42:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.4
X-Spam-Level: 
X-Spam-Status: No, score=-2.4 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.199, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 TR59HCc6ohmc for <ietf@ietfa.amsl.com>; Tue,  5 Apr 2016 09:42:03 -0700 (PDT)
Received: from mail-yw0-x22e.google.com (mail-yw0-x22e.google.com [IPv6:2607:f8b0:4002:c05::22e]) (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 1901012D761 for <ietf@ietf.org>; Tue,  5 Apr 2016 09:42:03 -0700 (PDT)
Received: by mail-yw0-x22e.google.com with SMTP id g3so23538553ywa.3 for <ietf@ietf.org>; Tue, 05 Apr 2016 09:42:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc; bh=4CadfECHLRNraHD7Obm1X2v/jgPueqZIu2ha3g3N/PU=; b=tNWNrPlnKunwYs6WAq3DufbqQ87lYqo8xCeBurpioP9wBHusppImD9nCJocZOyE6eO wUDCvP169W2TgSYoTyT1L5V3pMIei0zQBjJAp7IfrK1nzNK4HFnt7+RrmFWe7n1NP4c7 0B9+a3mMX8yFr4LBN77EgGhMtdxE0TNvhNgdZ410FGvWbn9mBdAHapH91GmqyIyif1HS qsbVI85q7PmS4/rfbKCCxTCi0Ayj0Ba8JV5acNUp56lz9cmp/fYTNUvRu5F1WiB1XwbG 0/S1imkL5g/wNpV3hG8SHgxOmFklFoCoH05BqIRVYTQ8iKOO6+LNqDr8vaY3zt35JRWO RkyA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:date :message-id:subject:from:to:cc; bh=4CadfECHLRNraHD7Obm1X2v/jgPueqZIu2ha3g3N/PU=; b=NVohu04FRWAF0bxzqAfVuTjPq3GFXms9ez43YLzlWFzTNg08csUR23Mlu6nx1wediL t+7YVQUXgKKW0NyG54Fj6Knjb/O69vSu9Q3h+a2DiGOaxbctR9QntX8wOIK+TAovrYx1 EBY72auUBdd8aFxt6bCWO4FV+7wdHMCMNh1JU53sODec2CsKBb82fe5vR/Th865JT3kf 9+xL3ET8qThEnXGghUX5eiVTS9rWae3FdSp4gWrYMAW/h1VBB646HcNHc006/8kQqukB ccbNuAAxMvRcl5OzHJ6TwjD1vfszMldQhUOr4dMHoYbyISFAhm+HxwCV+C/DCLT0QK7I 9Tjw==
X-Gm-Message-State: AD7BkJIeC14lMhRI7gaNjq64ciNZcQKTbtHCq7JiuHPcn46q64hjVRJa1Kc192Sv6TcT6suTiI7UpTKqxQqx5g==
MIME-Version: 1.0
X-Received: by 10.129.71.135 with SMTP id u129mr11577015ywa.162.1459874522347;  Tue, 05 Apr 2016 09:42:02 -0700 (PDT)
Sender: barryleiba@gmail.com
Received: by 10.83.28.67 with HTTP; Tue, 5 Apr 2016 09:42:02 -0700 (PDT)
In-Reply-To: <049e01d18f4f$904a45b0$b0ded110$@olddog.co.uk>
References: <20160405133227.25939.47740.idtracker@ietfa.amsl.com> <049e01d18f4f$904a45b0$b0ded110$@olddog.co.uk>
Date: Tue, 5 Apr 2016 12:42:02 -0400
X-Google-Sender-Auth: P6ctW_0-SkGKfjfbPbOrEX9vlkE
Message-ID: <CALaySJ+PcAyxuB7iAm2xHvDRREoQoAVEyBYNAoF_1rfMK5i6RQ@mail.gmail.com>
Subject: Re: FW: I-D Action: draft-leiba-cotton-iana-5226bis-12.txt
From: Barry Leiba <barryleiba@computer.org>
To: adrian@olddog.co.uk
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/vsH1sDizF0QWilfycn4R3SN9Ay4>
Cc: "draft-leiba-cotton-iana-5226bis.all@tools.ietf.org" <draft-leiba-cotton-iana-5226bis.all@tools.ietf.org>, IETF discussion list <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: Tue, 05 Apr 2016 16:42:12 -0000

> Thanks for resurrecting this document. It's been a while and IIRC the document
> was somewhere in the IESG process post IETF last call. You seem to have made
> some pretty substantial changes: I wonder if you could post a summary.

That'd be really difficult at this point, though one way you can
discern what I've done is to look at the old IESG ballot.  I addressed
pretty much all the comments there, save a few that I disagreed with.
And there is, of course, the diff tool, which should mostly help.

> wonder whether the Shepherding AD could let us know whether this will come back
> for a further IETF last call (I can relax and read it later) or plans to go for
> approval with only IESG sign-off (I need to read it urgently and scream if there
> are issues).

I've also asked Terry, who is now the sponsoring AD, to decide whether
a new IETF last call is needed.  It will certainly need a fresh IESG
ballot and a new telechat appearance at the least.  Whether the
changes are substantive enough to need a new last call is something
that I, myself, am of two minds on.

> FWIW, I noticed that section 1.2 now has some text in double square brackets
> that seeks to (temporarily?) describe what material should go on the first
> version of https://iana.org/help/protocol-registration. Can I suggest that you
> make the RFC-to-be stable and future-proof by converting this to a description
> of a minimal subset of information that should be on the web page in the first
> and all subsequent versions (i.e., information that should be on the page,
> period) and then you can remove the brackets.

Indeed; that is the intent.  I wanted to get the text out for review
and further processing while I work with Michelle on getting the
initial page populated and posted.

Barry


From nobody Tue Apr  5 10:06:58 2016
Return-Path: <terry.manderson@icann.org>
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 6859E12D7BB for <ietf@ietfa.amsl.com>; Tue,  5 Apr 2016 10:06:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level: 
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 erjQbACcXtDC for <ietf@ietfa.amsl.com>; Tue,  5 Apr 2016 10:06:55 -0700 (PDT)
Received: from out.west.pexch112.icann.org (pfe112-ca-1.pexch112.icann.org [64.78.40.7]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0125512D797 for <ietf@ietf.org>; Tue,  5 Apr 2016 10:06:55 -0700 (PDT)
Received: from PMBX112-W1-CA-1.pexch112.icann.org (64.78.40.21) by PMBX112-W1-CA-1.pexch112.icann.org (64.78.40.21) with Microsoft SMTP Server (TLS) id 15.0.1130.7; Tue, 5 Apr 2016 10:06:52 -0700
Received: from PMBX112-W1-CA-1.pexch112.icann.org ([64.78.40.21]) by PMBX112-W1-CA-1.PEXCH112.ICANN.ORG ([64.78.40.21]) with mapi id 15.00.1130.005; Tue, 5 Apr 2016 10:06:52 -0700
From: Terry Manderson <terry.manderson@icann.org>
To: Barry Leiba <barryleiba@computer.org>, "adrian@olddog.co.uk" <adrian@olddog.co.uk>
Subject: Re: I-D Action: draft-leiba-cotton-iana-5226bis-12.txt
Thread-Topic: I-D Action: draft-leiba-cotton-iana-5226bis-12.txt
Thread-Index: AQHRj12MntWzKvqu50SsRk7Spf3a7w==
Date: Tue, 5 Apr 2016 17:06:52 +0000
Message-ID: <D32A2AAA.80C48%terry.manderson@icann.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.6.2.160219
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [192.0.32.234]
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="B_3542756807_12727132"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/aDQc_2P9lBJddNxvvHbB71q_3OM>
Cc: "draft-leiba-cotton-iana-5226bis.all@tools.ietf.org" <draft-leiba-cotton-iana-5226bis.all@tools.ietf.org>, IETF discussion list <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: Tue, 05 Apr 2016 17:06:56 -0000

--B_3542756807_12727132
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit


On 6/04/2016, 2:42 AM, "barryleiba@gmail.com on behalf of Barry Leiba"
<barryleiba@gmail.com on behalf of barryleiba@computer.org> wrote:

>
>I've also asked Terry, who is now the sponsoring AD, to decide whether
>a new IETF last call is needed.  It will certainly need a fresh IESG
>ballot and a new telechat appearance at the least.  Whether the
>changes are substantive enough to need a new last call is something
>that I, myself, am of two minds on.


Given the fact that this document has been with the IESG for a long time,
and that a number of the raised DISCUSS items were indeed substantial in
my eyes, I would very much like the community to take a fresh look. I will
be reissuing the IETF LC shortly after IETF95.

Cheers
Terry

--B_3542756807_12727132
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"

MIIYwwYJKoZIhvcNAQcCoIIYtDCCGLACAQExCzAJBgUrDgMCGgUAMAsGCSqGSIb3DQEHAaCC
FowwggV0MIIEXKADAgECAhAJ0fxYYYV36W1njUywVtW8MA0GCSqGSIb3DQEBCwUAMGUxCzAJ
BgNVBAYTAlVTMRUwEwYDVQQKEwxEaWdpQ2VydCBJbmMxGTAXBgNVBAsTEHd3dy5kaWdpY2Vy
dC5jb20xJDAiBgNVBAMTG0RpZ2lDZXJ0IFNIQTIgQXNzdXJlZCBJRCBDQTAeFw0xNTAzMjYw
MDAwMDBaFw0xODAzMjYxMjAwMDBaMIGQMQswCQYDVQQGEwJVUzETMBEGA1UECBMKQ2FsaWZv
cm5pYTEUMBIGA1UEBxMLTG9zIEFuZ2VsZXMxPDA6BgNVBAoTM0ludGVybmV0IENvcnBvcmF0
aW9uIGZvciBBc3NpZ25lZCBOYW1lcyBhbmQgTnVtYmVyczEYMBYGA1UEAxMPVGVycnkgTWFu
ZGVyc29uMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAwTImt0Ol/9dOAbnm4lby
4RG1iQEnHVB5UJTYqwX8kqEhA5NPFHbMX22ChnP7M/zIlY+OP2TfKcwfdF5DJN4ybt4gFGzE
9ksigMe365F0uA2Q4+CskwqWo2fGIqrhgb0C68bg6EnZxj73KlJ0mvbQqzLBY8fVwr8srWpB
BexjbYSeXp/+0W41ZOJPcdii59TDXRBGuziWjp+rd7yh8KCzKcj/Px1TzAE5U/TftZOfigYi
h6KTTDZBGnN+4DDaaCnZ93rveayavI3hd4agqiIWe/gB78+0vHyk5DFoe6HkwuL0qJVaBW57
KIt8AYq+p0P+igNhiQoHkPx3VvS7ZViGdQIDAQABo4IB8jCCAe4wHwYDVR0jBBgwFoAU5wIj
gABP2Ne8lAvZP3Q5STI8inkwHQYDVR0OBBYEFIXwv/ZX+K34v+mCL8g1Coo9c6lMMAwGA1Ud
EwEB/wQCMAAwJAYDVR0RBB0wG4EZdGVycnkubWFuZGVyc29uQGljYW5uLm9yZzAOBgNVHQ8B
Af8EBAMCBaAwHQYDVR0lBBYwFAYIKwYBBQUHAwIGCCsGAQUFBwMEMEMGA1UdIAQ8MDowOAYK
YIZIAYb9bAQBAjAqMCgGCCsGAQUFBwIBFhxodHRwczovL3d3dy5kaWdpY2VydC5jb20vQ1BT
MIGIBgNVHR8EgYAwfjA9oDugOYY3aHR0cDovL2NybDMuZGlnaWNlcnQuY29tL0RpZ2lDZXJ0
U0hBMkFzc3VyZWRJRENBLWcxLmNybDA9oDugOYY3aHR0cDovL2NybDQuZGlnaWNlcnQuY29t
L0RpZ2lDZXJ0U0hBMkFzc3VyZWRJRENBLWcxLmNybDB5BggrBgEFBQcBAQRtMGswJAYIKwYB
BQUHMAGGGGh0dHA6Ly9vY3NwLmRpZ2ljZXJ0LmNvbTBDBggrBgEFBQcwAoY3aHR0cDovL2Nh
Y2VydHMuZGlnaWNlcnQuY29tL0RpZ2lDZXJ0U0hBMkFzc3VyZWRJRENBLmNydDANBgkqhkiG
9w0BAQsFAAOCAQEAH1Dvq3r4yh4+zU4t+5Rg3EzwMpSPxApBivVcW/KPq9uwdlu3yGBPJlG9
j4BXOT7fEUEGpCfyfRhBzTReyc2zask73fDRTzNFl5U3gqzOre5+Xtzv0qHyZGZ2EGcPTFv9
oaAVTug//Z6ZSr4dtDphV/7uSA4Hj1riFh5yxHErwUfrbCneIspVqwSVJqjkKWGID6W0YB0D
cYJZGlyAH0FP/4+TMDxXOti2ypQrsZpNSfvc4TGC1p13Lyp4XEY+UysVtcypAgersTBN6gCb
7ueBt5KPTj9pH4w4C0lNO6rRIc6AGtJIuXHYyiy9CXUTOT5xLToXLZCyPXd+HFuWwdD9lzCC
Bk4wggU2oAMCAQICEASueWBmZpAaucV/pmxb3M0wDQYJKoZIhvcNAQELBQAwZTELMAkGA1UE
BhMCVVMxFTATBgNVBAoTDERpZ2lDZXJ0IEluYzEZMBcGA1UECxMQd3d3LmRpZ2ljZXJ0LmNv
bTEkMCIGA1UEAxMbRGlnaUNlcnQgQXNzdXJlZCBJRCBSb290IENBMB4XDTEzMTEwNTEyMDAw
MFoXDTI4MTEwNTEyMDAwMFowZTELMAkGA1UEBhMCVVMxFTATBgNVBAoTDERpZ2lDZXJ0IElu
YzEZMBcGA1UECxMQd3d3LmRpZ2ljZXJ0LmNvbTEkMCIGA1UEAxMbRGlnaUNlcnQgU0hBMiBB
c3N1cmVkIElEIENBMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA3PgRIz9qte/A
J3kbLQWHohBDMd8O1BUbT3ekIs4+jHDwvgeO3ScqvAEdtiwKyt1pWB9B7WoFH9pjeFkeIiwr
+Lp+yTU7VvEffEJ+JbAjGcZFONc9RPkgfGCuHLBaGAS+jzv3qfCUmqYMY0m2QRdTQDK9T+ZQ
elAfJUXo8Ymvzf9e/1Dz8BcR/73FifW9YrnY+45FBIVtmc3FSE39JqsCNkXqNtdfauIagkEK
3OnZ9ZEXjsYhrTg8E+Yef2ac1U3ZRtr2z1KnfTskw7TBUTXGm+vU737kewPhRL16CzfgT8uC
ig1xGOSm4IksG/OyczzBsJKeGH29q33FfQihLMKfcwIDAQABo4IC+DCCAvQwEgYDVR0TAQH/
BAgwBgEB/wIBADAOBgNVHQ8BAf8EBAMCAYYwNAYIKwYBBQUHAQEEKDAmMCQGCCsGAQUFBzAB
hhhodHRwOi8vb2NzcC5kaWdpY2VydC5jb20wgYEGA1UdHwR6MHgwOqA4oDaGNGh0dHA6Ly9j
cmw0LmRpZ2ljZXJ0LmNvbS9EaWdpQ2VydEFzc3VyZWRJRFJvb3RDQS5jcmwwOqA4oDaGNGh0
dHA6Ly9jcmwzLmRpZ2ljZXJ0LmNvbS9EaWdpQ2VydEFzc3VyZWRJRFJvb3RDQS5jcmwwHQYD
VR0lBBYwFAYIKwYBBQUHAwIGCCsGAQUFBwMEMIIBswYDVR0gBIIBqjCCAaYwggGiBgpghkgB
hv1sAAIEMIIBkjAoBggrBgEFBQcCARYcaHR0cHM6Ly93d3cuZGlnaWNlcnQuY29tL0NQUzCC
AWQGCCsGAQUFBwICMIIBVh6CAVIAQQBuAHkAIAB1AHMAZQAgAG8AZgAgAHQAaABpAHMAIABD
AGUAcgB0AGkAZgBpAGMAYQB0AGUAIABjAG8AbgBzAHQAaQB0AHUAdABlAHMAIABhAGMAYwBl
AHAAdABhAG4AYwBlACAAbwBmACAAdABoAGUAIABEAGkAZwBpAEMAZQByAHQAIABDAFAALwBD
AFAAUwAgAGEAbgBkACAAdABoAGUAIABSAGUAbAB5AGkAbgBnACAAUABhAHIAdAB5ACAAQQBn
AHIAZQBlAG0AZQBuAHQAIAB3AGgAaQBjAGgAIABsAGkAbQBpAHQAIABsAGkAYQBiAGkAbABp
AHQAeQAgAGEAbgBkACAAYQByAGUAIABpAG4AYwBvAHIAcABvAHIAYQB0AGUAZAAgAGgAZQBy
AGUAaQBuACAAYgB5ACAAcgBlAGYAZQByAGUAbgBjAGUALjAdBgNVHQ4EFgQU5wIjgABP2Ne8
lAvZP3Q5STI8inkwHwYDVR0jBBgwFoAUReuir/SSy4IxLVGLp6chnfNtyA8wDQYJKoZIhvcN
AQELBQADggEBAE7UiSe5/R2Hd34PKAWQ8QovyTs+vZOckMav+pFRhzJUa+jKwXFRXJmOtfrg
YhmZpgeafBMn2+UCooQS2RX2CkRXxDSPbXMfOtagAT3e44LkRWuy6yX9gF4dOZC+W0L2zpFg
4/mgVgxIEM4zaHvNk6vwastPWA+5e10bBIGepyLiV0kn7pKTCL5pCFMCOi5dyBn0UIBOAtmw
XZG0k4f5lpaBVUCOZu2C2LsoX+1MYe0GWCgZUxFEvEcgKbIEbNiJVJk7ddtneCweknjGVT1Y
EhEybr1DDE0023vGQtvsvqubYUwGkuOO3yEqUFcEwGCiNdUknmY3CUnP1fhls+DibsIwggO3
MIICn6ADAgECAhAM5+DlF9hG/o/lYPwb8DA5MA0GCSqGSIb3DQEBBQUAMGUxCzAJBgNVBAYT
AlVTMRUwEwYDVQQKEwxEaWdpQ2VydCBJbmMxGTAXBgNVBAsTEHd3dy5kaWdpY2VydC5jb20x
JDAiBgNVBAMTG0RpZ2lDZXJ0IEFzc3VyZWQgSUQgUm9vdCBDQTAeFw0wNjExMTAwMDAwMDBa
Fw0zMTExMTAwMDAwMDBaMGUxCzAJBgNVBAYTAlVTMRUwEwYDVQQKEwxEaWdpQ2VydCBJbmMx
GTAXBgNVBAsTEHd3dy5kaWdpY2VydC5jb20xJDAiBgNVBAMTG0RpZ2lDZXJ0IEFzc3VyZWQg
SUQgUm9vdCBDQTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAK0OFc7kQ4BcsYfz
t2D5cRKlrtwmlIiq9M71IDkoWGAM+IDaqRWVMmE8tbEohIqK3J8KDIMXeo+QrIrneVNcMYQq
9g+YMjZ2zN7dPKii72r7IfJSYd+fINcf4rHZ/hhk0hJbX/lYGDW8R82hNvlrf9SwOD7BG8OM
M9nYLxj+KA+zp4PWw25EwGE1lhb+WZyLdm3X8aJLDSv/C3LanmDQjpA1xnhVhyChz+VtCshJ
fDGYM2wi6YfQMlqiuhOCEe05F52ZOnKh5vqk2dUXMXWuhX0irj8BRob2KHnIsdrkVxfEfhwO
sLSSplazvbKX7aqn8LfFqD+VFtD/oZbrCF8Yd08CAwEAAaNjMGEwDgYDVR0PAQH/BAQDAgGG
MA8GA1UdEwEB/wQFMAMBAf8wHQYDVR0OBBYEFEXroq/0ksuCMS1Ri6enIZ3zbcgPMB8GA1Ud
IwQYMBaAFEXroq/0ksuCMS1Ri6enIZ3zbcgPMA0GCSqGSIb3DQEBBQUAA4IBAQCiDrzf4u3w
43JzemSUv/dyZtgy5EJ1Yq6H6/LV2d5Ws5/MzhQouQ2XYFwSTFjk0z2DSUVYlzVpGqhH6lbG
easS2GeBhN9/CTyU5rgmLCC9PbMoifdf/yLil4Qf6WXvh+DfwWdJs13rsgkq6ybteL59Pyvz
tyY1bV+JAbZJW58BBZurPSXBzLZ/wvFvhsb6ZGjrgS2U60K3+owe3WLxvlBnt2y98/Efaww2
BxZ/N3ypW2168RJGYIPXJwS+S86XvsNnKmgR34DnDDNmvxMNFG7zfx9jEB76jRslbWyPpbdh
AbHSoyahEHGdreLD+cOZUbcrBwjOLuZQsqf6CkUvovDyMIIHAzCCBeugAwIBAgIQD89pSVGb
AJQ9+ZeKCcX9BTANBgkqhkiG9w0BAQUFADBiMQswCQYDVQQGEwJVUzEVMBMGA1UEChMMRGln
aUNlcnQgSW5jMRkwFwYDVQQLExB3d3cuZGlnaWNlcnQuY29tMSEwHwYDVQQDExhEaWdpQ2Vy
dCBBc3N1cmVkIElEIENBLTEwHhcNMTIwMzI3MDAwMDAwWhcNMTUwMzI3MTIwMDAwWjCBrDEL
MAkGA1UEBhMCVVMxEzARBgNVBAgTCkNhbGlmb3JuaWExFzAVBgNVBAcTDk1hcmluYSBkZWwg
UmV5MTwwOgYDVQQKEzNJbnRlcm5ldCBDb3Jwb3JhdGlvbiBmb3IgQXNzaWduZWQgTmFtZXMg
YW5kIE51bWJlcnMxFzAVBgNVBAsTDkROUyBPcGVyYXRpb25zMRgwFgYDVQQDEw9UZXJyeSBN
YW5kZXJzb24wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCkYWeFt1OjJ30tsKGB
BQiMjfoNTDSC6JG1CpPj05eZpit0LVkMU0jrtrHczcRzMuqdkaE/QTBjmprbRatlrMEq7uv+
yU9U35crRmjx3yuZDD/6SOO4ZnMFBJvWdevSOWq+8wU4hAEANOnBirYCfF4oixVCBy1bkat1
hsY5xUx5QB12OpnYA0/57QJ6BL7z1ZuF6lJ4yYmU0qI88q9atkahb8l7Nm5TgEbpg6ryyN98
ixnFLmhC/gPoYKHczP3y+JHaMveuJl75hHq6ZuHeH2PyX20VFsXNBKJrvZ8BhTZOoozuNapP
jiG6HLdqngPuTz3JVyTTR2FX809nclnxoMWjAgMBAAGjggNoMIIDZDAfBgNVHSMEGDAWgBQV
ABIrE5iymQftHt+ivlcNK2cCzTAdBgNVHQ4EFgQUs8L0dmF6T/V40vXJJzF+YNyzNo0wJAYD
VR0RBB0wG4EZdGVycnkubWFuZGVyc29uQGljYW5uLm9yZzAOBgNVHQ8BAf8EBAMCBaAwHQYD
VR0lBBYwFAYIKwYBBQUHAwQGCCsGAQUFBwMCMH0GA1UdHwR2MHQwOKA2oDSGMmh0dHA6Ly9j
cmwzLmRpZ2ljZXJ0LmNvbS9EaWdpQ2VydEFzc3VyZWRJRENBLTEuY3JsMDigNqA0hjJodHRw
Oi8vY3JsNC5kaWdpY2VydC5jb20vRGlnaUNlcnRBc3N1cmVkSURDQS0xLmNybDCCAcUGA1Ud
IASCAbwwggG4MIIBtAYKYIZIAYb9bAQBAjCCAaQwOgYIKwYBBQUHAgEWLmh0dHA6Ly93d3cu
ZGlnaWNlcnQuY29tL3NzbC1jcHMtcmVwb3NpdG9yeS5odG0wggFkBggrBgEFBQcCAjCCAVYe
ggFSAEEAbgB5ACAAdQBzAGUAIABvAGYAIAB0AGgAaQBzACAAQwBlAHIAdABpAGYAaQBjAGEA
dABlACAAYwBvAG4AcwB0AGkAdAB1AHQAZQBzACAAYQBjAGMAZQBwAHQAYQBuAGMAZQAgAG8A
ZgAgAHQAaABlACAARABpAGcAaQBDAGUAcgB0ACAAQwBQAC8AQwBQAFMAIABhAG4AZAAgAHQA
aABlACAAUgBlAGwAeQBpAG4AZwAgAFAAYQByAHQAeQAgAEEAZwByAGUAZQBtAGUAbgB0ACAA
dwBoAGkAYwBoACAAbABpAG0AaQB0ACAAbABpAGEAYgBpAGwAaQB0AHkAIABhAG4AZAAgAGEA
cgBlACAAaQBuAGMAbwByAHAAbwByAGEAdABlAGQAIABoAGUAcgBlAGkAbgAgAGIAeQAgAHIA
ZQBmAGUAcgBlAG4AYwBlAC4wdwYIKwYBBQUHAQEEazBpMCQGCCsGAQUFBzABhhhodHRwOi8v
b2NzcC5kaWdpY2VydC5jb20wQQYIKwYBBQUHMAKGNWh0dHA6Ly9jYWNlcnRzLmRpZ2ljZXJ0
LmNvbS9EaWdpQ2VydEFzc3VyZWRJRENBLTEuY3J0MAwGA1UdEwEB/wQCMAAwDQYJKoZIhvcN
AQEFBQADggEBAGKcMSvyr3YW8kKqyqdspTEKTc6lR6H6OITyC056f6PlMmFZ+nWlkopWlflz
QcxOUZv3+5rNogNcwczrxr+eaSx9J+pYCEU3rgBs3yiLDwsD72EJJDAD1x84fQOOJtfYb4oE
4Djzco83Dk4h6sMAiUg0xGcdewhJK80D6tb3xtS75PgFoxLcQrBprLghx2mY8EPErBiO1uXA
NWOEU3EH+kvXiKUrDsFyGHQ4FqvVIYv2plu68ltOmBh+wR2oraoJpt9jGbond1MyVFOvi48e
7hgPRXupNbjxB4Wl0wKKGz0qT3ToBpp8VAkULtjiO/iPLx4knuwwvy5sRAwuZAfpVE4xggH/
MIIB+wIBATB5MGUxCzAJBgNVBAYTAlVTMRUwEwYDVQQKEwxEaWdpQ2VydCBJbmMxGTAXBgNV
BAsTEHd3dy5kaWdpY2VydC5jb20xJDAiBgNVBAMTG0RpZ2lDZXJ0IFNIQTIgQXNzdXJlZCBJ
RCBDQQIQCdH8WGGFd+ltZ41MsFbVvDAJBgUrDgMCGgUAoF0wIwYJKoZIhvcNAQkEMRYEFFsa
J4sX8fqQgsdVDNI21+X9nfuNMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcN
AQkFMQ8XDTE2MDQwNTE3MDY0N1owDQYJKoZIhvcNAQEBBQAEggEAKY2dA/55IzjdUHsZgPeH
qvS7zRGTZYXbKmlhO00RbvHnJx/7Vnmk98UoqxVMC+oDNE3Itv2s/ODeyHLfNlWHGPe5PPsF
/wqDBIUrEj2ubY52WeDPbdkc9b+80yRSuXTSe/m/obIZHlcM8OR/Z99hohghKDUTRwibYeko
Lp7LiV3620OfgYmxQ525vcHhdzVCB1+FVdHCCvLnaXdpH/eG7biwFanXjexdF747GK2YClWU
XTFcpWOC6MQ5tgwVL0wJY0FL8BSBiwz1KT/czOuBTHAAVLE+qIJtu8Nm9T6dEoF7ZS7HXhAs
egCjVvdZ+R0cvIOQ8AJ1XhkM5uTSTJbUvg==

--B_3542756807_12727132--


From nobody Wed Apr  6 08:15:29 2016
Return-Path: <ggx@gigix.net>
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 F312112D5E6 for <ietf@ietfa.amsl.com>; Wed,  6 Apr 2016 08:15:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gigix-net.20150623.gappssmtp.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 fwTY-G9Hi1Va for <ietf@ietfa.amsl.com>; Wed,  6 Apr 2016 08:15:23 -0700 (PDT)
Received: from mail-qk0-x236.google.com (mail-qk0-x236.google.com [IPv6:2607:f8b0:400d:c09::236]) (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 767C912D6F9 for <ietf@ietf.org>; Wed,  6 Apr 2016 08:11:39 -0700 (PDT)
Received: by mail-qk0-x236.google.com with SMTP id i4so18759873qkc.3 for <ietf@ietf.org>; Wed, 06 Apr 2016 08:11:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gigix-net.20150623.gappssmtp.com; s=20150623; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=y08T5mNKZqTVThkn2h1K3qsZ9awbLMSt/67t5I8opbc=; b=kWFJ5DCXeLrJBgEBgRe1xvlvKZYC0BxPRhU+wyCunyAfDErYo+irTfxZ/+BFyqnJ2R gCoddBFHVnRgmQWWuzLVq+5aTWYM4zeAksytdmAQY1pcLeFo+q8aWCxa3dJ1O9sYPnyJ HlJK0y76WcoVpSsUP1eBY4LqVUye/v9brz8iPD07OzQDx4b4HqdjCdgoNFsLSz3quF3V aZHaDZMrVeXF/QkjdVSsXNtK/+3rEse4WWZA89BqBT+YNS1K7uIbFwiidNbqRECXifq2 Dapv4qRulLzqTDYY/x55SmJE6Q5UEUi52KoCtyLrgxLzk/1d0FYxLKq+95NNIsU+xMQv OL4A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=y08T5mNKZqTVThkn2h1K3qsZ9awbLMSt/67t5I8opbc=; b=BdZRdyk1fErjw0YIWxetzLu3BzesSkUyPQzCXRxK197oQXGkKHDjxifvryLj3oGQLa 3SifcXWGTVttZ+HtgMioUcc1wRQpQXIAARfXHChZnT8QN6JWVPCVbRWKgm5TtsJlo8U4 VRqOXXt3DZR5fI5WOWqddBVC09yHgn8RpoPIktiDeBUcG2SjCKgKhw6A8ZtqD20UocQ5 H1DmBWgE84dLGXCQxU8hsFDbe7RFVKPzExoBd75Xwd83hOR/HmZ5XCx9sMvc2JAs4ryh XcrEOf2J1/vDIOoGDt8K2GRAdhLZ3rzwYagrxnx1i0UrTvNgBJWeQ9Tz63zDkM6ZuIog /0uA==
X-Gm-Message-State: AD7BkJLeMOawS09v3XM4ldcI/+Slue6GNxBL2sflIMyFboONm7pII1bIht8wDRq0EnTwEQ==
X-Received: by 10.55.81.87 with SMTP id f84mr47605110qkb.10.1459955498544; Wed, 06 Apr 2016 08:11:38 -0700 (PDT)
Received: from dhcp-9bb9.meeting.ietf.org (dhcp-9bb9.meeting.ietf.org. [31.133.155.185]) by smtp.gmail.com with ESMTPSA id x10sm1425661qhc.42.2016.04.06.08.11.35 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Wed, 06 Apr 2016 08:11:37 -0700 (PDT)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Subject: Re: Gen-ART LC review of draft-ietf-lisp-eid-block-mgmnt-06
From: Luigi Iannone <ggx@gigix.net>
In-Reply-To: <007401d17c27$783d0a10$68b71e30$@akayla.com>
Date: Wed, 6 Apr 2016 12:11:34 -0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <296CE5D3-A607-4715-9D9D-DDEA9AB9AA5B@gigix.net>
References: <004001d1608f$ef60e6b0$ce22b410$@akayla.com> <30DBBD82-6F32-4D05-B1D6-0E2564855ED7@gigix.net> <B3384C62-EE51-4E80-9A75-B49AD16172C9@gigix.net> <00a701d1629f$7a9719a0$6fc54ce0$@akayla.com> <474E4613-8EB5-47AE-806E-086BE920855B@gigix.net> <1F7BB12F-63A0-4FA2-AAA5-79110671355B@gigix.net> <007401d17c27$783d0a10$68b71e30$@akayla.com>
To: Peter Yee <peter@akayla.com>
X-Mailer: Apple Mail (2.3124)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/KpZ4rafPFOIX4egM-GUU7TVZ8mE>
Cc: draft-ietf-lisp-eid-block-mgmnt.all@tools.ietf.org, IETF Gen-ART <gen-art@ietf.org>, IETF <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, 06 Apr 2016 15:15:27 -0000

Hi Peter,

Sorry for taking some time look at your comments.

Thanks again for the time you spend on the draft, I think it has =
improved a lot.

I as well that the proposed change address your comments (see my answers =
inline)

ciao

=20

> On 12 Mar 2016, at 03:21, Peter Yee <peter@akayla.com> wrote:
>=20
> Luigi,
> 	Please see my responses below prefixed with PEY>.
>=20
> 	Thanks.
>=20
> 		Kind regards,
> 		-Peter
>=20
> -----Original Message-----
> From: Luigi Iannone [mailto:ggx@gigix.net]=20
> Sent: Wednesday, February 24, 2016 8:31 AM
> To: Peter Yee
> Cc: draft-ietf-lisp-eid-block-mgmnt.all@tools.ietf.org; =
gen-art@ietf.org; ietf@ietf.org
> Subject: Re: Gen-ART LC review of draft-ietf-lisp-eid-block-mgmnt-06
>=20
> Hi Peter,
>=20
> since we cleared the minor issues we can move to the major issues.
>=20
> The IANA Consideration section was not exactly an example of clarity.
> So better to rewrite it=E2=80=A6.
>=20
> Hereafter  you can find my replies to your comments and at the end =
you=E2=80=99ll find the proposed text for the new IANA Consideration =
Section.
>=20
> Let me know if it works for you.
>=20
> ciao
>=20
> L.
>=20
>=20
>> Major issues:=20
>>=20
>> This draft does not give much management perspective nor many=20
>> procedures, perhaps because it calls itself a framework for =
management.
>=20
> Indeed, it is a guideline document.
> Having said that, RIPE had no difficulties in implementing the =
registration service.
>=20
> PEY>Sure, but that may well be because this draft is retrospective =
rather than prescriptive.  Meaning that it documents what was already =
done or expected to be, rather than telling a na=C3=AFve registrar your =
expectations of them.  As I noted earlier, given that you only expect =
one registrar and this is all being done as part of an experiment, I =
don't think we'll actually have a problem here.

OK thanks.




>=20
>> It mostly lists
>> data to be captured and discusses renewals periods.  It does not=20
>> discuss how requests are vetted or what would cause one to be=20
>> disapproved, if that's even a possibility.
>=20
> In Section 5, last bullet, and point 4 of section 6 there is =
information on what should be provided in order to have a soul =
registration request.
>=20
> PEY>That still doesn't address whether requests are vetted, it simply =
says that any can be an applicant, that they must explain why the =
parameters of why they want the registration, and that the details will =
be made public.  That's still not much in the way of guidance to the =
registrar.

I think the current proposed text fixes the issue:

       Anyone can obtain an entry in the EID prefix registry, on the
       understanding that the prefix so registered is for the exclusive
       use in the LISP experimental network, and that their registration
       details (as specified in Section 6) are openly published in the
       EID prefix registry.


Anyone can have it. Just provide some information and this is done. ;-)

>=20
>> It does not give any recourse for disapproved requests.
>> It does not specify how a request (whether pending or approved) is=20
>> abandoned or surrendered.  Consider section 3 of RFC 5226 as possibly=20=

>> being useful, for example.
>=20
> In the new IANA Considerations section FCFS policy is now spelled out.
>=20
> PEY>That's a helpful start and sort of implies that that all requests =
are granted and granted in the order received.  If that's the case, it =
would be useful to say so.

This is IMHO implicit in FCFS. RFC 5226 reads:

	    First Come First Served - Assignments are made to anyone on =
a
            first come, first served basis.  There is no substantive
            review of the request, other than to ensure that it is
            well-formed and doesn't duplicate an existing assignment.




>=20
>> Given the details that the draft does discuss, it really needs to=20
>> have an actual discussion of management procedures
>=20
> Can you be more specific on whether something else is missing?
>=20
> PEY>Pretend you are a na=C3=AFve registrar who has been hired to =
manage the EID prefix requests.  Does this document tell you enough to =
do your job successfully?  Does it tell registrants what they can expect =
of the process?  The document is titled "LISP EID Block Management =
Guidelines", yet it doesn't really say much about the management =
processes.

You might be right on the =E2=80=9Cnaive registar=E2=80=9D. But we are =
lucky enough and RIPE is not a naive registar.
Hence, may be is not worth to go in further details on this point.

>=20
>> or give a pointer as
>> to where these are discussed or how they are to be executed in =
concert=20
>> with the framework.
>>=20
>> Section 10 (IANA Considerations): This section seems inadequate from=20=

>> an RFC
>> 5226 perspective as well as simply throwing a lot on IANA to provide=20=

>> the lookup mechanism without giving any further guidance than a bunch=20=

>> of protocols (RDAP, WHOIS, HTTP, etc.)  Also see RFC 5226, Section =
4.2.
>> Specific requirements for IANA need to be clearly spelled out in this=20=

>> section, especially as there are potentially multiple registry=20
>> operators that are somehow involved in prefix allocation requests.
>=20
> As for the latest agreement with RIPE, actually IANA does not need to =
do anything.
> This is now speed out in the new reviewed section.
>=20
> PEY>That helps, but only on the assumption that RIPE already has an =
idea of what is expected of them.  Which seems to be the case.

Indeed. AFAIK they already implemented the registry. They just need the =
go ahead to open it.

>=20
>> This is not at all
>> made clear in the document how coordination between registry =
operators=20
>> and IANA is to be carried out.
>=20
> Since RIPE takes over all of the service, and will be the only one, =
there is no specific coordination to be performed.
>=20
> PEY>Good.  Removing the text about multiple registry operators also =
helps clear that point up.
>=20
>> It's not even clear whether users are supposed to be directly=20
>> requesting prefixes from IANA or whether IANA should reject such=20
>> requests.
>=20
> In the latest version is spelled out that requests have to go to RIPE.
>=20
> PEY>So, do requests from users go directly to RIPE?  Replace IANA in =
my comments with RIPE and then see if they are covered.

I think everything is ok.

>=20
>> There's no guidance on how IANA recognizes valid requests.
>=20
> Valid request are the ones respecting the content of this document.=20
> This is now spelled out in the new text.
>=20
> PEY>Okay.
>=20
>> There's no guidance on whether there is a limit to the number of=20
>> requests that may be made by an organization or individual.
>=20
> There is no limit. This is now spelled out in the new text.
>=20
> PEY>Good.
>=20
>> The document notes a
>> hierarchical distribution of the address space but gives no further=20=

>> guidance to IANA on how this hierarchy is to be organized and how=20
>> registration requests impact the hierarchy.
>=20
> The second bullet of section 5 has been deleted (as you also suggested =
elsewhere).
> Due to the limited duration of the experiment one single registration =
operator (RIPE) is sufficient.
>=20
> PEY>See?  I couldn't even tell that the hierarchy was organized around =
the registrars, or that's what seems to be implied by your statement =
above. Does going to a single registrar eliminate the hierarchy?  If =
not, along what lines does the registrar assign requests to the =
hierarchy?  Again, I go back to the na=C3=AFve registrar.  Reading this =
document, if I were that registrar, I would be wondering about those =
details.
>=20

Good. Problem is solved.

>> In short, a whole lot more needs to appear in this section and in the=20=

>> text leading up to it.
>=20
> Hopefully the proposed text fills the holes=E2=80=A6.
>=20
>>=20
>> Then again, I'm no LISP expert, so I could be completely off-base=20
>> here.  :-)
>>=20
>=20
> At this point actually more than you think ;-)
>=20
>=20
> %%%%%% NEW IANA SECTION PROPOSED TEXT %%%%%
>=20
> IANA Considerations
>=20
>   IANA allocated the following IPv6 address block for experimental use
>   as LISP EID prefix [I-D.ietf-lisp-eid-block]:
>=20
>   o  Address Block: 2001:5::/32
>=20
>   o  Name: EID Space for LISP
>=20
>   o  RFC: [I-D.ietf-lisp-eid-block]
>=20
>   o  Further Details at: http://www.iana.org/assignments/
>      iana-ipv6-special-registry/iana-ipv6-special-registry.xhtml
>=20
>   In order to grant requesting organisations and individuals exclusive
>   use of EID prefixes out of such reserved block (limited to the
>   duration of the LISP experiment as outlined in Section 7) there is =
an
>   operational requirement for an EID registration service.
>=20
>   Provided that the policies and requirements outlined in Section 4,
>   Section 5, and Section 6 are respected, EID prefix registration is
>   accorded based on a "First Come First Served" basis.
>   There is no hard limit in the number of registrations an =
organization
>   or individual can submit as long as information described in
>   Section 6 is provided, in particular point 4: "Experiment
>   Description".
>=20
>   IANA and RIPE NCC agreed for the latter to run such service on =
behalf
>   of the former, for the duration of the experiment and following the
>   procedures outlined in Section 10.  Therefore, this document has no
>   IANA actions.
>=20
> PEY>That helps to coalesce the disparate information given in sections =
4, 5, and 6 a bit.  It might not completely assist the na=C3=AFve =
registrar in managing the assignments, but I suspect RIPE already has =
this in hand.  Don't let my comments stand in the way of advancing this =
document if RIPE already knows what it's going to be doing and isn't =
looking for full-blown guidance.  I reviewed the document without regard =
to RIPE's background in it.  It seems obvious that there's additional =
knowledge that's borne outside of the document.  Placing that knowledge =
within the document would be nice for the historical record, but =
probably isn't necessary to run the experiment.
>=20

As I said above, you might be right about the naive registar, but RIPE =
already did the job.
Certainly your comments are helpful if in the future we go for a =
permanent allocation.

Thanks a lot again for your help.

ciao

L.



>=20
>> On 20 Feb 2016, at 04:29, Peter Yee <peter@akayla.com> wrote:
>>=20
>> Luigi,
>> 	Sorry for the tardy reply.  My comments below are prefaced with =
PEY>.
>>=20
>> 	Kind regards,
>> 	-Peter
>>=20
>> -----Original Message-----
>> From: Luigi Iannone [mailto:ggx@gigix.net]
>> Sent: Friday, February 12, 2016 3:06 AM
>> To: Peter Yee
>> Cc: draft-ietf-lisp-eid-block-mgmnt.all@tools.ietf.org;=20
>> gen-art@ietf.org; ietf@ietf.org
>> Subject: Re: Gen-ART LC review of draft-ietf-lisp-eid-block-mgmnt-06
>>=20
>> Hi Peter,
>>=20
>>> On 08 Feb 2016, at 19:35, Peter Yee <peter@akayla.com> wrote:
>>>=20
>>> No problem, Luigi.  I'll just be happy if my feedback proves =
helpful.
>>=20
>> It actually is and I realise that we did a pretty poor job in =
handling your review. Sorry for that.
>>=20
>> In order to progress, let me propose a incremental approach:
>>=20
>> Hereafter I put and comment everything that is minor issues.=20
>> Let me know if you are OK.
>>=20
>> Once we clear them we will go to the beefy stuff (aka major issues).
>>=20
>> ciao
>>=20
>> Luigi
>>=20
>>=20
>>>> Minor issues:=20
>>>>=20
>>>> Page 1, Abstract, 2nd sentence, "sub-prefixes": This term is not=20
>>>> defined and suffers from the same problem as ietf-lisp-eid-block in=20=

>>>> that is also used once in that document but not further described.
>>>> There appears to be some confusion between the use of prefix and =
sub-prefix that should be rectified.
>>>> Prefix in this document appears to generally mean sub-prefix with=20=

>>>> regards to the experimental block, but this is not made clear.
>>>>=20
>>=20
>> What about the following text:
>>=20
>> 	This document proposes a framework for the management of the
>> 	LISP EID Address Block. The framework described relies on =
hierarchical=20
>> 	distribution of the address space, granting temporary usage of =
prefixes of
>>       such space to requesting organizations.  =20
>>=20
>> PEY> I think that will finesse the prefix/sub-prefix issue.
>>=20
>>=20
>>>> Page 4, Section 5, items 1 and 2: considering that multiple=20
>>>> registries may be assigning these (sub-)prefixes and that they must=20=

>>>> be globally unique, is there a mechanism to ensure this other than=20=

>>>> waiting for the inevitable IANA clash between simultaneous =
registrations?
>>>>=20
>>=20
>> Fair enough. This was a degree of freedom we left to IANA. The =
requirement is globally uniqueness, how IANA, registries, or anybody =
else running the =E2=80=9CRegistry" want to sync to respect the =
requirement is something left as =E2=80=9Cimplementation specific=E2=80=9D=
.
>>=20
>> My personal take on this point is that since the experiment has a =
limited duration and because it is very likely that the only registry =
running the service will be RIPE NCC, there is no need to over-engineer =
this point.
>>=20
>> PEY> Somewhat agreed in that the actual usage should not cause any =
conflicts.  Note that S5 item 2 raises the concept of additional =
registries, and hence my concerns.  However, do note that Jari Arkko has =
raised concerns with the registry as well, so you may want to add =
language (and even consider removing S5 item 2) in order to reduce the =
confusion.
>>=20
>>=20
>>>> Nits:
>>>>=20
>>>> Page 3, Section 2, 1st paragraph, 1st sentence: change "separates"=20=

>>>> to "separate=E2=80=9D.
>> Thanks, will be fixed in -07.
>>=20
>>>>=20
>>>> Page 3, Section 2, 3rd paragraph: change "organisation" to =
"organization".
>>>> All other uses of the word in the document have been spelled=20
>>>> "organization", so make this usage consistent with the others.  Or=20=

>>>> change them all to "organisation" if that's preferred.  Pick one.
>> Thanks, will be fixed in -07.
>>=20
>>>>=20
>>>> Page 3, Section 3, 1st sentence: delete an extraneous space after=20=

>>>> the open parenthesis.
>> Thanks, will be fixed in -07.
>>=20
>>>>=20
>>>> Page 3, Section 4, 1st sentence: insert "for" between "request" and=20=

>>>> "registration".
>> Thanks, will be fixed in -07.
>>=20
>>>>=20
>>>> Page 4, 1st full paragraph, 4th sentence: insert "be" between=20
>>>> "should" and "no=E2=80=9D.
>> Does not apply anymore.
>>=20
>>>> Page 4, Section 5, item 3: insert a comma after "information". =20
>>>> Change "though" to "through=E2=80=9D.
>> Thanks, will be fixed in -07.
>>=20
>>>> Change "I-D.ietf-weirds-rdap-sec" to RFC 7481.
>> This is already fixed in -06.
>>=20
>>>> Change "whois" to "WHOIS".  Change "http" to "HTTP=E2=80=9D.
>> Thanks, will be fixed in -07.
>>=20
>>>>=20
>>>> Page 5, Section 6, 2nd paragraph: delete the comma after =
"registry".
>>>>=20
>>>> Page 5, Section 6, item 1: insert "the" between "In" and "case". =20=

>>>> Append a comma after "prefix=E2=80=9D.
>> Thanks, will be fixed in -07.
>>=20
>>>>=20
>>>> Page 5, Section 6, item 1: despite being based on the IANA PEN =
form,=20
>>>> how about adding a sub-item (d) for the organization's website? =20
>>>> This might allow for user disambiguation of registrants with =
similar names.
>> It does not harm actually. Will be added in -07.
>>=20
>>>>=20
>>>> Page 7, 1st partial paragraph, 1st partial sentence: insert "as"=20
>>>> between "so" and "to=E2=80=9D.
>> Thanks, will be fixed in -07.
>>=20
>>>>=20
>>>> Page 7, 1st full paragraph: delete the comma after "allocation=E2=80=9D=
.
>> Thanks, will be fixed in -07.
>>=20
>>>> Page 7, Section 8, 2nd paragraph: delete the comma after =
"reasons=E2=80=9D.
>> Thanks, will be fixed in -07.
>>=20
>>>> Page 7, Section 10, 2nd paragraph, 2nd sentence: insert "an" =
between "for"
>>>> and "EID=E2=80=9D.
>> This is already fixed in -06.
>>=20
>>>> Page 8, Section 11.1, [I-D.ietf-lisp-eid-block]: change the "-09" =
to "-11=E2=80=9D.
>> We are now at -12 and will keep the reference updated.
>>=20
>>>> Page 9, Appendix A: This appendix is almost wholly superfluous and=20=

>>>> unnecessary to understanding the core of the document.  Most terms=20=

>>>> that appear in the appendix make no other appearance in the body of=20=

>>>> the document and the definition of these terms does not inform a=20
>>>> reading of the body of the document.  I'd recommend dropping the=20
>>>> appendix and elsewhere in the document throwing in a pointer to RFC =
6830.
>>>>=20
>>>>=20
>>=20
>> This is a fair point and it has been raised also by other.=20
>> Let me answer in the same way: What is the aim in having such =
appendix?
>> - It is an appendix so its content is clearly optional.
>> - It clearly spells out that is not normative content but only to =
avoid the reader digging around to find the definitions.
>> - Some readers that do not know LISP might find it handy to have it =
around.
>>=20
>> PEY>I might suggest a separate Informational RFC that provides the =
information contained in the appendix for reference when using all of =
the LISP documents rather than burying it in a management framework.  =
But I also recognize that this may not be an expeditious way to progress =
things, so do no more than take my thoughts under advisement.
>>=20
>> ciao
>>=20
>> Luigi
>>=20
>>>=20
>>> 		-Peter
>>>=20
>>> -----Original Message-----
>>> From: Luigi Iannone [mailto:ggx@gigix.net]
>>> Sent: Monday, February 08, 2016 3:19 AM
>>> To: Luigi Iannone
>>> Cc: Peter Yee; draft-ietf-lisp-eid-block-mgmnt.all@tools.ietf.org;
>>> gen-art@ietf.org; ietf@ietf.org
>>> Subject: Re: Gen-ART LC review of draft-ietf-lisp-eid-block-mgmnt-06
>>>=20
>>>=20
>>>> On 08 Feb 2016, at 12:17, Luigi Iannone <ggx@gigix.net> wrote:
>>>>=20
>>>> Hi Peter,
>>>>=20
>>>> Back in April we indeed did not sent you a specific feedback.=20
>>>> Reason is that we received several comments/reviews and batched =
everything in a new I-D, with sending specific feedback to all.
>>>>=20
>>>=20
>>> The correct sentence is: =E2=80=9Cwithout sending specific feedback =
to all=E2=80=9D
>>>=20
>>> I should really start to proofread my mails before hitting the send=20=

>>> button  ;-)
>>>=20
>>> ciao
>>>=20
>>> L.
>>>=20
>>>> Yet, if you are unsatisfied on how we addressed the issues we =
certainly need to do more work.
>>>>=20
>>>> Give me some time to go again thoroughly through your first review =
and I=E2=80=99ll get back to you with a specific feedback.
>>>>=20
>>>> Thanks for your time spent on this document.
>>>>=20
>>>> ciao
>>>>=20
>>>> L.
>>>>=20
>>>>=20
>>>>=20
>>>>> On 06 Feb 2016, at 04:39, Peter Yee <peter@akayla.com> wrote:
>>>>>=20
>>>>> I am the assigned Gen-ART reviewer for this draft.  The General=20
>>>>> Area Review Team (Gen-ART) reviews all IETF documents being=20
>>>>> processed by the IESG for the IETF Chair.  Please treat these=20
>>>>> comments just like any other last call comment.  For background on=20=

>>>>> Gen-ART, please see the FAQ at=20
>>>>> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>
>>>>>=20
>>>>> Document: draft-ietf-lisp-eid-block-mgmnt-06
>>>>> Reviewer: Peter Yee
>>>>> Review Date: February 5, 2016
>>>>> IETF LC End Date: February 5, 2016
>>>>> IESG Telechat date: February 18, 2016
>>>>>=20
>>>>> Summary: This draft has serious issues, described in the review,=20=

>>>>> and needs to be rethought. [Not ready]
>>>>>=20
>>>>> The draft attempts to specify the framework for the management of=20=

>>>>> experimental LISP EID sub-prefixes, but really could use some=20
>>>>> additional work to flesh out the management aspects that are left =
unsaid.
>>>>>=20
>>>>> This draft fixes only two minor nits I raised in my review of the
>>>>> -04 version.  Nothing else has been addressed, nor have I received=20=

>>>>> any feedback on that review.  In light of this, I have little new =
to add.
>>>>> It is possible that the agreement between the IANA and the RIPE =
NCC=20
>>>>> will alleviate the major concern I had with the draft, but not=20
>>>>> being privy to that agreement, I can't make that determination.
>>>>>=20
>>>>> My original review with the unaddressed comments can be found =
here:
>>>>> =
https://www.ietf.org/mail-archive/web/gen-art/current/msg11620.html


From nobody Wed Apr  6 12:17:20 2016
Return-Path: <peter@akayla.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 F30BA12D52F; Wed,  6 Apr 2016 12:17:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.919
X-Spam-Level: 
X-Spam-Status: No, score=-1.919 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01] 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 Fg8yvecPufZT; Wed,  6 Apr 2016 12:17:15 -0700 (PDT)
Received: from p3plsmtpa08-09.prod.phx3.secureserver.net (p3plsmtpa08-09.prod.phx3.secureserver.net [173.201.193.110]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AF49112D13D; Wed,  6 Apr 2016 12:17:15 -0700 (PDT)
Received: from [31.133.177.150] ([31.133.177.150]) by p3plsmtpa08-09.prod.phx3.secureserver.net with  id f7H71s00M3F4iKB017HCay; Wed, 06 Apr 2016 12:17:14 -0700
User-Agent: Microsoft-MacOutlook/14.6.2.160219
Date: Wed, 06 Apr 2016 12:17:06 -0700
Subject: Re: Gen-ART LC review of draft-ietf-lisp-eid-block-mgmnt-06
From: Peter Yee <peter@akayla.com>
To: Luigi Iannone <ggx@gigix.net>
Message-ID: <D32AADA8.1668E%peter@akayla.com>
Thread-Topic: Gen-ART LC review of draft-ietf-lisp-eid-block-mgmnt-06
References: <004001d1608f$ef60e6b0$ce22b410$@akayla.com> <30DBBD82-6F32-4D05-B1D6-0E2564855ED7@gigix.net> <B3384C62-EE51-4E80-9A75-B49AD16172C9@gigix.net> <00a701d1629f$7a9719a0$6fc54ce0$@akayla.com> <474E4613-8EB5-47AE-806E-086BE920855B@gigix.net> <1F7BB12F-63A0-4FA2-AAA5-79110671355B@gigix.net> <007401d17c27$783d0a10$68b71e30$@akayla.com> <296CE5D3-A607-4715-9D9D-DDEA9AB9AA5B@gigix.net>
In-Reply-To: <296CE5D3-A607-4715-9D9D-DDEA9AB9AA5B@gigix.net>
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/ZsYII1aZR1io8wU7L9zJvmTtD1U>
Cc: draft-ietf-lisp-eid-block-mgmnt.all@tools.ietf.org, IETF Gen-ART <gen-art@ietf.org>, IETF <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, 06 Apr 2016 19:17:19 -0000

Luigi,
	Given the RIPE situation, I think we are all good to go.  I see that the
IESG has approved moving the document forward.  Congratulations. :-)

		Kind regards,
		-Peter

On 4/6/16, 8:11 AM, "Luigi Iannone" <ggx@gigix.net> wrote:

>Hi Peter,
>
>Sorry for taking some time look at your comments.
>
>Thanks again for the time you spend on the draft, I think it has improved
>a lot.
>
>I as well that the proposed change address your comments (see my answers
>inline)
>
>ciao
>
>=20
>
>> On 12 Mar 2016, at 03:21, Peter Yee <peter@akayla.com> wrote:
>>=20
>> Luigi,
>> 	Please see my responses below prefixed with PEY>.
>>=20
>> 	Thanks.
>>=20
>> 		Kind regards,
>> 		-Peter
>>=20
>> -----Original Message-----
>> From: Luigi Iannone [mailto:ggx@gigix.net]
>> Sent: Wednesday, February 24, 2016 8:31 AM
>> To: Peter Yee
>> Cc: draft-ietf-lisp-eid-block-mgmnt.all@tools.ietf.org;
>>gen-art@ietf.org; ietf@ietf.org
>> Subject: Re: Gen-ART LC review of draft-ietf-lisp-eid-block-mgmnt-06
>>=20
>> Hi Peter,
>>=20
>> since we cleared the minor issues we can move to the major issues.
>>=20
>> The IANA Consideration section was not exactly an example of clarity.
>> So better to rewrite it=E2=80=A6.
>>=20
>> Hereafter  you can find my replies to your comments and at the end
>>you=E2=80=99ll find the proposed text for the new IANA Consideration Section.
>>=20
>> Let me know if it works for you.
>>=20
>> ciao
>>=20
>> L.
>>=20
>>=20
>>> Major issues:=20
>>>=20
>>> This draft does not give much management perspective nor many
>>> procedures, perhaps because it calls itself a framework for management.
>>=20
>> Indeed, it is a guideline document.
>> Having said that, RIPE had no difficulties in implementing the
>>registration service.
>>=20
>> PEY>Sure, but that may well be because this draft is retrospective
>>rather than prescriptive.  Meaning that it documents what was already
>>done or expected to be, rather than telling a na=C3=AFve registrar your
>>expectations of them.  As I noted earlier, given that you only expect
>>one registrar and this is all being done as part of an experiment, I
>>don't think we'll actually have a problem here.
>
>OK thanks.
>
>
>
>
>>=20
>>> It mostly lists
>>> data to be captured and discusses renewals periods.  It does not
>>> discuss how requests are vetted or what would cause one to be
>>> disapproved, if that's even a possibility.
>>=20
>> In Section 5, last bullet, and point 4 of section 6 there is
>>information on what should be provided in order to have a soul
>>registration request.
>>=20
>> PEY>That still doesn't address whether requests are vetted, it simply
>>says that any can be an applicant, that they must explain why the
>>parameters of why they want the registration, and that the details will
>>be made public.  That's still not much in the way of guidance to the
>>registrar.
>
>I think the current proposed text fixes the issue:
>
>       Anyone can obtain an entry in the EID prefix registry, on the
>       understanding that the prefix so registered is for the exclusive
>       use in the LISP experimental network, and that their registration
>       details (as specified in Section 6) are openly published in the
>       EID prefix registry.
>
>
>Anyone can have it. Just provide some information and this is done. ;-)
>
>>=20
>>> It does not give any recourse for disapproved requests.
>>> It does not specify how a request (whether pending or approved) is
>>> abandoned or surrendered.  Consider section 3 of RFC 5226 as possibly
>>> being useful, for example.
>>=20
>> In the new IANA Considerations section FCFS policy is now spelled out.
>>=20
>> PEY>That's a helpful start and sort of implies that that all requests
>>are granted and granted in the order received.  If that's the case, it
>>would be useful to say so.
>
>This is IMHO implicit in FCFS. RFC 5226 reads:
>
>	    First Come First Served - Assignments are made to anyone on a
>            first come, first served basis.  There is no substantive
>            review of the request, other than to ensure that it is
>            well-formed and doesn't duplicate an existing assignment.
>
>
>
>
>>=20
>>> Given the details that the draft does discuss, it really needs to
>>> have an actual discussion of management procedures
>>=20
>> Can you be more specific on whether something else is missing?
>>=20
>> PEY>Pretend you are a na=C3=AFve registrar who has been hired to manage the
>>EID prefix requests.  Does this document tell you enough to do your job
>>successfully?  Does it tell registrants what they can expect of the
>>process?  The document is titled "LISP EID Block Management Guidelines",
>>yet it doesn't really say much about the management processes.
>
>You might be right on the =E2=80=9Cnaive registar=E2=80=9D. But we are lucky enough an=
d
>RIPE is not a naive registar.
>Hence, may be is not worth to go in further details on this point.
>
>>=20
>>> or give a pointer as
>>> to where these are discussed or how they are to be executed in concert
>>> with the framework.
>>>=20
>>> Section 10 (IANA Considerations): This section seems inadequate from
>>> an RFC
>>> 5226 perspective as well as simply throwing a lot on IANA to provide
>>> the lookup mechanism without giving any further guidance than a bunch
>>> of protocols (RDAP, WHOIS, HTTP, etc.)  Also see RFC 5226, Section 4.2.
>>> Specific requirements for IANA need to be clearly spelled out in this
>>> section, especially as there are potentially multiple registry
>>> operators that are somehow involved in prefix allocation requests.
>>=20
>> As for the latest agreement with RIPE, actually IANA does not need to
>>do anything.
>> This is now speed out in the new reviewed section.
>>=20
>> PEY>That helps, but only on the assumption that RIPE already has an
>>idea of what is expected of them.  Which seems to be the case.
>
>Indeed. AFAIK they already implemented the registry. They just need the
>go ahead to open it.
>
>>=20
>>> This is not at all
>>> made clear in the document how coordination between registry operators
>>> and IANA is to be carried out.
>>=20
>> Since RIPE takes over all of the service, and will be the only one,
>>there is no specific coordination to be performed.
>>=20
>> PEY>Good.  Removing the text about multiple registry operators also
>>helps clear that point up.
>>=20
>>> It's not even clear whether users are supposed to be directly
>>> requesting prefixes from IANA or whether IANA should reject such
>>> requests.
>>=20
>> In the latest version is spelled out that requests have to go to RIPE.
>>=20
>> PEY>So, do requests from users go directly to RIPE?  Replace IANA in my
>>comments with RIPE and then see if they are covered.
>
>I think everything is ok.
>
>>=20
>>> There's no guidance on how IANA recognizes valid requests.
>>=20
>> Valid request are the ones respecting the content of this document.
>> This is now spelled out in the new text.
>>=20
>> PEY>Okay.
>>=20
>>> There's no guidance on whether there is a limit to the number of
>>> requests that may be made by an organization or individual.
>>=20
>> There is no limit. This is now spelled out in the new text.
>>=20
>> PEY>Good.
>>=20
>>> The document notes a
>>> hierarchical distribution of the address space but gives no further
>>> guidance to IANA on how this hierarchy is to be organized and how
>>> registration requests impact the hierarchy.
>>=20
>> The second bullet of section 5 has been deleted (as you also suggested
>>elsewhere).
>> Due to the limited duration of the experiment one single registration
>>operator (RIPE) is sufficient.
>>=20
>> PEY>See?  I couldn't even tell that the hierarchy was organized around
>>the registrars, or that's what seems to be implied by your statement
>>above. Does going to a single registrar eliminate the hierarchy?  If
>>not, along what lines does the registrar assign requests to the
>>hierarchy?  Again, I go back to the na=C3=AFve registrar.  Reading this
>>document, if I were that registrar, I would be wondering about those
>>details.
>>=20
>
>Good. Problem is solved.
>
>>> In short, a whole lot more needs to appear in this section and in the
>>> text leading up to it.
>>=20
>> Hopefully the proposed text fills the holes=E2=80=A6.
>>=20
>>>=20
>>> Then again, I'm no LISP expert, so I could be completely off-base
>>> here.  :-)
>>>=20
>>=20
>> At this point actually more than you think ;-)
>>=20
>>=20
>> %%%%%% NEW IANA SECTION PROPOSED TEXT %%%%%
>>=20
>> IANA Considerations
>>=20
>>   IANA allocated the following IPv6 address block for experimental use
>>   as LISP EID prefix [I-D.ietf-lisp-eid-block]:
>>=20
>>   o  Address Block: 2001:5::/32
>>=20
>>   o  Name: EID Space for LISP
>>=20
>>   o  RFC: [I-D.ietf-lisp-eid-block]
>>=20
>>   o  Further Details at: http://www.iana.org/assignments/
>>      iana-ipv6-special-registry/iana-ipv6-special-registry.xhtml
>>=20
>>   In order to grant requesting organisations and individuals exclusive
>>   use of EID prefixes out of such reserved block (limited to the
>>   duration of the LISP experiment as outlined in Section 7) there is an
>>   operational requirement for an EID registration service.
>>=20
>>   Provided that the policies and requirements outlined in Section 4,
>>   Section 5, and Section 6 are respected, EID prefix registration is
>>   accorded based on a "First Come First Served" basis.
>>   There is no hard limit in the number of registrations an organization
>>   or individual can submit as long as information described in
>>   Section 6 is provided, in particular point 4: "Experiment
>>   Description".
>>=20
>>   IANA and RIPE NCC agreed for the latter to run such service on behalf
>>   of the former, for the duration of the experiment and following the
>>   procedures outlined in Section 10.  Therefore, this document has no
>>   IANA actions.
>>=20
>> PEY>That helps to coalesce the disparate information given in sections
>>4, 5, and 6 a bit.  It might not completely assist the na=C3=AFve registrar
>>in managing the assignments, but I suspect RIPE already has this in
>>hand.  Don't let my comments stand in the way of advancing this document
>>if RIPE already knows what it's going to be doing and isn't looking for
>>full-blown guidance.  I reviewed the document without regard to RIPE's
>>background in it.  It seems obvious that there's additional knowledge
>>that's borne outside of the document.  Placing that knowledge within the
>>document would be nice for the historical record, but probably isn't
>>necessary to run the experiment.
>>=20
>
>As I said above, you might be right about the naive registar, but RIPE
>already did the job.
>Certainly your comments are helpful if in the future we go for a
>permanent allocation.
>
>Thanks a lot again for your help.
>
>ciao
>
>L.
>
>
>
>>=20
>>> On 20 Feb 2016, at 04:29, Peter Yee <peter@akayla.com> wrote:
>>>=20
>>> Luigi,
>>> 	Sorry for the tardy reply.  My comments below are prefaced with PEY>.
>>>=20
>>> 	Kind regards,
>>> 	-Peter
>>>=20
>>> -----Original Message-----
>>> From: Luigi Iannone [mailto:ggx@gigix.net]
>>> Sent: Friday, February 12, 2016 3:06 AM
>>> To: Peter Yee
>>> Cc: draft-ietf-lisp-eid-block-mgmnt.all@tools.ietf.org;
>>> gen-art@ietf.org; ietf@ietf.org
>>> Subject: Re: Gen-ART LC review of draft-ietf-lisp-eid-block-mgmnt-06
>>>=20
>>> Hi Peter,
>>>=20
>>>> On 08 Feb 2016, at 19:35, Peter Yee <peter@akayla.com> wrote:
>>>>=20
>>>> No problem, Luigi.  I'll just be happy if my feedback proves helpful.
>>>=20
>>> It actually is and I realise that we did a pretty poor job in handling
>>>your review. Sorry for that.
>>>=20
>>> In order to progress, let me propose a incremental approach:
>>>=20
>>> Hereafter I put and comment everything that is minor issues.
>>> Let me know if you are OK.
>>>=20
>>> Once we clear them we will go to the beefy stuff (aka major issues).
>>>=20
>>> ciao
>>>=20
>>> Luigi
>>>=20
>>>=20
>>>>> Minor issues:
>>>>>=20
>>>>> Page 1, Abstract, 2nd sentence, "sub-prefixes": This term is not
>>>>> defined and suffers from the same problem as ietf-lisp-eid-block in
>>>>> that is also used once in that document but not further described.
>>>>> There appears to be some confusion between the use of prefix and
>>>>>sub-prefix that should be rectified.
>>>>> Prefix in this document appears to generally mean sub-prefix with
>>>>> regards to the experimental block, but this is not made clear.
>>>>>=20
>>>=20
>>> What about the following text:
>>>=20
>>> 	This document proposes a framework for the management of the
>>> 	LISP EID Address Block. The framework described relies on
>>>hierarchical=20
>>> 	distribution of the address space, granting temporary usage of
>>>prefixes of
>>>       such space to requesting organizations.
>>>=20
>>> PEY> I think that will finesse the prefix/sub-prefix issue.
>>>=20
>>>=20
>>>>> Page 4, Section 5, items 1 and 2: considering that multiple
>>>>> registries may be assigning these (sub-)prefixes and that they must
>>>>> be globally unique, is there a mechanism to ensure this other than
>>>>> waiting for the inevitable IANA clash between simultaneous
>>>>>registrations?
>>>>>=20
>>>=20
>>> Fair enough. This was a degree of freedom we left to IANA. The
>>>requirement is globally uniqueness, how IANA, registries, or anybody
>>>else running the =E2=80=9CRegistry" want to sync to respect the requirement is
>>>something left as =E2=80=9Cimplementation specific=E2=80=9D.
>>>=20
>>> My personal take on this point is that since the experiment has a
>>>limited duration and because it is very likely that the only registry
>>>running the service will be RIPE NCC, there is no need to over-engineer
>>>this point.
>>>=20
>>> PEY> Somewhat agreed in that the actual usage should not cause any
>>>conflicts.  Note that S5 item 2 raises the concept of additional
>>>registries, and hence my concerns.  However, do note that Jari Arkko
>>>has raised concerns with the registry as well, so you may want to add
>>>language (and even consider removing S5 item 2) in order to reduce the
>>>confusion.
>>>=20
>>>=20
>>>>> Nits:
>>>>>=20
>>>>> Page 3, Section 2, 1st paragraph, 1st sentence: change "separates"
>>>>> to "separate=E2=80=9D.
>>> Thanks, will be fixed in -07.
>>>=20
>>>>>=20
>>>>> Page 3, Section 2, 3rd paragraph: change "organisation" to
>>>>>"organization".
>>>>> All other uses of the word in the document have been spelled
>>>>> "organization", so make this usage consistent with the others.  Or
>>>>> change them all to "organisation" if that's preferred.  Pick one.
>>> Thanks, will be fixed in -07.
>>>=20
>>>>>=20
>>>>> Page 3, Section 3, 1st sentence: delete an extraneous space after
>>>>> the open parenthesis.
>>> Thanks, will be fixed in -07.
>>>=20
>>>>>=20
>>>>> Page 3, Section 4, 1st sentence: insert "for" between "request" and
>>>>> "registration".
>>> Thanks, will be fixed in -07.
>>>=20
>>>>>=20
>>>>> Page 4, 1st full paragraph, 4th sentence: insert "be" between
>>>>> "should" and "no=E2=80=9D.
>>> Does not apply anymore.
>>>=20
>>>>> Page 4, Section 5, item 3: insert a comma after "information".
>>>>> Change "though" to "through=E2=80=9D.
>>> Thanks, will be fixed in -07.
>>>=20
>>>>> Change "I-D.ietf-weirds-rdap-sec" to RFC 7481.
>>> This is already fixed in -06.
>>>=20
>>>>> Change "whois" to "WHOIS".  Change "http" to "HTTP=E2=80=9D.
>>> Thanks, will be fixed in -07.
>>>=20
>>>>>=20
>>>>> Page 5, Section 6, 2nd paragraph: delete the comma after "registry".
>>>>>=20
>>>>> Page 5, Section 6, item 1: insert "the" between "In" and "case".
>>>>> Append a comma after "prefix=E2=80=9D.
>>> Thanks, will be fixed in -07.
>>>=20
>>>>>=20
>>>>> Page 5, Section 6, item 1: despite being based on the IANA PEN form,
>>>>> how about adding a sub-item (d) for the organization's website?
>>>>> This might allow for user disambiguation of registrants with similar
>>>>>names.
>>> It does not harm actually. Will be added in -07.
>>>=20
>>>>>=20
>>>>> Page 7, 1st partial paragraph, 1st partial sentence: insert "as"
>>>>> between "so" and "to=E2=80=9D.
>>> Thanks, will be fixed in -07.
>>>=20
>>>>>=20
>>>>> Page 7, 1st full paragraph: delete the comma after "allocation=E2=80=9D.
>>> Thanks, will be fixed in -07.
>>>=20
>>>>> Page 7, Section 8, 2nd paragraph: delete the comma after "reasons=E2=80=9D.
>>> Thanks, will be fixed in -07.
>>>=20
>>>>> Page 7, Section 10, 2nd paragraph, 2nd sentence: insert "an" between
>>>>>"for"
>>>>> and "EID=E2=80=9D.
>>> This is already fixed in -06.
>>>=20
>>>>> Page 8, Section 11.1, [I-D.ietf-lisp-eid-block]: change the "-09" to
>>>>>"-11=E2=80=9D.
>>> We are now at -12 and will keep the reference updated.
>>>=20
>>>>> Page 9, Appendix A: This appendix is almost wholly superfluous and
>>>>> unnecessary to understanding the core of the document.  Most terms
>>>>> that appear in the appendix make no other appearance in the body of
>>>>> the document and the definition of these terms does not inform a
>>>>> reading of the body of the document.  I'd recommend dropping the
>>>>> appendix and elsewhere in the document throwing in a pointer to RFC
>>>>>6830.
>>>>>=20
>>>>>=20
>>>=20
>>> This is a fair point and it has been raised also by other.
>>> Let me answer in the same way: What is the aim in having such appendix?
>>> - It is an appendix so its content is clearly optional.
>>> - It clearly spells out that is not normative content but only to
>>>avoid the reader digging around to find the definitions.
>>> - Some readers that do not know LISP might find it handy to have it
>>>around.
>>>=20
>>> PEY>I might suggest a separate Informational RFC that provides the
>>>information contained in the appendix for reference when using all of
>>>the LISP documents rather than burying it in a management framework.
>>>But I also recognize that this may not be an expeditious way to
>>>progress things, so do no more than take my thoughts under advisement.
>>>=20
>>> ciao
>>>=20
>>> Luigi
>>>=20
>>>>=20
>>>> 		-Peter
>>>>=20
>>>> -----Original Message-----
>>>> From: Luigi Iannone [mailto:ggx@gigix.net]
>>>> Sent: Monday, February 08, 2016 3:19 AM
>>>> To: Luigi Iannone
>>>> Cc: Peter Yee; draft-ietf-lisp-eid-block-mgmnt.all@tools.ietf.org;
>>>> gen-art@ietf.org; ietf@ietf.org
>>>> Subject: Re: Gen-ART LC review of draft-ietf-lisp-eid-block-mgmnt-06
>>>>=20
>>>>=20
>>>>> On 08 Feb 2016, at 12:17, Luigi Iannone <ggx@gigix.net> wrote:
>>>>>=20
>>>>> Hi Peter,
>>>>>=20
>>>>> Back in April we indeed did not sent you a specific feedback.
>>>>> Reason is that we received several comments/reviews and batched
>>>>>everything in a new I-D, with sending specific feedback to all.
>>>>>=20
>>>>=20
>>>> The correct sentence is: =E2=80=9Cwithout sending specific feedback to all=E2=80=
=9D
>>>>=20
>>>> I should really start to proofread my mails before hitting the send
>>>> button  ;-)
>>>>=20
>>>> ciao
>>>>=20
>>>> L.
>>>>=20
>>>>> Yet, if you are unsatisfied on how we addressed the issues we
>>>>>certainly need to do more work.
>>>>>=20
>>>>> Give me some time to go again thoroughly through your first review
>>>>>and I=E2=80=99ll get back to you with a specific feedback.
>>>>>=20
>>>>> Thanks for your time spent on this document.
>>>>>=20
>>>>> ciao
>>>>>=20
>>>>> L.
>>>>>=20
>>>>>=20
>>>>>=20
>>>>>> On 06 Feb 2016, at 04:39, Peter Yee <peter@akayla.com> wrote:
>>>>>>=20
>>>>>> I am the assigned Gen-ART reviewer for this draft.  The General
>>>>>> Area Review Team (Gen-ART) reviews all IETF documents being
>>>>>> processed by the IESG for the IETF Chair.  Please treat these
>>>>>> comments just like any other last call comment.  For background on
>>>>>> Gen-ART, please see the FAQ at
>>>>>> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>
>>>>>>=20
>>>>>> Document: draft-ietf-lisp-eid-block-mgmnt-06
>>>>>> Reviewer: Peter Yee
>>>>>> Review Date: February 5, 2016
>>>>>> IETF LC End Date: February 5, 2016
>>>>>> IESG Telechat date: February 18, 2016
>>>>>>=20
>>>>>> Summary: This draft has serious issues, described in the review,
>>>>>> and needs to be rethought. [Not ready]
>>>>>>=20
>>>>>> The draft attempts to specify the framework for the management of
>>>>>> experimental LISP EID sub-prefixes, but really could use some
>>>>>> additional work to flesh out the management aspects that are left
>>>>>>unsaid.
>>>>>>=20
>>>>>> This draft fixes only two minor nits I raised in my review of the
>>>>>> -04 version.  Nothing else has been addressed, nor have I received
>>>>>> any feedback on that review.  In light of this, I have little new
>>>>>>to add.
>>>>>> It is possible that the agreement between the IANA and the RIPE NCC
>>>>>> will alleviate the major concern I had with the draft, but not
>>>>>> being privy to that agreement, I can't make that determination.
>>>>>>=20
>>>>>> My original review with the unaddressed comments can be found here:
>>>>>> https://www.ietf.org/mail-archive/web/gen-art/current/msg11620.html
>
>



From nobody Wed Apr  6 15:17:26 2016
Return-Path: <alexandre.petrescu@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 9958412D174 for <ietf@ietfa.amsl.com>; Wed,  6 Apr 2016 15:17:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.352
X-Spam-Level: 
X-Spam-Status: No, score=-5.352 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_SOFTFAIL=0.665] 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 IiPX_J814QSA for <ietf@ietfa.amsl.com>; Wed,  6 Apr 2016 15:17:22 -0700 (PDT)
Received: from oxalide-out.extra.cea.fr (oxalide-out.extra.cea.fr [132.168.224.8]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5C9F412D613 for <ietf@ietf.org>; Wed,  6 Apr 2016 15:17:22 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by oxalide.extra.cea.fr (8.15.2/8.15.2/CEAnet-Internet-out-2.4) with ESMTP id u36MHDXY007131; Thu, 7 Apr 2016 00:17:13 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 5467F204562; Thu,  7 Apr 2016 00:18:22 +0200 (CEST)
Received: from muguet1.intra.cea.fr (muguet1.intra.cea.fr [132.166.192.6]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 4712120455E; Thu,  7 Apr 2016 00:18:22 +0200 (CEST)
Received: from [132.166.84.226] ([132.166.84.226]) by muguet1.intra.cea.fr (8.15.2/8.15.2/CEAnet-Intranet-out-1.4) with ESMTP id u36MHBm1030491; Thu, 7 Apr 2016 00:17:11 +0200
To: IETF Discussion <ietf@ietf.org>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Subject: ITS BoF outcome - comment on charter
Message-ID: <57058AE6.9010001@gmail.com>
Date: Wed, 6 Apr 2016 19:17:10 -0300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.7.0
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="------------090102010202070003010403"
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/DvJBqHwlf8WLYuZTOo7B66TwwvY>
Cc: =?UTF-8?B?5YiY5aSn6bmPKOm5j+aIkCk=?= <max.ldp@alibaba-inc.com>
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, 06 Apr 2016 22:17:24 -0000

This is a multi-part message in MIME format.
--------------090102010202070003010403
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit

Hi IETFers,

We had a great BoF today on Intelligent Transportation Systems (ITS).
The slides are at:
https://datatracker.ietf.org/meeting/95/materials.html/#its

There is a liaison from ISO TC204, slide 13 of "ISO TC204 needs"
https://www.ietf.org/proceedings/95/slides/slides-95-its-7.pdf

Please join the ITS email list at ietf.org/mailman/listinfo/its and
comment on the charter.

Yours,

Alex and Dapeng


--------------090102010202070003010403
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 7bit

<html>
  <head>

    <meta http-equiv="content-type" content="text/html; charset=utf-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <font face="Courier New">Hi IETFers,<br>
      <br>
      We had a great BoF today on Intelligent Transportation Systems
      (ITS).<br>
      The slides are at:<br>
      <a class="moz-txt-link-freetext" href="https://datatracker.ietf.org/meeting/95/materials.html/#its">https://datatracker.ietf.org/meeting/95/materials.html/#its</a><br>
      <br>
      There is a liaison from ISO TC204, slide 13 of "ISO TC204 needs"<br>
      <a class="moz-txt-link-freetext" href="https://www.ietf.org/proceedings/95/slides/slides-95-its-7.pdf">https://www.ietf.org/proceedings/95/slides/slides-95-its-7.pdf</a><br>
      <br>
      Please join the ITS email list at ietf.org/mailman/listinfo/its
      and<br>
      comment on the charter.<br>
      <br>
      Yours,<br>
      <br>
      Alex and Dapeng<br>
      <br>
    </font>
  </body>
</html>

--------------090102010202070003010403--


From nobody Wed Apr  6 15:34:06 2016
Return-Path: <presnick@qti.qualcomm.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 1378112D707 for <ietf@ietfa.amsl.com>; Wed,  6 Apr 2016 15:33:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.03
X-Spam-Level: 
X-Spam-Status: No, score=-7.03 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_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=qti.qualcomm.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 Rz12ziRuVidl for <ietf@ietfa.amsl.com>; Wed,  6 Apr 2016 15:33:55 -0700 (PDT)
Received: from wolverine01.qualcomm.com (wolverine01.qualcomm.com [199.106.114.254]) (using TLSv1.2 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ADA9412D1E0 for <ietf@ietf.org>; Wed,  6 Apr 2016 15:33:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1459982034; x=1491518034; h=from:to:subject:date:message-id:in-reply-to:references: mime-version:content-transfer-encoding; bh=rAKq55Gl2/LWurwSEm8cR95Lex5dx2P4z3DtFis9g8A=; b=rICQckBXUKBlBAazDamfHlkleYtlFefGhQGrYu19OZHob3z4xxPMdO4K AfdpP7yZjFugfcd3hG3YYH5DRjaUbkAL2yIua6C+GjxpqOL/5a2M1ga51 KD9swrvEr7w44Ve/4m3PprNOLfEu1zhR626Djm0tBuH8Mhfi6Qw/iGtUX Q=;
X-IronPort-AV: E=Sophos;i="5.24,448,1455004800";  d="scan'208,217";a="183050756"
Received: from unknown (HELO Ironmsg03-L.qualcomm.com) ([10.53.140.110]) by wolverine01.qualcomm.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 06 Apr 2016 15:33:54 -0700
X-IronPort-AV: E=McAfee;i="5700,7163,8127"; a="1125458175"
Received: from nasanexm01f.na.qualcomm.com ([10.85.0.32]) by Ironmsg03-L.qualcomm.com with ESMTP/TLS/RC4-SHA; 06 Apr 2016 15:33:54 -0700
Received: from [10.64.130.5] (10.80.80.8) by NASANEXM01F.na.qualcomm.com (10.85.0.32) with Microsoft SMTP Server (TLS) id 15.0.1130.7; Wed, 6 Apr 2016 15:33:53 -0700
From: Pete Resnick <presnick@qti.qualcomm.com>
To: <ietf@ietf.org>
Subject: Re: Proposed New Note Well
Date: Wed, 6 Apr 2016 19:33:50 -0300
Message-ID: <E5F9AC1D-4FC2-40A7-90A3-DC3913C10D42@qti.qualcomm.com>
In-Reply-To: <20160321165157.31914.47506.idtracker@ietfa.amsl.com>
References: <20160321165157.31914.47506.idtracker@ietfa.amsl.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="=_MailMate_E4A0A37C-CB67-496A-A480-5BD00560EE54_="
Content-Transfer-Encoding: 8bit
X-Mailer: MailMate (1.9.4r5239)
X-Originating-IP: [10.80.80.8]
X-ClientProxiedBy: NASANEXM01E.na.qualcomm.com (10.85.0.31) To NASANEXM01F.na.qualcomm.com (10.85.0.32)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/uygSbL1o9dVZmdFggDR5HTj3JNI>
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, 06 Apr 2016 22:33:59 -0000

--=_MailMate_E4A0A37C-CB67-496A-A480-5BD00560EE54_=
Content-Type: text/plain; charset="utf-8"; format=flowed; markup=markdown
Content-Transfer-Encoding: 8bit

Two things, neither earth-shattering:

1. Jari did say he thought it was still too long. The second paragraph 
(mentioning the patent policy) seems duplicative with what's in the 
second bullet and the list at the bottom. And of course the top-level 
message should be that first bullet: You have to follow all of the 
rules. Let's just strike the second paragraph.

2. In addition to the pointer to the documents at the bottom (which I 
presume will be links when this thing appears in HTML), it would be 
great to have a link to https://www.ietf.org/ombudsteam placed next to 
the line regarding anti-harassment procedures. That'll let people also 
find the IESG Statement and other info.

pr

On 21 Mar 2016, at 13:51, IESG Secretary wrote:

> Note Well
>
> This is a reminder of IETF policies in effect on various topics such 
> as
> patents or code of conduct. It is only meant to point you in the right
> direction. Exceptions may apply.
>
> The IETF's patent policy and the definition of an IETF "contribution"
> and "participation" are set forth in BCP 79; please read it carefully.
>
> As a reminder:
>
> â€˘ By participating in the IETF, you agree to follow IETF processes 
> and
>   policies.
> â€˘ If you are aware that any IETF contribution is covered by patents 
> or
>   patent applications that are owned or controlled by you or your
>   sponsor, you must disclose that fact, or not participate in the
>   discussion.
> â€˘ As a participant in any IETF activity you acknowledge that 
> written,
>   audio and video records of meetings may be made public.
> â€˘ Personal information that you provide to IETF will be handled in
>   accordance with the IETF Privacy Statement.
>
> Definitive information is in the documents listed below and other IETF
> BCPs. For advice, please talk to WG chairs or ADs:
> â€‹
> BCP 9 (Internet Standards Process)
> â€‹BCP 25 (Working Group processes)
> BCP 25 (Anti-Harassment Procedures)
> BCP 54 (Code of Conduct)
> â€‹BCP 78 (Copyright)
> â€‹BCP 79 (Patents, Participation)
> TBD (Privacy)


-- 
Pete Resnick <http://www.qualcomm.com/~presnick/>
Qualcomm Technologies, Inc. - +1 (858)651-4478
--=_MailMate_E4A0A37C-CB67-496A-A480-5BD00560EE54_=
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

<div class=3D"markdown">
<p dir=3D"auto">Two things, neither earth-shattering:</p>

<ol>
<li value=3D1><p dir=3D"auto">Jari did say he thought it was still too lo=
ng. The second paragraph (mentioning the patent policy) seems duplicative=
 with what's in the second bullet and the list at the bottom. And of cour=
se the top-level message should be that first bullet: You have to follow =
all of the rules. Let's just strike the second paragraph.</p></li>
<li value=3D2><p dir=3D"auto">In addition to the pointer to the documents=
 at the bottom (which I presume will be links when this thing appears in =
HTML), it would be great to have a link to <a href=3D"https://www.ietf.or=
g/ombudsteam">https://www.ietf.org/ombudsteam</a> placed next to the line=
 regarding anti-harassment procedures. That'll let people also find the I=
ESG Statement and other info.</p></li>
</ol>

<p dir=3D"auto">pr</p>

<p dir=3D"auto">On 21 Mar 2016, at 13:51, IESG Secretary wrote:</p>

<blockquote>
<p dir=3D"auto">Note Well</p>

<p dir=3D"auto">This is a reminder of IETF policies in effect on various =
topics such as<br>
patents or code of conduct. It is only meant to point you in the right<br=
>
direction. Exceptions may apply.</p>

<p dir=3D"auto">The IETF's patent policy and the definition of an IETF "c=
ontribution"<br>
and "participation" are set forth in BCP 79; please read it carefully.</p=
>

<p dir=3D"auto">As a reminder:</p>

<p dir=3D"auto">=E2=80=A2 By participating in the IETF, you agree to foll=
ow IETF processes and<br>
  policies.<br>
=E2=80=A2 If you are aware that any IETF contribution is covered by paten=
ts or<br>
  patent applications that are owned or controlled by you or your<br>
  sponsor, you must disclose that fact, or not participate in the<br>
  discussion.<br>
=E2=80=A2 As a participant in any IETF activity you acknowledge that writ=
ten,<br>
  audio and video records of meetings may be made public.<br>
=E2=80=A2 Personal information that you provide to IETF will be handled i=
n<br>
  accordance with the IETF Privacy Statement.</p>

<p dir=3D"auto">Definitive information is in the documents listed below a=
nd other IETF<br>
BCPs. For advice, please talk to WG chairs or ADs:<br>
=E2=80=8B<br>
BCP 9 (Internet Standards Process)<br>
=E2=80=8BBCP 25 (Working Group processes)<br>
BCP 25 (Anti-Harassment Procedures)<br>
BCP 54 (Code of Conduct)<br>
=E2=80=8BBCP 78 (Copyright)<br>
=E2=80=8BBCP 79 (Patents, Participation)<br>
TBD (Privacy)</p>
</blockquote>

<p dir=3D"auto">-- <br>
Pete Resnick <a href=3D"http://www.qualcomm.com/%7Epresnick/">http://www.=
qualcomm.com/~presnick/</a><br>
Qualcomm Technologies, Inc. - +1 (858)651-4478</p>

</div>
--=_MailMate_E4A0A37C-CB67-496A-A480-5BD00560EE54_=--


From nobody Wed Apr  6 15:37:45 2016
Return-Path: <sob@sobco.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 100AC12D15D for <ietf@ietfa.amsl.com>; Wed,  6 Apr 2016 15:37:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.108
X-Spam-Level: 
X-Spam-Status: No, score=-1.108 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RDNS_NONE=0.793, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=no 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 QvcnKYSlK3uN for <ietf@ietfa.amsl.com>; Wed,  6 Apr 2016 15:37:41 -0700 (PDT)
Received: from sobco.sobco.com (unknown [136.248.127.164]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 29B0F12D134 for <ietf@ietf.org>; Wed,  6 Apr 2016 15:37:41 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by sobco.sobco.com (Postfix) with ESMTP id 59F8A1B0923E; Wed,  6 Apr 2016 18:37:40 -0400 (EDT)
X-Virus-Scanned: amavisd-new at sobco.com
Received: from sobco.sobco.com ([127.0.0.1]) by localhost (sobco.sobco.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UJoHdCyB_a_v; Wed,  6 Apr 2016 18:37:39 -0400 (EDT)
Received: from dhcp3.sobco.com (vpn2.sobco.com [136.248.127.173]) by sobco.sobco.com (Postfix) with ESMTPSA id C9B931B09226; Wed,  6 Apr 2016 18:37:38 -0400 (EDT)
Content-Type: multipart/alternative; boundary="Apple-Mail=_E644CF5C-7B90-43AA-820F-2F829D986AE7"
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Subject: Re: Proposed New Note Well
From: Scott Bradner <sob@sobco.com>
In-Reply-To: <E5F9AC1D-4FC2-40A7-90A3-DC3913C10D42@qti.qualcomm.com>
Date: Wed, 6 Apr 2016 18:37:36 -0400
Message-Id: <D9752087-788F-43D5-8ECE-EF1C677D45C9@sobco.com>
References: <20160321165157.31914.47506.idtracker@ietfa.amsl.com> <E5F9AC1D-4FC2-40A7-90A3-DC3913C10D42@qti.qualcomm.com>
To: Pete Resnick <presnick@qti.qualcomm.com>
X-Mailer: Apple Mail (2.3124)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/Yq1W-1BcWOXk9kSgGB4YrKe6Mj8>
Cc: 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, 06 Apr 2016 22:37:43 -0000

--Apple-Mail=_E644CF5C-7B90-43AA-820F-2F829D986AE7
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

imo - the 2nd pp is not duplicative - consider that the whole current =
note we=E2=80=99ll is just covering =E2=80=9Cwhat is a contribution=E2=80=9D=

and the question of what =E2=80=9Cparticipating=E2=80=9D=E2=80=9D is has =
been a contentious issue for a long time

Scott

> On Apr 6, 2016, at 6:33 PM, Pete Resnick <presnick@qti.qualcomm.com> =
wrote:
>=20
> Two things, neither earth-shattering:
>=20
> Jari did say he thought it was still too long. The second paragraph =
(mentioning the patent policy) seems duplicative with what's in the =
second bullet and the list at the bottom. And of course the top-level =
message should be that first bullet: You have to follow all of the =
rules. Let's just strike the second paragraph.
>=20
> In addition to the pointer to the documents at the bottom (which I =
presume will be links when this thing appears in HTML), it would be =
great to have a link to https://www.ietf.org/ombudsteam =
<https://www.ietf.org/ombudsteam> placed next to the line regarding =
anti-harassment procedures. That'll let people also find the IESG =
Statement and other info.
>=20
> pr
>=20
> On 21 Mar 2016, at 13:51, IESG Secretary wrote:
>=20
> Note Well
>=20
> This is a reminder of IETF policies in effect on various topics such =
as
> patents or code of conduct. It is only meant to point you in the right
> direction. Exceptions may apply.
>=20
> The IETF's patent policy and the definition of an IETF "contribution"
> and "participation" are set forth in BCP 79; please read it carefully.
>=20
> As a reminder:
>=20
> =E2=80=A2 By participating in the IETF, you agree to follow IETF =
processes and
> policies.
> =E2=80=A2 If you are aware that any IETF contribution is covered by =
patents or
> patent applications that are owned or controlled by you or your
> sponsor, you must disclose that fact, or not participate in the
> discussion.
> =E2=80=A2 As a participant in any IETF activity you acknowledge that =
written,
> audio and video records of meetings may be made public.
> =E2=80=A2 Personal information that you provide to IETF will be =
handled in
> accordance with the IETF Privacy Statement.
>=20
> Definitive information is in the documents listed below and other IETF
> BCPs. For advice, please talk to WG chairs or ADs:
> =E2=80=8B
> BCP 9 (Internet Standards Process)
> =E2=80=8BBCP 25 (Working Group processes)
> BCP 25 (Anti-Harassment Procedures)
> BCP 54 (Code of Conduct)
> =E2=80=8BBCP 78 (Copyright)
> =E2=80=8BBCP 79 (Patents, Participation)
> TBD (Privacy)
>=20
> --=20
> Pete Resnick http://www.qualcomm.com/~presnick/ =
<http://www.qualcomm.com/%7Epresnick/>
> Qualcomm Technologies, Inc. - +1 (858)651-4478
>=20


--Apple-Mail=_E644CF5C-7B90-43AA-820F-2F829D986AE7
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D"">imo - the 2nd pp is not duplicative - consider that the whole =
current note we=E2=80=99ll is just covering =E2=80=9Cwhat is a =
contribution=E2=80=9D<div class=3D"">and the question of what =
=E2=80=9Cparticipating=E2=80=9D=E2=80=9D is has been a contentious issue =
for a long time</div><div class=3D""><br class=3D""></div><div =
class=3D"">Scott</div><div class=3D""><br class=3D""><div><blockquote =
type=3D"cite" class=3D""><div class=3D"">On Apr 6, 2016, at 6:33 PM, =
Pete Resnick &lt;<a href=3D"mailto:presnick@qti.qualcomm.com" =
class=3D"">presnick@qti.qualcomm.com</a>&gt; wrote:</div><br =
class=3D"Apple-interchange-newline"><div class=3D""><div =
class=3D"markdown"><p dir=3D"auto" class=3D"">Two things, neither =
earth-shattering:</p>

<ol class=3D"">
<li value=3D"1" class=3D""><p dir=3D"auto" class=3D"">Jari did say he =
thought it was still too long. The second paragraph (mentioning the =
patent policy) seems duplicative with what's in the second bullet and =
the list at the bottom. And of course the top-level message should be =
that first bullet: You have to follow all of the rules. Let's just =
strike the second paragraph.</p></li>
<li value=3D"2" class=3D""><p dir=3D"auto" class=3D"">In addition to the =
pointer to the documents at the bottom (which I presume will be links =
when this thing appears in HTML), it would be great to have a link to <a =
href=3D"https://www.ietf.org/ombudsteam" =
class=3D"">https://www.ietf.org/ombudsteam</a> placed next to the line =
regarding anti-harassment procedures. That'll let people also find the =
IESG Statement and other info.</p></li>
</ol><p dir=3D"auto" class=3D"">pr</p><p dir=3D"auto" class=3D"">On 21 =
Mar 2016, at 13:51, IESG Secretary wrote:</p>

<blockquote class=3D""><p dir=3D"auto" class=3D"">Note Well</p><p =
dir=3D"auto" class=3D"">This is a reminder of IETF policies in effect on =
various topics such as<br class=3D"">
patents or code of conduct. It is only meant to point you in the =
right<br class=3D"">
direction. Exceptions may apply.</p><p dir=3D"auto" class=3D"">The =
IETF's patent policy and the definition of an IETF "contribution"<br =
class=3D"">
and "participation" are set forth in BCP 79; please read it =
carefully.</p><p dir=3D"auto" class=3D"">As a reminder:</p><p dir=3D"auto"=
 class=3D"">=E2=80=A2 By participating in the IETF, you agree to follow =
IETF processes and<br class=3D"">
  policies.<br class=3D"">
=E2=80=A2 If you are aware that any IETF contribution is covered by =
patents or<br class=3D"">
  patent applications that are owned or controlled by you or your<br =
class=3D"">
  sponsor, you must disclose that fact, or not participate in the<br =
class=3D"">
  discussion.<br class=3D"">
=E2=80=A2 As a participant in any IETF activity you acknowledge that =
written,<br class=3D"">
  audio and video records of meetings may be made public.<br class=3D"">
=E2=80=A2 Personal information that you provide to IETF will be handled =
in<br class=3D"">
  accordance with the IETF Privacy Statement.</p><p dir=3D"auto" =
class=3D"">Definitive information is in the documents listed below and =
other IETF<br class=3D"">
BCPs. For advice, please talk to WG chairs or ADs:<br class=3D"">
=E2=80=8B<br class=3D"">
BCP 9 (Internet Standards Process)<br class=3D"">
=E2=80=8BBCP 25 (Working Group processes)<br class=3D"">
BCP 25 (Anti-Harassment Procedures)<br class=3D"">
BCP 54 (Code of Conduct)<br class=3D"">
=E2=80=8BBCP 78 (Copyright)<br class=3D"">
=E2=80=8BBCP 79 (Patents, Participation)<br class=3D"">
TBD (Privacy)</p>
</blockquote><p dir=3D"auto" class=3D"">-- <br class=3D"">
Pete Resnick <a href=3D"http://www.qualcomm.com/%7Epresnick/" =
class=3D"">http://www.qualcomm.com/~presnick/</a><br class=3D"">
Qualcomm Technologies, Inc. - +1 (858)651-4478</p>

</div></div></blockquote></div><br class=3D""></div></body></html>=

--Apple-Mail=_E644CF5C-7B90-43AA-820F-2F829D986AE7--


From nobody Wed Apr  6 16:02:33 2016
Return-Path: <tjc@ecs.soton.ac.uk>
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 AF2B812D7C9 for <ietf@ietfa.amsl.com>; Wed,  6 Apr 2016 16:02:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.53
X-Spam-Level: 
X-Spam-Status: No, score=-3.53 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_MED=-2.3, SPF_NEUTRAL=0.779, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ecs.soton.ac.uk
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 yrEqhJhRSwO1 for <ietf@ietfa.amsl.com>; Wed,  6 Apr 2016 16:02:29 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [IPv6:2001:630:d0:f102::25e]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5308112D635 for <ietf@ietf.org>; Wed,  6 Apr 2016 16:02:28 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (localhost [127.0.0.1]) by falcon.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id u36N2Mss021996; Thu, 7 Apr 2016 00:02:22 +0100
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk u36N2Mss021996
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=201304; t=1459983742; bh=Y4yiQfpMpKhJS6GkIG8dUJwF84w=; h=Mime-Version:Subject:From:In-Reply-To:Date:Cc:References:To; b=0KdcO3gIE8dSkfRSFXuiweETOP0TJWfQ8BXlnxCkjZIMLR2coGJeJja2lLzIwucT6 5blI7jexcC2Jdrjw2VqOCFJAHWYlbdyqGALFfJcCYdeFYyTm1v6xRm3Rr3Wsq7k8zN hKbOlSjEJB51BPLA854mFEqcx3YMS34JX+qT7GL0=
Received: from gander.ecs.soton.ac.uk ([2001:630:d0:f102:250:56ff:fea0:401]) by falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [2001:630:d0:f102:250:56ff:fea0:68da]) envelope-from <tjc@ecs.soton.ac.uk> with ESMTP (valid=N/A) id s3602M30539121461A ret-id none; Thu, 07 Apr 2016 00:02:22 +0100
Received: from [IPv6:2001:67c:370:152:706f:f3be:f1f3:4fd0] ([IPv6:2001:67c:370:152:706f:f3be:f1f3:4fd0]) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id u36N2CEi007223 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 7 Apr 2016 00:02:15 +0100
Content-Type: multipart/alternative; boundary="Apple-Mail=_639196CB-FC6B-43F2-8882-ADAE338894AD"
Mime-Version: 1.0 (Mac OS X Mail 9.2 \(3112\))
Subject: Re: Proposed New Note Well
From: Tim Chown <tjc@ecs.soton.ac.uk>
In-Reply-To: <E5F9AC1D-4FC2-40A7-90A3-DC3913C10D42@qti.qualcomm.com>
Date: Thu, 7 Apr 2016 00:02:12 +0100
Message-ID: <EMEW3|3d155810c4ad7ef897f82a141d170921s3602M03tjc|ecs.soton.ac.uk|A46DBCE2-4195-464A-9FF9-03BF6ED7729E@ecs.soton.ac.uk>
References: <20160321165157.31914.47506.idtracker@ietfa.amsl.com> <E5F9AC1D-4FC2-40A7-90A3-DC3913C10D42@qti.qualcomm.com> <A46DBCE2-4195-464A-9FF9-03BF6ED7729E@ecs.soton.ac.uk>
To: Pete Resnick <presnick@qti.qualcomm.com>
X-Mailer: Apple Mail (2.3112)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=s3602M305391214600; tid=s3602M30539121461A; client=relay,forged,no_ptr,ipv6; mail=; rcpt=; nrcpt=2:0; fails=0
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: u36N2Mss021996
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/mOqIZ_nzAGDYvUk06put6O-K2yY>
Cc: 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, 06 Apr 2016 23:02:31 -0000

--Apple-Mail=_639196CB-FC6B-43F2-8882-ADAE338894AD
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

On 6 Apr 2016, at 23:33, Pete Resnick <presnick@qti.qualcomm.com> wrote:
>=20
> Two things, neither earth-shattering:
>=20
> Jari did say he thought it was still too long. The second paragraph =
(mentioning the patent policy) seems duplicative with what's in the =
second bullet and the list at the bottom. And of course the top-level =
message should be that first bullet: You have to follow all of the =
rules. Let's just strike the second paragraph.
>=20
> In addition to the pointer to the documents at the bottom (which I =
presume will be links when this thing appears in HTML), it would be =
great to have a link to https://www.ietf.org/ombudsteam =
<https://www.ietf.org/ombudsteam> placed next to the line regarding =
anti-harassment procedures. That'll let people also find the IESG =
Statement and other info.
>=20
I agree. And it would be good if it could fit legibly on a single slide, =
for use in the WG chair slide decks, even if it=E2=80=99s something that =
in reality gets all the attention of a pre-flight safety video.

As a slight aside, I noticed this week that at least one WG used the =
proposed template rather than the (I think!) current one. While the =
direction of the new text  looks fine, we should probably be careful =
about what we=E2=80=99re using if it=E2=80=99s not yet official.

Tim
> pr
>=20
> On 21 Mar 2016, at 13:51, IESG Secretary wrote:
>=20
> Note Well
>=20
> This is a reminder of IETF policies in effect on various topics such =
as
> patents or code of conduct. It is only meant to point you in the right
> direction. Exceptions may apply.
>=20
> The IETF's patent policy and the definition of an IETF "contribution"
> and "participation" are set forth in BCP 79; please read it carefully.
>=20
> As a reminder:
>=20
> =E2=80=A2 By participating in the IETF, you agree to follow IETF =
processes and
> policies.
> =E2=80=A2 If you are aware that any IETF contribution is covered by =
patents or
> patent applications that are owned or controlled by you or your
> sponsor, you must disclose that fact, or not participate in the
> discussion.
> =E2=80=A2 As a participant in any IETF activity you acknowledge that =
written,
> audio and video records of meetings may be made public.
> =E2=80=A2 Personal information that you provide to IETF will be =
handled in
> accordance with the IETF Privacy Statement.
>=20
> Definitive information is in the documents listed below and other IETF
> BCPs. For advice, please talk to WG chairs or ADs:
> =E2=80=8B
> BCP 9 (Internet Standards Process)
> =E2=80=8BBCP 25 (Working Group processes)
> BCP 25 (Anti-Harassment Procedures)
> BCP 54 (Code of Conduct)
> =E2=80=8BBCP 78 (Copyright)
> =E2=80=8BBCP 79 (Patents, Participation)
> TBD (Privacy)
>=20
> --=20
> Pete Resnick http://www.qualcomm.com/~presnick/ =
<http://www.qualcomm.com/%7Epresnick/>
> Qualcomm Technologies, Inc. - +1 (858)651-4478
>=20


--Apple-Mail=_639196CB-FC6B-43F2-8882-ADAE338894AD
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D"">On 6 Apr 2016, at 23:33, Pete Resnick &lt;<a =
href=3D"mailto:presnick@qti.qualcomm.com" =
class=3D"">presnick@qti.qualcomm.com</a>&gt; wrote:<br =
class=3D""><div><blockquote type=3D"cite" class=3D""><br =
class=3D"Apple-interchange-newline"><div class=3D""><div =
class=3D"markdown"><p dir=3D"auto" class=3D"">Two things, neither =
earth-shattering:</p>

<ol class=3D"">
<li value=3D"1" class=3D""><p dir=3D"auto" class=3D"">Jari did say he =
thought it was still too long. The second paragraph (mentioning the =
patent policy) seems duplicative with what's in the second bullet and =
the list at the bottom. And of course the top-level message should be =
that first bullet: You have to follow all of the rules. Let's just =
strike the second paragraph.</p></li>
<li value=3D"2" class=3D""><p dir=3D"auto" class=3D"">In addition to the =
pointer to the documents at the bottom (which I presume will be links =
when this thing appears in HTML), it would be great to have a link to <a =
href=3D"https://www.ietf.org/ombudsteam" =
class=3D"">https://www.ietf.org/ombudsteam</a> placed next to the line =
regarding anti-harassment procedures. That'll let people also find the =
IESG Statement and other info.</p></li></ol></div></div></blockquote>I =
agree. And it would be good if it could fit legibly on a single slide, =
for use in the WG chair slide decks, even if it=E2=80=99s something that =
in reality gets all the attention of a pre-flight safety =
video.</div><div><br class=3D"">As a slight aside, I noticed this week =
that at least one WG used the proposed template rather than the (I =
think!) current one. While the direction of the new text &nbsp;looks =
fine, we should probably be careful about what we=E2=80=99re using if =
it=E2=80=99s not yet official.<div class=3D""><br class=3D""><div =
class=3D""><div class=3D"">Tim</div></div></div><blockquote type=3D"cite" =
class=3D""><div class=3D""><div class=3D"markdown"><ol class=3D"">
</ol><p dir=3D"auto" class=3D"">pr</p><p dir=3D"auto" class=3D"">On 21 =
Mar 2016, at 13:51, IESG Secretary wrote:</p>

<blockquote class=3D""><p dir=3D"auto" class=3D"">Note Well</p><p =
dir=3D"auto" class=3D"">This is a reminder of IETF policies in effect on =
various topics such as<br class=3D"">
patents or code of conduct. It is only meant to point you in the =
right<br class=3D"">
direction. Exceptions may apply.</p><p dir=3D"auto" class=3D"">The =
IETF's patent policy and the definition of an IETF "contribution"<br =
class=3D"">
and "participation" are set forth in BCP 79; please read it =
carefully.</p><p dir=3D"auto" class=3D"">As a reminder:</p><p dir=3D"auto"=
 class=3D"">=E2=80=A2 By participating in the IETF, you agree to follow =
IETF processes and<br class=3D"">
  policies.<br class=3D"">
=E2=80=A2 If you are aware that any IETF contribution is covered by =
patents or<br class=3D"">
  patent applications that are owned or controlled by you or your<br =
class=3D"">
  sponsor, you must disclose that fact, or not participate in the<br =
class=3D"">
  discussion.<br class=3D"">
=E2=80=A2 As a participant in any IETF activity you acknowledge that =
written,<br class=3D"">
  audio and video records of meetings may be made public.<br class=3D"">
=E2=80=A2 Personal information that you provide to IETF will be handled =
in<br class=3D"">
  accordance with the IETF Privacy Statement.</p><p dir=3D"auto" =
class=3D"">Definitive information is in the documents listed below and =
other IETF<br class=3D"">
BCPs. For advice, please talk to WG chairs or ADs:<br class=3D"">
=E2=80=8B<br class=3D"">
BCP 9 (Internet Standards Process)<br class=3D"">
=E2=80=8BBCP 25 (Working Group processes)<br class=3D"">
BCP 25 (Anti-Harassment Procedures)<br class=3D"">
BCP 54 (Code of Conduct)<br class=3D"">
=E2=80=8BBCP 78 (Copyright)<br class=3D"">
=E2=80=8BBCP 79 (Patents, Participation)<br class=3D"">
TBD (Privacy)</p>
</blockquote><p dir=3D"auto" class=3D"">-- <br class=3D"">
Pete Resnick <a href=3D"http://www.qualcomm.com/%7Epresnick/" =
class=3D"">http://www.qualcomm.com/~presnick/</a><br class=3D"">
Qualcomm Technologies, Inc. - +1 (858)651-4478</p>

</div></div></blockquote></div><br class=3D""></body></html>=

--Apple-Mail=_639196CB-FC6B-43F2-8882-ADAE338894AD--


From nobody Wed Apr  6 16:04:17 2016
Return-Path: <alexandre.petrescu@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 07CD012D65F for <ietf@ietfa.amsl.com>; Wed,  6 Apr 2016 16:04:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.333
X-Spam-Level: 
X-Spam-Status: No, score=-5.333 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, SPF_SOFTFAIL=0.665] 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 PftcBqetO2yx for <ietf@ietfa.amsl.com>; Wed,  6 Apr 2016 16:04:11 -0700 (PDT)
Received: from sainfoin-out.extra.cea.fr (sainfoin-out.extra.cea.fr [132.167.192.145]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5008F12D616 for <ietf@ietf.org>; Wed,  6 Apr 2016 16:04:11 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by sainfoin.extra.cea.fr (8.15.2/8.15.2/CEAnet-Internet-out-2.4) with ESMTP id u36Mi4r2024141 for <ietf@ietf.org>; Thu, 7 Apr 2016 00:44:04 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id CCBBE2045AE for <ietf@ietf.org>; Thu,  7 Apr 2016 00:45:13 +0200 (CEST)
Received: from muguet2.intra.cea.fr (muguet2.intra.cea.fr [132.166.192.7]) by pisaure.intra.cea.fr (Postfix) with ESMTP id C0D3520447D for <ietf@ietf.org>; Thu,  7 Apr 2016 00:45:13 +0200 (CEST)
Received: from [132.166.84.226] ([132.166.84.226]) by muguet2.intra.cea.fr (8.15.2/8.15.2/CEAnet-Intranet-out-1.4) with ESMTP id u36Mi2Xs003822 for <ietf@ietf.org>; Thu, 7 Apr 2016 00:44:03 +0200
Subject: Re: ITS BoF outcome - comment on charter (and raw minutes)
To: ietf@ietf.org
References: <57058AE6.9010001@gmail.com>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <57059131.5000805@gmail.com>
Date: Wed, 6 Apr 2016 19:44:01 -0300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.7.0
MIME-Version: 1.0
In-Reply-To: <57058AE6.9010001@gmail.com>
Content-Type: multipart/mixed; boundary="------------000003020600000700090005"
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/C8funKPxfcwVoF3fFvp3yEUTePI>
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, 06 Apr 2016 23:04:15 -0000

This is a multi-part message in MIME format.
--------------000003020600000700090005
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit

Attached are raw minutes.

Many thanks to minute takers: Charles Perkins, J-C. Zuniga.

The room used an echo-ey boomy public address system so the notes were a 
bit hard to take.  We need better.

Alex

Le 06/04/2016 19:17, Alexandre Petrescu a Ă©crit :
> Hi IETFers,
>
> We had a great BoF today on Intelligent Transportation Systems (ITS).
> The slides are at:
> https://datatracker.ietf.org/meeting/95/materials.html/#its
>
> There is a liaison from ISO TC204, slide 13 of "ISO TC204 needs"
> https://www.ietf.org/proceedings/95/slides/slides-95-its-7.pdf
>
> Please join the ITS email list at ietf.org/mailman/listinfo/its and
> comment on the charter.
>
> Yours,
>
> Alex and Dapeng
>

--------------000003020600000700090005
Content-Type: text/plain;
 name="Minutes.txt"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
 filename="Minutes.txt"

DQpNaW51dGVzIGZvciBbaXRzXQ0KDQqVIEludHJvZHVjdGlvbjoNCg0KDQqWIEFkbWluaXN0
cmF0aXZlIC0gQk9GIENoYWlycyAtIDUgbWluDQoNCg0KliBJVFMgR29hbHMgYW5kIFN1Y2Nl
c3MgQ3JpdGVyaWEgLSBCT0YgQ2hhaXJzIC0gMTAgbWluDQoNCg0KlSBQcm9ibGVtIFNwYWNl
Og0KDQoNCpYgVHV0b3JpYWwgb2YgSVAgaW4gdmVoaWN1bGFyIGNvbW11bmljYXRpb25zIC0g
QWxleCBQZXRyZXNjdSAtIDIwIG1pbg0KUmFuZGVsIEdlbGxhbmQ6IFNpbmNlIHRoZXJlIGFy
ZSBzbyBtYW55IE1BQyAmIFBIWSwgdGhleSB1c2UgdGhlaXIgb3duDQoJbWVzc2FnaW5nIC0t
IHNvIGNvdWxkIHVzZSBJUC4gIEJ1dCB2ZWhpY2FscyBhcmUgdXNpbmcgZGlmZmVyZW50IFBI
WQ0KCSYgTUFDLCBzbyB0aGV5IGNhbid0IGNvbW11bmljYXRlDQpBbGV4OiBCdXQgc29tZSBv
ZiB0aGUgcmFkaW9zIGFyZSBhY3R1YWxseSBjb21wYXRpYmxlDQoNCkJvYiBIaW5kZW46IE9u
ICJUb3BvbG9neSIgc2xpZGUgLS0gdGhpcyBpcyB2ZXJ5IHNpbXBsaWZpZWQuICBUaGVyZSB3
aWxsIGJlDQoJbWFueSBjYXJzLCB3aXRoIHZlcnkgZHluYW1pYyBpbnRlcmNvbm5lY3Rpb24N
CkFsZXg6IFllcy4gIEdpdmVzIG1vcmUgZXhhbXBsZXMgdG8gc3VwcG9ydCBjb250ZW50aW9u
DQoNCkRhcGVuZyBMaXU6IE9uY2UgY29ubmVjdGl2aXR5IGlzIGVzdGFibGlzaGVkLA0KCQkJ
SVAgd2lsbCBlbmFibGUgYmV0dGVyIGNvbW11bmljYXRpb24uDQoNClBhdCBUaGFsZXI6IEV2
ZW4gZm9yIGNvbXBhdGlibGUgUEhZLCBNQUNzIG1heSBiZSBkaWZmZXJlbnQsIHNvIGNhbid0
IGp1c3QgZGF5DQoJInVzZSBJUCINCg0KRXJpayBOb3JkbWFyazogSGF2ZSBwZW9wbGUgY29u
c2lkZXJlZCB3aGF0IHRoZSBJUCBhZGRyZXNzaW5nIHdpbGwgbG9vayBsaWtlPw0KCUluIHRo
ZSBjYXIsIHRoZSBhZGRyZXNzaW5nIGlzIHN0YWJsZSwgYnV0IG5vdCBvdXRzaWRlIHRoZSBj
YXIuICBIb3cNCglkb2VzIG9uZSBjYXIga25vdyB0aGUgYWRkcmVzcyBpbiB0aGUgb3RoZXIg
Y2FyPw0KQWxleDogWWVzLCBwZW9wbGUgYXJlIHdvcmtpbmcgb24gdGhpcy4gIElFVEYgY2Fu
IGhlbHAuDQoNCkNhcmxvczogQXJlIHBlb3BsZSB3b3JraW5nIG9uIHRoZSBhZGRyZXNzaW5n
IHNoZW1lLg0KDQpEaW5vOiBXZSBoYXZlIGFuIElQIG1vYmlsaXR5IHByb2JsZW0NCg0KRGly
ayBLaXJjaGVyOiBCcm9hZGNhc3QuICBTZW1hbnRpYyBsYXllci4NCkFsZXg6IFRoZXJlIG1h
eSBiZSBtdWx0aXBsZSBob3BzIGJld2VlbiBjYXJzLCBhbmQgbXVsdGlwbGUgaG9wcyBpbiBh
IGNhci4NCglNYXkgbmVlZCBJUHY0IGJyb2FkY2FzdCwgb3IgSVB2NiBicm9hZGNhc3QNCg0K
RGlubzogRXZlbiB3aXRob3V0IHRoZSBtb2JpbGl0eSBwcm9ibGVtLCB3ZSBzdGlsbCB3b3Vs
ZCBoYXZlIHBoeXNpY2FsIGxheWVyDQoJaW5jb21wYXRpYmxlIHByb2JsZW1zLiAgQnV0IHRo
YXQgaXMgZXhhY3RseSB3aGF0IElQIHNvbHZlcy4NCg0KliBJVFMgdXNlLWNhc2VzIEMtQUND
IGFuZCBQbGF0b29uaW5nIC0gQWxleCBQZXRyZXNjdSAtIDEwIG1pbg0KZHJhZnQtcGV0cmVz
Y3UtaXRzLWNhY2Mtc2RvLTA0DQoNCjx3aGlsZSBwcmVzZW50aW5nIFBsYXRvb25pbmcgc2Nh
bGFiaWxpdHkgc2xpZGU+DQpMb3UgQmVyZ2VyOiBIYWNrYWJsZS4gIFdoYXQncyB0aGUgc2Vj
dXJpdHkgbW9kZWw/DQpBbGV4OiBEbyBub3QgaGF2ZSBzbGlkZXMgYWJvdXQgdGhpcy4NCkVy
aWMgUmVzY29sbzogV2h5IG1ha2UgYW55IHJlcHJlc2VudGF0aW9uIGFib3V0IGV4Y2VlZGlu
ZyBzcGVlZGxpbWl0Lg0KQWxleDogSXQncyBqdXN0IGFuIGV4YW1wbGUNCkVyaWMgUmVzY29s
bzogV2hhdCBpZiB0aGUgcG9saWNlIGFzayB0aGlzIHF1ZXN0aW9uPw0KPGNvbW1lbnQgZnJv
bSBmbG9vciAtIGFkZCBzcGVlZCBwYXJhbWV0ZXI+DQoNClNhbmRyYTogdGhlcmUgaXMgYSBs
b3Qgb2Ygd29yayBiZWluZyBkb25lIG9uIHNlY3VyaXR5DQoJPSBTYWZldHkgcGFydA0KDQpF
cmljIEJ1cmRpY2s6IFRoZXJlIGFyZSBhIGxvdCBvZiBwcml2YWN5IGlzc3Vlcy4gIFRoZXJl
IGlzIHdvcmsgYWJvdXQgamFtbWluZy4NCglJdCdzIG5vdCBqdXN0IE1vYmlsZSBJUC4NCg0K
RXJpayBOb3JkbWFyazogVGhlcmUgd2FzIGFuIElFVEYgcGxlbmFyeSB0aGF0IGlzIHJlbGV2
YW50IHRvIHNlY3VyaXR5Lg0KCT0gUG9saWNlIGNhbiBwcm9iYWx5IGdvIGdldCB0aGUgZGF0
YQ0KDQpFcmljIFJlc2NvbG86IExvdHMgb2Ygd29yayB0byBiZSBkb25lIC0tIHByZXZlbnQg
cXVlcnlpbmcgaW4gdGhlIGNhci4NCg0KDQqWIElUUyBWMlYgcHJvYmxlbSBzdGF0ZW1lbnQg
LSBEYXBlbmcgTGl1IC0gNSBtaW4NCmRyYWZ0LXBldHJlc2N1LWl0cy1wcm9ibGVtLTAwDQoN
ClJhbmRlbCBHZWxsYW5kOiBIb3cgZG8gdGhleSBrbm93IHdoZW4gdGhleSBuZWVkIHRvIGRp
c2NvdmVyIHRoZSBvdGhlciB2ZWhpY2xlcycNCglhZGRyZXNzPw0KRGlyayBLaXJjaGVyOiBT
dWItUHJvYmxlbSgxKSBuZWVkcyB0byBiZSBjaGFyYWN0ZXJpemVkIGNvcnJlY3RseS4gIFdo
YXQgaXMgYQ0KCXJlYWxpc3RpYyB1c2UgY2FzZTogIEFuc3dlcjogQy1BQ0MNCg0KLi4uOiBk
byB5b3UgaGF2ZSBkYXRhPw0KQWxleDogSG93IG11Y2ggZGF0YSBkbyB5b3Ugd2FudD8NCg0K
UmFuZGVsIEdlbGxlbnM6IFRoaXMgc2hvd3MgaG93IElQIGlzIHVzZWZ1bCwgYnV0IGl0J3Mg
bm90IHdoeSBJUCBpcyBuZWVkZWQ/DQoJU28gaXQgaXMgbmVlZGVkIHRvIGV4aGliaXQgdGhl
IG5lZWQsIG5vdCBqdXN0IHRoZSB1c2UgY2FzZS4NCg0KRXJpayBOb3JkbWFyazogaG93IGlk
ZW50aXRpZXMgKG9yIGV2ZW4gdGVtcG9yYXJ5IGlkZW50aXRpZXMpIGVzdGFibGlzaGVkPw0K
DQpIYW5uZXMgVHNob2ZlbmlnOiBJcyB0aGVyZSBhIG5lZWQgZm9yIGFub3RoZXIgbGF5ZXIg
Zm9yIGlkZW50aXR5Pw0KDQoNCpYgSVRTIFYySSBwcm9ibGVtIHN0YXRlbWVudCAtIEphZWhv
b24gUGF1bCBKZW9uZyAtIDUgbWluDQpkcmFmdC1qZW9uZy1pdHMtdjJpLXByb2JsZW0tc3Rh
dGVtZW50LTAwDQoNCkNoYXJsaWU6IFdoYXQgZG9lcyBpdCBtZWFuIHRvICJkaXJlY3RseSIg
Y29ubmVjdCB0byB0aGUgUlNPJ3MgbmV0d29yaw0KSmFlaG9vbjogRXhjaGFuZ2UgcHJlZml4
ZXMNCg0KV29tYW4gPGRpZCBub3QgdW5kZXJzdGFuZCwgc29ycnk+DQoNCkRpbm86IGEgbG9z
dCBwYWNrZXQgY291bGQgYmUgYSBjYXRhc3Ryb3BoZSwgYW1pZHN0IGEgbG90IG9mIGNvbm5l
Y3Rpb24uDQoJTmVlZCB0byBhdm9pZCBjaGl0LWNoYXQuICBTaG91bGQgYXZvaWQgbXVsdGlw
bGUgc29sdXRpb25zLg0KCUlmIHNlY3VyaXR5IHJlcXVpcmVzIERpZmZpZS1IZWxsbWFuLCBt
YXkgbm90IGdldCB0byBmaW5hbGx5IHNheSAiQlJBS0UiDQpEaW5vOiBNYXkgbm90IGJlIGFi
bGUgdG8gZ28gZ2V0IGEgY2VydGlmaWNhdGUuDQoNCjwuLi4uPz46IE1heSBub3QgaGF2ZSB0
aW1lIHRvIA0KDQpEaXJrIEtpcmNoZXI6IFF1ZXN0aW9uIGFib3V0IHVzZSBjYXNlLi4uDQoN
CkFsZXg6IFNvbWUgb3BlcmF0b3JzIGFscmVhZHkgcHJvdmlkZSBjb25uZWN0aW9uIGJldHdl
ZW4gUlNVcywgYW5kIHRodXMNCgljYW4gcHJvdmlkZSBoYW5kb3ZlcnMNCg0KlSBEaXNjdXNz
aW9uIC0gMTAgbWluDQoNCkFhcm9uIEZhbGs6IEdvb2QgdG8gaGF2ZSB0aGUgZGlzY3Vzc2lv
bi4gIFVzZWZ1bCBjb25mdXNpb24gWz8/fQ0KRGlyayBLaXJjaGVyOiBVc2UgY2FzZXMgbmVl
ZCBkaXNjdXNzaW9uLCBhcyB3ZWxsIGFzIG5ldHdvcmsgZHJpdmVycy4NCkNhcmxvczogQXJl
IHlvdSB0YWxraW5nIGFib3V0IHJlcXVpcmVtZW50cz8NCkRpcms6IE5ldHdvcmsgcmVxdWly
ZW1lbnRzLi4uDQpFcmlrIE5vcmRtYXJrOiBEb24ndCByZWFsbHkgZ3Jhc3AgZXhhY3RseSB3
aHkgSVAgaXMgbmVlZGVkIGZvciBzaW5nbGUgaG9wLg0KCVdpbGwgdGhpcyB1c2UgdGhlIHNh
bWUgSW50ZXJuZXQ/ICBXaGF0IGFib3V0IHRoZSB0aW1pbmcgcmVxdWlyZW1lbnRzPw0KU3Rh
biBSYXRsaWZmOiBWMlYgY291bGQgYmUgbW9iaWxlIGFkIGhvYyBuZXR3b3JrPw0KUnVzczog
Tm90IGlmIGl0J3MganVzdCBvbmUgaG9wLg0KPC4uLj4gOiBXYW50IHRvIGtub3cgd2hhdCBj
YXJzIGFyZSBjbG9zaW5nIGluLiAgQ291bGQgd2FudCB0byBzZW5kIG1lc3NhZ2UNCglqdXN0
IGJhY2t3YXJkcy4NCkRpbm86IFdoYXQgaWYgeW91ICpkb24ndCogaGF2ZSBJUD8gIEEgbG90
IG9mIHZlaGljbGVzIGFscmVhZHkgaGF2ZSBJUCwgc28gaXQNCglpcyBhbHJlYWR5IHRoZXJl
LiAgSVAgY291bGQgc2ltcGxpZnkgdGhlIGF1dG9tb2JpbGUgYW5kIHRoZQ0KCWNvbW11bmlj
YXRpb25zLiAgV2Ugd2lsbCB3YW50IHRvIHdyaXRlIGFwcGxpY2F0aW9ucy4gIFdpbGwgbmVl
ZCB0byBoYXZlDQoJY29tcGF0aWJsZSBmb3JtYXQuICBXZSB3aWxsIHdhbnQgb3BlbiBzdGFu
ZGFyZHMuDQpTcGVuY2VyIERhd2tpbnM6IFdhcyB3YWl0aW5nIGZvciBhIHRyYW5zcG9ydCBx
dWVzdGlvbi4gIEFwcGxpY2F0aW9ucyBtaWdodCBiZQ0KCWNsb3NlIHRvIGVhY2ggb3RoZXI/
ICBBYm91dCB1cGRhdGluZyB0aGUgY2FyLg0KSGFubmVzOiBBcHBsaWNhdGlvbnMgbWlnaHQg
YmUgcnVubmluZyBvbiBtYW55IGRpZmZlcmVudCBjb21wdXRlcnMgYW5kIG1lZGlhLA0KCWJ1
dCBzdGlsbCBuZWVkIHRvIGNvbW11bmljYXRlLg0KUGF0IFRoYWxlcjogVXBkYXRpbmcgdGhl
IGNhciBpcyBhIGRpZmZlcmVudCBzb3J0IG9mIHRoaW5nIHRoYW4gVjJJLiAgV2Ugd2lsbA0K
CWhhdmUgdXBkYXRlcyBhdCB0aGUgc2VydmljZSBzdGF0aW9uLCBzbyB5b3UncmUgbm90IG1v
dmluZy4NCglUaHJlZSBjb25jZXJuczogc2VjdXJpdHkgcHJvYmxlbS4gVGltZSBjb25zdHJh
aW50cy4NClNwZW5jZXI6IE5lZWQgdG8gdW5kZXJzdGFuZCB3aGF0IHRoZSB2b2x1bWUgb2Yg
ZGF0YSB3b3VsZCBiZS4NCkRpcms6IElzIGl0LCBvciBpcyBpdCBub3QsIFRDUD8gIFRoZXJl
IGFyZSBhIGNvdXBsZSBvZiBwcm90b2NvbHMgaW4gdXNlIHRvZGF5Lg0KRXJpYyBCdXJkaWNr
OiBTaG91bGQgYXNzdW1lIHRoYXQgYWxsIHByb3RvY29scyBhcmUgYnJva2VuLg0KCVRoZSBj
b250cm9sIG1lY2hhbmlzbXMgY291bGQgY29sbGFwc2Ugd2l0aCB0aGUgbnVtYmVyIG9mIGNh
cnMuDQoNCpYgV2hhdCBkb2N1bWVudHMgYXJlIG5lZWRlZCB0byBhZHZhbmNlIHRoaXMgd29y
az8NCmh0dHA6Ly9pdHUuaW50L2dvL0lUU2NvbW1zIGlzIGNvbXBsZXRlIGxpc3Qgb2YgSVRV
IHdvcmsgaXRlbXMNCg0KRGlubzogV2h5IGluY2x1ZGUgdHJhaW5zIGJ1dCBub3QgcGxhbmVz
Pw0KQWxleDogTy5LLg0KRXJpayBCdXJkaWNrOiBXaGF0IGFib3V0IHdoZW4gZ2V0IG9udG8g
dGhlIG9jZWFuPw0KRGlyazogU29tZSBvZiB0aGUgdXNlIGNhc2VzIGFyZSB2ZXJ5IGRpc3Np
bWlsYXIuICBOZWVkIHRvIHBpY2sgb25lIHByb2JsZW0uDQpBYXJvbiBmcm9tIEphYmJlcjog
Q2FuIGFzc3VtZSB1c2Ugb2YgY2VydGlmaWNhdGVzLg0KRGlubzogTmVlZCB0byBsb29rIGF0
IHRoZSByZXF1aXJlbWVudHMgYW5kIHNlZSBpZiB0aGVyZSBhcmUgc29sdXRpb25zLA0KCWV2
ZW4gdGhvdWdoIHRoZXJlIGFyZSBhIGxvdCBvZiB3b3JrIGl0ZW1zLg0KRXJpayBOb3JkbWFy
azogQ2FuIHdlIGZpZ3VyZSBvdXQgd2hhdCBpcyBuZWVkZWQgZm9yIHRoZSBpbW1lZGlhdGUg
dGVybT8NClJhbmRhbGwgR2VsbGVuczogV2hhdCBhYm91dCBjb29yZGluYXRpb24gd2l0aCBv
dGhlciBTRE9zPyAgRm9yIGluc3RhbmNlDQoJcmVnYXJkaW5nIElQdjYtb3Zlci1mb28uDQpB
bGV4OiBXaXRoIGEgd29ya2luZyBncm91cCB3ZSBjYW4gaGF2ZSBhIGNoYW5uZWwgYnkgd2hp
Y2ggdG8gZG8gdGhlIGNvb3JkaW5hdGlvbg0KUmFuZGFsbDogV2UgaGF2ZSB0aGF0IHdpdGgg
SVNPLCAzR1BQLCBldGMuDQoNCkNsb3NpbmcgcmVtYXJrczoNCldlIHdpbGwgcHVibGlzaCB0
aGUgY2hhcnRlciBvbiB0aGUgd29ya2luZyBncm91cC4gIEluIGFib3V0IGEgbW9udGggd2UN
CndpbGwgc2VlIGlmIHdlIGhhdmUgYSByaWdvcm91cyBjaGFydGVyLg0K
--------------000003020600000700090005--


From nobody Wed Apr  6 16:35:15 2016
Return-Path: <adrian@olddog.co.uk>
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 A685212D0C0 for <ietf@ietfa.amsl.com>; Wed,  6 Apr 2016 16:35:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.721
X-Spam-Level: 
X-Spam-Status: No, score=-0.721 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01] 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 84sdVMrwdSfb for <ietf@ietfa.amsl.com>; Wed,  6 Apr 2016 16:35:12 -0700 (PDT)
Received: from asmtp1.iomartmail.com (asmtp1.iomartmail.com [62.128.201.248]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BC64B12D109 for <ietf@ietf.org>; Wed,  6 Apr 2016 16:35:10 -0700 (PDT)
Received: from asmtp1.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp1.iomartmail.com (8.13.8/8.13.8) with ESMTP id u36NZ61i006763 for <ietf@ietf.org>; Thu, 7 Apr 2016 00:35:06 +0100
Received: from 950129200 (dhcp-b176.meeting.ietf.org [31.133.177.118]) (authenticated bits=0) by asmtp1.iomartmail.com (8.13.8/8.13.8) with ESMTP id u36NYvg4006598 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Thu, 7 Apr 2016 00:35:02 +0100
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: <ietf@ietf.org>
Subject: "We did not know" is not a good excuse
Date: Thu, 7 Apr 2016 00:34:53 +0100
Message-ID: <09ff01d1905c$f15d4e70$d417eb50$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AdGQXOo2K6ee2QfjSBaO8Tfj5mxHYw==
Content-Language: en-gb
X-TM-AS-MML: disable
X-TM-AS-Product-Ver: IMSS-7.1.0.1679-8.0.0.1202-22244.003
X-TM-AS-Result: No--4.018-10.0-31-10
X-imss-scan-details: No--4.018-10.0-31-10
X-TMASE-MatchedRID: xqMNgaEvljj3Zb7NlHCdGBD3+0w1DhqKVJDKIGEbk29o5YsPsbyLXVLz hkLBD2O7P3hFqVh2HCdoGBkHVItBPMGh4ydZRcg32OSj4qJA9QYd03X7Es+c45soi2XrUn/JyeM tMD9QOgCrrVqVQLpWR+TCMddcL/gjxlblqLlYqXKni4g44ComJNEni61pX4HB4R0fFxcdTJdNip w1PdbX54aIedR3xqzH1hg4ioGwsJx023OQ/voYij9xSzhrFQzGQQkoO9T7ETw2Fo4EfHNqXY5MJ KdFN6D6I9UhQYuUjidG3TVmsFmvfmY7eqLvyw0k
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/L8Qc6ldDisE224vOeLUWglz5890>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: adrian@olddog.co.uk
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, 06 Apr 2016 23:35:14 -0000

One might assume that a step in the selection of a location is to look at some
advice for travellers.
One such source of information is the US State Department. (Not the source of
all wisdom, but a source of some information.)

https://travel.state.gov/content/passports/en/country/singapore.html has a
sizeable section on LGBT rights and associate issues.

Yes, this is hard to get right and people make mistakes.
Yes, move on.

How do we move on so:
- this problem stops being a problem for IETF 100
- this problem does not recur

Adrian


From nobody Wed Apr  6 19:19:15 2016
Return-Path: <dhc@dcrocker.net>
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 A119612D61F for <ietf@ietfa.amsl.com>; Wed,  6 Apr 2016 19:19:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] 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 lWfe5wAkYVH8 for <ietf@ietfa.amsl.com>; Wed,  6 Apr 2016 19:19:13 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E4F3912D13A for <ietf@ietf.org>; Wed,  6 Apr 2016 19:19:12 -0700 (PDT)
Received: from [192.168.11.242] (104-60-96-29.lightspeed.sntcca.sbcglobal.net [104.60.96.29]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id u372JB1F023471 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Wed, 6 Apr 2016 19:19:11 -0700
Subject: Re: "We did not know" is not a good excuse
To: adrian@olddog.co.uk, ietf@ietf.org
References: <09ff01d1905c$f15d4e70$d417eb50$@olddog.co.uk>
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
Message-ID: <5705C39E.30807@dcrocker.net>
Date: Wed, 6 Apr 2016 19:19:10 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2
MIME-Version: 1.0
In-Reply-To: <09ff01d1905c$f15d4e70$d417eb50$@olddog.co.uk>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Wed, 06 Apr 2016 19:19:12 -0700 (PDT)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/0vImjZeql153C0T5u1EgU53lLv0>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: dcrocker@bbiw.net
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, 07 Apr 2016 02:19:14 -0000

On 4/6/2016 4:34 PM, Adrian Farrel wrote:
> How do we move on so:
...
> - this problem does not recur


What you probably do not mean is 'we do not go to Singapore again.

What you probably /do/ mean is that further venue selections avoid 
places that effectively serve to exclude participation by various 
constituencies.  Or at least, that is what I hope you mean, because it 
has broader utility.

So I'll repeat what I said at the virtual microphone:

    If the community wishes meeting venue selection to refrain from 
choosing specific places, the community needs to develop that list.

Anything less specific leaves too much to interpretation, which 
guarantees that similar errors will recur.

d/

-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net


From nobody Wed Apr  6 19:37:48 2016
Return-Path: <melinda.shore@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 B416E12D13A for <ietf@ietfa.amsl.com>; Wed,  6 Apr 2016 19:37:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 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, RCVD_IN_DNSWL_LOW=-0.7, 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 tnhTrxFOd25n for <ietf@ietfa.amsl.com>; Wed,  6 Apr 2016 19:37:45 -0700 (PDT)
Received: from mail-pf0-x244.google.com (mail-pf0-x244.google.com [IPv6:2607:f8b0:400e:c00::244]) (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 5DE1B12D0A3 for <ietf@ietf.org>; Wed,  6 Apr 2016 19:37:45 -0700 (PDT)
Received: by mail-pf0-x244.google.com with SMTP id r187so5883992pfr.2 for <ietf@ietf.org>; Wed, 06 Apr 2016 19:37:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding; bh=qWrCZM6xj9Zv/c1H6Z428KNUCt6tTO5JDAOuXNNjB+A=; b=NmtezBjEbeW7GORYj8JYVSrMhfJ42KDpq3QgQ6nS8lRs9+U1THTTzSPzcvbEtI8wbK /GKxS0FOj6cZmWmUQ7IzNSWGKxAK9bcb7R4dASMQ92u4wC6bqbrT15iPAvTkGDawHdbt pN8JtlP7yaCNwDMIAEe2DEGRch8vYna06NOVqureW3/5PUNtBzNf9kueoUcT6ShkUJW+ Zi4F9AIYL15ih7XAimHtn97rutnumqrPKAwOWgblkufwUIlv+bPJstkGxBD9hqJrGvXc coJepCQIH/RQgpKMN7b+WwSacac5MkCAB9jMNwI13Q1XyBTnHXD6o8vnnq8czzode15r /a2w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=qWrCZM6xj9Zv/c1H6Z428KNUCt6tTO5JDAOuXNNjB+A=; b=amU7YicpgD1WBMlIjbU9cZI87zyNiaJN9jGxgUQI/oZenxD1+LoEJz3DDsEaXWx/P6 3VNVsyvF6gFLEHIsglBwjqTsRVIrqgUAtElT5hib5Hk//P1MfX0YvsLxN2tKslCHdwmu e9OWUxVdljn11Jnan5sm2glDz2fBMx6iXlfdImKWlEmcMPvKTBy/I4hdvSK4OijVAK2S gD0sfoCDxsR3o8dNHk3X5jDnrITTY/yW2jD4btVY+Z12CWjhGQ6R88S2CAKiVUpnfXfC 6Iz35WzMerHH9OD0AgiM0zJS/QZp2ot5M5NJ4kbcT7BnaxqtBMahbHJj3NvwM7aeTgjW u5Yg==
X-Gm-Message-State: AD7BkJJ7QjyibfTlUiGDDGzsgp0PCc6tzuPw0+zoPuRJTYQqUiXFMznFodwfnp+LXba+4g==
X-Received: by 10.98.12.83 with SMTP id u80mr1042450pfi.116.1459996664971; Wed, 06 Apr 2016 19:37:44 -0700 (PDT)
Received: from Melindas-MacBook-Pro.local (74-124-96-91-radius.dynamic.acsalaska.net. [74.124.96.91]) by smtp.googlemail.com with ESMTPSA id g70sm7789519pfj.13.2016.04.06.19.37.43 for <ietf@ietf.org> (version=TLSv1/SSLv3 cipher=OTHER); Wed, 06 Apr 2016 19:37:44 -0700 (PDT)
Subject: Re: "We did not know" is not a good excuse
To: ietf@ietf.org
References: <09ff01d1905c$f15d4e70$d417eb50$@olddog.co.uk> <5705C39E.30807@dcrocker.net>
From: Melinda Shore <melinda.shore@gmail.com>
Message-ID: <5705C837.5060000@gmail.com>
Date: Wed, 6 Apr 2016 18:38:47 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:38.0) Gecko/20100101 Thunderbird/38.6.0
MIME-Version: 1.0
In-Reply-To: <5705C39E.30807@dcrocker.net>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/pth7HksQ43i2n1GfxdfdJ_IJ_qg>
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, 07 Apr 2016 02:37:46 -0000

On 4/6/16 6:19 PM, Dave Crocker wrote:
> Anything less specific leaves too much to interpretation, which
> guarantees that similar errors will recur.

The situation in Singapore goes well beyond being vaguely
homophobic, to actively criminalizing the families of some
IETF participants.  This is not simply a matter of same-sex
marriage not being legal there, or of the country lacking
anti-discrimination laws.

I am not surprised that any given person might not be
familiar with the situation in Singapore and/or did not
think to check out the human rights situation, but I am
quite surprised that that was the case with a fair-sized
blob of people.  I do think that having broader diversity
among various bodies would make a terrific difference but
from my own experience I tend to think the economics of the
situation make that rather more difficult than loading up
the I* committees with people who share a number of demographic
traits.

Melinda


From nobody Wed Apr  6 20:12:10 2016
Return-Path: <harish.pillay@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 7C1A712D0BF for <ietf@ietfa.amsl.com>; Wed,  6 Apr 2016 20:12:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 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, RCVD_IN_DNSWL_LOW=-0.7, 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 TBHh1RMgikYm for <ietf@ietfa.amsl.com>; Wed,  6 Apr 2016 20:12:07 -0700 (PDT)
Received: from mail-io0-x234.google.com (mail-io0-x234.google.com [IPv6:2607:f8b0:4001:c06::234]) (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 218D212D0B3 for <ietf@ietf.org>; Wed,  6 Apr 2016 20:12:07 -0700 (PDT)
Received: by mail-io0-x234.google.com with SMTP id g185so79311274ioa.2 for <ietf@ietf.org>; Wed, 06 Apr 2016 20:12:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to;  bh=Ml/4gvo90qtde5sHPEN/qZm8RaAT4mfY+5e+vflT/4s=; b=MtAe3lE1dQIpozcG7yhmbxDiQadwVGUr3yNhw7RypkqKb1UOnlaDOpEOUCFF1lE9T9 aw82y+9qks8sB1cpX+zKec6qpeEreNxDtoYUOIwkt7m0nD7DVBFiVLR6zKuVyRLLfy+T 4ln6rWDjm3D5/rMFvIcyUzNiczcyo7wum07JU64JXUgzoDFMA8m2cnRXRzwo/NV8JCMU Hf6RVf/BS3dHuY+sj7wGh4i2WepZHP+4eL2pSS45tBS0OwBGDgq3JnK/9f+eKmO6YaW6 LY1yOhc9HDdtj2VuslF7E2h+qRM7GqKOCjp3h0tuSISm/ul8VouqiewzsovN8iP6diCh x7Yg==
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:date :message-id:subject:from:to; bh=Ml/4gvo90qtde5sHPEN/qZm8RaAT4mfY+5e+vflT/4s=; b=ZDV7uOLrfpiwBja4TA5EvC2lvwPvERfYSdVqesT1z6KxcWiqAmkTVziOpoMqw9UTET 9dfJyRoouA+cGKqDP91T8waSeUoGTTWX7WFnqFJZ7qWTdfgpFpra5yppH3U7AuwWmwOO D72RPFVW5TzygoxGzowrVKCBrlso+4WInGrZrYfMxplcBky4OkkmJjZ99cZXPQaiE5g9 niRlJaVsfQ0qrd9VPK0YpjS4eU31gfB1wJoBBGEoJp/pUQKB9kd9rsf5xv8aNxvNBSqr fxg9EmwisiUP3adGc7eB7cIOqYi8fwWDksgd+X6K+XuhBMcPqefEnZkxdaIQl9gtLDSI 8KFg==
X-Gm-Message-State: AD7BkJLuR0YVXltHGDbrjgbq//iyFHu86JdiBQMwukDrVtcYncEbAYrizGtyxdJWVc7NqwSV7DDywSJXrNJcog==
MIME-Version: 1.0
X-Received: by 10.107.161.140 with SMTP id k134mr1240400ioe.190.1459998726544;  Wed, 06 Apr 2016 20:12:06 -0700 (PDT)
Received: by 10.107.129.214 with HTTP; Wed, 6 Apr 2016 20:12:06 -0700 (PDT)
In-Reply-To: <5705C837.5060000@gmail.com>
References: <09ff01d1905c$f15d4e70$d417eb50$@olddog.co.uk> <5705C39E.30807@dcrocker.net> <5705C837.5060000@gmail.com>
Date: Thu, 7 Apr 2016 11:12:06 +0800
Message-ID: <CAHkmkwuOxOnmJa7KOPdW0Fpqdoq2c7oKWmt9B+zvSy6WcCY5QA@mail.gmail.com>
Subject: Re: "We did not know" is not a good excuse
From: Harish Pillay <harish.pillay@gmail.com>
To: ietf@ietf.org
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/P7_9nI6gSuQdWXtCTjHWbfRRLEQ>
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, 07 Apr 2016 03:12:09 -0000

On Thu, Apr 7, 2016 at 10:38 AM, Melinda Shore <melinda.shore@gmail.com> wrote:
> On 4/6/16 6:19 PM, Dave Crocker wrote:
>>
>> Anything less specific leaves too much to interpretation, which
>> guarantees that similar errors will recur.
>
>
> The situation in Singapore goes well beyond being vaguely
> homophobic, to actively criminalizing the families of some
> IETF participants.  This is not simply a matter of same-sex
> marriage not being legal there, or of the country lacking
> anti-discrimination laws.

I would like to ask for validation and citation of what you are
saying above. I live in Singapore and yes, we do have the archaic
rules on our books (Section 377A of the Penal Code -
https://en.wikipedia.org/wiki/Section_377A_of_the_Penal_Code_%28Singapore%29)
This is a rule we inherited from our British colonial days.

I don't agree with that section, but it is there.

There are ongoing debates on withdrawing Section 377A and it
will happen eventually. It is a matter of time.

If there is any "active criminalizing" then how would this annual
event called pinkdot.sg (http://pinkdot.sg/) happen? The next
pinkdot.sg is on 4th June 2016. But, as it has been
in Singapore so far, open and honest dialogue is used to get to
a favourable resolution. It is still work in progress though.

So, let's keep discussions based on facts please.

Harish


From nobody Wed Apr  6 20:27:30 2016
Return-Path: <presnick@qti.qualcomm.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 76FCD12D0DE for <ietf@ietfa.amsl.com>; Wed,  6 Apr 2016 20:27:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.01
X-Spam-Level: 
X-Spam-Status: No, score=-7.01 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_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=qti.qualcomm.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 9-Z9ibSCE1wd for <ietf@ietfa.amsl.com>; Wed,  6 Apr 2016 20:27:25 -0700 (PDT)
Received: from wolverine02.qualcomm.com (wolverine02.qualcomm.com [199.106.114.251]) (using TLSv1.2 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4578012D0B3 for <ietf@ietf.org>; Wed,  6 Apr 2016 20:27:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1459999645; x=1491535645; h=from:to:cc:subject:date:message-id:in-reply-to: references:mime-version:content-transfer-encoding; bh=CgKNMQT85/kxxk5ZH6YtFxZY8AfN6hClID9nuiPtYaA=; b=VzkdqepsugNruBbcJS/c2u184FtYXgHrkdZqpLhoY/zO9jVtO20IS4v8 d87CwVHR4rdKtjVp8VlJaP6bnA9Yl/QqVZPiuiWKrlv+9w8iyt+fdZNLC sg5uA+x7CS+ZIZUD4KV5VYjAsyBm645fY5wu/sQw/2J7EI0zRrbicri1o w=;
X-IronPort-AV: E=Sophos;i="5.24,448,1455004800";  d="scan'208,217";a="277903469"
Received: from ironmsg04-r-new.qualcomm.com (HELO Ironmsg04-R.qualcomm.com) ([10.53.140.108]) by wolverine02.qualcomm.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 06 Apr 2016 20:27:24 -0700
X-IronPort-AV: E=McAfee;i="5700,7163,8127"; a="1170796855"
Received: from nasanexm01f.na.qualcomm.com ([10.85.0.32]) by Ironmsg04-R.qualcomm.com with ESMTP/TLS/RC4-SHA; 06 Apr 2016 20:27:24 -0700
Received: from [10.64.173.153] (10.80.80.8) by NASANEXM01F.na.qualcomm.com (10.85.0.32) with Microsoft SMTP Server (TLS) id 15.0.1130.7; Wed, 6 Apr 2016 20:27:23 -0700
From: Pete Resnick <presnick@qti.qualcomm.com>
To: Scott Bradner <sob@sobco.com>
Subject: Re: Proposed New Note Well
Date: Thu, 7 Apr 2016 00:27:20 -0300
Message-ID: <A3FBD041-3BC9-442C-B581-F874B4359FE1@qti.qualcomm.com>
In-Reply-To: <D9752087-788F-43D5-8ECE-EF1C677D45C9@sobco.com>
References: <20160321165157.31914.47506.idtracker@ietfa.amsl.com> <E5F9AC1D-4FC2-40A7-90A3-DC3913C10D42@qti.qualcomm.com> <D9752087-788F-43D5-8ECE-EF1C677D45C9@sobco.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="=_MailMate_0A13FA2C-4533-41CA-AC08-B156249E08CD_="
Content-Transfer-Encoding: 8bit
X-Mailer: MailMate (1.9.4r5239)
X-Originating-IP: [10.80.80.8]
X-ClientProxiedBy: NASANEXM01F.na.qualcomm.com (10.85.0.32) To NASANEXM01F.na.qualcomm.com (10.85.0.32)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/V6Muzh0H7vEr8CSiRZPwz-zoa5I>
Cc: 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, 07 Apr 2016 03:27:29 -0000

--=_MailMate_0A13FA2C-4533-41CA-AC08-B156249E08CD_=
Content-Type: text/plain; charset="utf-8"; format=flowed; markup=markdown
Content-Transfer-Encoding: 8bit

How about if we changed the description of BCP 79:

BCP 79 (Patent Policy, definitions of "Participation" and 
"Contribution")

?

pr

On 6 Apr 2016, at 19:37, Scott Bradner wrote:

> imo - the 2nd pp is not duplicative - consider that the whole current 
> note weâ€™ll is just covering â€śwhat is a contributionâ€ť
> and the question of what â€śparticipatingâ€ťâ€ť is has been a 
> contentious issue for a long time
>
> Scott
>
>> On Apr 6, 2016, at 6:33 PM, Pete Resnick <presnick@qti.qualcomm.com> 
>> wrote:
>>
>> Two things, neither earth-shattering:
>>
>> Jari did say he thought it was still too long. The second paragraph 
>> (mentioning the patent policy) seems duplicative with what's in the 
>> second bullet and the list at the bottom. And of course the top-level 
>> message should be that first bullet: You have to follow all of the 
>> rules. Let's just strike the second paragraph.
>>
>> In addition to the pointer to the documents at the bottom (which I 
>> presume will be links when this thing appears in HTML), it would be 
>> great to have a link to https://www.ietf.org/ombudsteam 
>> <https://www.ietf.org/ombudsteam> placed next to the line regarding 
>> anti-harassment procedures. That'll let people also find the IESG 
>> Statement and other info.
>>
>> pr
>>
>> On 21 Mar 2016, at 13:51, IESG Secretary wrote:
>>
>> Note Well
>>
>> This is a reminder of IETF policies in effect on various topics such 
>> as
>> patents or code of conduct. It is only meant to point you in the 
>> right
>> direction. Exceptions may apply.
>>
>> The IETF's patent policy and the definition of an IETF "contribution"
>> and "participation" are set forth in BCP 79; please read it 
>> carefully.
>>
>> As a reminder:
>>
>> â€˘ By participating in the IETF, you agree to follow IETF processes 
>> and
>> policies.
>> â€˘ If you are aware that any IETF contribution is covered by patents 
>> or
>> patent applications that are owned or controlled by you or your
>> sponsor, you must disclose that fact, or not participate in the
>> discussion.
>> â€˘ As a participant in any IETF activity you acknowledge that 
>> written,
>> audio and video records of meetings may be made public.
>> â€˘ Personal information that you provide to IETF will be handled in
>> accordance with the IETF Privacy Statement.
>>
>> Definitive information is in the documents listed below and other 
>> IETF
>> BCPs. For advice, please talk to WG chairs or ADs:
>> â€‹
>> BCP 9 (Internet Standards Process)
>> â€‹BCP 25 (Working Group processes)
>> BCP 25 (Anti-Harassment Procedures)
>> BCP 54 (Code of Conduct)
>> â€‹BCP 78 (Copyright)
>> â€‹BCP 79 (Patents, Participation)
>> TBD (Privacy)


-- 
Pete Resnick <http://www.qualcomm.com/~presnick/>
Qualcomm Technologies, Inc. - +1 (858)651-4478
--=_MailMate_0A13FA2C-4533-41CA-AC08-B156249E08CD_=
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

<div class=3D"markdown">
<p dir=3D"auto">How about if we changed the description of BCP 79:</p>

<p dir=3D"auto">BCP 79 (Patent Policy, definitions of "Participation" and=
 "Contribution")</p>

<p dir=3D"auto">?</p>

<p dir=3D"auto">pr</p>

<p dir=3D"auto">On 6 Apr 2016, at 19:37, Scott Bradner wrote:</p>

<blockquote>
<p dir=3D"auto">imo - the 2nd pp is not duplicative - consider that the w=
hole current note we=E2=80=99ll is just covering =E2=80=9Cwhat is a contr=
ibution=E2=80=9D<br>
and the question of what =E2=80=9Cparticipating=E2=80=9D=E2=80=9D is has =
been a contentious issue for a long time</p>

<p dir=3D"auto">Scott</p>

<blockquote>
<p dir=3D"auto">On Apr 6, 2016, at 6:33 PM, Pete Resnick <a href=3D"mailt=
o:presnick@qti.qualcomm.com">presnick@qti.qualcomm.com</a> wrote:</p>

<p dir=3D"auto">Two things, neither earth-shattering:</p>

<p dir=3D"auto">Jari did say he thought it was still too long. The second=
 paragraph (mentioning the patent policy) seems duplicative with what's i=
n the second bullet and the list at the bottom. And of course the top-lev=
el message should be that first bullet: You have to follow all of the rul=
es. Let's just strike the second paragraph.</p>

<p dir=3D"auto">In addition to the pointer to the documents at the bottom=
 (which I presume will be links when this thing appears in HTML), it woul=
d be great to have a link to <a href=3D"https://www.ietf.org/ombudsteam">=
https://www.ietf.org/ombudsteam</a> <a href=3D"https://www.ietf.org/ombud=
steam">https://www.ietf.org/ombudsteam</a> placed next to the line regard=
ing anti-harassment procedures. That'll let people also find the IESG Sta=
tement and other info.</p>

<p dir=3D"auto">pr</p>

<p dir=3D"auto">On 21 Mar 2016, at 13:51, IESG Secretary wrote:</p>

<p dir=3D"auto">Note Well</p>

<p dir=3D"auto">This is a reminder of IETF policies in effect on various =
topics such as<br>
patents or code of conduct. It is only meant to point you in the right<br=
>
direction. Exceptions may apply.</p>

<p dir=3D"auto">The IETF's patent policy and the definition of an IETF "c=
ontribution"<br>
and "participation" are set forth in BCP 79; please read it carefully.</p=
>

<p dir=3D"auto">As a reminder:</p>

<p dir=3D"auto">=E2=80=A2 By participating in the IETF, you agree to foll=
ow IETF processes and<br>
policies.<br>
=E2=80=A2 If you are aware that any IETF contribution is covered by paten=
ts or<br>
patent applications that are owned or controlled by you or your<br>
sponsor, you must disclose that fact, or not participate in the<br>
discussion.<br>
=E2=80=A2 As a participant in any IETF activity you acknowledge that writ=
ten,<br>
audio and video records of meetings may be made public.<br>
=E2=80=A2 Personal information that you provide to IETF will be handled i=
n<br>
accordance with the IETF Privacy Statement.</p>

<p dir=3D"auto">Definitive information is in the documents listed below a=
nd other IETF<br>
BCPs. For advice, please talk to WG chairs or ADs:<br>
=E2=80=8B<br>
BCP 9 (Internet Standards Process)<br>
=E2=80=8BBCP 25 (Working Group processes)<br>
BCP 25 (Anti-Harassment Procedures)<br>
BCP 54 (Code of Conduct)<br>
=E2=80=8BBCP 78 (Copyright)<br>
=E2=80=8BBCP 79 (Patents, Participation)<br>
TBD (Privacy)</p>
</blockquote>
</blockquote>

<p dir=3D"auto">-- <br>
Pete Resnick <a href=3D"http://www.qualcomm.com/%7Epresnick/">http://www.=
qualcomm.com/~presnick/</a><br>
Qualcomm Technologies, Inc. - +1 (858)651-4478</p>

</div>
--=_MailMate_0A13FA2C-4533-41CA-AC08-B156249E08CD_=--


From nobody Wed Apr  6 20:47:18 2016
Return-Path: <melinda.shore@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 A8D5012D0B3 for <ietf@ietfa.amsl.com>; Wed,  6 Apr 2016 20:47:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 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, RCVD_IN_DNSWL_LOW=-0.7, 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 xMs9Z30cSazy for <ietf@ietfa.amsl.com>; Wed,  6 Apr 2016 20:47:16 -0700 (PDT)
Received: from mail-pa0-x243.google.com (mail-pa0-x243.google.com [IPv6:2607:f8b0:400e:c03::243]) (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 0D07E12D0A3 for <ietf@ietf.org>; Wed,  6 Apr 2016 20:47:15 -0700 (PDT)
Received: by mail-pa0-x243.google.com with SMTP id q6so5778074pav.0 for <ietf@ietf.org>; Wed, 06 Apr 2016 20:47:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding; bh=82KdsYDGZ8qPNZVVSPNR02FSR6L+YzHjlEJN7cMNRyI=; b=Nm1x26Rmtd/yp0EIkfnbnjrcD3qvWdOuc4z+xVJp7akAeU/gIyVqBLxb5XyFL5PGwv FMF8r4Xkp8tB/X7EXbN7q8VdH96EWRhnKQlGabm3pmRGjSjR7oscHHE34g6OH9tze9Bq GkNf7mapOKGsF9GUz/OifCKZGeq01niR0CrBZJMjBBh2CF/bn6av6+8PTW/dZR3JLq/+ HirO9NV+BNlKJzkngJZAiwAxPjbwHp6ambB8xvumZ9kbnqSxSxt7U/0NnVWCeoCoAyxi DMtfN+0TL3rrdX5z3u830Bji7kEMY8y+77Hz1jLwEeLF0Ocmoza2VHXgWuuA7Wf9v7zN 1Xwg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=82KdsYDGZ8qPNZVVSPNR02FSR6L+YzHjlEJN7cMNRyI=; b=MOmCClbaVR1FpsXhQ4lZboMngguXcC0/KINv7o20CDZDEP1Ao7aVyAoFCfPb1sUttR KFn2td5D6EMdTyo1BK3HP67gcsB90HAde5PHw4cAkjpTKfxfe3Topy/svt3QTnJCxbyV 7j/H6XqMzTwdzZ1ytnH3fwKOUiz/C5lzaCTJb9f0blzmDdR1FzMA0bf8WK1k4tthv+9L YwjNJkeS1rlgu6Pc9pW4kAUUnt85ihXtYZ4MpN72MU4KK3sDl67UT4m9AymF14RA3MWR 8+UO23o3g6S12IwnzJ0g6lnEBIZQveAIguyfzv3C3YLv81YrKDbm5qJMCUAtPoG1RBAv fLWg==
X-Gm-Message-State: AD7BkJLuoKpy3XJPuXozw8fAbRf+PdjxwAJl8yWhe9RqmL+Zeb19+0NANozWjp548kPNEA==
X-Received: by 10.66.160.7 with SMTP id xg7mr1471640pab.10.1460000835532; Wed, 06 Apr 2016 20:47:15 -0700 (PDT)
Received: from Melindas-MacBook-Pro.local (74-124-96-91-radius.dynamic.acsalaska.net. [74.124.96.91]) by smtp.googlemail.com with ESMTPSA id u64sm8000798pfa.86.2016.04.06.20.47.14 for <ietf@ietf.org> (version=TLSv1/SSLv3 cipher=OTHER); Wed, 06 Apr 2016 20:47:14 -0700 (PDT)
Subject: Re: "We did not know" is not a good excuse
To: ietf@ietf.org
References: <09ff01d1905c$f15d4e70$d417eb50$@olddog.co.uk> <5705C39E.30807@dcrocker.net> <5705C837.5060000@gmail.com> <CAHkmkwuOxOnmJa7KOPdW0Fpqdoq2c7oKWmt9B+zvSy6WcCY5QA@mail.gmail.com>
From: Melinda Shore <melinda.shore@gmail.com>
Message-ID: <5705D883.2090309@gmail.com>
Date: Wed, 6 Apr 2016 19:48:19 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:38.0) Gecko/20100101 Thunderbird/38.6.0
MIME-Version: 1.0
In-Reply-To: <CAHkmkwuOxOnmJa7KOPdW0Fpqdoq2c7oKWmt9B+zvSy6WcCY5QA@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/i1j7lb2ahttty7W2Stupxh83wdw>
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, 07 Apr 2016 03:47:17 -0000

On 4/6/16 7:12 PM, Harish Pillay wrote:
> There are ongoing debates on withdrawing Section 377A and it
> will happen eventually. It is a matter of time.

Well, it was upheld by your courts as recently as late 2014, and
it is by no means the only anti-gay law on the books in Singapore.

Melinda


From nobody Wed Apr  6 21:32:37 2016
Return-Path: <adrian@olddog.co.uk>
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 BA0F912D137 for <ietf@ietfa.amsl.com>; Wed,  6 Apr 2016 21:32:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.22
X-Spam-Level: 
X-Spam-Status: No, score=-1.22 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01] 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 h5FFBV73q5Zl for <ietf@ietfa.amsl.com>; Wed,  6 Apr 2016 21:32:33 -0700 (PDT)
Received: from asmtp1.iomartmail.com (asmtp1.iomartmail.com [62.128.201.248]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7AF1712D123 for <ietf@ietf.org>; Wed,  6 Apr 2016 21:32:33 -0700 (PDT)
Received: from asmtp1.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp1.iomartmail.com (8.13.8/8.13.8) with ESMTP id u374WOVx020986; Thu, 7 Apr 2016 05:32:24 +0100
Received: from 950129200 (static.66.246.111.190.cps.com.ar [190.111.246.66] (may be forged)) (authenticated bits=0) by asmtp1.iomartmail.com (8.13.8/8.13.8) with ESMTP id u374WLRX020944 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO); Thu, 7 Apr 2016 05:32:23 +0100
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: <dcrocker@bbiw.net>
References: <09ff01d1905c$f15d4e70$d417eb50$@olddog.co.uk> <5705C39E.30807@dcrocker.net>
In-Reply-To: <5705C39E.30807@dcrocker.net>
Subject: RE: "We did not know" is not a good excuse
Date: Thu, 7 Apr 2016 05:32:17 +0100
Message-ID: <0a5801d19086$79f40e30$6ddc2a90$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQGMmqG5z30WLKo9QlhbwnFG9R5TNAJCqcjan/XAz9A=
Content-Language: en-gb
X-TM-AS-MML: disable
X-TM-AS-Product-Ver: IMSS-7.1.0.1679-8.0.0.1202-22244.005
X-TM-AS-Result: No--14.877-10.0-31-10
X-imss-scan-details: No--14.877-10.0-31-10
X-TMASE-MatchedRID: nVQUmLJJeyYn2WEbWzq9rfHkpkyUphL9TJDl9FKHbrmHwGEm+CpYGcvS OFlVWsCbiQB26/9yMlW33SGYV5ytzsfgk3gaw8COJlIRBurDUWMhXHiVbGfuYznKpbGL4ChVqA7 +29SXlN6aKL/c2Xr4HsOkNyJjwMMRJDsLtEDPxjkV271HorxLNJb07sTmkdICmyiLZetSf8nJ4y 0wP1A6AMaUO+wtQNbajoczmuoPCq24GuLs8K0RsNq33n95UPoMbiLm3GKRSRL7Ana5VBNuxstUZ hqpwE9N
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/rztetnqMDsuRYkWajnA1MV8uvjA>
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: adrian@olddog.co.uk
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, 07 Apr 2016 04:32:35 -0000

Dave,

> > How do we move on so:
> ...
> > - this problem does not recur
> 
> What you probably /do/ mean is that further venue selections avoid
> places that effectively serve to exclude participation by various
> constituencies. 

What I mean, and I have no reason to doubt the good intentions and diligence of
the IAOC and Meetings Committee, is that we need to avoid situations where:

- the IAOC is unaware of the strength of feeling in the community on a selection
issue
- the IAOC is unaware of travel issues for a particular venue
- the community is surprised by the choice of venue
- the venue, host, sponsor, IAOC, IETF, are embarrassed by the reaction to a
venue announcement

It may be true that the community could provide a list of vetoed and approved
locations for the Meetings Committee to work with. That is a possible approach.
Another approach might be for the Meetings Committee to suggest some venues and
see what the community feels (this has happened before with a poll on some
venues that Ray sent to the community).

But I want to spec the problem, not engineer a solution. I trust the IAOC to
develop a solution to the problem that works with the other issues they have to
handle. And I trust them to bring the solution forward soon.

Adrian


From nobody Wed Apr  6 22:18:28 2016
Return-Path: <harish.pillay@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 36C3D12D1BD for <ietf@ietfa.amsl.com>; Wed,  6 Apr 2016 22:18:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 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, RCVD_IN_DNSWL_LOW=-0.7, 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 6yHfeIlfJjGc for <ietf@ietfa.amsl.com>; Wed,  6 Apr 2016 22:18:26 -0700 (PDT)
Received: from mail-ig0-x22b.google.com (mail-ig0-x22b.google.com [IPv6:2607:f8b0:4001:c05::22b]) (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 D070512D15A for <ietf@ietf.org>; Wed,  6 Apr 2016 22:18:25 -0700 (PDT)
Received: by mail-ig0-x22b.google.com with SMTP id f1so145879254igr.1 for <ietf@ietf.org>; Wed, 06 Apr 2016 22:18:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to;  bh=bXUXi/SQS4LVnpAAuMr/7o8BM23B2qLGPWPj2HiNiXw=; b=Eo3xMVFQxi4buR6GlyPatZ54jCTM2zz+RUv4a9d9hQc6oH6jyrsMgjrjaLNCGCw0iQ utYhWr2AI0MNIgXTBR+QDRuIGdKGMkAI0it2PEGr9f51B6nKvRgkQFbv2E8od70CB2f6 CkFDhRfn/u/FJ2pFgIj0A2fBv5hqfz7etbvXJvUxDfe19p7sQ6a1asZ0N4BgaL8K2vvT 0tJ+nLTOV6mipEThApbm5KrTRmjM3Ab5iplMWjHniiQuSfRi56ktRgTYUW4YYZh1pDXF 4DrJIxLZvTw3OPAsun/EPVJNW7Fpj7heaKDaZnCxIj335ex3DpYmNj54BB19NC2I9Z/k vXyA==
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:date :message-id:subject:from:to; bh=bXUXi/SQS4LVnpAAuMr/7o8BM23B2qLGPWPj2HiNiXw=; b=Oskz041h9e8sCbt8H4kSzd1F7t+1avS9hUhUl3DUSWwDmbrkiGpygzTcVk6SdyTnBc a6BqwTA7yKDwbc4Ij1hOmdUxa4RCyoo8PWD9HsjsghGGHVRnCK6SuAOVJWxGBxj6QPc7 F6+4NGa/vyE6Cy6qU0eFZ0YUdUGhG5P67pedZfj0S9PiBx2QKi3jsro0hdwGhDOkvGm4 HtsRS/yB3gNKfotkBf9JQKzCQ2uXDNNvOETMmaPu5bGdG2vMYcjX7azSj9MwRyQj/T9b XecCg/rchFEMExQzA7CEc8KXWmh+Mojf+gexdmX6WG4NHIBTgZGt79Kx9m1v+qGUisQz DIHA==
X-Gm-Message-State: AD7BkJJ1D5pcD2wZf22IUQlXHWhdTKQe4O+WAdZB3oQI+8nDtfksN8Hi50/avLNGxL8gRyEmp+nurKRnU35jyw==
MIME-Version: 1.0
X-Received: by 10.50.61.148 with SMTP id p20mr1669511igr.20.1460006305278; Wed, 06 Apr 2016 22:18:25 -0700 (PDT)
Received: by 10.107.129.214 with HTTP; Wed, 6 Apr 2016 22:18:25 -0700 (PDT)
In-Reply-To: <5705D883.2090309@gmail.com>
References: <09ff01d1905c$f15d4e70$d417eb50$@olddog.co.uk> <5705C39E.30807@dcrocker.net> <5705C837.5060000@gmail.com> <CAHkmkwuOxOnmJa7KOPdW0Fpqdoq2c7oKWmt9B+zvSy6WcCY5QA@mail.gmail.com> <5705D883.2090309@gmail.com>
Date: Thu, 7 Apr 2016 13:18:25 +0800
Message-ID: <CAHkmkwt9geOiwXnqi=LxPWUVp0_oR7GDgzt6KZ3ZM46U__c3Yw@mail.gmail.com>
Subject: Re: "We did not know" is not a good excuse
From: Harish Pillay <harish.pillay@gmail.com>
To: ietf@ietf.org
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/jG8B-0dNU-MkRmuXiGg1Tc6eCBU>
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, 07 Apr 2016 05:18:27 -0000

>> There are ongoing debates on withdrawing Section 377A and it
>> will happen eventually. It is a matter of time.
>
> Well, it was upheld by your courts as recently as late 2014, and
> it is by no means the only anti-gay law on the books in Singapore.

No different from the many other anti-gay laws on books in many
countries including the US. Important thing is, in the Singapore
context, that even though it is in the books, it is NOT enforced
in any aggressive nor wanton manner.

Harish


From nobody Wed Apr  6 22:32:29 2016
Return-Path: <melinda.shore@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 66C0E12D1EC for <ietf@ietfa.amsl.com>; Wed,  6 Apr 2016 22:32:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 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, RCVD_IN_DNSWL_LOW=-0.7, 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 gafb5hyjZmBg for <ietf@ietfa.amsl.com>; Wed,  6 Apr 2016 22:32:25 -0700 (PDT)
Received: from mail-pf0-x243.google.com (mail-pf0-x243.google.com [IPv6:2607:f8b0:400e:c00::243]) (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 CE28612D1D5 for <ietf@ietf.org>; Wed,  6 Apr 2016 22:32:25 -0700 (PDT)
Received: by mail-pf0-x243.google.com with SMTP id r187so6243008pfr.2 for <ietf@ietf.org>; Wed, 06 Apr 2016 22:32:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding; bh=0Gi1gXk4JRigTxF1YWws/va3BMlkZpL6GiVopDlHBAQ=; b=WLX7kO6vVc+tiuCkRtjEI0dA/s+XvzhU4eWfpEasXTdCUJw0Ak18mbphOMumcmwDLU pG997KX7Hr9nI4mFwLqLE6UI63XZfI470gh9rVLuRdCGvrv+KsEsjb4xD5qcM1iIClGY wJy9auhOq1OOoD9W+Mm618HSVnew4oe2Y7uWvJfWr9lVMAIiCPhrwF3BZ7IoWeRs0PJ/ Jvm9tN/XbgL7a53d9m7+Ccati0qZ9cMXob16BbNW2M1IV+JJXkPhkmqV/iKqHQ2oAUxf aHtF+kX7W4j18ONR/5pGIXRl3IHD7PuEORDUgKGGbF7nsaoYCyEYChrMFjIA4RXR0f1H FyEg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=0Gi1gXk4JRigTxF1YWws/va3BMlkZpL6GiVopDlHBAQ=; b=kydktZxFWlnQ9+FyGIlRcIBEo6hmtViH5s2DisL/4DaXwnCVmFjpqlmgDXBaWbBEIk xXrYm6mBs0HtwuZCQdxnC50zx1sX1phN0pqBn23MQIBmGGrSTy/mw0mLOSMAliVXzDPz KvEj6GXihCG2dz2SJ8gjIyukXEaKp1OAeXJq9Pkb73MBTWR0oMZjGKhRjzJZ4OPG8YxZ zdntnMcOxDoqZ+62vBVEcOqf58jFzlgNgMDwacJxb1TkESapLW5JdKJbCYGqZgMSM0Q4 CXXd4P3ECR3tCEl+RvV5bXoEvb9KclWt+pCfWpjUteR2RtYqIdZRmp/117zYM6Fvi34h U8ng==
X-Gm-Message-State: AD7BkJLPxx0taD+OcScugllpmddapTq2N7Pt2CyYXKVsQRDw+Dch+l5l6nbvyAwZ4ouP3g==
X-Received: by 10.98.68.145 with SMTP id m17mr1946366pfi.65.1460007145330; Wed, 06 Apr 2016 22:32:25 -0700 (PDT)
Received: from Melindas-MacBook-Pro.local (74-124-96-91-radius.dynamic.acsalaska.net. [74.124.96.91]) by smtp.googlemail.com with ESMTPSA id m89sm8718649pfi.12.2016.04.06.22.32.24 for <ietf@ietf.org> (version=TLSv1/SSLv3 cipher=OTHER); Wed, 06 Apr 2016 22:32:24 -0700 (PDT)
Subject: Re: "We did not know" is not a good excuse
To: ietf@ietf.org
References: <09ff01d1905c$f15d4e70$d417eb50$@olddog.co.uk> <5705C39E.30807@dcrocker.net> <5705C837.5060000@gmail.com> <CAHkmkwuOxOnmJa7KOPdW0Fpqdoq2c7oKWmt9B+zvSy6WcCY5QA@mail.gmail.com> <5705D883.2090309@gmail.com> <CAHkmkwt9geOiwXnqi=LxPWUVp0_oR7GDgzt6KZ3ZM46U__c3Yw@mail.gmail.com>
From: Melinda Shore <melinda.shore@gmail.com>
Message-ID: <5705F127.30209@gmail.com>
Date: Wed, 6 Apr 2016 21:33:27 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:38.0) Gecko/20100101 Thunderbird/38.6.0
MIME-Version: 1.0
In-Reply-To: <CAHkmkwt9geOiwXnqi=LxPWUVp0_oR7GDgzt6KZ3ZM46U__c3Yw@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/KVBcEa3358vLruFYdlVWBxEMFEc>
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, 07 Apr 2016 05:32:27 -0000

On 4/6/16 9:18 PM, Harish Pillay wrote:
> No different from the many other anti-gay laws on books in many
> countries including the US.

Actually, it is.  Our Supreme Court has been striking down
anti-gay legislation, not upholding it.  Right now it is the
law in Singapore that sexual contact between consenting adult
men is a criminal act.  The best way to clarify that Singapore
doesn't really mean it is to get rid of the law, along with
your other miscellaneous anti-gay laws.

I live in Alaska, so I'm certainly sympathetic to the problem
of living in a place you love that does some things that are
very wrong and that are difficult to explain to people not from
there, and the embarrassment that sometimes goes with that.
But my own feeling is that the best way to deal with those
situations is to own them and to work for change.  I respect your
feelings about your country but I will not be attending a
meeting in Singapore unless the laws change.

Melinda


From nobody Wed Apr  6 22:58:32 2016
Return-Path: <harish.pillay@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 EDD3612D544 for <ietf@ietfa.amsl.com>; Wed,  6 Apr 2016 22:58:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 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, RCVD_IN_DNSWL_LOW=-0.7, 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 djfGUY-IFQNt for <ietf@ietfa.amsl.com>; Wed,  6 Apr 2016 22:58:29 -0700 (PDT)
Received: from mail-io0-x235.google.com (mail-io0-x235.google.com [IPv6:2607:f8b0:4001:c06::235]) (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 0F39412D1EC for <ietf@ietf.org>; Wed,  6 Apr 2016 22:58:25 -0700 (PDT)
Received: by mail-io0-x235.google.com with SMTP id g185so82359074ioa.2 for <ietf@ietf.org>; Wed, 06 Apr 2016 22:58:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to;  bh=s5jt/ySjh4WeVgYQ3m1YXdXT51PQ3qxLyXCsCbRXOJU=; b=dt1aDqiuilgdWrbthfE+LsDq4hQvhsF/xyB+gUIo/Ma+THeegiJqQa72s5XhB2OkRL 1RMYHLw99XfvNMcn2qk0+ebVKQYL4jgWDgqEt2GtLHdvCKGrSfKSoaj/mOJ3uwBro0S5 pqfrNgbq2wsr/MENSbRauaGEkBZwa0b3JY2PA/mkz/enftuCoLX3S0Rrb8VQrNuDq5d1 9ECAsPR+akvjaA+cpiDIDMkO1brYimnNumn4UdhkQCBmM1lJHaIG+F0A9tACy9LTpzsh DSiMSiYUQJzxjK3e0kbUkhJ1UXE/h6K2JpcDB7JFp0KSL5Ln08IveRSfJQffzh+409CT zF3g==
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:date :message-id:subject:from:to; bh=s5jt/ySjh4WeVgYQ3m1YXdXT51PQ3qxLyXCsCbRXOJU=; b=ZHRybGWSCqjDboIAhN5SxBdTQUbBROlvOAp9dB5Vs3zdJf26Hgrc1fy0m4ZmO2DZ1t 61UC9sSLDbhOaYAwr7m0wPjnHJOq04KNUvXA0M0g2oYfjNmaHeSFfTGgu4iEOWlGHRlb OTIzz/hKvv5b+N7YWSAcMy/HC390gAIxIJY6791+zSSTFhoKmSluJd58iFapiy1SmpNM Kf6K9oNTNqpRnAI+ypkljNCOl32qgR4hn1NfFoTQlouPq1Ph2U4qrlZ+FgOn++3I7qE6 nBMzj1yk1xTPcd0Xucvuqv/pk86vp7odGTrgqzbUVpHMeMjwPswqxIdhdMpfC/iMNGkY wkmA==
X-Gm-Message-State: AD7BkJLe5c+nf4lP7XUwnL5LfTmcD1hPQO5DWX0CE9eWUJB24z/xm+U3XPhfXDygPLfKZ9cHDX1q4KogHFSLig==
MIME-Version: 1.0
X-Received: by 10.107.56.196 with SMTP id f187mr1487959ioa.156.1460008704391;  Wed, 06 Apr 2016 22:58:24 -0700 (PDT)
Received: by 10.107.129.214 with HTTP; Wed, 6 Apr 2016 22:58:24 -0700 (PDT)
In-Reply-To: <5705F127.30209@gmail.com>
References: <09ff01d1905c$f15d4e70$d417eb50$@olddog.co.uk> <5705C39E.30807@dcrocker.net> <5705C837.5060000@gmail.com> <CAHkmkwuOxOnmJa7KOPdW0Fpqdoq2c7oKWmt9B+zvSy6WcCY5QA@mail.gmail.com> <5705D883.2090309@gmail.com> <CAHkmkwt9geOiwXnqi=LxPWUVp0_oR7GDgzt6KZ3ZM46U__c3Yw@mail.gmail.com> <5705F127.30209@gmail.com>
Date: Thu, 7 Apr 2016 13:58:24 +0800
Message-ID: <CAHkmkwvQFVMwMdh9BzLxepNyWA6+BuzmgSP4xH6Uejm6W=CiHQ@mail.gmail.com>
Subject: Re: "We did not know" is not a good excuse
From: Harish Pillay <harish.pillay@gmail.com>
To: ietf@ietf.org
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/qYjFY0ULxaC-QPzDqOBwWWpAukk>
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, 07 Apr 2016 05:58:31 -0000

>> No different from the many other anti-gay laws on books in many
>> countries including the US.
>
> Actually, it is.  Our Supreme Court has been striking down
> anti-gay legislation, not upholding it.  Right now it is the
> law in Singapore that sexual contact between consenting adult
> men is a criminal act.  The best way to clarify that Singapore
> doesn't really mean it is to get rid of the law, along with
> your other miscellaneous anti-gay laws.

There has not been, to the best of my knowledge, *anyone* who
has been charged in court under that rule (which I think is the
only rule there is) unless it was based on a report made by
one of the parties involved and it is usually under that offense
of rape or by parents (of minors involved). No one is going around
looking into bedrooms to see what is happening.

Again, no one who has participated in the pinkdot.sg event has,
to the best of my knowledge, been charged or penalised for
their orientation.

> I live in Alaska, so I'm certainly sympathetic to the problem
> of living in a place you love that does some things that are
> very wrong and that are difficult to explain to people not from
> there, and the embarrassment that sometimes goes with that.
> But my own feeling is that the best way to deal with those
> situations is to own them and to work for change.  I respect your
> feelings about your country but I will not be attending a
> meeting in Singapore unless the laws change.

It is a pity that you won't attend. I respect your stand and
principle. I feel that you are unfortunately making this more
of an issue than it really is in Singapore. Yes, we have prudes
(exclusively the religious sort[0]) who make it their problem
what consenting adults do based on their interpretation of
some fairy tale :-).

Singapore is far from perfect and we have our peculiarities. But
so does every society and country.

I would strongly encourage you to come to Singapore. I would
be more than happy to welcome you here. We need keep the
channels open and not closed. Then, and only then, will things
change for the better.

Harish
[0] http://news.asiaone.com/news/singapore/gay-lifestyle-against-bible-says-council-churches


From nobody Thu Apr  7 00:53:37 2016
Return-Path: <john-ietf@jck.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 A610612D59C for <ietf@ietfa.amsl.com>; Thu,  7 Apr 2016 00:53:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] 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 GTFM2R4qtQ5a for <ietf@ietfa.amsl.com>; Thu,  7 Apr 2016 00:53:27 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0C85E12D585 for <ietf@ietf.org>; Thu,  7 Apr 2016 00:53:26 -0700 (PDT)
Received: from [198.252.137.10] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1ao4kb-00064b-LI; Thu, 07 Apr 2016 03:53:13 -0400
Date: Thu, 07 Apr 2016 03:53:08 -0400
From: John C Klensin <john-ietf@jck.com>
To: dcrocker@bbiw.net, adrian@olddog.co.uk, ietf@ietf.org
Subject: Re: "We did not know" is not a good excuse
Message-ID: <3A9DD13A35E258166DA28763@JcK-HP8200.jck.com>
In-Reply-To: <5705C39E.30807@dcrocker.net>
References: <09ff01d1905c$f15d4e70$d417eb50$@olddog.co.uk> <5705C39E.30807@dcrocker.net>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/iqA0O9aAeiOst_8tonMNipZGadY>
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, 07 Apr 2016 07:53:30 -0000

--On Wednesday, April 06, 2016 19:19 -0700 Dave Crocker
<dhc@dcrocker.net> wrote:

> On 4/6/2016 4:34 PM, Adrian Farrel wrote:
>> How do we move on so:
> ...
>> - this problem does not recur
> 
> 
> What you probably do not mean is 'we do not go to Singapore
> again.
> 
> What you probably /do/ mean is that further venue selections
> avoid places that effectively serve to exclude participation
> by various constituencies.  Or at least, that is what I hope
> you mean, because it has broader utility.
> 
> So I'll repeat what I said at the virtual microphone:
> 
>     If the community wishes meeting venue selection to refrain
> from choosing specific places, the community needs to develop
> that list.
> 
> Anything less specific leaves too much to interpretation,
> which guarantees that similar errors will recur.

Dave,

Thanks for clarifying.  I agreed with what I thought you said at
the virtual microphone.   I disagree with the above.

If the issue is "come up with firm criteria, including what
issues are showstoppers", then I think that is a
nearly-reasonable expectation.   I would still expect the IAOC
to do some diligent investigation and propose a list for
community discussion, just as we have similar expectations for
WGs, but I think some list could be developed.  

FWIW, I think the "showstopper" idea borrows heavily from what
Pete had to say last night.   If the community decides that some
conditions (or lack thereof, make a particular venue, city, or
country unacceptable,  I don't think the community should hear
about how the 1-1-1 rule, or whatever replaces it, required
making tradeoffs or balancing issues.   Put differently, I see
that "rule" as more of a guideline: if we cannot find acceptable
venues in a particular region without compromising important
principles, then we go to that region less often (or even not at
all), not drop those principles in the interest of balance.

And, as others have said, this is precisely why some of us have
been very concerned about the lack of openness, transparency,
and meaningful consultation by the Meetings Committee and IAOC.

On the other hand, if you meant, as the quoted text above seems
to indicate, that the community needs to come up with a list of
banned "specific places", with the Meetings Committee treating
everywhere else as OK, I think that is an unreasonable
expectation.  Not only do I think the community expects the
Meetings Committee and IAOC to do the research and be
consultative (see Adrian's notes) but, if the only firm rule is
"specific excluded places" and everything else is "a balance",
with balancing factors sorted out in secrecy, then it seems to
me that our history suggests that "1-1-1" or "nice vacation spot
for spouses and families" is likely to outweigh what I hope most
of us would agree are important principles.

best,
     john

p.s. I think the question about Singapore is not "do we go back
a second time" but "do we go at all".  However long and painful
the contract negotiation process was, the costs of renegotiating
or extricating ourselves _are_ a matter of tradeoffs or
"balance".  Of course, it is probably impossible to predict what
the state of their laws, and enforcement of those laws, might be
a year and a half out, but that is at least as much an argument
against suggestions that we should be working even more than
three years out than it is that going to a place with odious
laws and a history of brutal enforcement of what they choose to
enforce is a matter of "balancing" assorted factors.




From nobody Thu Apr  7 01:23:23 2016
Return-Path: <lloyd.wood@yahoo.co.uk>
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 8BCDD12D5A9 for <ietf@ietfa.amsl.com>; Thu,  7 Apr 2016 01:23:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level: 
X-Spam-Status: No, score=-2.701 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, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-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=yahoo.co.uk
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 PZHHnORGQO3W for <ietf@ietfa.amsl.com>; Thu,  7 Apr 2016 01:23:19 -0700 (PDT)
Received: from nm32-vm1.bullet.mail.gq1.yahoo.com (nm32-vm1.bullet.mail.gq1.yahoo.com [98.136.216.224]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CFD1F12D5B3 for <ietf@ietf.org>; Thu,  7 Apr 2016 01:23:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.co.uk; s=s2048;  t=1460017399; bh=IeE2S86z+vFLdqmsUDObizbWQjlM1AUo1JfRxOv0olM=;  h=Date:From:Reply-To:To:In-Reply-To:References:Subject:From:Subject;  b=N3GhsacUlWrD1+4ST85LcVx4TNihW33Hk2W5uf3QrRQ5rT7PgGXq70/xDXxBYHtldroQrb+0mffM9O8LNK3Dr5sMC2UuwF77dNgSDwqTHa2a2Go7RQdH+mHs4YebwEq1kvaPVJQDj6LmYY5OhEZb6iQpvK4k8uM3VH4bBzPQRCqGY6aZPFSigx9tUZWpntY6f007Zs8+is4TFiFSa1mH6aw4TvjbpubNw2iTxUUJRxDiZkKCsI5sDuULwgeluIIlY4cqg8rwezw9Ai8OoLfxkF+/5SZHC+lzk++iB4zUmadl/AfwaEysbiRbPjzJH3ckulCLlOInP0Q7ORU0+3kbcQ==
Received: from [127.0.0.1] by nm32.bullet.mail.gq1.yahoo.com with NNFMP; 07 Apr 2016 08:23:19 -0000
Received: from [98.137.12.191] by nm32.bullet.mail.gq1.yahoo.com with NNFMP; 07 Apr 2016 08:20:22 -0000
Received: from [212.82.98.60] by tm12.bullet.mail.gq1.yahoo.com with NNFMP; 07 Apr 2016 08:20:22 -0000
Received: from [212.82.98.81] by tm13.bullet.mail.ir2.yahoo.com with NNFMP; 07 Apr 2016 08:20:21 -0000
Received: from [127.0.0.1] by omp1018.mail.ir2.yahoo.com with NNFMP; 07 Apr 2016 08:20:21 -0000
X-Yahoo-Newman-Property: ymail-4
X-Yahoo-Newman-Id: 915190.53086.bm@omp1018.mail.ir2.yahoo.com
X-YMail-OSG: sm_opA8VM1kHnhSZFNooKKEKgL68cRxpn7QRDqhaJSDgOvxxkECNFD30AmSAq__ iIkLVSaG1xk5PoppqhCx4r6aNE1ooaFlNKzs5dHzLAFY9svgA9FyJ9LUvQVfluzMp8ALnrNImgey 5VS5ohS7zEtDiGRtFczrhIOq_25aZTvOqn4Z_JHmRTgGcu9f_7hW1jAfvqhlL49FZXrrUi2aUOkT lMw7E72ZoAwXAP7E1PHjMcyjINJT_RYAT3mOCbSkOMVxKgdSwSM6Uaeidech3V63o7UMhc2L3VcT JnezGGKzFjFtAYs_Eg.Yse_bVIMQ7s5gqLK3Z8HthVfecxuCsLFnIdllbLk_rU_srcLQLJuxKMbB h9BlF8B0aaYnKsSg_Eo1fQ6VlrE85gfigAX0_ZBm_J1lTtn4X9boqVLslyiXYyrZ.WHwpahObOaK g76tLjutRXw9gxR0ZlE.uxrf6UGpdwyA2p0djdrPTaOrjzETEe8.GrHhhuxS8sQaKrkEnahrr4dJ 57ipIRtT84j7mf8w3xvELFFWNIxt_zmF5X_c6KZogQgg_b7Di
Received: by 212.82.98.122; Thu, 07 Apr 2016 08:20:21 +0000 
Date: Thu, 7 Apr 2016 08:20:20 +0000 (UTC)
From: <lloyd.wood@yahoo.co.uk>
To: Melinda Shore <melinda.shore@gmail.com>, "ietf@ietf.org" <ietf@ietf.org>
Message-ID: <1742258375.1209279.1460017220756.JavaMail.yahoo@mail.yahoo.com>
In-Reply-To: <5705C837.5060000@gmail.com>
References: <5705C837.5060000@gmail.com>
Subject: Re: "We did not know" is not a good excuse
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/C072JtxTC016gNR14jJ4ah3fFpA>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: lloyd.wood@yahoo.co.uk
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, 07 Apr 2016 08:23:21 -0000

> The situation in Singapore goes well beyond being vaguely 
> homophobic, to actively criminalizing the families of some 
> IETF participants.

And e.g. Papua New Guinea is the same. If you have a work
trip there, don't take your family there. Not least because
it's rather more violent than Singapore. But do go to
Singapore for the shopping. If members of your family have
a tendency towards shoplifting, I suspect shopping in
Singapore may be a bad idea for them. (While the
shopping in Port Moresby is _terrible_. Really limited
selections. And you need armed guards. And, oh, the
food. Locals have a sweet tooth. The diabetic and
gluten-intolerant members of your family will have
problems.)

Really, just don't take your family on work trips.
It's simply more trouble than it's worth. Either
they're bored, thrown in jail for shoplifting because
they're bored, or complaining incessantly that Minnesota
is too cold once they run out of boring interconnected
malls to shoplift from. (While in Port Moresby, the knives
come out early, and the shoplifter never gets bored. Or
reaches jail. Or a hospital. Which is perhaps just as
well.)

On a related note, nuclear weapons exist to endanger
the lives of most IETF participants. And their families.
I believe that the IETF should be actively boycotting
all countries with nuclear weapons. 

Singapore, to my knowledge, does not have a nuclear
arsenal and hasn't invaded any other countries to
endanger families' lives recently, so I'm okay with
Singapore.

I really want to know exactly what the IETF's declared
stances are on nuclear weapons, on armed proliferation, and
on state belligerency on the international stage by
warriors that endanger families.

The IETF should be showing we care by boycotting those
countries that do not meet our exacting standards in this
regard. They won't get our money or suffer our complaints
about their poor hotel and wifi service, and their revenue
and funding of their military-industrial complexes will
suffer greatly while their hotel services fail to improve
at all as a result of not receiving the enlightened
supportive criticism that comes from our high expectations.

Jari, can we get a workgroup set up with a list of RFC
position statements as target deliverables to get this
started? (Also, if we can get something out repudiating
IS-IS's existence as a routing protocol and denying that
we endorse it or its spread, that would no doubt be
well-received by everyone who has never heard of or
used IS-IS, and quite a few who have.)

thanks

L.
Lloyd Wood lloyd.wood@yahoo.co.uk http://about.me/lloydwood 


From nobody Thu Apr  7 05:41:13 2016
Return-Path: <ron.even.tlv@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 1626012D8BC; Thu,  7 Apr 2016 05:41:05 -0700 (PDT)
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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 LKQtVXBnG_WP; Thu,  7 Apr 2016 05:40:59 -0700 (PDT)
Received: from mail-qg0-x22e.google.com (mail-qg0-x22e.google.com [IPv6:2607:f8b0:400d:c04::22e]) (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 51ADB12D8BB; Thu,  7 Apr 2016 05:40:36 -0700 (PDT)
Received: by mail-qg0-x22e.google.com with SMTP id f52so61492754qga.3; Thu, 07 Apr 2016 05:40:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=from:to:cc:subject:date:message-id:mime-version:thread-index :content-language; bh=wRV/feiytcaxDGuf4eD4yv3JRCKJUQGIdp1Yodj6Kfw=; b=JFH9Cd8DJNCwUU3e2XeerXpcennvZuajls+Ok9d4wCx0lcEMKeOL7LiwGDlgdoPjGR tXwaYSpjeDdjQzkriZFmObk0iUuP6BsOsHFhTAjwH0jBEZ36UtD8b/bDCVz0q69ORdIk FoKlmlsAQNasipgt0yyNKoHyfOSuGT3Ma54GSStvh0lV4n5qhpnZThiy1HXVWILTdoOY KbqFdlfljAvop2y5UYEZbiIHK40AGP7x7r2rNyuimd1aqjtT/gWQYIaQenGJyuLRQOUW ESQjn54cPRwt9gY03PAS1aEmssC0F15sJgtxJ3V9FLSgIr75kW/4waPIqUf0mw2ppvOV Db2Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:to:cc:subject:date:message-id:mime-version :thread-index:content-language; bh=wRV/feiytcaxDGuf4eD4yv3JRCKJUQGIdp1Yodj6Kfw=; b=BpiVZMYII6uhaDsUtlFVS7BkiQ+nhEfi6yVy6lfePJXvcOLCLPo9A4aMirmbaHwwdp dmRjNXepVlIKuJkfDrP0HOtmszal/H56+5zEeKDyw7gmJAFZm6iQvHWG5UEP6XDaVcu6 PWkEkccyO3zkHE5X9Je8hQxBrvpkLro5UlSFVhAVYdvmckE7nJRJpySx0fS/aob37cHK UfP3KrysGEOFMJJEwJ1xaT160rgcYN8FeRzRlDu1v0reAnubBKuF9DEKZjQEUtLRfd9h xd0QMRpR8ghR7eNT8wyNIGp0QEdqmT/0d7zM7Z5lAtYobBJKKVhIT9IebDxa6osiSnhy xt5A==
X-Gm-Message-State: AD7BkJLpsWbc0LEBJp+Z7vjose64Rck9JhIxNCDnDh0cWa/5MN1MWux71IUQdFxAB/ebMg==
X-Received: by 10.140.91.244 with SMTP id z107mr3289104qgd.45.1460032835316; Thu, 07 Apr 2016 05:40:35 -0700 (PDT)
Received: from RoniPC ([2001:67c:370:160:e03e:d3ff:6be5:1fb6]) by smtp.gmail.com with ESMTPSA id 131sm1917810qhk.15.2016.04.07.05.40.33 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 07 Apr 2016 05:40:34 -0700 (PDT)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: <draft-ietf-tls-chacha20-poly1305.all@tools.ietf.org>
Subject: Gen-ART LC review of draft-ietf-tls-chacha20-poly1305-04 - resend
Date: Thu, 7 Apr 2016 15:40:30 +0300
Message-ID: <017a01d190ca$ace223b0$06a66b10$@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_017B_01D190E3.D2315780"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AdGQygxSCEkbP4XEQq2U/CrA+ZxzCg==
Content-Language: he
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/oPnPr6sSjnX0hOgFrnXJh1pI1Cw>
Cc: gen-art@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: Thu, 07 Apr 2016 12:41:05 -0000

This is a multipart message in MIME format.

------=_NextPart_000_017B_01D190E3.D2315780
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Please resolve these comments along with any other Last Call comments you
may receive.

Document:  draft-ietf-tls-chacha20-poly1305-04

Reviewer: Roni Even

Review Date:2016-3-28

IETF LC End Date: 2016-4-9

IESG Telechat date: 

 

Summary: This draft is almost ready for publication as a standard track
RFC.

 

 

 

Major issues:

I am wondering why this is a standard track document and not informational
since the registration requirements are specification required.  (RFC5246)

 

I am also wondering why this document updates RFC5246 and RFC6347.  Reading
the document it looked to me that the registration document is used also to
endorse this cypher suite by the IETF and if this is the case my view is
that there should be two documents, one Informational for registration and
the will be standard track and update RFC5246 and RFC6347

For Example the following text from section 1 "Therefore, a new stream
cipher to replace RC4 and address all the  previous issues is needed. "
provides what may look as a normative recommendation.

 

 

Minor issues:

 

Nits/editorial comments:

 


------=_NextPart_000_017B_01D190E3.D2315780
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 14 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin-top:0cm;
	margin-right:0cm;
	margin-bottom:10.0pt;
	margin-left:0cm;
	line-height:115%;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:10.5pt;
	font-family:Consolas;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
span.EmailStyle19
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:"Courier New";}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><a =
name=3D"OLE_LINK2"></a><a name=3D"OLE_LINK1"></a>I am the assigned =
Gen-ART reviewer for this draft. For background on Gen-ART, please see =
the FAQ at &lt;<a =
href=3D"http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq" =
target=3D"_blank">http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq=
</a>&gt;.<o:p></o:p></p><p class=3DMsoNormal>Please resolve these =
comments along with any other Last Call comments you may =
receive.<o:p></o:p></p><p class=3DMsoNormal>Document:&nbsp; <span =
style=3D'font-size:10.5pt;line-height:115%;font-family:"Courier =
New"'>draft-ietf-tls-chacha20-poly1305-04</span><span =
style=3D'font-family:"Courier New"'><o:p></o:p></span></p><p =
class=3DMsoNormal>Reviewer: Roni Even<o:p></o:p></p><p =
class=3DMsoNormal>Review Date:2016&#8211;3-28<o:p></o:p></p><p =
class=3DMsoNormal>IETF LC End Date: 2016&#8211;4-9<o:p></o:p></p><p =
class=3DMsoNormal>IESG Telechat date: <o:p></o:p></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Summary: =
This draft is almost ready for publication as a standard track&nbsp; =
RFC.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Major =
issues:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>I am =
wondering why this is a standard track document and not informational =
since the registration requirements are specification required.&nbsp; =
(RFC5246)<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>I am also =
wondering why this document updates RFC5246 and RFC6347. &nbsp;Reading =
the document it looked to me that the registration document is used also =
to endorse this cypher suite by the IETF and if this is the case my view =
is that there should be two documents, one Informational for =
registration and the will be standard track and update RFC5246 and =
RFC6347<o:p></o:p></span></p><pre =
style=3D'page-break-before:always'><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>For =
Example the following text from section 1 </span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>&#8220;<spa=
n style=3D'color:black'>Therefore, a new stream cipher to replace RC4 =
and address all the&nbsp; previous issues is needed. &#8220; =
&nbsp;provides what may look as a normative =
recommendation.<o:p></o:p></span></span></pre><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Minor =
issues:<o:p></o:p></span></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>Nits/editorial comments:<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></body></html>
------=_NextPart_000_017B_01D190E3.D2315780--


From nobody Thu Apr  7 05:50:44 2016
Return-Path: <john-ietf@jck.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 7BD3312D8E6 for <ietf@ietfa.amsl.com>; Thu,  7 Apr 2016 05:50:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] 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 NjBtvWDqQ-UQ for <ietf@ietfa.amsl.com>; Thu,  7 Apr 2016 05:50:40 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2661012D8F7 for <ietf@ietf.org>; Thu,  7 Apr 2016 05:50:32 -0700 (PDT)
Received: from [198.252.137.10] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1ao9OH-0006cr-En; Thu, 07 Apr 2016 08:50:29 -0400
Date: Thu, 07 Apr 2016 08:50:24 -0400
From: John C Klensin <john-ietf@jck.com>
To: Pete Resnick <presnick@qti.qualcomm.com>, Scott Bradner <sob@sobco.com>
Subject: Re: Proposed New Note Well
Message-ID: <450A3791838BC1F5A866A4E6@JcK-HP8200.jck.com>
In-Reply-To: <A3FBD041-3BC9-442C-B581-F874B4359FE1@qti.qualcomm.com>
References: <20160321165157.31914.47506.idtracker@ietfa.amsl.com> <E5F9AC1D-4FC2-40A7-90A3-DC3913C10D42@qti.qualcomm.com> <D9752087-788F-43D5-8ECE-EF1C677D45C9@sobco.com> <A3FBD041-3BC9-442C-B581-F874B4359FE1@qti.qualcomm.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/7CREPTvetjcwW_5n5Tpre4-qqYQ>
Cc: 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, 07 Apr 2016 12:50:42 -0000

Pete,

I think that would be an improvement, but I see a slightly
different tension that we probably need to deal with explicitly.
If we really want "short", e.g., fitting on one slide in big
letters, then the Note Well can be reduced to something like...

	"The IETF has a collection of policies.   As with a
	shrink-wrap license, you are responsible for all of them
	the moment you start participating or contributing, or
	interacting with other participants, in any way and can
	get yourself and your organization into big trouble for
	violating them.  An introduction to those policies and
	links to the details can be found at <link>."

If it seems to be useful, one more sentence to the effect that,
if one has questions after reading through the policies,
contact... could be added, but that might (should) be in
whatever is at the end of the link anyway.

IIR, a very brief statement of that sort is where this "Note
Well" stuff started.  It has gotten bloated as its mission has
crept toward explaining or enumerating the policies and the IETF
has become more policy-laden.

If we actually care about an on-screen version, a list of a
half-dozen or more links just isn't going to do it anyway.  It
won't be displayed long enough to copy it down.  That is
actually a reasonable guideline -- anything that requires
someone to look at material later, rather than being
read/listened to and absorbed, needs to be reduced to NTE one
link or reference or it won't be written down/ remembered.

In a way, we are going to end up with two Note Wells, one for
slide display and quick reminders (like registration forms) and
something else for posting, circulation in writing, and the
target of the reference/link in the first.  I fear that is
inevitable and that we should be adapting to it rather than
pretending we can create a one-screen document that covers
everything.

     john


--On Thursday, April 07, 2016 00:27 -0300 Pete Resnick
<presnick@qti.qualcomm.com> wrote:

> How about if we changed the description of BCP 79:
> 
> BCP 79 (Patent Policy, definitions of "Participation" and
> "Contribution")
>...

> On 6 Apr 2016, at 19:37, Scott Bradner wrote:
> 
>> imo - the 2nd pp is not duplicative - consider that the whole
>> current  note we'll is just covering "what is a
>> contribution" and the question of what
>> "participating"" is has been a  contentious issue for a
>> long time





From nobody Thu Apr  7 05:51:07 2016
Return-Path: <ron.even.tlv@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 8B19612D906; Thu,  7 Apr 2016 05:51:05 -0700 (PDT)
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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 PydWDC9YB9Gd; Thu,  7 Apr 2016 05:51:01 -0700 (PDT)
Received: from mail-qk0-x22d.google.com (mail-qk0-x22d.google.com [IPv6:2607:f8b0:400d:c09::22d]) (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 ECDAE12D8FF; Thu,  7 Apr 2016 05:50:53 -0700 (PDT)
Received: by mail-qk0-x22d.google.com with SMTP id k135so26184901qke.0; Thu, 07 Apr 2016 05:50:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=from:to:cc:subject:date:message-id:mime-version:thread-index :content-language; bh=E2Xb0qrOv9krDOmlVdCdsQOzBhpr0HngCaxrqgCNI10=; b=wn70vHEjpr+CurNEgk8V2DPwyvn0qeNL9/5nJTHjExjFIX78t/VgXFzRVQW29d7myJ NkikWk9KjOxQlhFQZqb46iA5kroDEuWE7KQ8E2gf3dVza/ZA0WtESdXPCf9n3dDn/Tw5 cwvXuH4j3xBsz7Icc9D6XJA/ANINRKjGADDd2Bx3wxJmras6AUHFKKjM+MyCz+AWloYR 4zVBPURjfTav04/5txIushnDdttoenCssJXZk/g14Lkk3opii7wgDWxa9L/O+R45FW+/ ipmBvvvGsAG/aL5kt0X0NQqvyBxT8oTOgU4gjgSNyD2C1mB4GhAhV6/9obXb4/Ze8PgZ Rz/w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:to:cc:subject:date:message-id:mime-version :thread-index:content-language; bh=E2Xb0qrOv9krDOmlVdCdsQOzBhpr0HngCaxrqgCNI10=; b=Fb+s5c5n5tbeufI7H0c9+WZAmWIOH1l9ZSSWh8mXKT1Z/QJdk2pVqAHOSX5oCzG34g 2J8X86foNzSf4HhEOEisdt4xD6VqcG7GnkQHwDw9dW6AKPWBKKz06vLvKsO4UnrTJbjn w0gK4SLTCLJ07Sjrk3b6I+Lw3kotcW2qSWyaDNYAtRJqkZkg0x0vWcWhi5YY9Oj8kw8c RN1nZO+wgGrNDncJ1vPy6vnU4ywVCJau4FkI2w4UxqQbcvJNuaAZVDtLf5vjDeRuuxgb 2hflD2YvmHNYYlibjVHKKig2ojJPBCZ+u9LS9jhG1Qjvgf/Xm/3I1x6fkDk1FiNJpg7F X7mQ==
X-Gm-Message-State: AD7BkJJs1t1qOX1i20M5GupUB/cFnu6UTqgguhXrkKYfyZtaRC7I/WB0DhJNxptNDMhHwA==
X-Received: by 10.55.217.22 with SMTP id u22mr3290334qki.63.1460033452357; Thu, 07 Apr 2016 05:50:52 -0700 (PDT)
Received: from RoniPC ([2001:67c:370:160:e03e:d3ff:6be5:1fb6]) by smtp.gmail.com with ESMTPSA id t36sm3305618qgt.42.2016.04.07.05.50.50 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 07 Apr 2016 05:50:51 -0700 (PDT)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: <draft-ietf-tls-chacha20-poly1305@ietf.org>
Subject: Gen-ART LC review of draft-ietf-tls-chacha20-poly1305-04 - resend
Date: Thu, 7 Apr 2016 15:50:47 +0300
Message-ID: <017f01d190cc$1c912f20$55b38d60$@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0180_01D190E5.41E17460"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AdGQygxSCEkbP4XEQq2U/CrA+ZxzCg==
Content-Language: he
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/rJAbN9aWA2Sv5uA-IU0KPUZse-o>
Cc: gen-art@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: Thu, 07 Apr 2016 12:51:05 -0000

This is a multipart message in MIME format.

------=_NextPart_000_0180_01D190E5.41E17460
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Please resolve these comments along with any other Last Call comments you
may receive.

Document:  draft-ietf-tls-chacha20-poly1305-04

Reviewer: Roni Even

Review Date:2016-3-28

IETF LC End Date: 2016-4-9

IESG Telechat date: 

 

Summary: This draft is almost ready for publication as a standard track
RFC.

 

 

 

Major issues:

I am wondering why this is a standard track document and not informational
since the registration requirements are specification required.  (RFC5246)

 

I am also wondering why this document updates RFC5246 and RFC6347.  Reading
the document it looked to me that the registration document is used also to
endorse this cypher suite by the IETF and if this is the case my view is
that there should be two documents, one Informational for registration and
the will be standard track and update RFC5246 and RFC6347

For Example the following text from section 1 "Therefore, a new stream
cipher to replace RC4 and address all the  previous issues is needed. "
provides what may look as a normative recommendation.

 

 

Minor issues:

 

Nits/editorial comments:

 


------=_NextPart_000_0180_01D190E5.41E17460
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 14 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin-top:0cm;
	margin-right:0cm;
	margin-bottom:10.0pt;
	margin-left:0cm;
	line-height:115%;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:10.5pt;
	font-family:Consolas;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:"Courier New";}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
span.EmailStyle21
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><a =
name=3D"OLE_LINK2"></a><a name=3D"OLE_LINK1"></a>I am the assigned =
Gen-ART reviewer for this draft. For background on Gen-ART, please see =
the FAQ at &lt;<a =
href=3D"http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq" =
target=3D"_blank">http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq=
</a>&gt;.<o:p></o:p></p><p class=3DMsoNormal>Please resolve these =
comments along with any other Last Call comments you may =
receive.<o:p></o:p></p><p class=3DMsoNormal>Document:&nbsp; <span =
style=3D'font-size:10.5pt;line-height:115%;font-family:"Courier =
New"'>draft-ietf-tls-chacha20-poly1305-04</span><span =
style=3D'font-family:"Courier New"'><o:p></o:p></span></p><p =
class=3DMsoNormal>Reviewer: Roni Even<o:p></o:p></p><p =
class=3DMsoNormal>Review Date:2016&#8211;3-28<o:p></o:p></p><p =
class=3DMsoNormal>IETF LC End Date: 2016&#8211;4-9<o:p></o:p></p><p =
class=3DMsoNormal>IESG Telechat date: <o:p></o:p></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Summary: =
This draft is almost ready for publication as a standard track&nbsp; =
RFC.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Major =
issues:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>I am =
wondering why this is a standard track document and not informational =
since the registration requirements are specification required.&nbsp; =
(RFC5246)<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>I am also =
wondering why this document updates RFC5246 and RFC6347. &nbsp;Reading =
the document it looked to me that the registration document is used also =
to endorse this cypher suite by the IETF and if this is the case my view =
is that there should be two documents, one Informational for =
registration and the will be standard track and update RFC5246 and =
RFC6347<o:p></o:p></span></p><pre =
style=3D'page-break-before:always'><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>For =
Example the following text from section 1 &#8220;<span =
style=3D'color:black'>Therefore, a new stream cipher to replace RC4 and =
address all the&nbsp; previous issues is needed. &#8220; &nbsp;provides =
what may look as a normative =
recommendation.<o:p></o:p></span></span></pre><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Minor =
issues:<o:p></o:p></span></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>Nits/editorial comments:<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></body></html>
------=_NextPart_000_0180_01D190E5.41E17460--


From nobody Thu Apr  7 07:16:51 2016
Return-Path: <stewart.bryant@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 042FD12D509; Thu,  7 Apr 2016 07:16:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 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, RCVD_IN_DNSWL_LOW=-0.7, 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 7DN2uHH_dB6G; Thu,  7 Apr 2016 07:16:30 -0700 (PDT)
Received: from mail-wm0-x22f.google.com (mail-wm0-x22f.google.com [IPv6:2a00:1450:400c:c09::22f]) (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 447BE12D11E; Thu,  7 Apr 2016 07:16:21 -0700 (PDT)
Received: by mail-wm0-x22f.google.com with SMTP id f198so27545288wme.0; Thu, 07 Apr 2016 07:16:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding; bh=OGm9FawcCOXJ8KKaaMB/J3+zFMRN4ogtBityMlMeuCU=; b=Q0/oU25aNvx50Zf+xf6WnB/Sg7mgUoT4EOeav/x12u9cxdn5CZSUUJ2v2jocShPzP2 6RsezXeStbtWnVca+7ZI30CvQxkZrO8TptApfcjT9mygumStoXbUbzajtNgrcK2P1NIA //hlcuUAtdynhkybVCvpkFwwmEufSM69Fn63V2FW/ohwr65XYDKs7vZvVaTrkNurCykz iXS7FKwDrlL2obAzawfRl5Nbg7TYNNJsZgleHmJJ9B8hkihnJCFE+15Wz8n7AZam13gd nEJZEsImLLopKpxbWT0Sq2Ag1pZYk3dlEHhVKIbWcw629DKNnpscIVZFPVGmTac8zuhS OfFQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=OGm9FawcCOXJ8KKaaMB/J3+zFMRN4ogtBityMlMeuCU=; b=FBtjj2DxtG856ormxyum6asKA1JWfPZ3DoBA8Vc4LmvH4OAnBn0Dwa7yZSigGJ6+2H 5NU4GXLAgPv5fEo/DzXbkYNeuzXkiDNuiR0RZIe7qJRUNn0qvO7ylHJ6hyaqmrZUhLpQ Iy21vQMcJId4v4upk2/KPRYP2OPT8ZyyWxFSSHelZFJdysrcdTKVCedKqwjeriyFRwHJ 6DHreKx6oX7FtlS9i+Xp47BZZy4/me133j9d8uRrSh5Etbl4UXLeJtetdHnZsMc0MkHX TzRDHLLowf5/4W/9dfIwqR+CuNc3rP9hJ36a5XrjQzFyZjl48SxMIde97KYJKklcAQEr RAOA==
X-Gm-Message-State: AD7BkJKwtngVQs2jZP/ctTqQxdCk4wDGvSHw8J0Jm+UiY+s9v+In2GEmESBEra1YQ2uoyQ==
X-Received: by 10.28.11.131 with SMTP id 125mr30784815wml.58.1460038579755; Thu, 07 Apr 2016 07:16:19 -0700 (PDT)
Received: from [192.168.2.126] (host213-123-124-182.in-addr.btopenworld.com. [213.123.124.182]) by smtp.gmail.com with ESMTPSA id w193sm3506495wmd.0.2016.04.07.07.16.18 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 07 Apr 2016 07:16:18 -0700 (PDT)
Subject: Re: secdir review of draft-ietf-mpls-rfc6374-udp-return-path
To: Sandra Murphy <sandy@tislabs.com>, secdir@ietf.org, The IETF <ietf@ietf.org>, draft-ietf-mpls-rfc6374-udp-return-path.all@tools.ietf.org
References: <07A977A4-FD9E-4669-A8D0-7644131E06AD@tislabs.com> <5673D89F.7090409@gmail.com>
From: Stewart Bryant <stewart.bryant@gmail.com>
Message-ID: <57066BB0.6060600@gmail.com>
Date: Thu, 7 Apr 2016 15:16:16 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.7.0
MIME-Version: 1.0
In-Reply-To: <5673D89F.7090409@gmail.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/PDDbeJ6krdUNz21X_DJBHHfWajI>
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, 07 Apr 2016 14:16:32 -0000

On 18/12/2015 09:57, Stewart Bryant wrote:

Sandy, I have looked at this discussion again. Please see inline:
>
>>
>> Section 4.2
>>
>>
>>   If an Out-of-band response is requested and the Address object or the
>>   URO is missing, the query SHOULD be dropped in the case of a
>>   unidirectional LSP.  If both these TLVs are missing on a
>>   bidirectional LSP, the control code of Response message should set to
>>   0x1C indicating "Error - Invalid Message" ([RFC6374] Section 3.1) and
>>   the response SHOULD be sent over the reverse LSP.  The receipt of
>>   such a mal-formed request SHOULD be notified to the operator through
>>   the management system, taking the normal precautions with respect to
>>   the prevention of overload of the error reporting system.
>>
>> The first sentence says that both the Address object and the URO must
>> be present or the query is dropped - right?  I'm reading this as
>>
>>       (if not(Address) OR not(URO)) then drop.
>>
>> What Address object - there are three - Return, Source and
>> Destination.  I'm betting on Return, but the text should be clear.
>
> That is return address - I will update the text.

Looking at the text again, since we are ONLY talking about systems using 
the
URO, the Address object text fragment is pointless so I have deleted it.

>
>
>>
>> The RFC6374 out-of-band response feature and the "Return Address"
>> object seem to indicate the potential exists in RFC6374 as well.
>> RFC6374's security consideration section does not mention the
>> reflection attack possibility, only the integrity of the return
>> out-of-band path and the possibility of affecting the validity of the
>> measurements.  But even if the assumptions of well-managed, private,
>> service provider networks are met, I believe that the potential and
>> increased need for careful configuration should be mentioned. "Note:
>> the feature can be misused, so take care".  Perhaps a manageability
>> section caution about checking the Return Address or URO to ensure
>> addresses are within the private or service provider network.
>> something?  Or presume all will be well, because this is to be used in
>> well managed private and service provider networks?
> I will look at adding some text, although the assumption is that
> MPLS networks are well managed, and there are many other ways
> they would break if they were not.
>

This text is only about the URO case. The only residual text on the DA obj
is in the section that is to be deleted.

- Stewart


From nobody Thu Apr  7 08:15:17 2016
Return-Path: <ldaigle@thinkingcat.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 0BCED12D68C for <ietf@ietfa.amsl.com>; Thu,  7 Apr 2016 08:15:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.491
X-Spam-Level: 
X-Spam-Status: No, score=-2.491 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001, T_DKIM_INVALID=0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=neutral reason="invalid (public key: not available)" header.d=thinkingcat.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 WV-5dlRTTx3J for <ietf@ietfa.amsl.com>; Thu,  7 Apr 2016 08:15:11 -0700 (PDT)
Received: from homiemail-a54.g.dreamhost.com (sub4.mail.dreamhost.com [69.163.253.135]) (using TLSv1.1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 608C112D964 for <ietf@ietf.org>; Thu,  7 Apr 2016 08:02:46 -0700 (PDT)
Received: from homiemail-a54.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a54.g.dreamhost.com (Postfix) with ESMTP id 2B7A740133013; Thu,  7 Apr 2016 08:02:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=thinkingcat.com; h=from:to :subject:date:message-id:mime-version:content-type :content-transfer-encoding; s=thinkingcat.com; bh=M7xIvpe3WouExY M63vjwfBCY0GQ=; b=jR7OxyWFRL3H4AgNnJPp2lvsuyAq80VDjYUK3/ge4WaR4k vHs3VWqmfvxgmIUjke2WNZXPdC1PLOjCA3lLXCtkJY8/tfuPk11DPbhBh0eKP976 rtEm+FBLeOOh/JV/G7trcScz3xGE7R4PfVYDmSRiF3TWgcceGQd6azozwyFFs=
Received: from [31.133.140.167] (dhcp-8ca7.meeting.ietf.org [31.133.140.167]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: leslie@oceanpurl.net) by homiemail-a54.g.dreamhost.com (Postfix) with ESMTPSA id 6A85C400F8A33; Thu,  7 Apr 2016 08:02:31 -0700 (PDT)
From: "Leslie Daigle" <ldaigle@thinkingcat.com>
To: "IETF discussion list" <ietf@ietf.org>
Subject: An update on IETF 100 planning
Date: Thu, 07 Apr 2016 11:02:09 -0400
Message-ID: <3364A782-59B7-4E2A-903F-A3969A245326@thinkingcat.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
X-Mailer: MailMate (1.9.4r5234)
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/hKwBYOwPkE6VTA4mxxf00NTLLF0>
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, 07 Apr 2016 15:15:17 -0000

At Wednesday=E2=80=99s plenary meeting, we were pleased to announce that=20
contracts are finalized and the IETF 100 meeting is set to take place in=20
Singapore.

As a first comment from the floor, an issue was identified:   Singapore=20
has laws that discriminate against LGBTQ people, which were raised as a=20
concern by some members of our community.

The IAOC and its Meetings Committee were unaware of these laws when the=20
meeting location was selected.

At this point, there are 2 separate issues to be addressed:  1/=20
reviewing the current committed plan for IETF 100  and 2/ reviewing our=20
meeting planning procedures to ensure that we have input at appropriate=20
points to ensure issues are identified and addressed before contracts=20
are signed and announcements made.

Dealing with IETF 100 is the first order of business.  The IAOC is=20
gathering information about the situation =E2=80=94 including the full co=
st of=20
canceling existing contracts, so that the IETF community can have a=20
fuller picture from which to provide guidance for our next steps.

More as we have it.

Leslie.
IAOC Chair.

--=20

-------------------------------------------------------------------
Leslie Daigle
Principal, ThinkingCat Enterprises LLC
ldaigle@thinkingcat.com
-------------------------------------------------------------------


From nobody Thu Apr  7 08:19:13 2016
Return-Path: <dhc@dcrocker.net>
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 4641612D54E for <ietf@ietfa.amsl.com>; Thu,  7 Apr 2016 08:19:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] 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 9RNPg_9HcK0Y for <ietf@ietfa.amsl.com>; Thu,  7 Apr 2016 08:19:09 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B103D12D899 for <ietf@ietf.org>; Thu,  7 Apr 2016 08:07:43 -0700 (PDT)
Received: from [192.168.1.168] (76-218-10-206.lightspeed.sntcca.sbcglobal.net [76.218.10.206]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id u37F7gF5004400 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Thu, 7 Apr 2016 08:07:42 -0700
Subject: Re: "We did not know" is not a good excuse
To: adrian@olddog.co.uk
References: <09ff01d1905c$f15d4e70$d417eb50$@olddog.co.uk> <5705C39E.30807@dcrocker.net> <0a5801d19086$79f40e30$6ddc2a90$@olddog.co.uk>
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
Message-ID: <570677BC.9000900@dcrocker.net>
Date: Thu, 7 Apr 2016 08:07:40 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2
MIME-Version: 1.0
In-Reply-To: <0a5801d19086$79f40e30$6ddc2a90$@olddog.co.uk>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Thu, 07 Apr 2016 08:07:43 -0700 (PDT)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/FVm4Q-8JOEBMo3lgXxw0N07trNo>
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: dcrocker@bbiw.net
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, 07 Apr 2016 15:19:11 -0000

On 4/6/2016 9:32 PM, Adrian Farrel wrote:
> It may be true that the community could provide a list of vetoed and approved
> locations for the Meetings Committee to work with. That is a possible approach.
> Another approach might be for the Meetings Committee to suggest some venues and
> see what the community feels (this has happened before with a poll on some
> venues that Ray sent to the community).


A practical issue is that announcing a venue before there is a contract 
in place for the meeting site impairs our ability to negotiate the 
contract.  And I'll suggest that this is not an issue that one should 
try to 'game', such as by trying to obscure the choice by floating 
various venue possibilities or otherwise hoping that we haven't signaled 
the choice to a specific city/hotel.

Rather, the way to deal with the choice of acceptable/unacceptable 
countries or cities is for the IETF community to develop lists 
reflecting the range of choices.

The IETF's established set of regions is Eastern/Southeastern Asia, 
North America, Europe.  For each of these, the total list of countries 
is relatively small, so that a priori consideration and assessment by 
the IETF community ought to be feasible.

(Other regions fall into the asterisk realm of 1:1:1:* and are already 
subject to prior discussion with the IETF community.)

d/
-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net


From nobody Thu Apr  7 08:34:43 2016
Return-Path: <jari.arkko@piuha.net>
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 102A312D0CA for <ietf@ietfa.amsl.com>; Thu,  7 Apr 2016 08:34:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] 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 zujukRZl0z30 for <ietf@ietfa.amsl.com>; Thu,  7 Apr 2016 08:34:40 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [IPv6:2a00:1d50:2::130]) by ietfa.amsl.com (Postfix) with ESMTP id BBD5C12D195 for <ietf@ietf.org>; Thu,  7 Apr 2016 08:31:24 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id ED24F2CCBF; Thu,  7 Apr 2016 18:31:23 +0300 (EEST) (envelope-from jari.arkko@piuha.net)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PyD3cC4BvorZ; Thu,  7 Apr 2016 18:31:23 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id A966C2CC95; Thu,  7 Apr 2016 18:31:22 +0300 (EEST) (envelope-from jari.arkko@piuha.net)
From: Jari Arkko <jari.arkko@piuha.net>
X-Pgp-Agent: GPGMail 2.5.2
Content-Type: multipart/signed; boundary="Apple-Mail=_EFEF6A6C-B6BC-44C4-854C-09820332102B"; protocol="application/pgp-signature"; micalg=pgp-sha512
Subject: Concerns about Singapore
Date: Thu, 7 Apr 2016 12:31:20 -0300
Message-Id: <0D914666-C3D4-4CCE-AD5E-4E5B34EA1A73@piuha.net>
To: Ted Hardie <ted.ietf@gmail.com>
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/PfpZwOKfasK97Dxf5_GRq4yk6YQ>
Cc: IETF <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, 07 Apr 2016 15:34:42 -0000

--Apple-Mail=_EFEF6A6C-B6BC-44C4-854C-09820332102B
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252


Ted,

As you=92ve seen from Leslie=92s message, the IAOC has taken very =
seriously the concerns you expressed in the plenary about Singapore.

I think we all thought we were sensitive to these types of issues, but =
clearly we weren=92t. Sorry.

I know that I am personally still in the education phase about the =
situation. But I wanted to follow-up with two points from an IETF =
perspective. First, the ability of our participants to enter our =
meetings without concerns is of crucial importance for us. And second, =
as the IAOC determines in more detail what our options are, I wanted to =
say that we want to communicate that assessment to the IETF community =
and work with the community to determine what the best path forward with =
IETF #100 is.

In addition, the longer term process about explicit documentation of =
community=92s wishes regarding the meetings selection process and =
requirements is already in progress. The MTGVENUE BOF will be meeting =
today Thursday at 16:20 in Pacifico A. Everybody, please contribute to =
that.

Jari Arkko, IETF Chair


--Apple-Mail=_EFEF6A6C-B6BC-44C4-854C-09820332102B
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQIcBAEBCgAGBQJXBn1IAAoJEM80gCTQU46q/RwP/2xqksI/LQ5hS1BBjMZ4uB7m
4AuB4i3f5bkCXdDZYitcYnlpgQ3gLB4MkxDgPmkykBYoARHTUFAuvOGF6EUL0TvF
zo9nSAt3ero25XgpDM6/UyfAz0cPx+LiPmcUHJrZC8+zvM+QlSC+pD/XHIsnDnhC
tT/o1lhQJTkknuJm/guRApwSbxjKLCRNd8VAS+psDkpR2G0/pBaKWo0aGzqQ2mwZ
X7ajbK50owluoz5j7vHZOiNofOq4qyOzkCZGSTH8V1CqF37fEI+63YPkw/eoUH+I
3Pir/UXIJh5cF5bWEKj68eJpELawEMcpmiRmlzKNUlQAULLz6PumjFPtbIRWZRmY
hR1pqz4r82NmyxPb13uevCT5m8gWRQr3+j/7ni/4+JO7ez7kI8+/9+ZVy8dc0JBx
olLaj0uMuvfPmsMmyu+TJyp0e/OtCzvUT6hPbUGYPPfKutSnSbobNzTihHM2e5dY
jSs9J5sHIfXAZmW6QOPOZ0ZkyL36WS+pUWGW6b9lqNOoh/oN8jSO/eci/84hJV0R
dOYzO2wSv50JhVrZ+qdS7tK0FEvD2C5W2dIAofu/ZQRnDPfeLODyjzsw3OCpZmSB
bVa2EiLsPPsD05ROECj5QcvQ6YyLTJkbdJVrMqHuqYu2MeIKppaxuPydKImMX85V
XSEiKutcbnJn6WpJ76tw
=kQVn
-----END PGP SIGNATURE-----

--Apple-Mail=_EFEF6A6C-B6BC-44C4-854C-09820332102B--


From nobody Thu Apr  7 08:39:12 2016
Return-Path: <mellon@fugue.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 A9E7612D0B8 for <ietf@ietfa.amsl.com>; Thu,  7 Apr 2016 08:39:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.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 5T30fEPE_3lA for <ietf@ietfa.amsl.com>; Thu,  7 Apr 2016 08:39:08 -0700 (PDT)
Received: from mail-lb0-x230.google.com (mail-lb0-x230.google.com [IPv6:2a00:1450:4010:c04::230]) (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 E208B12D19A for <ietf@ietf.org>; Thu,  7 Apr 2016 08:24:19 -0700 (PDT)
Received: by mail-lb0-x230.google.com with SMTP id bk9so24988170lbc.3 for <ietf@ietf.org>; Thu, 07 Apr 2016 08:24:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=emkljwQEwAs9MNQIuxKjZcuZpjDh3xuojuk8YSy6YtI=; b=2E6LaidVbGKUpnHNqSP/8mQRgZ/GCkykAu96Dd4TImdATcTfwUQUpo+QbbzdVk78b1 H3fN6/J/0LDqY8lgpnBbf1wjpYha+4z5xcCqi8WCwBTt63z0xlG5Lnkqy8zdNgJwt3q0 pnSsv+fok7mNp3MdQjcC8N3h6zXC1Qsuj1Y/K2By67+ybQc78FqyBL7irdw7oClayrQk NAwazcFcNsH0sYZ0+MoxEICf+QpM13AOUxF1skvVCuKK3BlcPgTKJfgWmPXtoPwqCFrd VGpIKBvqfg+D4Lq2jAvO5ulw5FeNgGZcnYs39wXgL1AeM9FDIilO7MG9D05L2MoKrOcn 76xg==
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=emkljwQEwAs9MNQIuxKjZcuZpjDh3xuojuk8YSy6YtI=; b=PCFal5rlPMwyVUTggx3Z6nGv1vv6b9grRJKE8nMagkULwM/EFhDbS0dU7PTFWLJEnp VCypChdp4Kvn8JWj909j58H8WfXicL+tbFFO5VEL2TmNQPPTC4t1zDDykg+41tGDHLlA UMd/bJbnnrSJcOdfrydXaNICCGxB3zRrvZ8mZVWU9iLX1edK6YwgnYyRB77R+nlfMrc6 OB1sbww6RYyN3whsJDT/oxQGGVRSs0hsdpme0fjSkDxjKsT0gkiDxKqKOdpNm3ZaNKQl 0uKR5TMtTJXX7UVJSX8QcDDmGxmxCopNoZmLnnlkZmgntm/9Ri7YOIwu2bfS14SLXqjw d5kg==
X-Gm-Message-State: AD7BkJLh68b3Pz9T8+S7jOcteshSCy6LZRd5Dz8AFVQueBhTQzhAaCLtPuMs8moR4MXBb4Bo9fN98rjk1OpGLw==
X-Received: by 10.112.13.8 with SMTP id d8mr1624563lbc.110.1460042657917; Thu, 07 Apr 2016 08:24:17 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.25.40.136 with HTTP; Thu, 7 Apr 2016 08:23:38 -0700 (PDT)
X-Originating-IP: [2001:67c:370:136:ec62:80b3:91d7:df8a]
In-Reply-To: <570677BC.9000900@dcrocker.net>
References: <09ff01d1905c$f15d4e70$d417eb50$@olddog.co.uk> <5705C39E.30807@dcrocker.net> <0a5801d19086$79f40e30$6ddc2a90$@olddog.co.uk> <570677BC.9000900@dcrocker.net>
From: Ted Lemon <mellon@fugue.com>
Date: Thu, 7 Apr 2016 12:23:38 -0300
Message-ID: <CAPt1N1=21nqO2ctfKgdDHK_xmJohsLCBAP4z8Tu_XrDH4DUPoA@mail.gmail.com>
Subject: Re: "We did not know" is not a good excuse
To: Dave Crocker <dcrocker@bbiw.net>
Content-Type: multipart/alternative; boundary=001a11c3b44efb8443052fe6abb8
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/g2Kj7meBU7Vaq2QtI1Tj-qysZo0>
Cc: 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, 07 Apr 2016 15:39:10 -0000

--001a11c3b44efb8443052fe6abb8
Content-Type: text/plain; charset=UTF-8

Dave, how would it complicate the negotiation process to simply say "we are
considering the following cities for future IETFs: does anybody know of an
issue that they want to raise with any of these?"   We don't have to say
when, or how definite.   It's hard to see how this would cause
problems--can you explain?

I'm not objecting to just making an exhaustive list; I just am not
convinced that it would really make any difference, particularly since
things change.   E.g., I suspect that the IETF that was scheduled for
Charlotte, NC, is no longer in the offing... :}

--001a11c3b44efb8443052fe6abb8
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Dave, how would it complicate the negotiation process to s=
imply say &quot;we are considering the following cities for future IETFs: d=
oes anybody know of an issue that they want to raise with any of these?&quo=
t; =C2=A0 We don&#39;t have to say when, or how definite. =C2=A0 It&#39;s h=
ard to see how this would cause problems--can you explain?<div><br></div><d=
iv>I&#39;m not objecting to just making an exhaustive list; I just am not c=
onvinced that it would really make any difference, particularly since thing=
s change. =C2=A0 E.g., I suspect that the IETF that was scheduled for Charl=
otte, NC, is no longer in the offing... :}</div></div>

--001a11c3b44efb8443052fe6abb8--


From nobody Thu Apr  7 09:30:52 2016
Return-Path: <stewart.bryant@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 665D012D139 for <ietf@ietfa.amsl.com>; Thu,  7 Apr 2016 09:30:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 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, RCVD_IN_DNSWL_LOW=-0.7, 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 dy56W0Y6T9Ph for <ietf@ietfa.amsl.com>; Thu,  7 Apr 2016 09:30:48 -0700 (PDT)
Received: from mail-wm0-x243.google.com (mail-wm0-x243.google.com [IPv6:2a00:1450:400c:c09::243]) (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 099ED12D1ED for <ietf@ietf.org>; Thu,  7 Apr 2016 09:30:46 -0700 (PDT)
Received: by mail-wm0-x243.google.com with SMTP id l6so5663189wml.3 for <ietf@ietf.org>; Thu, 07 Apr 2016 09:30:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=C4HGF0F6/B4bh1WoIFIOcTKi/qDpgqJg0BTzRRRJIO4=; b=vy5S8wi51hBEDLmZVo8j71bWk/6jrFsgGaoAW6kteFjifyjFt9N1LUPpR8r8kChND8 Tdzd/Zd06V5rBMjn4ngN7vCNEr5QzV1noz30DQYx8xHeaQgZgbzQ5G3rLqaywMHvsFBm 72DGKHhS7PzijiQCTpzMmCPtNL6zq2mQH++ZF7VIbk+q3B6fmctm4mQJvczeDO8cGnJk dPJaOuswpDErcsTnA8ZFveeeWgHjb+h/5XwIuIDFMdlf/AFOkriyN1usS3TF2JyfVesP cWjM1H9Oy4wcOYEFUQgDjO3hiWf6HT6vqXedBY8hfxE7IMPUAVniVLPLQ4mpFuTLHbS1 seUQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=C4HGF0F6/B4bh1WoIFIOcTKi/qDpgqJg0BTzRRRJIO4=; b=lOP06EkVIQokQ6TvpRB9zZa685vlK25lqVWTv4nnvVKiwG9r+cG0X17wJpaEC9Roc6 SYXhi74PXy0X7YhnF+wf0+xoJnKxJyUiKKpjZOtecDdboukR+HA1Yf5fcyYB5X4JLNsC PyjNzQ9Zj1eG6LJ/YrBY79s5SXgAgvOQvSRuBFJgNBnXqXYpdu7jNzoIue+/sSuimC9h +A7/nuNMLTrQ7SGTnR8N23iIdlrRL/kqfbkJGjVsKeKF/O94XK0C7q9uqVgzlUHqFel3 DKUVKBKkS0QXAVOS7zFa3kFm3BkTr8GrjtIdsU0sByP4N1lVW7jvPtLrZJgBLw8CpmkZ fszg==
X-Gm-Message-State: AD7BkJL0sS71w2wn6MmWFrmSnvJZSYhVMBeDPzGC7DPfRo3yp46s3yJiWedrLwVEyDtjTg==
X-Received: by 10.28.176.133 with SMTP id z127mr32117651wme.66.1460046644603;  Thu, 07 Apr 2016 09:30:44 -0700 (PDT)
Received: from [192.168.2.113] (host213-123-124-182.in-addr.btopenworld.com. [213.123.124.182]) by smtp.gmail.com with ESMTPSA id b135sm4296955wmb.10.2016.04.07.09.30.43 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 07 Apr 2016 09:30:43 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (1.0)
Subject: Re: "We did not know" is not a good excuse
From: Stewart Bryant <stewart.bryant@gmail.com>
X-Mailer: iPhone Mail (13E238)
In-Reply-To: <570677BC.9000900@dcrocker.net>
Date: Thu, 7 Apr 2016 17:30:42 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <203EFD6F-183D-4C92-9006-3BFE24BB525B@gmail.com>
References: <09ff01d1905c$f15d4e70$d417eb50$@olddog.co.uk> <5705C39E.30807@dcrocker.net> <0a5801d19086$79f40e30$6ddc2a90$@olddog.co.uk> <570677BC.9000900@dcrocker.net>
To: dcrocker@bbiw.net
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/oJIvvY2fojaWF5zOLq_h4HLYqMY>
Cc: 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, 07 Apr 2016 16:30:50 -0000

> On 7 Apr 2016, at 16:07, Dave Crocker <dhc@dcrocker.net> wrote:
>=20
>  And I'll suggest that this is not an issue that one should try to 'game',=
 such as by trying to obscure the choice by floating various venue possibili=
ties or otherwise hoping that we haven't signaled the choice to a specific c=
ity/hotel.

Such a process served us well in getting feedback on members of the I* until=
 recently.

I would have thought that it would pick up problems of the type that was ide=
ntified last night without compromising our commercial position too badly.

Stewart=


From nobody Thu Apr  7 09:34:53 2016
Return-Path: <john-ietf@jck.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 C124212D1D7 for <ietf@ietfa.amsl.com>; Thu,  7 Apr 2016 09:34:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] 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 xk0n4AeJgHxx for <ietf@ietfa.amsl.com>; Thu,  7 Apr 2016 09:34:35 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E6A8D12D11D for <ietf@ietf.org>; Thu,  7 Apr 2016 09:34:32 -0700 (PDT)
Received: from [198.252.137.10] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1aoCt0-00078J-S6; Thu, 07 Apr 2016 12:34:26 -0400
Date: Thu, 07 Apr 2016 12:34:21 -0400
From: John C Klensin <john-ietf@jck.com>
To: Ted Lemon <mellon@fugue.com>, Dave Crocker <dcrocker@bbiw.net>
Subject: Re: "We did not know" is not a good excuse
Message-ID: <BCF66170D3B05FCAAD0EAE51@JcK-HP8200.jck.com>
In-Reply-To: <CAPt1N1=21nqO2ctfKgdDHK_xmJohsLCBAP4z8Tu_XrDH4DUPoA@mail.gmail.com>
References: <09ff01d1905c$f15d4e70$d417eb50$@olddog.co.uk> <5705C39E.30807@dcrocker.net> <0a5801d19086$79f40e30$6ddc2a90$@olddog.co.uk> <570677BC.9000900@dcrocker.net> <CAPt1N1=21nqO2ctfKgdDHK_xmJohsLCBAP4z8Tu_XrDH4DUPoA@mail.gmail.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/E3h5gsbZijPCW3_c6I1Ba6jG9-M>
Cc: 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, 07 Apr 2016 16:34:46 -0000

--On Thursday, April 07, 2016 12:23 -0300 Ted Lemon
<mellon@fugue.com> wrote:

> Dave, how would it complicate the negotiation process to
> simply say "we are considering the following cities for future
> IETFs: does anybody know of an issue that they want to raise
> with any of these?"   We don't have to say when, or how
> definite.   It's hard to see how this would cause
> problems--can you explain?

Exactly.  Singapore may be a special case because it is a
"city=country" one but, other than Luxembourg, there are
relatively few others of those that are likely candidates for
discussion.   I'm not suggesting supplying padding, but I assume
that there are multiple places that might be considered in any
of those regions (and even countries between them) and
identifying a list of them and asking the question Ted suggests
should not be an issue.

I also can't imagine why doing that would get in the way of
negotiations, at least unless the process has turned into "let's
go to Timbuktu, now let's start negotiating with hotels there".
Independent of other issues with that city, I'd suggest that, if
the model comes down to that, we'd be in bad trouble for other
reasons, so I assume it hasn't.   It would be better if cities
were eliminated before a call for proposals was issued but, even
if one were issued that included several cities, I don't see
huge problems if some candidate venues were eliminated because
we decided their cities or countries were off-limits: it would
really be no different from a solicitation and contracting
standpoint than eliminating one because our preliminary
investigations concluded that adequate connectivity was
impossible for that city.

>...

    john




From nobody Thu Apr  7 09:38:03 2016
Return-Path: <dhc@dcrocker.net>
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 8993F12D167 for <ietf@ietfa.amsl.com>; Thu,  7 Apr 2016 09:38:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] 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 ZqQMd71dFe-1 for <ietf@ietfa.amsl.com>; Thu,  7 Apr 2016 09:38:01 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B318E12D11D for <ietf@ietf.org>; Thu,  7 Apr 2016 09:38:00 -0700 (PDT)
Received: from [192.168.1.168] (76-218-10-206.lightspeed.sntcca.sbcglobal.net [76.218.10.206]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id u37GbxY1008478 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Thu, 7 Apr 2016 09:37:59 -0700
Subject: Re: "We did not know" is not a good excuse
To: Stewart Bryant <stewart.bryant@gmail.com>
References: <09ff01d1905c$f15d4e70$d417eb50$@olddog.co.uk> <5705C39E.30807@dcrocker.net> <0a5801d19086$79f40e30$6ddc2a90$@olddog.co.uk> <570677BC.9000900@dcrocker.net> <203EFD6F-183D-4C92-9006-3BFE24BB525B@gmail.com>
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
Message-ID: <57068CE5.1040709@dcrocker.net>
Date: Thu, 7 Apr 2016 09:37:57 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2
MIME-Version: 1.0
In-Reply-To: <203EFD6F-183D-4C92-9006-3BFE24BB525B@gmail.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Thu, 07 Apr 2016 09:37:59 -0700 (PDT)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/C3UWr5i4_-ZuVFh2AH0vPvUNMVE>
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: dcrocker@bbiw.net
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, 07 Apr 2016 16:38:02 -0000

On 4/7/2016 9:30 AM, Stewart Bryant wrote:
>> On 7 Apr 2016, at 16:07, Dave Crocker <dhc@dcrocker.net> wrote:
>>   And I'll suggest that this is not an issue that one should try to 'game', such as by trying to obscure the choice by floating various venue possibilities or otherwise hoping that we haven't signaled the choice to a specific city/hotel.
>
> Such a process served us well in getting feedback on members of the I* until recently.
>
> I would have thought that it would pick up problems of the type that was identified last night without compromising our commercial position too badly.


Stewart,  if you are referring to the gaming that used to be done, when 
soliciting information about nomcom candidates, by padding the list of 
names with various non-candidates, in my experience on several nomcoms, 
no it did not work well at all.

d/


-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net


From nobody Thu Apr  7 10:12:08 2016
Return-Path: <adam@nostrum.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 5049C12D0FE for <ietf@ietfa.amsl.com>; Thu,  7 Apr 2016 10:12:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] 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 K07-xcnmePv1 for <ietf@ietfa.amsl.com>; Thu,  7 Apr 2016 10:12:05 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (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 6CC1A12D1B8 for <ietf@ietf.org>; Thu,  7 Apr 2016 10:12:05 -0700 (PDT)
Received: from dhcp-a0da.meeting.ietf.org (dhcp-a0da.meeting.ietf.org [31.133.160.218]) (authenticated bits=0) by nostrum.com (8.15.2/8.14.9) with ESMTPSA id u37HC1nu071074 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Thu, 7 Apr 2016 12:12:03 -0500 (CDT) (envelope-from adam@nostrum.com)
Subject: Re: Concerns about Singapore
To: Jari Arkko <jari.arkko@piuha.net>, Ted Hardie <ted.ietf@gmail.com>
References: <0D914666-C3D4-4CCE-AD5E-4E5B34EA1A73@piuha.net>
From: Adam Roach <adam@nostrum.com>
Message-ID: <570694E1.90509@nostrum.com>
Date: Thu, 7 Apr 2016 14:12:01 -0300
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:38.0) Gecko/20100101 Thunderbird/38.7.1
MIME-Version: 1.0
In-Reply-To: <0D914666-C3D4-4CCE-AD5E-4E5B34EA1A73@piuha.net>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/3e3yrxL_Rgo3HeYC_29PflVLEdA>
Cc: IETF <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, 07 Apr 2016 17:12:07 -0000

On 4/7/16 12:31, Jari Arkko wrote:
> In addition, the longer term process about explicit documentation of communityâ€™s wishes regarding the meetings selection process and requirements is already in progress. The MTGVENUE BOF will be meeting today Thursday at 16:20 in Pacifico A. Everybody, please contribute to that.

Indeed, venue selection appears to be something people care deeply 
about, for a variety of reasons. I will point out that the current draft 
being discussed later today 
(https://tools.ietf.org/html/draft-baker-mtgvenue-iaoc-venue-selection-process-01) 
does squarely address the issue under discussion in section 3.1, under 
the section marked "Inclusiveness." Selection of venues that exclude 
participation based on sexual orientation is explicitly proscribed by 
name in the existing proposal.

/a


From nobody Thu Apr  7 10:15:51 2016
Return-Path: <adrian@olddog.co.uk>
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 714DF12D516 for <ietf@ietfa.amsl.com>; Thu,  7 Apr 2016 10:15:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.721
X-Spam-Level: 
X-Spam-Status: No, score=-0.721 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01] 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 ZLrrfc6S6aMS for <ietf@ietfa.amsl.com>; Thu,  7 Apr 2016 10:15:47 -0700 (PDT)
Received: from asmtp2.iomartmail.com (asmtp2.iomartmail.com [62.128.201.249]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 14BA612D1DE for <ietf@ietf.org>; Thu,  7 Apr 2016 10:15:46 -0700 (PDT)
Received: from asmtp2.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp2.iomartmail.com (8.13.8/8.13.8) with ESMTP id u37HFcYh029260; Thu, 7 Apr 2016 18:15:38 +0100
Received: from 950129200 (dhcp-b176.meeting.ietf.org [31.133.177.118]) (authenticated bits=0) by asmtp2.iomartmail.com (8.13.8/8.13.8) with ESMTP id u37HFAJ1029103 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO); Thu, 7 Apr 2016 18:15:16 +0100
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: <dcrocker@bbiw.net>
References: <09ff01d1905c$f15d4e70$d417eb50$@olddog.co.uk> <5705C39E.30807@dcrocker.net> <0a5801d19086$79f40e30$6ddc2a90$@olddog.co.uk> <570677BC.9000900@dcrocker.net>
In-Reply-To: <570677BC.9000900@dcrocker.net>
Subject: RE: "We did not know" is not a good excuse
Date: Thu, 7 Apr 2016 18:15:07 +0100
Message-ID: <00b001d190f1$196e6b80$4c4b4280$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQGMmqG5z30WLKo9QlhbwnFG9R5TNAJCqcjaAkyoPygCMVXiDZ/SpdtQ
Content-Language: en-gb
X-TM-AS-MML: disable
X-TM-AS-Product-Ver: IMSS-7.1.0.1679-8.0.0.1202-22246.000
X-TM-AS-Result: No-2.051-10.0-31-10
X-imss-scan-details: No-2.051-10.0-31-10
X-TMASE-MatchedRID: 5+1rHnqhWUQ4HKI/yaqRm4zb2GR6Ttd3H8cjAOna5KtaW2Ktn+I8/hEQ uhnt7JpjH9NHCwoYsb3mrA+Lc6CI37Cul2XVVRIPtrSss6fsjJbE7bRw0ZDPdX7wEfYmi+rXo8W MkQWv6iV95l0nVeyiuBQF+BLVItD4C24oEZ6SpSmb4wHqRpnaDloBejTqxk8YF0sdaHTHb4fbzt 1k6zXI/irSN06TrpHLsoyfxaAS8/fWim5wZMkGaf0tasqNnrFIO/4ugxoBFPDBenvS2vbcD+Q/b JqlQQ/copZ51QxAj3fx+wL7E8WTG+w2n3R9PgSOc5bjXhMesgI=
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/oJd_zbC4HMMPReNBTByntpg-Lxo>
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: adrian@olddog.co.uk
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, 07 Apr 2016 17:15:49 -0000

> A practical issue is that announcing a venue before there is a contract
> in place for the meeting site impairs our ability to negotiate the
> contract.

We are engineering.
But I will break a rule and go there.

I don't see that saying "we are considering Hong Kong, Singapore, and Manila"
reduces our ability to negotiate in Singapore. Maybe it even strengthens it.

But there we go. Looks like sometimes we may need to pay a price to get what we
want. The loss on cancelation may be greater than the loss on negotiation.

Adrian


From nobody Thu Apr  7 10:30:01 2016
Return-Path: <fred@cisco.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 36F3512D0BD for <ietf@ietfa.amsl.com>; Thu,  7 Apr 2016 10:29:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -114.531
X-Spam-Level: 
X-Spam-Status: No, score=-114.531 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 g0zoD-Sb-AXq for <ietf@ietfa.amsl.com>; Thu,  7 Apr 2016 10:29:56 -0700 (PDT)
Received: from alln-iport-2.cisco.com (alln-iport-2.cisco.com [173.37.142.89]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9D55612D531 for <ietf@ietf.org>; Thu,  7 Apr 2016 10:29:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1557; q=dns/txt; s=iport; t=1460050193; x=1461259793; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=IPzBMgueXhodR3qUiGuaDtUQIHSl3HTDhWDVccK1tIE=; b=E6jzkWppIyrErLQSfCukmuci2x4++zQ/XXVEOJ+mTSBOoJfAAenUNl4U SSuJgtJ+oNKLZpp/vxW9IKatsFNk5tW+iNGMjP+LErzFJ32NRBz/MHZdC 6s3wUcKASJhJiUtYaZk9aF6DHxgrB93BoC/5ssAqv+2S5y6k+LrbESADS I=;
X-Files: signature.asc : 833
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0C6AgDumAZX/5tdJa1cgzeBUAa6Uw6Bc?= =?us-ascii?q?4YNAoFFOBQBAQEBAQEBZRwLhEEBAQEDAXkFCwIBCBguMiUBAQQOBQ6IEQjBawE?= =?us-ascii?q?BAQEBAQEBAQEBAQEBAQEBAQEBAQ0IiBaCVodqgisFmAQBgyOBZokCgVEBjTyPI?= =?us-ascii?q?wEeAUOCBBmBSmyHdX4BAQE?=
X-IronPort-AV: E=Sophos;i="5.24,449,1454976000";  d="asc'?scan'208";a="257202277"
Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by alln-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 07 Apr 2016 17:29:49 +0000
Received: from XCH-RCD-013.cisco.com (xch-rcd-013.cisco.com [173.37.102.23]) by rcdn-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id u37HTneV016979 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 7 Apr 2016 17:29:49 GMT
Received: from xch-rcd-013.cisco.com (173.37.102.23) by XCH-RCD-013.cisco.com (173.37.102.23) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Thu, 7 Apr 2016 12:29:48 -0500
Received: from xch-rcd-013.cisco.com ([173.37.102.23]) by XCH-RCD-013.cisco.com ([173.37.102.23]) with mapi id 15.00.1104.009; Thu, 7 Apr 2016 12:29:48 -0500
From: "Fred Baker (fred)" <fred@cisco.com>
To: "adrian@olddog.co.uk" <adrian@olddog.co.uk>
Subject: Re: "We did not know" is not a good excuse
Thread-Topic: "We did not know" is not a good excuse
Thread-Index: AdGQXOo2K6ee2QfjSBaO8Tfj5mxHYwAwEVyA
Date: Thu, 7 Apr 2016 17:29:48 +0000
Message-ID: <3C0A584D-843E-4FE4-B09D-AD237E974E83@cisco.com>
References: <09ff01d1905c$f15d4e70$d417eb50$@olddog.co.uk>
In-Reply-To: <09ff01d1905c$f15d4e70$d417eb50$@olddog.co.uk>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-mailer: Apple Mail (2.3124)
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.24.35.191]
Content-Type: multipart/signed; boundary="Apple-Mail=_7E2C5CDB-B692-4630-BF89-A2153261B8EF"; protocol="application/pgp-signature"; micalg=pgp-sha1
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/w5uUALppTlshnwNVAsmXOBBUlVY>
Cc: "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: Thu, 07 Apr 2016 17:29:58 -0000

--Apple-Mail=_7E2C5CDB-B692-4630-BF89-A2153261B8EF
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=us-ascii


> On Apr 6, 2016, at 8:34 PM, adrian@olddog.co.uk wrote:
> 
> How do we move on so:
> - this problem stops being a problem for IETF 100
> - this problem does not recur

That would be a very relevant conversation on mtgvenue@ietf.org.

--Apple-Mail=_7E2C5CDB-B692-4630-BF89-A2153261B8EF
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="signature.asc"
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iQIVAwUBVwaZX0ayAOS/EQ8MAQKdCRAAnpJMc9NQaJS0hquONWVN8vT4tVxktMV5
iPWqbUliz+yuqcqR5Rh6v/gHwH7gamjh8r1sUBezNaHLeYyqYAVGqHGwwHtOIzKD
/yyaExiDTFyhT/QAW2rIiXR0zSxcwJY/3eyTMI6y+yyOg1Aoz7a5ihHOcvdOcgIl
jyhbF8SvZw41FG5OE4iwtqoL/hrGOtn/C6pJ+Uu9cyFshqhwZiGiX9zxECIO9VjV
B32vXYyMitOS07AvLp5SkzsfoqBuiQFP+RFWQRFyhfA/f05RCCCho5oExkoeu4Xo
Nnf6g9lhtXva9MlQpRV85QCuCD0mH9KkQorIr0KbL0ZQcWOeyHuLr5J4Tl5iIP2r
ol4pFST41+JwIm8onDy4Gnf5pdOHHFZEC0hcshzXOf8wiSOtAp8eYAfsXXJQIwLq
dkbDa/ApsCGSRtz/lRbdZ3aE7qmZN8V7cBFoA+Nhb9beFxnr8ParSKRs2oMAhqoO
4x6WIXF7rJ83ivx4c5Bcji3lcCdgja0qkBZWh0Uq5EoVZG3iAw1Zz01gQnR+LmoH
v6/yFW32/CaPkPho9iHO6qA1WFdTJ6Gnkddjg+KEyBLueY/gHPQtTCI/izJ8vZTV
hh7uajPVlGHh0zX2AWPVxc8Og7yiAF4iFp/AgHPe/OOgBODTfQuHPrv1WguLQaQ6
w9DEK4ifoog=
=Z1WB
-----END PGP SIGNATURE-----

--Apple-Mail=_7E2C5CDB-B692-4630-BF89-A2153261B8EF--


From nobody Thu Apr  7 10:35:39 2016
Return-Path: <stefan.winter@restena.lu>
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 4B7E212D1A3 for <ietf@ietfa.amsl.com>; Thu,  7 Apr 2016 10:35:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.909
X-Spam-Level: 
X-Spam-Status: No, score=-1.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, T_RP_MATCHES_RCVD=-0.01] 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 O-tPwx1QKx65 for <ietf@ietfa.amsl.com>; Thu,  7 Apr 2016 10:35:35 -0700 (PDT)
Received: from smtp.restena.lu (legolas.restena.lu [158.64.1.34]) (using TLSv1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C16D612D586 for <ietf@ietf.org>; Thu,  7 Apr 2016 10:35:25 -0700 (PDT)
Received: from viper.local (unknown [IPv6:2001:a18:1:40::2]) by smtp.restena.lu (Postfix) with ESMTPSA id 9F275BB744; Thu,  7 Apr 2016 19:35:21 +0200 (CEST)
Subject: Re: "We did not know" is not a good excuse
To: John C Klensin <john-ietf@jck.com>, Ted Lemon <mellon@fugue.com>, Dave Crocker <dcrocker@bbiw.net>
References: <09ff01d1905c$f15d4e70$d417eb50$@olddog.co.uk> <5705C39E.30807@dcrocker.net> <0a5801d19086$79f40e30$6ddc2a90$@olddog.co.uk> <570677BC.9000900@dcrocker.net> <CAPt1N1=21nqO2ctfKgdDHK_xmJohsLCBAP4z8Tu_XrDH4DUPoA@mail.gmail.com> <BCF66170D3B05FCAAD0EAE51@JcK-HP8200.jck.com>
From: Stefan Winter <stefan.winter@restena.lu>
Openpgp: id=AD3091F3AB24E05F4F722C03C0DE6A358A39DC66
Message-ID: <57069A56.2020303@restena.lu>
Date: Thu, 7 Apr 2016 14:35:18 -0300
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:38.0) Gecko/20100101 Thunderbird/38.7.2
MIME-Version: 1.0
In-Reply-To: <BCF66170D3B05FCAAD0EAE51@JcK-HP8200.jck.com>
Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="Drnp6mFdCtDoL1EAMXSUDEW46q1LepaBc"
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/dz-1-bIu0tkrUOPy_2HiH6ESk7E>
Cc: 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, 07 Apr 2016 17:35:38 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--Drnp6mFdCtDoL1EAMXSUDEW46q1LepaBc
Content-Type: multipart/mixed; boundary="cH73FPrjQ645AgMdvNCst7IgNi2J0hbll"
From: Stefan Winter <stefan.winter@restena.lu>
To: John C Klensin <john-ietf@jck.com>, Ted Lemon <mellon@fugue.com>,
 Dave Crocker <dcrocker@bbiw.net>
Cc: ietf@ietf.org
Message-ID: <57069A56.2020303@restena.lu>
Subject: Re: "We did not know" is not a good excuse
References: <09ff01d1905c$f15d4e70$d417eb50$@olddog.co.uk>
 <5705C39E.30807@dcrocker.net> <0a5801d19086$79f40e30$6ddc2a90$@olddog.co.uk>
 <570677BC.9000900@dcrocker.net>
 <CAPt1N1=21nqO2ctfKgdDHK_xmJohsLCBAP4z8Tu_XrDH4DUPoA@mail.gmail.com>
 <BCF66170D3B05FCAAD0EAE51@JcK-HP8200.jck.com>
In-Reply-To: <BCF66170D3B05FCAAD0EAE51@JcK-HP8200.jck.com>

--cH73FPrjQ645AgMdvNCst7IgNi2J0hbll
Content-Type: multipart/mixed;
 boundary="------------050003080807060202010900"

This is a multi-part message in MIME format.
--------------050003080807060202010900
Content-Type: multipart/alternative;
 boundary="------------030006080603040504070101"


--------------030006080603040504070101
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

Hi,

>> Dave, how would it complicate the negotiation process to
>> simply say "we are considering the following cities for future
>> IETFs: does anybody know of an issue that they want to raise
>> with any of these?"   We don't have to say when, or how
>> definite.   It's hard to see how this would cause
>> problems--can you explain?
> Exactly.  Singapore may be a special case because it is a
> "city=3Dcountry" one but, other than Luxembourg, there are
> relatively few others of those that are likely candidates for
> discussion.

Not that it adds particularly much to the discussion at hand, but would
you please note that the country of Luxembourg has 2,586.4 km^2 /
998 sq mi surface, while the city of Luxembourg is just one out of
multiple cities in the country.

If you are looking for area surface matches between a country and its
(only) city, you may rather want to look in the general direction of the
country Monacco and its city Monte Carlo (different name, same thing -
how's that for a special case!).

(Now waiting for someone from Monacco to correct me about my ignorance
of throwing both into one bowl)

Greetings,

Stefan Winter

>    I'm not suggesting supplying padding, but I assume
> that there are multiple places that might be considered in any
> of those regions (and even countries between them) and
> identifying a list of them and asking the question Ted suggests
> should not be an issue.
>
> I also can't imagine why doing that would get in the way of
> negotiations, at least unless the process has turned into "let's
> go to Timbuktu, now let's start negotiating with hotels there".
> Independent of other issues with that city, I'd suggest that, if
> the model comes down to that, we'd be in bad trouble for other
> reasons, so I assume it hasn't.   It would be better if cities
> were eliminated before a call for proposals was issued but, even
> if one were issued that included several cities, I don't see
> huge problems if some candidate venues were eliminated because
> we decided their cities or countries were off-limits: it would
> really be no different from a solicitation and contracting
> standpoint than eliminating one because our preliminary
> investigations concluded that adequate connectivity was
> impossible for that city.
>
>> ...
>     john
>
>
>


--------------030006080603040504070101
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

<html>
  <head>
    <meta content=3D"text/html; charset=3Dwindows-1252"
      http-equiv=3D"Content-Type">
  </head>
  <body bgcolor=3D"#FFFFFF" text=3D"#000000">
    <div class=3D"moz-cite-prefix">Hi,<br>
      <br>
    </div>
    <blockquote cite=3D"mid:BCF66170D3B05FCAAD0EAE51@JcK-HP8200.jck.com"
      type=3D"cite">
      <pre wrap=3D"">
</pre>
      <blockquote type=3D"cite">
        <pre wrap=3D"">Dave, how would it complicate the negotiation proc=
ess to
simply say "we are considering the following cities for future
IETFs: does anybody know of an issue that they want to raise
with any of these?"   We don't have to say when, or how
definite.   It's hard to see how this would cause
problems--can you explain?
</pre>
      </blockquote>
      <pre wrap=3D"">
Exactly.  Singapore may be a special case because it is a
"city=3Dcountry" one but, other than Luxembourg, there are
relatively few others of those that are likely candidates for
discussion.</pre>
    </blockquote>
    <br>
    Not that it adds particularly much to the discussion at hand, but
    would you please note that the country of Luxembourg has
    <meta http-equiv=3D"content-type" content=3D"text/html;
      charset=3Dwindows-1252">
    2,586.4=A0km<sup><small>2</small></sup> /<br>
    998=A0sq=A0mi surface, while the city of Luxembourg is just one out o=
f
    multiple cities in the country.<br>
    <br>
    If you are looking for area surface matches between a country and
    its (only) city, you may rather want to look in the general
    direction of the country Monacco and its city Monte Carlo (different
    name, same thing - how's that for a special case!).<br>
    <br>
    (Now waiting for someone from Monacco to correct me about my
    ignorance of throwing both into one bowl)<br>
    <br>
    Greetings,<br>
    <br>
    Stefan Winter<br>
    <br>
    <blockquote cite=3D"mid:BCF66170D3B05FCAAD0EAE51@JcK-HP8200.jck.com"
      type=3D"cite">
      <pre wrap=3D"">   I'm not suggesting supplying padding, but I assum=
e
that there are multiple places that might be considered in any
of those regions (and even countries between them) and
identifying a list of them and asking the question Ted suggests
should not be an issue.

I also can't imagine why doing that would get in the way of
negotiations, at least unless the process has turned into "let's
go to Timbuktu, now let's start negotiating with hotels there".
Independent of other issues with that city, I'd suggest that, if
the model comes down to that, we'd be in bad trouble for other
reasons, so I assume it hasn't.   It would be better if cities
were eliminated before a call for proposals was issued but, even
if one were issued that included several cities, I don't see
huge problems if some candidate venues were eliminated because
we decided their cities or countries were off-limits: it would
really be no different from a solicitation and contracting
standpoint than eliminating one because our preliminary
investigations concluded that adequate connectivity was
impossible for that city.

</pre>
      <blockquote type=3D"cite">
        <pre wrap=3D"">...
</pre>
      </blockquote>
      <pre wrap=3D"">
    john



</pre>
    </blockquote>
    <br>
  </body>
</html>

--------------030006080603040504070101--

--------------050003080807060202010900
Content-Type: application/pgp-keys;
 name="0x8A39DC66.asc"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
 filename="0x8A39DC66.asc"

-----BEGIN PGP PUBLIC KEY BLOCK-----
Version: GnuPG/MacGPG2 v2

mQINBFIplEwBEADTSz+DS8nio+RSvfSLLfaOnCGi1nqpn8Pb1laVUyEvnAAzZ5je
miS88GxfiDH6hUGlWzcaW0hCfUHGiohr485adbjxRksPngWgAt/1bRxpifsW3zOb
Fjgog01WWQV5Sihlwc4zr8zvYbFA5BJZ6YdkR9C5J015riv5OS30WTjA65SSXgYr
b7zJWPwmegTFwE093uBFvC39waz3xYpVu5j87nO6w2MVQt/8sY2/2BFPEq+xfOaj
l18UEwc7w8SCgnZdlVNcmEK4UBvJuwS/1lsR2JeQa8Gu1EDxC7PRgMgNXsDSWnnB
e9aVmfG54+6ILe1QH2dwk9sPBQT5w2+vjijrb3Dv9ur+1kN+TNU2XE436jVpnnY/
3OsLdix30STQn4Q/XOm7YoVMeDwwviefilRxzK0dXA+wKj92T68Od82CFxuZqPAg
BCVmWfQM91iK9piqFK+QP+R3vF6+NGDBdwbe68iVKs0v5L8XmbxBQndjpmo+lo2a
smBR2TAIfZHaKdgtBw13u3GPVVKlg/Mpko8ki9JOSem2aFyi3kQEVKptWgXT3POl
97DWJzsR5VyKz6GOx9kJAEISRyLZwm0wqh8+9LCza5oeIKW381lzq1b9x30vOh8C
BSQQJ+cG9ko0yPHAj7Suw2TmPXx1qMctmE6Ahq82ZW30SljdZby8WQuR2wARAQAB
tDxTdGVmYW4gV2ludGVyIChSRVNURU5BIGtleSAyMDEzKykgPHN0ZWZhbi53aW50
ZXJAcmVzdGVuYS5sdT6JAjkEEwECACMFAlIplEwCGwMHCwkIBwMCAQYVCAIJCgsE
FgIDAQIeAQIXgAAKCRDA3mo1ijncZj7/D/99hVS+mJr8dSPCaDaUFFxBiT2eI1Lo
R8VKEerTCRw5BsdL6pN2eRJZ9NmsqWo1ynWVHEzO91bNZ+oZGgyoNohcBAI7p+r0
qUTzkyqwdZO4kMm0pqKoM9xkP3tf2mjGujKjOz4Y7S7wnz2ZFokeUsecoRVJF/++
/qHnmeWLn44J1HUKLHYCjMu+QXGOgGXgz024jQ5eUrnPwzNp0Z90AFVHlWC+bymt
y/ToIUUCQqS5Ff0jzdWLd8U695OG9iGvjBQT1LdEjsfbAwuKV5UcnpxNqUpUwKa5
9hdX5/2cMZP07FI1UXwnBlxa8rJfdb13FLjSKX4vUUHedYUZMjMPgcwl1a+zGE22
lHiSQWgP8QLA/W3BLsi22ERCEPZBfexOeOtaWIItDIz18fIaQoMDoRPshzar0JI2
CzLYsyeKySAtYJEHFVoLmMvhkwzBmgqA/BEswUA67CfCr1jFHRXdpmWM7YkyAmMa
9q6LwquWKS5+MXlUXe/3oZUcgpw/T9Uuy3Jo3RdS7B3jFcWaVr6KsO/A9u1gr/aY
n5M+iJTQSj4vzqtkQaJTpSspRZoKa66HZt3IwSYiDiYZqtM83ynuj9kjnZzGfnuT
aNIi996q6Mptr33mOzIE1wmMqnJYwTr3EcNtf483q/qrJwh5ES8Q9xY7aat/ZcSl
8fKubW4TlfVr8YhGBBARAgAGBQJSKZUGAAoJEPo5vdH/HhVmYTgAn24eoqO/O98o
vNpt08Uab/+/tmYKAJ9kjXm9Njz5h33efzeelZUa484rr7kCDQRSKZRMARAAvBPp
n7FQq7LQ5glohtbL6XIEo1U4X67S0TzUYieENSWSVYuWYIhCBldmWdmH8Bpj/qHe
qdon7v+SLtR4WngzMR9toupKcFfHnbP9kpazTSB2ySHxXWGX1gJOpPXdCcg9iveK
BHEsDn00ThTcPsvtXpnnzET16pXIvOXO0bxTmVZ4INIF1SWgvYma/g8kBbgXLpkj
8tOywBqFiiYPEZlDeCxDHiMgUDh6olda9K/0TZFTdMPUgjKuubfAeaDNCOrVt4Rj
mFOaRLikcZocmgJhm3z/j25x7/mnNu+0di1H/S67YGQJ+pqCFInzIXDx7aRW2+JC
iqsY2X3xOPWZZzjyis5SNnfOcPH3gt2hYz1fy+thsBGf4NgCN01JRqIJ2/MOQCgU
dwh+9l8xqaJvCkUHM4hVh4W62MAe1u7UEqQbvvNEqxM5034vcvlE+/LRkrDCspw+
2YJ9QyroLerVRwW5DVleP8Ifi8VB3yD80nqXYs9aqRy0BkDNIQ43ERhESMt8dJqr
NkxgC6pemZrhNwyDh+hy2kPNGQh/iBpdKuH1o3E24TIZoV2v3YHvzob7aAYHddE/
PofAXhJW7I9mAs+HdWDmnI8ckuPDFpFH+Y/BFGvEXgcnJAJ1wEvf+4LuiIi0MHjR
4EWFn9vvoFDAIqD10h3FSd3D59HGtdSsNn4XaCsAEQEAAYkCHwQYAQIACQUCUimU
TAIbDAAKCRDA3mo1ijncZhBtEACL036ddjc5pFoYIdoUY1vT8SMXJNquewCnL1qu
DADzqDZFU5GNlQEy10krSfBwlTb9ahTtE0JFrOdZwUZtoa1Pgfr8nU6KOgrXPHbN
jS/9dyc5CwGVVIpOavIm2CsMVDJ9LCF/NT+u/t1k6eGfHhPVl3dUQyDa/lzc1chK
UIVQYQkFmr0A/iXP+29lFCaI+IeyU0bSdZhezDwUROn5vEx+fiPZyHDShCb+BxJv
/o2LQp9JHenCiSbO+ioRZdxgbWfoKBuXOfmSStqMWXas/gZ5vS3xq72LNtKPRxgp
jX3P8Zml1XDqpcBau7eK75VKE0Yd06YxnUIsbcEzInUc3uzW/u0DFpXYkMJb0XIv
JyUt5yYPKfV13N8kSkPi5pLxm8yuftXMzfgeFMR7nafY3glTVj/TxElzg6xeZNqf
C2ZjIbBtZg9ylHU8u8wwB+dX282crs0R3N9A064C71/cXlBqcjzjlKH2NUIWGxr+
od3TXFIFjszSU3NgMPKrWNhFLLwS81MpbkOe73s6aDhS8RDyNucoxtKXriLR+4Xi
u4+pyj5ukYP1JqpB3ZobY/XZgCnJMye+7xeTpIDJ1LPORxM3NNAElyb26lxAK2P+
km+EpI0Zzz6rNSCfg5jYQ474+e/GBgaSG4MlaPoZ+XAfN46u1Xjjv1/AkkA4IA6m
5zP5og=3D=3D
=3D3NUt
-----END PGP PUBLIC KEY BLOCK-----

--------------050003080807060202010900--

--cH73FPrjQ645AgMdvNCst7IgNi2J0hbll--

--Drnp6mFdCtDoL1EAMXSUDEW46q1LepaBc
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2

iQIcBAEBCgAGBQJXBppXAAoJEMDeajWKOdxm/e8P/0+DN0grYn4pn0xDUUYeMsxC
hnUqYEZsf2p4XvU2m7a0XBqLHhn0Jh8ARlCvQZOShYfaRM9LqiGyVenr31VA3ner
/cGAw7bEyZigwFV9nBKg+jp6Vzw6BW9lIIHM4GhQ3EX8GsJK9+i4xlmd6dSOpSly
FEQtjbFkR3nLSfHqLajIN+BL+L2p4h2QT8u+MCZOrhYFee3ypox3GBgfnfmV1Iwe
V9IipO4uyVL5xmZc7YGdWkwq0lEFS7ii0l6quz9bHAzogUn2gtPAXKXOLiUkSgiQ
alyWnNDHTM3rhFZsTI/TAsFljxonmP7RTKUd7TttZHz5bzMVd04Bz10N9s1Zxv0V
FHex2J6hEefKYqg/VfVxwbnZIDZ2Kp4TBdMEHBTvz0g9kcHrCvgCgqDISWO8TnEq
hdafELlLY8+FDRsWmVg/yqy6Mz9ex2Oy8zU1GFYiD/LefuBjRod3GYTG54S6PQNa
xuzqO9g4KuuirIJegTpYvPVMUq+tMzvmAhPv83n9zx1j+UUAiu+mazX8UDG2E6Km
eGTem4pfh746MOxWfS62pDsueKkqyNXoBX+nXQwPZH1npphZf18DVEQ9ZN4+TV8W
XQzHLPbmNCDhpdlMHTgGbF3pTza6L+sOlmzwJz1sk3wSVCz3Ggbjym439G6KY1SD
4AvomoYEb4D99Pwr1GAw
=/YSe
-----END PGP SIGNATURE-----

--Drnp6mFdCtDoL1EAMXSUDEW46q1LepaBc--


From nobody Thu Apr  7 10:41:13 2016
Return-Path: <john-ietf@jck.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 D4B5312D5D7 for <ietf@ietfa.amsl.com>; Thu,  7 Apr 2016 10:41:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] 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 vd5IJW_jOx9C for <ietf@ietfa.amsl.com>; Thu,  7 Apr 2016 10:41:11 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5B9D212D59A for <ietf@ietf.org>; Thu,  7 Apr 2016 10:41:11 -0700 (PDT)
Received: from [198.252.137.10] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1aoDvX-0007Sy-6r; Thu, 07 Apr 2016 13:41:07 -0400
Date: Thu, 07 Apr 2016 13:41:02 -0400
From: John C Klensin <john-ietf@jck.com>
To: Stefan Winter <stefan.winter@restena.lu>, Ted Lemon <mellon@fugue.com>, Dave Crocker <dcrocker@bbiw.net>
Subject: Re: "We did not know" is not a good excuse
Message-ID: <DAC6168972FB4273973AC87E@JcK-HP8200.jck.com>
In-Reply-To: <57069A56.2020303@restena.lu>
References: <09ff01d1905c$f15d4e70$d417eb50$@olddog.co.uk> <5705C39E.30807@dcrocker.net> <0a5801d19086$79f40e30$6ddc2a90$@olddog.co.uk> <570677BC.9000900@dcrocker.net> <CAPt1N1=21nqO2ctfKgdDHK_xmJohsLCBAP4z8Tu_XrDH4DUPoA@mail.gmail.com> <BCF66170D3B05FCAAD0EAE51@JcK-HP8200.jck.com> <57069A56.2020303@restena.lu>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/jZRQ1ksFRsuuHLk1aNTnLSxtaMw>
Cc: 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, 07 Apr 2016 17:41:13 -0000

Stafan,

My apologies... bad example.   I was, however, thinking less of
the city area to country area ratio than about the "probably
only one plausible city in the country to hold an IETF-sized
meeting" issue.    I should have been more clear about that or
chosen a better example (or, more likely, both).  

     john


--On Thursday, April 07, 2016 14:35 -0300 Stefan Winter
<stefan.winter@restena.lu> wrote:

> Hi,
> 
>>> Dave, how would it complicate the negotiation process to
>>> simply say "we are considering the following cities for
>>> future IETFs: does anybody know of an issue that they want
>>> to raise with any of these?"   We don't have to say when, or
>>> how definite.   It's hard to see how this would cause
>>> problems--can you explain?
>> Exactly.  Singapore may be a special case because it is a
>> "city=country" one but, other than Luxembourg, there are
>> relatively few others of those that are likely candidates for
>> discussion.
> 
> Not that it adds particularly much to the discussion at hand,
> but would you please note that the country of Luxembourg has
> 2,586.4 km^2 / 998 sq mi surface, while the city of Luxembourg
> is just one out of multiple cities in the country.
> 
> If you are looking for area surface matches between a country
> and its (only) city, you may rather want to look in the
> general direction of the country Monacco and its city Monte
> Carlo (different name, same thing - how's that for a special
> case!).
> 
> (Now waiting for someone from Monacco to correct me about my
> ignorance of throwing both into one bowl)





From nobody Thu Apr  7 11:11:50 2016
Return-Path: <superuser@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 2BB1812D67B for <ietf@ietfa.amsl.com>; Thu,  7 Apr 2016 11:11:48 -0700 (PDT)
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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 rM8LL8wvXo5F for <ietf@ietfa.amsl.com>; Thu,  7 Apr 2016 11:11:46 -0700 (PDT)
Received: from mail-vk0-x22b.google.com (mail-vk0-x22b.google.com [IPv6:2607:f8b0:400c:c05::22b]) (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 1D17912D64D for <ietf@ietf.org>; Thu,  7 Apr 2016 11:11:46 -0700 (PDT)
Received: by mail-vk0-x22b.google.com with SMTP id c4so109674151vkb.3 for <ietf@ietf.org>; Thu, 07 Apr 2016 11:11:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:date:message-id:subject:from:to; bh=0dcCtNBjLo+OTPMNpm4kreoAN1jN2a3pdjPUakL1ik8=; b=rgChj9ZYfQ83IYT7sSsoTODSBwUJpNUDRKZ2YkgbcSyzjQurnpgxWKnXepLMdqPucv UGIe4HdIyR7cVqMhAk51bALE+6cHXaWfuEuIZKxilaHo1v7YCXLyAbkBSkkTChQq6MyF vspLKeeDuvXSMXw6Fjk1Kdzzyw6kXXajcXtKr3HfbrkaZqln7d3OyKpqP2ZJDeoBG+pA K6j7nsRiykjRpahZnarhBYgJCvBhMzaleWPQeBB7/2bfxng+uTmA7DONFfc1IQ2GOMxM hEn25MHAFBiQHYRvgbUWsE3Ip29owhInJBmhrIHY0/ehESOM+EObsWwcBozBAwlgDcXS AiGw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:date:message-id:subject:from:to; bh=0dcCtNBjLo+OTPMNpm4kreoAN1jN2a3pdjPUakL1ik8=; b=LnEurxYtjzOkxoBAAUU4YfJMnl6C/DfICx+2KSRkP9k0YrvXdFtOcHIpnvEvku0nKx pAq9I7b5Pz4OZ5IlYcjJpI4odPXJkgyLBTMlvGMFn6Do3V6xfBaNLZp8d5gKgbEFQPmk XLAtn8Uy/+k8mZyl5ruCn6FK0cL6czNxKlXG40Nx71yQabbG772dmRoiqkOMnAgidBcH hvOBTX1xA0KyVOuFaQ2Es1FdVCVoq2j0Fm20FlR+iTjYHP9Wh+9w+J8YFDx7b2titgSA VcOGrrNF/R+iBLLtzFwXzlSZF8NwtAeU+FSHUiReWSxlJa+7PZZZyFoiKfZTE73OUsei o+XA==
X-Gm-Message-State: AD7BkJL/fWU7zmP4TaXHLLCsNsyq4j/JKk+8Jbg96uFOpI4ASTkPSGDADRUrRoXFObmW4o5o8JPUqUCw6lbzyQ==
MIME-Version: 1.0
X-Received: by 10.31.52.147 with SMTP id b141mr2117961vka.82.1460052705192; Thu, 07 Apr 2016 11:11:45 -0700 (PDT)
Received: by 10.103.43.5 with HTTP; Thu, 7 Apr 2016 11:11:45 -0700 (PDT)
Date: Thu, 7 Apr 2016 15:11:45 -0300
Message-ID: <CAL0qLwY0FuDp5=RMFEhUMtkK=XNDxX2dogvVY7+OSy88jrrvOQ@mail.gmail.com>
Subject: Qualifying for NomCom
From: "Murray S. Kucherawy" <superuser@gmail.com>
To: ietf <ietf@ietf.org>
Content-Type: multipart/alternative; boundary=001a1143f846d8f947052fe9024d
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/0dAqECeJ9URtDeC97AK_SQrQ34c>
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, 07 Apr 2016 18:11:48 -0000

--001a1143f846d8f947052fe9024d
Content-Type: text/plain; charset=UTF-8

Yes, this again.

I've refreshed RFC7437bis in the datatracker since we're effectively
between active NomCom periods, so now's a good time to take another look at
this.

For those that didn't follow along last time, the big showstopper for this
draft as I have it now had to do with updating the criteria for qualifying
to serve on the NomCom.  The current draft says:

(1) To qualify, one must have attended three of the last five in-person
meetings, as it's been for a long time now.

(2) This is regularly criticized as selecting for attendees with the
support and budget to travel to the meetings, and possibly excludes people
who make substantial or numerous IETF contributions but participate
remotely more than in person.

We made previous attempts on this list to come up with new criteria given
(2) above, but weren't successful at coming to consensus, so I took them
back out, leaving the text that's there now.  The previous thread:
https://mailarchive.ietf.org/arch/msg/ietf/QHwG1KrQDBK9u0wsfALjPSre-pw

I'd like to take another run at this before the next NomCom really gets
going.  One suggestion I was given here at IETF 95 is to come up with some
system that's worth trying, and not over-engineer it to protect against
gaming or other abuses until such time as such abuse is evident.  It might,
for example, be sufficient defense to empower the NomCom Chair or the IETF
Chair (or both) with a "panic button", making them able to declare that
selection criteria will fall back to what we have now if it looks like the
proposed new qualification system is likely to yield an inappropriate set
of selecting NomCom members.

Comments welcome.

-MSK

--001a1143f846d8f947052fe9024d
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div><div><div><div><div><div><div><div>Yes, this again.<b=
r><br></div>I&#39;ve refreshed RFC7437bis in the datatracker since we&#39;r=
e effectively between active NomCom periods, so now&#39;s a good time to ta=
ke another look at this.<br><br></div>For those that didn&#39;t follow alon=
g last time, the big showstopper for this draft as I have it now had to do =
with updating the criteria for qualifying to serve on the NomCom.=C2=A0 The=
 current draft says:<br><br></div>(1) To qualify, one must have attended th=
ree of the last five in-person meetings, as it&#39;s been for a long time n=
ow.<br><br></div>(2) This is regularly criticized as selecting for attendee=
s with the support and budget to travel to the meetings, and possibly exclu=
des people who make substantial or numerous IETF contributions but particip=
ate remotely more than in person.<br><br></div>We made previous attempts on=
 this list to come up with new criteria given (2) above, but weren&#39;t su=
ccessful at coming to consensus, so I took them back out, leaving the text =
that&#39;s there now.=C2=A0 The previous thread:<br><a href=3D"https://mail=
archive.ietf.org/arch/msg/ietf/QHwG1KrQDBK9u0wsfALjPSre-pw">https://mailarc=
hive.ietf.org/arch/msg/ietf/QHwG1KrQDBK9u0wsfALjPSre-pw</a><br><br></div>I&=
#39;d like to take another run at this before the next NomCom really gets g=
oing.=C2=A0 One suggestion I was given here at IETF 95 is to come up with s=
ome system that&#39;s worth trying, and not over-engineer it to protect aga=
inst gaming or other abuses until such time as such abuse is evident.=C2=A0=
 It might, for example, be sufficient defense to empower the NomCom Chair o=
r the IETF Chair (or both) with a &quot;panic button&quot;, making them abl=
e to declare that selection criteria will fall back to what we have now if =
it looks like the proposed new qualification system is likely to yield an i=
nappropriate set of selecting NomCom members.<br><br></div>Comments welcome=
.<br><br></div>-MSK<br></div>

--001a1143f846d8f947052fe9024d--


From nobody Thu Apr  7 11:13:58 2016
Return-Path: <mellon@fugue.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 12A0112D690 for <ietf@ietfa.amsl.com>; Thu,  7 Apr 2016 11:13:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.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 1yJlTKqC3_sL for <ietf@ietfa.amsl.com>; Thu,  7 Apr 2016 11:13:54 -0700 (PDT)
Received: from mail-lb0-x22e.google.com (mail-lb0-x22e.google.com [IPv6:2a00:1450:4010:c04::22e]) (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 9D43A12D68E for <ietf@ietf.org>; Thu,  7 Apr 2016 11:13:53 -0700 (PDT)
Received: by mail-lb0-x22e.google.com with SMTP id bk9so27919483lbc.3 for <ietf@ietf.org>; Thu, 07 Apr 2016 11:13:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=nLGNS8BDD7P/u82PF8xbRuNuqGcxgdGQF7Fx0/BAy04=; b=bZV8ZG88Y9qHPBhJHw7uCr1j7FLcMSG2b8IWBHO305iuAfW2SVnoXI7V7nEpsJ+N0Y H8UMUOJqC5MvKJXG11e9Sr5L4p/D7KJ47PTv2i9bwxMlt2BQ3+zcrLnY39UK5aOq8bFI ZSNY8wUKq1+NGyD4jhAxawA/OSciV6xI+8KX0wMjUDOb17ldSXCo7fycPNdlJ8h9dUsI vVhDF6Oot+0UGUduu0rU8/URdMUcsP7R/AKcfDMKc63T0jQpvtpP10rN9uCdvb5Sj1wu jnXKwmTORSnVBrtyX0GZyUOd/U81g2jHM5Un5mbwcWI6JV0zgYPJsqdDrsA0zv0hyFhQ wcAw==
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=nLGNS8BDD7P/u82PF8xbRuNuqGcxgdGQF7Fx0/BAy04=; b=WHyfNrk/XBAe2av70TONrwXeHl2EruemYwIEzuIDszP7yB+aM5VfosOZJnNfjEc4BJ zopC+okOeLp6+s7/VV2Pi7LvhnbmGuIiLKH8A/ok3ebB42xnZkcZYFAlIGwvrYUibxFS WJITwHXiXj+IuHJCRkqWI74Os2nPGlK9BNIPzOablXR55t+oCl7ggPvuWwJqgEwf2kdV MuCMx0yqoUeQ3TDtoNfJyddQNCufAujWCxDn5hqNCuSgr+ORVxX46h3CiqnQUZvQjfSh Yr2KYT63rHlMonlaXPciraUHT6ETMo0t3dQ73T2XC0CKsQRPjxiKgBbA8KzW6IfJsSpk ANFQ==
X-Gm-Message-State: AD7BkJIRtOgtbVo9VPwDCXjqFWEvCqTLYAMqLVqGeuIoTXL5cPoo+vxGY6TgkUY3Xqk3hC94ZS47Eca6U8txzw==
X-Received: by 10.112.159.70 with SMTP id xa6mr1896826lbb.87.1460052831874; Thu, 07 Apr 2016 11:13:51 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.25.40.136 with HTTP; Thu, 7 Apr 2016 11:13:12 -0700 (PDT)
X-Originating-IP: [2001:67c:370:176:ec62:80b3:91d7:df8a]
In-Reply-To: <CAL0qLwY0FuDp5=RMFEhUMtkK=XNDxX2dogvVY7+OSy88jrrvOQ@mail.gmail.com>
References: <CAL0qLwY0FuDp5=RMFEhUMtkK=XNDxX2dogvVY7+OSy88jrrvOQ@mail.gmail.com>
From: Ted Lemon <mellon@fugue.com>
Date: Thu, 7 Apr 2016 15:13:12 -0300
Message-ID: <CAPt1N1=SYpo-CiHoc07Ukb04Kb1LGV2=BPPyRLUsaqyLM9Hbwg@mail.gmail.com>
Subject: Re: Qualifying for NomCom
To: "Murray S. Kucherawy" <superuser@gmail.com>
Content-Type: multipart/alternative; boundary=001a11c2860865c500052fe90a6a
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/hVCV-JIQY8DB_csF0P5jOCEgtPM>
Cc: ietf <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, 07 Apr 2016 18:13:56 -0000

--001a11c2860865c500052fe90a6a
Content-Type: text/plain; charset=UTF-8

What do you mean by "coming to consensus?"

On Thu, Apr 7, 2016 at 3:11 PM, Murray S. Kucherawy <superuser@gmail.com>
wrote:

> Yes, this again.
>
> I've refreshed RFC7437bis in the datatracker since we're effectively
> between active NomCom periods, so now's a good time to take another look at
> this.
>
> For those that didn't follow along last time, the big showstopper for this
> draft as I have it now had to do with updating the criteria for qualifying
> to serve on the NomCom.  The current draft says:
>
> (1) To qualify, one must have attended three of the last five in-person
> meetings, as it's been for a long time now.
>
> (2) This is regularly criticized as selecting for attendees with the
> support and budget to travel to the meetings, and possibly excludes people
> who make substantial or numerous IETF contributions but participate
> remotely more than in person.
>
> We made previous attempts on this list to come up with new criteria given
> (2) above, but weren't successful at coming to consensus, so I took them
> back out, leaving the text that's there now.  The previous thread:
> https://mailarchive.ietf.org/arch/msg/ietf/QHwG1KrQDBK9u0wsfALjPSre-pw
>
> I'd like to take another run at this before the next NomCom really gets
> going.  One suggestion I was given here at IETF 95 is to come up with some
> system that's worth trying, and not over-engineer it to protect against
> gaming or other abuses until such time as such abuse is evident.  It might,
> for example, be sufficient defense to empower the NomCom Chair or the IETF
> Chair (or both) with a "panic button", making them able to declare that
> selection criteria will fall back to what we have now if it looks like the
> proposed new qualification system is likely to yield an inappropriate set
> of selecting NomCom members.
>
> Comments welcome.
>
> -MSK
>

--001a11c2860865c500052fe90a6a
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">What do you mean by &quot;coming to consensus?&quot;</div>=
<div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Thu, Apr 7, 20=
16 at 3:11 PM, Murray S. Kucherawy <span dir=3D"ltr">&lt;<a href=3D"mailto:=
superuser@gmail.com" target=3D"_blank">superuser@gmail.com</a>&gt;</span> w=
rote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;borde=
r-left:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div><div><div><di=
v><div><div><div><div>Yes, this again.<br><br></div>I&#39;ve refreshed RFC7=
437bis in the datatracker since we&#39;re effectively between active NomCom=
 periods, so now&#39;s a good time to take another look at this.<br><br></d=
iv>For those that didn&#39;t follow along last time, the big showstopper fo=
r this draft as I have it now had to do with updating the criteria for qual=
ifying to serve on the NomCom.=C2=A0 The current draft says:<br><br></div>(=
1) To qualify, one must have attended three of the last five in-person meet=
ings, as it&#39;s been for a long time now.<br><br></div>(2) This is regula=
rly criticized as selecting for attendees with the support and budget to tr=
avel to the meetings, and possibly excludes people who make substantial or =
numerous IETF contributions but participate remotely more than in person.<b=
r><br></div>We made previous attempts on this list to come up with new crit=
eria given (2) above, but weren&#39;t successful at coming to consensus, so=
 I took them back out, leaving the text that&#39;s there now.=C2=A0 The pre=
vious thread:<br><a href=3D"https://mailarchive.ietf.org/arch/msg/ietf/QHwG=
1KrQDBK9u0wsfALjPSre-pw" target=3D"_blank">https://mailarchive.ietf.org/arc=
h/msg/ietf/QHwG1KrQDBK9u0wsfALjPSre-pw</a><br><br></div>I&#39;d like to tak=
e another run at this before the next NomCom really gets going.=C2=A0 One s=
uggestion I was given here at IETF 95 is to come up with some system that&#=
39;s worth trying, and not over-engineer it to protect against gaming or ot=
her abuses until such time as such abuse is evident.=C2=A0 It might, for ex=
ample, be sufficient defense to empower the NomCom Chair or the IETF Chair =
(or both) with a &quot;panic button&quot;, making them able to declare that=
 selection criteria will fall back to what we have now if it looks like the=
 proposed new qualification system is likely to yield an inappropriate set =
of selecting NomCom members.<br><br></div>Comments welcome.<span class=3D"H=
OEnZb"><font color=3D"#888888"><br><br></font></span></div><span class=3D"H=
OEnZb"><font color=3D"#888888">-MSK<br></font></span></div>
</blockquote></div><br></div>

--001a11c2860865c500052fe90a6a--


From nobody Thu Apr  7 11:18:02 2016
Return-Path: <superuser@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 5BC7612D667 for <ietf@ietfa.amsl.com>; Thu,  7 Apr 2016 11:18:01 -0700 (PDT)
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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 z9C4Bgen7poI for <ietf@ietfa.amsl.com>; Thu,  7 Apr 2016 11:17:58 -0700 (PDT)
Received: from mail-vk0-x22c.google.com (mail-vk0-x22c.google.com [IPv6:2607:f8b0:400c:c05::22c]) (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 D970812D52E for <ietf@ietf.org>; Thu,  7 Apr 2016 11:17:57 -0700 (PDT)
Received: by mail-vk0-x22c.google.com with SMTP id c4so109890549vkb.3 for <ietf@ietf.org>; Thu, 07 Apr 2016 11:17:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=l/Ts2imiNyaxJ0i8JUm+21iqSGPVT9aJLXmRHe3n/9M=; b=KWP2c2iUUxLroux0tOXoCQZHODpmHVldVFpI1BuCltvTecLX1CzNp9gib7hje1lqwY 4MtUAZ1f69A/l/WwTyX2v2gITrGSN0TJdLz7JxWKdb0pQByJ0IFs6lKkZRKsdD9G0r+K OpgI849Dnb0SPigF5w5JMgA+KiSffIgRyeSI1Qyg2TkYEg+CkJOLmSj2mGeMxLJtf0qQ 0B6Ta9/Z6zU60Z4Rg4tkTjmHZ6Gjvo/39bvalT53ynBPTEvxXtjeiY3CHWSUFxwhroEM ZHLJHmA/2WWwwYon2ohXYUgsSOpOyuLGd4D3k41YBSr/cwufjHaSYqQsPjG+iTZa34m4 os3w==
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:date :message-id:subject:from:to:cc; bh=l/Ts2imiNyaxJ0i8JUm+21iqSGPVT9aJLXmRHe3n/9M=; b=ImQEkegDzpCOQ7UwHO87d9k4oSYq1f3PMBrNWytbIfIc+HTdgvxzb4JJKlMXhUVAv0 6/Ua84fW9QhcDJmHS2fgHL8IkadgD12j0QQxgoOl2d+GviwJ/f1hCUwayGRNfJ47v+hN sFH+WQZWm2TimI5u4eEb03fmY+aAMvNpgI/UcWiWfhRp8epOYOuFb9wEfHc91BuqZsrP jegUq3fanl1NpenBkAU66FY83pV7ZrLGwm3MfWXNpORcgxdpSzVZOMF0koETGymx/TQm FM7U6ugBUDo/CFbCwsHNdQhE/o0EU8BoeKYsWAvfHUU2TKZC3pGLF9+J8RflZuvhzQ02 69Iw==
X-Gm-Message-State: AD7BkJJSSGKyWcwBmHjlDufKGp3EbX1kV4sa9JjabS+AKElAvDYg5U+NbxbNVMyiwS3SYK8u/1Glqxn+CEpoAA==
MIME-Version: 1.0
X-Received: by 10.31.52.147 with SMTP id b141mr2131286vka.82.1460053077011; Thu, 07 Apr 2016 11:17:57 -0700 (PDT)
Received: by 10.103.43.5 with HTTP; Thu, 7 Apr 2016 11:17:56 -0700 (PDT)
In-Reply-To: <CAPt1N1=SYpo-CiHoc07Ukb04Kb1LGV2=BPPyRLUsaqyLM9Hbwg@mail.gmail.com>
References: <CAL0qLwY0FuDp5=RMFEhUMtkK=XNDxX2dogvVY7+OSy88jrrvOQ@mail.gmail.com> <CAPt1N1=SYpo-CiHoc07Ukb04Kb1LGV2=BPPyRLUsaqyLM9Hbwg@mail.gmail.com>
Date: Thu, 7 Apr 2016 15:17:56 -0300
Message-ID: <CAL0qLwbhYRqw7fXHzYY0=W-CpmeHeDdaZx3z2Qg0cA2aMrmVwg@mail.gmail.com>
Subject: Re: Qualifying for NomCom
From: "Murray S. Kucherawy" <superuser@gmail.com>
To: Ted Lemon <mellon@fugue.com>
Content-Type: multipart/alternative; boundary=001a1143f846023536052fe919f4
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/UpsBrp6vEadVX9aTLxYmp6xDLZ8>
Cc: ietf <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, 07 Apr 2016 18:18:01 -0000

--001a1143f846023536052fe919f4
Content-Type: text/plain; charset=UTF-8

On Thu, Apr 7, 2016 at 3:13 PM, Ted Lemon <mellon@fugue.com> wrote:

> What do you mean by "coming to consensus?"
>

There was no clear agreement on a new set of qualifying criteria, and the
discussion faded out.

-MSK

--001a1143f846023536052fe919f4
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">On Thu, Apr 7, 2016 at 3:13 PM, Ted Lemon <span dir=3D"ltr=
">&lt;<a href=3D"mailto:mellon@fugue.com" target=3D"_blank">mellon@fugue.co=
m</a>&gt;</span> wrote:<br><div class=3D"gmail_extra"><div class=3D"gmail_q=
uote"><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-l=
eft:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr">What do you mean by &=
quot;coming to consensus?&quot;</div></blockquote><div><br></div><div>There=
 was no clear agreement on a new set of qualifying criteria, and the discus=
sion faded out.<br><br></div><div>-MSK <br></div></div></div></div>

--001a1143f846023536052fe919f4--


From nobody Thu Apr  7 11:20:32 2016
Return-Path: <mellon@fugue.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 232DD12D0DA for <ietf@ietfa.amsl.com>; Thu,  7 Apr 2016 11:20:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.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 Chbd-4xYek5J for <ietf@ietfa.amsl.com>; Thu,  7 Apr 2016 11:20:29 -0700 (PDT)
Received: from mail-lb0-x234.google.com (mail-lb0-x234.google.com [IPv6:2a00:1450:4010:c04::234]) (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 1D8E612D655 for <ietf@ietf.org>; Thu,  7 Apr 2016 11:20:24 -0700 (PDT)
Received: by mail-lb0-x234.google.com with SMTP id vo2so55243747lbb.1 for <ietf@ietf.org>; Thu, 07 Apr 2016 11:20:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=GHble0JGMZIEu6aejB+vv2Bhi+hB/tXpKj3bZXRhcec=; b=HEvdnTFlKEP+kT5tG/CwIidGfVWf7Q6YvTI3nujIxWrZrvSpsitfrASsNjbLfLcj6e Hs2Bhhx214arcVp23bIDvqIKQv2Y90WKglx7/T6L2UZQwtjmcWhuc5AyjnNCH62bxZLO Js6MbnZ7gOBOGEnbuZ/kSsTzkWI6d+1Bz7+iWtTYTmMQjgH4bG6DyuJHM/VCf9U2Fd6+ UCNFES9A+D/+cNSychooyEHct/zVEc9vsVojAFiQOL/6Sqg39L4vvdK6ULNhirMlnSCL 2hriBdyTjXqyyZHqeCyxDIWt+/KBn///JmsaPhH7b1Zm6ZmTlgsQWfBdnenEzmYo/uWl EmfA==
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=GHble0JGMZIEu6aejB+vv2Bhi+hB/tXpKj3bZXRhcec=; b=aUa+3M2bfcQ8ctv4X2ho6s0OrWUA0pfz0lQiClA7ZySvrv8VmTPOJiT6L27nb7yG+Z NUrCXlNmMx+Vfr4ufK9kHjgUd9lgSw4K4Fvc9hff6XRXcgCuP+/hv+NSxSico47+yisQ UBUS3emwtzV8b7uTwVJthAvMN7PHRJ5ey0xc3pcBFCgaHHewYXkaj8elQE7Jwn3NjRmS 6S4u7N4PyYVkmnCP85d4uqkARUJTl9Ter7Mkii49J00VsWrG75TXd1CURPq48mAm3Z5/ jf2PITMp6N8FpZTdfrnKQRjJ/8kJUbNL0xhKzx5MqM3dZkLb6FTjkpzTkzeewjjUtP5L ynTA==
X-Gm-Message-State: AD7BkJJu4VnK/TE3DeBi1FUQailTEgzN5F6sEqHEe0NHJsgsd//8TS05baDDYASAANLqIc0v1LZXO8C2IhurSg==
X-Received: by 10.112.161.41 with SMTP id xp9mr1946353lbb.133.1460053222329; Thu, 07 Apr 2016 11:20:22 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.25.40.136 with HTTP; Thu, 7 Apr 2016 11:19:42 -0700 (PDT)
X-Originating-IP: [2001:67c:370:176:ec62:80b3:91d7:df8a]
In-Reply-To: <CAL0qLwbhYRqw7fXHzYY0=W-CpmeHeDdaZx3z2Qg0cA2aMrmVwg@mail.gmail.com>
References: <CAL0qLwY0FuDp5=RMFEhUMtkK=XNDxX2dogvVY7+OSy88jrrvOQ@mail.gmail.com> <CAPt1N1=SYpo-CiHoc07Ukb04Kb1LGV2=BPPyRLUsaqyLM9Hbwg@mail.gmail.com> <CAL0qLwbhYRqw7fXHzYY0=W-CpmeHeDdaZx3z2Qg0cA2aMrmVwg@mail.gmail.com>
From: Ted Lemon <mellon@fugue.com>
Date: Thu, 7 Apr 2016 15:19:42 -0300
Message-ID: <CAPt1N1nqmC7NJyg2M6Na8vUj8T-qObO-1gHFEXZzrobb3oOQhA@mail.gmail.com>
Subject: Re: Qualifying for NomCom
To: "Murray S. Kucherawy" <superuser@gmail.com>
Content-Type: multipart/alternative; boundary=001a11c26b2aabbb5d052fe92128
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/s6clvp9dQru_xkfMq6KSqLjMftg>
Cc: ietf <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, 07 Apr 2016 18:20:31 -0000

--001a11c26b2aabbb5d052fe92128
Content-Type: text/plain; charset=UTF-8

Right.   So that's not what "consensus" means.   Suggest you reread RFC
7282.   It's not normative, but I think it's helpful to reread when you
feel that you have failed to find consensus.   It contains some good advice
about getting to consensus.

On Thu, Apr 7, 2016 at 3:17 PM, Murray S. Kucherawy <superuser@gmail.com>
wrote:

> On Thu, Apr 7, 2016 at 3:13 PM, Ted Lemon <mellon@fugue.com> wrote:
>
>> What do you mean by "coming to consensus?"
>>
>
> There was no clear agreement on a new set of qualifying criteria, and the
> discussion faded out.
>
> -MSK
>

--001a11c26b2aabbb5d052fe92128
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Right. =C2=A0 So that&#39;s not what &quot;consensus&quot;=
 means. =C2=A0 Suggest you reread RFC 7282. =C2=A0 It&#39;s not normative, =
but I think it&#39;s helpful to reread when you feel that you have failed t=
o find consensus. =C2=A0 It contains some good advice about getting to cons=
ensus.</div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Th=
u, Apr 7, 2016 at 3:17 PM, Murray S. Kucherawy <span dir=3D"ltr">&lt;<a hre=
f=3D"mailto:superuser@gmail.com" target=3D"_blank">superuser@gmail.com</a>&=
gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 =
0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr"><span =
class=3D"">On Thu, Apr 7, 2016 at 3:13 PM, Ted Lemon <span dir=3D"ltr">&lt;=
<a href=3D"mailto:mellon@fugue.com" target=3D"_blank">mellon@fugue.com</a>&=
gt;</span> wrote:<br></span><div class=3D"gmail_extra"><div class=3D"gmail_=
quote"><span class=3D""><blockquote class=3D"gmail_quote" style=3D"margin:0=
 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr">Wha=
t do you mean by &quot;coming to consensus?&quot;</div></blockquote><div><b=
r></div></span><div>There was no clear agreement on a new set of qualifying=
 criteria, and the discussion faded out.<span class=3D"HOEnZb"><font color=
=3D"#888888"><br><br></font></span></div><span class=3D"HOEnZb"><font color=
=3D"#888888"><div>-MSK <br></div></font></span></div></div></div>
</blockquote></div><br></div>

--001a11c26b2aabbb5d052fe92128--


From nobody Thu Apr  7 11:25:28 2016
Return-Path: <jhaas@slice.pfrc.org>
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 3D8B112D60A for <ietf@ietfa.amsl.com>; Thu,  7 Apr 2016 11:25:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.912
X-Spam-Level: 
X-Spam-Status: No, score=-1.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 5jt0zs5kt-jM for <ietf@ietfa.amsl.com>; Thu,  7 Apr 2016 11:25:26 -0700 (PDT)
Received: from slice.pfrc.org (slice.pfrc.org [67.207.130.108]) by ietfa.amsl.com (Postfix) with ESMTP id E4CE412D0F0 for <ietf@ietf.org>; Thu,  7 Apr 2016 11:25:25 -0700 (PDT)
Received: by slice.pfrc.org (Postfix, from userid 1001) id F14291E83B; Thu,  7 Apr 2016 14:29:36 -0400 (EDT)
Date: Thu, 7 Apr 2016 14:29:36 -0400
From: Jeffrey Haas <jhaas@pfrc.org>
To: Jari Arkko <jari.arkko@piuha.net>
Subject: Re: Concerns about Singapore
Message-ID: <20160407182936.GA21340@pfrc.org>
References: <0D914666-C3D4-4CCE-AD5E-4E5B34EA1A73@piuha.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <0D914666-C3D4-4CCE-AD5E-4E5B34EA1A73@piuha.net>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/wgqy7hRrht4I_YjAHfbUjIZQBWg>
Cc: Ted Hardie <ted.ietf@gmail.com>, IETF <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, 07 Apr 2016 18:25:27 -0000

Jari,

On Thu, Apr 07, 2016 at 12:31:20PM -0300, Jari Arkko wrote:
> I know that I am personally still in the education phase about the
> situation. But I wanted to follow-up with two points from an IETF
> perspective. First, the ability of our participants to enter our meetings
> without concerns is of crucial importance for us.

As I'm unclear whether I'll be free for mtgvenue, I'll make my statement
here:

The legal environments of the various countries we consider for venues
obviously must be a general consideration for our selection criteria.  For
most considerations, these are "here are thing you do not do - they are not
legal".

For this particular issue, the consideration is whether the people themselves
are the thing that is illegal.

While I am unclear on the full legal status of lgbt persons as "illegal
people" within the proposed venue, the laws on the books are obviously
unfriendly.  However, I'll note that even countries that contribute a large
number of our participants have laws on their books that may be similarly
negative and yet are generally known to not be enforced.  This includes the
US and India.

I am happy to see that this consideration is being given discussion.

-- Jeff (one of the impacted parties)


From nobody Thu Apr  7 11:30:46 2016
Return-Path: <dhruv.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 7AC2712D164 for <ietf@ietfa.amsl.com>; Thu,  7 Apr 2016 11:30:45 -0700 (PDT)
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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 q_pjcUHrtIiZ for <ietf@ietfa.amsl.com>; Thu,  7 Apr 2016 11:30:43 -0700 (PDT)
Received: from mail-io0-x22f.google.com (mail-io0-x22f.google.com [IPv6:2607:f8b0:4001:c06::22f]) (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 71FD612D0F0 for <ietf@ietf.org>; Thu,  7 Apr 2016 11:30:43 -0700 (PDT)
Received: by mail-io0-x22f.google.com with SMTP id 2so104359158ioy.1 for <ietf@ietf.org>; Thu, 07 Apr 2016 11:30:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc; bh=acUp88XXysDFl4vafGmyqj4yjsMgsw0l9qHUIK23goE=; b=sq7Vx0q5h1KuCFUbdj2EW6PxaxZLejDWAGDeRYlOOE6MTWQK7EwfLel4N/fmN40bSv 2eZGJ4yhiC3TIJaZn1RBQnRhXrBN/F0BzPzfG9xGUUyplTwioT/KOC9phGK8sekSEdzG QtyHGf44zmeeJy4XcsRs+plzEK6NDl4+Ow5mW4g8Z09lCJ/mY/U65YRaLSkNkKorHgWG BPmo7/8SNd1GfOU9sxOLS1DuOlbRLjyOCfGWr9ikh0C7Kx08U9IWsoink5N9PrP80gYp S3cZivEC4feCaEn/TUzWb0WIHSQZ/12ipl/qHreihTSIdS3JQx+MFPo7llfjMthJqAmK Nsww==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:date :message-id:subject:from:to:cc; bh=acUp88XXysDFl4vafGmyqj4yjsMgsw0l9qHUIK23goE=; b=gvbH/ZLWk8mhLdMAHQ/LH5e2QsFq79gZivomxAm4VMDANIVggg7Zcs59FHoHmvdikM bDkSFhCgKwBlTtQ4Zx9dXpyYE4s+On2oBqVt82ufabEM8Iabf8nxiAxI+7fOlFORxjti 0YP+OzmNfeIeKJNYrp76YzoAa52rho4gcxqJNizeUnoCiPhUgIJzO5m8MrD4FoTS3GV5 BiYQQB6z1BQIl0pTvVdCAnSpP+JRESsjMiDSVgZNlgZzEJM8p3y5/5dDLmbIIaIk/yDe 7Q09JNnmqPt34mqbbwnpGudtWH+QVkVJqA9ya1xaByd459v4tHuEjU0slvXvuJWvdO4u rS3Q==
X-Gm-Message-State: AD7BkJIdsxGsuQU5MFQm76xhP8M4pMJu9t/NSUZImW6HA/nLW+EKoN1/dtoXoSIsWDpvsxn+Bz/lnqzeErOCwQ==
MIME-Version: 1.0
X-Received: by 10.107.162.17 with SMTP id l17mr5731744ioe.42.1460053842769; Thu, 07 Apr 2016 11:30:42 -0700 (PDT)
Sender: dhruvdhody@gmail.com
X-Google-Sender-Delegation: dhruvdhody@gmail.com
Received: by 10.50.222.71 with HTTP; Thu, 7 Apr 2016 11:30:42 -0700 (PDT)
In-Reply-To: <20160407182936.GA21340@pfrc.org>
References: <0D914666-C3D4-4CCE-AD5E-4E5B34EA1A73@piuha.net> <20160407182936.GA21340@pfrc.org>
Date: Thu, 7 Apr 2016 15:30:42 -0300
X-Google-Sender-Auth: 4c-otB4i90p2jzT2QE6tY7a6MG8
Message-ID: <CAB75xn780nNDjGa_Cc222J20-+1CCHt09Xp8KHzaK=n0xx51pg@mail.gmail.com>
Subject: Re: Concerns about Singapore
From: Dhruv Dhody <dhruv.ietf@gmail.com>
To: Jeffrey Haas <jhaas@pfrc.org>
Content-Type: multipart/alternative; boundary=001a11409936a6bf02052fe94667
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/x0WxGWtPIPwKdFG5ks2Azj-tddU>
Cc: Ted Hardie <ted.ietf@gmail.com>, IETF <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, 07 Apr 2016 18:30:45 -0000

--001a11409936a6bf02052fe94667
Content-Type: text/plain; charset=UTF-8

+1

I am happy to see that LGBT inclusiveness taken seriously by the IETF. But
looking at the law on the books in black and white, would be doing a
disservice to a large region of the world (with a large number of Internet
users).

Dhruv (Impacted on 2 fronts)

On Thu, Apr 7, 2016 at 3:29 PM, Jeffrey Haas <jhaas@pfrc.org> wrote:

> Jari,
>
> On Thu, Apr 07, 2016 at 12:31:20PM -0300, Jari Arkko wrote:
> > I know that I am personally still in the education phase about the
> > situation. But I wanted to follow-up with two points from an IETF
> > perspective. First, the ability of our participants to enter our meetings
> > without concerns is of crucial importance for us.
>
> As I'm unclear whether I'll be free for mtgvenue, I'll make my statement
> here:
>
> The legal environments of the various countries we consider for venues
> obviously must be a general consideration for our selection criteria.  For
> most considerations, these are "here are thing you do not do - they are not
> legal".
>
> For this particular issue, the consideration is whether the people
> themselves
> are the thing that is illegal.
>
> While I am unclear on the full legal status of lgbt persons as "illegal
> people" within the proposed venue, the laws on the books are obviously
> unfriendly.  However, I'll note that even countries that contribute a large
> number of our participants have laws on their books that may be similarly
> negative and yet are generally known to not be enforced.  This includes the
> US and India.
>
> I am happy to see that this consideration is being given discussion.
>
> -- Jeff (one of the impacted parties)
>
>

--001a11409936a6bf02052fe94667
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-family:trebuche=
t ms,sans-serif;color:#4c1130">+1=C2=A0</div><div class=3D"gmail_default" s=
tyle=3D"font-family:trebuchet ms,sans-serif;color:#4c1130"><br></div><div c=
lass=3D"gmail_default" style=3D"font-family:trebuchet ms,sans-serif;color:#=
4c1130">I am happy to see that LGBT inclusiveness taken seriously by the IE=
TF. But looking at the law on the books in black and white, would be doing =
a disservice to a large region of the world (with a large number of Interne=
t users).=C2=A0</div><div class=3D"gmail_default" style=3D"font-family:treb=
uchet ms,sans-serif;color:#4c1130"><br></div><div class=3D"gmail_default" s=
tyle=3D"font-family:trebuchet ms,sans-serif;color:#4c1130">Dhruv (Impacted =
on 2 fronts)</div></div><div class=3D"gmail_extra"><br><div class=3D"gmail_=
quote">On Thu, Apr 7, 2016 at 3:29 PM, Jeffrey Haas <span dir=3D"ltr">&lt;<=
a href=3D"mailto:jhaas@pfrc.org" target=3D"_blank">jhaas@pfrc.org</a>&gt;</=
span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8e=
x;border-left:1px #ccc solid;padding-left:1ex">Jari,<br>
<span class=3D""><br>
On Thu, Apr 07, 2016 at 12:31:20PM -0300, Jari Arkko wrote:<br>
&gt; I know that I am personally still in the education phase about the<br>
&gt; situation. But I wanted to follow-up with two points from an IETF<br>
&gt; perspective. First, the ability of our participants to enter our meeti=
ngs<br>
&gt; without concerns is of crucial importance for us.<br>
<br>
</span>As I&#39;m unclear whether I&#39;ll be free for mtgvenue, I&#39;ll m=
ake my statement<br>
here:<br>
<br>
The legal environments of the various countries we consider for venues<br>
obviously must be a general consideration for our selection criteria.=C2=A0=
 For<br>
most considerations, these are &quot;here are thing you do not do - they ar=
e not<br>
legal&quot;.<br>
<br>
For this particular issue, the consideration is whether the people themselv=
es<br>
are the thing that is illegal.<br>
<br>
While I am unclear on the full legal status of lgbt persons as &quot;illega=
l<br>
people&quot; within the proposed venue, the laws on the books are obviously=
<br>
unfriendly.=C2=A0 However, I&#39;ll note that even countries that contribut=
e a large<br>
number of our participants have laws on their books that may be similarly<b=
r>
negative and yet are generally known to not be enforced.=C2=A0 This include=
s the<br>
US and India.<br>
<br>
I am happy to see that this consideration is being given discussion.<br>
<br>
-- Jeff (one of the impacted parties)<br>
<br>
</blockquote></div><br></div>

--001a11409936a6bf02052fe94667--


From nobody Thu Apr  7 11:31:12 2016
Return-Path: <stewart.bryant@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 0CD5F12D56E for <ietf@ietfa.amsl.com>; Thu,  7 Apr 2016 11:31:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 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, RCVD_IN_DNSWL_LOW=-0.7, 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 RGaVhP2a8zn5 for <ietf@ietfa.amsl.com>; Thu,  7 Apr 2016 11:31:08 -0700 (PDT)
Received: from mail-wm0-x241.google.com (mail-wm0-x241.google.com [IPv6:2a00:1450:400c:c09::241]) (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 995F812D5C2 for <ietf@ietf.org>; Thu,  7 Apr 2016 11:31:05 -0700 (PDT)
Received: by mail-wm0-x241.google.com with SMTP id n3so23570415wmn.1 for <ietf@ietf.org>; Thu, 07 Apr 2016 11:31:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=tAN5nunqxjra2ZKJdBpRnyB7VVHlsLbBarbqWcrgD64=; b=NgwE07Beds8NThO0hYV7BcnLepvO3bMf3CXXlpEZ2H3SGvqT5xu0jPL+59OlwnGfQ3 quYFAECjUOdrq1cd0gjjhRz2CIPk/oMj2aNl7xrm7ZvsMbld0XVdz8S+QXL0v6Th+yXT C2Qe957F8au/PECvKd+lBGP3Q6OyDhY3AiSpNs7uXKu0Wn+3aCysSX3Ziywi1LCOtbi5 HM/iuXMLrXpLD+GUjNuqDx42maStB2lBuhtlbf7yk5dAxOjk1nyXUnmBMh1V9zPy1M03 HUP3w7oERqORJLVVNRlKF5SBmr71e5Hy/R3IBmVDM1RAwviyLNIjTAwIdDIBch2NmFXm CojA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=tAN5nunqxjra2ZKJdBpRnyB7VVHlsLbBarbqWcrgD64=; b=A0A74ri+Kb+7GIx0IVv11QaKRQR/J6Lyy/bo2jtam5mtQuT2xyE0TtMt0j5a7aFGMW ew435wPvZ8IrTk0VXHknTjHko8xQilxr+jgjzTc4IwkzGng8GEYO96BCfYuNgApVFrvZ RBL53d9JgrR+ersq+1tbuNMpxvZYGbWxqy7MiIt05xL3gvWkpzsgednfz6NJfPcZmWrQ Q6WejyBNCoFAhP/2XIpR2YwjjyHUT5d1SFu2tbXuk+cs0E4BeUopESs2eJmnIAxYVSA9 WSq5eyr23T957lJ2mnfhDkTmK5oZwfP9uGF5q3GuQ9u11Z+bBdEhjn+snavoFjlRq0yU 0/hQ==
X-Gm-Message-State: AD7BkJKbkZ0gMODiHUSIBIWa++ECPUMWxUf0ooIE9S0qEUDA2nW6L67ylTbyywa936aR/w==
X-Received: by 10.194.158.226 with SMTP id wx2mr4953927wjb.91.1460053864202; Thu, 07 Apr 2016 11:31:04 -0700 (PDT)
Received: from [192.168.2.126] (host213-123-124-182.in-addr.btopenworld.com. [213.123.124.182]) by smtp.gmail.com with ESMTPSA id 188sm10198303wmk.6.2016.04.07.11.31.02 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 07 Apr 2016 11:31:03 -0700 (PDT)
Subject: Re: "We did not know" is not a good excuse
To: dcrocker@bbiw.net
References: <09ff01d1905c$f15d4e70$d417eb50$@olddog.co.uk> <5705C39E.30807@dcrocker.net> <0a5801d19086$79f40e30$6ddc2a90$@olddog.co.uk> <570677BC.9000900@dcrocker.net> <203EFD6F-183D-4C92-9006-3BFE24BB525B@gmail.com> <57068CE5.1040709@dcrocker.net>
From: Stewart Bryant <stewart.bryant@gmail.com>
Message-ID: <5706A765.4090408@gmail.com>
Date: Thu, 7 Apr 2016 19:31:01 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.7.0
MIME-Version: 1.0
In-Reply-To: <57068CE5.1040709@dcrocker.net>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/m-wZAXoJ4D9pLaT8iY2WjoeiN2Q>
Cc: 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, 07 Apr 2016 18:31:10 -0000

On 07/04/2016 17:37, Dave Crocker wrote:
> On 4/7/2016 9:30 AM, Stewart Bryant wrote:
>>> On 7 Apr 2016, at 16:07, Dave Crocker <dhc@dcrocker.net> wrote:
>>>   And I'll suggest that this is not an issue that one should try to 
>>> 'game', such as by trying to obscure the choice by floating various 
>>> venue possibilities or otherwise hoping that we haven't signaled the 
>>> choice to a specific city/hotel.
>>
>> Such a process served us well in getting feedback on members of the 
>> I* until recently.
>>
>> I would have thought that it would pick up problems of the type that 
>> was identified last night without compromising our commercial 
>> position too badly.
>
>
> Stewart,  if you are referring to the gaming that used to be done, 
> when soliciting information about nomcom candidates, by padding the 
> list of names with various non-candidates, in my experience on several 
> nomcoms, no it did not work well at all.
>
> d/
>
>

Of course one's mileage may vary. Whilst I prefer the new system, my 
recollection from the two Nomcoms I served on was that the padded 
systems worked well enough.

The padding is somewhat different in this case because the padding may 
actually be not fully researched candidates and the input may mean that 
you avoid additional work reviewing a city that would otherwise be 
dropped at a later stage.

Stewart


From nobody Thu Apr  7 11:35:22 2016
Return-Path: <superuser@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 79C8812D56E for <ietf@ietfa.amsl.com>; Thu,  7 Apr 2016 11:35:20 -0700 (PDT)
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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 3JiEsUy6cLnX for <ietf@ietfa.amsl.com>; Thu,  7 Apr 2016 11:35:19 -0700 (PDT)
Received: from mail-vk0-x22a.google.com (mail-vk0-x22a.google.com [IPv6:2607:f8b0:400c:c05::22a]) (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 D467112D564 for <ietf@ietf.org>; Thu,  7 Apr 2016 11:35:18 -0700 (PDT)
Received: by mail-vk0-x22a.google.com with SMTP id c4so110483412vkb.3 for <ietf@ietf.org>; Thu, 07 Apr 2016 11:35:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=HC9bJ6IiE+YMmiKmHx+Z6lwfuFwKdc+gfck6ykzIsPs=; b=pHj4edrbYwN0K6KN88RpyB4P+Fv/fIG181Y2Nz0rXo/11e6W4shkVYS70T0Ap2Os/P nw+QHa0PNo3cwUNAWGqhvokV2T2zqP/6bFpxohA4FUTuEVjkYV7+M/ugys3spIZ2KcuD SKGbLvlvpRXIjNG/4Xb4oRFPeJR6hzu/r8HSRWZCHAIVMIRaf5ppqnutvUOu47DE290z u6RQmurCeXlNWnuCLhpyyiVDFDDt4IXbltdoIutrEcGOBMrRAwtjZ5uyexyg4oW4RJ7x bzBbiiUofgZHBbIvL2etuAjPVaHCHg9kkT74WKQO2eWmFZbY+Yqksl13XMS5fuGSuNSH c4qw==
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:date :message-id:subject:from:to:cc; bh=HC9bJ6IiE+YMmiKmHx+Z6lwfuFwKdc+gfck6ykzIsPs=; b=FJX88cgXa/gcA49IavVm5STi5OeFuVR5ZVFJXFsc20QumopKYRlijT+6qRcMkweiMn i6DAny+4ziKIgFHefY2XJ/J7KByStLHQU4O2wRZkGjDxhVBrI/Bgin6t9gKl1TZS5h6z 1/IT9SbrMH8epdNHePjKew0yqRt38BnK+53vV9FniAOY9eYtt9PXJHCW0bkMdyNhniaZ FrcQaLMOuhiGCSRYg3eaD/wTH051FS5ciPuHF7JeiAyWPis6w6mG5hyb0JkWuenOMfqD GIVPydMx/2MCVNQtGkSqnf1IAUmpExGzNujsHyAtxj2++iltMknE44av7OI95ghuCC2l +q3w==
X-Gm-Message-State: AD7BkJIloy3Ssq+IMD9dGOp0FwkQyzwnz09O41A9Ynrd9zLxiC790qA0Eko0fA2iNoljR61ZhAConKIszGmXJw==
MIME-Version: 1.0
X-Received: by 10.176.1.54 with SMTP id 51mr2102055uak.123.1460054117998; Thu, 07 Apr 2016 11:35:17 -0700 (PDT)
Received: by 10.103.43.5 with HTTP; Thu, 7 Apr 2016 11:35:17 -0700 (PDT)
In-Reply-To: <CAPt1N1nqmC7NJyg2M6Na8vUj8T-qObO-1gHFEXZzrobb3oOQhA@mail.gmail.com>
References: <CAL0qLwY0FuDp5=RMFEhUMtkK=XNDxX2dogvVY7+OSy88jrrvOQ@mail.gmail.com> <CAPt1N1=SYpo-CiHoc07Ukb04Kb1LGV2=BPPyRLUsaqyLM9Hbwg@mail.gmail.com> <CAL0qLwbhYRqw7fXHzYY0=W-CpmeHeDdaZx3z2Qg0cA2aMrmVwg@mail.gmail.com> <CAPt1N1nqmC7NJyg2M6Na8vUj8T-qObO-1gHFEXZzrobb3oOQhA@mail.gmail.com>
Date: Thu, 7 Apr 2016 15:35:17 -0300
Message-ID: <CAL0qLwZHGa5OvSmZ=bTd6AWchsm4r=QaJn2nPqD+YjeWPmH9pA@mail.gmail.com>
Subject: Re: Qualifying for NomCom
From: "Murray S. Kucherawy" <superuser@gmail.com>
To: Ted Lemon <mellon@fugue.com>
Content-Type: multipart/alternative; boundary=001a113c86a80e67b2052fe9576c
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/9wud14L6JkxfO24ElpPW9e6y90Y>
Cc: ietf <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, 07 Apr 2016 18:35:20 -0000

--001a113c86a80e67b2052fe9576c
Content-Type: text/plain; charset=UTF-8

On Thu, Apr 7, 2016 at 3:19 PM, Ted Lemon <mellon@fugue.com> wrote:

> Right.   So that's not what "consensus" means.   Suggest you reread RFC
> 7282.   It's not normative, but I think it's helpful to reread when you
> feel that you have failed to find consensus.   It contains some good advice
> about getting to consensus.
>

Well let's see...

"Lack of disagreement is more important than agreement..."  check.  There
was disagreement with the proposals, and no better ones presented available.

"Rough consensus is achieved when all issues are addressed, but not
necessarily accommodated..." check.  I wasn't able to even address the
concerns raised, because they were valid, and again there were no solid
remedies proposed.

etc.

On the other hand, I realize now that previous thread went on longer than I
remembered, and there was a proposal that we (I, probably) construct an
RFC3933-style process experiment and let that run for a while.  If it works
well, we can codify it by adding it to RFC7437bis.  So I'll do that.  If
anyone wants to volunteer to collaborate on it, please contact me directly.

-MSK

--001a113c86a80e67b2052fe9576c
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">On Thu, Apr 7, 2016 at 3:19 PM, Ted Lemon <span dir=3D"ltr=
">&lt;<a href=3D"mailto:mellon@fugue.com" target=3D"_blank">mellon@fugue.co=
m</a>&gt;</span> wrote:<br><div class=3D"gmail_extra"><div class=3D"gmail_q=
uote"><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-l=
eft:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr">Right. =C2=A0 So that=
&#39;s not what &quot;consensus&quot; means. =C2=A0 Suggest you reread RFC =
7282. =C2=A0 It&#39;s not normative, but I think it&#39;s helpful to reread=
 when you feel that you have failed to find consensus. =C2=A0 It contains s=
ome good advice about getting to consensus.</div></blockquote><div><br></di=
v><div>Well let&#39;s see...<br><br></div><div>&quot;Lack of disagreement i=
s more important than agreement...&quot;=C2=A0 check.=C2=A0 There was disag=
reement with the proposals, and no better ones presented available.<br><br>=
</div><div>&quot;Rough consensus is achieved when all issues are addressed,=
 but not necessarily accommodated...&quot; check.=C2=A0 I wasn&#39;t able t=
o even address the concerns raised, because they were valid, and again ther=
e were no solid remedies proposed.<br><br></div>etc.<br><br></div><div clas=
s=3D"gmail_quote">On the other hand, I realize now that previous thread wen=
t on longer than I remembered, and there was a proposal that we (I, probabl=
y) construct an RFC3933-style process experiment and let that run for a whi=
le.=C2=A0 If it works well, we can codify it by adding it to RFC7437bis.=C2=
=A0 So I&#39;ll do that.=C2=A0 If anyone wants to volunteer to collaborate =
on it, please contact me directly.<br><br></div><div class=3D"gmail_quote">=
-MSK<br></div></div></div>

--001a113c86a80e67b2052fe9576c--


From nobody Thu Apr  7 12:12:07 2016
Return-Path: <leifj@mnt.se>
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 7D34512D1F0 for <ietf@ietfa.amsl.com>; Thu,  7 Apr 2016 12:12:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mnt-se.20150623.gappssmtp.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 Z_A_kcFG7llf for <ietf@ietfa.amsl.com>; Thu,  7 Apr 2016 12:12:04 -0700 (PDT)
Received: from mail-qg0-x230.google.com (mail-qg0-x230.google.com [IPv6:2607:f8b0:400d:c04::230]) (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 5DB3912D0EF for <ietf@ietf.org>; Thu,  7 Apr 2016 12:12:04 -0700 (PDT)
Received: by mail-qg0-x230.google.com with SMTP id f105so48158573qge.2 for <ietf@ietf.org>; Thu, 07 Apr 2016 12:12:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mnt-se.20150623.gappssmtp.com; s=20150623; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding; bh=x1QgFvQosShbGfQo2C+b+N4YN5OyP+fRtEn95h5Z8uk=; b=F9NawRqx5eXBobtE5qShcQ4Z+TIFtMI2E+fxHtyKeRsBgm6bycwwzvweI6RUkKEoCj 9++XpUPyye69ZUXxT+qJHgjgwi6JUOdol6XdYXHI8hwM7Fkw8Uoc9cUl0S8O8gOsdETD 2cwfui5aEOamHsdAhpLPrurL3sAixxLImJZ0Ppr77K6Bcl1d/QwhlqZBPmcFIgfuT0HB Mfc3paRe6Pnzqb316tTdiDObtTrAuVB8R94MCe3+oH3fsP1s+HVr0TrEsOKhG3+Wqj9U NTKnf4hGYPGHnm8W3IgdOQ++UKlfayvJtG2LFNnd2L7gXU1rGSoCqeEokzOH4+lMszm0 QCyQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=x1QgFvQosShbGfQo2C+b+N4YN5OyP+fRtEn95h5Z8uk=; b=E46WTj0gIeZF9a5s0uYEkMtuUoUdGY/PHJ/55A9CFs2ivYtfqfakAhGN6MrNsm/HyO CUjDnRH/lLSRxej3Zjgar6ginVRVZCYBz1s3C7kGM6wlwvHHo8z6eNWplMUsscyjue2T tyO52N6L31EOBlGYi/xPpqBiVembFZR/OmK9KGEaoj6HoFDcA7pj+Werd9Fnvq+oyOCV G/mNV6dT7LN63ThVmcMmIAwb4mbT9CXR2jxxLXgjdVeoDfIlugXk+eBysVUnuq2U3xDk wB4/JgDt9ajWe3p666VXZTjgvwvBN3LOS034j7Ir2rw8Nhq5lJz622jBC505IpDTnH+v WwFQ==
X-Gm-Message-State: AD7BkJLlkfICS8nQsJKqlVuZyNUgOinSRr/lwm39GAa2wZHmm7t+4C9TB4pE/i1DsU3Bow==
X-Received: by 10.140.22.212 with SMTP id 78mr6224322qgn.77.1460056323416; Thu, 07 Apr 2016 12:12:03 -0700 (PDT)
Received: from ?IPv6:2001:67c:370:152:4059:bb38:ef12:29ac? ([2001:67c:370:152:4059:bb38:ef12:29ac]) by smtp.googlemail.com with ESMTPSA id u102sm3968189qge.27.2016.04.07.12.12.01 for <ietf@ietf.org> (version=TLSv1/SSLv3 cipher=OTHER); Thu, 07 Apr 2016 12:12:02 -0700 (PDT)
Subject: Re: Concerns about Singapore
To: ietf@ietf.org
References: <0D914666-C3D4-4CCE-AD5E-4E5B34EA1A73@piuha.net> <20160407182936.GA21340@pfrc.org> <CAB75xn780nNDjGa_Cc222J20-+1CCHt09Xp8KHzaK=n0xx51pg@mail.gmail.com>
From: Leif Johansson <leifj@mnt.se>
Message-ID: <5706B100.9040509@mnt.se>
Date: Thu, 7 Apr 2016 21:12:00 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0
MIME-Version: 1.0
In-Reply-To: <CAB75xn780nNDjGa_Cc222J20-+1CCHt09Xp8KHzaK=n0xx51pg@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/KT5ysF0NWWcv57miDPcn_G4Dwbg>
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, 07 Apr 2016 19:12:06 -0000

On 2016-04-07 20:30, Dhruv Dhody wrote:
> +1 
> 
> I am happy to see that LGBT inclusiveness taken seriously by the IETF.
> But looking at the law on the books in black and white, would be doing a
> disservice to a large region of the world (with a large number of
> Internet users). 

I don't parse that actually.

How is reading the law of Singapore "doing disservice to a large region
of the world?"

I don't think "yes but many who live in Singapore are nice people"
nor "yes but those laws are hardly ever applied" are useful arguments
in this discussion but maybe thats just me...

I am pretty sure that Ted (to pick a random example) would be able to
travel to Singapore for an IETF and be /personally/ quite safe because
as you say the laws of the land would be selectively applied.

That is always the problem of selectively applied laws: they are used
when it is convenient... and are often used to intimidate. That is why
censorship is often self-administered in countries where there are
censorship laws "on the books".

	Cheers Leif


From nobody Thu Apr  7 12:41:52 2016
Return-Path: <dhruv.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 CF26612D5E8 for <ietf@ietfa.amsl.com>; Thu,  7 Apr 2016 12:41:51 -0700 (PDT)
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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 HCAT7ST86eT1 for <ietf@ietfa.amsl.com>; Thu,  7 Apr 2016 12:41:48 -0700 (PDT)
Received: from mail-ig0-x22e.google.com (mail-ig0-x22e.google.com [IPv6:2607:f8b0:4001:c05::22e]) (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 CDB8612D55D for <ietf@ietf.org>; Thu,  7 Apr 2016 12:41:44 -0700 (PDT)
Received: by mail-ig0-x22e.google.com with SMTP id f1so161423077igr.1 for <ietf@ietf.org>; Thu, 07 Apr 2016 12:41:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc; bh=iAzxA51Jl5n+s5bGkm3VVBBIAWPWSxoF0Pk7bG8iTys=; b=Bs17835DY4+Hon/QayYNH2/+FUrKoeHlYi/13Udq8NAz4vmEgUqcCTXTAeTqSpktSU 3HWqWHBJSfbthKI4oCyCPz1yR9NoeUa71hfLQofBXIz+z79q0wvD7kV5r7/znEZZKubi Gma96S9IWeQgBMUxRUSDcNVeHZL67WXOnsQKOiwphbQnmcxecUxMelU65plwlM/4oA0u AUIfgCHFn7G5vApKsrXt7PZub7GsY00qjmH/VCNOpBk5qmFEjyb5nGtLYBTT24pQNcdI NmNSLeM6Fln6pI8IxzGsKICXYPZlYDRLx6V6VU6CzrP3DZQ6FqNIs4M8A3m19ZvJeBk1 gsJQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:date :message-id:subject:from:to:cc; bh=iAzxA51Jl5n+s5bGkm3VVBBIAWPWSxoF0Pk7bG8iTys=; b=WP9W75VYnis+ComjN52Kk+fjxpD+covog98zHhJEjn/4tdgYYB+TSth+aqn72W3zfk qP2VVDlKUsFsU6DVz9q9Tg+7j3HSnn1n/A1eQXcTJNE6KB+ITDBJj/lILUsQIucY1WTQ RjL+chsaBAojJgoY4ijZLgvUJPNUiYOgfkR088bvB5RDPsGTOZ8EfNQ481SbB/ycoLzi T1dWYb9uufxzWrwtQoqMCbRQKbDDMk3OEWIyMOSTHxrpqFUsKGmnthx259Lrj8+aXKYC awa2AwGyUyYrxY+prKG+bgEX9VlGGE+z9/cWAN6YzRjA9VpKHTM3yliW+VRvfbzKxKrk TFbg==
X-Gm-Message-State: AD7BkJIrJUgJ20wlPpUWLT0XE5CgX5H7bj2OI2+16J4zSoNqXTClI/GV3bpKqPmjmvB0V37QmeGsih/wBR2MLA==
MIME-Version: 1.0
X-Received: by 10.50.79.167 with SMTP id k7mr28643164igx.27.1460058104042; Thu, 07 Apr 2016 12:41:44 -0700 (PDT)
Sender: dhruvdhody@gmail.com
X-Google-Sender-Delegation: dhruvdhody@gmail.com
Received: by 10.50.222.71 with HTTP; Thu, 7 Apr 2016 12:41:43 -0700 (PDT)
In-Reply-To: <5706B100.9040509@mnt.se>
References: <0D914666-C3D4-4CCE-AD5E-4E5B34EA1A73@piuha.net> <20160407182936.GA21340@pfrc.org> <CAB75xn780nNDjGa_Cc222J20-+1CCHt09Xp8KHzaK=n0xx51pg@mail.gmail.com> <5706B100.9040509@mnt.se>
Date: Thu, 7 Apr 2016 16:41:43 -0300
X-Google-Sender-Auth: SlEaK4zPneXH-CCAciTIYrLG9_M
Message-ID: <CAB75xn6fmj84ROUtG5eUB3GerHx83hrEr3w5vSADY_g=BRg5FA@mail.gmail.com>
Subject: Re: Concerns about Singapore
From: Dhruv Dhody <dhruv.ietf@gmail.com>
To: Leif Johansson <leifj@mnt.se>
Content-Type: multipart/alternative; boundary=089e013a1a38a49f6e052fea44cc
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/KDR8xpX3FqFA1c_g6HPpvTpzDBU>
Cc: "ietf@ietf.org 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, 07 Apr 2016 19:41:52 -0000

--089e013a1a38a49f6e052fea44cc
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi Leif,

On Thu, Apr 7, 2016 at 4:12 PM, Leif Johansson <leifj@mnt.se> wrote:

> On 2016-04-07 20:30, Dhruv Dhody wrote:
> > +1
> >
> > I am happy to see that LGBT inclusiveness taken seriously by the IETF.
> > But looking at the law on the books in black and white, would be doing =
a
> > disservice to a large region of the world (with a large number of
> > Internet users).
>
> I don't parse that actually.
>

=E2=80=8BSorry if I was not clear.
=E2=80=8B

>
> How is reading the law of Singapore "doing disservice to a large region
> of the world?"
>

=E2=80=8BNo, I meant that IETF would be doing a disservice to a large part =
of the
world (that has on its books these laws). We need to have a nuanced
approach and this being another factor in a multitude of factors. Having a
blanket rule that the IETF will not go to any such place is something
I disagree with.


>
> I don't think "yes but many who live in Singapore are nice people"
> nor "yes but those laws are hardly ever applied" are useful arguments
> in this discussion but maybe thats just me...
>
> I am pretty sure that Ted (to pick a random example) would be able to
> travel to Singapore for an IETF and be /personally/ quite safe because
> as you say the laws of the land would be selectively applied.
>
> That is always the problem of selectively applied laws: they are used
> when it is convenient... and are often used to intimidate. That is why
> censorship is often self-administered in countries where there are
> censorship laws "on the books".
>

=E2=80=8BI agree with you. I understand this well, as an openly gay person,=
 living
in a country with such laws=E2=80=8B on the book.
I hope these laws go away but till then, having a blanket rule against
taking IETF to a big part of the world is something I find wrong.

Thanks!
Dhruv


>         Cheers Leif
>
>

--089e013a1a38a49f6e052fea44cc
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-family:trebuche=
t ms,sans-serif;color:#4c1130">Hi Leif,=C2=A0</div><div class=3D"gmail_extr=
a"><br><div class=3D"gmail_quote">On Thu, Apr 7, 2016 at 4:12 PM, Leif Joha=
nsson <span dir=3D"ltr">&lt;<a href=3D"mailto:leifj@mnt.se" target=3D"_blan=
k">leifj@mnt.se</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" =
style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><sp=
an>On 2016-04-07 20:30, Dhruv Dhody wrote:<br>
&gt; +1<br>
&gt;<br>
&gt; I am happy to see that LGBT inclusiveness taken seriously by the IETF.=
<br>
&gt; But looking at the law on the books in black and white, would be doing=
 a<br>
&gt; disservice to a large region of the world (with a large number of<br>
&gt; Internet users).<br>
<br>
</span>I don&#39;t parse that actually.<br></blockquote><div><br></div><div=
 class=3D"gmail_default" style=3D"font-family:&quot;trebuchet ms&quot;,sans=
-serif;color:rgb(76,17,48)">=E2=80=8BSorry if I=C2=A0was not clear.=C2=A0</=
div><div class=3D"gmail_default" style=3D"font-family:&quot;trebuchet ms&qu=
ot;,sans-serif;color:rgb(76,17,48)">=E2=80=8B</div><blockquote class=3D"gma=
il_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-lef=
t:1ex">
<br>
How is reading the law of Singapore &quot;doing disservice to a large regio=
n<br>
of the world?&quot;<br></blockquote><div><br></div><div><div class=3D"gmail=
_default" style=3D"font-family:&quot;trebuchet ms&quot;,sans-serif;color:rg=
b(76,17,48)">=E2=80=8BNo, I meant that IETF would be doing a disservice to =
a large part of the world (that has on its books these laws). We need to ha=
ve a nuanced approach and this being another factor in a multitude of facto=
rs. Having a blanket rule that the IETF will not go to any such place is so=
mething I=C2=A0disagree=C2=A0with. =C2=A0=C2=A0</div><div class=3D"gmail_de=
fault" style=3D"font-family:&quot;trebuchet ms&quot;,sans-serif;color:rgb(7=
6,17,48)">=C2=A0</div></div><blockquote class=3D"gmail_quote" style=3D"marg=
in:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
I don&#39;t think &quot;yes but many who live in Singapore are nice people&=
quot;<br>
nor &quot;yes but those laws are hardly ever applied&quot; are useful argum=
ents<br>
in this discussion but maybe thats just me...<br>
<br>
I am pretty sure that Ted (to pick a random example) would be able to<br>
travel to Singapore for an IETF and be /personally/ quite safe because<br>
as you say the laws of the land would be selectively applied.<br>
<br>
That is always the problem of selectively applied laws: they are used<br>
when it is convenient... and are often used to intimidate. That is why<br>
censorship is often self-administered in countries where there are<br>
censorship laws &quot;on the books&quot;.<br></blockquote><div><br></div><d=
iv><div class=3D"gmail_default" style=3D"font-family:&quot;trebuchet ms&quo=
t;,sans-serif;color:rgb(76,17,48)">=E2=80=8BI agree with you. I understand =
this well, as an openly gay person, living in a country with such laws=E2=
=80=8B on the book.=C2=A0</div><div class=3D"gmail_default" style=3D"font-f=
amily:&quot;trebuchet ms&quot;,sans-serif;color:rgb(76,17,48)">I hope these=
 laws go away but=C2=A0till then, having a blanket rule against taking IETF=
 to a big part of the world is something I=C2=A0find wrong.=C2=A0</div></di=
v><div class=3D"gmail_default" style=3D"font-family:&quot;trebuchet ms&quot=
;,sans-serif;color:rgb(76,17,48)"><br></div><div class=3D"gmail_default" st=
yle=3D"font-family:&quot;trebuchet ms&quot;,sans-serif;color:rgb(76,17,48)"=
>Thanks!=C2=A0</div><div class=3D"gmail_default" style=3D"font-family:&quot=
;trebuchet ms&quot;,sans-serif;color:rgb(76,17,48)">Dhruv</div><div class=
=3D"gmail_default" style=3D"font-family:&quot;trebuchet ms&quot;,sans-serif=
;color:rgb(76,17,48)"><br></div><blockquote class=3D"gmail_quote" style=3D"=
margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Cheers Leif<br>
<br>
</blockquote></div><br></div></div>

--089e013a1a38a49f6e052fea44cc--


From nobody Thu Apr  7 12:45:17 2016
Return-Path: <d3e3e3@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 5C41A12D17D for <ietf@ietfa.amsl.com>; Thu,  7 Apr 2016 12:45:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.45
X-Spam-Level: 
X-Spam-Status: No, score=-2.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, RCVD_IN_DNSWL_LOW=-0.7, 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 5khmsEQ_NSj6 for <ietf@ietfa.amsl.com>; Thu,  7 Apr 2016 12:45:14 -0700 (PDT)
Received: from mail-oi0-x22f.google.com (mail-oi0-x22f.google.com [IPv6:2607:f8b0:4003:c06::22f]) (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 BC3D512D157 for <ietf@ietf.org>; Thu,  7 Apr 2016 12:45:14 -0700 (PDT)
Received: by mail-oi0-x22f.google.com with SMTP id s79so112127227oie.1 for <ietf@ietf.org>; Thu, 07 Apr 2016 12:45:14 -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=f5OE0438D+m6H4enwjZVu6gI1fyyfPndsB1tC88FTMM=; b=o0agbQzpLUkgIllnrakZe948HMcer2/FR9HiGzpS2HRaf0lodwL32ufzv3H/O8liNi T88VaL+wlQQtoy7VvZS/1k8mZX6Nk6gTB69SuL39iO607b4z1UFWX4/miBTBRM+C43He VHN7WLbAQvYoK2xgVIyuUt0I+GXUvSxjBCzA4wMZkBonOLRBsFq39af9fJN037YLuM65 h+t1PCt/PZYngkQxV6gbjak4StJcbSIINVxnA4gXU4G1hFinIaIv1nMGU1Kc/Bv4+hnU W665qe+NUq+MwZSOfbv7vUS3XmuuN7qR/w8qqIQsrQhSL/vB4MM0kitbiKeIms7+XAgh pIcw==
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=f5OE0438D+m6H4enwjZVu6gI1fyyfPndsB1tC88FTMM=; b=JWAcuYNFx92Jx+/hTzpYzulQT7Ej+Fq3ofiDRYJSmwR4ybGlUGGgYoalXIqS94an/A EufEDvgwWJFO//KIwk9u0e1RqZn8HiNWK91iNf5pc61VkIbIGr/0WZ4ij890e5eBrwqV OKQRWx4mN3ZG+mSUBPPHfMS4BjdkW9MIUBb8xlb6dw4KIaV/zxfmiDhoJfAlrJGkLrOX ibxH29TbOkUO1WXgUwsuvoqujMbLgF/7WI4Ho1RPwYq8pe99VY5T3D6Dzfx43bfaoDEX lxSZ27HCkxkT1QktIpN3qMBC6lBJqYw5/VyoJgBNad8YySBJ4PfrPWVf0BCfdm/tSE8k o4uQ==
X-Gm-Message-State: AD7BkJLZmGQH9lBo47EwRdg7jOLqK55FLgH+JGMWHNXrNCHgY8o9lrPUCqFxgPT4O8bPWWV+xBC9IAZqwNcoKg==
X-Received: by 10.157.44.139 with SMTP id p11mr2577365otb.124.1460058314171; Thu, 07 Apr 2016 12:45:14 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.157.22.250 with HTTP; Thu, 7 Apr 2016 12:44:59 -0700 (PDT)
In-Reply-To: <5706B100.9040509@mnt.se>
References: <0D914666-C3D4-4CCE-AD5E-4E5B34EA1A73@piuha.net> <20160407182936.GA21340@pfrc.org> <CAB75xn780nNDjGa_Cc222J20-+1CCHt09Xp8KHzaK=n0xx51pg@mail.gmail.com> <5706B100.9040509@mnt.se>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Thu, 7 Apr 2016 15:44:59 -0400
Message-ID: <CAF4+nEGhBwL5ejdiORJpy4GCmQ56=c5UJEQTvAnnoh57eAOoog@mail.gmail.com>
Subject: Re: Concerns about Singapore
To: Leif Johansson <leifj@mnt.se>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/qd-9H29y8NZEPuCtsDmV7Ubf5dU>
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, 07 Apr 2016 19:45:16 -0000

On Thu, Apr 7, 2016 at 3:12 PM, Leif Johansson <leifj@mnt.se> wrote:
> On 2016-04-07 20:30, Dhruv Dhody wrote:
>> +1
>>
>> I am happy to see that LGBT inclusiveness taken seriously by the IETF.
>> But looking at the law on the books in black and white, would be doing a
>> disservice to a large region of the world (with a large number of
>> Internet users).
>
> I don't parse that actually.
>
> How is reading the law of Singapore "doing disservice to a large region
> of the world?"

I think the idea is that a literal interpretation of archaic laws in
many places would give you a wrong impression.

Let me give a small example. I assume most of the attendees at this
meeting flew into Argentina and brought with them at least one laptop
with a vale over $300 USD. It seems there is an Argentine law
requiring you to file a customs declaration on entry and imposing a
50% duty on the value of what you bring in over $300 USD. This seems
somewhat onerous since almost everyone at this meeting has a laptop
worth more than $300. But from my observations as EZE, the Argentina
authorities do not care if you have filled out this form and thousands
of people stream through a day completely ignoring it. The authorities
will take it from you if you filled it out but don't seem to even look
at it very closely... So it seems to be no problem for IETF meeting
attendees.

Thanks,
Donald
=============================
 Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
 155 Beaver Street, Milford, MA 01757 USA
 d3e3e3@gmail.com

>....
>
>         Cheers Leif


From nobody Thu Apr  7 12:51:39 2016
Return-Path: <leifj@mnt.se>
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 043A012D17D for <ietf@ietfa.amsl.com>; Thu,  7 Apr 2016 12:51:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mnt-se.20150623.gappssmtp.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 366_TPzpWIt3 for <ietf@ietfa.amsl.com>; Thu,  7 Apr 2016 12:51:33 -0700 (PDT)
Received: from mail-qk0-x235.google.com (mail-qk0-x235.google.com [IPv6:2607:f8b0:400d:c09::235]) (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 994D112D157 for <ietf@ietf.org>; Thu,  7 Apr 2016 12:51:33 -0700 (PDT)
Received: by mail-qk0-x235.google.com with SMTP id o6so35490247qkc.2 for <ietf@ietf.org>; Thu, 07 Apr 2016 12:51:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mnt-se.20150623.gappssmtp.com; s=20150623; h=subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=8HvVc2sTVgv8mtXimUmzGK20HxKUHwIo7cJIH5J/HBw=; b=b9d1AMm34d8sc+QuiOqkHPc8devcocgWn/TuUVw/hMBLYfzUdVVpGo9+i5kOG933I8 iq70/XpbWtB31lY/3A1NLD3XqtHQu93fLJa7vPZZyqiTij2Lul6TmJPB3cpQHda4dqbu 1NIArKp60MOQDvUmuNW8nXCRuDFNOOmMJzAtePqGyPvTd/1nsESfNvUXNGapxvRGf0Vj r+hpOKSswbamyT3mSiuJ+P+b7hoIiFgJBbj/mzlPc4yXkYZjmIHwMcjCjgVObxTs1h5E tskcfLbpj2RJinC+OsebrVMYbO4nCj0vLkcivbNPZJd8apIg4eISwF07YILEt4eQ8QZY Tr8g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=8HvVc2sTVgv8mtXimUmzGK20HxKUHwIo7cJIH5J/HBw=; b=COY1pJ+N5ATCC1y9j4TsPwd/yeVBDAWug5W3ljIOr3F9Y7hC2/xp3HhQsw1RPHZR5X RQcdpn1QkWxJt/3lvgNiKdd5PB5zr17xCdf5ypB9HDQnujg+vr+F3eddZiz2dnzLfkOB +xsbnVbVLY6xP8TRdvfH1Qe/iq6a/TPpxEvEN5TUITtcuZWp1r+/MkLP9PBdZPUKFUKa yn7Fy0Mt99j2c1Kuo/yrdj8AFg/nFGryLZm9DwSpqBzCJSkW4lcuvISMn0PPk8t1ujLB edyXczSxAahBWqRf/lsMNbLOg0oijY1m4NPD1HlAH64DEnE0aj3X2ycJBPQNg3sTtXFE aLJg==
X-Gm-Message-State: AD7BkJJW3H9whzTllkOw38uCCTHaEYOAsE8AbNC8bYzFIev0Y6BFfCpEyG7yg8C36XKEmw==
X-Received: by 10.55.197.70 with SMTP id p67mr6315013qki.66.1460058692708; Thu, 07 Apr 2016 12:51:32 -0700 (PDT)
Received: from ?IPv6:2001:67c:370:152:4059:bb38:ef12:29ac? ([2001:67c:370:152:4059:bb38:ef12:29ac]) by smtp.googlemail.com with ESMTPSA id 64sm4027931qgy.34.2016.04.07.12.51.31 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 07 Apr 2016 12:51:31 -0700 (PDT)
Subject: Re: Concerns about Singapore
To: Dhruv Dhody <dhruv.ietf@gmail.com>
References: <0D914666-C3D4-4CCE-AD5E-4E5B34EA1A73@piuha.net> <20160407182936.GA21340@pfrc.org> <CAB75xn780nNDjGa_Cc222J20-+1CCHt09Xp8KHzaK=n0xx51pg@mail.gmail.com> <5706B100.9040509@mnt.se> <CAB75xn6fmj84ROUtG5eUB3GerHx83hrEr3w5vSADY_g=BRg5FA@mail.gmail.com>
From: Leif Johansson <leifj@mnt.se>
Message-ID: <5706BA40.3060005@mnt.se>
Date: Thu, 7 Apr 2016 21:51:28 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0
MIME-Version: 1.0
In-Reply-To: <CAB75xn6fmj84ROUtG5eUB3GerHx83hrEr3w5vSADY_g=BRg5FA@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/90_hx0KlIDtl-8H44ZBmSC_4muA>
Cc: "ietf@ietf.org 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, 07 Apr 2016 19:51:35 -0000

> â€‹No, I meant that IETF would be doing a disservice to a large part of
> the world (that has on its books these laws). We need to have a nuanced
> approach and this being another factor in a multitude of factors. Having
> a blanket rule that the IETF will not go to any such place is something
> I disagree with.   
>  
> 

Where do you draw the line then?



From nobody Thu Apr  7 13:00:55 2016
Return-Path: <swmike@swm.pp.se>
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 740C212D18B for <ietf@ietfa.amsl.com>; Thu,  7 Apr 2016 13:00:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.311
X-Spam-Level: 
X-Spam-Status: No, score=-4.311 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=swm.pp.se
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 wnBbumLP1MWy for <ietf@ietfa.amsl.com>; Thu,  7 Apr 2016 13:00:51 -0700 (PDT)
Received: from uplift.swm.pp.se (swm.pp.se [212.247.200.143]) (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 5B40312D17D for <ietf@ietf.org>; Thu,  7 Apr 2016 13:00:51 -0700 (PDT)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id 37101A2; Thu,  7 Apr 2016 22:00:40 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1460059240; bh=uCL5lwSJcl+/wU4YMMymaY9TTIJsMpNMexN1GUPsy9Y=; h=Date:From:To:Subject:In-Reply-To:References:From; b=r5DK4T59TvKnIh9iZcoxGciV8uzXY//taL/Nmk+Ff63WUywPNSQFLvdgvvjDtsPOJ XetE0KlJSw7LujEeIunxJUvTYGIIVfmSI8M4NljycLBv7s2dV79FW6Xk0LBIf5k0Rr Gpi7qB26HabH/Q1vukpfveL7yQ9RLzpVv7HGoLnQ=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 32FA2A1 for <ietf@ietf.org>; Thu,  7 Apr 2016 22:00:40 +0200 (CEST)
Date: Thu, 7 Apr 2016 22:00:40 +0200 (CEST)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: "ietf@ietf.org Discussion" <ietf@ietf.org>
Subject: Re: Concerns about Singapore
In-Reply-To: <5706BA40.3060005@mnt.se>
Message-ID: <alpine.DEB.2.02.1604072157240.31096@uplift.swm.pp.se>
References: <0D914666-C3D4-4CCE-AD5E-4E5B34EA1A73@piuha.net> <20160407182936.GA21340@pfrc.org> <CAB75xn780nNDjGa_Cc222J20-+1CCHt09Xp8KHzaK=n0xx51pg@mail.gmail.com> <5706B100.9040509@mnt.se> <CAB75xn6fmj84ROUtG5eUB3GerHx83hrEr3w5vSADY_g=BRg5FA@mail.gmail.com> <5706BA40.3060005@mnt.se>
User-Agent: Alpine 2.02 (DEB 1266 2009-07-14)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: MULTIPART/MIXED; BOUNDARY="-137064504-594578348-1460059240=:31096"
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/TMMYRAvsGtrclcV2Y3-Vf3eKU1w>
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, 07 Apr 2016 20:00:54 -0000

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.

---137064504-594578348-1460059240=:31096
Content-Type: TEXT/PLAIN; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8BIT

On Thu, 7 Apr 2016, Leif Johansson wrote:

>
>> â€‹No, I meant that IETF would be doing a disservice to a large part of
>> the world (that has on its books these laws). We need to have a nuanced
>> approach and this being another factor in a multitude of factors. Having
>> a blanket rule that the IETF will not go to any such place is something
>> I disagree with.
>
> Where do you draw the line then?

I think it's impossible to draw a firm line. Most of it is grey area.

I'm sure I could come up with arguments why we should not go to USA or 
Sweden for our meetings, because neither place if perfect.

There are numerous very "offensive" (or replace with "weird" or some other 
word) laws on the books in most countries, and I do think we have to look 
at how those laws are applied as part of our process in deciding where to 
go.

There are no perfect places to go. There are bad and less bad ones.

-- 
Mikael Abrahamsson    email: swmike@swm.pp.se
---137064504-594578348-1460059240=:31096--


From nobody Thu Apr  7 13:08:13 2016
Return-Path: <lhotka@nic.cz>
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 C5BC612D60A for <ietf@ietfa.amsl.com>; Thu,  7 Apr 2016 13:08:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.01
X-Spam-Level: 
X-Spam-Status: No, score=-7.01 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nic.cz
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 hVDOfeNIdLe4 for <ietf@ietfa.amsl.com>; Thu,  7 Apr 2016 13:08:09 -0700 (PDT)
Received: from mail.nic.cz (mail.nic.cz [217.31.204.67]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8184D12D59F for <ietf@ietf.org>; Thu,  7 Apr 2016 13:08:09 -0700 (PDT)
Received: from [IPv6:2001:67c:370:176:e8f5:e53e:2cba:ae41] (unknown [IPv6:2001:67c:370:176:e8f5:e53e:2cba:ae41]) by mail.nic.cz (Postfix) with ESMTPSA id 358AC18015E; Thu,  7 Apr 2016 22:08:06 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=nic.cz; s=default; t=1460059688; bh=qVMwRgZmU2x/O6qBPTnsVMmyy623IRkspTCCeqfwIjU=; h=From:Date:To; b=aQjSXHtneZ3jRa3LvnR9BViCgoq/XcGEvtbhaOYtA3rPyS1vP2flqDnK6Xni7/PTG HB32eA7VecckWJV86sLEpuMAzMA6Qr2p17DH/IfGua8h5eNV8RBMQQck56YXiu5ymF Ukdb+/ZAktGKHntfaSvooRR6KzpfAN2iUSrEdrhY=
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Subject: Re: Concerns about Singapore
From: Ladislav Lhotka <lhotka@nic.cz>
In-Reply-To: <alpine.DEB.2.02.1604072157240.31096@uplift.swm.pp.se>
Date: Thu, 7 Apr 2016 17:08:02 -0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <A9B63A6D-3102-482F-8FFC-2E57A5FD8336@nic.cz>
References: <0D914666-C3D4-4CCE-AD5E-4E5B34EA1A73@piuha.net> <20160407182936.GA21340@pfrc.org> <CAB75xn780nNDjGa_Cc222J20-+1CCHt09Xp8KHzaK=n0xx51pg@mail.gmail.com> <5706B100.9040509@mnt.se> <CAB75xn6fmj84ROUtG5eUB3GerHx83hrEr3w5vSADY_g=BRg5FA@mail.gmail.com> <5706BA40.3060005@mnt.se> <alpine.DEB.2.02.1604072157240.31096@uplift.swm.pp.se>
To: Mikael Abrahamsson <swmike@swm.pp.se>
X-Mailer: Apple Mail (2.3124)
X-Virus-Scanned: clamav-milter 0.98.7 at mail
X-Virus-Status: Clean
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/XuJGTvXEiNPnTisv46C1ckzSykE>
Cc: "ietf@ietf.org 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, 07 Apr 2016 20:08:13 -0000

> On 07 Apr 2016, at 17:00, Mikael Abrahamsson <swmike@swm.pp.se> wrote:
>=20
> On Thu, 7 Apr 2016, Leif Johansson wrote:
>=20
>>=20
>>> =E2=80=8BNo, I meant that IETF would be doing a disservice to a =
large part of
>>> the world (that has on its books these laws). We need to have a =
nuanced
>>> approach and this being another factor in a multitude of factors. =
Having
>>> a blanket rule that the IETF will not go to any such place is =
something
>>> I disagree with.
>>=20
>> Where do you draw the line then?
>=20
> I think it's impossible to draw a firm line. Most of it is grey area.
>=20
> I'm sure I could come up with arguments why we should not go to USA or =
Sweden for our meetings, because neither place if perfect.

Right. And since Leif mentioned censorship, let me note that IETF =
already held a meeting in a country where censorship, and Internet =
censorship in particular, is commonplace.

>=20
> There are numerous very "offensive" (or replace with "weird" or some =
other word) laws on the books in most countries, and I do think we have =
to look at how those laws are applied as part of our process in deciding =
where to go.

Yes, and speaking of myself, I am prepared, to a reasonable degree, to =
adjust my behaviour to those laws (and cultural habits as well).

Lada

>=20
> There are no perfect places to go. There are bad and less bad ones.
>=20
> --=20
> Mikael Abrahamsson    email: swmike@swm.pp.se

--
Ladislav Lhotka, CZ.NIC Labs
PGP Key ID: E74E8C0C





From nobody Thu Apr  7 13:20:39 2016
Return-Path: <drc@virtualized.org>
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 16B3B12D6CC for <ietf@ietfa.amsl.com>; Thu,  7 Apr 2016 13:20:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=virtualized-org.20150623.gappssmtp.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 vaSxgcz5DiHG for <ietf@ietfa.amsl.com>; Thu,  7 Apr 2016 13:20:37 -0700 (PDT)
Received: from mail-wm0-x233.google.com (mail-wm0-x233.google.com [IPv6:2a00:1450:400c:c09::233]) (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 40F1812D5AB for <ietf@ietf.org>; Thu,  7 Apr 2016 13:20:30 -0700 (PDT)
Received: by mail-wm0-x233.google.com with SMTP id v188so68280911wme.1 for <ietf@ietf.org>; Thu, 07 Apr 2016 13:20:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=virtualized-org.20150623.gappssmtp.com; s=20150623; h=subject:mime-version:from:in-reply-to:date:cc:message-id:references :to; bh=+Ac6BTve6Phdb7bI0KlSa+w2hn8Rldgxzy73deZkkWc=; b=ziXav0z9PRqcec5Cko9DMevj7a1VmQXySlPE8Im50Tz92tugXo1QWKMQQZ1QJt6xOC JBycNT69+vJIwoH4jZwm4aKQGJ80eyr+Gux/ArBxSMJnCWaHL6FavmbLUrTScqaAV97i FRZmmWBBQh356wjOKLN1hBbN9HXWVErAhls5RDVO7xkjNoRUx7KngVYz+xkRlUXgm3+6 hGK3rIqMV68XmJyy0ncTzm4wBv3WcHKcqlb+2yR6qq/4efzN5SwbY5wVj638qVU7L11x W3gTiqBv2VOBGGoUZoV5ef3KsRQrOWnngbLUcweJr+JVNMVVqtXzw+CbyGDRPCpzBMh9 kEKQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:mime-version:from:in-reply-to:date:cc :message-id:references:to; bh=+Ac6BTve6Phdb7bI0KlSa+w2hn8Rldgxzy73deZkkWc=; b=KqU++Rpdhvhnu32NoAY2EcknI+E6Fa6vRU/yKVMYU7//8R9qn4NMREhjsFGBHNKGjC YrmlOAsCD2otlOhthmf5Coko3OXXcc6rla3g3V70Dv+ysuxjS/pEz5UAU++9CS35ZjjM p587ypK7/mp46GSB6FlUFRwStoM7GnMggHlkAyllhAS1YoEJKaAWNDrRpIwQqRvs6xoc CEOen0HeTEc6D5Rjqv35pEea9CvKRQ5WUTcS3g2gDe8CTJ/U8mLawqNc8mSktgNx3kJf DHNUlmi/SowheyZC18TWoEyTzyBtV+qqwxT3Cx2qrDrI1nqhCVCbR6L+tJb6XtWv+NJX JLqw==
X-Gm-Message-State: AD7BkJIyFYhJ4piJ91HL1HPu4qs5ABxRi9JB8hFp1n7dnHjRanTcib4K/oREr2HcS6u0/w==
X-Received: by 10.28.189.133 with SMTP id n127mr6301989wmf.5.1460060428683; Thu, 07 Apr 2016 13:20:28 -0700 (PDT)
Received: from ?IPv6:2001:67c:370:176:46f:484f:5b6f:8947? ([2001:67c:370:176:46f:484f:5b6f:8947]) by smtp.gmail.com with ESMTPSA id d2sm10107978wjf.28.2016.04.07.13.20.25 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 07 Apr 2016 13:20:27 -0700 (PDT)
Subject: Re: Concerns about Singapore
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Content-Type: multipart/signed; boundary="Apple-Mail=_308B2572-4623-4867-8AFD-498D24553BFE"; protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail 2.6b2
From: David Conrad <drc@virtualized.org>
In-Reply-To: <CAB75xn6fmj84ROUtG5eUB3GerHx83hrEr3w5vSADY_g=BRg5FA@mail.gmail.com>
Date: Thu, 7 Apr 2016 17:20:22 -0300
Message-Id: <9B723FB0-6B93-4C85-ADD9-D423F873CF08@virtualized.org>
References: <0D914666-C3D4-4CCE-AD5E-4E5B34EA1A73@piuha.net> <20160407182936.GA21340@pfrc.org> <CAB75xn780nNDjGa_Cc222J20-+1CCHt09Xp8KHzaK=n0xx51pg@mail.gmail.com> <5706B100.9040509@mnt.se> <CAB75xn6fmj84ROUtG5eUB3GerHx83hrEr3w5vSADY_g=BRg5FA@mail.gmail.com>
To: Dhruv Dhody <dhruv.ietf@gmail.com>
X-Mailer: Apple Mail (2.3124)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/p-8ybxSHJgLxr8Vkvqz5MHOoFiQ>
Cc: "ietf@ietf.org 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, 07 Apr 2016 20:20:39 -0000

--Apple-Mail=_308B2572-4623-4867-8AFD-498D24553BFE
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_DA7A429E-F048-4834-BBC0-60B60D0C5119"


--Apple-Mail=_DA7A429E-F048-4834-BBC0-60B60D0C5119
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

> =E2=80=8BNo, I meant that IETF would be doing a disservice to a large =
part of the world (that has on its books these laws).

For reference:

http://76crimes.com/76-countries-where-homosexuality-is-illegal/

(haven't verified, but I read it on the Internet so it must be true)

Regards,
-drc


--Apple-Mail=_DA7A429E-F048-4834-BBC0-60B60D0C5119
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D""><div><blockquote type=3D"cite" class=3D""><div class=3D""><div =
dir=3D"ltr" class=3D""><div class=3D"gmail_extra"><div =
class=3D"gmail_quote"><div class=3D""><div class=3D"gmail_default" =
style=3D"font-family:&quot;trebuchet =
ms&quot;,sans-serif;color:rgb(76,17,48)">=E2=80=8BNo, I meant that IETF =
would be doing a disservice to a large part of the world (that has on =
its books these laws). =
</div></div></div></div></div></div></blockquote><div><br =
class=3D""></div><div>For reference:</div><div><br =
class=3D""></div><div><a =
href=3D"http://76crimes.com/76-countries-where-homosexuality-is-illegal/" =
class=3D"">http://76crimes.com/76-countries-where-homosexuality-is-illegal=
/</a></div><div><br class=3D""></div><div>(haven't verified, but I read =
it on the Internet so it must be true)</div><div><br =
class=3D""></div><div>Regards,</div><div>-drc</div><div><br =
class=3D""></div></div></body></html>=

--Apple-Mail=_DA7A429E-F048-4834-BBC0-60B60D0C5119--

--Apple-Mail=_308B2572-4623-4867-8AFD-498D24553BFE
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQEcBAEBCgAGBQJXBsEGAAoJENV6ebf0/4rXGMQH/2p6lMy5ier+ymfDWWVmliQl
D151hfOYGD4aKHFJwHVvuCVXs+ppSaiDrnkVO5tGC3eGxrNBP2tJDnXwpg0m1Hz/
EccTHW/w3mRoFJh9jLPZ5O/4y22KS0WGkcHwiDiWCjWoH3beLeRkl9tBKEGcGL37
iHcsqyO/kwKi2+0dkGE8NYdlIHK4tU6ubrrYsJuVeWil0fslJ1gPelC2dpg+LEHe
ze5qMiUR3jQPcaJQKCnN1bcw4VpNFWwYhQHpNEiFyvpYIe/auQvTubGp+cmNZ8DS
cDbr65Ovfa3ntUpmdNePPjG2G7cv0x18BYRoB8Sc+oL25Jh3ImlG7CFP8KEi+CY=
=Uv6q
-----END PGP SIGNATURE-----

--Apple-Mail=_308B2572-4623-4867-8AFD-498D24553BFE--


From nobody Thu Apr  7 13:45:14 2016
Return-Path: <melinda.shore@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 6711112D10C for <ietf@ietfa.amsl.com>; Thu,  7 Apr 2016 13:45:09 -0700 (PDT)
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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 AJ_a9TBThFcG for <ietf@ietfa.amsl.com>; Thu,  7 Apr 2016 13:45:01 -0700 (PDT)
Received: from mail-ig0-x22c.google.com (mail-ig0-x22c.google.com [IPv6:2607:f8b0:4001:c05::22c]) (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 C034C12D55A for <ietf@ietf.org>; Thu,  7 Apr 2016 13:45:01 -0700 (PDT)
Received: by mail-ig0-x22c.google.com with SMTP id kb1so22461043igb.0 for <ietf@ietf.org>; Thu, 07 Apr 2016 13:45: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:date:message-id:subject:from:to :cc; bh=+KQeCyZ3oXszJ7BaFvo57pGwILSavxAxwoepxq5COKo=; b=sXkmKYcBS4+dedWXKdp7lCHCi9piZhVowptRB9VmYl93MLxXP6LCTzxkAyoyV6AvQJ ToOzK3wJ3FC9ULGIp3Ymcx9HWOJg4tUVcxole9V3EX6iVE1/O65G7r/E8fFFvpe9z6/T tnPf83iX57bLLfzQ1mxMKxJmrCkiSbJEZTnuSn4ihCrtwMKMZwio6tixrXeFW2z+co8j VpfHqGePEebQgWeSG7NBgZlMLs9ECJ1GU1dbd4X8798qYLrpfmgntsEl3i+m77AQ+Av8 mxKKDbHSXmUwEO5jjx1mC8Q0sZFFLvvaNJycULfWJsv+4RA/PStkSh/k8I6tqg62S720 qeNA==
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:date :message-id:subject:from:to:cc; bh=+KQeCyZ3oXszJ7BaFvo57pGwILSavxAxwoepxq5COKo=; b=GoNCnLD7MHDmrsuDxtD1+FWmCiMfIL/mS9SEoXly7uQXOZgqJIjPrihmGLdrMLhhMd T7cB3UmLIjDIi0X1TQ+YapOfdGU7qFrO39PDoyk/pQ1lJyI7VAl6i/ZuZC5bBjpSR0+s lAubjgT2TNHI2c7zHBr7gKZIQ9UzdS3RVXLzUHAREOOy84dbQfzbp76OyDNt+B1Yc6rL sO8//6bOHN4BsWrT1wmHy7D+ZmZBm+U3KFtpgkvKFf0j6ChmIOvDaNDpij4TsAThB/TP g4FEzNc3JsLgu7FTzNjTMQ55Eoj2WEsVJgKuYSkSD4KQprTE76SxsoLoRLlgUOfsTX4q UeWw==
X-Gm-Message-State: AD7BkJIHS6UN+yOLzm2qalyuH1iJoZCd2y48yua6+5yE8Zq1IV1yZpVnyE8AL1LrykUX5hov4tprU5XsqJbWnA==
MIME-Version: 1.0
X-Received: by 10.50.137.66 with SMTP id qg2mr28947495igb.25.1460061901095; Thu, 07 Apr 2016 13:45:01 -0700 (PDT)
Received: by 10.50.205.7 with HTTP; Thu, 7 Apr 2016 13:45:00 -0700 (PDT)
Received: by 10.50.205.7 with HTTP; Thu, 7 Apr 2016 13:45:00 -0700 (PDT)
In-Reply-To: <CAKRbAfB=n5kNGKoQLZE1Dq1TVpZ+39c+ddW7HLnTQY_QZQ7zbQ@mail.gmail.com>
References: <0D914666-C3D4-4CCE-AD5E-4E5B34EA1A73@piuha.net> <20160407182936.GA21340@pfrc.org> <CAB75xn780nNDjGa_Cc222J20-+1CCHt09Xp8KHzaK=n0xx51pg@mail.gmail.com> <5706B100.9040509@mnt.se> <CAB75xn6fmj84ROUtG5eUB3GerHx83hrEr3w5vSADY_g=BRg5FA@mail.gmail.com> <9B723FB0-6B93-4C85-ADD9-D423F873CF08@virtualized.org> <CAKRbAfB=n5kNGKoQLZE1Dq1TVpZ+39c+ddW7HLnTQY_QZQ7zbQ@mail.gmail.com>
Date: Thu, 7 Apr 2016 12:45:00 -0800
Message-ID: <CAKRbAfDJxtgMiyQKWt9ppcJVFexkhgVEnCApdy_9GDOWtLOMGA@mail.gmail.com>
Subject: Re: Concerns about Singapore
From: Melinda Shore <melinda.shore@gmail.com>
To: David Conrad <drc@virtualized.org>
Content-Type: multipart/alternative; boundary=001a11c3c2ccf72df7052feb26f3
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/ATWGQbBmElXUNb3wh6t2mzgBGA0>
Cc: 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, 07 Apr 2016 20:45:09 -0000

--001a11c3c2ccf72df7052feb26f3
Content-Type: text/plain; charset=UTF-8

I've been thinking quite a bit about that line, and I think that in a lot
of those marginal cases it comes down to questions about public
accommodation and the ability to move freely.  It seems to me that when
there's a legitimate question about whether or not our participants will be
able to check into a meeting hotel with his or her family, were have a
problem that goes beyond individual conscience.

Melinda

--001a11c3c2ccf72df7052feb26f3
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<p dir=3D"ltr">I&#39;ve been thinking quite a bit about that line, and I th=
ink that in a lot of those marginal cases it comes down to questions about =
public accommodation and the ability to move freely.=C2=A0 It seems to me t=
hat when there&#39;s a legitimate question about whether or not our partici=
pants will be able to check into a meeting hotel with his or her family, we=
re have a problem that goes beyond individual conscience.</p>
<p dir=3D"ltr">Melinda</p>

--001a11c3c2ccf72df7052feb26f3--


From nobody Thu Apr  7 13:48:57 2016
Return-Path: <leifj@mnt.se>
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 C5A5012D55A for <ietf@ietfa.amsl.com>; Thu,  7 Apr 2016 13:48:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mnt-se.20150623.gappssmtp.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 PdJ6RK_R4VHS for <ietf@ietfa.amsl.com>; Thu,  7 Apr 2016 13:48:54 -0700 (PDT)
Received: from mail-qg0-x22f.google.com (mail-qg0-x22f.google.com [IPv6:2607:f8b0:400d:c04::22f]) (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 EECCA12D10C for <ietf@ietf.org>; Thu,  7 Apr 2016 13:48:53 -0700 (PDT)
Received: by mail-qg0-x22f.google.com with SMTP id j35so74417111qge.0 for <ietf@ietf.org>; Thu, 07 Apr 2016 13:48:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mnt-se.20150623.gappssmtp.com; s=20150623; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding; bh=Ei5S3bVo7V6d2wVYrVeMVH3Q3TFTMfJpDIaijHSoV20=; b=bPvQ/D0KBKYLmbLDbLcG4Rrj3J1TRAgQ9XDhe8Jz1gGrMmya1hRvi01oWhuYRU8XkH tSVy7FQwMJi6dLrKP5a6RiUJWfbJY+LZj8b3RpoDTMCj2evPKPKaSaVgnStzWTvpLKMA zkZp6AoQ4dwoT+uYiQ3AgfRWS2pZWhjUEBVOw5qurknTnU8oaoPANfxPwMxv9MtfxrOw Yn8PxorB5iV+xNKFyJ7Z8qE9gjhEAu7DXKHa4K6aYO2ROIJmAeT3CrGq9XILFxvJycBl WtX/nDbqXtxCFtb+mIJuWzMYMOiags3c+fm6g4DWLtmFCX9aMVmkgb+wtG4ENDDLPXbH PKAA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=Ei5S3bVo7V6d2wVYrVeMVH3Q3TFTMfJpDIaijHSoV20=; b=NQ3Q19H5f5u6X6EK/nrIssdoEyzEQhQPEjDBtgG3GIExy6ZLPSyLE1rhln/K9MtFJ0 6tM/88i0l9q8gKjqUQoXliFQZMOOhFERnytX6QKfu3j6x2cW+3U1W+IEq5ztJvs17jg0 eQ5U03u+Vn6gK2rb5eaMWjscTAVOjNTgUaoChoL/2/3AfYkFVPCeQdwJVEApw6RPEykX jsID90DSRHDmA0pvcIYh6XDovtvIV9y1nV4UbYB6pBbC5k68MKVZOaLmpRpYA8WZWqE1 kWhXMmh9yKvpBzS6acFM1bOaPYdcQbjnLcW1kp4HHoK+bh4UOb9TH7bQz6/6v3FjaBfd byCA==
X-Gm-Message-State: AD7BkJIMBr9f4EFnFjymmegdiC82T3Y7we/tCJ+ivayA+skRm3liqmY1tL9bhkUPMAPltg==
X-Received: by 10.140.105.198 with SMTP id c64mr6722422qgf.94.1460062132966; Thu, 07 Apr 2016 13:48:52 -0700 (PDT)
Received: from [31.133.153.155] (dhcp-999b.meeting.ietf.org. [31.133.153.155]) by smtp.googlemail.com with ESMTPSA id b66sm4103303qhb.48.2016.04.07.13.48.51 for <ietf@ietf.org> (version=TLSv1/SSLv3 cipher=OTHER); Thu, 07 Apr 2016 13:48:51 -0700 (PDT)
Subject: Re: Concerns about Singapore
To: ietf@ietf.org
References: <0D914666-C3D4-4CCE-AD5E-4E5B34EA1A73@piuha.net> <20160407182936.GA21340@pfrc.org> <CAB75xn780nNDjGa_Cc222J20-+1CCHt09Xp8KHzaK=n0xx51pg@mail.gmail.com> <5706B100.9040509@mnt.se> <CAB75xn6fmj84ROUtG5eUB3GerHx83hrEr3w5vSADY_g=BRg5FA@mail.gmail.com> <5706BA40.3060005@mnt.se> <alpine.DEB.2.02.1604072157240.31096@uplift.swm.pp.se>
From: Leif Johansson <leifj@mnt.se>
Message-ID: <5706C7B1.3040203@mnt.se>
Date: Thu, 7 Apr 2016 22:48:49 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0
MIME-Version: 1.0
In-Reply-To: <alpine.DEB.2.02.1604072157240.31096@uplift.swm.pp.se>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/MVHl6FYBfJ1-CHfHNag9nQuTwTc>
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, 07 Apr 2016 20:48:56 -0000

>> Where do you draw the line then?
> 
> I think it's impossible to draw a firm line. Most of it is grey area.
> 

there are some things none of us would be ok with I think

finding endless examples of "yeah but what about laws against jaywalking
over here in Podunk" doesn't help as we are trying to determine what is
clearly beyond the pale.

> I'm sure I could come up with arguments why we should not go to USA or
> Sweden for our meetings, because neither place if perfect.

prove it :-)


From nobody Thu Apr  7 13:49:47 2016
Return-Path: <johnl@taugh.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 9E36412D10C for <ietf@ietfa.amsl.com>; Thu,  7 Apr 2016 13:49:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] 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 U7Wkzm-XryRF for <ietf@ietfa.amsl.com>; Thu,  7 Apr 2016 13:49:44 -0700 (PDT)
Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EE38D12D0AC for <ietf@ietf.org>; Thu,  7 Apr 2016 13:49:43 -0700 (PDT)
Received: (qmail 89311 invoked from network); 7 Apr 2016 20:49:43 -0000
Received: from unknown (64.57.183.18) by mail1.iecc.com with QMQP; 7 Apr 2016 20:49:43 -0000
Date: 7 Apr 2016 20:38:11 -0000
Message-ID: <20160407203811.54154.qmail@ary.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: "We did not know" is not a good excuse
In-Reply-To: <DAC6168972FB4273973AC87E@JcK-HP8200.jck.com>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/hxqkzh8DkzwE_4edu0cgMIrE4LY>
Cc: john-ietf@jck.com
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, 07 Apr 2016 20:49:45 -0000

>My apologies... bad example.   I was, however, thinking less of
>the city area to country area ratio than about the "probably
>only one plausible city in the country to hold an IETF-sized
>meeting" issue.    I should have been more clear about that or
>chosen a better example (or, more likely, both).  

Unless the country is so small that there's only one plausible meeting
hotel, that still doesn't strike me as a problem.

So if they said they were thinking about the Bahamas, that could be a
problem, anywhere else, not so much.

R's,
John


From nobody Thu Apr  7 13:51:53 2016
Return-Path: <dhc@dcrocker.net>
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 B77B412D6E4 for <ietf@ietfa.amsl.com>; Thu,  7 Apr 2016 13:51:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] 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 Pe8STeK7faTV for <ietf@ietfa.amsl.com>; Thu,  7 Apr 2016 13:51:46 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 54BEA12D0AC for <ietf@ietf.org>; Thu,  7 Apr 2016 13:51:46 -0700 (PDT)
Received: from [192.168.1.168] (76-218-10-206.lightspeed.sntcca.sbcglobal.net [76.218.10.206]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id u37Kpjqv010761 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Thu, 7 Apr 2016 13:51:45 -0700
Subject: Re: "We did not know" is not a good excuse
To: John Levine <johnl@taugh.com>, ietf@ietf.org
References: <20160407203811.54154.qmail@ary.lan>
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
Message-ID: <5706C85F.6050809@dcrocker.net>
Date: Thu, 7 Apr 2016 13:51:43 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2
MIME-Version: 1.0
In-Reply-To: <20160407203811.54154.qmail@ary.lan>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Thu, 07 Apr 2016 13:51:45 -0700 (PDT)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/z6g7iSoOSATgr1Wci_7GB-tiYYY>
Cc: john-ietf@jck.com
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: dcrocker@bbiw.net
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, 07 Apr 2016 20:51:52 -0000

On 4/7/2016 1:38 PM, John Levine wrote:
> Unless the country is so small that there's only one plausible meeting
> hotel, that still doesn't strike me as a problem.


IETF meeting venue requirements are sufficiently unusual that, in fact, 
there often are /very/ few choices within many countries.

d/


-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net


From nobody Thu Apr  7 13:52:52 2016
Return-Path: <mcr+ietf@sandelman.ca>
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 C4B9112D701 for <ietf@ietfa.amsl.com>; Thu,  7 Apr 2016 13:52:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Level: 
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 eabmscIi54eU for <ietf@ietfa.amsl.com>; Thu,  7 Apr 2016 13:52:48 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C5D4E12D608 for <ietf@ietf.org>; Thu,  7 Apr 2016 13:52:48 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id 52AAC2009E for <ietf@ietf.org>; Thu,  7 Apr 2016 16:56:24 -0400 (EDT)
Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id A411163755 for <ietf@ietf.org>; Thu,  7 Apr 2016 16:52:47 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: ietf <ietf@ietf.org>
Subject: Re: Qualifying for NomCom
In-Reply-To: <CAL0qLwZHGa5OvSmZ=bTd6AWchsm4r=QaJn2nPqD+YjeWPmH9pA@mail.gmail.com>
References: <CAL0qLwY0FuDp5=RMFEhUMtkK=XNDxX2dogvVY7+OSy88jrrvOQ@mail.gmail.com> <CAPt1N1=SYpo-CiHoc07Ukb04Kb1LGV2=BPPyRLUsaqyLM9Hbwg@mail.gmail.com> <CAL0qLwbhYRqw7fXHzYY0=W-CpmeHeDdaZx3z2Qg0cA2aMrmVwg@mail.gmail.com> <CAPt1N1nqmC7NJyg2M6Na8vUj8T-qObO-1gHFEXZzrobb3oOQhA@mail.gmail.com> <CAL0qLwZHGa5OvSmZ=bTd6AWchsm4r=QaJn2nPqD+YjeWPmH9pA@mail.gmail.com>
X-Mailer: MH-E 8.6; nmh 1.6+dev; GNU Emacs 24.4.2
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Thu, 07 Apr 2016 16:52:47 -0400
Message-ID: <24691.1460062367@obiwan.sandelman.ca>
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/vckBVUZ9PjF31SbqR-uNu9sZ3u8>
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, 07 Apr 2016 20:52:51 -0000

--=-=-=
Content-Type: text/plain


Murray S. Kucherawy <superuser@gmail.com> wrote:
    >> Right. So that's not what "consensus" means. Suggest you reread
    >> RFC 7282. It's not normative, but I think it's helpful to reread
    >> when you feel that you have failed to find consensus. It contains
    >> some good advice about getting to consensus.

    > Well let's see...

    > "Lack of disagreement is more important than agreement..." check.
    > There was disagreement with the proposals, and no better ones
    > presented available.

    > "Rough consensus is achieved when all issues are addressed, but not
    > necessarily accommodated..." check. I wasn't able to even address the
    > concerns raised, because they were valid, and again there were no
    > solid remedies proposed.

I concur with Murray: there were objections which remained open and
uncontested.

    > On the other hand, I realize now that previous thread went on longer
    > than I remembered, and there was a proposal that we (I, probably)
    > construct an RFC3933-style process experiment and let that run for a
    > while. If it works well, we can codify it by adding it to RFC7437bis.
    > So I'll do that. If anyone wants to volunteer to collaborate on it,
    > please contact me directly.

Yes, let's do that!

It would awesome if we could say definitely that the new rules
contribute to more volunteers before we actually use them.

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-




--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQEVAwUBVwbInICLcPvd0N1lAQLICQgAsWeEWTM3554O1V/KaJeG/nmcvFPy5Vdl
pPFFOrgD8D4noqGtsqGyzSo0jMQ5yh4oC+QBuPkLUgFaPM9LIyyhSvuzNVO1hVLv
nzWRhk0826gjt1yXX4WU/R0tupaXQv+8Bto1G1+MwFMkvd5b2VTYawSgIDXEicL3
NCZK8O7mHJt4M7Tj3crXhdop+lFncL+m0PiYTM/wUE98rDY/p9n1jn8at2ndpxbn
ayBYk+Iku4860iGbuOQOYrgqU7WsF2DiLAfbXKHWpxVLVrocH4ZdV2lIdS1XcoQn
owDQzXLuS5SqsG8UGW846j0AgLpaTrBHDBcL3TMqefSsUGI3lY66lA==
=GKUB
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Thu Apr  7 13:58:19 2016
Return-Path: <harald@alvestrand.no>
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 AF0A712D6E8 for <ietf@ietfa.amsl.com>; Thu,  7 Apr 2016 13:58:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.21
X-Spam-Level: 
X-Spam-Status: No, score=-4.21 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, T_RP_MATCHES_RCVD=-0.01] 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 Zj16cg0seqEf for <ietf@ietfa.amsl.com>; Thu,  7 Apr 2016 13:58:10 -0700 (PDT)
Received: from mork.alvestrand.no (mork.alvestrand.no [158.38.152.117]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7A3CF12D665 for <ietf@ietf.org>; Thu,  7 Apr 2016 13:58:10 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mork.alvestrand.no (Postfix) with ESMTP id A1A3E7C7C75 for <ietf@ietf.org>; Thu,  7 Apr 2016 22:58:08 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at alvestrand.no
Received: from mork.alvestrand.no ([127.0.0.1]) by localhost (mork.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id a0t2itb7WoR2 for <ietf@ietf.org>; Thu,  7 Apr 2016 22:58:07 +0200 (CEST)
Received: from [31.133.178.180] (dhcp-b2b4.meeting.ietf.org [31.133.178.180]) by mork.alvestrand.no (Postfix) with ESMTPSA id 524227C7C74 for <ietf@ietf.org>; Thu,  7 Apr 2016 22:58:07 +0200 (CEST)
Subject: Re: Qualifying for NomCom
To: ietf@ietf.org
References: <CAL0qLwY0FuDp5=RMFEhUMtkK=XNDxX2dogvVY7+OSy88jrrvOQ@mail.gmail.com>
From: Harald Alvestrand <harald@alvestrand.no>
Message-ID: <5706C9DC.9010400@alvestrand.no>
Date: Thu, 7 Apr 2016 22:58:04 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0
MIME-Version: 1.0
In-Reply-To: <CAL0qLwY0FuDp5=RMFEhUMtkK=XNDxX2dogvVY7+OSy88jrrvOQ@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/Gcwq1wZDpAYdfjDALXAxjGzkn3M>
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, 07 Apr 2016 20:58:17 -0000

I liked the suggestion of a process experiment where the Nomcom chair
could accept a volunteer that did not qualify under the current rules,
based on his/her own judgment, possibly with a challenge period (we
already have a challenge period in the procedure).

Once we have a few tens of examples of people who want to serve and the
community doesn't mind being allowed to serve, we can start seeing if we
can find rules that cover them.

Harald

On 04/07/2016 08:11 PM, Murray S. Kucherawy wrote:
> Yes, this again.
>
> I've refreshed RFC7437bis in the datatracker since we're effectively
> between active NomCom periods, so now's a good time to take another
> look at this.
>
> For those that didn't follow along last time, the big showstopper for
> this draft as I have it now had to do with updating the criteria for
> qualifying to serve on the NomCom.  The current draft says:
>
> (1) To qualify, one must have attended three of the last five
> in-person meetings, as it's been for a long time now.
>
> (2) This is regularly criticized as selecting for attendees with the
> support and budget to travel to the meetings, and possibly excludes
> people who make substantial or numerous IETF contributions but
> participate remotely more than in person.
>
> We made previous attempts on this list to come up with new criteria
> given (2) above, but weren't successful at coming to consensus, so I
> took them back out, leaving the text that's there now.  The previous
> thread:
> https://mailarchive.ietf.org/arch/msg/ietf/QHwG1KrQDBK9u0wsfALjPSre-pw
>
> I'd like to take another run at this before the next NomCom really
> gets going.  One suggestion I was given here at IETF 95 is to come up
> with some system that's worth trying, and not over-engineer it to
> protect against gaming or other abuses until such time as such abuse
> is evident.  It might, for example, be sufficient defense to empower
> the NomCom Chair or the IETF Chair (or both) with a "panic button",
> making them able to declare that selection criteria will fall back to
> what we have now if it looks like the proposed new qualification
> system is likely to yield an inappropriate set of selecting NomCom
> members.
>
> Comments welcome.
>
> -MSK


-- 
Surveillance is pervasive. Go Dark.


From nobody Thu Apr  7 14:09:41 2016
Return-Path: <brian.e.carpenter@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 E4DE112D55A for <ietf@ietfa.amsl.com>; Thu,  7 Apr 2016 14:09:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 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, RCVD_IN_DNSWL_LOW=-0.7, 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 qsRnQtug1t7z for <ietf@ietfa.amsl.com>; Thu,  7 Apr 2016 14:09:38 -0700 (PDT)
Received: from mail-pf0-x236.google.com (mail-pf0-x236.google.com [IPv6:2607:f8b0:400e:c00::236]) (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 2ADB012D10C for <ietf@ietf.org>; Thu,  7 Apr 2016 14:09:38 -0700 (PDT)
Received: by mail-pf0-x236.google.com with SMTP id 184so62703505pff.0 for <ietf@ietf.org>; Thu, 07 Apr 2016 14:09:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=subject:to:references:from:organization:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=a2bmTh2/Wgf2g4VC33BGsqvvJp/TZgWFBgiqOqxlr8U=; b=DtO+x2D1TXxUpAC7d2rR1uZIcfplc7dYcohp3zH37nYoaSd4GI19P1TIfMzQoLNTFu +4X3WihWVLQgRHtMIDPNrzjrfnvnsysNQHjaFRl/rNBUsJO0QZjwViXARi3/7PEJncL9 SMExejbB6owekC/oE1dqOHAWJtG1Jba3EGMvYgDTcJEfgwKxLw8vuDCLTXQFBG4sZRlI rsnKq69R3JhHH57NSKDSG27vxAa8/tiryqMDBffR9PXMApcbtAJ8OaruoWhZ4mQZT8BT hOY/9Pnz/y0kX3/8WOfvYhCgV/0JcfvAu/xV06hSb8PrcpgideZ2Wi/exAktFvWIa1YS T31A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=a2bmTh2/Wgf2g4VC33BGsqvvJp/TZgWFBgiqOqxlr8U=; b=Lawli6U+Tytw/kAKHqjxdMbxG/LrQPeyGNt9YrC6OgKCF9Le+T0S6wltxJWMtFq8Th D7GyUq+nv4+NTovTAvKKcZXkzsnrG4h+GcGRq/ESMf6VV+Qq3uM2qG9rjuhJNOFV/mWS fGi4PHLmUpHY+eVaNhP3gksYsVAcN96NEYeBXerWXAjBs6ESi3lsqC83cdIkHV9QWfU3 1V+swAyVPot0AEnVibcFn5Qkg8D15jpf6nCRlsyuDp4/PUKlptM3X5VuGY2F4xWXfxRq nL6d+5R3uoQsi0uvD4lnkXMS7yMhUIN9jMM5iw+07GTR1r1tBUO7Osjxdpn54Vgr4oED km5Q==
X-Gm-Message-State: AD7BkJKVj+BsCrlaUS4f/Tr85BjzaHdkkFxGb2OnI/Se1L/XbKk+2wDHdWsLJhC9rRAzDg==
X-Received: by 10.98.18.195 with SMTP id 64mr7464833pfs.131.1460063377754; Thu, 07 Apr 2016 14:09:37 -0700 (PDT)
Received: from ?IPv6:2406:e007:78d0:1:28cc:dc4c:9703:6781? ([2406:e007:78d0:1:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id l11sm14166746pfb.56.2016.04.07.14.09.34 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 07 Apr 2016 14:09:35 -0700 (PDT)
Subject: Re: Qualifying for NomCom
To: Michael Richardson <mcr+ietf@sandelman.ca>, ietf <ietf@ietf.org>
References: <CAL0qLwY0FuDp5=RMFEhUMtkK=XNDxX2dogvVY7+OSy88jrrvOQ@mail.gmail.com> <CAPt1N1=SYpo-CiHoc07Ukb04Kb1LGV2=BPPyRLUsaqyLM9Hbwg@mail.gmail.com> <CAL0qLwbhYRqw7fXHzYY0=W-CpmeHeDdaZx3z2Qg0cA2aMrmVwg@mail.gmail.com> <CAPt1N1nqmC7NJyg2M6Na8vUj8T-qObO-1gHFEXZzrobb3oOQhA@mail.gmail.com> <CAL0qLwZHGa5OvSmZ=bTd6AWchsm4r=QaJn2nPqD+YjeWPmH9pA@mail.gmail.com> <24691.1460062367@obiwan.sandelman.ca>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <5706CC94.3080804@gmail.com>
Date: Fri, 8 Apr 2016 09:09:40 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.7.0
MIME-Version: 1.0
In-Reply-To: <24691.1460062367@obiwan.sandelman.ca>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/CYx6Wh-zae8XxCZB8ky7zYx2NF8>
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, 07 Apr 2016 21:09:40 -0000

On 08/04/2016 08:52, Michael Richardson wrote:
...
>     > On the other hand, I realize now that previous thread went on longer
>     > than I remembered, and there was a proposal that we (I, probably)
>     > construct an RFC3933-style process experiment and let that run for a
>     > while. If it works well, we can codify it by adding it to RFC7437bis.
>     > So I'll do that. If anyone wants to volunteer to collaborate on it,
>     > please contact me directly.
> 
> Yes, let's do that!
> 
> It would awesome if we could say definitely that the new rules
> contribute to more volunteers before we actually use them.

That's not quite how RFC3933 works. You'd *actually* run the experimental
procedure for (say) one cycle, with automatic reversion to RFC7437 unless
RFC7437bis was approved. I think it's a good idea. A one-year experiment
affects ~half the IESG and IAB seats so is highly unlikely to lead to
disaster.

   Brian


From nobody Thu Apr  7 14:19:46 2016
Return-Path: <laurent.ciavaglia@nokia.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 C3FF712D191 for <ietf@ietfa.amsl.com>; Thu,  7 Apr 2016 14:19:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.92
X-Spam-Level: 
X-Spam-Status: No, score=-6.92 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] 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 FmJMfjR1mkZ2 for <ietf@ietfa.amsl.com>; Thu,  7 Apr 2016 14:19:43 -0700 (PDT)
Received: from smtp-fr.alcatel-lucent.com (fr-hpida-esg-02.alcatel-lucent.com [135.245.210.21]) (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 0C3C112D5E7 for <ietf@ietf.org>; Thu,  7 Apr 2016 14:19:43 -0700 (PDT)
Received: from fr712umx4.dmz.alcatel-lucent.com (unknown [135.245.210.45]) by Websense Email Security Gateway with ESMTPS id 80B6D9ACB147F; Thu,  7 Apr 2016 21:19:37 +0000 (GMT)
Received: from fr712usmtp2.zeu.alcatel-lucent.com (fr712usmtp2.zeu.alcatel-lucent.com [135.239.2.42]) by fr712umx4.dmz.alcatel-lucent.com (GMO-o) with ESMTP id u37LJfFx001809 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 7 Apr 2016 21:19:41 GMT
Received: from FR711WXCHHUB01.zeu.alcatel-lucent.com (fr711wxchhub01.zeu.alcatel-lucent.com [135.239.2.111]) by fr712usmtp2.zeu.alcatel-lucent.com (GMO) with ESMTP id u37LJdx4005115 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 7 Apr 2016 23:19:40 +0200
Received: from [135.224.198.34] (135.239.27.38) by FR711WXCHHUB01.zeu.alcatel-lucent.com (135.239.2.111) with Microsoft SMTP Server (TLS) id 14.3.195.1; Thu, 7 Apr 2016 23:19:39 +0200
Subject: Re: Concerns about Singapore
To: EXT Mikael Abrahamsson <swmike@swm.pp.se>, "ietf@ietf.org Discussion" <ietf@ietf.org>
References: <0D914666-C3D4-4CCE-AD5E-4E5B34EA1A73@piuha.net> <20160407182936.GA21340@pfrc.org> <CAB75xn780nNDjGa_Cc222J20-+1CCHt09Xp8KHzaK=n0xx51pg@mail.gmail.com> <5706B100.9040509@mnt.se> <CAB75xn6fmj84ROUtG5eUB3GerHx83hrEr3w5vSADY_g=BRg5FA@mail.gmail.com> <5706BA40.3060005@mnt.se> <alpine.DEB.2.02.1604072157240.31096@uplift.swm.pp.se>
From: Laurent Ciavaglia <laurent.ciavaglia@nokia.com>
Organization: Bell Labs
Message-ID: <5706CEEA.70402@alcatel-lucent.com>
Date: Thu, 7 Apr 2016 23:19:38 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2
MIME-Version: 1.0
In-Reply-To: <alpine.DEB.2.02.1604072157240.31096@uplift.swm.pp.se>
Content-Type: multipart/alternative; boundary="------------060707060505050508000500"
X-Originating-IP: [135.239.27.38]
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/fgyz9zyJ_uS63dz3sqtzmMt4e-g>
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, 07 Apr 2016 21:19:45 -0000

--------------060707060505050508000500
Content-Type: text/plain; charset="utf-8"; format=flowed
Content-Transfer-Encoding: 7bit

On 07/04/2016 22:00, EXT Mikael Abrahamsson wrote:
> There are no perfect places to go.
Except Minneapolis. ;)

-- Laurent.

--------------060707060505050508000500
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta content="text/html; charset=utf-8" http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#333333">
    On 07/04/2016 22:00, EXT Mikael Abrahamsson wrote:<br>
    <blockquote
      cite="mid:alpine.DEB.2.02.1604072157240.31096@uplift.swm.pp.se"
      type="cite">There are no perfect places to go.</blockquote>
    Except Minneapolis. ;)<br>
    <br>
    <div class="moz-signature">-- Laurent.</div>
  </body>
</html>

--------------060707060505050508000500--


From nobody Thu Apr  7 14:21:15 2016
Return-Path: <superuser@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 33ED512D71D for <ietf@ietfa.amsl.com>; Thu,  7 Apr 2016 14:21:13 -0700 (PDT)
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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 UL_4P_tEmNl7 for <ietf@ietfa.amsl.com>; Thu,  7 Apr 2016 14:21:11 -0700 (PDT)
Received: from mail-vk0-x233.google.com (mail-vk0-x233.google.com [IPv6:2607:f8b0:400c:c05::233]) (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 8DC8F12D65D for <ietf@ietf.org>; Thu,  7 Apr 2016 14:21:08 -0700 (PDT)
Received: by mail-vk0-x233.google.com with SMTP id e185so115894050vkb.1 for <ietf@ietf.org>; Thu, 07 Apr 2016 14:21:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=yb5Q6aEwGesqrwsDDZSJa3U+zwUNEKzJOCjrm+mGpbE=; b=qaINyWKN0Q4RizzgNe5nhYFjSoKctHzTHiS7uv/3+iGxWJ8QN3I/2Rt8Cari/v8Ehq GPZ/EvtndTS5PknLW/dt0o/xVFefyLDesSzuxBqAQ4c2TwchRJiwT99iNmLbDJFTHigr saQ4jL8EfnprGkBxdJ++z599lec0LVRTjqFEXdOMnxBeK2X/Sf4vCOHJW1rGqAr+qCMs 9poIXdMXW3zNGWYJV4y0d8VWTq3eCTGoBVEYcK5/4bs7VO7wjuvxam29FZFhhD2kCgJH IqZa11v306hHNgHnGJlzCtMZxtobQQlbMurmYRvC2qGZ3Ne680LiZjd87g1M+zK5Uorg vTEg==
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:date :message-id:subject:from:to:cc; bh=yb5Q6aEwGesqrwsDDZSJa3U+zwUNEKzJOCjrm+mGpbE=; b=VDuHCcmcTYmq18JVv1Y6nVhcGnm6CZqpZ6FCfqaFAZGEz4uOZDDYs0gnxPwDMkSfep uXJUsr/qRehZ7nlpYe/1vf4s3MyV99TOiTNrTY9SWQy0vNs3tiy9Zj3tOmww7TbeRDWk XkX+Wp1Z1bx31MJ0mKgZyMcojitzG6eYFLkfgJVaKNZwZgMiMrZJxqVyuFg/GRo+V984 f33lPhjE3WVuGIb+r0h9ZK4yBt5zYPDqcF+y0n3OVi1z7MM98zL878tyqxTMK9UhUJsm wMLEaLCNWMBculRBKROH89IwYswngw2YpP9eFFY4JkIUpDqJd0gvurrEA3CrTUbzAhz2 8smg==
X-Gm-Message-State: AD7BkJJ9TD6vwTSQ0rzujtYe7fXA7qgl6tTsAsegP3uOPeQizCox0Ksb/odZ4t4b9hfE2Qvp9hCittgtg3J/rw==
MIME-Version: 1.0
X-Received: by 10.176.1.54 with SMTP id 51mr2428590uak.123.1460064067715; Thu, 07 Apr 2016 14:21:07 -0700 (PDT)
Received: by 10.103.43.5 with HTTP; Thu, 7 Apr 2016 14:21:07 -0700 (PDT)
In-Reply-To: <5706CC94.3080804@gmail.com>
References: <CAL0qLwY0FuDp5=RMFEhUMtkK=XNDxX2dogvVY7+OSy88jrrvOQ@mail.gmail.com> <CAPt1N1=SYpo-CiHoc07Ukb04Kb1LGV2=BPPyRLUsaqyLM9Hbwg@mail.gmail.com> <CAL0qLwbhYRqw7fXHzYY0=W-CpmeHeDdaZx3z2Qg0cA2aMrmVwg@mail.gmail.com> <CAPt1N1nqmC7NJyg2M6Na8vUj8T-qObO-1gHFEXZzrobb3oOQhA@mail.gmail.com> <CAL0qLwZHGa5OvSmZ=bTd6AWchsm4r=QaJn2nPqD+YjeWPmH9pA@mail.gmail.com> <24691.1460062367@obiwan.sandelman.ca> <5706CC94.3080804@gmail.com>
Date: Thu, 7 Apr 2016 18:21:07 -0300
Message-ID: <CAL0qLwYvCpL9wwHL0E33HRbMvcckpad=gV-VYgAomJpCdiSrpg@mail.gmail.com>
Subject: Re: Qualifying for NomCom
From: "Murray S. Kucherawy" <superuser@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Content-Type: multipart/alternative; boundary=001a113c86a81b07b1052feba847
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/eADtbZTdHsrKR4sBhEc6sfM1UZ8>
Cc: Michael Richardson <mcr+ietf@sandelman.ca>, ietf <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, 07 Apr 2016 21:21:13 -0000

--001a113c86a81b07b1052feba847
Content-Type: text/plain; charset=UTF-8

How's this look for starters?

http://blackops.org/~msk/draft-kucherawy-nomcom-procexp.txt

On Thu, Apr 7, 2016 at 6:09 PM, Brian E Carpenter <
brian.e.carpenter@gmail.com> wrote:

> On 08/04/2016 08:52, Michael Richardson wrote:
> ...
> >     > On the other hand, I realize now that previous thread went on
> longer
> >     > than I remembered, and there was a proposal that we (I, probably)
> >     > construct an RFC3933-style process experiment and let that run for
> a
> >     > while. If it works well, we can codify it by adding it to
> RFC7437bis.
> >     > So I'll do that. If anyone wants to volunteer to collaborate on it,
> >     > please contact me directly.
> >
> > Yes, let's do that!
> >
> > It would awesome if we could say definitely that the new rules
> > contribute to more volunteers before we actually use them.
>
> That's not quite how RFC3933 works. You'd *actually* run the experimental
> procedure for (say) one cycle, with automatic reversion to RFC7437 unless
> RFC7437bis was approved. I think it's a good idea. A one-year experiment
> affects ~half the IESG and IAB seats so is highly unlikely to lead to
> disaster.
>
>    Brian
>
>

--001a113c86a81b07b1052feba847
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">How&#39;s this look for starters?<br><br><a href=3D"http:/=
/blackops.org/~msk/draft-kucherawy-nomcom-procexp.txt">http://blackops.org/=
~msk/draft-kucherawy-nomcom-procexp.txt</a><br></div><div class=3D"gmail_ex=
tra"><br><div class=3D"gmail_quote">On Thu, Apr 7, 2016 at 6:09 PM, Brian E=
 Carpenter <span dir=3D"ltr">&lt;<a href=3D"mailto:brian.e.carpenter@gmail.=
com" target=3D"_blank">brian.e.carpenter@gmail.com</a>&gt;</span> wrote:<br=
><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1=
px #ccc solid;padding-left:1ex">On 08/04/2016 08:52, Michael Richardson wro=
te:<br>
...<br>
<span class=3D"">&gt;=C2=A0 =C2=A0 =C2=A0&gt; On the other hand, I realize =
now that previous thread went on longer<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; than I remembered, and there was a proposal th=
at we (I, probably)<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; construct an RFC3933-style process experiment =
and let that run for a<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; while. If it works well, we can codify it by a=
dding it to RFC7437bis.<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; So I&#39;ll do that. If anyone wants to volunt=
eer to collaborate on it,<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; please contact me directly.<br>
&gt;<br>
&gt; Yes, let&#39;s do that!<br>
&gt;<br>
&gt; It would awesome if we could say definitely that the new rules<br>
&gt; contribute to more volunteers before we actually use them.<br>
<br>
</span>That&#39;s not quite how RFC3933 works. You&#39;d *actually* run the=
 experimental<br>
procedure for (say) one cycle, with automatic reversion to RFC7437 unless<b=
r>
RFC7437bis was approved. I think it&#39;s a good idea. A one-year experimen=
t<br>
affects ~half the IESG and IAB seats so is highly unlikely to lead to<br>
disaster.<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
=C2=A0 =C2=A0Brian<br>
<br>
</font></span></blockquote></div><br></div>

--001a113c86a81b07b1052feba847--


From nobody Thu Apr  7 14:22:24 2016
Return-Path: <leifj@mnt.se>
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 9007C12D710 for <ietf@ietfa.amsl.com>; Thu,  7 Apr 2016 14:22:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mnt-se.20150623.gappssmtp.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 TzxT_JBaGdzP for <ietf@ietfa.amsl.com>; Thu,  7 Apr 2016 14:22:19 -0700 (PDT)
Received: from mail-qg0-x231.google.com (mail-qg0-x231.google.com [IPv6:2607:f8b0:400d:c04::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 8C33E12D191 for <ietf@ietf.org>; Thu,  7 Apr 2016 14:22:16 -0700 (PDT)
Received: by mail-qg0-x231.google.com with SMTP id c6so75167968qga.1 for <ietf@ietf.org>; Thu, 07 Apr 2016 14:22:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mnt-se.20150623.gappssmtp.com; s=20150623; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=9RcxrhdCmw2uitDeoxwSst7O9pwP3XK/5WhXAKKGxMA=; b=JddFw97sdRvePZUEXXcnDlHKB2t5yDwnmgWHBHsHdDKFJrW6sPieKzRW10ArabP4yL Q5GuWQnFbp0jEnfzzP6DkIADPTocUQlAehmjbg4hhc28sbgJI2rm90559a9spRugOvrx meLpSR5g7zJafAtJlg+DVCLzsrXGxXILiCvSiPLPwWXoNShorgSLgAYdRwcAUX2qFD/3 5967f4yDyvIGj/hQKewgc6Zg8emq2L40IkHX9dwjhmqvcbQ9j1SRVUgi+m0pBlSJvh1f L2LQ39Y4DztXkTkOX+Ol4dUCZ7Ntc9JOlatdsZmlyaO+io1Tsd/HWMwhE7o60q2/DQAh W/Fw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=9RcxrhdCmw2uitDeoxwSst7O9pwP3XK/5WhXAKKGxMA=; b=SWWfVSKf8YZOg5DvNNqhoSUqWCnM935WcWvVfl+XwIthDwipdmOJvNOwuzXDYb8mqU +zdE+V4CQwXiE5CBlCSDEhv7k7fNB9FD14GfFPFoX5ZIuh6bV8St21KQ4a1M/H4lEOt7 vKHRQyuFDdVrmWHN2y/6INuM1SGzZClxlZy4lKSkiLGyPjpQcD7pYEpYHUPIl/6TVIey gVNWh7qSSliOGhpasAb0Z7HKygby4kY+iGse7rDXx92TN2nkmso7k/o4XjJ1QlMbuyqr IDDj/I+oKU8xJDmpL2IyxBH+3ctrTb+C1Lct7OZVSMWuW7wno0Zc7KpjgKf6RsqwAJMw Y3Mw==
X-Gm-Message-State: AD7BkJJpGnOe+nIfkmIY+u1+USuRdwEOHBrE6DrswbcpzOZURJfZNvztGfOdPOBLJGqs6w==
X-Received: by 10.141.2.198 with SMTP id e189mr7372973qhd.64.1460064135632; Thu, 07 Apr 2016 14:22:15 -0700 (PDT)
Received: from ?IPv6:2001:67c:370:160:e4dc:bf93:4449:ca62? ([2001:67c:370:160:e4dc:bf93:4449:ca62]) by smtp.gmail.com with ESMTPSA id p83sm780177qke.49.2016.04.07.14.22.14 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 07 Apr 2016 14:22:14 -0700 (PDT)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (1.0)
Subject: Re: Concerns about Singapore
From: Leif Johansson <leifj@mnt.se>
X-Mailer: iPhone Mail (13E234)
In-Reply-To: <5706CEEA.70402@alcatel-lucent.com>
Date: Thu, 7 Apr 2016 18:22:13 -0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <D8151E5B-3862-4A77-A3FD-18D63334AA29@mnt.se>
References: <0D914666-C3D4-4CCE-AD5E-4E5B34EA1A73@piuha.net> <20160407182936.GA21340@pfrc.org> <CAB75xn780nNDjGa_Cc222J20-+1CCHt09Xp8KHzaK=n0xx51pg@mail.gmail.com> <5706B100.9040509@mnt.se> <CAB75xn6fmj84ROUtG5eUB3GerHx83hrEr3w5vSADY_g=BRg5FA@mail.gmail.com> <5706BA40.3060005@mnt.se> <alpine.DEB.2.02.1604072157240.31096@uplift.swm.pp.se> <5706CEEA.70402@alcatel-lucent.com>
To: Laurent Ciavaglia <laurent.ciavaglia@nokia.com>
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/nVbeqsr_2Ymn5bRYi5LHEFXf280>
Cc: "ietf@ietf.org 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, 07 Apr 2016 21:22:23 -0000

Skickat fr=C3=A5n min iPhone

> 7 apr. 2016 kl. 18:19 skrev Laurent Ciavaglia <laurent.ciavaglia@nokia.com=
>:
>=20
>> On 07/04/2016 22:00, EXT Mikael Abrahamsson wrote:
>> There are no perfect places to go.
> Except Minneapolis. ;)
>=20
> -- Laurent.

+1=


From nobody Thu Apr  7 14:23:07 2016
Return-Path: <laurent.ciavaglia@nokia.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 1D2EF12D191 for <ietf@ietfa.amsl.com>; Thu,  7 Apr 2016 14:23:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.92
X-Spam-Level: 
X-Spam-Status: No, score=-6.92 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] 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 03rK9x0YWeNH for <ietf@ietfa.amsl.com>; Thu,  7 Apr 2016 14:23:02 -0700 (PDT)
Received: from smtp-fr.alcatel-lucent.com (fr-hpida-esg-02.alcatel-lucent.com [135.245.210.21]) (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 E52D012D65D for <ietf@ietf.org>; Thu,  7 Apr 2016 14:23:00 -0700 (PDT)
Received: from fr712umx4.dmz.alcatel-lucent.com (unknown [135.245.210.45]) by Websense Email Security Gateway with ESMTPS id 247D21D338788; Thu,  7 Apr 2016 21:22:55 +0000 (GMT)
Received: from fr712usmtp2.zeu.alcatel-lucent.com (fr712usmtp2.zeu.alcatel-lucent.com [135.239.2.42]) by fr712umx4.dmz.alcatel-lucent.com (GMO-o) with ESMTP id u37LMwKm005979 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 7 Apr 2016 21:22:58 GMT
Received: from FR711WXCHHUB01.zeu.alcatel-lucent.com (fr711wxchhub01.zeu.alcatel-lucent.com [135.239.2.111]) by fr712usmtp2.zeu.alcatel-lucent.com (GMO) with ESMTP id u37LMvLU008859 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 7 Apr 2016 23:22:58 +0200
Received: from [135.224.198.34] (135.239.27.40) by FR711WXCHHUB01.zeu.alcatel-lucent.com (135.239.2.111) with Microsoft SMTP Server (TLS) id 14.3.195.1; Thu, 7 Apr 2016 23:22:57 +0200
Subject: Re: Concerns about Singapore
To: EXT Leif Johansson <leifj@mnt.se>, <ietf@ietf.org>
References: <0D914666-C3D4-4CCE-AD5E-4E5B34EA1A73@piuha.net> <20160407182936.GA21340@pfrc.org> <CAB75xn780nNDjGa_Cc222J20-+1CCHt09Xp8KHzaK=n0xx51pg@mail.gmail.com> <5706B100.9040509@mnt.se> <CAB75xn6fmj84ROUtG5eUB3GerHx83hrEr3w5vSADY_g=BRg5FA@mail.gmail.com> <5706BA40.3060005@mnt.se> <alpine.DEB.2.02.1604072157240.31096@uplift.swm.pp.se> <5706C7B1.3040203@mnt.se>
From: Laurent Ciavaglia <laurent.ciavaglia@nokia.com>
Organization: Bell Labs
Message-ID: <5706CFB0.2090203@alcatel-lucent.com>
Date: Thu, 7 Apr 2016 23:22:56 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2
MIME-Version: 1.0
In-Reply-To: <5706C7B1.3040203@mnt.se>
Content-Type: multipart/alternative; boundary="------------080208050706060900080905"
X-Originating-IP: [135.239.27.40]
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/SwHF__43ODoZt2ymJqFdlfs9Qfo>
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, 07 Apr 2016 21:23:05 -0000

--------------080208050706060900080905
Content-Type: text/plain; charset="utf-8"; format=flowed
Content-Transfer-Encoding: 7bit



On 07/04/2016 22:48, EXT Leif Johansson wrote:
[...]
>> I'm sure I could come up with arguments why we should not go to USA or
>> Sweden for our meetings, because neither place if perfect.
> prove it :-)

death penalty.
firearm death rate.
D. Trump

--Laurent.

--------------080208050706060900080905
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta content="text/html; charset=utf-8" http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#333333">
    <br>
    <br>
    <div class="moz-cite-prefix">On 07/04/2016 22:48, EXT Leif Johansson
      wrote:<br>
    </div>
    [...] <br>
    <blockquote cite="mid:5706C7B1.3040203@mnt.se" type="cite">
      <blockquote type="cite">
        <pre wrap="">I'm sure I could come up with arguments why we should not go to USA or
Sweden for our meetings, because neither place if perfect.
</pre>
      </blockquote>
      <pre wrap="">
prove it :-)
</pre>
    </blockquote>
    <br>
    death penalty.<br>
    firearm death rate.<br>
    D. Trump<br>
    <br>
    --Laurent.<br>
  </body>
</html>

--------------080208050706060900080905--


From nobody Thu Apr  7 14:23:53 2016
Return-Path: <jared@puck.nether.net>
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 D3A0212D710 for <ietf@ietfa.amsl.com>; Thu,  7 Apr 2016 14:23:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.212
X-Spam-Level: 
X-Spam-Status: No, score=-4.212 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 Q6xvj83rMEGy for <ietf@ietfa.amsl.com>; Thu,  7 Apr 2016 14:23:50 -0700 (PDT)
Received: from puck.nether.net (puck.nether.net [204.42.254.5]) by ietfa.amsl.com (Postfix) with ESMTP id 7881912D191 for <ietf@ietf.org>; Thu,  7 Apr 2016 14:23:50 -0700 (PDT)
Received: from [192.168.1.13] (unknown [190.174.142.189]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by puck.nether.net (Postfix) with ESMTPSA id 6EDCC540B1B; Thu,  7 Apr 2016 17:23:46 -0400 (EDT)
Subject: Re: Concerns about Singapore
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Content-Type: text/plain; charset=us-ascii
From: Jared Mauch <jared@puck.nether.net>
In-Reply-To: <D8151E5B-3862-4A77-A3FD-18D63334AA29@mnt.se>
Date: Thu, 7 Apr 2016 17:23:47 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <7E3E34E3-346F-49D4-8030-335E802BE150@puck.nether.net>
References: <0D914666-C3D4-4CCE-AD5E-4E5B34EA1A73@piuha.net> <20160407182936.GA21340@pfrc.org> <CAB75xn780nNDjGa_Cc222J20-+1CCHt09Xp8KHzaK=n0xx51pg@mail.gmail.com> <5706B100.9040509@mnt.se> <CAB75xn6fmj84ROUtG5eUB3GerHx83hrEr3w5vSADY_g=BRg5FA@mail.gmail.com> <5706BA40.3060005@mnt.se> <alpine.DEB.2.02.1604072157240.31096@uplift.swm.pp.se> <5706CEEA.70402@alcatel-lucent.com> <D8151E5B-3862-4A77-A3FD-18D63334AA29@mnt.se>
To: Leif Johansson <leifj@mnt.se>
X-Mailer: Apple Mail (2.3124)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/zb3MUDKh1Auro4mRwZeD_YeN0pQ>
Cc: "ietf@ietf.org 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, 07 Apr 2016 21:23:51 -0000

> On Apr 7, 2016, at 5:22 PM, Leif Johansson <leifj@mnt.se> wrote:
>=20
>> 7 apr. 2016 kl. 18:19 skrev Laurent Ciavaglia =
<laurent.ciavaglia@nokia.com>:
>>=20
>>> On 07/04/2016 22:00, EXT Mikael Abrahamsson wrote:
>>> There are no perfect places to go.
>> Except Minneapolis. ;)
>>=20
>> -- Laurent.
>=20
> +1

lutefisk availability is the tie breaking criteria for mtgvenue?


From nobody Thu Apr  7 14:24:43 2016
Return-Path: <ynir.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 5563612D65D for <ietf@ietfa.amsl.com>; Thu,  7 Apr 2016 14:24:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 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, RCVD_IN_DNSWL_LOW=-0.7, 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 f40Lmzb_ykdK for <ietf@ietfa.amsl.com>; Thu,  7 Apr 2016 14:24:39 -0700 (PDT)
Received: from mail-qg0-x231.google.com (mail-qg0-x231.google.com [IPv6:2607:f8b0:400d:c04::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 E23D812D6F8 for <ietf@ietf.org>; Thu,  7 Apr 2016 14:24:38 -0700 (PDT)
Received: by mail-qg0-x231.google.com with SMTP id f105so51413979qge.2 for <ietf@ietf.org>; Thu, 07 Apr 2016 14:24:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=m9qf3mNnWh85YURsV7daHt8JzuA5Gq4h2a+ePwvjNR0=; b=m320BOPBChSAN63hfKv6kp1rWaCDhQJIEOmHvDbqRnOHPXu6IQFpftpuip3l84u1q6 Q04OfAI7QT9aF8+b+FWYmQNo7CkV7vQ4utHZ9IdMji9rArSJO3cQKSFxaLnCRRzC9ld8 KEzXaT+SMuZLe3cz5rCfInYgBz0Rt1aw6A9JygAUuhxk4qk2uBFlnDPJmfhzcjAHvGu4 MwYdgkcWcc7dSzzY/lPu55iy2xd98rw7+E1e796DaMnu7NF6O3EDkCdkTubSUvQpxhC+ BuLLGQN4+aF75rDmQ53I0zJ0XKZh9eUv94H0bp1CmNlaFkEyEcZtSDvxQ3F6Bmh0+cT5 mrYA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=m9qf3mNnWh85YURsV7daHt8JzuA5Gq4h2a+ePwvjNR0=; b=KELVEFgHi6/jWDTV3fIWgNYWEAF/hFWm0vCJqLk6AaWkbZo0FPE34HfjtLStSuhtuP Mai4MtA/IOFAoW6vMvFB0GHjmDpH2xPO7S4LdqUZhAClSUnzAom1DaqEnXTiuWJ8lcwC PSO7drdwqowZc9sDMOjZiVI2AGij5cTjh0zLnv/R4at6TQGGxvVthJb55jTzTPfhhTKI uSefri2FQmObQSYr4ixzpFOL9tEGsBKZr2zmZpxXZSFMHjjmg2eM869oVZVZRc3WejcL UMj1/wBkaper029pwgZpfAMLDz6iyEFHdbAcfozaw0tVcyG7LJlKKm/9WIS6OnrND0G3 K5JQ==
X-Gm-Message-State: AD7BkJKveRsEegQqsUhXQMQZLJV5cCnsA0zgyj6zL+HovFto94lP5IhWe2o756BV1HkwgQ==
X-Received: by 10.140.83.212 with SMTP id j78mr7019066qgd.83.1460064278095; Thu, 07 Apr 2016 14:24:38 -0700 (PDT)
Received: from ?IPv6:2001:67c:370:160:4431:c36b:c0f:2a25? ([2001:67c:370:160:4431:c36b:c0f:2a25]) by smtp.gmail.com with ESMTPSA id r132sm4159927qhc.41.2016.04.07.14.24.36 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Thu, 07 Apr 2016 14:24:37 -0700 (PDT)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Subject: Re: Concerns about Singapore
From: Yoav Nir <ynir.ietf@gmail.com>
In-Reply-To: <5706C7B1.3040203@mnt.se>
Date: Thu, 7 Apr 2016 18:24:35 -0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <56706297-A6B7-4E1D-B3DC-1B6085696C6C@gmail.com>
References: <0D914666-C3D4-4CCE-AD5E-4E5B34EA1A73@piuha.net> <20160407182936.GA21340@pfrc.org> <CAB75xn780nNDjGa_Cc222J20-+1CCHt09Xp8KHzaK=n0xx51pg@mail.gmail.com> <5706B100.9040509@mnt.se> <CAB75xn6fmj84ROUtG5eUB3GerHx83hrEr3w5vSADY_g=BRg5FA@mail.gmail.com> <5706BA40.3060005@mnt.se> <alpine.DEB.2.02.1604072157240.31096@uplift.swm.pp.se> <5706C7B1.3040203@mnt.se>
To: Leif Johansson <leifj@mnt.se>
X-Mailer: Apple Mail (2.3124)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/tCZoKlYHE5svSjoLVsCUBaNPyHI>
Cc: 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, 07 Apr 2016 21:24:41 -0000

On 7 Apr 2016, at 5:48 PM, Leif Johansson <leifj@mnt.se> wrote:

>> I'm sure I could come up with arguments why we should not go to USA =
or
>> Sweden for our meetings, because neither place if perfect.
>=20
> prove it :-)

Here=E2=80=99s a picture of Swedish Minister for Culture Lena Adelsohn =
Liljeroth cutting a cake:

=
http://assets.vice.com/content-images/contentimage/no-slug/4d991c394e90d21=
b560107314ce36105.jpg

What do I win?


From nobody Thu Apr  7 14:28:08 2016
Return-Path: <bertietf@bwijnen.net>
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 B57AB12D6FB for <ietf@ietfa.amsl.com>; Thu,  7 Apr 2016 14:28:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.62
X-Spam-Level: 
X-Spam-Status: No, score=-2.62 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01] 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 Ns6uOejt5608 for <ietf@ietfa.amsl.com>; Thu,  7 Apr 2016 14:28:04 -0700 (PDT)
Received: from lb2-smtp-cloud3.xs4all.net (lb2-smtp-cloud3.xs4all.net [194.109.24.26]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C85D612D10C for <ietf@ietf.org>; Thu,  7 Apr 2016 14:28:03 -0700 (PDT)
Received: from dhcp-b0ea.meeting.ietf.org ([31.133.176.234]) by smtp-cloud3.xs4all.net with ESMTP id fZTw1s00553osVK01ZU0Kj; Thu, 07 Apr 2016 23:28:02 +0200
Subject: Re: Concerns about Singapore
To: Laurent Ciavaglia <laurent.ciavaglia@nokia.com>, EXT Leif Johansson <leifj@mnt.se>, ietf@ietf.org
References: <0D914666-C3D4-4CCE-AD5E-4E5B34EA1A73@piuha.net> <20160407182936.GA21340@pfrc.org> <CAB75xn780nNDjGa_Cc222J20-+1CCHt09Xp8KHzaK=n0xx51pg@mail.gmail.com> <5706B100.9040509@mnt.se> <CAB75xn6fmj84ROUtG5eUB3GerHx83hrEr3w5vSADY_g=BRg5FA@mail.gmail.com> <5706BA40.3060005@mnt.se> <alpine.DEB.2.02.1604072157240.31096@uplift.swm.pp.se> <5706C7B1.3040203@mnt.se> <5706CFB0.2090203@alcatel-lucent.com>
From: "Bert Wijnen (IETF)" <bertietf@bwijnen.net>
Message-ID: <5706D0DA.3030201@bwijnen.net>
Date: Thu, 7 Apr 2016 23:27:54 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:38.0) Gecko/20100101 Thunderbird/38.7.1
MIME-Version: 1.0
In-Reply-To: <5706CFB0.2090203@alcatel-lucent.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/N5sfcHgGVJ0PKiVDOEd3bbrjbbI>
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, 07 Apr 2016 21:28:05 -0000

+1

On 07/04/16 23:22, Laurent Ciavaglia wrote:
>
>
> On 07/04/2016 22:48, EXT Leif Johansson wrote:
> [...]
>>> I'm sure I could come up with arguments why we should not go to USA or
>>> Sweden for our meetings, because neither place if perfect.
>> prove it :-)
>
> death penalty.
> firearm death rate.
> D. Trump
>
> --Laurent.


From nobody Thu Apr  7 14:57:35 2016
Return-Path: <harald@alvestrand.no>
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 9024312D10C for <ietf@ietfa.amsl.com>; Thu,  7 Apr 2016 14:57:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.909
X-Spam-Level: 
X-Spam-Status: No, score=-1.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, T_RP_MATCHES_RCVD=-0.01] 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 bOV6nShIWmkm for <ietf@ietfa.amsl.com>; Thu,  7 Apr 2016 14:57:23 -0700 (PDT)
Received: from mork.alvestrand.no (mork.alvestrand.no [IPv6:2001:700:1:2::117]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 605C612D72D for <ietf@ietf.org>; Thu,  7 Apr 2016 14:57:23 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mork.alvestrand.no (Postfix) with ESMTP id C0DD17C7C76; Thu,  7 Apr 2016 23:57:21 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at alvestrand.no
Received: from mork.alvestrand.no ([127.0.0.1]) by localhost (mork.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id p7MK9h_FN18i; Thu,  7 Apr 2016 23:57:20 +0200 (CEST)
Received: from [31.133.178.180] (dhcp-b2b4.meeting.ietf.org [31.133.178.180]) by mork.alvestrand.no (Postfix) with ESMTPSA id 641207C7C75; Thu,  7 Apr 2016 23:57:19 +0200 (CEST)
Subject: Re: Qualifying for NomCom
To: "Murray S. Kucherawy" <superuser@gmail.com>, Brian E Carpenter <brian.e.carpenter@gmail.com>
References: <CAL0qLwY0FuDp5=RMFEhUMtkK=XNDxX2dogvVY7+OSy88jrrvOQ@mail.gmail.com> <CAPt1N1=SYpo-CiHoc07Ukb04Kb1LGV2=BPPyRLUsaqyLM9Hbwg@mail.gmail.com> <CAL0qLwbhYRqw7fXHzYY0=W-CpmeHeDdaZx3z2Qg0cA2aMrmVwg@mail.gmail.com> <CAPt1N1nqmC7NJyg2M6Na8vUj8T-qObO-1gHFEXZzrobb3oOQhA@mail.gmail.com> <CAL0qLwZHGa5OvSmZ=bTd6AWchsm4r=QaJn2nPqD+YjeWPmH9pA@mail.gmail.com> <24691.1460062367@obiwan.sandelman.ca> <5706CC94.3080804@gmail.com> <CAL0qLwYvCpL9wwHL0E33HRbMvcckpad=gV-VYgAomJpCdiSrpg@mail.gmail.com>
From: Harald Alvestrand <harald@alvestrand.no>
Message-ID: <5706D7BC.8020800@alvestrand.no>
Date: Thu, 7 Apr 2016 23:57:16 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0
MIME-Version: 1.0
In-Reply-To: <CAL0qLwYvCpL9wwHL0E33HRbMvcckpad=gV-VYgAomJpCdiSrpg@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------060608070309060009040004"
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/_Gnjg9jMKr0_hQiVH7CPT8wXLB4>
Cc: Michael Richardson <mcr+ietf@sandelman.ca>, ietf <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, 07 Apr 2016 21:57:33 -0000

This is a multi-part message in MIME format.
--------------060608070309060009040004
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

On 04/07/2016 11:21 PM, Murray S. Kucherawy wrote:
> How's this look for starters?
>
> http://blackops.org/~msk/draft-kucherawy-nomcom-procexp.txt
> <http://blackops.org/%7Emsk/draft-kucherawy-nomcom-procexp.txt>
>
> On Thu, Apr 7, 2016 at 6:09 PM, Brian E Carpenter
> <brian.e.carpenter@gmail.com <mailto:brian.e.carpenter@gmail.com>> wrot=
e:
>
>     On 08/04/2016 08:52, Michael Richardson wrote:
>     ...
>     >     > On the other hand, I realize now that previous thread went =
on longer
>     >     > than I remembered, and there was a proposal that we (I,
>     probably)
>     >     > construct an RFC3933-style process experiment and let that
>     run for a
>     >     > while. If it works well, we can codify it by adding it to
>     RFC7437bis.
>     >     > So I'll do that. If anyone wants to volunteer to
>     collaborate on it,
>     >     > please contact me directly.
>     >
>     > Yes, let's do that!
>     >
>     > It would awesome if we could say definitely that the new rules
>     > contribute to more volunteers before we actually use them.
>
>     That's not quite how RFC3933 works. You'd *actually* run the
>     experimental
>     procedure for (say) one cycle, with automatic reversion to RFC7437
>     unless
>     RFC7437bis was approved. I think it's a good idea. A one-year
>     experiment
>     affects ~half the IESG and IAB seats so is highly unlikely to lead =
to
>     disaster.
>

Two suggestions:

- Scope objections and aborts to the time between the announcement of
the final list of volunteers and the selection of the comittee. This
closes the loophole that the powers-that-be can look at the selected
nomcom, say "we don't like this group", and force a re-selection by
spuriously objecting.

- The timing says "This experiment is defined to last for one year,
starting and ending with the constitution of the next NomCom after this
document is approved and published." - this is neither determinate nor
grammatical, I think - in particular, it starts and ends at the same time=
=2E

I suggest "This experiment is defined to start with the first call for
volunteers after IESG approval of this document, and ends with the
selection of the nomcom from that volunteer pool. Evaluation of the
experiment will be done after the selection process of the formed nomcom
completes."

Otherwise - go for it!


>
>        Brian
>
>


--=20
Surveillance is pervasive. Go Dark.


--------------060608070309060009040004
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta content="text/html; charset=utf-8" http-equiv="Content-Type">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <div class="moz-cite-prefix">On 04/07/2016 11:21 PM, Murray S.
      Kucherawy wrote:<br>
    </div>
    <blockquote
cite="mid:CAL0qLwYvCpL9wwHL0E33HRbMvcckpad=gV-VYgAomJpCdiSrpg@mail.gmail.com"
      type="cite">
      <div dir="ltr">How's this look for starters?<br>
        <br>
        <a moz-do-not-send="true"
          href="http://blackops.org/%7Emsk/draft-kucherawy-nomcom-procexp.txt">http://blackops.org/~msk/draft-kucherawy-nomcom-procexp.txt</a><br>
      </div>
      <div class="gmail_extra"><br>
        <div class="gmail_quote">On Thu, Apr 7, 2016 at 6:09 PM, Brian E
          Carpenter <span dir="ltr">&lt;<a moz-do-not-send="true"
              href="mailto:brian.e.carpenter@gmail.com" target="_blank">brian.e.carpenter@gmail.com</a>&gt;</span>
          wrote:<br>
          <blockquote class="gmail_quote" style="margin:0 0 0
            .8ex;border-left:1px #ccc solid;padding-left:1ex">On
            08/04/2016 08:52, Michael Richardson wrote:<br>
            ...<br>
            <span class="">&gt;Â  Â  Â &gt; On the other hand, I realize
              now that previous thread went on longer<br>
              &gt;Â  Â  Â &gt; than I remembered, and there was a proposal
              that we (I, probably)<br>
              &gt;Â  Â  Â &gt; construct an RFC3933-style process
              experiment and let that run for a<br>
              &gt;Â  Â  Â &gt; while. If it works well, we can codify it by
              adding it to RFC7437bis.<br>
              &gt;Â  Â  Â &gt; So I'll do that. If anyone wants to
              volunteer to collaborate on it,<br>
              &gt;Â  Â  Â &gt; please contact me directly.<br>
              &gt;<br>
              &gt; Yes, let's do that!<br>
              &gt;<br>
              &gt; It would awesome if we could say definitely that the
              new rules<br>
              &gt; contribute to more volunteers before we actually use
              them.<br>
              <br>
            </span>That's not quite how RFC3933 works. You'd *actually*
            run the experimental<br>
            procedure for (say) one cycle, with automatic reversion to
            RFC7437 unless<br>
            RFC7437bis was approved. I think it's a good idea. A
            one-year experiment<br>
            affects ~half the IESG and IAB seats so is highly unlikely
            to lead to<br>
            disaster.<br>
          </blockquote>
        </div>
      </div>
    </blockquote>
    <br>
    Two suggestions:<br>
    <br>
    - Scope objections and aborts to the time between the announcement
    of the final list of volunteers and the selection of the comittee.
    This closes the loophole that the powers-that-be can look at the
    selected nomcom, say "we don't like this group", and force a
    re-selection by spuriously objecting.<br>
    <br>
    - The timing says "This experiment is defined to last for one year,
    starting and ending with the constitution of the next NomCom after
    this document is approved and published." - this is neither
    determinate nor grammatical, I think - in particular, it starts and
    ends at the same time.<br>
    <br>
    I suggest "This experiment is defined to start with the first call
    for volunteers after IESG approval of this document, and ends with
    the selection of the nomcom from that volunteer pool. Evaluation of
    the experiment will be done after the selection process of the
    formed nomcom completes."<br>
    <br>
    Otherwise - go for it!<br>
    <br>
    <br>
    <meta http-equiv="content-type" content="text/html; charset=utf-8">
    <meta http-equiv="content-type" content="text/html; charset=utf-8">
    <blockquote
cite="mid:CAL0qLwYvCpL9wwHL0E33HRbMvcckpad=gV-VYgAomJpCdiSrpg@mail.gmail.com"
      type="cite">
      <div class="gmail_extra">
        <div class="gmail_quote">
          <blockquote class="gmail_quote" style="margin:0 0 0
            .8ex;border-left:1px #ccc solid;padding-left:1ex">
            <span class="HOEnZb"><font color="#888888"><br>
                Â  Â Brian<br>
                <br>
              </font></span></blockquote>
        </div>
        <br>
      </div>
    </blockquote>
    <br>
    <br>
    <pre class="moz-signature" cols="72">-- 
Surveillance is pervasive. Go Dark.
</pre>
  </body>
</html>

--------------060608070309060009040004--


From nobody Thu Apr  7 15:06:41 2016
Return-Path: <tony@att.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 8A04812D72A for <ietf@ietfa.amsl.com>; Thu,  7 Apr 2016 15:06:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001] 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 xjEP-csmkwEt for <ietf@ietfa.amsl.com>; Thu,  7 Apr 2016 15:06:37 -0700 (PDT)
Received: from mx0a-00191d01.pphosted.com (mx0a-00191d01.pphosted.com [67.231.149.140]) (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 93E8712D5E7 for <ietf@ietf.org>; Thu,  7 Apr 2016 15:06:37 -0700 (PDT)
Received: from pps.filterd (m0049287.ppops.net [127.0.0.1]) by m0049287.ppops.net-00191d01. (8.15.0.59/8.15.0.59) with SMTP id u37M3prr029352; Thu, 7 Apr 2016 18:06:37 -0400
Received: from alpi155.enaf.aldc.att.com (sbcsmtp7.sbc.com [144.160.229.24]) by m0049287.ppops.net-00191d01. with ESMTP id 225xwf1h9n-1 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT);  Thu, 07 Apr 2016 18:06:36 -0400
Received: from enaf.aldc.att.com (localhost [127.0.0.1]) by alpi155.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id u37M6ZFw017379; Thu, 7 Apr 2016 18:06:35 -0400
Received: from mlpi408.sfdc.sbc.com (mlpi408.sfdc.sbc.com [130.9.128.240]) by alpi155.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id u37M6Rvx017289 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 7 Apr 2016 18:06:31 -0400
Received: from MISOUT7MSGHUBAE.ITServices.sbc.com (MISOUT7MSGHUBAE.itservices.sbc.com [130.9.129.149]) by mlpi408.sfdc.sbc.com (RSA Interceptor); Thu, 7 Apr 2016 22:06:13 GMT
Received: from MISOUT7MSGUSRCG.ITServices.sbc.com ([169.254.7.206]) by MISOUT7MSGHUBAE.ITServices.sbc.com ([130.9.129.149]) with mapi id 14.03.0248.002; Thu, 7 Apr 2016 18:06:12 -0400
From: "HANSEN, TONY L" <tony@att.com>
To: "Murray S. Kucherawy" <superuser@gmail.com>
Subject: Re: Qualifying for NomCom
Thread-Topic: Qualifying for NomCom
Thread-Index: AQHRkPkBaE3TgFgCo0Odl4x3Th89cJ9/E2cAgAABUgCAAAB+AIAABFuAgAAma4CAAAS3AIAAAzOA///JioA=
Date: Thu, 7 Apr 2016 22:06:11 +0000
Message-ID: <5E36120B-6D4E-4C0D-9905-2C698455D395@att.com>
References: <CAL0qLwY0FuDp5=RMFEhUMtkK=XNDxX2dogvVY7+OSy88jrrvOQ@mail.gmail.com> <CAPt1N1=SYpo-CiHoc07Ukb04Kb1LGV2=BPPyRLUsaqyLM9Hbwg@mail.gmail.com> <CAL0qLwbhYRqw7fXHzYY0=W-CpmeHeDdaZx3z2Qg0cA2aMrmVwg@mail.gmail.com> <CAPt1N1nqmC7NJyg2M6Na8vUj8T-qObO-1gHFEXZzrobb3oOQhA@mail.gmail.com> <CAL0qLwZHGa5OvSmZ=bTd6AWchsm4r=QaJn2nPqD+YjeWPmH9pA@mail.gmail.com> <24691.1460062367@obiwan.sandelman.ca> <5706CC94.3080804@gmail.com> <CAL0qLwYvCpL9wwHL0E33HRbMvcckpad=gV-VYgAomJpCdiSrpg@mail.gmail.com>
In-Reply-To: <CAL0qLwYvCpL9wwHL0E33HRbMvcckpad=gV-VYgAomJpCdiSrpg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.110.241.40]
Content-Type: multipart/alternative; boundary="_000_5E36120B6D4E4C0D99052C698455D395attcom_"
MIME-Version: 1.0
X-RSA-Inspected: yes
X-RSA-Classifications: public
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2016-04-07_15:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_policy_notspam policy=outbound_policy 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-1603180000 definitions=main-1604070312
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/bB6vzA0Nub9jTahCMj8pCIBdMnM>
Cc: ietf <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, 07 Apr 2016 22:06:39 -0000

--_000_5E36120B6D4E4C0D99052C698455D395attcom_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

TG9va3MgcHJldHR5IGdvb2QuDQoNClRoZXJlJ3MgYSBmb3VydGggcG9zc2libGUgb3V0Y29tZTog
d2UndmUgZ2F0aGVyZWQgZW5vdWdoIGluZm9ybWF0aW9uIGZyb20gdGhlIGV4cGVyaW1lbnQgdGhh
dCB3ZSBrbm93IHdoYXQgd2Ugd2FudCB0byBkbyBhbmQgZG9uJ3QgbmVlZCB0byByZS1ydW4gYW5v
dGhlciBleHBlcmltZW50IGluIG9yZGVyIHRvIHJldmlzZSA3NDM3Lg0KDQpUb255DQoNCkZyb206
IGlldGYgPGlldGYtYm91bmNlc0BpZXRmLm9yZzxtYWlsdG86aWV0Zi1ib3VuY2VzQGlldGYub3Jn
Pj4gb24gYmVoYWxmIG9mICJNdXJyYXkgUy4gS3VjaGVyYXd5IiA8c3VwZXJ1c2VyQGdtYWlsLmNv
bTxtYWlsdG86c3VwZXJ1c2VyQGdtYWlsLmNvbT4+DQpEYXRlOiBUaHVyc2RheSwgQXByaWwgNywg
MjAxNiBhdCA1OjIxIFBNDQpUbzogQnJpYW4gRSBDYXJwZW50ZXIgPGJyaWFuLmUuY2FycGVudGVy
QGdtYWlsLmNvbTxtYWlsdG86YnJpYW4uZS5jYXJwZW50ZXJAZ21haWwuY29tPj4NCkNjOiBNaWNo
YWVsIFJpY2hhcmRzb24gPG1jcitpZXRmQHNhbmRlbG1hbi5jYTxtYWlsdG86bWNyK2lldGZAc2Fu
ZGVsbWFuLmNhPj4sIGlldGYgPGlldGZAaWV0Zi5vcmc8bWFpbHRvOmlldGZAaWV0Zi5vcmc+Pg0K
U3ViamVjdDogUmU6IFF1YWxpZnlpbmcgZm9yIE5vbUNvbQ0KDQpIb3cncyB0aGlzIGxvb2sgZm9y
IHN0YXJ0ZXJzPw0KDQpodHRwOi8vYmxhY2tvcHMub3JnL35tc2svZHJhZnQta3VjaGVyYXd5LW5v
bWNvbS1wcm9jZXhwLnR4dA0KDQpPbiBUaHUsIEFwciA3LCAyMDE2IGF0IDY6MDkgUE0sIEJyaWFu
IEUgQ2FycGVudGVyIDxicmlhbi5lLmNhcnBlbnRlckBnbWFpbC5jb208bWFpbHRvOmJyaWFuLmUu
Y2FycGVudGVyQGdtYWlsLmNvbT4+IHdyb3RlOg0KT24gMDgvMDQvMjAxNiAwODo1MiwgTWljaGFl
bCBSaWNoYXJkc29uIHdyb3RlOg0KLi4uDQo+ICAgICA+IE9uIHRoZSBvdGhlciBoYW5kLCBJIHJl
YWxpemUgbm93IHRoYXQgcHJldmlvdXMgdGhyZWFkIHdlbnQgb24gbG9uZ2VyDQo+ICAgICA+IHRo
YW4gSSByZW1lbWJlcmVkLCBhbmQgdGhlcmUgd2FzIGEgcHJvcG9zYWwgdGhhdCB3ZSAoSSwgcHJv
YmFibHkpDQo+ICAgICA+IGNvbnN0cnVjdCBhbiBSRkMzOTMzLXN0eWxlIHByb2Nlc3MgZXhwZXJp
bWVudCBhbmQgbGV0IHRoYXQgcnVuIGZvciBhDQo+ICAgICA+IHdoaWxlLiBJZiBpdCB3b3JrcyB3
ZWxsLCB3ZSBjYW4gY29kaWZ5IGl0IGJ5IGFkZGluZyBpdCB0byBSRkM3NDM3YmlzLg0KPiAgICAg
PiBTbyBJJ2xsIGRvIHRoYXQuIElmIGFueW9uZSB3YW50cyB0byB2b2x1bnRlZXIgdG8gY29sbGFi
b3JhdGUgb24gaXQsDQo+ICAgICA+IHBsZWFzZSBjb250YWN0IG1lIGRpcmVjdGx5Lg0KPg0KPiBZ
ZXMsIGxldCdzIGRvIHRoYXQhDQo+DQo+IEl0IHdvdWxkIGF3ZXNvbWUgaWYgd2UgY291bGQgc2F5
IGRlZmluaXRlbHkgdGhhdCB0aGUgbmV3IHJ1bGVzDQo+IGNvbnRyaWJ1dGUgdG8gbW9yZSB2b2x1
bnRlZXJzIGJlZm9yZSB3ZSBhY3R1YWxseSB1c2UgdGhlbS4NCg0KVGhhdCdzIG5vdCBxdWl0ZSBo
b3cgUkZDMzkzMyB3b3Jrcy4gWW91J2QgKmFjdHVhbGx5KiBydW4gdGhlIGV4cGVyaW1lbnRhbA0K
cHJvY2VkdXJlIGZvciAoc2F5KSBvbmUgY3ljbGUsIHdpdGggYXV0b21hdGljIHJldmVyc2lvbiB0
byBSRkM3NDM3IHVubGVzcw0KUkZDNzQzN2JpcyB3YXMgYXBwcm92ZWQuIEkgdGhpbmsgaXQncyBh
IGdvb2QgaWRlYS4gQSBvbmUteWVhciBleHBlcmltZW50DQphZmZlY3RzIH5oYWxmIHRoZSBJRVNH
IGFuZCBJQUIgc2VhdHMgc28gaXMgaGlnaGx5IHVubGlrZWx5IHRvIGxlYWQgdG8NCmRpc2FzdGVy
Lg0KDQogICBCcmlhbg0KDQoNCg==

--_000_5E36120B6D4E4C0D99052C698455D395attcom_
Content-Type: text/html; charset="utf-8"
Content-ID: <9E865BD0CA1EE749815C6925BA71751F@LOCAL>
Content-Transfer-Encoding: base64

PGh0bWw+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIgY29udGVudD0i
dGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjwvaGVhZD4NCjxib2R5IHN0eWxlPSJ3b3JkLXdy
YXA6IGJyZWFrLXdvcmQ7IC13ZWJraXQtbmJzcC1tb2RlOiBzcGFjZTsgLXdlYmtpdC1saW5lLWJy
ZWFrOiBhZnRlci13aGl0ZS1zcGFjZTsgY29sb3I6IHJnYigwLCAwLCAwKTsgZm9udC1zaXplOiAx
NHB4OyBmb250LWZhbWlseTogQ2FsaWJyaSwgc2Fucy1zZXJpZjsiPg0KPGRpdj4NCjxkaXY+TG9v
a3MgcHJldHR5IGdvb2QuPC9kaXY+DQo8ZGl2Pjxicj4NCjwvZGl2Pg0KPGRpdj5UaGVyZSdzIGEg
Zm91cnRoIHBvc3NpYmxlIG91dGNvbWU6IHdlJ3ZlIGdhdGhlcmVkIGVub3VnaCBpbmZvcm1hdGlv
biBmcm9tIHRoZSBleHBlcmltZW50IHRoYXQgd2Uga25vdyB3aGF0IHdlIHdhbnQgdG8gZG8gYW5k
IGRvbid0IG5lZWQgdG8gcmUtcnVuIGFub3RoZXIgZXhwZXJpbWVudCBpbiBvcmRlciB0byByZXZp
c2UgNzQzNy48L2Rpdj4NCjxkaXY+PGJyPg0KPC9kaXY+DQo8ZGl2PjxzcGFuIGNsYXNzPSJBcHBs
ZS10YWItc3BhbiIgc3R5bGU9IndoaXRlLXNwYWNlOnByZSI+PC9zcGFuPlRvbnk8L2Rpdj4NCjwv
ZGl2Pg0KPGRpdj48YnI+DQo8L2Rpdj4NCjxzcGFuIGlkPSJPTEtfU1JDX0JPRFlfU0VDVElPTiI+
DQo8ZGl2IHN0eWxlPSJmb250LWZhbWlseTpDYWxpYnJpOyBmb250LXNpemU6MTJwdDsgdGV4dC1h
bGlnbjpsZWZ0OyBjb2xvcjpibGFjazsgQk9SREVSLUJPVFRPTTogbWVkaXVtIG5vbmU7IEJPUkRF
Ui1MRUZUOiBtZWRpdW0gbm9uZTsgUEFERElORy1CT1RUT006IDBpbjsgUEFERElORy1MRUZUOiAw
aW47IFBBRERJTkctUklHSFQ6IDBpbjsgQk9SREVSLVRPUDogI2I1YzRkZiAxcHQgc29saWQ7IEJP
UkRFUi1SSUdIVDogbWVkaXVtIG5vbmU7IFBBRERJTkctVE9QOiAzcHQiPg0KPHNwYW4gc3R5bGU9
ImZvbnQtd2VpZ2h0OmJvbGQiPkZyb206IDwvc3Bhbj5pZXRmICZsdDs8YSBocmVmPSJtYWlsdG86
aWV0Zi1ib3VuY2VzQGlldGYub3JnIj5pZXRmLWJvdW5jZXNAaWV0Zi5vcmc8L2E+Jmd0OyBvbiBi
ZWhhbGYgb2YgJnF1b3Q7TXVycmF5IFMuIEt1Y2hlcmF3eSZxdW90OyAmbHQ7PGEgaHJlZj0ibWFp
bHRvOnN1cGVydXNlckBnbWFpbC5jb20iPnN1cGVydXNlckBnbWFpbC5jb208L2E+Jmd0Ozxicj4N
CjxzcGFuIHN0eWxlPSJmb250LXdlaWdodDpib2xkIj5EYXRlOiA8L3NwYW4+VGh1cnNkYXksIEFw
cmlsIDcsIDIwMTYgYXQgNToyMSBQTTxicj4NCjxzcGFuIHN0eWxlPSJmb250LXdlaWdodDpib2xk
Ij5UbzogPC9zcGFuPkJyaWFuIEUgQ2FycGVudGVyICZsdDs8YSBocmVmPSJtYWlsdG86YnJpYW4u
ZS5jYXJwZW50ZXJAZ21haWwuY29tIj5icmlhbi5lLmNhcnBlbnRlckBnbWFpbC5jb208L2E+Jmd0
Ozxicj4NCjxzcGFuIHN0eWxlPSJmb250LXdlaWdodDpib2xkIj5DYzogPC9zcGFuPk1pY2hhZWwg
UmljaGFyZHNvbiAmbHQ7PGEgaHJlZj0ibWFpbHRvOm1jciYjNDM7aWV0ZkBzYW5kZWxtYW4uY2Ei
Pm1jciYjNDM7aWV0ZkBzYW5kZWxtYW4uY2E8L2E+Jmd0OywgaWV0ZiAmbHQ7PGEgaHJlZj0ibWFp
bHRvOmlldGZAaWV0Zi5vcmciPmlldGZAaWV0Zi5vcmc8L2E+Jmd0Ozxicj4NCjxzcGFuIHN0eWxl
PSJmb250LXdlaWdodDpib2xkIj5TdWJqZWN0OiA8L3NwYW4+UmU6IFF1YWxpZnlpbmcgZm9yIE5v
bUNvbTxicj4NCjwvZGl2Pg0KPGRpdj48YnI+DQo8L2Rpdj4NCjxkaXY+DQo8ZGl2Pg0KPGRpdiBk
aXI9Imx0ciI+SG93J3MgdGhpcyBsb29rIGZvciBzdGFydGVycz88YnI+DQo8YnI+DQo8YSBocmVm
PSJodHRwOi8vYmxhY2tvcHMub3JnL35tc2svZHJhZnQta3VjaGVyYXd5LW5vbWNvbS1wcm9jZXhw
LnR4dCI+aHR0cDovL2JsYWNrb3BzLm9yZy9+bXNrL2RyYWZ0LWt1Y2hlcmF3eS1ub21jb20tcHJv
Y2V4cC50eHQ8L2E+PGJyPg0KPC9kaXY+DQo8ZGl2IGNsYXNzPSJnbWFpbF9leHRyYSI+PGJyPg0K
PGRpdiBjbGFzcz0iZ21haWxfcXVvdGUiPk9uIFRodSwgQXByIDcsIDIwMTYgYXQgNjowOSBQTSwg
QnJpYW4gRSBDYXJwZW50ZXIgPHNwYW4gZGlyPSJsdHIiPg0KJmx0OzxhIGhyZWY9Im1haWx0bzpi
cmlhbi5lLmNhcnBlbnRlckBnbWFpbC5jb20iIHRhcmdldD0iX2JsYW5rIj5icmlhbi5lLmNhcnBl
bnRlckBnbWFpbC5jb208L2E+Jmd0Ozwvc3Bhbj4gd3JvdGU6PGJyPg0KPGJsb2NrcXVvdGUgY2xh
c3M9ImdtYWlsX3F1b3RlIiBzdHlsZT0ibWFyZ2luOjAgMCAwIC44ZXg7Ym9yZGVyLWxlZnQ6MXB4
ICNjY2Mgc29saWQ7cGFkZGluZy1sZWZ0OjFleCI+DQpPbiAwOC8wNC8yMDE2IDA4OjUyLCBNaWNo
YWVsIFJpY2hhcmRzb24gd3JvdGU6PGJyPg0KLi4uPGJyPg0KPHNwYW4gY2xhc3M9IiI+Jmd0OyZu
YnNwOyAmbmJzcDsgJm5ic3A7Jmd0OyBPbiB0aGUgb3RoZXIgaGFuZCwgSSByZWFsaXplIG5vdyB0
aGF0IHByZXZpb3VzIHRocmVhZCB3ZW50IG9uIGxvbmdlcjxicj4NCiZndDsmbmJzcDsgJm5ic3A7
ICZuYnNwOyZndDsgdGhhbiBJIHJlbWVtYmVyZWQsIGFuZCB0aGVyZSB3YXMgYSBwcm9wb3NhbCB0
aGF0IHdlIChJLCBwcm9iYWJseSk8YnI+DQomZ3Q7Jm5ic3A7ICZuYnNwOyAmbmJzcDsmZ3Q7IGNv
bnN0cnVjdCBhbiBSRkMzOTMzLXN0eWxlIHByb2Nlc3MgZXhwZXJpbWVudCBhbmQgbGV0IHRoYXQg
cnVuIGZvciBhPGJyPg0KJmd0OyZuYnNwOyAmbmJzcDsgJm5ic3A7Jmd0OyB3aGlsZS4gSWYgaXQg
d29ya3Mgd2VsbCwgd2UgY2FuIGNvZGlmeSBpdCBieSBhZGRpbmcgaXQgdG8gUkZDNzQzN2Jpcy48
YnI+DQomZ3Q7Jm5ic3A7ICZuYnNwOyAmbmJzcDsmZ3Q7IFNvIEknbGwgZG8gdGhhdC4gSWYgYW55
b25lIHdhbnRzIHRvIHZvbHVudGVlciB0byBjb2xsYWJvcmF0ZSBvbiBpdCw8YnI+DQomZ3Q7Jm5i
c3A7ICZuYnNwOyAmbmJzcDsmZ3Q7IHBsZWFzZSBjb250YWN0IG1lIGRpcmVjdGx5Ljxicj4NCiZn
dDs8YnI+DQomZ3Q7IFllcywgbGV0J3MgZG8gdGhhdCE8YnI+DQomZ3Q7PGJyPg0KJmd0OyBJdCB3
b3VsZCBhd2Vzb21lIGlmIHdlIGNvdWxkIHNheSBkZWZpbml0ZWx5IHRoYXQgdGhlIG5ldyBydWxl
czxicj4NCiZndDsgY29udHJpYnV0ZSB0byBtb3JlIHZvbHVudGVlcnMgYmVmb3JlIHdlIGFjdHVh
bGx5IHVzZSB0aGVtLjxicj4NCjxicj4NCjwvc3Bhbj5UaGF0J3Mgbm90IHF1aXRlIGhvdyBSRkMz
OTMzIHdvcmtzLiBZb3UnZCAqYWN0dWFsbHkqIHJ1biB0aGUgZXhwZXJpbWVudGFsPGJyPg0KcHJv
Y2VkdXJlIGZvciAoc2F5KSBvbmUgY3ljbGUsIHdpdGggYXV0b21hdGljIHJldmVyc2lvbiB0byBS
RkM3NDM3IHVubGVzczxicj4NClJGQzc0MzdiaXMgd2FzIGFwcHJvdmVkLiBJIHRoaW5rIGl0J3Mg
YSBnb29kIGlkZWEuIEEgb25lLXllYXIgZXhwZXJpbWVudDxicj4NCmFmZmVjdHMgfmhhbGYgdGhl
IElFU0cgYW5kIElBQiBzZWF0cyBzbyBpcyBoaWdobHkgdW5saWtlbHkgdG8gbGVhZCB0bzxicj4N
CmRpc2FzdGVyLjxicj4NCjxzcGFuIGNsYXNzPSJIT0VuWmIiPjxmb250IGNvbG9yPSIjODg4ODg4
Ij48YnI+DQombmJzcDsgJm5ic3A7QnJpYW48YnI+DQo8YnI+DQo8L2ZvbnQ+PC9zcGFuPjwvYmxv
Y2txdW90ZT4NCjwvZGl2Pg0KPGJyPg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9zcGFuPg0K
PC9ib2R5Pg0KPC9odG1sPg0K

--_000_5E36120B6D4E4C0D99052C698455D395attcom_--


From nobody Thu Apr  7 15:08:30 2016
Return-Path: <superuser@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 A012D12D73C for <ietf@ietfa.amsl.com>; Thu,  7 Apr 2016 15:08:29 -0700 (PDT)
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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 CZ2Cu_UWN-BY for <ietf@ietfa.amsl.com>; Thu,  7 Apr 2016 15:08:28 -0700 (PDT)
Received: from mail-vk0-x230.google.com (mail-vk0-x230.google.com [IPv6:2607:f8b0:400c:c05::230]) (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 EE9E112D103 for <ietf@ietf.org>; Thu,  7 Apr 2016 15:08:27 -0700 (PDT)
Received: by mail-vk0-x230.google.com with SMTP id e185so117156495vkb.1 for <ietf@ietf.org>; Thu, 07 Apr 2016 15:08:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=7zHHVZNzgqt62Ug5g5MojLQ1mGttFtRFeCoesl2thqg=; b=JvWHTa6WmK7okT8NlWR1yE79L8xC4oxno3N82O4rIgAN1vs84j2B07ZLnz4Nq7aley /n8a2LW61MpcjOYKvX4NYPAwq/NTpwEJwDdMiMIuRc4KW1BJRIBrzEpN0ieTjbtZ3R6x LhitQegkh6vHpRZ3MLqSzyscmB2+ZKc6SqEmhMeJUco3YXkOWPERXLVVQHdezneQKDEI 8ugtJ1qztaGnjXx/f/ZwQYD4FdyUEWx5FEl9xSU7WvNrnholiTqpSzVzCd81R9PFXWm6 pa0fDsDj+7Z9YWZubEsLFyzNKSs3v2fBteU23sOYRePyKSd2n+KMk7gf/oxhwkGGeLYG KePQ==
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:date :message-id:subject:from:to:cc; bh=7zHHVZNzgqt62Ug5g5MojLQ1mGttFtRFeCoesl2thqg=; b=HqfxoFKX9SQL7cLG4Dlpx2hv4oKy45kSwwjfb6Uyhnf/IG3CwwBYKRmNTBN8AQ6R+d XylIe4hy6xYNFIXIPPiv2IxRS4GPc92HKaIuVrNjkNeUeglX6lV97LjZQWzGjSp6lLs/ hHes9SG3wlMHV15YLxsJwyLgyNOwLhnZGCMlHZzSNPniaHR7me0AlqJGFlTkgxE2ZfmM 4GejHm2lr54hWOQqL9wc9tzHm1jnHFGnOW+aMXDxSp0Yrc02aL9dHl3Q629O9ODMxOVF iDvugW8scJS/DpJ8wGi/m9I3M0xnqrmAriiab0J8h75QHcnLjjDgkooFL1E8DcQnVp7s QY0A==
X-Gm-Message-State: AD7BkJLrPE7+YMNbJWPTgIn9v2otFFNT+0nWqbgQizwGnUHQx7swg4nUYOPx3lP73G43As1SLosnz56sptKTvQ==
MIME-Version: 1.0
X-Received: by 10.159.37.101 with SMTP id 92mr2578679uaz.66.1460066907089; Thu, 07 Apr 2016 15:08:27 -0700 (PDT)
Received: by 10.103.43.5 with HTTP; Thu, 7 Apr 2016 15:08:26 -0700 (PDT)
In-Reply-To: <5706D7BC.8020800@alvestrand.no>
References: <CAL0qLwY0FuDp5=RMFEhUMtkK=XNDxX2dogvVY7+OSy88jrrvOQ@mail.gmail.com> <CAPt1N1=SYpo-CiHoc07Ukb04Kb1LGV2=BPPyRLUsaqyLM9Hbwg@mail.gmail.com> <CAL0qLwbhYRqw7fXHzYY0=W-CpmeHeDdaZx3z2Qg0cA2aMrmVwg@mail.gmail.com> <CAPt1N1nqmC7NJyg2M6Na8vUj8T-qObO-1gHFEXZzrobb3oOQhA@mail.gmail.com> <CAL0qLwZHGa5OvSmZ=bTd6AWchsm4r=QaJn2nPqD+YjeWPmH9pA@mail.gmail.com> <24691.1460062367@obiwan.sandelman.ca> <5706CC94.3080804@gmail.com> <CAL0qLwYvCpL9wwHL0E33HRbMvcckpad=gV-VYgAomJpCdiSrpg@mail.gmail.com> <5706D7BC.8020800@alvestrand.no>
Date: Thu, 7 Apr 2016 19:08:26 -0300
Message-ID: <CAL0qLwYyHOTV-RQtYfTwhH6Rq1fZk_=e64gEjay7OYMYdPZUVg@mail.gmail.com>
Subject: Re: Qualifying for NomCom
From: "Murray S. Kucherawy" <superuser@gmail.com>
To: Harald Alvestrand <harald@alvestrand.no>
Content-Type: multipart/alternative; boundary=94eb2c123f1c58734c052fec5107
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/S9hz6swlIDpMMy8CU6RTGDG-eqY>
Cc: Michael Richardson <mcr+ietf@sandelman.ca>, ietf <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, 07 Apr 2016 22:08:29 -0000

--94eb2c123f1c58734c052fec5107
Content-Type: text/plain; charset=UTF-8

On Thu, Apr 7, 2016 at 6:57 PM, Harald Alvestrand <harald@alvestrand.no>
wrote:

> - Scope objections and aborts to the time between the announcement of the
> final list of volunteers and the selection of the comittee. This closes the
> loophole that the powers-that-be can look at the selected nomcom, say "we
> don't like this group", and force a re-selection by spuriously objecting.
>

OK.


> - The timing says "This experiment is defined to last for one year,
> starting and ending with the constitution of the next NomCom after this
> document is approved and published." - this is neither determinate nor
> grammatical, I think - in particular, it starts and ends at the same time.
>

The NomCom is no longer constituted when it dissolves, which is what I
meant by that.  But I can be more explicit.


> I suggest "This experiment is defined to start with the first call for
> volunteers after IESG approval of this document, and ends with the
> selection of the nomcom from that volunteer pool. Evaluation of the
> experiment will be done after the selection process of the formed nomcom
> completes."
>

We might be splitting hairs, but to my mind, the experiment continues
beyond the seating of the NomCom, because that NomCom was formed under the
terms of the experiment; so the experiment truly ends when that NomCom
completes its obligations and dissolves.


> Otherwise - go for it!
>

I'll fold the above in.  Any other feedback?

-MSK

--94eb2c123f1c58734c052fec5107
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">On Thu, Apr 7, 2016 at 6:57 PM, Harald Alvestrand <span di=
r=3D"ltr">&lt;<a href=3D"mailto:harald@alvestrand.no" target=3D"_blank">har=
ald@alvestrand.no</a>&gt;</span> wrote:<br><div class=3D"gmail_extra"><div =
class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margin:0 0=
 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
 =20
   =20
 =20
  <span class=3D""></span>- Scope objections and aborts to the time between=
 the announcement
    of the final list of volunteers and the selection of the comittee.
    This closes the loophole that the powers-that-be can look at the
    selected nomcom, say &quot;we don&#39;t like this group&quot;, and forc=
e a
    re-selection by spuriously objecting.<br></blockquote><div><br></div><d=
iv>OK.<br>=C2=A0<br></div><blockquote class=3D"gmail_quote" style=3D"margin=
:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div text=3D"#0000=
00" bgcolor=3D"#FFFFFF">
    - The timing says &quot;This experiment is defined to last for one year=
,
    starting and ending with the constitution of the next NomCom after
    this document is approved and published.&quot; - this is neither
    determinate nor grammatical, I think - in particular, it starts and
    ends at the same time.<br></div></blockquote><div><br></div><div>The No=
mCom is no longer constituted when it dissolves, which is what I meant by t=
hat.=C2=A0 But I can be more explicit.<br>=C2=A0<br></div><blockquote class=
=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padd=
ing-left:1ex"><div text=3D"#000000" bgcolor=3D"#FFFFFF">
    I suggest &quot;This experiment is defined to start with the first call
    for volunteers after IESG approval of this document, and ends with
    the selection of the nomcom from that volunteer pool. Evaluation of
    the experiment will be done after the selection process of the
    formed nomcom completes.&quot;<br></div></blockquote><div><br></div><di=
v>We might be splitting hairs, but to my mind, the experiment continues bey=
ond the seating of the NomCom, because that NomCom was formed under the ter=
ms of the experiment; so the experiment truly ends when that NomCom complet=
es its obligations and dissolves.<br>=C2=A0<br></div><blockquote class=3D"g=
mail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-l=
eft:1ex"><div text=3D"#000000" bgcolor=3D"#FFFFFF">
    Otherwise - go for it!<br></div></blockquote><div><br></div><div>I&#39;=
ll fold the above in.=C2=A0 Any other feedback?<br><br></div><div>-MSK<br><=
/div></div></div></div>

--94eb2c123f1c58734c052fec5107--


From nobody Thu Apr  7 15:09:23 2016
Return-Path: <superuser@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 A0DFE12D198 for <ietf@ietfa.amsl.com>; Thu,  7 Apr 2016 15:09:22 -0700 (PDT)
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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 fmzN1qbjAPLO for <ietf@ietfa.amsl.com>; Thu,  7 Apr 2016 15:09:21 -0700 (PDT)
Received: from mail-vk0-x229.google.com (mail-vk0-x229.google.com [IPv6:2607:f8b0:400c:c05::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 1988712D0E1 for <ietf@ietf.org>; Thu,  7 Apr 2016 15:09:20 -0700 (PDT)
Received: by mail-vk0-x229.google.com with SMTP id t129so30919438vkg.2 for <ietf@ietf.org>; Thu, 07 Apr 2016 15:09:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=2+FSDfHK7cCKqozXgIehrFU3mcYqfjmwKmz273msmQQ=; b=eXVzcDQGHUnuaoISHaZENFyLEeTYIgec/CpaCsVYqA3fBWwYKXnolcD31mU44DgSL3 /goAxSX68WfQscrgWMu6vk8Z016jme+Lg1RfXKr6ysRr9KW31xS/eNWspBlUcBaaQXzL IcMCgH5SKRmjQAArX6tkl1yslBCm5X4RfvRF+wAYSx6xTbrRCokxDEZYd1/y3q4+OUen psI4G7Y+tA0WtUfWjMDMqFDoOeoZygZCHP6qJjOxxh2n0TX0vqOTFEmRHgeYvc2Aw1sP Q/0rMKFNbtqyu1ru4qSkgd+TzAPCwD6f1RF7IRmxsIpbL5KAhaUdj4w4rwOR/p2OCxQe 7rjw==
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:date :message-id:subject:from:to:cc; bh=2+FSDfHK7cCKqozXgIehrFU3mcYqfjmwKmz273msmQQ=; b=VqOJ5EkU94mcU7chmMxWPRyxNBIS969RSKfjkdZN42MRvzDuY2hQqZTC/yL5nBsZuZ WKYFGYApJZ/wRniCGnaI8N0yvhcNIzqzrXF0MkRu+6ZoCGv19t5PsynqBDK80jLkmWGf 1Ck+ahnoi02UfDnPlAwAb9mTkC4u+PMhXnWBcSq8CvnM1EeNvXykYMO+Ix+KEJq+LKM7 s22KGySEB3fCCd/AamGnkV9Kvlk97r234wEBUB5UgA1WVtMa9fAqDkEYAww42mgwUePq yxQw7bPt4UibUcwfj3L3CyyLH5R89lTMH/HzYShWedact4IJYvzkkIyYu2oF2ygaE2g0 98kA==
X-Gm-Message-State: AD7BkJI2ipZSE1tKNaSkGqlI7CXl4AsmX6vEurBTF3x+gHS+q+ArOEhD32k91P/Hjz6IEniwuivyyDDZ7n4J7Q==
MIME-Version: 1.0
X-Received: by 10.176.0.8 with SMTP id 8mr2228944uai.67.1460066959278; Thu, 07 Apr 2016 15:09:19 -0700 (PDT)
Received: by 10.103.43.5 with HTTP; Thu, 7 Apr 2016 15:09:19 -0700 (PDT)
In-Reply-To: <5E36120B-6D4E-4C0D-9905-2C698455D395@att.com>
References: <CAL0qLwY0FuDp5=RMFEhUMtkK=XNDxX2dogvVY7+OSy88jrrvOQ@mail.gmail.com> <CAPt1N1=SYpo-CiHoc07Ukb04Kb1LGV2=BPPyRLUsaqyLM9Hbwg@mail.gmail.com> <CAL0qLwbhYRqw7fXHzYY0=W-CpmeHeDdaZx3z2Qg0cA2aMrmVwg@mail.gmail.com> <CAPt1N1nqmC7NJyg2M6Na8vUj8T-qObO-1gHFEXZzrobb3oOQhA@mail.gmail.com> <CAL0qLwZHGa5OvSmZ=bTd6AWchsm4r=QaJn2nPqD+YjeWPmH9pA@mail.gmail.com> <24691.1460062367@obiwan.sandelman.ca> <5706CC94.3080804@gmail.com> <CAL0qLwYvCpL9wwHL0E33HRbMvcckpad=gV-VYgAomJpCdiSrpg@mail.gmail.com> <5E36120B-6D4E-4C0D-9905-2C698455D395@att.com>
Date: Thu, 7 Apr 2016 19:09:19 -0300
Message-ID: <CAL0qLwak6GRDYAcYqdOewoSmRj6DP5ptQKjqXkOedBaHcKC7WA@mail.gmail.com>
Subject: Re: Qualifying for NomCom
From: "Murray S. Kucherawy" <superuser@gmail.com>
To: "HANSEN, TONY L" <tony@att.com>
Content-Type: multipart/alternative; boundary=001a1141855a74cb03052fec548c
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/7nW37qFgLwRwhzbtUsW9TZ2E6eI>
Cc: ietf <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, 07 Apr 2016 22:09:22 -0000

--001a1141855a74cb03052fec548c
Content-Type: text/plain; charset=UTF-8

On Thu, Apr 7, 2016 at 7:06 PM, HANSEN, TONY L <tony@att.com> wrote:

>
> There's a fourth possible outcome: we've gathered enough information from
> the experiment that we know what we want to do and don't need to re-run
> another experiment in order to revise 7437.
>

Isn't that the same as the first outcome?

-MSK

--001a1141855a74cb03052fec548c
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">On Thu, Apr 7, 2016 at 7:06 PM, HANSEN, TONY L <span dir=
=3D"ltr">&lt;<a href=3D"mailto:tony@att.com" target=3D"_blank">tony@att.com=
</a>&gt;</span> wrote:<br><div class=3D"gmail_extra"><div class=3D"gmail_qu=
ote"><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-le=
ft:1px #ccc solid;padding-left:1ex">



<div style=3D"word-wrap:break-word;color:rgb(0,0,0);font-size:14px;font-fam=
ily:Calibri,sans-serif">
<div><br><div>There&#39;s a fourth possible outcome: we&#39;ve gathered eno=
ugh information from the experiment that we know what we want to do and don=
&#39;t need to re-run another experiment in order to revise 7437.</div></di=
v></div></blockquote><div><br></div><div>Isn&#39;t that the same as the fir=
st outcome?<br><br></div><div>-MSK<br></div></div></div></div>

--001a1141855a74cb03052fec548c--


From nobody Thu Apr  7 15:12:37 2016
Return-Path: <tony@att.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 ADA1512D0E1 for <ietf@ietfa.amsl.com>; Thu,  7 Apr 2016 15:12:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.58
X-Spam-Level: 
X-Spam-Status: No, score=-1.58 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MISSING_HEADERS=1.021, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001] autolearn=no 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 x-oYxNii9dSX for <ietf@ietfa.amsl.com>; Thu,  7 Apr 2016 15:12:34 -0700 (PDT)
Received: from mx0a-00191d01.pphosted.com (mx0a-00191d01.pphosted.com [67.231.149.140]) (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 A503312D0BF for <ietf@ietf.org>; Thu,  7 Apr 2016 15:12:34 -0700 (PDT)
Received: from pps.filterd (m0053301.ppops.net [127.0.0.1]) by mx0a-00191d01.pphosted.com (8.15.0.59/8.15.0.59) with SMTP id u37HcSqe003756 for <ietf@ietf.org>; Thu, 7 Apr 2016 13:41:18 -0400
Received: from alpi155.enaf.aldc.att.com (sbcsmtp7.sbc.com [144.160.229.24]) by mx0a-00191d01.pphosted.com with ESMTP id 225u3ehxe4-1 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for <ietf@ietf.org>; Thu, 07 Apr 2016 13:41:18 -0400
Received: from enaf.aldc.att.com (localhost [127.0.0.1]) by alpi155.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id u37HfHaW016006 for <ietf@ietf.org>; Thu, 7 Apr 2016 13:41:17 -0400
Received: from mlpi409.sfdc.sbc.com (mlpi409.sfdc.sbc.com [130.9.128.241]) by alpi155.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id u37HfBSA015915 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for <ietf@ietf.org>; Thu, 7 Apr 2016 13:41:12 -0400
Received: from MISOUT7MSGHUBAF.ITServices.sbc.com (MISOUT7MSGHUBAF.itservices.sbc.com [130.9.129.150]) by mlpi409.sfdc.sbc.com (RSA Interceptor) for <ietf@ietf.org>; Thu, 7 Apr 2016 17:41:09 GMT
Received: from MISOUT7MSGUSRCG.ITServices.sbc.com ([169.254.7.206]) by MISOUT7MSGHUBAF.ITServices.sbc.com ([130.9.129.150]) with mapi id 14.03.0248.002; Thu, 7 Apr 2016 13:41:08 -0400
From: "HANSEN, TONY L" <tony@att.com>
CC: "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: "We did not know" is not a good excuse
Thread-Topic: "We did not know" is not a good excuse
Thread-Index: AdGQXOo2K6ee2QfjSBaO8Tfj5mxHYwJCqcjan/XAz9Df+XGQAIAAI5yA///ENwA=
Date: Thu, 7 Apr 2016 17:41:08 +0000
Message-ID: <ACF0B32B-6961-4705-9150-30D661E66138@att.com>
References: <09ff01d1905c$f15d4e70$d417eb50$@olddog.co.uk> <5705C39E.30807@dcrocker.net> <0a5801d19086$79f40e30$6ddc2a90$@olddog.co.uk> <570677BC.9000900@dcrocker.net> <00b001d190f1$196e6b80$4c4b4280$@olddog.co.uk>
In-Reply-To: <00b001d190f1$196e6b80$4c4b4280$@olddog.co.uk>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.110.241.96]
Content-Type: text/plain; charset="utf-8"
Content-ID: <1F06A3D53F285C448F7FD1150BE2771B@LOCAL>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-RSA-Inspected: yes
X-RSA-Classifications: public
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2016-04-07_13:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_policy_notspam policy=outbound_policy 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-1601100000 definitions=main-1604070250
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/p7Q5HBujPTlSWdsT2zKzELpHsyQ>
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, 07 Apr 2016 22:12:36 -0000

T24gNC83LzE2LCAxOjE1IFBNLCAiaWV0ZiBvbiBiZWhhbGYgb2YgQWRyaWFuIEZhcnJlbCIgPGll
dGYtYm91bmNlc0BpZXRmLm9yZyBvbiBiZWhhbGYgb2YgYWRyaWFuQG9sZGRvZy5jby51az4gd3Jv
dGU6DQoNCg0KDQo+PiBBIHByYWN0aWNhbCBpc3N1ZSBpcyB0aGF0IGFubm91bmNpbmcgYSB2ZW51
ZSBiZWZvcmUgdGhlcmUgaXMgYSBjb250cmFjdA0KPj4gaW4gcGxhY2UgZm9yIHRoZSBtZWV0aW5n
IHNpdGUgaW1wYWlycyBvdXIgYWJpbGl0eSB0byBuZWdvdGlhdGUgdGhlDQo+PiBjb250cmFjdC4N
Cj4NCj5XZSBhcmUgZW5naW5lZXJpbmcuDQo+QnV0IEkgd2lsbCBicmVhayBhIHJ1bGUgYW5kIGdv
IHRoZXJlLg0KPg0KPkkgZG9uJ3Qgc2VlIHRoYXQgc2F5aW5nICJ3ZSBhcmUgY29uc2lkZXJpbmcg
SG9uZyBLb25nLCBTaW5nYXBvcmUsIGFuZCBNYW5pbGEiDQo+cmVkdWNlcyBvdXIgYWJpbGl0eSB0
byBuZWdvdGlhdGUgaW4gU2luZ2Fwb3JlLiBNYXliZSBpdCBldmVuIHN0cmVuZ3RoZW5zIGl0Lg0K
Pg0KPkJ1dCB0aGVyZSB3ZSBnby4gTG9va3MgbGlrZSBzb21ldGltZXMgd2UgbWF5IG5lZWQgdG8g
cGF5IGEgcHJpY2UgdG8gZ2V0IHdoYXQgd2UNCj53YW50LiBUaGUgbG9zcyBvbiBjYW5jZWxhdGlv
biBtYXkgYmUgZ3JlYXRlciB0aGFuIHRoZSBsb3NzIG9uIG5lZ290aWF0aW9uLg0KDQoNClRoZXJl
IGhhdmUgYmVlbiBwZXJpb2RpYyBzdXJ2ZXlzIGFmdGVyIG1lZXRpbmdzLCBhbmQgdGhlcmUgaGF2
ZSBjZXJ0YWlubHkgYmVlbiBxdWVzdGlvbnMgaW4gdGhlcmUgcmVnYXJkaW5nIHBvdGVudGlhbCBz
aXRlcyB3aXRoIGEgbWVhbnMgb2YgYWRkaW5nIGNvbW1lbnRzLg0KDQoNCkl0IHNlZW1zIGxpa2Ug
dGhpcyBwcmFjdGljZSBzaG91bGQgY29udGludWUuDQoNCglUb255DQo=


From nobody Thu Apr  7 15:25:35 2016
Return-Path: <john-ietf@jck.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 9CEFF12D718 for <ietf@ietfa.amsl.com>; Thu,  7 Apr 2016 15:25:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] 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 EJksUJgAPnyt for <ietf@ietfa.amsl.com>; Thu,  7 Apr 2016 15:25:30 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B4F5412D749 for <ietf@ietf.org>; Thu,  7 Apr 2016 15:25:29 -0700 (PDT)
Received: from [198.252.137.10] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1aoIMi-00089d-Ep; Thu, 07 Apr 2016 18:25:28 -0400
Date: Thu, 07 Apr 2016 18:25:23 -0400
From: John C Klensin <john-ietf@jck.com>
To: "HANSEN, TONY L" <tony@att.com>
Subject: Re: "We did not know" is not a good excuse
Message-ID: <345BC98986BA481F4E325FE4@JcK-HP8200.jck.com>
In-Reply-To: <ACF0B32B-6961-4705-9150-30D661E66138@att.com>
References: <09ff01d1905c$f15d4e70$d417eb50$@olddog.co.uk> <5705C39E.30807@dcrocker.net> <0a5801d19086$79f40e30$6ddc2a90$@olddog.co.uk> <570677BC.9000900@dcrocker.net> <00b001d190f1$196e6b80$4c4b4280$@olddog.co.uk> <ACF0B32B-6961-4705-9150-30D661E66138@att.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/hYAqzicOOcN92W1bMtv3-cHMBHI>
Cc: 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, 07 Apr 2016 22:25:34 -0000

--On Thursday, April 07, 2016 17:41 +0000 "HANSEN, TONY L"
<tony@att.com> wrote:

>> But there we go. Looks like sometimes we may need to pay a
>> price to get what we want. The loss on cancelation may be
>> greater than the loss on negotiation.
> 
> 
> There have been periodic surveys after meetings, and there
> have certainly been questions in there regarding potential
> sites with a means of adding comments.
> 
> 
> It seems like this practice should continue.

Of course, those periodic surveys have been available to meeting
attendees and have not picked up any information or preferences
those who did not show up in person for one reason or another
might have.



From nobody Thu Apr  7 15:33:48 2016
Return-Path: <john-ietf@jck.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 5875412D718 for <ietf@ietfa.amsl.com>; Thu,  7 Apr 2016 15:33:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] 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 4VSTc9Sv8pCg for <ietf@ietfa.amsl.com>; Thu,  7 Apr 2016 15:33:47 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D055112D72A for <ietf@ietf.org>; Thu,  7 Apr 2016 15:33:46 -0700 (PDT)
Received: from [198.252.137.10] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1aoIUf-0008AT-QT; Thu, 07 Apr 2016 18:33:41 -0400
Date: Thu, 07 Apr 2016 18:33:36 -0400
From: John C Klensin <john-ietf@jck.com>
To: Laurent Ciavaglia <laurent.ciavaglia@nokia.com>, EXT Mikael Abrahamsson <swmike@swm.pp.se>, "ietf@ietf.org Discussion" <ietf@ietf.org>
Subject: Re: Concerns about Singapore
Message-ID: <A1D17F91B9C8D60D91222AAC@JcK-HP8200.jck.com>
In-Reply-To: <5706CEEA.70402@alcatel-lucent.com>
References: <0D914666-C3D4-4CCE-AD5E-4E5B34EA1A73@piuha.net> <20160407182936.GA21340@pfrc.org> <CAB75xn780nNDjGa_Cc222J20-+1CCHt09Xp8KHzaK=n0xx51pg@mail.gmail.com> <5706B100.9040509@mnt.se> <CAB75xn6fmj84ROUtG5eUB3GerHx83hrEr3w5vSADY_g=BRg5FA@mail.gmail.com> <5706BA40.3060005@mnt.se> <alpine.DEB.2.02.1604072157240.31096@uplift.swm.pp.se> <5706CEEA.70402@alcatel-lucent.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/M7BKqII48F9vPgnnRhaVJ5kn22A>
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, 07 Apr 2016 22:33:48 -0000

--On Thursday, April 07, 2016 23:19 +0200 Laurent Ciavaglia
<laurent.ciavaglia@nokia.com> wrote:

> On 07/04/2016 22:00, EXT Mikael Abrahamsson wrote:
>> There are no perfect places to go.
> Except Minneapolis. ;)

If it were, the frequency with which we have been back there in
recent years might act as confirmation of the maxim that the
perfect is the enemy of the good.   I assume there are other
reasons, perhaps even better ones.

   john




From nobody Thu Apr  7 15:55:53 2016
Return-Path: <superuser@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 63AD312D613 for <ietf@ietfa.amsl.com>; Thu,  7 Apr 2016 15:55:52 -0700 (PDT)
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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 j0QsrlU4GVF3 for <ietf@ietfa.amsl.com>; Thu,  7 Apr 2016 15:55:50 -0700 (PDT)
Received: from mail-vk0-x236.google.com (mail-vk0-x236.google.com [IPv6:2607:f8b0:400c:c05::236]) (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 831AA12D580 for <ietf@ietf.org>; Thu,  7 Apr 2016 15:55:50 -0700 (PDT)
Received: by mail-vk0-x236.google.com with SMTP id e185so118267038vkb.1 for <ietf@ietf.org>; Thu, 07 Apr 2016 15:55:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=pNdGSG2rgIvnqqhvq4XWF2Ylpx4k0DOq2d4DHx+bgjo=; b=LIVSOURskGcyTxevGBmvOPNfTWQX9SHhRKy62Zd1zPNnbQzYNeILna8MdxttD7wnGe 9E4T5cJ88v6TmYvCLEclayOtOD2d22ujBnBPM2/qjjGfkWHWBNuYgQtC1YrLQa3kKFCI uHj2ZQVzmqLI4jW2j7YCIWtt2qrqBavdDbfBqRLNMDx7lrC4kmJLMlXSD2Sxuyge8jCb o+NtghLN0EE5+pyp680q6kUoAoNkoJrG3tlZiLmUR6ItVjNAJuys1ws6W9gHMsZo5Ymt hq3QGz/CPKgTQU16cpdqVt6M+CtoWVctw/4d4GLJf2BNM3/is+Yheg7gMR8c7QSFVsGF KTcg==
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:date :message-id:subject:from:to:cc; bh=pNdGSG2rgIvnqqhvq4XWF2Ylpx4k0DOq2d4DHx+bgjo=; b=mDIsuH65Jwqu0nnZ9L0btZJAVzncGc7FK5oFBbvuMn2JtjJN3qUb/3n/WMic55HyTL Oa+jrZM+rcdx2U/YZ69ECdJ0TmM5xFfpFo4AFiw+IH9ExPT2pPDytxd32dD/afvhItjc oIx30nDFRZj4KKC0CBSy/6/y6M2xH6jNlch7kE5TRSsfQGtiIS5nM6yJDVzeqNlfyvoW u7KqPzojdCsZRAu4hnenl/GeWYuoKsWS5LM/lzkJb6s9MQI/56T+yZtHQgGmTqqCmJOT 8T6vBa0OCbZzrlwNVOQLzI9Gc7msJzo4wkBvpxmDXMgqBKzvT9cc7Y/tvJ9nWM2f8tGZ fPKA==
X-Gm-Message-State: AD7BkJLq4NpT3R7RoqEgdSQqC/LdyvJajfhY7m1t+bp5vW39Pwf8txm/5jXPHIlnIvh7Xh9B9avNxgeTXwQW1g==
MIME-Version: 1.0
X-Received: by 10.176.64.169 with SMTP id i38mr2294973uad.154.1460069749644; Thu, 07 Apr 2016 15:55:49 -0700 (PDT)
Received: by 10.103.49.139 with HTTP; Thu, 7 Apr 2016 15:55:49 -0700 (PDT)
In-Reply-To: <60B61524-EFF7-4489-A0C7-AA4A139FEF6C@att.com>
References: <CAL0qLwY0FuDp5=RMFEhUMtkK=XNDxX2dogvVY7+OSy88jrrvOQ@mail.gmail.com> <CAPt1N1=SYpo-CiHoc07Ukb04Kb1LGV2=BPPyRLUsaqyLM9Hbwg@mail.gmail.com> <CAL0qLwbhYRqw7fXHzYY0=W-CpmeHeDdaZx3z2Qg0cA2aMrmVwg@mail.gmail.com> <CAPt1N1nqmC7NJyg2M6Na8vUj8T-qObO-1gHFEXZzrobb3oOQhA@mail.gmail.com> <CAL0qLwZHGa5OvSmZ=bTd6AWchsm4r=QaJn2nPqD+YjeWPmH9pA@mail.gmail.com> <24691.1460062367@obiwan.sandelman.ca> <5706CC94.3080804@gmail.com> <CAL0qLwYvCpL9wwHL0E33HRbMvcckpad=gV-VYgAomJpCdiSrpg@mail.gmail.com> <5E36120B-6D4E-4C0D-9905-2C698455D395@att.com> <CAL0qLwak6GRDYAcYqdOewoSmRj6DP5ptQKjqXkOedBaHcKC7WA@mail.gmail.com> <60B61524-EFF7-4489-A0C7-AA4A139FEF6C@att.com>
Date: Thu, 7 Apr 2016 19:55:49 -0300
Message-ID: <CAL0qLwYDW_zwfdr4-2=r0vt2Cb1wNFm+-aog0Wubu+8PbaYWEw@mail.gmail.com>
Subject: Re: Qualifying for NomCom
From: "Murray S. Kucherawy" <superuser@gmail.com>
To: "HANSEN, TONY L" <tony@att.com>
Content-Type: multipart/alternative; boundary=94eb2c124588c66572052fecfa55
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/fSKvqJ-8r4MVI_5_ZA1wlU3QIls>
Cc: ietf <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, 07 Apr 2016 22:55:52 -0000

--94eb2c124588c66572052fecfa55
Content-Type: text/plain; charset=UTF-8

On Thu, Apr 7, 2016 at 7:20 PM, HANSEN, TONY L <tony@att.com> wrote:

> No, outcome 1 says to use the criteria in section 2 directly as specified
> there. Outcome 4 lets us twiddle it.
>

Wouldn't we want to repeat the experiment with the twiddling before making
it part of the BCP?  That's outcome 2.

-MSK

--94eb2c124588c66572052fecfa55
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">On Thu, Apr 7, 2016 at 7:20 PM, HANSEN, TONY L <span dir=
=3D"ltr">&lt;<a href=3D"mailto:tony@att.com" target=3D"_blank">tony@att.com=
</a>&gt;</span> wrote:<br><div class=3D"gmail_extra"><div class=3D"gmail_qu=
ote"><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-le=
ft:1px #ccc solid;padding-left:1ex">



<div style=3D"word-wrap:break-word;color:rgb(0,0,0);font-size:14px;font-fam=
ily:Calibri,sans-serif">
<div>
<div>
<div>No, outcome 1 says to use the criteria in section 2 directly as specif=
ied there. Outcome 4 lets us twiddle it.</div></div></div></div></blockquot=
e><div><br></div><div>Wouldn&#39;t we want to repeat the experiment with th=
e twiddling before making it part of the BCP?=C2=A0 That&#39;s outcome 2.<b=
r><br></div><div>-MSK<br></div></div></div></div>

--94eb2c124588c66572052fecfa55--


From nobody Thu Apr  7 15:57:05 2016
Return-Path: <john-ietf@jck.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 AF53312D613 for <ietf@ietfa.amsl.com>; Thu,  7 Apr 2016 15:57:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] 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 rRA5Z-AiQTLy for <ietf@ietfa.amsl.com>; Thu,  7 Apr 2016 15:57:02 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E4D4E12D757 for <ietf@ietf.org>; Thu,  7 Apr 2016 15:57:01 -0700 (PDT)
Received: from [198.252.137.10] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1aoIrE-0008D0-Vt for ietf@ietf.org; Thu, 07 Apr 2016 18:57:00 -0400
Date: Thu, 07 Apr 2016 18:56:55 -0400
From: John C Klensin <john-ietf@jck.com>
To: "ietf@ietf.org Discussion" <ietf@ietf.org>
Subject: A distinction along Pete's dimensions (was: Re: Concerns about Singapore)
Message-ID: <22E40FD2507C568AB2849D61@JcK-HP8200.jck.com>
In-Reply-To: <7E3E34E3-346F-49D4-8030-335E802BE150@puck.nether.net>
References: <0D914666-C3D4-4CCE-AD5E-4E5B34EA1A73@piuha.net> <20160407182936.GA21340@pfrc.org> <CAB75xn780nNDjGa_Cc222J20-+1CCHt09Xp8KHzaK=n0xx51pg@mail.gmail.com> <5706B100.9040509@mnt.se> <CAB75xn6fmj84ROUtG5eUB3GerHx83hrEr3w5vSADY_g=BRg5FA@mail.gmail.com> <5706BA40.3060005@mnt.se> <alpine.DEB.2.02.1604072157240.31096@uplift.swm.pp.se> <5706CEEA.70402@alcatel-lucent.com> <D8151E5B-3862-4A77-A3FD-18D63334AA29@mnt.se> <7E3E34E3-346F-49D4-8030-335E802BE150@puck.nether.net>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/Uyjab3MnZgbT75Nptd5gfVowsQ8>
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, 07 Apr 2016 22:57:03 -0000

Hi.

Thinking about Pete's comments (with which I agree), and some
other comments made late in the BOF, an observation:

There are lots of places in the world with archaic laws
affecting personal behavior and relationships that we generally
find unacceptable.  In some of those places, they are not
enforced, have not been enforced for decades (or much longer),
and it is clear that any attempt to enforce them would result in
political outrage even though it is hard to get rid of them.  In
other places, they either are enforced or their enforcement is
only a matter of a small shift in the political winds or some
politician or lae enforcement entity looking for an excuse to
harass an individual or group.

Places where the problem is tied to laws or rules created
recently have to be treated as part of the second group, at
least until a _lot_ of experience accumulates.

The two cases may be hard to distinguish from a distance, but
they are very different.  In the first case, we might well want
to avoid meeting there, and make a statement about our reasons
for doing so, in order to join with others to create economic of
social pressure for change.  Or we might want to deliberately go
there in order to be supportive of local communities.  Getting
that choice right depends on input from people who are local and
listening to that input very carefully.  IMO, it is also a
decision that should be made openly and in consultation with the
IETF community and not in secret by a non-transparent IAOC
and/or Meetings Committee, both because that is the right thing
to do and because whatever message we want to deliver is likely
to be much more effective if it has clear community support.

The second, especially if it puts members of our community (or
anyone who attends with them) at risk of criminal or other types
of harsh treatment, falls into Pete's category that I would
describe as "don't even think about it" (at least I hope that is
consistent with his remarks).  I actually have mixed feelings
about Ted's suggestion that everyone else leave their families
home too.  On the one hand, it would help make a point and
spread the pain around.  On the other, it would seem a far
better option for everyone who is concerned about the problem
--and everyone who can be educated enough between now and
meeting 100 to care-- to stay home and participate remotely.  If
that were to wreck the budget or cause other real pain to either
the venue or the IAOC, I think we could at least be assured that
it wouldn't happen again.   But I really hope that we can make
whatever changes are needed to prevent us from _ever_ getting to
that point.

Note that I have not expressed an opinion above about whether
Singapore, or anywhere else that we are scheduled to go or might
contemplate, falls into the first category, the second, or, in
other cases, neither.  I don't have enough information, someone
local has said what amounts to "first category" and I think we
need to put some community effort into figuring that out.
What upset me is that the situation there caught us by surprise
but I think we need to move past that, figure out what to do
about that meeting, and, most important, make sure we learn from
the situations, both in terms of not repeating mistakes and
about the value of sufficient transparency that the IAOC can
obtain and take advantage of community knowledge.

    john



From nobody Thu Apr  7 16:10:53 2016
Return-Path: <mellon@fugue.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 98C3812D556 for <ietf@ietfa.amsl.com>; Thu,  7 Apr 2016 16:10:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.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 W-E9Uwv5HqlS for <ietf@ietfa.amsl.com>; Thu,  7 Apr 2016 16:10:47 -0700 (PDT)
Received: from mail-lf0-x22f.google.com (mail-lf0-x22f.google.com [IPv6:2a00:1450:4010:c07::22f]) (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 BEC0012D12E for <ietf@ietf.org>; Thu,  7 Apr 2016 16:10:46 -0700 (PDT)
Received: by mail-lf0-x22f.google.com with SMTP id c126so67677618lfb.2 for <ietf@ietf.org>; Thu, 07 Apr 2016 16:10:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=G8PDqNLVZkJtCX/0FWzjHDt0MkGl2bjogb5V1W85MCw=; b=VdR1u8LlaiScJInaEdcTcImZFdrTmO63ZERrxm1ypXlHmcAteFWOgo+WrseMlzXORt HhZw5WnE+B3c9ugsIidcRlf3/90fOA7f5I9I7kD5w1HgpygPn8FHiMCVPwRNr1Ihc7C+ RRTU5bQVMg0gIy1EanVXsf7oPzGvaSrWZXhw80pNjoNFwv6HWD2QODu24u8Rza9toJOb CQyP8KeSKn2ZF+LmdXYn7Xri1ABVOowAom4HKYdhoufH00coKz1qW0SsK+OuhZdwZ8Si tW2G+eHmbWiLWe6H8E9uo5Pso+PHhwm6xYMswR7NA+5zuayHYMLW2eAjBvlPTgk+tIy2 1G5Q==
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=G8PDqNLVZkJtCX/0FWzjHDt0MkGl2bjogb5V1W85MCw=; b=cXSShjg7uo9uENOo3xzY8zXnvQNcXoaM0rOQzzZSzj/sTitNyhHMW3ZyQXbUpJusuP c7q+Wdj67bCBqS76H4gHZO6YMndMoU6kZtq7Y3QeUSrGjZEO0w0CpyFAddRFYzkX927q +4vx+EwkvFaUw4IdhuUyZmJo5jQ+jq4C9FmX5/gfaru23jTYIeHHjd/U2fm2JvYsdqIz 0VKeCWLSVuP7/4FAYWKthuDSffo9yF+xNcj+o307YtJEB7d9k69aPwwJUvTaaLW1eNKN NVSC/uPkpUKcf/1h4fyOqo1eG21e8zKlpR1YOQRYMyND+STNwBlJQR89d+EkZS1YQp7I E80g==
X-Gm-Message-State: AD7BkJJpuPMfokAWv2RixXeN5y10TigZl0MjVha8MyDqYSg2vThAEe5sd41iJew2gPNoIKwbZLfGa0uhlnyjbQ==
X-Received: by 10.25.144.143 with SMTP id s137mr2359522lfd.53.1460070644881; Thu, 07 Apr 2016 16:10:44 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.25.40.136 with HTTP; Thu, 7 Apr 2016 16:10:05 -0700 (PDT)
X-Originating-IP: [2001:67c:370:176:ec62:80b3:91d7:df8a]
In-Reply-To: <A1D17F91B9C8D60D91222AAC@JcK-HP8200.jck.com>
References: <0D914666-C3D4-4CCE-AD5E-4E5B34EA1A73@piuha.net> <20160407182936.GA21340@pfrc.org> <CAB75xn780nNDjGa_Cc222J20-+1CCHt09Xp8KHzaK=n0xx51pg@mail.gmail.com> <5706B100.9040509@mnt.se> <CAB75xn6fmj84ROUtG5eUB3GerHx83hrEr3w5vSADY_g=BRg5FA@mail.gmail.com> <5706BA40.3060005@mnt.se> <alpine.DEB.2.02.1604072157240.31096@uplift.swm.pp.se> <5706CEEA.70402@alcatel-lucent.com> <A1D17F91B9C8D60D91222AAC@JcK-HP8200.jck.com>
From: Ted Lemon <mellon@fugue.com>
Date: Thu, 7 Apr 2016 20:10:05 -0300
Message-ID: <CAPt1N1m8ep-O__b--zFKUyNqXv+rntTj6Nc1LoAED6_WrqEMVg@mail.gmail.com>
Subject: Re: Concerns about Singapore
To: John C Klensin <john-ietf@jck.com>
Content-Type: multipart/alternative; boundary=001a1140227422b032052fed30c8
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/Tm1c-GuU-iRUYAnv-mfTzGUiFGg>
Cc: "ietf@ietf.org 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, 07 Apr 2016 23:10:50 -0000

--001a1140227422b032052fed30c8
Content-Type: text/plain; charset=UTF-8

Supposedly we never have very good attendance in Minneapolis because it
doesn't pull in tourists. :)

On Thu, Apr 7, 2016 at 7:33 PM, John C Klensin <john-ietf@jck.com> wrote:

>
>
> --On Thursday, April 07, 2016 23:19 +0200 Laurent Ciavaglia
> <laurent.ciavaglia@nokia.com> wrote:
>
> > On 07/04/2016 22:00, EXT Mikael Abrahamsson wrote:
> >> There are no perfect places to go.
> > Except Minneapolis. ;)
>
> If it were, the frequency with which we have been back there in
> recent years might act as confirmation of the maxim that the
> perfect is the enemy of the good.   I assume there are other
> reasons, perhaps even better ones.
>
>    john
>
>
>
>

--001a1140227422b032052fed30c8
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Supposedly we never have very good attendance in Minneapol=
is because it doesn&#39;t pull in tourists. :)</div><div class=3D"gmail_ext=
ra"><br><div class=3D"gmail_quote">On Thu, Apr 7, 2016 at 7:33 PM, John C K=
lensin <span dir=3D"ltr">&lt;<a href=3D"mailto:john-ietf@jck.com" target=3D=
"_blank">john-ietf@jck.com</a>&gt;</span> wrote:<br><blockquote class=3D"gm=
ail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-le=
ft:1ex"><br>
<br>
--On Thursday, April 07, 2016 23:19 +0200 Laurent Ciavaglia<br>
<span class=3D"">&lt;<a href=3D"mailto:laurent.ciavaglia@nokia.com">laurent=
.ciavaglia@nokia.com</a>&gt; wrote:<br>
<br>
&gt; On 07/04/2016 22:00, EXT Mikael Abrahamsson wrote:<br>
&gt;&gt; There are no perfect places to go.<br>
&gt; Except Minneapolis. ;)<br>
<br>
</span>If it were, the frequency with which we have been back there in<br>
recent years might act as confirmation of the maxim that the<br>
perfect is the enemy of the good.=C2=A0 =C2=A0I assume there are other<br>
reasons, perhaps even better ones.<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
=C2=A0 =C2=A0john<br>
<br>
<br>
<br>
</font></span></blockquote></div><br></div>

--001a1140227422b032052fed30c8--


From nobody Thu Apr  7 16:18:51 2016
Return-Path: <dhc@dcrocker.net>
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 A26DA12D613 for <ietf@ietfa.amsl.com>; Thu,  7 Apr 2016 16:18:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] 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 RH7xLfjgVfsI for <ietf@ietfa.amsl.com>; Thu,  7 Apr 2016 16:18:48 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3C1B712D1ED for <ietf@ietf.org>; Thu,  7 Apr 2016 16:18:48 -0700 (PDT)
Received: from [192.168.1.168] (76-218-10-206.lightspeed.sntcca.sbcglobal.net [76.218.10.206]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id u37NIlc9028023 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Thu, 7 Apr 2016 16:18:47 -0700
Subject: Re: A distinction along Pete's dimensions
To: John C Klensin <john-ietf@jck.com>, "ietf@ietf.org Discussion" <ietf@ietf.org>
References: <0D914666-C3D4-4CCE-AD5E-4E5B34EA1A73@piuha.net> <20160407182936.GA21340@pfrc.org> <CAB75xn780nNDjGa_Cc222J20-+1CCHt09Xp8KHzaK=n0xx51pg@mail.gmail.com> <5706B100.9040509@mnt.se> <CAB75xn6fmj84ROUtG5eUB3GerHx83hrEr3w5vSADY_g=BRg5FA@mail.gmail.com> <5706BA40.3060005@mnt.se> <alpine.DEB.2.02.1604072157240.31096@uplift.swm.pp.se> <5706CEEA.70402@alcatel-lucent.com> <D8151E5B-3862-4A77-A3FD-18D63334AA29@mnt.se> <7E3E34E3-346F-49D4-8030-335E802BE150@puck.nether.net> <22E40FD2507C568AB2849D61@JcK-HP8200.jck.com>
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
Message-ID: <5706EAD5.9070408@dcrocker.net>
Date: Thu, 7 Apr 2016 16:18:45 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2
MIME-Version: 1.0
In-Reply-To: <22E40FD2507C568AB2849D61@JcK-HP8200.jck.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Thu, 07 Apr 2016 16:18:47 -0700 (PDT)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/7753BGQExS84EQfyoBKemNXBvig>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: dcrocker@bbiw.net
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, 07 Apr 2016 23:18:49 -0000

On 4/7/2016 3:56 PM, John C Klensin wrote:
> The two cases may be hard to distinguish from a distance, but
> they are very different.


I'm going to suggest that, in practical terms for the IETF, it doesn't 
matter.

It doesn't matter because none of the theory or formal issues can be 
reliably and accurately applied for issues of social concern.

What matters is whatever the community decides it cares about at the 
time we are looking at the area.


Here's my logic:

    While some regions -- especially Asia -- have been challenging for 
finding venues, we already have an extensive track-record of finding 
places the community deems acceptable.  Consequently, we have safe 
harbors to fall back on, for each of the 3 regions we regularly visit.

    So when a new country or city is being considered -- and by new, I 
think I mean 'we have never been there', but perhaps we need to leave 
room for reconsideration of previously-visited places? -- we float the 
general countries and maybe cities to the community and wait for support 
and objections.


Whatever criteria the community chooses to apply at that time are the 
relevant criteria.  No theory or modeling or documentation or even 
consistency -- and especially no guessing and no errors by an anointed 
body -- are required.


d/

-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net


From nobody Thu Apr  7 16:22:06 2016
Return-Path: <mellon@fugue.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 223E612D650 for <ietf@ietfa.amsl.com>; Thu,  7 Apr 2016 16:22:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.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 m87pm8FBhn_6 for <ietf@ietfa.amsl.com>; Thu,  7 Apr 2016 16:22:04 -0700 (PDT)
Received: from mail-lf0-x236.google.com (mail-lf0-x236.google.com [IPv6:2a00:1450:4010:c07::236]) (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 EA75F12D532 for <ietf@ietf.org>; Thu,  7 Apr 2016 16:22:03 -0700 (PDT)
Received: by mail-lf0-x236.google.com with SMTP id e190so65965846lfe.0 for <ietf@ietf.org>; Thu, 07 Apr 2016 16:22:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=0RWsiwBzUaMwQAk9QHEkV6/ockyKoe3CJUusOpAEhXc=; b=cRNuM8+g8sjYEi78ygsDU8cVfouHgji6T9qNVxQ7iferWY4veMZKT0n1KMoi2i6jYk mxe+qLF7z4GfCCTYRSjTcFJJ89ZEKtQRD5dzRWul0CUkc3I/L1MwUFMrOLpE26R5yGgj tkNmRuI3Qnawd5yW+E9GAyFbUuh1CIGXf1AEK+dahvL4nEy3qtA0JpJRpdQmS7sPL7LM yBFOFYvgHxbaM0M3fvcfblr1jOZYUB/N9OYy8hRwMYuu8Hxlqm/8cyIYDwO4yGCLNDyW tpLdT5HKC2VJNDrZsBblwD70iFBWDswm52mNxZiVZZL2ZGlXvGt2owL+f/F0TGIliwQV h/nQ==
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=0RWsiwBzUaMwQAk9QHEkV6/ockyKoe3CJUusOpAEhXc=; b=e+IYtVYf/JJZ6fmhvJNgkn9TYUcrdlevyn8Ns+aDzuwc691U6kc7wbgJiUjREPhd9W 82ZsrAdGf3FIffuPolcgNTazsNy80MPurZOSxDMMPtDhJyc5gGQRgifas7tYCcVRSWvA FMCyggY/d+rwARoW6mrMxTkkQ3O080yMh8iK2SZ764cT14yPJg1A7xfK+U915sxMvAyn J1gMMNvXM2PYTYaaRWs1LGM39PFA/yV9SdRv3my2gNfvPfqcfxauB/eoulZIvOs7lYpt CbpK3pbRecqp1HSMUV6Qrp6IAA7eg/BLdfH0uO3fXfC1iq5Y5OzgaDJ6aVR8YLdyJwLN xNHw==
X-Gm-Message-State: AD7BkJIdNO8dyzVa1w+9m+P/YHYgrnCLNSd+rBIzV3V/3AG/Locl6ApNwt6ogYA3quzjZXCc4IY6MJcQtkUNCg==
X-Received: by 10.25.205.146 with SMTP id d140mr2363158lfg.109.1460071322091;  Thu, 07 Apr 2016 16:22:02 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.25.40.136 with HTTP; Thu, 7 Apr 2016 16:21:22 -0700 (PDT)
X-Originating-IP: [2001:67c:370:176:ec62:80b3:91d7:df8a]
In-Reply-To: <5706EAD5.9070408@dcrocker.net>
References: <0D914666-C3D4-4CCE-AD5E-4E5B34EA1A73@piuha.net> <20160407182936.GA21340@pfrc.org> <CAB75xn780nNDjGa_Cc222J20-+1CCHt09Xp8KHzaK=n0xx51pg@mail.gmail.com> <5706B100.9040509@mnt.se> <CAB75xn6fmj84ROUtG5eUB3GerHx83hrEr3w5vSADY_g=BRg5FA@mail.gmail.com> <5706BA40.3060005@mnt.se> <alpine.DEB.2.02.1604072157240.31096@uplift.swm.pp.se> <5706CEEA.70402@alcatel-lucent.com> <D8151E5B-3862-4A77-A3FD-18D63334AA29@mnt.se> <7E3E34E3-346F-49D4-8030-335E802BE150@puck.nether.net> <22E40FD2507C568AB2849D61@JcK-HP8200.jck.com> <5706EAD5.9070408@dcrocker.net>
From: Ted Lemon <mellon@fugue.com>
Date: Thu, 7 Apr 2016 20:21:22 -0300
Message-ID: <CAPt1N1kR7WkHaaKzYcoCnjRMTzj0AemcGvB7Yvgvy20fBA0bdQ@mail.gmail.com>
Subject: Re: A distinction along Pete's dimensions
To: Dave Crocker <dcrocker@bbiw.net>
Content-Type: multipart/alternative; boundary=001a114128ca801c47052fed5805
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/BcOpuE7VgJRAyStIu23YuHxyrQQ>
Cc: John C Klensin <john-ietf@jck.com>, "ietf@ietf.org 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, 07 Apr 2016 23:22:06 -0000

--001a114128ca801c47052fed5805
Content-Type: text/plain; charset=UTF-8

I was a little puzzled to hear that Yokohama didn't meet the food
requirements, by the way.   I ate more than half my meals from the
excellent nearby grocery store.   Would like to go back there agian!

On Thu, Apr 7, 2016 at 8:18 PM, Dave Crocker <dhc@dcrocker.net> wrote:

> On 4/7/2016 3:56 PM, John C Klensin wrote:
>
>> The two cases may be hard to distinguish from a distance, but
>> they are very different.
>>
>
>
> I'm going to suggest that, in practical terms for the IETF, it doesn't
> matter.
>
> It doesn't matter because none of the theory or formal issues can be
> reliably and accurately applied for issues of social concern.
>
> What matters is whatever the community decides it cares about at the time
> we are looking at the area.
>
>
> Here's my logic:
>
>    While some regions -- especially Asia -- have been challenging for
> finding venues, we already have an extensive track-record of finding places
> the community deems acceptable.  Consequently, we have safe harbors to fall
> back on, for each of the 3 regions we regularly visit.
>
>    So when a new country or city is being considered -- and by new, I
> think I mean 'we have never been there', but perhaps we need to leave room
> for reconsideration of previously-visited places? -- we float the general
> countries and maybe cities to the community and wait for support and
> objections.
>
>
> Whatever criteria the community chooses to apply at that time are the
> relevant criteria.  No theory or modeling or documentation or even
> consistency -- and especially no guessing and no errors by an anointed body
> -- are required.
>
>
> d/
>
> --
>
>   Dave Crocker
>   Brandenburg InternetWorking
>   bbiw.net
>
>

--001a114128ca801c47052fed5805
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">I was a little puzzled to hear that Yokohama didn&#39;t me=
et the food requirements, by the way. =C2=A0 I ate more than half my meals =
from the excellent nearby grocery store. =C2=A0 Would like to go back there=
 agian!</div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On T=
hu, Apr 7, 2016 at 8:18 PM, Dave Crocker <span dir=3D"ltr">&lt;<a href=3D"m=
ailto:dhc@dcrocker.net" target=3D"_blank">dhc@dcrocker.net</a>&gt;</span> w=
rote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;borde=
r-left:1px #ccc solid;padding-left:1ex">On 4/7/2016 3:56 PM, John C Klensin=
 wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
The two cases may be hard to distinguish from a distance, but<br>
they are very different.<br>
</blockquote>
<br>
<br>
I&#39;m going to suggest that, in practical terms for the IETF, it doesn&#3=
9;t matter.<br>
<br>
It doesn&#39;t matter because none of the theory or formal issues can be re=
liably and accurately applied for issues of social concern.<br>
<br>
What matters is whatever the community decides it cares about at the time w=
e are looking at the area.<br>
<br>
<br>
Here&#39;s my logic:<br>
<br>
=C2=A0 =C2=A0While some regions -- especially Asia -- have been challenging=
 for finding venues, we already have an extensive track-record of finding p=
laces the community deems acceptable.=C2=A0 Consequently, we have safe harb=
ors to fall back on, for each of the 3 regions we regularly visit.<br>
<br>
=C2=A0 =C2=A0So when a new country or city is being considered -- and by ne=
w, I think I mean &#39;we have never been there&#39;, but perhaps we need t=
o leave room for reconsideration of previously-visited places? -- we float =
the general countries and maybe cities to the community and wait for suppor=
t and objections.<br>
<br>
<br>
Whatever criteria the community chooses to apply at that time are the relev=
ant criteria.=C2=A0 No theory or modeling or documentation or even consiste=
ncy -- and especially no guessing and no errors by an anointed body -- are =
required.<span class=3D"HOEnZb"><font color=3D"#888888"><br>
<br>
<br>
d/<br>
<br>
-- <br>
<br>
=C2=A0 Dave Crocker<br>
=C2=A0 Brandenburg InternetWorking<br>
=C2=A0 <a href=3D"http://bbiw.net" rel=3D"noreferrer" target=3D"_blank">bbi=
w.net</a><br>
<br>
</font></span></blockquote></div><br></div>

--001a114128ca801c47052fed5805--


From nobody Thu Apr  7 16:52:05 2016
Return-Path: <tony@att.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 0C52F12D1EA for <ietf@ietfa.amsl.com>; Thu,  7 Apr 2016 16:52:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001] 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 uX2QCaTye7vY for <ietf@ietfa.amsl.com>; Thu,  7 Apr 2016 16:52:02 -0700 (PDT)
Received: from mx0a-00191d01.pphosted.com (mx0a-00191d01.pphosted.com [67.231.149.140]) (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 89F8E12D15E for <ietf@ietf.org>; Thu,  7 Apr 2016 16:52:02 -0700 (PDT)
Received: from pps.filterd (m0049295.ppops.net [127.0.0.1]) by m0049295.ppops.net-00191d01. (8.15.0.59/8.15.0.59) with SMTP id u37MJTqA037189; Thu, 7 Apr 2016 18:21:10 -0400
Received: from alpi155.enaf.aldc.att.com (sbcsmtp7.sbc.com [144.160.229.24]) by m0049295.ppops.net-00191d01. with ESMTP id 225yjrgwmr-1 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT);  Thu, 07 Apr 2016 18:21:09 -0400
Received: from enaf.aldc.att.com (localhost [127.0.0.1]) by alpi155.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id u37ML7lM028702; Thu, 7 Apr 2016 18:21:08 -0400
Received: from mlpi407.sfdc.sbc.com (mlpi407.sfdc.sbc.com [130.9.128.239]) by alpi155.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id u37ML1XW028651 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 7 Apr 2016 18:21:06 -0400
Received: from MISOUT7MSGHUBAG.ITServices.sbc.com (MISOUT7MSGHUBAG.itservices.sbc.com [130.9.129.151]) by mlpi407.sfdc.sbc.com (RSA Interceptor); Thu, 7 Apr 2016 22:20:52 GMT
Received: from MISOUT7MSGUSRCG.ITServices.sbc.com ([169.254.7.206]) by MISOUT7MSGHUBAG.ITServices.sbc.com ([130.9.129.151]) with mapi id 14.03.0248.002; Thu, 7 Apr 2016 18:20:52 -0400
From: "HANSEN, TONY L" <tony@att.com>
To: "Murray S. Kucherawy" <superuser@gmail.com>
Subject: Re: Qualifying for NomCom
Thread-Topic: Qualifying for NomCom
Thread-Index: AQHRkPkBaE3TgFgCo0Odl4x3Th89cJ9/E2cAgAABUgCAAAB+AIAABFuAgAAma4CAAAS3AIAAAzOA///JioCAAEPugP//wCuA
Date: Thu, 7 Apr 2016 22:20:51 +0000
Message-ID: <60B61524-EFF7-4489-A0C7-AA4A139FEF6C@att.com>
References: <CAL0qLwY0FuDp5=RMFEhUMtkK=XNDxX2dogvVY7+OSy88jrrvOQ@mail.gmail.com> <CAPt1N1=SYpo-CiHoc07Ukb04Kb1LGV2=BPPyRLUsaqyLM9Hbwg@mail.gmail.com> <CAL0qLwbhYRqw7fXHzYY0=W-CpmeHeDdaZx3z2Qg0cA2aMrmVwg@mail.gmail.com> <CAPt1N1nqmC7NJyg2M6Na8vUj8T-qObO-1gHFEXZzrobb3oOQhA@mail.gmail.com> <CAL0qLwZHGa5OvSmZ=bTd6AWchsm4r=QaJn2nPqD+YjeWPmH9pA@mail.gmail.com> <24691.1460062367@obiwan.sandelman.ca> <5706CC94.3080804@gmail.com> <CAL0qLwYvCpL9wwHL0E33HRbMvcckpad=gV-VYgAomJpCdiSrpg@mail.gmail.com> <5E36120B-6D4E-4C0D-9905-2C698455D395@att.com> <CAL0qLwak6GRDYAcYqdOewoSmRj6DP5ptQKjqXkOedBaHcKC7WA@mail.gmail.com>
In-Reply-To: <CAL0qLwak6GRDYAcYqdOewoSmRj6DP5ptQKjqXkOedBaHcKC7WA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.110.241.40]
Content-Type: multipart/alternative; boundary="_000_60B61524EFF74489A0C7AA4A139FEF6Cattcom_"
MIME-Version: 1.0
X-RSA-Inspected: yes
X-RSA-Classifications: public
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2016-04-07_15:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_policy_notspam policy=outbound_policy 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-1603180000 definitions=main-1604070316
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/EMqKcWKJmIAG9Y-RkGDfK3gydlU>
Cc: ietf <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, 07 Apr 2016 23:52:04 -0000

--_000_60B61524EFF74489A0C7AA4A139FEF6Cattcom_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

Tm8sIG91dGNvbWUgMSBzYXlzIHRvIHVzZSB0aGUgY3JpdGVyaWEgaW4gc2VjdGlvbiAyIGRpcmVj
dGx5IGFzIHNwZWNpZmllZCB0aGVyZS4gT3V0Y29tZSA0IGxldHMgdXMgdHdpZGRsZSBpdC4NCg0K
VG9ueQ0KDQpGcm9tOiAiTXVycmF5IFMuIEt1Y2hlcmF3eSIgPHN1cGVydXNlckBnbWFpbC5jb208
bWFpbHRvOnN1cGVydXNlckBnbWFpbC5jb20+Pg0KRGF0ZTogVGh1cnNkYXksIEFwcmlsIDcsIDIw
MTYgYXQgNjowOSBQTQ0KVG86IFRvbnkgSGFuc2VuIDx0b255QGF0dC5jb208bWFpbHRvOnRvbnlA
YXR0LmNvbT4+DQpDYzogaWV0ZiA8aWV0ZkBpZXRmLm9yZzxtYWlsdG86aWV0ZkBpZXRmLm9yZz4+
DQpTdWJqZWN0OiBSZTogUXVhbGlmeWluZyBmb3IgTm9tQ29tDQoNCk9uIFRodSwgQXByIDcsIDIw
MTYgYXQgNzowNiBQTSwgSEFOU0VOLCBUT05ZIEwgPHRvbnlAYXR0LmNvbTxtYWlsdG86dG9ueUBh
dHQuY29tPj4gd3JvdGU6DQoNClRoZXJlJ3MgYSBmb3VydGggcG9zc2libGUgb3V0Y29tZTogd2Un
dmUgZ2F0aGVyZWQgZW5vdWdoIGluZm9ybWF0aW9uIGZyb20gdGhlIGV4cGVyaW1lbnQgdGhhdCB3
ZSBrbm93IHdoYXQgd2Ugd2FudCB0byBkbyBhbmQgZG9uJ3QgbmVlZCB0byByZS1ydW4gYW5vdGhl
ciBleHBlcmltZW50IGluIG9yZGVyIHRvIHJldmlzZSA3NDM3Lg0KDQpJc24ndCB0aGF0IHRoZSBz
YW1lIGFzIHRoZSBmaXJzdCBvdXRjb21lPw0KDQotTVNLDQo=

--_000_60B61524EFF74489A0C7AA4A139FEF6Cattcom_
Content-Type: text/html; charset="utf-8"
Content-ID: <50939CC6202E5E40BEBA9569A66F45D4@LOCAL>
Content-Transfer-Encoding: base64

PGh0bWw+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIgY29udGVudD0i
dGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjwvaGVhZD4NCjxib2R5IHN0eWxlPSJ3b3JkLXdy
YXA6IGJyZWFrLXdvcmQ7IC13ZWJraXQtbmJzcC1tb2RlOiBzcGFjZTsgLXdlYmtpdC1saW5lLWJy
ZWFrOiBhZnRlci13aGl0ZS1zcGFjZTsgY29sb3I6IHJnYigwLCAwLCAwKTsgZm9udC1zaXplOiAx
NHB4OyBmb250LWZhbWlseTogQ2FsaWJyaSwgc2Fucy1zZXJpZjsiPg0KPGRpdj4NCjxkaXY+DQo8
ZGl2Pk5vLCBvdXRjb21lIDEgc2F5cyB0byB1c2UgdGhlIGNyaXRlcmlhIGluIHNlY3Rpb24gMiBk
aXJlY3RseSBhcyBzcGVjaWZpZWQgdGhlcmUuIE91dGNvbWUgNCBsZXRzIHVzIHR3aWRkbGUgaXQu
PC9kaXY+DQo8ZGl2Pjxicj4NCjwvZGl2Pg0KPGRpdj48c3BhbiBjbGFzcz0iQXBwbGUtdGFiLXNw
YW4iIHN0eWxlPSJ3aGl0ZS1zcGFjZTpwcmUiPjwvc3Bhbj5Ub255PC9kaXY+DQo8ZGl2Pg0KPGRp
diBpZD0iTUFDX09VVExPT0tfU0lHTkFUVVJFIj48L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rp
dj4NCjxkaXY+PGJyPg0KPC9kaXY+DQo8c3BhbiBpZD0iT0xLX1NSQ19CT0RZX1NFQ1RJT04iPg0K
PGRpdiBzdHlsZT0iZm9udC1mYW1pbHk6Q2FsaWJyaTsgZm9udC1zaXplOjEycHQ7IHRleHQtYWxp
Z246bGVmdDsgY29sb3I6YmxhY2s7IEJPUkRFUi1CT1RUT006IG1lZGl1bSBub25lOyBCT1JERVIt
TEVGVDogbWVkaXVtIG5vbmU7IFBBRERJTkctQk9UVE9NOiAwaW47IFBBRERJTkctTEVGVDogMGlu
OyBQQURESU5HLVJJR0hUOiAwaW47IEJPUkRFUi1UT1A6ICNiNWM0ZGYgMXB0IHNvbGlkOyBCT1JE
RVItUklHSFQ6IG1lZGl1bSBub25lOyBQQURESU5HLVRPUDogM3B0Ij4NCjxzcGFuIHN0eWxlPSJm
b250LXdlaWdodDpib2xkIj5Gcm9tOiA8L3NwYW4+JnF1b3Q7TXVycmF5IFMuIEt1Y2hlcmF3eSZx
dW90OyAmbHQ7PGEgaHJlZj0ibWFpbHRvOnN1cGVydXNlckBnbWFpbC5jb20iPnN1cGVydXNlckBn
bWFpbC5jb208L2E+Jmd0Ozxicj4NCjxzcGFuIHN0eWxlPSJmb250LXdlaWdodDpib2xkIj5EYXRl
OiA8L3NwYW4+VGh1cnNkYXksIEFwcmlsIDcsIDIwMTYgYXQgNjowOSBQTTxicj4NCjxzcGFuIHN0
eWxlPSJmb250LXdlaWdodDpib2xkIj5UbzogPC9zcGFuPlRvbnkgSGFuc2VuICZsdDs8YSBocmVm
PSJtYWlsdG86dG9ueUBhdHQuY29tIj50b255QGF0dC5jb208L2E+Jmd0Ozxicj4NCjxzcGFuIHN0
eWxlPSJmb250LXdlaWdodDpib2xkIj5DYzogPC9zcGFuPmlldGYgJmx0OzxhIGhyZWY9Im1haWx0
bzppZXRmQGlldGYub3JnIj5pZXRmQGlldGYub3JnPC9hPiZndDs8YnI+DQo8c3BhbiBzdHlsZT0i
Zm9udC13ZWlnaHQ6Ym9sZCI+U3ViamVjdDogPC9zcGFuPlJlOiBRdWFsaWZ5aW5nIGZvciBOb21D
b208YnI+DQo8L2Rpdj4NCjxkaXY+PGJyPg0KPC9kaXY+DQo8ZGl2Pg0KPGRpdj4NCjxkaXYgZGly
PSJsdHIiPk9uIFRodSwgQXByIDcsIDIwMTYgYXQgNzowNiBQTSwgSEFOU0VOLCBUT05ZIEwgPHNw
YW4gZGlyPSJsdHIiPiZsdDs8YSBocmVmPSJtYWlsdG86dG9ueUBhdHQuY29tIiB0YXJnZXQ9Il9i
bGFuayI+dG9ueUBhdHQuY29tPC9hPiZndDs8L3NwYW4+IHdyb3RlOjxicj4NCjxkaXYgY2xhc3M9
ImdtYWlsX2V4dHJhIj4NCjxkaXYgY2xhc3M9ImdtYWlsX3F1b3RlIj4NCjxibG9ja3F1b3RlIGNs
YXNzPSJnbWFpbF9xdW90ZSIgc3R5bGU9Im1hcmdpbjowIDAgMCAuOGV4O2JvcmRlci1sZWZ0OjFw
eCAjY2NjIHNvbGlkO3BhZGRpbmctbGVmdDoxZXgiPg0KPGRpdiBzdHlsZT0id29yZC13cmFwOmJy
ZWFrLXdvcmQ7Y29sb3I6cmdiKDAsMCwwKTtmb250LXNpemU6MTRweDtmb250LWZhbWlseTpDYWxp
YnJpLHNhbnMtc2VyaWYiPg0KPGRpdj48YnI+DQo8ZGl2PlRoZXJlJ3MgYSBmb3VydGggcG9zc2li
bGUgb3V0Y29tZTogd2UndmUgZ2F0aGVyZWQgZW5vdWdoIGluZm9ybWF0aW9uIGZyb20gdGhlIGV4
cGVyaW1lbnQgdGhhdCB3ZSBrbm93IHdoYXQgd2Ugd2FudCB0byBkbyBhbmQgZG9uJ3QgbmVlZCB0
byByZS1ydW4gYW5vdGhlciBleHBlcmltZW50IGluIG9yZGVyIHRvIHJldmlzZSA3NDM3LjwvZGl2
Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvYmxvY2txdW90ZT4NCjxkaXY+PGJyPg0KPC9kaXY+DQo8ZGl2
Pklzbid0IHRoYXQgdGhlIHNhbWUgYXMgdGhlIGZpcnN0IG91dGNvbWU/PGJyPg0KPGJyPg0KPC9k
aXY+DQo8ZGl2Pi1NU0s8YnI+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2
Pg0KPC9kaXY+DQo8L3NwYW4+DQo8L2JvZHk+DQo8L2h0bWw+DQo=

--_000_60B61524EFF74489A0C7AA4A139FEF6Cattcom_--


From nobody Thu Apr  7 18:18:21 2016
Return-Path: <randy@psg.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 223FF12D512 for <ietf@ietfa.amsl.com>; Thu,  7 Apr 2016 18:18:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.91
X-Spam-Level: 
X-Spam-Status: No, score=-6.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, T_RP_MATCHES_RCVD=-0.01] 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 9aPXD9DLNQmJ for <ietf@ietfa.amsl.com>; Thu,  7 Apr 2016 18:18:19 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BDC5312D17A for <ietf@ietf.org>; Thu,  7 Apr 2016 18:18:19 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com) by ran.psg.com with esmtp (Exim 4.82) (envelope-from <randy@psg.com>) id 1aoL3v-0001jt-H5; Fri, 08 Apr 2016 01:18:15 +0000
Date: Thu, 07 Apr 2016 22:18:15 -0300
Message-ID: <m21t6gc2zs.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Laurent Ciavaglia <laurent.ciavaglia@nokia.com>
Subject: Re: Concerns about Singapore
In-Reply-To: <5706CFB0.2090203@alcatel-lucent.com>
References: <0D914666-C3D4-4CCE-AD5E-4E5B34EA1A73@piuha.net> <20160407182936.GA21340@pfrc.org> <CAB75xn780nNDjGa_Cc222J20-+1CCHt09Xp8KHzaK=n0xx51pg@mail.gmail.com> <5706B100.9040509@mnt.se> <CAB75xn6fmj84ROUtG5eUB3GerHx83hrEr3w5vSADY_g=BRg5FA@mail.gmail.com> <5706BA40.3060005@mnt.se> <alpine.DEB.2.02.1604072157240.31096@uplift.swm.pp.se> <5706C7B1.3040203@mnt.se> <5706CFB0.2090203@alcatel-lucent.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/EBbuGeP1PkB2QljsixFHZcppw2g>
Cc: 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: Fri, 08 Apr 2016 01:18:21 -0000

> death penalty.
> firearm death rate.
> D. Trump

add difficulty of getting visas for many folk

randy


From nobody Thu Apr  7 18:25:43 2016
Return-Path: <leifj@mnt.se>
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 7D9FF12D126 for <ietf@ietfa.amsl.com>; Thu,  7 Apr 2016 18:25:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.83
X-Spam-Level: 
X-Spam-Status: No, score=-1.83 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_SORBS_WEB=0.77] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mnt-se.20150623.gappssmtp.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 dWUV9uYnHHBX for <ietf@ietfa.amsl.com>; Thu,  7 Apr 2016 18:25:38 -0700 (PDT)
Received: from mail-qk0-x22f.google.com (mail-qk0-x22f.google.com [IPv6:2607:f8b0:400d:c09::22f]) (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 18AE312D17A for <ietf@ietf.org>; Thu,  7 Apr 2016 18:25:38 -0700 (PDT)
Received: by mail-qk0-x22f.google.com with SMTP id o6so38607831qkc.2 for <ietf@ietf.org>; Thu, 07 Apr 2016 18:25:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mnt-se.20150623.gappssmtp.com; s=20150623; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding; bh=R8X0YkDnK4KitXk1PSdzYjaTaDrWCYCUis08S6c7Ijg=; b=uIclbRB2e/P9qnmPbEKedXsSzo5xPVd0mpErHt8hcGAlrDuhCab6nVGBOfuQOMucn0 5q/JVKCgWFzQ9tLSX8AUxfKyrI3OsLORFmAtcL+e5DKK74t3KpS59bRjfsL5uztPyatn t9dAJf5O9VPQ2hAqAdoBaNdLaTTM1pzzse0CRScwd2gM0nXRKo8lZR0wgTvq7f01cpcL D+DplqpvsuhCe5KoOuwhIn7mjfrRHyb7ZI10gqmJL1iZCRAdi8y3n4Ezm3nkLKS2OvuV +yplaAS4rnD8Ovif45LHUQ9YWZNm5M/5KQQT/J3YIOEDkmZW+Jj6hMA1J21TPKVQOEl9 CJSg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=R8X0YkDnK4KitXk1PSdzYjaTaDrWCYCUis08S6c7Ijg=; b=fXUkOfpR/1m4UCusyZU3dd0dCvwEyLEWsFrowUuCbWo0ejynmfbjVGRGXR5HOF7y7x KkZOIiPNd3pUvPNH8OZvmkXqCC5ACCAu5R0Tcep4UAQYptYcHNBYBp4DjXRRphEBiMlj +qzqnRuAsZva9VueVNfhvjxX697uhG0GFw1OjsuxAMWS5Sf/u14YRdCz3q1OS8sxdaOx XfqMmTC6DoQBM0hRmS1bnneYcBAKNX6G0HaQux7W+LpDh7zgKuQts6MecpgsFY5my/R2 SKJqby3G+Aue7QkzbvuWBX+w4lN+NJknthIpO2G3cmsKrrNxYzMijvFtGLez99R0YMly 3HgQ==
X-Gm-Message-State: AD7BkJImVsI9fLeE0SthCTGcgo2KE3UGBF8s/EGnxZzpa07lQY+ae+GHHqL3MzJUcwQ1Hw==
X-Received: by 10.55.165.3 with SMTP id o3mr6478150qke.0.1460078737175; Thu, 07 Apr 2016 18:25:37 -0700 (PDT)
Received: from [192.168.0.100] ([200.61.9.66]) by smtp.googlemail.com with ESMTPSA id g184sm4619303qkb.7.2016.04.07.18.25.35 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 07 Apr 2016 18:25:36 -0700 (PDT)
Subject: Re: Concerns about Singapore
To: Laurent Ciavaglia <laurent.ciavaglia@nokia.com>, ietf@ietf.org
References: <0D914666-C3D4-4CCE-AD5E-4E5B34EA1A73@piuha.net> <20160407182936.GA21340@pfrc.org> <CAB75xn780nNDjGa_Cc222J20-+1CCHt09Xp8KHzaK=n0xx51pg@mail.gmail.com> <5706B100.9040509@mnt.se> <CAB75xn6fmj84ROUtG5eUB3GerHx83hrEr3w5vSADY_g=BRg5FA@mail.gmail.com> <5706BA40.3060005@mnt.se> <alpine.DEB.2.02.1604072157240.31096@uplift.swm.pp.se> <5706C7B1.3040203@mnt.se> <5706CFB0.2090203@alcatel-lucent.com>
From: Leif Johansson <leifj@mnt.se>
Message-ID: <5707088C.9020406@mnt.se>
Date: Fri, 8 Apr 2016 03:25:32 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0
MIME-Version: 1.0
In-Reply-To: <5706CFB0.2090203@alcatel-lucent.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/URquiCDjA6Ip6ift2ojq9mhq8K8>
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: Fri, 08 Apr 2016 01:25:41 -0000

On 2016-04-07 23:22, Laurent Ciavaglia wrote:
> 
> 
> On 07/04/2016 22:48, EXT Leif Johansson wrote:
> [...]
>>> I'm sure I could come up with arguments why we should not go to USA or
>>> Sweden for our meetings, because neither place if perfect.
>> prove it :-)
> 
> death penalty.
> firearm death rate.
> D. Trump
> 
> --Laurent.

I was talking about Sweden :-)

We just watch the shamu show from our side of the atlantic


From nobody Thu Apr  7 18:31:55 2016
Return-Path: <leifj@mnt.se>
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 2D92812D16C for <ietf@ietfa.amsl.com>; Thu,  7 Apr 2016 18:31:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.83
X-Spam-Level: 
X-Spam-Status: No, score=-1.83 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_SORBS_WEB=0.77] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mnt-se.20150623.gappssmtp.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 3IftUTflkVDn for <ietf@ietfa.amsl.com>; Thu,  7 Apr 2016 18:31:52 -0700 (PDT)
Received: from mail-qg0-x232.google.com (mail-qg0-x232.google.com [IPv6:2607:f8b0:400d:c04::232]) (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 573F812D1CF for <ietf@ietf.org>; Thu,  7 Apr 2016 18:31:52 -0700 (PDT)
Received: by mail-qg0-x232.google.com with SMTP id f105so55650233qge.2 for <ietf@ietf.org>; Thu, 07 Apr 2016 18:31:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mnt-se.20150623.gappssmtp.com; s=20150623; h=subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=oxrJJsaYBpsDUgkzOT/44l58lQqnzakRJFFbAPLkvO0=; b=fyUytwelKrPdO7WPgJc079njKHzfp1lm2IR/zjx73YhTQagrZ58jmKOEg8OPqGQB6h gdpn7rUsgNDDzNYguwanHb7dImfPY1dGhObWv4qufM08JQhbrbxYUqzwBN2Wbbj/fJPH 1WIt7gXNHOa08YReBHK9HIpB8zL/V3wFO2SX1MQko4Oyfpbp1v8Q2Io/cmWCPwivGFc3 BHIbMnUMzbPfqC97RU0db0EMpdLGTBNstf0ViCErsQiaatCeZjg4JfWzYWAvZBBxMVa9 89GvxUC6Ynmc1x/0vAd1WHL1qfTyLnc8+7n5k3SVhMmvzImQL4rrE93XB5KJf6+Nfb/T jM2g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=oxrJJsaYBpsDUgkzOT/44l58lQqnzakRJFFbAPLkvO0=; b=WQ7z4Ek1r6H1aIGNH2TtrO0QP2ew7MJnZ7mTr93L/W+xX2h/ij9NN2k4rS8zSn9cpY ermoVmGJr2Jcdc9KRj+vBv8JjYjGwPJ3YDt9TBOL/2v61B+QqbLsU9ERkztdEnO+9Rh3 zHB9vqCn4OdHDmL8XVVh9idFUw8ZT4DiyPBZM86OGVtgBu23284z3w3caT22K9msriDP CoLYEZ4iCBjWgyvhiolfoXeTQ9xHYP/g2eM2haH/FuaDuM6FXbZ+wGrwf+zA9fcppv7e qmhtBwGKZ1Cp6pHQR+aXeuJnK2yEMp0PROOcI804IZEPbVzHdPHWjzPIatNgrg/BYb8q FE6Q==
X-Gm-Message-State: AD7BkJLXaTECsIby/ILz84dYRUZEjdrTNq8WUFrpD41XFQJr4VNpDHWpsWUzs1TNfr4k1Q==
X-Received: by 10.140.93.9 with SMTP id c9mr7986477qge.74.1460079111429; Thu, 07 Apr 2016 18:31:51 -0700 (PDT)
Received: from [192.168.0.100] ([200.61.9.66]) by smtp.googlemail.com with ESMTPSA id f91sm4601762qgf.4.2016.04.07.18.31.49 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 07 Apr 2016 18:31:50 -0700 (PDT)
Subject: Re: Concerns about Singapore
To: Yoav Nir <ynir.ietf@gmail.com>
References: <0D914666-C3D4-4CCE-AD5E-4E5B34EA1A73@piuha.net> <20160407182936.GA21340@pfrc.org> <CAB75xn780nNDjGa_Cc222J20-+1CCHt09Xp8KHzaK=n0xx51pg@mail.gmail.com> <5706B100.9040509@mnt.se> <CAB75xn6fmj84ROUtG5eUB3GerHx83hrEr3w5vSADY_g=BRg5FA@mail.gmail.com> <5706BA40.3060005@mnt.se> <alpine.DEB.2.02.1604072157240.31096@uplift.swm.pp.se> <5706C7B1.3040203@mnt.se> <56706297-A6B7-4E1D-B3DC-1B6085696C6C@gmail.com>
From: Leif Johansson <leifj@mnt.se>
Message-ID: <57070A03.2090508@mnt.se>
Date: Fri, 8 Apr 2016 03:31:47 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0
MIME-Version: 1.0
In-Reply-To: <56706297-A6B7-4E1D-B3DC-1B6085696C6C@gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/jOIFP5zQDODlrtsfXBq-uc9CPi4>
Cc: 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: Fri, 08 Apr 2016 01:31:54 -0000

On 2016-04-07 23:24, Yoav Nir wrote:
> 
> On 7 Apr 2016, at 5:48 PM, Leif Johansson <leifj@mnt.se> wrote:
> 
>>> I'm sure I could come up with arguments why we should not go to USA or
>>> Sweden for our meetings, because neither place if perfect.
>>
>> prove it :-)
> 
> Hereâ€™s a picture of Swedish Minister for Culture Lena Adelsohn Liljeroth cutting a cake:
> 
> http://assets.vice.com/content-images/contentimage/no-slug/4d991c394e90d21b560107314ce36105.jpg
> 
> What do I win?
> 

she got voted out so you could hire her off of the ex-politician
consultant pool


From nobody Thu Apr  7 20:20:39 2016
Return-Path: <rg+ietf@randy.pensive.org>
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 7E0FA12D62B for <ietf@ietfa.amsl.com>; Thu,  7 Apr 2016 20:20:38 -0700 (PDT)
X-Quarantine-ID: <lOWZGXo1YJeQ>
X-Virus-Scanned: amavisd-new at amsl.com
X-Amavis-Alert: BAD HEADER SECTION, Duplicate header field: "MIME-Version"
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] 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 lOWZGXo1YJeQ for <ietf@ietfa.amsl.com>; Thu,  7 Apr 2016 20:20:37 -0700 (PDT)
Received: from turing.pensive.org (turing.pensive.org [99.111.97.161]) by ietfa.amsl.com (Postfix) with ESMTP id 3C90F12D561 for <ietf@ietf.org>; Thu,  7 Apr 2016 20:20:37 -0700 (PDT)
Received: from dhcp-93ce.meeting.ietf.org (99.111.97.161) by  turing.pensive.org with ESMTP (EIMS X 3.3.9); Thu, 7 Apr 2016 20:20:36 -0700
Mime-Version: 1.0
Message-Id: <p0624061dd32cd3d549c0@dhcp-93ce.meeting.ietf.org>
In-Reply-To: <57059131.5000805@gmail.com>
References: <57058AE6.9010001@gmail.com> <57059131.5000805@gmail.com>
X-Mailer: Eudora for Mac OS X
Date: Thu, 7 Apr 2016 20:19:53 -0700
To: Alexandre Petrescu <alexandre.petrescu@gmail.com>, ietf@ietf.org
From: Randall Gellens <rg+ietf@randy.pensive.org>
Subject: Re: ITS BoF outcome - comment on charter (and raw minutes)
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Random-Sig-Tag: 1.0b28
X-Random-Sig-Tag: 1.0b28
X-Random-Sig-Tag: 1.0b28
X-Random-Sig-Tag: 1.0b28
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/XLXVKbN8A_0X2v9BGtTFxaPVlzg>
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: Fri, 08 Apr 2016 03:20:38 -0000

At 7:44 PM -0300 4/6/16, Alexandre Petrescu wrote:

>  The room used an echo-ey boomy public address system so the notes 
> were a bit hard to take.  We need better.

Indeed, it was extremely difficult to understand speakers because of 
this.  The center of the room was the worst for comprehension; the 
sides of the room were worst for ear pain.

-- 
Randall Gellens
Opinions are personal;    facts are suspect;    I speak for myself only
-------------- Randomly selected tag: ---------------
Creditors have better memories than debtors.
                                    --Benjamin Franklin


From nobody Thu Apr  7 20:58:46 2016
Return-Path: <chopps@chopps.org>
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 59AAD12D792 for <ietf@ietfa.amsl.com>; Thu,  7 Apr 2016 20:58:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.909
X-Spam-Level: 
X-Spam-Status: No, score=-1.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, T_RP_MATCHES_RCVD=-0.01] 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 cXc0-07xlLUO for <ietf@ietfa.amsl.com>; Thu,  7 Apr 2016 20:58:43 -0700 (PDT)
Received: from smtp.chopps.org (smtp.chopps.org [54.88.81.56]) by ietfa.amsl.com (Postfix) with ESMTP id A6C4A12D783 for <ietf@ietf.org>; Thu,  7 Apr 2016 20:58:43 -0700 (PDT)
Received: from [192.168.1.5] (24-247-68-31.dhcp.trcy.mi.charter.com [24.247.68.31]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by smtp.chopps.org (Postfix) with ESMTPSA id C35D96115C; Fri,  8 Apr 2016 03:58:42 +0000 (UTC)
Subject: Re: Concerns about Singapore
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Content-Type: multipart/signed; boundary="Apple-Mail=_22240C40-490B-4EA6-9991-98B377163753"; protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail 2.6b2
From: Christian Hopps <chopps@chopps.org>
In-Reply-To: <A9B63A6D-3102-482F-8FFC-2E57A5FD8336@nic.cz>
Date: Thu, 7 Apr 2016 23:58:41 -0400
Message-Id: <CC16B445-2B74-4182-BC58-F9D4BFFA1CCF@chopps.org>
References: <0D914666-C3D4-4CCE-AD5E-4E5B34EA1A73@piuha.net> <20160407182936.GA21340@pfrc.org> <CAB75xn780nNDjGa_Cc222J20-+1CCHt09Xp8KHzaK=n0xx51pg@mail.gmail.com> <5706B100.9040509@mnt.se> <CAB75xn6fmj84ROUtG5eUB3GerHx83hrEr3w5vSADY_g=BRg5FA@mail.gmail.com> <5706BA40.3060005@mnt.se> <alpine.DEB.2.02.1604072157240.31096@uplift.swm.pp.se> <A9B63A6D-3102-482F-8FFC-2E57A5FD8336@nic.cz>
To: Ladislav Lhotka <lhotka@nic.cz>
X-Mailer: Apple Mail (2.3124)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/8v-3upHxoCRHiQow38dLsYiyEh0>
Cc: "ietf@ietf.org 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: Fri, 08 Apr 2016 03:58:45 -0000

--Apple-Mail=_22240C40-490B-4EA6-9991-98B377163753
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_E6B97625-3466-4DEA-84BA-5AF762E1F750"


--Apple-Mail=_E6B97625-3466-4DEA-84BA-5AF762E1F750
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


> On Apr 7, 2016, at 4:08 PM, Ladislav Lhotka <lhotka@nic.cz> wrote:
>=20
> Right. And since Leif mentioned censorship, let me note that IETF =
already held a meeting in a country where censorship, and Internet =
censorship in particular, is commonplace.

I actually did not attend that meeting for this very reason. I am very =
proud to be a part of IETF and the open and inclusive process in which =
we work. I found it very odd, and disheartening that this site was =
chosen, and skipped it in protest.

Chris.

--Apple-Mail=_E6B97625-3466-4DEA-84BA-5AF762E1F750
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dus-ascii"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D""><br class=3D""><div><blockquote type=3D"cite" class=3D""><div =
class=3D"">On Apr 7, 2016, at 4:08 PM, Ladislav Lhotka &lt;<a =
href=3D"mailto:lhotka@nic.cz" class=3D"">lhotka@nic.cz</a>&gt; =
wrote:</div><br class=3D"Apple-interchange-newline"><div class=3D""><span =
style=3D"font-family: Helvetica; font-size: 16px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
orphans: auto; text-align: start; text-indent: 0px; text-transform: =
none; white-space: normal; widows: auto; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; float: none; display: inline =
!important;" class=3D"">Right. And since Leif mentioned censorship, let =
me note that IETF already held a meeting in a country where censorship, =
and Internet censorship in particular, is commonplace.</span><br =
style=3D"font-family: Helvetica; font-size: 16px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
orphans: auto; text-align: start; text-indent: 0px; text-transform: =
none; white-space: normal; widows: auto; word-spacing: 0px; =
-webkit-text-stroke-width: 0px;" class=3D""></div></blockquote></div><br =
class=3D""><div class=3D"">I actually did not attend that meeting for =
this very reason. I am very proud to be a part of IETF and the open and =
inclusive process in which we work. I found it very odd, and =
disheartening that this site was chosen, and skipped it in =
protest.</div><div class=3D""><br class=3D""></div><div =
class=3D"">Chris.</div></body></html>=

--Apple-Mail=_E6B97625-3466-4DEA-84BA-5AF762E1F750--

--Apple-Mail=_22240C40-490B-4EA6-9991-98B377163753
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQIcBAEBCgAGBQJXByxxAAoJEC4dgw7XuDAlLPAP/ijNUOYyhZPTQkhevESpokMM
gbyS8DTl7z/EZhrcbLNpqIFMf5Up2fQedshqHlDSk96OrCAlsznmPRVw3NxwSr9p
mL+R7W3cYbTF38nPSaQwNJ4351a+SomhjCBl2BQFTTzZoU3oBvx+TttHQy5xIISK
oCaM2oW+2xpUR1ghIDtcOMWw52gQOGz7arI2GYVqhTu8UEbkss6o4465kRC2n+Vm
N6PBNWkEw0vgAowXr+fIZHHWjHrQHHvu9UpqiqeMpIoztsfj2AUxnw2ZY26yZnHm
BTOy1lMTvJCEj793DzYqgY/qzkT4z2/HlDYffJsanV3t2h3s3W3AjcZK6X/ELxmW
slglgfcUoetXd549TJi5xMtltBw3peFftRnBXsOlupLrmuJBMPCbmxWQriUvWEeW
ptDwEKRB1O3snRT5dT5u4ZXrn61xOJ+/b5fl2Ilysx+kjfPtz9EKwCBLJwBQIEA5
WAY8Zn15w+ebws9ayv06TN8sarjevlsgh/bJ+d4M/uXcK7r9/cYragV7L8XBp0Ra
qBWdmhK8WTK0UuU8JsR6ihw7ZkSFeBLBsU03rD9jRkG95oVriQlskaQ9APNXaVE/
Zi/mj7U2yqm6Top60n5uYlhVCD40h4xee+ZjGYCR+CwXvzcRRnP6JvDU0uJBthab
S2MreNsDMXwz2UWOz/EC
=7kvf
-----END PGP SIGNATURE-----

--Apple-Mail=_22240C40-490B-4EA6-9991-98B377163753--


From nobody Thu Apr  7 21:53:12 2016
Return-Path: <narten@us.ibm.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 3E22112D76E for <ietf@ietfa.amsl.com>; Thu,  7 Apr 2016 21:53:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.212
X-Spam-Level: 
X-Spam-Status: No, score=-4.212 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 yS-mIypYkfzB for <ietf@ietfa.amsl.com>; Thu,  7 Apr 2016 21:53:07 -0700 (PDT)
Received: from e17.ny.us.ibm.com (e17.ny.us.ibm.com [129.33.205.207]) (using TLSv1.2 with cipher CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AE7AB12D124 for <ietf@ietf.org>; Thu,  7 Apr 2016 21:53:07 -0700 (PDT)
Received: from localhost by e17.ny.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for <ietf@ietf.org> from <narten@us.ibm.com>; Fri, 8 Apr 2016 00:53:06 -0400
Received: from d01dlp02.pok.ibm.com (9.56.250.167) by e17.ny.us.ibm.com (146.89.104.204) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Fri, 8 Apr 2016 00:53:05 -0400
X-IBM-Helo: d01dlp02.pok.ibm.com
X-IBM-MailFrom: narten@us.ibm.com
X-IBM-RcptTo: ietf@ietf.org
Received: from b01cxnp23032.gho.pok.ibm.com (b01cxnp23032.gho.pok.ibm.com [9.57.198.27]) by d01dlp02.pok.ibm.com (Postfix) with ESMTP id C3C686E8040 for <ietf@ietf.org>; Fri,  8 Apr 2016 00:39:53 -0400 (EDT)
Received: from b01ledav006.gho.pok.ibm.com (b01ledav006.gho.pok.ibm.com [9.57.199.111]) by b01cxnp23032.gho.pok.ibm.com (8.14.9/8.14.9/NCO v10.0) with ESMTP id u384r4DL31850700 for <ietf@ietf.org>; Fri, 8 Apr 2016 04:53:04 GMT
Received: from b01ledav006.gho.pok.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 5E53FAC03C for <ietf@ietf.org>; Fri,  8 Apr 2016 05:52:39 -0400 (EDT)
Received: from rotala.raleigh.ibm.com (unknown [9.27.222.27]) by b01ledav006.gho.pok.ibm.com (Postfix) with ESMTPS id 3E96EAC03A for <ietf@ietf.org>; Fri,  8 Apr 2016 05:52:39 -0400 (EDT)
Received: from rotala.raleigh.ibm.com (localhost [127.0.0.1]) by rotala.raleigh.ibm.com (8.15.2/8.12.5) with ESMTP id u384r3fL024834 for <ietf@ietf.org>; Fri, 8 Apr 2016 00:53:03 -0400
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.15.2/8.15.2/Submit) id u384r2Eh024774 for ietf@ietf.org; Fri, 8 Apr 2016 00:53:02 -0400
From: narten@us.ibm.com
Message-Id: <201604080453.u384r2Eh024774@rotala.raleigh.ibm.com>
Date: Fri, 08 Apr 2016 00:53:02 -0400
To: ietf@ietf.org
Subject: Weekly posting summary for ietf@ietf.org
User-Agent: Heirloom mailx 12.5 7/5/10
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-TM-AS-GCONF: 00
X-Content-Scanned: Fidelis XPS MAILER
x-cbid: 16040804-0041-0000-0000-000003D5A36B
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/TchQYn_-6JaSI81ZeWp3nQWIxgY>
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: Fri, 08 Apr 2016 04:53:11 -0000

Total of 143 messages in the last 7 days.
 
script run at: Fri Apr  8 00:53:02 EDT 2016
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
 10.49% |   15 |  8.89% |   123973 | john-ietf@jck.com
  4.20% |    6 |  7.03% |    98080 | stewe@stewe.org
  4.90% |    7 |  4.80% |    66964 | superuser@gmail.com
  4.20% |    6 |  3.30% |    45971 | leifj@mnt.se
  3.50% |    5 |  3.55% |    49553 | mellon@fugue.com
  4.20% |    6 |  2.80% |    39066 | dhc@dcrocker.net
  3.50% |    5 |  3.18% |    44385 | barryleiba@computer.org
  2.80% |    4 |  2.94% |    41008 | joelja@bogus.com
  2.80% |    4 |  2.63% |    36700 | alexandre.petrescu@gmail.com
  2.80% |    4 |  2.51% |    35036 | brian.e.carpenter@gmail.com
  2.80% |    4 |  2.27% |    31654 | melinda.shore@gmail.com
  2.80% |    4 |  1.86% |    25986 | adrian@olddog.co.uk
  2.10% |    3 |  2.50% |    34860 | tony@att.com
  2.10% |    3 |  1.83% |    25596 | stewart.bryant@gmail.com
  2.10% |    3 |  1.72% |    23967 | harish.pillay@gmail.com
  2.10% |    3 |  1.71% |    23836 | jari.arkko@piuha.net
  1.40% |    2 |  2.04% |    28489 | ron.even.tlv@gmail.com
  1.40% |    2 |  1.76% |    24516 | presnick@qti.qualcomm.com
  1.40% |    2 |  1.75% |    24439 | dhruv.ietf@gmail.com
  1.40% |    2 |  1.70% |    23665 | sob@sobco.com
  1.40% |    2 |  1.62% |    22545 | stephen.farrell@cs.tcd.ie
  1.40% |    2 |  1.51% |    21061 | harald@alvestrand.no
  1.40% |    2 |  1.25% |    17468 | michael.cameron@ericsson.com
  0.70% |    1 |  1.94% |    27015 | ggx@gigix.net
  0.70% |    1 |  1.87% |    26146 | peter@akayla.com
  1.40% |    2 |  1.06% |    14765 | laurent.ciavaglia@nokia.com
  0.70% |    1 |  1.64% |    22904 | worley@ariadne.com
  1.40% |    2 |  0.76% |    10538 | randy@psg.com
  0.70% |    1 |  1.22% |    17022 | stefan.winter@restena.lu
  0.70% |    1 |  1.20% |    16760 | david.black@emc.com
  0.70% |    1 |  1.17% |    16276 | abdussalambaryun@gmail.com
  0.70% |    1 |  1.09% |    15261 | terry.manderson@icann.org
  0.70% |    1 |  1.07% |    14968 | iab-chair@iab.org
  0.70% |    1 |  1.04% |    14525 | tjc@ecs.soton.ac.uk
  0.70% |    1 |  1.00% |    13948 | tobias.gondrom@gondrom.org
  0.70% |    1 |  0.99% |    13791 | rpelletier@isoc.org
  0.70% |    1 |  0.98% |    13625 | daedulus@btconnect.com
  0.70% |    1 |  0.91% |    12668 | joe@cdt.org
  0.70% |    1 |  0.82% |    11505 | jhildebr@cisco.com
  0.70% |    1 |  0.82% |    11387 | lars@netapp.com
  0.70% |    1 |  0.76% |    10661 | narten@us.ibm.com
  0.70% |    1 |  0.71% |     9929 | drc@virtualized.org
  0.70% |    1 |  0.70% |     9800 | aallen@blackberry.com
  0.70% |    1 |  0.68% |     9505 | lloyd.wood@yahoo.co.uk
  0.70% |    1 |  0.68% |     9450 | chopps@chopps.org
  0.70% |    1 |  0.64% |     8994 | spencerdawkins.ietf@gmail.com
  0.70% |    1 |  0.63% |     8847 | morrowc.lists@gmail.com
  0.70% |    1 |  0.62% |     8677 | fred@cisco.com
  0.70% |    1 |  0.61% |     8558 | linus@nordberg.se
  0.70% |    1 |  0.60% |     8330 | d3e3e3@gmail.com
  0.70% |    1 |  0.57% |     8004 | ben@nostrum.com
  0.70% |    1 |  0.56% |     7796 | mcr+ietf@sandelman.ca
  0.70% |    1 |  0.55% |     7717 | ynir.ietf@gmail.com
  0.70% |    1 |  0.55% |     7629 | lee@asgard.org
  0.70% |    1 |  0.54% |     7495 | lhotka@nic.cz
  0.70% |    1 |  0.52% |     7321 | lists@digitaldissidents.org
  0.70% |    1 |  0.52% |     7235 | swmike@swm.pp.se
  0.70% |    1 |  0.52% |     7204 | ldaigle@thinkingcat.com
  0.70% |    1 |  0.49% |     6791 | oej@edvina.net
  0.70% |    1 |  0.48% |     6712 | chair@ietf.org
  0.70% |    1 |  0.44% |     6155 | jhaas@pfrc.org
  0.70% |    1 |  0.44% |     6100 | adam@nostrum.com
  0.70% |    1 |  0.42% |     5914 | jared@puck.nether.net
  0.70% |    1 |  0.42% |     5825 | bertietf@bwijnen.net
  0.70% |    1 |  0.42% |     5798 | rsk@gsp.org
  0.70% |    1 |  0.41% |     5743 | rg+ietf@randy.pensive.org
  0.70% |    1 |  0.40% |     5529 | johnl@taugh.com
  0.70% |    1 |  0.38% |     5252 | francis.dupont@fdupont.fr
--------+------+--------+----------+------------------------
100.00% |  143 |100.00% |  1394893 | Total


From nobody Thu Apr  7 23:25:08 2016
Return-Path: <tony@att.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 1A46D12D16A for <ietf@ietfa.amsl.com>; Thu,  7 Apr 2016 23:25:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001] 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 IRPh7jdWeFLl for <ietf@ietfa.amsl.com>; Thu,  7 Apr 2016 23:25:05 -0700 (PDT)
Received: from mx0a-00191d01.pphosted.com (mx0a-00191d01.pphosted.com [67.231.149.140]) (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 733E412D15A for <ietf@ietf.org>; Thu,  7 Apr 2016 23:25:05 -0700 (PDT)
Received: from pps.filterd (m0053301.ppops.net [127.0.0.1]) by mx0a-00191d01.pphosted.com (8.15.0.59/8.15.0.59) with SMTP id u382OFgv024343; Thu, 7 Apr 2016 22:28:09 -0400
Received: from alpi155.enaf.aldc.att.com (sbcsmtp7.sbc.com [144.160.229.24]) by mx0a-00191d01.pphosted.com with ESMTP id 22615gjf6j-1 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT);  Thu, 07 Apr 2016 22:28:08 -0400
Received: from enaf.aldc.att.com (localhost [127.0.0.1]) by alpi155.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id u382S7Oh000704; Thu, 7 Apr 2016 22:28:07 -0400
Received: from mlpi408.sfdc.sbc.com (mlpi408.sfdc.sbc.com [130.9.128.240]) by alpi155.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id u382S4AQ000685 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 7 Apr 2016 22:28:04 -0400
Received: from MISOUT7MSGHUBAA.ITServices.sbc.com (MISOUT7MSGHUBAA.itservices.sbc.com [130.9.129.145]) by mlpi408.sfdc.sbc.com (RSA Interceptor); Fri, 8 Apr 2016 02:27:52 GMT
Received: from MISOUT7MSGUSRCG.ITServices.sbc.com ([169.254.7.206]) by MISOUT7MSGHUBAA.ITServices.sbc.com ([130.9.129.145]) with mapi id 14.03.0248.002; Thu, 7 Apr 2016 22:27:51 -0400
From: "HANSEN, TONY L" <tony@att.com>
To: "Murray S. Kucherawy" <superuser@gmail.com>
Subject: Re: Qualifying for NomCom
Thread-Topic: Qualifying for NomCom
Thread-Index: AQHRkPkBaE3TgFgCo0Odl4x3Th89cJ9/E2cAgAABUgCAAAB+AIAABFuAgAAma4CAAAS3AIAAAzOA///JioCAAEPugP//wCuAgABM04D///guAA==
Date: Fri, 8 Apr 2016 02:27:51 +0000
Message-ID: <6012C604-0922-4582-A505-F7934B5FD903@att.com>
References: <CAL0qLwY0FuDp5=RMFEhUMtkK=XNDxX2dogvVY7+OSy88jrrvOQ@mail.gmail.com> <CAPt1N1=SYpo-CiHoc07Ukb04Kb1LGV2=BPPyRLUsaqyLM9Hbwg@mail.gmail.com> <CAL0qLwbhYRqw7fXHzYY0=W-CpmeHeDdaZx3z2Qg0cA2aMrmVwg@mail.gmail.com> <CAPt1N1nqmC7NJyg2M6Na8vUj8T-qObO-1gHFEXZzrobb3oOQhA@mail.gmail.com> <CAL0qLwZHGa5OvSmZ=bTd6AWchsm4r=QaJn2nPqD+YjeWPmH9pA@mail.gmail.com> <24691.1460062367@obiwan.sandelman.ca> <5706CC94.3080804@gmail.com> <CAL0qLwYvCpL9wwHL0E33HRbMvcckpad=gV-VYgAomJpCdiSrpg@mail.gmail.com> <5E36120B-6D4E-4C0D-9905-2C698455D395@att.com> <CAL0qLwak6GRDYAcYqdOewoSmRj6DP5ptQKjqXkOedBaHcKC7WA@mail.gmail.com> <60B61524-EFF7-4489-A0C7-AA4A139FEF6C@att.com> <CAL0qLwYDW_zwfdr4-2=r0vt2Cb1wNFm+-aog0Wubu+8PbaYWEw@mail.gmail.com>
In-Reply-To: <CAL0qLwYDW_zwfdr4-2=r0vt2Cb1wNFm+-aog0Wubu+8PbaYWEw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.110.241.40]
Content-Type: multipart/alternative; boundary="_000_6012C60409224582A505F7934B5FD903attcom_"
MIME-Version: 1.0
X-RSA-Inspected: yes
X-RSA-Classifications: public
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2016-04-08_03:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_policy_notspam policy=outbound_policy 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-1603180000 definitions=main-1604080036
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/z7JfYrGcUVB2qpuFnSjH4o4Ahes>
Cc: ietf <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: Fri, 08 Apr 2016 06:25:07 -0000

--_000_6012C60409224582A505F7934B5FD903attcom_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

SSBkb24ndCBrbm93LiBJdCBzZWVtcyBsaWtlIGl0IGRlcGVuZHMgb24gdGhlIG91dGNvbWUgb2Yg
dGhlIGV4cGVyaW1lbnQgYXMgdG8gd2hhdCB0aGUgbmV4dCBzdGVwIHNob3VsZCBiZS4gSXQgbWF5
IGJlIG9idmlvdXMgYXQgdGhhdCBwb2ludCB3aGF0IHRoZSBhbnN3ZXIgc2hvdWxkIGJlLCBidXQg
bm90IHdoYXQgd2FzIHNwZWNpZmllZCBpbiBzZWN0aW9uIDIuIEkgZG9uJ3Qgd2FudCB1cyB0byBi
ZSBvdmVybHkgY29uc3RyYWluZWQgaW4gb3VyIGNob2ljZXMuDQoNClRoZXJlJ3MgYWN0dWFsbHkg
YW5vdGhlciBjaG9pY2UgdGhhdCBpcyBub3Qgc3BlY2lmaWVkOiBpdCB3YXMgYSBtaXN0YWtlIHRv
IGRvIHRoaXMgZXhwZXJpbWVudCBhbmQgdGhhdCB0aGUgcnVsZXMgc2hvdWxkIHJlbWFpbiB0aGUg
c2FtZSBhcyB0aGV5IGFyZSBub3cgYW5kIG5vdCBjaGFuZ2UuDQoNCkhlcmUncyBteSBmb3JtdWxh
dGlvbiBvZiB0aGUgNCBjaG9pY2VzOg0KDQoqKSBXZSBsZWFybmVkIGVub3VnaCB0byBzYXkgdGhh
dCBubyBjaGFuZ2UgbmVlZCB0byBiZSBtYWRlIHRvIHRoZSBjdXJyZW50IHJ1bGVzLg0KKikgV2Ug
bGVhcm5lZCBzb21lIHRoaW5ncyBhbmQgbmVlZCB0byBydW4gYW5vdGhlciBleHBlcmltZW50IHdp
dGggZGlmZmVyZW50IHBhcmFtZXRlcnMuDQoqKSBXZSBsZWFybmVkIGVub3VnaCB0byBrbm93IHdo
YXQgdGhlIGNoYW5nZSB0byB0aGUgY3VycmVudCBydWxlcyBpcyB0aGF0IG5lZWRzIHRvIGJlIG1h
ZGUsIGVpdGhlcg0KLSkgYXMgc3BlY2lmaWVkIGluIHNlY3Rpb24gMiBvcg0KLSkgc29tZSBvdGhl
ciBmb3JtdWxhdGlvbi4NCg0KVG9ueQ0KDQpGcm9tOiAiTXVycmF5IFMuIEt1Y2hlcmF3eSIgPHN1
cGVydXNlckBnbWFpbC5jb208bWFpbHRvOnN1cGVydXNlckBnbWFpbC5jb20+Pg0KRGF0ZTogVGh1
cnNkYXksIEFwcmlsIDcsIDIwMTYgYXQgNjo1NSBQTQ0KVG86IFRvbnkgSGFuc2VuIDx0b255QGF0
dC5jb208bWFpbHRvOnRvbnlAYXR0LmNvbT4+DQpDYzogaWV0ZiA8aWV0ZkBpZXRmLm9yZzxtYWls
dG86aWV0ZkBpZXRmLm9yZz4+DQpTdWJqZWN0OiBSZTogUXVhbGlmeWluZyBmb3IgTm9tQ29tDQoN
Ck9uIFRodSwgQXByIDcsIDIwMTYgYXQgNzoyMCBQTSwgSEFOU0VOLCBUT05ZIEwgPHRvbnlAYXR0
LmNvbTxtYWlsdG86dG9ueUBhdHQuY29tPj4gd3JvdGU6DQpObywgb3V0Y29tZSAxIHNheXMgdG8g
dXNlIHRoZSBjcml0ZXJpYSBpbiBzZWN0aW9uIDIgZGlyZWN0bHkgYXMgc3BlY2lmaWVkIHRoZXJl
LiBPdXRjb21lIDQgbGV0cyB1cyB0d2lkZGxlIGl0Lg0KDQpXb3VsZG4ndCB3ZSB3YW50IHRvIHJl
cGVhdCB0aGUgZXhwZXJpbWVudCB3aXRoIHRoZSB0d2lkZGxpbmcgYmVmb3JlIG1ha2luZyBpdCBw
YXJ0IG9mIHRoZSBCQ1A/ICBUaGF0J3Mgb3V0Y29tZSAyLg0KDQotTVNLDQo=

--_000_6012C60409224582A505F7934B5FD903attcom_
Content-Type: text/html; charset="utf-8"
Content-ID: <81F36D02F8D77A4B8FCD3F5B17EEA529@LOCAL>
Content-Transfer-Encoding: base64

PGh0bWw+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIgY29udGVudD0i
dGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjwvaGVhZD4NCjxib2R5IHN0eWxlPSJ3b3JkLXdy
YXA6IGJyZWFrLXdvcmQ7IC13ZWJraXQtbmJzcC1tb2RlOiBzcGFjZTsgLXdlYmtpdC1saW5lLWJy
ZWFrOiBhZnRlci13aGl0ZS1zcGFjZTsgY29sb3I6IHJnYigwLCAwLCAwKTsgZm9udC1zaXplOiAx
NHB4OyBmb250LWZhbWlseTogQ2FsaWJyaSwgc2Fucy1zZXJpZjsiPg0KPGRpdj4NCjxkaXY+SSBk
b24ndCBrbm93LiBJdCBzZWVtcyBsaWtlIGl0IGRlcGVuZHMgb24gdGhlIG91dGNvbWUgb2YgdGhl
IGV4cGVyaW1lbnQgYXMgdG8gd2hhdCB0aGUgbmV4dCBzdGVwIHNob3VsZCBiZS4gSXQgbWF5IGJl
IG9idmlvdXMgYXQgdGhhdCBwb2ludCB3aGF0IHRoZSBhbnN3ZXIgc2hvdWxkIGJlLCBidXQgbm90
IHdoYXQgd2FzIHNwZWNpZmllZCBpbiBzZWN0aW9uIDIuIEkgZG9uJ3Qgd2FudCB1cyB0byBiZSBv
dmVybHkgY29uc3RyYWluZWQgaW4NCiBvdXIgY2hvaWNlcy48L2Rpdj4NCjxkaXY+PGJyPg0KPC9k
aXY+DQo8ZGl2PlRoZXJlJ3MgYWN0dWFsbHkgYW5vdGhlciBjaG9pY2UgdGhhdCBpcyBub3Qgc3Bl
Y2lmaWVkOiBpdCB3YXMgYSBtaXN0YWtlIHRvIGRvIHRoaXMgZXhwZXJpbWVudCBhbmQgdGhhdCB0
aGUgcnVsZXMgc2hvdWxkIHJlbWFpbiB0aGUgc2FtZSBhcyB0aGV5IGFyZSBub3cgYW5kIG5vdCBj
aGFuZ2UuPC9kaXY+DQo8ZGl2Pjxicj4NCjwvZGl2Pg0KPGRpdj5IZXJlJ3MgbXkgZm9ybXVsYXRp
b24gb2YgdGhlIDQgY2hvaWNlczo8L2Rpdj4NCjxkaXY+PGJyPg0KPC9kaXY+DQo8ZGl2PiopIFdl
IGxlYXJuZWQgZW5vdWdoIHRvIHNheSB0aGF0IG5vIGNoYW5nZSBuZWVkIHRvIGJlIG1hZGUgdG8g
dGhlIGN1cnJlbnQgcnVsZXMuPC9kaXY+DQo8ZGl2PiopIFdlIGxlYXJuZWQgc29tZSB0aGluZ3Mg
YW5kIG5lZWQgdG8gcnVuIGFub3RoZXIgZXhwZXJpbWVudCB3aXRoIGRpZmZlcmVudCBwYXJhbWV0
ZXJzLjwvZGl2Pg0KPGRpdj4qKSBXZSBsZWFybmVkIGVub3VnaCB0byBrbm93IHdoYXQgdGhlIGNo
YW5nZSB0byB0aGUgY3VycmVudCBydWxlcyBpcyB0aGF0IG5lZWRzIHRvIGJlIG1hZGUsIGVpdGhl
ciZuYnNwOzwvZGl2Pg0KPGRpdj48c3BhbiBjbGFzcz0iQXBwbGUtdGFiLXNwYW4iIHN0eWxlPSJ3
aGl0ZS1zcGFjZTpwcmUiPjwvc3Bhbj4tKSZuYnNwO2FzIHNwZWNpZmllZCBpbiBzZWN0aW9uIDIg
b3ImbmJzcDs8L2Rpdj4NCjxkaXY+PHNwYW4gY2xhc3M9IkFwcGxlLXRhYi1zcGFuIiBzdHlsZT0i
d2hpdGUtc3BhY2U6cHJlIj48L3NwYW4+LSkmbmJzcDtzb21lIG90aGVyIGZvcm11bGF0aW9uLjwv
ZGl2Pg0KPGRpdj48YnI+DQo8L2Rpdj4NCjxkaXY+PHNwYW4gY2xhc3M9IkFwcGxlLXRhYi1zcGFu
IiBzdHlsZT0id2hpdGUtc3BhY2U6cHJlIj48L3NwYW4+VG9ueTwvZGl2Pg0KPGRpdj4NCjxkaXYg
aWQ9Ik1BQ19PVVRMT09LX1NJR05BVFVSRSI+PC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPGRpdj48
YnI+DQo8L2Rpdj4NCjxzcGFuIGlkPSJPTEtfU1JDX0JPRFlfU0VDVElPTiI+DQo8ZGl2IHN0eWxl
PSJmb250LWZhbWlseTpDYWxpYnJpOyBmb250LXNpemU6MTJwdDsgdGV4dC1hbGlnbjpsZWZ0OyBj
b2xvcjpibGFjazsgQk9SREVSLUJPVFRPTTogbWVkaXVtIG5vbmU7IEJPUkRFUi1MRUZUOiBtZWRp
dW0gbm9uZTsgUEFERElORy1CT1RUT006IDBpbjsgUEFERElORy1MRUZUOiAwaW47IFBBRERJTkct
UklHSFQ6IDBpbjsgQk9SREVSLVRPUDogI2I1YzRkZiAxcHQgc29saWQ7IEJPUkRFUi1SSUdIVDog
bWVkaXVtIG5vbmU7IFBBRERJTkctVE9QOiAzcHQiPg0KPHNwYW4gc3R5bGU9ImZvbnQtd2VpZ2h0
OmJvbGQiPkZyb206IDwvc3Bhbj4mcXVvdDtNdXJyYXkgUy4gS3VjaGVyYXd5JnF1b3Q7ICZsdDs8
YSBocmVmPSJtYWlsdG86c3VwZXJ1c2VyQGdtYWlsLmNvbSI+c3VwZXJ1c2VyQGdtYWlsLmNvbTwv
YT4mZ3Q7PGJyPg0KPHNwYW4gc3R5bGU9ImZvbnQtd2VpZ2h0OmJvbGQiPkRhdGU6IDwvc3Bhbj5U
aHVyc2RheSwgQXByaWwgNywgMjAxNiBhdCA2OjU1IFBNPGJyPg0KPHNwYW4gc3R5bGU9ImZvbnQt
d2VpZ2h0OmJvbGQiPlRvOiA8L3NwYW4+VG9ueSBIYW5zZW4gJmx0OzxhIGhyZWY9Im1haWx0bzp0
b255QGF0dC5jb20iPnRvbnlAYXR0LmNvbTwvYT4mZ3Q7PGJyPg0KPHNwYW4gc3R5bGU9ImZvbnQt
d2VpZ2h0OmJvbGQiPkNjOiA8L3NwYW4+aWV0ZiAmbHQ7PGEgaHJlZj0ibWFpbHRvOmlldGZAaWV0
Zi5vcmciPmlldGZAaWV0Zi5vcmc8L2E+Jmd0Ozxicj4NCjxzcGFuIHN0eWxlPSJmb250LXdlaWdo
dDpib2xkIj5TdWJqZWN0OiA8L3NwYW4+UmU6IFF1YWxpZnlpbmcgZm9yIE5vbUNvbTxicj4NCjwv
ZGl2Pg0KPGRpdj48YnI+DQo8L2Rpdj4NCjxkaXY+DQo8ZGl2Pg0KPGRpdiBkaXI9Imx0ciI+T24g
VGh1LCBBcHIgNywgMjAxNiBhdCA3OjIwIFBNLCBIQU5TRU4sIFRPTlkgTCA8c3BhbiBkaXI9Imx0
ciI+Jmx0OzxhIGhyZWY9Im1haWx0bzp0b255QGF0dC5jb20iIHRhcmdldD0iX2JsYW5rIj50b255
QGF0dC5jb208L2E+Jmd0Ozwvc3Bhbj4gd3JvdGU6PGJyPg0KPGRpdiBjbGFzcz0iZ21haWxfZXh0
cmEiPg0KPGRpdiBjbGFzcz0iZ21haWxfcXVvdGUiPg0KPGJsb2NrcXVvdGUgY2xhc3M9ImdtYWls
X3F1b3RlIiBzdHlsZT0ibWFyZ2luOjAgMCAwIC44ZXg7Ym9yZGVyLWxlZnQ6MXB4ICNjY2Mgc29s
aWQ7cGFkZGluZy1sZWZ0OjFleCI+DQo8ZGl2IHN0eWxlPSJ3b3JkLXdyYXA6YnJlYWstd29yZDtj
b2xvcjpyZ2IoMCwwLDApO2ZvbnQtc2l6ZToxNHB4O2ZvbnQtZmFtaWx5OkNhbGlicmksc2Fucy1z
ZXJpZiI+DQo8ZGl2Pg0KPGRpdj4NCjxkaXY+Tm8sIG91dGNvbWUgMSBzYXlzIHRvIHVzZSB0aGUg
Y3JpdGVyaWEgaW4gc2VjdGlvbiAyIGRpcmVjdGx5IGFzIHNwZWNpZmllZCB0aGVyZS4gT3V0Y29t
ZSA0IGxldHMgdXMgdHdpZGRsZSBpdC48L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwv
YmxvY2txdW90ZT4NCjxkaXY+PGJyPg0KPC9kaXY+DQo8ZGl2PldvdWxkbid0IHdlIHdhbnQgdG8g
cmVwZWF0IHRoZSBleHBlcmltZW50IHdpdGggdGhlIHR3aWRkbGluZyBiZWZvcmUgbWFraW5nIGl0
IHBhcnQgb2YgdGhlIEJDUD8mbmJzcDsgVGhhdCdzIG91dGNvbWUgMi48YnI+DQo8YnI+DQo8L2Rp
dj4NCjxkaXY+LU1TSzxicj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+
DQo8L2Rpdj4NCjwvc3Bhbj4NCjwvYm9keT4NCjwvaHRtbD4NCg==

--_000_6012C60409224582A505F7934B5FD903attcom_--


From nobody Fri Apr  8 02:57:53 2016
Return-Path: <lhotka@nic.cz>
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 1002112D7F7 for <ietf@ietfa.amsl.com>; Fri,  8 Apr 2016 02:57:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.01
X-Spam-Level: 
X-Spam-Status: No, score=-7.01 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nic.cz
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 nDPv4W1xynCx for <ietf@ietfa.amsl.com>; Fri,  8 Apr 2016 02:57:49 -0700 (PDT)
Received: from mail.nic.cz (mail.nic.cz [217.31.204.67]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5CCA212D7FF for <ietf@ietf.org>; Fri,  8 Apr 2016 02:57:49 -0700 (PDT)
Received: from [10.10.0.186] (unknown [190.111.246.211]) by mail.nic.cz (Postfix) with ESMTPSA id 9A27E180993; Fri,  8 Apr 2016 11:57:46 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=nic.cz; s=default; t=1460109467; bh=RnS8KH2siUe4XVZkKxAk6z87GdcSxT/C6gnwVndB0zM=; h=From:Date:To; b=ZDPSuZm/Fa6zbiOA1ejMR4EIPpuFCL+dqdCH6J5iNS6IVuoh6QsvBhJbNHV9m8NSq /HmBL389meLd5758GuihVoJbO77lfNkkYT0FO/uTjD5OuDeVQ9kvF8YNiaXAuCm6T0 hHjoItlO2KGOzUFmy0WTrgG0yTvk5LfFTXMVcUqk=
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Subject: Re: Concerns about Singapore
From: Ladislav Lhotka <lhotka@nic.cz>
In-Reply-To: <1070A34B-E88B-4BF3-95D0-15B6BF26A704@bgp.nu>
Date: Fri, 8 Apr 2016 06:57:43 -0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <21284D9D-8C4C-4F07-B087-0402C2D8CB21@nic.cz>
References: <0D914666-C3D4-4CCE-AD5E-4E5B34EA1A73@piuha.net> <20160407182936.GA21340@pfrc.org> <CAB75xn780nNDjGa_Cc222J20-+1CCHt09Xp8KHzaK=n0xx51pg@mail.gmail.com> <5706B100.9040509@mnt.se> <CAB75xn6fmj84ROUtG5eUB3GerHx83hrEr3w5vSADY_g=BRg5FA@mail.gmail.com> <5706BA40.3060005@mnt.se> <alpine.DEB.2.02.1604072157240.31096@uplift.swm.pp.se> <A9B63A6D-3102-482F-8FFC-2E57A5FD8336@nic.cz> <1070A34B-E88B-4BF3-95D0-15B6BF26A704@bgp.nu>
To: "John G. Scudder" <jgs@bgp.nu>
X-Mailer: Apple Mail (2.3124)
X-Virus-Scanned: clamav-milter 0.98.7 at mail
X-Virus-Status: Clean
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/jU5wJftx-40t-c2NFMyjUzb43qA>
Cc: "ietf@ietf.org 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: Fri, 08 Apr 2016 09:57:52 -0000

> On 07 Apr 2016, at 22:45, John G. Scudder <jgs@bgp.nu> wrote:
>=20
> On Apr 7, 2016, at 5:08 PM, Ladislav Lhotka <lhotka@nic.cz> wrote:
>> Yes, and speaking of myself, I am prepared, to a reasonable degree, =
to adjust my behaviour to those laws (and cultural habits as well).
>=20
> It's wonderful for you if you are always able to do so. Not everyone =
has that luxury. I don't think I can say this better, so I'll

I didn't say I am always able to do so. For example, if Canada (again) =
introduced visa for Czech citizens, I won't go there.=20

>  just quote:
>=20
> On Apr 7, 2016, at 3:29 PM, Jeffrey Haas <jhaas@pfrc.org> wrote:
>> The legal environments of the various countries we consider for =
venues
>> obviously must be a general consideration for our selection criteria. =
 For
>> most considerations, these are "here are thing you do not do - they =
are not
>> legal".
>>=20
>> For this particular issue, the consideration is whether the people =
themselves
>> are the thing that is illegal.

I haven't studied the Singapore laws, but the US State Department =
summary says:

   The Penal Code criminalizes any =E2=80=9Cact of gross indecency=E2=80=9D=
 ...

which I understand as behaviour, not people themselves.

Lada

>=20
> --John

--
Ladislav Lhotka, CZ.NIC Labs
PGP Key ID: E74E8C0C





From nobody Fri Apr  8 03:38:16 2016
Return-Path: <nalini.elkins@insidethestack.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 5AA8A12D5CA for <ietf@ietfa.amsl.com>; Fri,  8 Apr 2016 03:38:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.62
X-Spam-Level: 
X-Spam-Status: No, score=-2.62 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=yahoo.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 2j_0txdbTUEQ for <ietf@ietfa.amsl.com>; Fri,  8 Apr 2016 03:38:13 -0700 (PDT)
Received: from nm1-vm4.bullet.mail.ne1.yahoo.com (nm1-vm4.bullet.mail.ne1.yahoo.com [98.138.91.161]) (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 5B9A112D5A4 for <ietf@ietf.org>; Fri,  8 Apr 2016 03:38:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1460111892; bh=eiKso1Yha5CMnwyVhtRYpZIdxsYWovwssmrsfFkMp1I=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:From:Subject; b=KBIca1Fi0WuWGsvokRo8/t1bUpLqIXRbXMF+FNIMWP6p4ER6oQb4itsGl8IIpmM+c/os1dE51yCwz8MRhmfIY0n4H9jF2OwRZyouSVPQa1hJhNisJORMuDuSWKQxcGOiCOz/ri7wfQbI3xGnq+NtRwQ2dXodF51kqVK524NF6jaw4Fyg2ZpmEnpyYSvmtJlBU5bBES1z4/702spdz2FkKoEMIMImGvq2AMGRBoJH7/HOjDP8fVgkl688ThbWdk64e1nfjrWFaqXZF6vKRu/JJATKlN1gXvXIUxDbk7T6Oax3d+vSWkc0m+qHvgii8Ew8vhbKcVzLMcLQ/3ZNtKmMaA==
Received: from [98.138.226.178] by nm1.bullet.mail.ne1.yahoo.com with NNFMP; 08 Apr 2016 10:38:12 -0000
Received: from [98.138.89.198] by tm13.bullet.mail.ne1.yahoo.com with NNFMP; 08 Apr 2016 10:38:12 -0000
Received: from [127.0.0.1] by omp1056.mail.ne1.yahoo.com with NNFMP; 08 Apr 2016 10:38:12 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 440473.93667.bm@omp1056.mail.ne1.yahoo.com
X-YMail-OSG: shZKSf8VM1nDezpSyb0HR3AaU0rfRV_6_Ky71tykBUz8Kz4Gcfa1Hxw7Yq.XLpb Lgt_VuyV2D753tVZSrrqSIZBxPmbhXExJ2SdmXYtEiWGU3h0PNSr9aVJ28QynTaT7E2thVGu3CxD bq4pB27yJQVbaBKVVOyagHojl_fQqdzupCrcMb3F_RD9O5n3OApKwDo_fesvW5wttyxvD6J0fKBv lUhUZwr3flpqLsRjjLsxX1OhFM3exqnKZ4x640JRlg6nVuVz0T9wBAmIO8cEvFdan39DI_NO1nQV rY4cZKxwVgnj6IXN0o3Wssk3wZ5Zb.8igpsxIkDb1nxhTVE44CPBgMSEpXFx1jq0RMaJCHqNIpxQ syuVVaqZ.K09lNjS4amMLB3Q5R11.T1Ba.xS7IPh3M5c_uMnICDewRERtrt2CL2k7ewUOFm7R2S9 wKozF6cldTtJX4rJPWj2VVXoi1W1yPpr8yo9MaUIjG24i5.U3QcpH.BoE5ueHVW.07yS0_LC4ZSE ZTXm6ENp7FcZPpLq65w4wErir6s8W9oSTw8ulpWWKVEzMPFGNewQ1M0EmVpEW9TZVLAjzxUhMzn1 MHP78p7f7YBbm48L6pX.E7V18mIHsZF1BTm8ta9g-
Received: by 98.138.105.194; Fri, 08 Apr 2016 10:38:11 +0000 
Date: Fri, 8 Apr 2016 10:38:11 +0000 (UTC)
From: <nalini.elkins@insidethestack.com>
To: Dhruv Dhody <dhruv.ietf@gmail.com>, Leif Johansson <leifj@mnt.se>
Message-ID: <1481689286.47880.1460111891664.JavaMail.yahoo@mail.yahoo.com>
In-Reply-To: <CAB75xn6fmj84ROUtG5eUB3GerHx83hrEr3w5vSADY_g=BRg5FA@mail.gmail.com>
References: <CAB75xn6fmj84ROUtG5eUB3GerHx83hrEr3w5vSADY_g=BRg5FA@mail.gmail.com>
Subject: Re: Concerns about Singapore
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/KVUbmK_GJsgx7E8RmHvjPBZJMcA>
Cc: "ietf@ietf.org Discussion" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: nalini.elkins@insidethestack.com
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: Fri, 08 Apr 2016 10:38:15 -0000

On a positive note:

Pope Francis urges greater acceptance of homosexuals, non-traditional famil=
ies =20
http://edition.cnn.com/2016/04/08/europe/vatican-pope-family/index.html?adk=
ey=3Dbn
=20
Thanks,

Nalini Elkins
Inside Products, Inc.
www.insidethestack.com
(831) 659-8360



________________________________
From: Dhruv Dhody <dhruv.ietf@gmail.com>
To: Leif Johansson <leifj@mnt.se>=20
Cc: "ietf@ietf.org Discussion" <ietf@ietf.org>
Sent: Thursday, April 7, 2016 12:41 PM
Subject: Re: Concerns about Singapore



Hi Leif,=20


On Thu, Apr 7, 2016 at 4:12 PM, Leif Johansson <leifj@mnt.se> wrote:

On 2016-04-07 20:30, Dhruv Dhody wrote:
>> +1
>>
>> I am happy to see that LGBT inclusiveness taken seriously by the IETF.
>> But looking at the law on the books in black and white, would be doing a
>> disservice to a large region of the world (with a large number of
>> Internet users).
>
>I don't parse that actually.
>

=E2=80=8BSorry if I was not clear.=20
=E2=80=8B

>How is reading the law of Singapore "doing disservice to a large region
>of the world?"
>

=E2=80=8BNo, I meant that IETF would be doing a disservice to a large part =
of the world (that has on its books these laws). We need to have a nuanced =
approach and this being another factor in a multitude of factors. Having a =
blanket rule that the IETF will not go to any such place is something I dis=
agree with.  =20
=20

>I don't think "yes but many who live in Singapore are nice people"
>nor "yes but those laws are hardly ever applied" are useful arguments
>in this discussion but maybe thats just me...
>
>I am pretty sure that Ted (to pick a random example) would be able to
>travel to Singapore for an IETF and be /personally/ quite safe because
>as you say the laws of the land would be selectively applied.
>
>That is always the problem of selectively applied laws: they are used
>when it is convenient... and are often used to intimidate. That is why
>censorship is often self-administered in countries where there are
>censorship laws "on the books".
>

=E2=80=8BI agree with you. I understand this well, as an openly gay person,=
 living in a country with such laws=E2=80=8B on the book.=20
I hope these laws go away but till then, having a blanket rule against taki=
ng IETF to a big part of the world is something I find wrong.=20

Thanks!=20
Dhruv


>        Cheers Leif
>
>


From nobody Fri Apr  8 03:41:19 2016
Return-Path: <ynir.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 F19D312D0F9 for <ietf@ietfa.amsl.com>; Fri,  8 Apr 2016 03:41:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 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, RCVD_IN_DNSWL_LOW=-0.7, 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 l2bRyv-taC23 for <ietf@ietfa.amsl.com>; Fri,  8 Apr 2016 03:41:16 -0700 (PDT)
Received: from mail-qg0-x231.google.com (mail-qg0-x231.google.com [IPv6:2607:f8b0:400d:c04::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 59ADA12D0A5 for <ietf@ietf.org>; Fri,  8 Apr 2016 03:41:16 -0700 (PDT)
Received: by mail-qg0-x231.google.com with SMTP id c6so86679503qga.1 for <ietf@ietf.org>; Fri, 08 Apr 2016 03:41:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to; bh=CWTsAUcsi+m/ewM8BYYwkelSCq/VU8os4Mrg8+BIZbM=; b=wtV6xZk4Y3r7zMZ9TLYgSX43C5PCow2MKVJXm/Hx/w4JNLWOnXRWmXHDvLYNLEVrnN L7wwY4f83tDlWXa7IruHkn4sliUuPz0HbSSd+be+YRV8Svu+4qh2lnZI0a/dKnZz/gkD FyLfvcewG0qvScDhwvz57teIdXCbDFnzysNc5K20CF5zI26JMWjdS8/5sYTr+sWCribs 21/1mbXCP8fueH4hfxvQcK0xKZE+jDlrKniyO1CsZjagjPohvrkTJyvLvjhLTKAMZqK0 VSXbbNscRHGXLkwUVD60OdvievWWlxkPmmdp2gK1mRl6fmxY2PwapBG9q08VOCVR4bTK gLYQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to; bh=CWTsAUcsi+m/ewM8BYYwkelSCq/VU8os4Mrg8+BIZbM=; b=MMMPwNhIGE2RJIwrAtnrt3r2Q4sidIddakAIBbgD5TosaF90HVe52enuSLgoxmQT/b +YMe2gTr14i7ivmyq00iD5+6NNJB4KfeXXDiRlsRzeBDfrdKnKMsjOdGFeOF0p6XJayG CZmPfkLNOS/KuYeIKWvPI1z0LLFfS3aL+uOqqStqH21yDjuSLfTOFxMmOpHb8Wf6chb+ 7/GY4fMLsRNdRNby/FfKts1Hu/rwXWNL+ydt+EsjVrvI5m0qPm3SfMZrasTDrahTw3bS xoOIyDD6GIvrVU2y/JaOYnYeBTMcro5mLViKvIB2N1QOGqvDI8n7GmZrCbX/9NWl0OPm W3Eg==
X-Gm-Message-State: AD7BkJJzvnurVdWUrelgewhxBoYn0gLotB3KkF99ZkEkOJ8zrc6XMx1khiyrKZDS0YJQ3Q==
X-Received: by 10.140.157.16 with SMTP id d16mr10518158qhd.89.1460112075450; Fri, 08 Apr 2016 03:41:15 -0700 (PDT)
Received: from [10.10.5.235] ([190.111.246.204]) by smtp.gmail.com with ESMTPSA id f91sm5243005qgf.4.2016.04.08.03.41.13 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Fri, 08 Apr 2016 03:41:14 -0700 (PDT)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Subject: Re: Qualifying for NomCom
From: Yoav Nir <ynir.ietf@gmail.com>
In-Reply-To: <6012C604-0922-4582-A505-F7934B5FD903@att.com>
Date: Fri, 8 Apr 2016 07:41:12 -0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <0043FB5E-3688-4230-A4CA-C743E7321FF7@gmail.com>
References: <CAL0qLwY0FuDp5=RMFEhUMtkK=XNDxX2dogvVY7+OSy88jrrvOQ@mail.gmail.com> <CAPt1N1=SYpo-CiHoc07Ukb04Kb1LGV2=BPPyRLUsaqyLM9Hbwg@mail.gmail.com> <CAL0qLwbhYRqw7fXHzYY0=W-CpmeHeDdaZx3z2Qg0cA2aMrmVwg@mail.gmail.com> <CAPt1N1nqmC7NJyg2M6Na8vUj8T-qObO-1gHFEXZzrobb3oOQhA@mail.gmail.com> <CAL0qLwZHGa5OvSmZ=bTd6AWchsm4r=QaJn2nPqD+YjeWPmH9pA@mail.gmail.com> <24691.1460062367@obiwan.sandelman.ca> <5706CC94.3080804@gmail.com> <CAL0qLwYvCpL9wwHL0E33HRbMvcckpad=gV-VYgAomJpCdiSrpg@mail.gmail.com> <5E36120B-6D4E-4C0D-9905-2C698455D395@att.com> <CAL0qLwak6GRDYAcYqdOewoSmRj6DP5ptQKjqXkOedBaHcKC7WA@mail.gmail.com> <60B61524-EFF7-4489-A0C7-AA4A139FEF6C@att.com> <CAL0qLwYDW_zwfdr4-2=r0vt2Cb1wNFm+-aog0Wubu+8PbaYWEw@mail.gmail.com> <6012C604-0922-4582-A505-F7934B5FD903@att.com>
To: "Murray S. Kucherawy" <superuser@gmail.com>, ietf <ietf@ietf.org>
X-Mailer: Apple Mail (2.3124)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/zmZ0f9erX6gpWEfpvfpTE9H7Gys>
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: Fri, 08 Apr 2016 10:41:18 -0000

ISTM that regardless of how the questions are phrased, this experiment =
is rigged to succeed.=20

Because of the confidentiality requirements, all the information we are =
likely to get will be from a report by the NomCom chair, and even that =
is going to be sanitized to such a degree that it won=E2=80=99t tell us =
anything.

So anything short of the NomCom appointing 7 marketing types to the IESG =
who will promptly replace all WG chairs with supermodels to =E2=80=9Cimpro=
ve the image of the IETF=E2=80=9D is going to be considered a failure of =
this experiment. The overwhelmingly most likely outcome is =E2=80=9CWe =
ran the experiment, nothing horrible happened, no issue with extending =
this forever=E2=80=9D. Besides, the work of the NomCom cannot be =
evaluated when they complete their work. We have to evaluate them by =
what their appointees do, and that=E2=80=99s a couple of more years in =
the future.

Yoav




From nobody Fri Apr  8 03:45:41 2016
Return-Path: <ynir.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 D2F0C12D654 for <ietf@ietfa.amsl.com>; Fri,  8 Apr 2016 03:45:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 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, RCVD_IN_DNSWL_LOW=-0.7, 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 RsobUkL180j6 for <ietf@ietfa.amsl.com>; Fri,  8 Apr 2016 03:45:38 -0700 (PDT)
Received: from mail-qg0-x22d.google.com (mail-qg0-x22d.google.com [IPv6:2607:f8b0:400d:c04::22d]) (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 0FF5D12D64F for <ietf@ietf.org>; Fri,  8 Apr 2016 03:45:37 -0700 (PDT)
Received: by mail-qg0-x22d.google.com with SMTP id c6so86743689qga.1 for <ietf@ietf.org>; Fri, 08 Apr 2016 03:45:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=UuuO8ppMclothsQWF5ukYUjcmxaH8/DBLy3jcxHtTXE=; b=UtcrqkPEfxtMW9Dr8E4YLEThEwXtmlFvqo0zlMhJEgqrYtoSZoBV9KRmCmDbOQBv4B ZtgEPXh3DLnynEPCp9jMy6OdTw3TTemU1kxa+mmKaeU5t1H0ni7I3upPgIJxHWmM2fpc mduOQ2yXL79uAHFOsiA/9de6C17+30i1Tu5ijoGJ7N05Ls2EGUZsOF5ZNRwacLGSu1Be yEelics6H5EN6Uz1YJo70RjaBOLI5mp78nuUDnV82O1VvuKblKoFSF7pulwCi1s9Pshb BCOZ9FaguZAvO1XlAc+D7066VRhsffA6eDTMsoiUJr8QV1d1m2nBYPEfoRcIzOCikri2 Rauw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=UuuO8ppMclothsQWF5ukYUjcmxaH8/DBLy3jcxHtTXE=; b=GXoY/OXEuEpVetSYqANOuGN38AoTjAkUFIc1CpDBC1SojdPW28UVAqUf1p7F/ceN5P Abhcn4QAIGY57pFkIxOI3gaSUDXaKjFc4ofMkvQvJg4E1OTraxRE+rsrmStUemSsjd8d cUkkV/pXmBqOTqznR9BrFvP6brnjRMdoF59vosjMNHr12UQwKoBkQoXi/T7J6leSoQox Be59Dgw85++q+3kCWC4/1KB1F5H0eSIZ6Mayg5JPRUaV1Smr2SWX1gD20xiETLbxaJAp wOK0dNVTgdV8v3XpSfDYtJ7wpGRoO+2NyYMCGBeRjNeNWOSAkvCS/LH31No8qLK1B6z+ alRw==
X-Gm-Message-State: AD7BkJLiTvUOcUUx3WAXxOAwaTX/dGWFiql26XYOsSWapeUevE4hvBEJAWfYd8KN07FI2A==
X-Received: by 10.140.169.132 with SMTP id p126mr10608850qhp.71.1460112337097;  Fri, 08 Apr 2016 03:45:37 -0700 (PDT)
Received: from [10.10.5.235] ([190.111.246.204]) by smtp.gmail.com with ESMTPSA id t85sm5280430qki.10.2016.04.08.03.45.35 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Fri, 08 Apr 2016 03:45:36 -0700 (PDT)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Subject: Re: Concerns about Singapore
From: Yoav Nir <ynir.ietf@gmail.com>
In-Reply-To: <1481689286.47880.1460111891664.JavaMail.yahoo@mail.yahoo.com>
Date: Fri, 8 Apr 2016 07:45:33 -0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <6E18B072-412B-474D-963F-7EF20E31979E@gmail.com>
References: <CAB75xn6fmj84ROUtG5eUB3GerHx83hrEr3w5vSADY_g=BRg5FA@mail.gmail.com> <1481689286.47880.1460111891664.JavaMail.yahoo@mail.yahoo.com>
To: nalini.elkins@insidethestack.com
X-Mailer: Apple Mail (2.3124)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/K3Qoh-wu_tY2z44w3Pxi5WnpAXQ>
Cc: "ietf@ietf.org 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: Fri, 08 Apr 2016 10:45:40 -0000

> On 8 Apr 2016, at 7:38 AM, <nalini.elkins@insidethestack.com> =
<nalini.elkins@insidethestack.com> wrote:
>=20
> On a positive note:
>=20
> Pope Francis urges greater acceptance of homosexuals, non-traditional =
families =20
> =
http://edition.cnn.com/2016/04/08/europe/vatican-pope-family/index.html?ad=
key=3Dbn
>=20

That=E2=80=99s fine, but I don=E2=80=99t think the Vatican has a good =
venue for us. :-)

Yoav



From nobody Fri Apr  8 03:55:03 2016
Return-Path: <superuser@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 E385E12D642 for <ietf@ietfa.amsl.com>; Fri,  8 Apr 2016 03:55:01 -0700 (PDT)
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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 rHUTK9x5F8LD for <ietf@ietfa.amsl.com>; Fri,  8 Apr 2016 03:55:00 -0700 (PDT)
Received: from mail-vk0-x22f.google.com (mail-vk0-x22f.google.com [IPv6:2607:f8b0:400c:c05::22f]) (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 712F212D5CA for <ietf@ietf.org>; Fri,  8 Apr 2016 03:55:00 -0700 (PDT)
Received: by mail-vk0-x22f.google.com with SMTP id c4so133316889vkb.3 for <ietf@ietf.org>; Fri, 08 Apr 2016 03:55:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=NMgi/h+W3wjXOBfHonDpAIEEK2G17DhmrEvP4r/i2EM=; b=cedCTFyhDvslOLAPrtALlkW1qWExB9iW21mgzqiz1UpbFoRkTM07e2JrMJsctggns6 QCVUqSx0ws/QS8wee0kW0wtlysVr0lbJMvpbr1norUNrBu5cFdbLTpfexgxcG+O7fp6r nOdM4mr/YsVNEY9+pB3JPjJWAQivkvPK66s/0aECp3x+G7puh/f69Oei+5wdHhJphII0 vedaGj3yrDuJt9WJ88Kx00XUCnUfBVGVczg29l+nXa6YzqmtPda2JJFSSA7cjdCT3bFN M2gu8kicaDirUcPJuiAZi4YbfFfsloPXW/YTVSSZ5avfKBdqpNeTZHS4COwjKTsopcMf IIQg==
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:date :message-id:subject:from:to:cc; bh=NMgi/h+W3wjXOBfHonDpAIEEK2G17DhmrEvP4r/i2EM=; b=ZanyPeH3tYhugbCBRTfRxDIoRQm8oGiMLdtwg/tczJTYDZItMiqc/7zY88C2tOiim5 CjAjBqFrAib+PARaLlcUs8JZX5CDUqm905NiUu2YaTlhbDGLskccUxXoNeBhuZv6vJK6 /xawGzKpA52MsZ9pRi4LtdLvYXigXUVlrnOFMmQVz6uxtsiT+EIGGhPO9gYHw+3wrlHm ni7ZAYWPToaaJxpYXB+S6nH2loIG9xS+i64DYa2mNwiFF7FvmSPc0eDgb0Rhwjxs9hdB 0ip3HPZg6V9jIhYPls9cCH8JxV/+cS7Xr8BHIbgcGWefjwVi7tviWXYhC/s0z9vS47xZ jwRg==
X-Gm-Message-State: AD7BkJIeIroChAT2GBP42YRGDT3D0KmiqBr1OapJ3+Zy1SL4TFd8LGz+RD0e6RFTUga63XTrF6oePrcdd5SHgg==
MIME-Version: 1.0
X-Received: by 10.31.188.142 with SMTP id m136mr3806190vkf.89.1460112899643; Fri, 08 Apr 2016 03:54:59 -0700 (PDT)
Received: by 10.103.43.5 with HTTP; Fri, 8 Apr 2016 03:54:59 -0700 (PDT)
In-Reply-To: <0043FB5E-3688-4230-A4CA-C743E7321FF7@gmail.com>
References: <CAL0qLwY0FuDp5=RMFEhUMtkK=XNDxX2dogvVY7+OSy88jrrvOQ@mail.gmail.com> <CAPt1N1=SYpo-CiHoc07Ukb04Kb1LGV2=BPPyRLUsaqyLM9Hbwg@mail.gmail.com> <CAL0qLwbhYRqw7fXHzYY0=W-CpmeHeDdaZx3z2Qg0cA2aMrmVwg@mail.gmail.com> <CAPt1N1nqmC7NJyg2M6Na8vUj8T-qObO-1gHFEXZzrobb3oOQhA@mail.gmail.com> <CAL0qLwZHGa5OvSmZ=bTd6AWchsm4r=QaJn2nPqD+YjeWPmH9pA@mail.gmail.com> <24691.1460062367@obiwan.sandelman.ca> <5706CC94.3080804@gmail.com> <CAL0qLwYvCpL9wwHL0E33HRbMvcckpad=gV-VYgAomJpCdiSrpg@mail.gmail.com> <5E36120B-6D4E-4C0D-9905-2C698455D395@att.com> <CAL0qLwak6GRDYAcYqdOewoSmRj6DP5ptQKjqXkOedBaHcKC7WA@mail.gmail.com> <60B61524-EFF7-4489-A0C7-AA4A139FEF6C@att.com> <CAL0qLwYDW_zwfdr4-2=r0vt2Cb1wNFm+-aog0Wubu+8PbaYWEw@mail.gmail.com> <6012C604-0922-4582-A505-F7934B5FD903@att.com> <0043FB5E-3688-4230-A4CA-C743E7321FF7@gmail.com>
Date: Fri, 8 Apr 2016 07:54:59 -0300
Message-ID: <CAL0qLwaccAX3drzCEvnimqzx3YBnTgt0jOChVCi6F=n3jk46Cg@mail.gmail.com>
Subject: Re: Qualifying for NomCom
From: "Murray S. Kucherawy" <superuser@gmail.com>
To: Yoav Nir <ynir.ietf@gmail.com>
Content-Type: multipart/alternative; boundary=001a1143026eb720a4052ff7065b
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/tKErJ1jq_D2bq8yfLejtezCL5Go>
Cc: ietf <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: Fri, 08 Apr 2016 10:55:02 -0000

--001a1143026eb720a4052ff7065b
Content-Type: text/plain; charset=UTF-8

On Fri, Apr 8, 2016 at 7:41 AM, Yoav Nir <ynir.ietf@gmail.com> wrote:

> ISTM that regardless of how the questions are phrased, this experiment is
> rigged to succeed.
> [...]
>

Do you have any suggestions?

-MSK

--001a1143026eb720a4052ff7065b
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">On Fri, Apr 8, 2016 at 7:41 AM, Yoav Nir <span dir=3D"ltr"=
>&lt;<a href=3D"mailto:ynir.ietf@gmail.com" target=3D"_blank">ynir.ietf@gma=
il.com</a>&gt;</span> wrote:<br><div class=3D"gmail_extra"><div class=3D"gm=
ail_quote"><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bor=
der-left:1px #ccc solid;padding-left:1ex">ISTM that regardless of how the q=
uestions are phrased, this experiment is rigged to succeed.<br>
[...]<br></blockquote><div><br></div><div>Do you have any suggestions?<br><=
br></div><div>-MSK<br></div></div></div></div>

--001a1143026eb720a4052ff7065b--


From nobody Fri Apr  8 04:20:34 2016
Return-Path: <olejacobsen@me.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 0ED5F12D14F for <ietf@ietfa.amsl.com>; Fri,  8 Apr 2016 04:20:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.631
X-Spam-Level: 
X-Spam-Status: No, score=-2.631 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 ZxBxaUerLzA9 for <ietf@ietfa.amsl.com>; Fri,  8 Apr 2016 04:20:30 -0700 (PDT)
Received: from mr11p00im-asmtp003.me.com (mr11p00im-asmtp003.me.com [17.110.69.254]) (using TLSv1.2 with cipher DHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 765CE12D0F8 for <ietf@ietf.org>; Fri,  8 Apr 2016 04:20:30 -0700 (PDT)
Received: from [10.1.10.8] (173-11-110-134-SFBA.hfc.comcastbusiness.net [173.11.110.134]) by mr11p00im-asmtp003.me.com (Oracle Communications Messaging Server 7.0.5.36.0 64bit (built Sep 8 2015)) with ESMTPSA id <0O5B0078IBI11K30@mr11p00im-asmtp003.me.com> for ietf@ietf.org; Fri, 08 Apr 2016 11:20:30 +0000 (GMT)
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, definitions=2016-04-08_08:,, signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 clxscore=1011 suspectscore=1 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1510270003 definitions=main-1604080169
Date: Fri, 08 Apr 2016 04:20:25 -0700 (PDT)
From: Ole Jacobsen <olejacobsen@me.com>
To: nalini.elkins@insidethestack.com
Subject: Re: Concerns about Singapore
In-reply-to: <1481689286.47880.1460111891664.JavaMail.yahoo@mail.yahoo.com>
Message-id: <alpine.OSX.2.01.1604080418530.36488@rabdullah.local>
References: <CAB75xn6fmj84ROUtG5eUB3GerHx83hrEr3w5vSADY_g=BRg5FA@mail.gmail.com> <1481689286.47880.1460111891664.JavaMail.yahoo@mail.yahoo.com>
User-Agent: Alpine 2.01 (OSX 1266 2009-07-14)
MIME-version: 1.0
Content-type: TEXT/PLAIN; charset=US-ASCII
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/jaO71oqq1Vv6GVOS3GkEniM6el8>
Cc: "ietf@ietf.org Discussion" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: Ole Jacobsen <olejacobsen@me.com>
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: Fri, 08 Apr 2016 11:20:32 -0000

I found this website very interesting in terms of what to expect on
the ground in Singapore with respect to the issue at hand:

http://www.utopia-asia.com/tipssing.htm

Ole


Ole J. Jacobsen
Editor and Publisher
The Internet Protocol Journal
Office:  +1 415-550-9433
Cell:    +1 415-370-4628
docomo: (090) 3337-9311
Web: protocoljournal.org
E-mail: olejacobsen@me.com





From nobody Fri Apr  8 04:20:41 2016
Return-Path: <swmike@swm.pp.se>
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 B692E12D772 for <ietf@ietfa.amsl.com>; Fri,  8 Apr 2016 04:20:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.311
X-Spam-Level: 
X-Spam-Status: No, score=-4.311 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=swm.pp.se
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 Cj_6ITONZMjB for <ietf@ietfa.amsl.com>; Fri,  8 Apr 2016 04:20:33 -0700 (PDT)
Received: from uplift.swm.pp.se (swm.pp.se [212.247.200.143]) (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 4812612D0F8 for <ietf@ietf.org>; Fri,  8 Apr 2016 04:20:33 -0700 (PDT)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id 7EB41A2; Fri,  8 Apr 2016 13:20:21 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1460114421; bh=FkuBpS8w1rw5yxwhOHUEe1yAU5lTrhmKBYiLNm6DV14=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=jFBcotWT/s7wI5RUzeIc1KK636OgVmIwsxCf5RAy64eBNpa732PQt/JWx9SCI4VFs arR5+/KAOZNHeUQa4knDvn/gD3J0d3IuCp7v/YtADAsFlynoCFMDDxPu2AR2HY+tGG s2YwzkZz9KPL9CA9j5juEAcVHwjl5eSmcH/P1o/g=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 74F01A1; Fri,  8 Apr 2016 13:20:21 +0200 (CEST)
Date: Fri, 8 Apr 2016 13:20:21 +0200 (CEST)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Laurent Ciavaglia <laurent.ciavaglia@nokia.com>
Subject: Re: Concerns about Singapore
In-Reply-To: <5706CEEA.70402@alcatel-lucent.com>
Message-ID: <alpine.DEB.2.02.1604081319150.16013@uplift.swm.pp.se>
References: <0D914666-C3D4-4CCE-AD5E-4E5B34EA1A73@piuha.net> <20160407182936.GA21340@pfrc.org> <CAB75xn780nNDjGa_Cc222J20-+1CCHt09Xp8KHzaK=n0xx51pg@mail.gmail.com> <5706B100.9040509@mnt.se> <CAB75xn6fmj84ROUtG5eUB3GerHx83hrEr3w5vSADY_g=BRg5FA@mail.gmail.com> <5706BA40.3060005@mnt.se> <alpine.DEB.2.02.1604072157240.31096@uplift.swm.pp.se> <5706CEEA.70402@alcatel-lucent.com>
User-Agent: Alpine 2.02 (DEB 1266 2009-07-14)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/IEp5mGddd74rP6WHXLHow1Xb5xE>
Cc: "ietf@ietf.org 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: Fri, 08 Apr 2016 11:20:36 -0000

On Thu, 7 Apr 2016, Laurent Ciavaglia wrote:

> On 07/04/2016 22:00, EXT Mikael Abrahamsson wrote:
>> There are no perfect places to go.
> Except Minneapolis. ;)

http://www.dumblaws.com/laws/united-states/minnesota

"It is illegal to sleep naked."
"Oral sex is prohibited."

-- 
Mikael Abrahamsson    email: swmike@swm.pp.se


From nobody Fri Apr  8 04:22:07 2016
Return-Path: <jari.arkko@piuha.net>
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 E746412D570 for <ietf@ietfa.amsl.com>; Fri,  8 Apr 2016 04:22:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] 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 J_Yo75yFeA6v for <ietf@ietfa.amsl.com>; Fri,  8 Apr 2016 04:22:04 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [IPv6:2a00:1d50:2::130]) by ietfa.amsl.com (Postfix) with ESMTP id BCBED12D14F for <ietf@ietf.org>; Fri,  8 Apr 2016 04:22:03 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 0045D2CC9A; Fri,  8 Apr 2016 14:22:03 +0300 (EEST) (envelope-from jari.arkko@piuha.net)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hJOYIfUizPUs; Fri,  8 Apr 2016 14:22:02 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 111B12CC95; Fri,  8 Apr 2016 14:22:00 +0300 (EEST) (envelope-from jari.arkko@piuha.net)
Subject: Re: A distinction along Pete's dimensions
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Content-Type: multipart/signed; boundary="Apple-Mail=_3C989D15-16BF-44A0-A05E-4BC7B6EABE6F"; protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail 2.5.2
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <5706EAD5.9070408@dcrocker.net>
Date: Fri, 8 Apr 2016 08:22:00 -0300
Message-Id: <64652CD9-E9A1-4A4E-A68D-5FF3C8E431DB@piuha.net>
References: <0D914666-C3D4-4CCE-AD5E-4E5B34EA1A73@piuha.net> <20160407182936.GA21340@pfrc.org> <CAB75xn780nNDjGa_Cc222J20-+1CCHt09Xp8KHzaK=n0xx51pg@mail.gmail.com> <5706B100.9040509@mnt.se> <CAB75xn6fmj84ROUtG5eUB3GerHx83hrEr3w5vSADY_g=BRg5FA@mail.gmail.com> <5706BA40.3060005@mnt.se> <alpine.DEB.2.02.1604072157240.31096@uplift.swm.pp.se> <5706CEEA.70402@alcatel-lucent.com> <D8151E5B-3862-4A77-A3FD-18D63334AA29@mnt.se> <7E3E34E3-346F-49D4-8030-335E802BE150@puck.nether.net> <22E40FD2507C568AB2849D61@JcK-HP8200.jck.com> <5706EAD5.9070408@dcrocker.net>
To: dcrocker@bbiw.net
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/Li9W0HgONgP6toAXKSJ8vxYoMrs>
Cc: John C Klensin <john-ietf@jck.com>, "ietf@ietf.org 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: Fri, 08 Apr 2016 11:22:06 -0000

--Apple-Mail=_3C989D15-16BF-44A0-A05E-4BC7B6EABE6F
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252


>   So when a new country or city is being considered -- and by new, I =
think I mean 'we have never been there', but perhaps we need to leave =
room for reconsideration of previously-visited places? -- we float the =
general countries and maybe cities to the community and wait for support =
and objections.
>=20
>=20
> Whatever criteria the community chooses to apply at that time are the =
relevant criteria.  No theory or modeling or documentation or even =
consistency -- and especially no guessing and no errors by an anointed =
body -- are required.

This would certainly work for me. There is obviously the question of =
calling what the result of the community discussion is, but I would view =
the community discussion as informing the decision by the meetings =
committee and the IAOC, i.e., the purpose of the crowdsourcing is to =
uncover issues that a smaller set of people might not catch, and then we =
have a better basis for the final decision.

(Speaking personally, not representing IAOC or other opinions.)

Jari


--Apple-Mail=_3C989D15-16BF-44A0-A05E-4BC7B6EABE6F
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQIcBAEBCgAGBQJXB5RYAAoJEM80gCTQU46qq3IP/R45WIWQWa78u7Oiq5RNIlZa
hIPAtQDK+Jbe2dCA0neCJSoLjK0CK14CldbJVPkMQKs+i/ZTQY3xlTGwBrJp6L1E
cK9DatRVkZNPYqHuIySx7yzewZ6BtN90U96oJwZXgFxHscIuatSFQId9c3DYl/Dm
x9ibXhdfw9D2VHvpVWqvpl9F3NjvXpRNK/KcY5L6ExnGx5cZ0x41j3MV1jt/RUH+
6xcwSTcLO/hZ4Sr3JAa6i9xMRPuAB5dbGDsGIA522e1da3bCHWJ0TmeCFWKsFt0p
jn4RGSHprpLd49IgO98mslBvAMNuaNG1t4SkSmTbpu/sRUbsA27HSNR0Q7ql5J8b
zOWz6qOJAWXjXkf23T70Nn0Js3Mi7B2dm97l6GxSSaFNivabMp3NudOeVS8iH/zu
NjYKOFtQmvxdNtidKBcG6CfVdgITdd68SOVdr8/k/q9uAUc26F7IjspcmV3k4nqW
1dA9602JWOrasU/l98ko+kiQe0+s/aNJclcU+324EJj7x0eCt7uPd3VTVJdsCa53
c9KxEsfFFRkYuc9Kuxr8HXucRUJKWvDfsz0xKpH5bAr5qO/E29XhYaa6sWw35LKy
GVN1Th8nU5meN0v2evFEX9hXyuotuNMkJqpgrGeKdcz63Cbbq+39jYEyJgPRZ0wB
RJkhtnxEEd/r6Y/4MxdA
=01L6
-----END PGP SIGNATURE-----

--Apple-Mail=_3C989D15-16BF-44A0-A05E-4BC7B6EABE6F--


From nobody Fri Apr  8 04:28:29 2016
Return-Path: <olejacobsen@me.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 06B8412D8C5 for <ietf@ietfa.amsl.com>; Fri,  8 Apr 2016 04:28:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.631
X-Spam-Level: 
X-Spam-Status: No, score=-2.631 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 v4vBFQGSqo9D for <ietf@ietfa.amsl.com>; Fri,  8 Apr 2016 04:28:25 -0700 (PDT)
Received: from mr11p00im-asmtp003.me.com (mr11p00im-asmtp003.me.com [17.110.69.254]) (using TLSv1.2 with cipher DHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EC73012D8C7 for <ietf@ietf.org>; Fri,  8 Apr 2016 04:28:19 -0700 (PDT)
Received: from [10.1.10.8] (173-11-110-134-SFBA.hfc.comcastbusiness.net [173.11.110.134]) by mr11p00im-asmtp003.me.com (Oracle Communications Messaging Server 7.0.5.36.0 64bit (built Sep 8 2015)) with ESMTPSA id <0O5B00LYLBV7TR10@mr11p00im-asmtp003.me.com> for ietf@ietf.org; Fri, 08 Apr 2016 11:28:19 +0000 (GMT)
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, definitions=2016-04-08_08:,, signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 clxscore=1011 suspectscore=0 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1510270003 definitions=main-1604080170
Date: Fri, 08 Apr 2016 04:28:18 -0700 (PDT)
From: Ole Jacobsen <olejacobsen@me.com>
To: Christian Hopps <chopps@chopps.org>
Subject: China
In-reply-to: <CC16B445-2B74-4182-BC58-F9D4BFFA1CCF@chopps.org>
Message-id: <alpine.OSX.2.01.1604080420470.36488@rabdullah.local>
References: <0D914666-C3D4-4CCE-AD5E-4E5B34EA1A73@piuha.net> <20160407182936.GA21340@pfrc.org> <CAB75xn780nNDjGa_Cc222J20-+1CCHt09Xp8KHzaK=n0xx51pg@mail.gmail.com> <5706B100.9040509@mnt.se> <CAB75xn6fmj84ROUtG5eUB3GerHx83hrEr3w5vSADY_g=BRg5FA@mail.gmail.com> <5706BA40.3060005@mnt.se> <alpine.DEB.2.02.1604072157240.31096@uplift.swm.pp.se> <A9B63A6D-3102-482F-8FFC-2E57A5FD8336@nic.cz> <CC16B445-2B74-4182-BC58-F9D4BFFA1CCF@chopps.org>
User-Agent: Alpine 2.01 (OSX 1266 2009-07-14)
MIME-version: 1.0
Content-type: TEXT/PLAIN; charset=US-ASCII
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/oOdl6GB3bjg4m0p8MRVDV0tptS8>
Cc: "ietf@ietf.org Discussion" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: Ole Jacobsen <olejacobsen@me.com>
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: Fri, 08 Apr 2016 11:28:28 -0000

On Thu, 7 Apr 2016, Christian Hopps wrote:

> I actually did not attend that meeting for this very reason. I am 
> very proud to be a part of IETF and the open and inclusive process 
> in which we work. I found it very odd, and disheartening that this 
> site was chosen, and skipped it in protest.
> 
> Chris.
> 

Christian,

I am sorry to hear that. Our "open and inclusive process" comprises 
many participants from China who have traditionally faced harsh and 
unpredictable visa problems in North America. In fairness to them, we 
held that meeting in Beijing. Note that we did so following an 
extensive discussion on the IETF mailing list and after negotiating 
the removal of a rather ominous hotel clause, as well as an unfiltered
network in the meeting venue.

I will just add that "engagement" is often seen as a better strategy
than "boycott" in many circles, but we don't need to have that debate
here and now :-)

Ole


From nobody Fri Apr  8 04:29:01 2016
Return-Path: <anne-marie.eklund-lowinder@iis.se>
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 2BEEF12D8D1 for <ietf@ietfa.amsl.com>; Fri,  8 Apr 2016 04:29:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.011
X-Spam-Level: 
X-Spam-Status: No, score=-2.011 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=iis.se
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 rpmaDYMqB3tD for <ietf@ietfa.amsl.com>; Fri,  8 Apr 2016 04:28:56 -0700 (PDT)
Received: from relay2.iis.se (relay2.iis.se [IPv6:2001:67c:124c:2007::38]) (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 03B1D12D8CF for <ietf@ietf.org>; Fri,  8 Apr 2016 04:28:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=iis.se; s=iis2015; h=received:received:received:from:to:cc:subject:thread-topic:thread-index:date: message-id:references:in-reply-to:accept-language:content-language: x-ms-has-attach:x-ms-tnef-correlator:x-pgp-mapi-encoding-version: x-pgp-encoding-format:x-pgp-encoding-version: x-ms-exchange-transport-fromentityheader:x-originating-ip:content-type: mime-version; bh=Jvp5iryeICxUrKnujw+uObLHlEXp944ZK2m/okdWKwg=; b=eFrrlCHwYVCsIi4GwJF8tr2ErWuM3hVh8f7a6LDSZFLCrKeR65ChqNV9u8apVFDRda/LqciH6T5Sv VMblrEAbCaWRBrnBoYd+09PQFSbJLwGA0bQ9+Ov4qH2zJsoKhBERU7HFN8Zvcw6U9AxTMWyIzauBja n4lgkW/TRCAEEFcI=
Received: from exchange01.office.nic.se (unknown [IPv6:2001:67c:124c:3010::25]) by relay2.iis.se (Halon Mail Gateway) with ESMTPS; Fri,  8 Apr 2016 11:28:34 +0000 (UTC)
Received: from exchange02.office.nic.se (2001:67c:124c:2043::25) by exchange01.office.nic.se (2001:67c:124c:3010::25) with Microsoft SMTP Server (TLS) id 15.0.1130.7; Fri, 8 Apr 2016 13:28:49 +0200
Received: from exchange02.office.nic.se ([fe80::681b:9cef:675b:d880]) by exchange02.office.nic.se ([fe80::681b:9cef:675b:d880%14]) with mapi id 15.00.1130.005; Fri, 8 Apr 2016 13:28:49 +0200
From: =?iso-8859-1?Q?Anne-Marie_Eklund-L=F6winder?= <anne-marie.eklund-lowinder@iis.se>
To: Mikael Abrahamsson <swmike@swm.pp.se>, Laurent Ciavaglia <laurent.ciavaglia@nokia.com>
Subject: SV: Concerns about Singapore
Thread-Topic: Concerns about Singapore
Thread-Index: AQHRkOMXu/hpihCPBEqaEE0fggHlb59+s5IAgAAATwCAAAuKAIAACE2AgAACugCAAAKSAIAAFhAAgADq5YCAACLKMA==
Date: Fri, 8 Apr 2016 11:28:48 +0000
Message-ID: <55791011d19e40a792999c45b571ecc2@exchange02.office.nic.se>
References: <0D914666-C3D4-4CCE-AD5E-4E5B34EA1A73@piuha.net> <20160407182936.GA21340@pfrc.org> <CAB75xn780nNDjGa_Cc222J20-+1CCHt09Xp8KHzaK=n0xx51pg@mail.gmail.com> <5706B100.9040509@mnt.se> <CAB75xn6fmj84ROUtG5eUB3GerHx83hrEr3w5vSADY_g=BRg5FA@mail.gmail.com> <5706BA40.3060005@mnt.se> <alpine.DEB.2.02.1604072157240.31096@uplift.swm.pp.se> <5706CEEA.70402@alcatel-lucent.com> <alpine.DEB.2.02.1604081319150.16013@uplift.swm.pp.se>
In-Reply-To: <alpine.DEB.2.02.1604081319150.16013@uplift.swm.pp.se>
Accept-Language: sv-SE, en-US
Content-Language: sv-SE
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-pgp-mapi-encoding-version: 2.5.0
x-pgp-encoding-format: MIME
x-pgp-encoding-version: 2.0.2
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [2001:67c:124c:3024::15f0]
Content-Type: multipart/signed; boundary="PGP_Universal_2DE01FCF_DD825F12_2FFB3522_1719739C"; protocol="application/pgp-signature"; micalg=pgp-sha1
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/vHLPRnln9irYL4IaGOP_Wro_TKM>
Cc: "ietf@ietf.org 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: Fri, 08 Apr 2016 11:29:00 -0000

--PGP_Universal_2DE01FCF_DD825F12_2FFB3522_1719739C
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: QUOTED-PRINTABLE



> -----Ursprungligt meddelande-----
> Fr=C3=A5n: ietf [mailto:ietf-bounces@ietf.org] F=C3=B6r Mikael Abrahamsson
> Skickat: den 8 april 2016 13:20
> Till: Laurent Ciavaglia <laurent.ciavaglia@nokia.com>
> Kopia: ietf@ietf.org Discussion <ietf@ietf.org>
> =C3=84mne: Re: Concerns about Singapore
>=20
> On Thu, 7 Apr 2016, Laurent Ciavaglia wrote:
>=20
> > On 07/04/2016 22:00, EXT Mikael Abrahamsson wrote:
> >> There are no perfect places to go.
> > Except Minneapolis. ;)
>=20
> http://www.dumblaws.com/laws/united-states/minnesota
>=20
> "It is illegal to sleep naked."
> "Oral sex is prohibited."
>=20
> --
> Mikael Abrahamsson    email: swmike@swm.pp.se

Well, if you start to dance spontaneously on a restaurant in Sweden you are=
 in trouble. It's a law against that.
If guests start spontaneous dance in a tavern or bar without dance permissi=
on the owners must stop that at once, otherwise the owner will get a fine. =
Most recently in November 2014 a tavern in the city of G=C3=A4vle got a war=
ning after the police had secretly filmed guests that moved suspiciously to=
 the music.

The law is from the 1920ies or so. No one bothered to change it.

Anne-Marie


Anne-Marie Eklund L=C3=B6winder
Chief Information Security Officer, IIS
Direct: +46 8 452 35 17 | Mobile: +46 734 31 53 10 | https://www.iis.se/en/
anne-marie.eklund-lowinder@iis.se  | @amelsec




--PGP_Universal_2DE01FCF_DD825F12_2FFB3522_1719739C
Content-Type: application/pgp-signature; name="PGP.sig"
Content-Transfer-Encoding: 7BIT
Content-Disposition: attachment; filename="PGP.sig"

-----BEGIN PGP SIGNATURE-----
Version: 10.0.2 (Build 13)

iQA/AwUBVweV76Xc8AFCsc+UEQJ7xACgjUi4UY7oj6clAPmt5gX0n2loe2sAnAuK
pVpBOpIwd90lcyNHSNcKbwo3
=Q094
-----END PGP SIGNATURE-----

--PGP_Universal_2DE01FCF_DD825F12_2FFB3522_1719739C--


From nobody Fri Apr  8 04:34:40 2016
Return-Path: <dirkx@webweaving.org>
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 EE46E12D192 for <ietf@ietfa.amsl.com>; Fri,  8 Apr 2016 04:34:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Level: 
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 gUNgWbC5Eiz4 for <ietf@ietfa.amsl.com>; Fri,  8 Apr 2016 04:34:37 -0700 (PDT)
Received: from weser.webweaving.org (weser.webweaving.org [148.251.234.232]) (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 E32A812D177 for <ietf@ietf.org>; Fri,  8 Apr 2016 04:34:36 -0700 (PDT)
Received: from beeb.leiden.webweaving.org (5ED23D88.cm-7-3a.dynamic.ziggo.nl [94.210.61.136]) (authenticated bits=0) by weser.webweaving.org (8.15.2/8.15.2) with ESMTPSA id u38BXJE8085159 (version=TLSv1 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 8 Apr 2016 13:33:19 +0200 (CEST) (envelope-from dirkx@webweaving.org)
X-Authentication-Warning: weser.webweaving.org: Host 5ED23D88.cm-7-3a.dynamic.ziggo.nl [94.210.61.136] claimed to be beeb.leiden.webweaving.org
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 9.2 \(3112\))
Subject: Re: Concerns about Singapore
From: Dirk-Willem van Gulik <dirkx@webweaving.org>
In-Reply-To: <alpine.DEB.2.02.1604081319150.16013@uplift.swm.pp.se>
Date: Fri, 8 Apr 2016 13:33:19 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <AC70275F-4DEB-4192-9C85-1B8B0ADEBC02@webweaving.org>
References: <0D914666-C3D4-4CCE-AD5E-4E5B34EA1A73@piuha.net> <20160407182936.GA21340@pfrc.org> <CAB75xn780nNDjGa_Cc222J20-+1CCHt09Xp8KHzaK=n0xx51pg@mail.gmail.com> <5706B100.9040509@mnt.se> <CAB75xn6fmj84ROUtG5eUB3GerHx83hrEr3w5vSADY_g=BRg5FA@mail.gmail.com> <5706BA40.3060005@mnt.se> <alpine.DEB.2.02.1604072157240.31096@uplift.swm.pp.se> <5706CEEA.70402@alcatel-lucent.com> <alpine.DEB.2.02.1604081319150.16013@uplift.swm.pp.se>
To: Mikael Abrahamsson <swmike@swm.pp.se>
X-Mailer: Apple Mail (2.3112)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3 (weser.webweaving.org [148.251.234.232]); Fri, 08 Apr 2016 13:33:19 +0200 (CEST)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/BPjsALibm5qvrLj7uoCDf927jKM>
Cc: "ietf@ietf.org 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: Fri, 08 Apr 2016 11:34:39 -0000

> On 08 Apr 2016, at 13:20, Mikael Abrahamsson <swmike@swm.pp.se> wrote:
>=20
> On Thu, 7 Apr 2016, Laurent Ciavaglia wrote:
>=20
>> On 07/04/2016 22:00, EXT Mikael Abrahamsson wrote:
>>> There are no perfect places to go.
>> Except Minneapolis. ;)
>=20
> http://www.dumblaws.com/laws/united-states/minnesota
>=20
> "It is illegal to sleep naked."
> "Oral sex is prohibited.=E2=80=9D

Speaking of Minneapolis and the 40something IETF there - around 98 or =
99; before EAR was changed - and I had to travel to a country with laws =
so arcane that it regulated cryptography.  And being asked to justify =
why on earth one could not do IETFs in safe & sensible countries.

Dw.=


From nobody Fri Apr  8 05:26:54 2016
Return-Path: <sean@sn3rd.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 E512412D8B4 for <ietf@ietfa.amsl.com>; Fri,  8 Apr 2016 05:26:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level: 
X-Spam-Status: No, score=-2.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=sn3rd.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 W1UYJ8Gx1fqH for <ietf@ietfa.amsl.com>; Fri,  8 Apr 2016 05:26:50 -0700 (PDT)
Received: from mail-qg0-x22d.google.com (mail-qg0-x22d.google.com [IPv6:2607:f8b0:400d:c04::22d]) (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 359C812D837 for <ietf@ietf.org>; Fri,  8 Apr 2016 05:26:48 -0700 (PDT)
Received: by mail-qg0-x22d.google.com with SMTP id c6so88586512qga.1 for <ietf@ietf.org>; Fri, 08 Apr 2016 05:26:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sn3rd.com; s=google; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=d/GZrknrflgUFjPfkoWQVMH/hAUD9U9vwoDTsIFfa8I=; b=WrCEwpbHu7JUz653qrMuaa01rE5JDxpyTZvH7iarnJ09QwdiIJH2n1V73BLKlw2/R5 LRgvSA7J2sURHKG+fEj7mQ04RWNhzeZtJW33jz4f86VpF067kGjIOBCDN9TW/dbKNV/K 4JshlNGQ9JiCsz6RZTan8Ft9DIcXP8o+DvV94=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=d/GZrknrflgUFjPfkoWQVMH/hAUD9U9vwoDTsIFfa8I=; b=f9jlf/HBLyjFwXK2PZC/jFjWE6jad+AS54afsNE2zNRV6gdnCtkia2ecdr8tZL2EnC PEjbEVDS2Q9+rB95FD6s61RV+5bCIwfMNl/AdWizj1gyUNXz+eWybXCMhI0FvvagBNKP 0FNQCDs8/ULAf9h6ge1canKQxIEPxqh2DOpkhx5OaqRfbKE8KudpHTP6mJavDe/EvohV KV+Zl0W7mwG+a30OY0injpANkYL0AamV9Zm5rsO3cIKgCDn+A8cxjOlgjDcy1knXGgpr JrYY3tgFSw7HERgW4f6APKrXFx9jE0HFpbU9cuudyHHhCydT3HqubzP6UctxH5IhY3V+ Q0lA==
X-Gm-Message-State: AD7BkJKwb6iOEd0pI9f2U2Wc5p1TU7VsjGaJHQhN7BxKmFT12femOB5VDRjtCAjTxfwlZw==
X-Received: by 10.140.146.142 with SMTP id 136mr11346551qhs.30.1460118407260;  Fri, 08 Apr 2016 05:26:47 -0700 (PDT)
Received: from ?IPv6:2001:67c:370:136:d522:f12e:a98d:84bc? ([2001:67c:370:136:d522:f12e:a98d:84bc]) by smtp.gmail.com with ESMTPSA id r132sm5338168qhc.41.2016.04.08.05.26.45 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Fri, 08 Apr 2016 05:26:46 -0700 (PDT)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Subject: Re: Gen-ART LC review of draft-ietf-tls-chacha20-poly1305-04 - resend
From: Sean Turner <sean@sn3rd.com>
In-Reply-To: <017a01d190ca$ace223b0$06a66b10$@gmail.com>
Date: Fri, 8 Apr 2016 09:26:41 -0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <A8A038B3-E10F-4A94-99D3-2C4D23A6E065@sn3rd.com>
References: <017a01d190ca$ace223b0$06a66b10$@gmail.com>
To: Roni Even <ron.even.tlv@gmail.com>
X-Mailer: Apple Mail (2.3124)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/E8lDofEjGXRXOsB062_z4GiyklM>
Cc: gen-art@ietf.org, draft-ietf-tls-chacha20-poly1305.all@ietf.org, "ietf@ietf.org list" <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: Fri, 08 Apr 2016 12:26:52 -0000

> On Apr 07, 2016, at 09:40, Roni Even <ron.even.tlv@gmail.com> wrote:
>=20
> I am the assigned Gen-ART reviewer for this draft. For background on =
Gen-ART, please see the FAQ at =
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>=20
> Please resolve these comments along with any other Last Call comments =
you may receive.
>=20
> Document:  draft-ietf-tls-chacha20-poly1305-04
>=20
> Reviewer: Roni Even
>=20
> Review Date:2016=E2=80=933-28
>=20
> IETF LC End Date: 2016=E2=80=934-9
>=20
> IESG Telechat date:=20
>=20
> =20
> Summary: This draft is almost ready for publication as a standard =
track  RFC.
> =20
> =20
> =20
> Major issues:
> I am wondering why this is a standard track document and not =
informational since the registration requirements are specification =
required.  (RFC5246)

I=E2=80=99m not sure I agree that Specification Required implies =
informational track.  Specification Required permits registrations from =
informational/experimental drafts, but it certainly doesn=E2=80=99t =
require informational/experimental.

Also note, the registry rules are:

0-191	Standards Action			Refers to value of first =
byte
192-254	Specification Required		Refers to value of first byte
255		Reserved for Private Use  	Refers to value of first =
byte

> I am also wondering why this document updates RFC5246 and RFC6347.  =
Reading the document it looked to me that the registration document is =
used also to endorse this cypher suite by the IETF and if this is the =
case my view is that there should be two documents, one Informational =
for registration and the will be standard track and update RFC5246 and =
RFC6347
> For Example the following text from section 1 =E2=80=9CTherefore, a =
new stream cipher to replace RC4 and address all the  previous issues is =
needed. =E2=80=9C  provides what may look as a normative recommendation.

As far as the updates header:

The RC4 stream cipher which was in TLS1.0-1.2 is now prohibited =
[RFC7465] (note not deprecated it=E2=80=99s prohibited) and =
ChaCha20-Poly1305-based ciphers are the replacement.  So, we do in fact =
want folks who were using RC4 to switch to ChaCha20-Poly1305, hence the =
updates header.

As far as splitting the registrations/updates:

What you=E2=80=99re suggesting is certainly one way to do it, but the =
way we=E2=80=99ve been doing it for years in the security area (e.g., =
TLS, IPSec, S/MIME, PKIX) is as follows (there have, of course, been =
exceptions):

- (if needed) Informational RFC for algorithm

- Standards track RFC for how to use algorithm with security protocol. =
This is how AES, Camellia, etc. were documented for TLS.

Also in play here is the need to avoid a bunch of DOWNREFs because two =
of the ChaCha20-Poly1305 suites are SHOULDs in the draft TLS1.3.  =
DOWNREFs aren=E2=80=99t anything to be scared of, but where we can avoid =
them I think we should.

I guess I=E2=80=99d rather not devise new process and just keep on doing =
what we=E2=80=99ve been doing.

spt

PS we are currently in the process of discussing a change to make the =
entire range (minus the reserved) specification required, but that =
won=E2=80=99t complete for a while and the implementers want this now =
(technically yesterday).=20


From nobody Fri Apr  8 05:27:28 2016
Return-Path: <paul@nohats.ca>
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 85B7C12D8B4 for <ietf@ietfa.amsl.com>; Fri,  8 Apr 2016 05:27:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.11
X-Spam-Level: 
X-Spam-Status: No, score=-1.11 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_ALL=0.8, T_RP_MATCHES_RCVD=-0.01] autolearn=no 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 Ow-FL66q2OlC for <ietf@ietfa.amsl.com>; Fri,  8 Apr 2016 05:27:24 -0700 (PDT)
Received: from mx.nohats.ca (mx.nohats.ca [IPv6:2a03:6000:1004:1::68]) (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 A476612D8CF for <ietf@ietf.org>; Fri,  8 Apr 2016 05:27:15 -0700 (PDT)
Received: from localhost (localhost [IPv6:::1]) by mx.nohats.ca (Postfix) with ESMTP id 3qhJcc5Wbbz7kj; Fri,  8 Apr 2016 14:27:12 +0200 (CEST)
X-OPENPGPKEY: Message passed unmodified
X-Virus-Scanned: amavisd-new at mx.nohats.ca
Received: from mx.nohats.ca ([IPv6:::1]) by localhost (mx.nohats.ca [IPv6:::1]) (amavisd-new, port 10024) with ESMTP id 6IzUUmEN9Wae; Fri,  8 Apr 2016 14:27:11 +0200 (CEST)
Received: from bofh.nohats.ca (206-248-139-105.dsl.teksavvy.com [206.248.139.105]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx.nohats.ca (Postfix) with ESMTPS; Fri,  8 Apr 2016 14:27:10 +0200 (CEST)
Received: from [10.220.0.173] (unknown [200.49.217.86]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by bofh.nohats.ca (Postfix) with ESMTPSA id CE05F6019B72; Fri,  8 Apr 2016 08:27:08 -0400 (EDT)
DKIM-Filter: OpenDKIM Filter v2.10.3 bofh.nohats.ca CE05F6019B72
References: <CAB75xn6fmj84ROUtG5eUB3GerHx83hrEr3w5vSADY_g=BRg5FA@mail.gmail.com> <1481689286.47880.1460111891664.JavaMail.yahoo@mail.yahoo.com> <6E18B072-412B-474D-963F-7EF20E31979E@gmail.com>
Mime-Version: 1.0 (1.0)
In-Reply-To: <6E18B072-412B-474D-963F-7EF20E31979E@gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Message-Id: <3352E874-D874-4676-B8CA-1C9E099F72F3@nohats.ca>
X-Mailer: iPhone Mail (13E238)
From: Paul Wouters <paul@nohats.ca>
Subject: Re: Concerns about Singapore
Date: Fri, 8 Apr 2016 09:26:59 -0300
To: Yoav Nir <ynir.ietf@gmail.com>
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/b_MChQ6vl0Lyan-bFJjxJRD7aCw>
Cc: "ietf@ietf.org 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: Fri, 08 Apr 2016 12:27:26 -0000

> On Apr 8, 2016, at 07:45, Yoav Nir <ynir.ietf@gmail.com> wrote:
>=20
>=20
>> On 8 Apr 2016, at 7:38 AM, <nalini.elkins@insidethestack.com> <nalini.elk=
ins@insidethestack.com> wrote:
>>=20
>> On a positive note:
>>=20
>> Pope Francis urges greater acceptance of homosexuals, non-traditional fam=
ilies =20
>> http://edition.cnn.com/2016/04/08/europe/vatican-pope-family/index.html?a=
dkey=3Dbn
>>=20
>=20
> That=E2=80=99s fine, but I don=E2=80=99t think the Vatican has a good venu=
e for us. :-)

But we could adopt the Conclave model of decision making!=20

Paul=


From nobody Fri Apr  8 05:31:49 2016
Return-Path: <paf@frobbit.se>
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 39D5312D7E5 for <ietf@ietfa.amsl.com>; Fri,  8 Apr 2016 05:31:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.611
X-Spam-Level: 
X-Spam-Status: No, score=-2.611 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 d081OeJ-txSO for <ietf@ietfa.amsl.com>; Fri,  8 Apr 2016 05:31:46 -0700 (PDT)
Received: from mail.frobbit.se (mail.frobbit.se [IPv6:2a02:80:3ffe::176]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8DF6212D760 for <ietf@ietf.org>; Fri,  8 Apr 2016 05:31:46 -0700 (PDT)
Received: from [192.71.80.209] (vpn-client-209.netnod.se [192.71.80.209]) by mail.frobbit.se (Postfix) with ESMTPSA id C5D5921455; Fri,  8 Apr 2016 14:31:43 +0200 (CEST)
From: "Patrik =?utf-8?b?RsOkbHRzdHLDtm0=?=" <paf@frobbit.se>
To: "Anne-Marie =?utf-8?q?Eklund-L=C3=B6winder?=" <anne-marie.eklund-lowinder@iis.se>
Subject: Re: Concerns about Singapore
Date: Fri, 08 Apr 2016 14:31:43 +0200
Message-ID: <6167B6AD-8A00-4C16-AF93-69A195BC2F86@frobbit.se>
In-Reply-To: <55791011d19e40a792999c45b571ecc2@exchange02.office.nic.se>
References: <0D914666-C3D4-4CCE-AD5E-4E5B34EA1A73@piuha.net> <20160407182936.GA21340@pfrc.org> <CAB75xn780nNDjGa_Cc222J20-+1CCHt09Xp8KHzaK=n0xx51pg@mail.gmail.com> <5706B100.9040509@mnt.se> <CAB75xn6fmj84ROUtG5eUB3GerHx83hrEr3w5vSADY_g=BRg5FA@mail.gmail.com> <5706BA40.3060005@mnt.se> <alpine.DEB.2.02.1604072157240.31096@uplift.swm.pp.se> <5706CEEA.70402@alcatel-lucent.com> <alpine.DEB.2.02.1604081319150.16013@uplift.swm.pp.se> <55791011d19e40a792999c45b571ecc2@exchange02.office.nic.se>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=_MailMate_B77323E3-B580-492C-8148-A39C1DB3B757_="; micalg=pgp-sha1; protocol="application/pgp-signature"
X-Mailer: MailMate (1.9.4r5234)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/85VyYdLb7RJ-92La29ReZgiCyEc>
Cc: "ietf@ietf.org 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: Fri, 08 Apr 2016 12:31:48 -0000

This is an OpenPGP/MIME signed message (RFC 3156 and 4880).

--=_MailMate_B77323E3-B580-492C-8148-A39C1DB3B757_=
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable



On 8 Apr 2016, at 13:28, Anne-Marie Eklund-L=C3=B6winder wrote:

> The law is from the 1920ies or so. No one bothered to change it.

This legislation is now to be removed.

The parliament of Sweden is discussing the issue on April 14 2016.

   paf

--=_MailMate_B77323E3-B580-492C-8148-A39C1DB3B757_=
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename=signature.asc
Content-Type: application/pgp-signature; name=signature.asc

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iEYEARECAAYFAlcHpK8ACgkQrMabGguI182qOACfbM6E08Zf3bheTTtAnbQt/ipr
iDUAn2DDxyee+WgTJC21Dsc9Ef22+udQ
=v7d0
-----END PGP SIGNATURE-----

--=_MailMate_B77323E3-B580-492C-8148-A39C1DB3B757_=--


From nobody Fri Apr  8 06:32:38 2016
Return-Path: <mcr+ietf@sandelman.ca>
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 0711E12D89A for <ietf@ietfa.amsl.com>; Fri,  8 Apr 2016 06:32:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Level: 
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 1refHiR2Y6rf for <ietf@ietfa.amsl.com>; Fri,  8 Apr 2016 06:32:30 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9485212D897 for <ietf@ietf.org>; Fri,  8 Apr 2016 06:32:30 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 4AEFC2009E for <ietf@ietf.org>; Fri,  8 Apr 2016 09:36:08 -0400 (EDT)
Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 538A663755 for <ietf@ietf.org>; Fri,  8 Apr 2016 09:32:29 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: "ietf\@ietf.org Discussion" <ietf@ietf.org>
Subject: Re: Concerns about Singapore
In-Reply-To: <A9B63A6D-3102-482F-8FFC-2E57A5FD8336@nic.cz>
References: <0D914666-C3D4-4CCE-AD5E-4E5B34EA1A73@piuha.net> <20160407182936.GA21340@pfrc.org> <CAB75xn780nNDjGa_Cc222J20-+1CCHt09Xp8KHzaK=n0xx51pg@mail.gmail.com> <5706B100.9040509@mnt.se> <CAB75xn6fmj84ROUtG5eUB3GerHx83hrEr3w5vSADY_g=BRg5FA@mail.gmail.com> <5706BA40.3060005@mnt.se> <alpine.DEB.2.02.1604072157240.31096@uplift.swm.pp.se> <A9B63A6D-3102-482F-8FFC-2E57A5FD8336@nic.cz>
X-Maniler: MH-E 8.6; nmh 1.6+dev; GNU Emacs 24.4.2
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Fri, 08 Apr 2016 09:32:29 -0400
Message-ID: <16925.1460122349@obiwan.sandelman.ca>
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/Tpwc6-PQNL8mUzoGJtN9SHdzyc0>
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: Fri, 08 Apr 2016 13:32:36 -0000

--=-=-=
Content-Type: text/plain


Ladislav Lhotka <lhotka@nic.cz> wrote:
    >> I'm sure I could come up with arguments why we should not go to USA or
    >> Sweden for our meetings, because neither place if perfect.

    > Right. And since Leif mentioned censorship, let me note that IETF
    > already held a meeting in a country where censorship, and Internet
    > censorship in particular, is commonplace.

yes, we tried that.  My impression is that there were two changes we made,
one was known in advance (closed network), the other was unknown (badges
being checked).
I'm not sure we were happy with either result.  I didn't go to Beijing.

    > Yes, and speaking of myself, I am prepared, to a reasonable degree, to
    > adjust my behaviour to those laws (and cultural habits as well).

I'm pretty sure that I won't make it for simple reasons of economy.
I think it's a pretty expensive city, and I'm not clear that there are
three-star options.

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-




--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQEVAwUBVwey6oCLcPvd0N1lAQLPegf/YndIYYoY2rqbWN9GGmjzdqOA9QM/KXk6
imJMs/N8pBdrJ2NvH4+g2QBM9bh99ds9xZKXedkyb+w+wxCkL4RHSyokGYaaKlcS
7RIa68Zkz2Iyl3JL3qTcRhh5HjVg++yBlVwM3izdx3EWM0RmLbJv5+u1eTYYnelh
jtuVHqbJBWD2ymML5yH+7HGDd3L5zPvxCH6K8hz56YtZ+fKC9SDo+rLGYK2D1q3q
tQj5CGp2IRWuXlF2+hHZVlE20iaTBbqXcmCR72zflYrSTNctQGbifHmEHZWBFVwn
VVGKj6xiKnHRGF+2q8Wmm7DOBlsHjQC2u1rzAgzaTHVQ3ZfGcI4vDQ==
=EZy9
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Fri Apr  8 06:35:06 2016
Return-Path: <jhaas@slice.pfrc.org>
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 3AB0012D58D for <ietf@ietfa.amsl.com>; Fri,  8 Apr 2016 06:35:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.912
X-Spam-Level: 
X-Spam-Status: No, score=-1.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 hnoXRTcE0eLD for <ietf@ietfa.amsl.com>; Fri,  8 Apr 2016 06:35:02 -0700 (PDT)
Received: from slice.pfrc.org (slice.pfrc.org [67.207.130.108]) by ietfa.amsl.com (Postfix) with ESMTP id 858CB12D0FF for <ietf@ietf.org>; Fri,  8 Apr 2016 06:35:02 -0700 (PDT)
Received: by slice.pfrc.org (Postfix, from userid 1001) id D958D1E83B; Fri,  8 Apr 2016 09:39:14 -0400 (EDT)
Date: Fri, 8 Apr 2016 09:39:14 -0400
From: Jeffrey Haas <jhaas@pfrc.org>
To: Ole Jacobsen <olejacobsen@me.com>
Subject: Re: China
Message-ID: <20160408133914.GB17588@pfrc.org>
References: <0D914666-C3D4-4CCE-AD5E-4E5B34EA1A73@piuha.net> <20160407182936.GA21340@pfrc.org> <CAB75xn780nNDjGa_Cc222J20-+1CCHt09Xp8KHzaK=n0xx51pg@mail.gmail.com> <5706B100.9040509@mnt.se> <CAB75xn6fmj84ROUtG5eUB3GerHx83hrEr3w5vSADY_g=BRg5FA@mail.gmail.com> <5706BA40.3060005@mnt.se> <alpine.DEB.2.02.1604072157240.31096@uplift.swm.pp.se> <A9B63A6D-3102-482F-8FFC-2E57A5FD8336@nic.cz> <CC16B445-2B74-4182-BC58-F9D4BFFA1CCF@chopps.org> <alpine.OSX.2.01.1604080420470.36488@rabdullah.local>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <alpine.OSX.2.01.1604080420470.36488@rabdullah.local>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/1mwcWgnHBVq0xEe0XnR2j8LcetQ>
Cc: "ietf@ietf.org 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: Fri, 08 Apr 2016 13:35:04 -0000

On Fri, Apr 08, 2016 at 04:28:18AM -0700, Ole Jacobsen wrote:
> I will just add that "engagement" is often seen as a better strategy
> than "boycott" in many circles, but we don't need to have that debate
> here and now :-)

This also covers much of my opinion.  In the absence of outright impact to
safety, it's better to engage.  Such engagement might imply an inquiry by
the IETF (potentially via either IAOC, IAB or whatever portion of IETF
"management" is deemed appropriate) to the host government as to the
concerns of the IETF for the welfare of its membership.

Laws and social norms shift at speeds even slower than our RFC process.  But
similarly, legal consensus is shaped by participation.  "We're concerned,
could you please clarify" may help refine the opinion of the host government
while simultaneously clarifying membership welfare issues.

-- Jeff


From nobody Fri Apr  8 06:54:35 2016
Return-Path: <mellon@fugue.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 52B6F12D897 for <ietf@ietfa.amsl.com>; Fri,  8 Apr 2016 06:54:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.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 5e1A9_Hv_l1s for <ietf@ietfa.amsl.com>; Fri,  8 Apr 2016 06:54:30 -0700 (PDT)
Received: from mail-lb0-x22d.google.com (mail-lb0-x22d.google.com [IPv6:2a00:1450:4010:c04::22d]) (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 2CA9212D602 for <ietf@ietf.org>; Fri,  8 Apr 2016 06:54:30 -0700 (PDT)
Received: by mail-lb0-x22d.google.com with SMTP id vo2so69833484lbb.1 for <ietf@ietf.org>; Fri, 08 Apr 2016 06:54:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=+j3CympSHgg4/ZCd3LUt0YKTQ31+NzEbeUv1O4wf6rg=; b=vk6ar9LIWu70aErzU92VndVMjH5Kl34vo4LJkaYBGLAJfUVo1m3VzoIT2BdPgCWvYD QwDF4gliAAetrYlbX2LuanoSOEJ0bRoe0oNtkFNCj7Hdz0NWDMNn3J4om910AWVXFmK8 m00E4zTnXhL0jIYvtO9YLqN41YwmM72OEUI1Pr30AOV944F4UrJAy+0AhahmpN/2vr7i r+1PzDRehotGOV35eT36pCHaBrnQgFvguIQr+1VP9xTr2RFzMQIYh/cJSfI834LDPBz+ XS6kLA3FaUCbet7rnlGj7LBuK+Dn9bvNy1EOGlflijeomrCOQSw1nrg1IlNfnGywIU2x 3NsQ==
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=+j3CympSHgg4/ZCd3LUt0YKTQ31+NzEbeUv1O4wf6rg=; b=U0gUAycU8iDu82GZ17zBZ/UC5rpKAKTGohgdsJCdw/CIYjArRioqarZu53YNGm+gm4 kdwqAe8utTWu8ErTFNLSep10zGJhCW2DH/SJQQlyu2HQrNMIv7acICOVZkJs9frchWeL kcWOOx3a7byg9oqrykEfYg4gTAKxg28V3QU8UpQ+o9/HTCukGDYl0UGmuV0qsV9zwLvv 1+2IV/eae2MtoMan5vD2+BrPYWO5pgYn7E1yQxUOc5bFaTHtSfkCcNsem7MRHplC+xD4 hoZ+qhpvL/dsZbTj5fCgv79dtWlcZzc4c5uGcg/e3jifDCs8R+kJrgqIyS3Z/SL/oTIz nApQ==
X-Gm-Message-State: AD7BkJIY8qurNTOoWpvf1ZDzOyiZeIdS+cbSpyznBU6Z755blerjn2PaIc2rX3PSV74fknzMdEW7bjgOjtUC2g==
X-Received: by 10.112.169.105 with SMTP id ad9mr3683886lbc.135.1460123668387;  Fri, 08 Apr 2016 06:54:28 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.25.40.136 with HTTP; Fri, 8 Apr 2016 06:53:48 -0700 (PDT)
X-Originating-IP: [31.133.178.155]
In-Reply-To: <20160408133914.GB17588@pfrc.org>
References: <0D914666-C3D4-4CCE-AD5E-4E5B34EA1A73@piuha.net> <20160407182936.GA21340@pfrc.org> <CAB75xn780nNDjGa_Cc222J20-+1CCHt09Xp8KHzaK=n0xx51pg@mail.gmail.com> <5706B100.9040509@mnt.se> <CAB75xn6fmj84ROUtG5eUB3GerHx83hrEr3w5vSADY_g=BRg5FA@mail.gmail.com> <5706BA40.3060005@mnt.se> <alpine.DEB.2.02.1604072157240.31096@uplift.swm.pp.se> <A9B63A6D-3102-482F-8FFC-2E57A5FD8336@nic.cz> <CC16B445-2B74-4182-BC58-F9D4BFFA1CCF@chopps.org> <alpine.OSX.2.01.1604080420470.36488@rabdullah.local> <20160408133914.GB17588@pfrc.org>
From: Ted Lemon <mellon@fugue.com>
Date: Fri, 8 Apr 2016 10:53:48 -0300
Message-ID: <CAPt1N1=DVi5MbNVmceX1zA_tTda4jQ=S=zY83ON2U5WQ_AzB_g@mail.gmail.com>
Subject: Re: China
To: Jeffrey Haas <jhaas@pfrc.org>
Content-Type: multipart/alternative; boundary=001a11c38c089527af052ff988af
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/MB5_Y32UB28IyixqQek-G94K_UE>
Cc: "ietf@ietf.org 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: Fri, 08 Apr 2016 13:54:34 -0000

--001a11c38c089527af052ff988af
Content-Type: text/plain; charset=UTF-8

There is another side to this, although I don't disagree with either of you
on the China observation.

The other side is this: it's tempting to say that since in the U.S. up
until recently, gay rights weren't a thing, and yet we held meetings in the
U.S., the same should apply elsewhere.   However, consider this: until
fairly recently, in the United States, if your spouse happened to be the
same sex, and got ill, or if a child got ill, there was a very, very real
chance that you would not only be excluded from making decisions about
their health options, you might be prevented from even being in the same
room with them.

This was something we tolerated in meeting venues because we didn't really
have a choice until fairly recently, other than simply restricting our
meetings to Europe and perhaps some parts of Asia.

Now that this is no longer an issue at least legally in the U.S., it would
be a backslide to go to a place where it still is an issue, even though we
tolerated this risk in the past.   I am fortunate enough to be married to
someone for whom this risk does not exist for me at present (although it
would have in the past, since she is from a different religious heritage
than I).   It breaks my heart to hear stories of the horror that gay
couples have gone through because of discrimination of this sort and other
sorts.   I am not okay with being party to that happening in the future.

I agree that engagement is important, but let us bear in mind the risks we
are asking our friends and colleagues to bear when we have this discussion.

On Fri, Apr 8, 2016 at 10:39 AM, Jeffrey Haas <jhaas@pfrc.org> wrote:

> On Fri, Apr 08, 2016 at 04:28:18AM -0700, Ole Jacobsen wrote:
> > I will just add that "engagement" is often seen as a better strategy
> > than "boycott" in many circles, but we don't need to have that debate
> > here and now :-)
>
> This also covers much of my opinion.  In the absence of outright impact to
> safety, it's better to engage.  Such engagement might imply an inquiry by
> the IETF (potentially via either IAOC, IAB or whatever portion of IETF
> "management" is deemed appropriate) to the host government as to the
> concerns of the IETF for the welfare of its membership.
>
> Laws and social norms shift at speeds even slower than our RFC process.
> But
> similarly, legal consensus is shaped by participation.  "We're concerned,
> could you please clarify" may help refine the opinion of the host
> government
> while simultaneously clarifying membership welfare issues.
>
> -- Jeff
>
>

--001a11c38c089527af052ff988af
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">There is another side to this, although I don&#39;t disagr=
ee with either of you on the China observation.<div><br></div><div>The othe=
r side is this: it&#39;s tempting to say that since in the U.S. up until re=
cently, gay rights weren&#39;t a thing, and yet we held meetings in the U.S=
., the same should apply elsewhere. =C2=A0 However, consider this: until fa=
irly recently, in the United States, if your spouse happened to be the same=
 sex, and got ill, or if a child got ill, there was a very, very real chanc=
e that you would not only be excluded from making decisions about their hea=
lth options, you might be prevented from even being in the same room with t=
hem.</div><div><br></div><div>This was something we tolerated in meeting ve=
nues because we didn&#39;t really have a choice until fairly recently, othe=
r than simply restricting our meetings to Europe and perhaps some parts of =
Asia.</div><div><br></div><div>Now that this is no longer an issue at least=
 legally in the U.S., it would be a backslide to go to a place where it sti=
ll is an issue, even though we tolerated this risk in the past. =C2=A0 I am=
 fortunate enough to be married to someone for whom this risk does not exis=
t for me at present (although it would have in the past, since she is from =
a different religious heritage than I). =C2=A0 It breaks my heart to hear s=
tories of the horror that gay couples have gone through because of discrimi=
nation of this sort and other sorts. =C2=A0 I am not okay with being party =
to that happening in the future.</div><div><br></div><div>I agree that enga=
gement is important, but let us bear in mind the risks we are asking our fr=
iends and colleagues to bear when we have this discussion.</div></div><div =
class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Fri, Apr 8, 2016 at=
 10:39 AM, Jeffrey Haas <span dir=3D"ltr">&lt;<a href=3D"mailto:jhaas@pfrc.=
org" target=3D"_blank">jhaas@pfrc.org</a>&gt;</span> wrote:<br><blockquote =
class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid=
;padding-left:1ex"><span class=3D"">On Fri, Apr 08, 2016 at 04:28:18AM -070=
0, Ole Jacobsen wrote:<br>
&gt; I will just add that &quot;engagement&quot; is often seen as a better =
strategy<br>
&gt; than &quot;boycott&quot; in many circles, but we don&#39;t need to hav=
e that debate<br>
&gt; here and now :-)<br>
<br>
</span>This also covers much of my opinion.=C2=A0 In the absence of outrigh=
t impact to<br>
safety, it&#39;s better to engage.=C2=A0 Such engagement might imply an inq=
uiry by<br>
the IETF (potentially via either IAOC, IAB or whatever portion of IETF<br>
&quot;management&quot; is deemed appropriate) to the host government as to =
the<br>
concerns of the IETF for the welfare of its membership.<br>
<br>
Laws and social norms shift at speeds even slower than our RFC process.=C2=
=A0 But<br>
similarly, legal consensus is shaped by participation.=C2=A0 &quot;We&#39;r=
e concerned,<br>
could you please clarify&quot; may help refine the opinion of the host gove=
rnment<br>
while simultaneously clarifying membership welfare issues.<br>
<br>
-- Jeff<br>
<br>
</blockquote></div><br></div>

--001a11c38c089527af052ff988af--


From nobody Fri Apr  8 06:59:49 2016
Return-Path: <mcr+ietf@sandelman.ca>
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 2BF4212D8F5 for <ietf@ietfa.amsl.com>; Fri,  8 Apr 2016 06:59:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Level: 
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 GtScx-UbaFqD for <ietf@ietfa.amsl.com>; Fri,  8 Apr 2016 06:59:46 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A3FAB12D8F2 for <ietf@ietf.org>; Fri,  8 Apr 2016 06:59:46 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id D41422009E; Fri,  8 Apr 2016 10:03:24 -0400 (EDT)
Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id B45FE63755; Fri,  8 Apr 2016 09:59:45 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: "Murray S. Kucherawy" <superuser@gmail.com>
Subject: Re: Qualifying for NomCom
In-Reply-To: <CAL0qLwYvCpL9wwHL0E33HRbMvcckpad=gV-VYgAomJpCdiSrpg@mail.gmail.com>
References: <CAL0qLwY0FuDp5=RMFEhUMtkK=XNDxX2dogvVY7+OSy88jrrvOQ@mail.gmail.com> <CAPt1N1=SYpo-CiHoc07Ukb04Kb1LGV2=BPPyRLUsaqyLM9Hbwg@mail.gmail.com> <CAL0qLwbhYRqw7fXHzYY0=W-CpmeHeDdaZx3z2Qg0cA2aMrmVwg@mail.gmail.com> <CAPt1N1nqmC7NJyg2M6Na8vUj8T-qObO-1gHFEXZzrobb3oOQhA@mail.gmail.com> <CAL0qLwZHGa5OvSmZ=bTd6AWchsm4r=QaJn2nPqD+YjeWPmH9pA@mail.gmail.com> <24691.1460062367@obiwan.sandelman.ca> <5706CC94.3080804@gmail.com> <CAL0qLwYvCpL9wwHL0E33HRbMvcckpad=gV-VYgAomJpCdiSrpg@mail.gmail.com>
X-Mailer: MH-E 8.6; nmh 1.6+dev; GNU Emacs 24.4.2
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Fri, 08 Apr 2016 09:59:45 -0400
Message-ID: <22930.1460123985@obiwan.sandelman.ca>
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/TX3TQljHyeLWFSkMefXRN2gJ1Uc>
Cc: ietf <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: Fri, 08 Apr 2016 13:59:48 -0000

--=-=-=
Content-Type: text/plain


Murray S. Kucherawy <superuser@gmail.com> wrote:
    > How's this look for starters?

    > http://blackops.org/~msk/draft-kucherawy-nomcom-procexp.txt

okay, this is very very open.
As a 3933 experiment, I think we can do this.

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-




--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQEVAwUBVwe5T4CLcPvd0N1lAQLH/QgAnCfm2dkt1uf6RYqasB8h9zrmoMU99wYR
0jzcncrT2bpGcyemd8d+2TmNCELuLyKXxo0M0sosVO0fv2ttQVUmzXR4Uvwoq4My
TLLcc9GlvYf4+UXJdFp+pnS1dKXfHLf68eC8rPfwCeGJuPb88kc4hGGI3WdDzbfM
2nSANDp5l8TxJyPCXwtDdmWf/qx+1Nf7xZUabGroPtxBM/jL3O1WRg6D7zeDcMHQ
iWxniuVLNeu+9gBNAXUwIQLC1u3sOSXpQu1EYyNFY8+Z4XwipaqjPVGrXv700cQb
u5bRYjU04i5K+cfs2G0FEPcTyRSu+KSsrgtFByFajsFEyhcDU2hkmQ==
=YaD7
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Fri Apr  8 07:01:03 2016
Return-Path: <mcr+ietf@sandelman.ca>
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 B061312D8EE for <ietf@ietfa.amsl.com>; Fri,  8 Apr 2016 07:01:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Level: 
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 j2zGsirbPerr for <ietf@ietfa.amsl.com>; Fri,  8 Apr 2016 07:01:00 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7573612D8D3 for <ietf@ietf.org>; Fri,  8 Apr 2016 07:00:59 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id A6B582009E for <ietf@ietf.org>; Fri,  8 Apr 2016 10:04:37 -0400 (EDT)
Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 99D9763755 for <ietf@ietf.org>; Fri,  8 Apr 2016 10:00:58 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: ietf <ietf@ietf.org>
Subject: Re: Qualifying for NomCom
In-Reply-To: <6012C604-0922-4582-A505-F7934B5FD903@att.com>
References: <CAL0qLwY0FuDp5=RMFEhUMtkK=XNDxX2dogvVY7+OSy88jrrvOQ@mail.gmail.com> <CAPt1N1=SYpo-CiHoc07Ukb04Kb1LGV2=BPPyRLUsaqyLM9Hbwg@mail.gmail.com> <CAL0qLwbhYRqw7fXHzYY0=W-CpmeHeDdaZx3z2Qg0cA2aMrmVwg@mail.gmail.com> <CAPt1N1nqmC7NJyg2M6Na8vUj8T-qObO-1gHFEXZzrobb3oOQhA@mail.gmail.com> <CAL0qLwZHGa5OvSmZ=bTd6AWchsm4r=QaJn2nPqD+YjeWPmH9pA@mail.gmail.com> <24691.1460062367@obiwan.sandelman.ca> <5706CC94.3080804@gmail.com> <CAL0qLwYvCpL9wwHL0E33HRbMvcckpad=gV-VYgAomJpCdiSrpg@mail.gmail.com> <5E36120B-6D4E-4C0D-9905-2C698455D395@att.com> <CAL0qLwak6GRDYAcYqdOewoSmRj6DP5ptQKjqXkOedBaHcKC7WA@mail.gmail.com> <60B61524-EFF7-4489-A0C7-AA4A139FEF6C@att.com> <CAL0qLwYDW_zwfdr4-2=r0vt2Cb1wNFm+-aog0Wubu+8PbaYWEw@mail.gmail.com> <6012C604-0922-4582-A505-F7934B5FD903@att.com>
X-Mailer: MH-E 8.6; nmh 1.6+dev; GNU Emacs 24.4.2
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Fri, 08 Apr 2016 10:00:58 -0400
Message-ID: <23201.1460124058@obiwan.sandelman.ca>
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/d4U5ld_4P2MtaQ8AF0r6A7-aXME>
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: Fri, 08 Apr 2016 14:01:01 -0000

--=-=-=
Content-Type: text/plain


So, we'll know by August if the experiment resulted in more volunteers.

My only concern is that we decide it was ineffective in getting more diverse
volunteers,  and stop; but it might have needed more than 1 year to socialize
the ideas out there.

A result might also be: the new rules cause no harm and should be kept until
such time we have more data.

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-




--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQEVAwUBVwe5mICLcPvd0N1lAQL1zQf9FkmaJGThediujGNMVpoTy8MuS/XRMxGY
4o+gt3wsJblOkP6U44thsKepelCK+tA7tpaXlbJwmK73zudjWsZqLfZS1xCBNnu1
naZLr3tbkuvoHHB43l2x+1BlRctjdHqZq89BHjI5710e9k4/JVOaLvhSAj1U8sNS
ju3UpvtCUoy0gJUMm6N36pvmvnz3AG33CXgXwAs8Uo6PiO/CWBGWIYH0t1EISZIB
TedUXXzJ4AaUAKe6acxZbG9r4l4nnS+NdIQssPlxOu29WdRoM2MGvqEgpyKGtc70
AwCg6KprQzcL6WBQsqR0MRDURBCQamvT8pGncuRXRYbFOxQfQ5nmNw==
=ESE0
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Fri Apr  8 07:07:53 2016
Return-Path: <mellon@fugue.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 DC70512D903 for <ietf@ietfa.amsl.com>; Fri,  8 Apr 2016 07:07:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.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 bMHTOZscdNEW for <ietf@ietfa.amsl.com>; Fri,  8 Apr 2016 07:07:37 -0700 (PDT)
Received: from mail-lb0-x232.google.com (mail-lb0-x232.google.com [IPv6:2a00:1450:4010:c04::232]) (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 0829312D829 for <ietf@ietf.org>; Fri,  8 Apr 2016 07:07:32 -0700 (PDT)
Received: by mail-lb0-x232.google.com with SMTP id u8so70064285lbk.0 for <ietf@ietf.org>; Fri, 08 Apr 2016 07:07:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=D1S+ZUvpF1y4NgfexyvNO8JsvspUKEin7pqgsu8OWq0=; b=Q7Ccz+buuwobH772WsDz51WalMovRXbH0KbDd9r96JBbWElDalRugJcVVPv8BzL4Bd DJBdu307LLK5YMrEHKsrtHKksBOm405+bp4pFt2jVx5bw+ce6U/MWK8+DEWZUAu71jJ6 zQClUIgBRj9Q7uwbXXQuS2i+dHgifs+VIDSOalxet/jYFqt0Voaxx3XjkAL2LpigGf5i Sf/fH08kGx50nMcRXicz20d3O0O2VesqVmSBmUzHBM3o3nxX7ZCLhWHQEG55cnq1zgzm sSW6XLQHqlaRRgP6Wq31zz5XfBYpS37LdYa/lWCgjAWHkswEm3MvZ1V9G3b2n5PilRr9 JXDw==
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=D1S+ZUvpF1y4NgfexyvNO8JsvspUKEin7pqgsu8OWq0=; b=YKv5Yetr2MXKOdOdtkzwKeyK8rFKzkyROYKdhHtFvnGDAMHy+ZORemmINRfPLilpOJ REmDRiMX1I9BJXTiB8WedboyK1/P/MfZup+EkpMxyiDhmqfQrJrrRUcongTw65V0pP1W YT5+ElFyA9wLp8dwFwuaz0Gqez1cPArditl+/PcKBsdcUDKIiyu8kMB56M+plAWeUTuv wgwj7FM2U42S/L9YuUlJboNN4fCeYMrsDl0kCIw0q95iOnbEr2fI0sgQUZyQNftok3U3 MbMZuqObx7A+ZjAQOdC7s2GHm8MMqisjHoK2fE1wokuOjH+W8W3tkR3FckUfB7P6gmky sTxQ==
X-Gm-Message-State: AD7BkJKdmNq8ML9fLXoRdGne/NYdLsjBJ5rw+jb3J3Nbn15gp4OrrL3UXI5/xm0L7MSaJUGaIpoC3lKPIz0Edg==
X-Received: by 10.112.161.41 with SMTP id xp9mr3712942lbb.133.1460124451160; Fri, 08 Apr 2016 07:07:31 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.25.40.136 with HTTP; Fri, 8 Apr 2016 07:06:51 -0700 (PDT)
X-Originating-IP: [31.133.178.155]
In-Reply-To: <23201.1460124058@obiwan.sandelman.ca>
References: <CAL0qLwY0FuDp5=RMFEhUMtkK=XNDxX2dogvVY7+OSy88jrrvOQ@mail.gmail.com> <CAPt1N1=SYpo-CiHoc07Ukb04Kb1LGV2=BPPyRLUsaqyLM9Hbwg@mail.gmail.com> <CAL0qLwbhYRqw7fXHzYY0=W-CpmeHeDdaZx3z2Qg0cA2aMrmVwg@mail.gmail.com> <CAPt1N1nqmC7NJyg2M6Na8vUj8T-qObO-1gHFEXZzrobb3oOQhA@mail.gmail.com> <CAL0qLwZHGa5OvSmZ=bTd6AWchsm4r=QaJn2nPqD+YjeWPmH9pA@mail.gmail.com> <24691.1460062367@obiwan.sandelman.ca> <5706CC94.3080804@gmail.com> <CAL0qLwYvCpL9wwHL0E33HRbMvcckpad=gV-VYgAomJpCdiSrpg@mail.gmail.com> <5E36120B-6D4E-4C0D-9905-2C698455D395@att.com> <CAL0qLwak6GRDYAcYqdOewoSmRj6DP5ptQKjqXkOedBaHcKC7WA@mail.gmail.com> <60B61524-EFF7-4489-A0C7-AA4A139FEF6C@att.com> <CAL0qLwYDW_zwfdr4-2=r0vt2Cb1wNFm+-aog0Wubu+8PbaYWEw@mail.gmail.com> <6012C604-0922-4582-A505-F7934B5FD903@att.com> <23201.1460124058@obiwan.sandelman.ca>
From: Ted Lemon <mellon@fugue.com>
Date: Fri, 8 Apr 2016 11:06:51 -0300
Message-ID: <CAPt1N1=VL4AUUJC2fdm-YV33kpHhzd54t3Dx0YBh7q0-=RV1Vw@mail.gmail.com>
Subject: Re: Qualifying for NomCom
To: Michael Richardson <mcr+ietf@sandelman.ca>
Content-Type: multipart/alternative; boundary=001a11c26b2a3d5a8f052ff9b7dd
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/fzW34d-vueIf_7MEZLMXByLKs3I>
Cc: ietf <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: Fri, 08 Apr 2016 14:07:39 -0000

--001a11c26b2a3d5a8f052ff9b7dd
Content-Type: text/plain; charset=UTF-8

There are some issues here.   First, who can challenge a nomcom volunteer's
elegibility?   Second, what process is followed if their eligibility is
challenged?   This actually seems a lot harder than some of the other
proposals that were put forth, which simply extended eligibility of the
same type to more IETF participants, rather than creating two classes of
IETF participants.

On Fri, Apr 8, 2016 at 11:00 AM, Michael Richardson <mcr+ietf@sandelman.ca>
wrote:

>
> So, we'll know by August if the experiment resulted in more volunteers.
>
> My only concern is that we decide it was ineffective in getting more
> diverse
> volunteers,  and stop; but it might have needed more than 1 year to
> socialize
> the ideas out there.
>
> A result might also be: the new rules cause no harm and should be kept
> until
> such time we have more data.
>
> --
> Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
>  -= IPv6 IoT consulting =-
>
>
>
>

--001a11c26b2a3d5a8f052ff9b7dd
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">There are some issues here. =C2=A0 First, who can challeng=
e a nomcom volunteer&#39;s elegibility? =C2=A0 Second, what process is foll=
owed if their eligibility is challenged? =C2=A0 This actually seems a lot h=
arder than some of the other proposals that were put forth, which simply ex=
tended eligibility of the same type to more IETF participants, rather than =
creating two classes of IETF participants.</div><div class=3D"gmail_extra">=
<br><div class=3D"gmail_quote">On Fri, Apr 8, 2016 at 11:00 AM, Michael Ric=
hardson <span dir=3D"ltr">&lt;<a href=3D"mailto:mcr+ietf@sandelman.ca" targ=
et=3D"_blank">mcr+ietf@sandelman.ca</a>&gt;</span> wrote:<br><blockquote cl=
ass=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;p=
adding-left:1ex"><br>
So, we&#39;ll know by August if the experiment resulted in more volunteers.=
<br>
<br>
My only concern is that we decide it was ineffective in getting more divers=
e<br>
volunteers,=C2=A0 and stop; but it might have needed more than 1 year to so=
cialize<br>
the ideas out there.<br>
<br>
A result might also be: the new rules cause no harm and should be kept unti=
l<br>
such time we have more data.<br>
<div class=3D"HOEnZb"><div class=3D"h5"><br>
--<br>
Michael Richardson &lt;<a href=3D"mailto:mcr%2BIETF@sandelman.ca">mcr+IETF@=
sandelman.ca</a>&gt;, Sandelman Software Works<br>
=C2=A0-=3D IPv6 IoT consulting =3D-<br>
<br>
<br>
<br>
</div></div></blockquote></div><br></div>

--001a11c26b2a3d5a8f052ff9b7dd--


From nobody Fri Apr  8 07:08:08 2016
Return-Path: <stefan.winter@restena.lu>
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 A13D312D904 for <ietf@ietfa.amsl.com>; Fri,  8 Apr 2016 07:08:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.909
X-Spam-Level: 
X-Spam-Status: No, score=-1.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, T_RP_MATCHES_RCVD=-0.01] 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 BKW3HmKS1azB for <ietf@ietfa.amsl.com>; Fri,  8 Apr 2016 07:08:04 -0700 (PDT)
Received: from smtp.restena.lu (legolas.restena.lu [158.64.1.34]) (using TLSv1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2F22912D8F8 for <ietf@ietf.org>; Fri,  8 Apr 2016 07:08:04 -0700 (PDT)
Received: from viper.local (unknown [IPv6:2001:a18:1:40::2]) by smtp.restena.lu (Postfix) with ESMTPSA id 1E283BB749 for <ietf@ietf.org>; Fri,  8 Apr 2016 16:08:01 +0200 (CEST)
Subject: Re: Concerns about Singapore
To: ietf@ietf.org
References: <0D914666-C3D4-4CCE-AD5E-4E5B34EA1A73@piuha.net> <20160407182936.GA21340@pfrc.org> <CAB75xn780nNDjGa_Cc222J20-+1CCHt09Xp8KHzaK=n0xx51pg@mail.gmail.com> <5706B100.9040509@mnt.se> <CAB75xn6fmj84ROUtG5eUB3GerHx83hrEr3w5vSADY_g=BRg5FA@mail.gmail.com> <5706BA40.3060005@mnt.se> <alpine.DEB.2.02.1604072157240.31096@uplift.swm.pp.se> <5706CEEA.70402@alcatel-lucent.com>
From: Stefan Winter <stefan.winter@restena.lu>
Openpgp: id=AD3091F3AB24E05F4F722C03C0DE6A358A39DC66
Message-ID: <5707BB3E.8040406@restena.lu>
Date: Fri, 8 Apr 2016 11:07:58 -0300
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:38.0) Gecko/20100101 Thunderbird/38.7.2
MIME-Version: 1.0
In-Reply-To: <5706CEEA.70402@alcatel-lucent.com>
Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="CWpNFIeH68S0HaCCjoIVbEGmbLTUwG2It"
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/ST9BeZXDojTJgEDdFsw7x11VOog>
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: Fri, 08 Apr 2016 14:08:05 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--CWpNFIeH68S0HaCCjoIVbEGmbLTUwG2It
Content-Type: multipart/mixed; boundary="o5KOesoE5bD9Lfd8qcLvfc6eRmehbnW77"
From: Stefan Winter <stefan.winter@restena.lu>
To: ietf@ietf.org
Message-ID: <5707BB3E.8040406@restena.lu>
Subject: Re: Concerns about Singapore
References: <0D914666-C3D4-4CCE-AD5E-4E5B34EA1A73@piuha.net>
 <20160407182936.GA21340@pfrc.org>
 <CAB75xn780nNDjGa_Cc222J20-+1CCHt09Xp8KHzaK=n0xx51pg@mail.gmail.com>
 <5706B100.9040509@mnt.se>
 <CAB75xn6fmj84ROUtG5eUB3GerHx83hrEr3w5vSADY_g=BRg5FA@mail.gmail.com>
 <5706BA40.3060005@mnt.se>
 <alpine.DEB.2.02.1604072157240.31096@uplift.swm.pp.se>
 <5706CEEA.70402@alcatel-lucent.com>
In-Reply-To: <5706CEEA.70402@alcatel-lucent.com>

--o5KOesoE5bD9Lfd8qcLvfc6eRmehbnW77
Content-Type: multipart/mixed;
 boundary="------------050002050402080106060304"

This is a multi-part message in MIME format.
--------------050002050402080106060304
Content-Type: multipart/alternative;
 boundary="------------040704070600050902030705"


--------------040704070600050902030705
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

Hi,

> There are no perfect places to go. Except Minneapolis. ;)

Too many LGBT unfriendlies there as well, it seems. For some reason, I
get what I consider spam, but others might not about "Minnesota for
Marriage". Luckily, their website is currently down for maintenance. And
I don't think anyone wants or the content warrants a forward of their
pamphlets.

Stefan

--------------040704070600050902030705
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable

<html>
  <head>
    <meta content=3D"text/html; charset=3Dutf-8" http-equiv=3D"Content-Ty=
pe">
  </head>
  <body bgcolor=3D"#FFFFFF" text=3D"#000000">
    <div class=3D"moz-cite-prefix">Hi,<br>
      <br>
    </div>
    <blockquote cite=3D"mid:5706CEEA.70402@alcatel-lucent.com" type=3D"ci=
te">
      <meta content=3D"text/html; charset=3Dutf-8" http-equiv=3D"Content-=
Type">
      There are no perfect places to go. Except Minneapolis. ;)<br>
    </blockquote>
    <br>
    Too many LGBT unfriendlies there as well, it seems. For some reason,
    I get what I consider spam, but others might not about "Minnesota
    for Marriage". Luckily, their website is currently down for
    maintenance. And I don't think anyone wants or the content warrants
    a forward of their pamphlets.<br>
    <br>
    Stefan<br>
  </body>
</html>

--------------040704070600050902030705--

--------------050002050402080106060304
Content-Type: application/pgp-keys;
 name="0x8A39DC66.asc"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
 filename="0x8A39DC66.asc"

-----BEGIN PGP PUBLIC KEY BLOCK-----
Version: GnuPG/MacGPG2 v2

mQINBFIplEwBEADTSz+DS8nio+RSvfSLLfaOnCGi1nqpn8Pb1laVUyEvnAAzZ5je
miS88GxfiDH6hUGlWzcaW0hCfUHGiohr485adbjxRksPngWgAt/1bRxpifsW3zOb
Fjgog01WWQV5Sihlwc4zr8zvYbFA5BJZ6YdkR9C5J015riv5OS30WTjA65SSXgYr
b7zJWPwmegTFwE093uBFvC39waz3xYpVu5j87nO6w2MVQt/8sY2/2BFPEq+xfOaj
l18UEwc7w8SCgnZdlVNcmEK4UBvJuwS/1lsR2JeQa8Gu1EDxC7PRgMgNXsDSWnnB
e9aVmfG54+6ILe1QH2dwk9sPBQT5w2+vjijrb3Dv9ur+1kN+TNU2XE436jVpnnY/
3OsLdix30STQn4Q/XOm7YoVMeDwwviefilRxzK0dXA+wKj92T68Od82CFxuZqPAg
BCVmWfQM91iK9piqFK+QP+R3vF6+NGDBdwbe68iVKs0v5L8XmbxBQndjpmo+lo2a
smBR2TAIfZHaKdgtBw13u3GPVVKlg/Mpko8ki9JOSem2aFyi3kQEVKptWgXT3POl
97DWJzsR5VyKz6GOx9kJAEISRyLZwm0wqh8+9LCza5oeIKW381lzq1b9x30vOh8C
BSQQJ+cG9ko0yPHAj7Suw2TmPXx1qMctmE6Ahq82ZW30SljdZby8WQuR2wARAQAB
tDxTdGVmYW4gV2ludGVyIChSRVNURU5BIGtleSAyMDEzKykgPHN0ZWZhbi53aW50
ZXJAcmVzdGVuYS5sdT6JAjkEEwECACMFAlIplEwCGwMHCwkIBwMCAQYVCAIJCgsE
FgIDAQIeAQIXgAAKCRDA3mo1ijncZj7/D/99hVS+mJr8dSPCaDaUFFxBiT2eI1Lo
R8VKEerTCRw5BsdL6pN2eRJZ9NmsqWo1ynWVHEzO91bNZ+oZGgyoNohcBAI7p+r0
qUTzkyqwdZO4kMm0pqKoM9xkP3tf2mjGujKjOz4Y7S7wnz2ZFokeUsecoRVJF/++
/qHnmeWLn44J1HUKLHYCjMu+QXGOgGXgz024jQ5eUrnPwzNp0Z90AFVHlWC+bymt
y/ToIUUCQqS5Ff0jzdWLd8U695OG9iGvjBQT1LdEjsfbAwuKV5UcnpxNqUpUwKa5
9hdX5/2cMZP07FI1UXwnBlxa8rJfdb13FLjSKX4vUUHedYUZMjMPgcwl1a+zGE22
lHiSQWgP8QLA/W3BLsi22ERCEPZBfexOeOtaWIItDIz18fIaQoMDoRPshzar0JI2
CzLYsyeKySAtYJEHFVoLmMvhkwzBmgqA/BEswUA67CfCr1jFHRXdpmWM7YkyAmMa
9q6LwquWKS5+MXlUXe/3oZUcgpw/T9Uuy3Jo3RdS7B3jFcWaVr6KsO/A9u1gr/aY
n5M+iJTQSj4vzqtkQaJTpSspRZoKa66HZt3IwSYiDiYZqtM83ynuj9kjnZzGfnuT
aNIi996q6Mptr33mOzIE1wmMqnJYwTr3EcNtf483q/qrJwh5ES8Q9xY7aat/ZcSl
8fKubW4TlfVr8YhGBBARAgAGBQJSKZUGAAoJEPo5vdH/HhVmYTgAn24eoqO/O98o
vNpt08Uab/+/tmYKAJ9kjXm9Njz5h33efzeelZUa484rr7kCDQRSKZRMARAAvBPp
n7FQq7LQ5glohtbL6XIEo1U4X67S0TzUYieENSWSVYuWYIhCBldmWdmH8Bpj/qHe
qdon7v+SLtR4WngzMR9toupKcFfHnbP9kpazTSB2ySHxXWGX1gJOpPXdCcg9iveK
BHEsDn00ThTcPsvtXpnnzET16pXIvOXO0bxTmVZ4INIF1SWgvYma/g8kBbgXLpkj
8tOywBqFiiYPEZlDeCxDHiMgUDh6olda9K/0TZFTdMPUgjKuubfAeaDNCOrVt4Rj
mFOaRLikcZocmgJhm3z/j25x7/mnNu+0di1H/S67YGQJ+pqCFInzIXDx7aRW2+JC
iqsY2X3xOPWZZzjyis5SNnfOcPH3gt2hYz1fy+thsBGf4NgCN01JRqIJ2/MOQCgU
dwh+9l8xqaJvCkUHM4hVh4W62MAe1u7UEqQbvvNEqxM5034vcvlE+/LRkrDCspw+
2YJ9QyroLerVRwW5DVleP8Ifi8VB3yD80nqXYs9aqRy0BkDNIQ43ERhESMt8dJqr
NkxgC6pemZrhNwyDh+hy2kPNGQh/iBpdKuH1o3E24TIZoV2v3YHvzob7aAYHddE/
PofAXhJW7I9mAs+HdWDmnI8ckuPDFpFH+Y/BFGvEXgcnJAJ1wEvf+4LuiIi0MHjR
4EWFn9vvoFDAIqD10h3FSd3D59HGtdSsNn4XaCsAEQEAAYkCHwQYAQIACQUCUimU
TAIbDAAKCRDA3mo1ijncZhBtEACL036ddjc5pFoYIdoUY1vT8SMXJNquewCnL1qu
DADzqDZFU5GNlQEy10krSfBwlTb9ahTtE0JFrOdZwUZtoa1Pgfr8nU6KOgrXPHbN
jS/9dyc5CwGVVIpOavIm2CsMVDJ9LCF/NT+u/t1k6eGfHhPVl3dUQyDa/lzc1chK
UIVQYQkFmr0A/iXP+29lFCaI+IeyU0bSdZhezDwUROn5vEx+fiPZyHDShCb+BxJv
/o2LQp9JHenCiSbO+ioRZdxgbWfoKBuXOfmSStqMWXas/gZ5vS3xq72LNtKPRxgp
jX3P8Zml1XDqpcBau7eK75VKE0Yd06YxnUIsbcEzInUc3uzW/u0DFpXYkMJb0XIv
JyUt5yYPKfV13N8kSkPi5pLxm8yuftXMzfgeFMR7nafY3glTVj/TxElzg6xeZNqf
C2ZjIbBtZg9ylHU8u8wwB+dX282crs0R3N9A064C71/cXlBqcjzjlKH2NUIWGxr+
od3TXFIFjszSU3NgMPKrWNhFLLwS81MpbkOe73s6aDhS8RDyNucoxtKXriLR+4Xi
u4+pyj5ukYP1JqpB3ZobY/XZgCnJMye+7xeTpIDJ1LPORxM3NNAElyb26lxAK2P+
km+EpI0Zzz6rNSCfg5jYQ474+e/GBgaSG4MlaPoZ+XAfN46u1Xjjv1/AkkA4IA6m
5zP5og=3D=3D
=3D3NUt
-----END PGP PUBLIC KEY BLOCK-----

--------------050002050402080106060304--

--o5KOesoE5bD9Lfd8qcLvfc6eRmehbnW77--

--CWpNFIeH68S0HaCCjoIVbEGmbLTUwG2It
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2

iQIcBAEBCgAGBQJXB7s/AAoJEMDeajWKOdxmdkEP/1Fjnof0z2oJrn/O/GH2GTiO
aRvk8eISqLCf7oq4Kb+74LsKZjtFHbbV9dgQTcZEJ1M7LCxkq/zx+nj3KZ0+zzox
V71Z7c7iZv5jgJfkYgVMun8wOGVq6GbH+9RTarpbF4Y0nNS+hsFMRXRF9iXfJPRn
5otvVhAKMjK8BgOBEeQRSxO5ppDWKAmm3J8umvpZetSktHwklU2lagubnUEZBhet
4cXKA7fbHgv5kPXeql4ZmM0GlFefqKkQIy0eDlgV6zijn13UrmCOo0n4HBEiR0UZ
U7oQtXbVFyWE8ZchYaH6UBsuP6OFlvxNEO/HRx0/TTfvfd0vhcsXHPjNaLR8dv4g
hrHjXbohSjTO3RGuU6iVP878DbvSvcarkvXg8wNmLn2URrK0anyYJViJU+35KTLh
429i9/T9yn0581knLcVr6Re8T3R4vyDswTPN3ZiBnoTXctJ68JPbAFifZM4KEXhz
HmhsJSPiJYt97P9qVwiB4gMbotJknbDvz7JclCszhbhAbwVY7MSgevfaNAUhtj35
34WDVaHxO8jn3Z1HD/YocU8vmTzstj/q76DENsltFbCIqy8c2ki2NyTGXHTXafkc
APDXZNjNK4ISbNKeh6rQUyS/Apji4re7zSStP1+gaOA7y1bedQ+QOOm/OMJhamdy
/AJGpDBRqrl0i1YG6aLy
=usZ4
-----END PGP SIGNATURE-----

--CWpNFIeH68S0HaCCjoIVbEGmbLTUwG2It--


From nobody Fri Apr  8 07:30:41 2016
Return-Path: <aallen@blackberry.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 EDD8312D1D0 for <ietf@ietfa.amsl.com>; Fri,  8 Apr 2016 07:30:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.631
X-Spam-Level: 
X-Spam-Status: No, score=-2.631 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 9BB0MBcxwJ93 for <ietf@ietfa.amsl.com>; Fri,  8 Apr 2016 07:30:35 -0700 (PDT)
Received: from smtp-p01.blackberry.com (smtp-p01.blackberry.com [208.65.78.88]) by ietfa.amsl.com (Postfix) with ESMTP id BC10612D1AC for <ietf@ietf.org>; Fri,  8 Apr 2016 07:30:35 -0700 (PDT)
Received: from xct108cnc.rim.net ([10.65.161.208]) by mhs211cnc.rim.net with ESMTP/TLS/AES256-SHA; 08 Apr 2016 12:04:25 -0400
Received: from XMB122CNC.rim.net ([fe80::28c6:fa1c:91c6:2e23]) by XCT108CNC.rim.net ([fe80::8dc1:9551:6ed8:c618%17]) with mapi id 14.03.0210.002; Fri, 8 Apr 2016 10:30:29 -0400
From: Andrew Allen <aallen@blackberry.com>
To: =?iso-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@frobbit.se>, =?iso-8859-1?Q?Anne-Marie_Eklund-L=F6winder?= <anne-marie.eklund-lowinder@iis.se>
Subject: Re: Concerns about Singapore
Thread-Topic: Concerns about Singapore
Thread-Index: AQHRkOMNjufwcA4TvkK+5mik25hZRp9/GCcAgAAATwCAAAuKAIAACE6AgAACuQCAAAKSAIAAFhAAgADq5YCAAAJcAIAAEZSA///eIWo=
Date: Fri, 8 Apr 2016 14:30:28 +0000
Message-ID: <20160408143026.6283348.2479.10374@blackberry.com>
References: <0D914666-C3D4-4CCE-AD5E-4E5B34EA1A73@piuha.net> <20160407182936.GA21340@pfrc.org> <CAB75xn780nNDjGa_Cc222J20-+1CCHt09Xp8KHzaK=n0xx51pg@mail.gmail.com> <5706B100.9040509@mnt.se> <CAB75xn6fmj84ROUtG5eUB3GerHx83hrEr3w5vSADY_g=BRg5FA@mail.gmail.com> <5706BA40.3060005@mnt.se> <alpine.DEB.2.02.1604072157240.31096@uplift.swm.pp.se> <5706CEEA.70402@alcatel-lucent.com> <alpine.DEB.2.02.1604081319150.16013@uplift.swm.pp.se> <55791011d19e40a792999c45b571ecc2@exchange02.office.nic.se>, <6167B6AD-8A00-4C16-AF93-69A195BC2F86@frobbit.se>
In-Reply-To: <6167B6AD-8A00-4C16-AF93-69A195BC2F86@frobbit.se>
Accept-Language: en-CA, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/Sed0OHfKGmLSFlPzW_glcIcmu-Y>
Cc: "ietf@ietf.org 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: Fri, 08 Apr 2016 14:30:40 -0000

Only goes to show that all laws should have a time to live timer value!

Sent from my BlackBerry 10 smartphone.
  Original Message
From: Patrik F=E4ltstr=F6m
Sent: Friday, April 8, 2016 09:32
To: Anne-Marie Eklund-L=F6winder
Cc: ietf@ietf.org Discussion
Subject: Re: Concerns about Singapore


On 8 Apr 2016, at 13:28, Anne-Marie Eklund-L=F6winder wrote:

> The law is from the 1920ies or so. No one bothered to change it.

This legislation is now to be removed.

The parliament of Sweden is discussing the issue on April 14 2016.

   paf


From nobody Fri Apr  8 07:37:00 2016
Return-Path: <ron.even.tlv@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 DDA6B12D518; Fri,  8 Apr 2016 07:36:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 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, RCVD_IN_DNSWL_LOW=-0.7, 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 IHJDWnbZDWsU; Fri,  8 Apr 2016 07:36:57 -0700 (PDT)
Received: from mail-qg0-x22c.google.com (mail-qg0-x22c.google.com [IPv6:2607:f8b0:400d:c04::22c]) (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 ACD2A12D18A; Fri,  8 Apr 2016 07:36:57 -0700 (PDT)
Received: by mail-qg0-x22c.google.com with SMTP id j35so91780644qge.0; Fri, 08 Apr 2016 07:36:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=from:to:cc:references:in-reply-to:subject:date:message-id :mime-version:content-transfer-encoding:thread-index :content-language; bh=3N2eKeN3wxbTTL9cHkZLRIT8cgK6eUGYUiirttNC9Cs=; b=bxcfeOMBZ8PHNSaY1WTAaKEiWFuqPOHFKe1Rz4bMftd9GNXZ4ZQiQgARnWBJzCIr/W X15jRSHSMHX5lPZK9bPQI/nfTi9cBow2CefW6vFDbUQHQkJ4ENqJXBdToQIiJ1+leeZH qbW6MzMKFal+8/2VXZiDK04HFPQQaBHznAGZR2uPIhVlhfJnCxXffdpw65BdOWtui2Xf kyhD6CHUUVS8yRRk3w+KlEctS677YhHUhKjJzdT/srLkHx4vSPfdMf/UTF1qApaJppZe WQIs7yvDzxdTACJpy/v7dMKRe2ul4OBj8xqzaeJ0ioSi6wheitcY2lULt0TSk+uJTB3U j6rQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:to:cc:references:in-reply-to:subject:date :message-id:mime-version:content-transfer-encoding:thread-index :content-language; bh=3N2eKeN3wxbTTL9cHkZLRIT8cgK6eUGYUiirttNC9Cs=; b=TO1BG0Tf+caAhjPSx4v8UvcLikaHEFH3Ag6VvF3Y2L0gamgtlYaI2FHhzJxSNGCnUl dzJxotnafT6M56bu6BaCI2AQ0h6gRJDzAlWSm0CpIo7G+I0oZcgPiIo4VfZvBC4mXGnA i6PKXGL7hsdllCb/An1/cB3+mBBDtAyOANDyA90SDTf1EQtFfDyuJnfJl1pvp9/aVu1o 63NBbxkW+kHnn/v6+j4aXKi6H+cFEP02kPcdDeFyc7LoaAY89A6AhJ/PdMyvTYp8oXlq lyjQmKwj7bXdbwnyTZS+dDH8p01T+pbV1E3u6Fx2U181vTLbYm+Tz6zOGkscG4wR+gE1 ZlKw==
X-Gm-Message-State: AD7BkJIynFnkMTQLPq9pUdTl3PTEQcRyxOhNYCHit4e4vfu75Iz7rdBZoyq/DgYt2CtO/Q==
X-Received: by 10.140.153.135 with SMTP id 129mr12342244qhz.38.1460126216845;  Fri, 08 Apr 2016 07:36:56 -0700 (PDT)
Received: from RoniPC ([2001:67c:370:176:1193:10da:961:ce1]) by smtp.gmail.com with ESMTPSA id b67sm5587871qhd.11.2016.04.08.07.36.54 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 08 Apr 2016 07:36:55 -0700 (PDT)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: "'Sean Turner'" <sean@sn3rd.com>
References: <017a01d190ca$ace223b0$06a66b10$@gmail.com> <A8A038B3-E10F-4A94-99D3-2C4D23A6E065@sn3rd.com>
In-Reply-To: <A8A038B3-E10F-4A94-99D3-2C4D23A6E065@sn3rd.com>
Subject: RE: Gen-ART LC review of draft-ietf-tls-chacha20-poly1305-04 - resend
Date: Fri, 8 Apr 2016 17:36:51 +0300
Message-ID: <00d901d191a4$185fa340$491ee9c0$@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQIM3GM2urfPwNWEbUqsemq3RkNvLQCQN/CbnwUH76A=
Content-Language: he
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/7cv9u5iYrHrdSBRfjZG_BlscSwk>
Cc: gen-art@ietf.org, draft-ietf-tls-chacha20-poly1305.all@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: Fri, 08 Apr 2016 14:37:00 -0000

Hi Sean,
Inline
Roni

> -----Original Message-----
> From: Sean Turner [mailto:sean@sn3rd.com]
> Sent: Friday, April 08, 2016 3:27 PM
> To: Roni Even
> Cc: ietf@ietf.org list; gen-art@ietf.org; draft-ietf-tls-chacha20-
> poly1305.all@ietf.org
> Subject: Re: Gen-ART LC review of draft-ietf-tls-chacha20-poly1305-04 =
-
> resend
>=20
>=20
> > On Apr 07, 2016, at 09:40, Roni Even <ron.even.tlv@gmail.com> wrote:
> >
> > I am the assigned Gen-ART reviewer for this draft. For background on =
Gen-
> ART, please see the FAQ at
> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
> >
> > Please resolve these comments along with any other Last Call =
comments
> you may receive.
> >
> > Document:  draft-ietf-tls-chacha20-poly1305-04
> >
> > Reviewer: Roni Even
> >
> > Review Date:2016=E2=80=933-28
> >
> > IETF LC End Date: 2016=E2=80=934-9
> >
> > IESG Telechat date:
> >
> >
> > Summary: This draft is almost ready for publication as a standard =
track
> RFC.
> >
> >
> >
> > Major issues:
> > I am wondering why this is a standard track document and not
> > informational since the registration requirements are specification
> > required.  (RFC5246)
>=20
> I=E2=80=99m not sure I agree that Specification Required implies =
informational track.
> Specification Required permits registrations from
> informational/experimental drafts, but it certainly doesn=E2=80=99t =
require
> informational/experimental.
>=20
> Also note, the registry rules are:
>=20
> 0-191	Standards Action			Refers to value of first byte
> 192-254	Specification Required		Refers to value of first byte
> 255		Reserved for Private Use  	Refers to value of first byte
[Roni Even] So  I would like to assume that there was a reason to have =
two different policies so why not follow it.
>=20
> > I am also wondering why this document updates RFC5246 and RFC6347.
> > Reading the document it looked to me that the registration document =
is
> used also to endorse this cypher suite by the IETF and if this is the =
case my
> view is that there should be two documents, one Informational for
> registration and the will be standard track and update RFC5246 and =
RFC6347
> For Example the following text from section 1 =E2=80=9CTherefore, a =
new stream
> cipher to replace RC4 and address all the  previous issues is needed. =
=E2=80=9C
> provides what may look as a normative recommendation.
>=20
> As far as the updates header:
>=20
> The RC4 stream cipher which was in TLS1.0-1.2 is now prohibited =
[RFC7465]
> (note not deprecated it=E2=80=99s prohibited) and =
ChaCha20-Poly1305-based ciphers
> are the replacement.  So, we do in fact want folks who were using RC4 =
to
> switch to ChaCha20-Poly1305, hence the updates header.
>=20
> As far as splitting the registrations/updates:
>=20
> What you=E2=80=99re suggesting is certainly one way to do it, but the =
way we=E2=80=99ve been
> doing it for years in the security area (e.g., TLS, IPSec, S/MIME, =
PKIX) is as
> follows (there have, of course, been exceptions):
>=20
> - (if needed) Informational RFC for algorithm
>=20
> - Standards track RFC for how to use algorithm with security protocol. =
This is
> how AES, Camellia, etc. were documented for TLS.

 [Roni Even] So this is the standard track RFC, I still do not get it
>From  RFC4346 a.5 "Cipher suite values with first byte decimal 192 =
(0xC0) through
         decimal 254 (0xFE) inclusive are reserved for assignment for
         non-Standards Track methods."

So this is the reason to have the registration as non standard document. =
  I looked at Camellia and it follows your explanation except for =
updating the TLS specification yet it uses the first byte from the range =
0-191.  So my question will be why did you use the first byte from 192 - =
range?




>=20
> Also in play here is the need to avoid a bunch of DOWNREFs because two =
of
> the ChaCha20-Poly1305 suites are SHOULDs in the draft TLS1.3.  =
DOWNREFs
> aren=E2=80=99t anything to be scared of, but where we can avoid them I =
think we
> should.
>=20
> I guess I=E2=80=99d rather not devise new process and just keep on =
doing what we=E2=80=99ve
> been doing.
>=20
> spt
>=20
> PS we are currently in the process of discussing a change to make the =
entire
> range (minus the reserved) specification required, but that =
won=E2=80=99t complete
> for a while and the implementers want this now (technically =
yesterday).


From nobody Fri Apr  8 07:39:01 2016
Return-Path: <mcr+ietf@sandelman.ca>
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 AEBE212D538 for <ietf@ietfa.amsl.com>; Fri,  8 Apr 2016 07:38:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Level: 
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 BHWSLM9wvBLL for <ietf@ietfa.amsl.com>; Fri,  8 Apr 2016 07:38:57 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3A5CA12D18A for <ietf@ietf.org>; Fri,  8 Apr 2016 07:38:57 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 84B502009E; Fri,  8 Apr 2016 10:42:35 -0400 (EDT)
Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 674B363755; Fri,  8 Apr 2016 10:38:56 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Ole Jacobsen <olejacobsen@me.com>
Subject: Re: China
In-Reply-To: <alpine.OSX.2.01.1604080420470.36488@rabdullah.local>
References: <0D914666-C3D4-4CCE-AD5E-4E5B34EA1A73@piuha.net> <20160407182936.GA21340@pfrc.org> <CAB75xn780nNDjGa_Cc222J20-+1CCHt09Xp8KHzaK=n0xx51pg@mail.gmail.com> <5706B100.9040509@mnt.se> <CAB75xn6fmj84ROUtG5eUB3GerHx83hrEr3w5vSADY_g=BRg5FA@mail.gmail.com> <5706BA40.3060005@mnt.se> <alpine.DEB.2.02.1604072157240.31096@uplift.swm.pp.se> <A9B63A6D-3102-482F-8FFC-2E57A5FD8336@nic.cz> <CC16B445-2B74-4182-BC58-F9D4BFFA1CCF@chopps.org> <alpine.OSX.2.01.1604080420470.36488@rabdullah.local>
X-Mailer: MH-E 8.6; nmh 1.6+dev; GNU Emacs 24.4.2
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Fri, 08 Apr 2016 10:38:56 -0400
Message-ID: <31709.1460126336@obiwan.sandelman.ca>
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/RiBSCQ5clePTNIX4DHGJ02mLnm0>
Cc: "ietf@ietf.org 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: Fri, 08 Apr 2016 14:38:59 -0000

--=-=-=
Content-Type: text/plain


Ole Jacobsen <olejacobsen@me.com> wrote:
    > I am sorry to hear that. Our "open and inclusive process" comprises
    > many participants from China who have traditionally faced harsh and
    > unpredictable visa problems in North America. In fairness to them, we
    > held that meeting in Beijing. Note that we did so following an
    > extensive discussion on the IETF mailing list and after negotiating
    > the removal of a rather ominous hotel clause, as well as an unfiltered
    > network in the meeting venue.

Yes, and we did this openly, and I don't feel we did the same thing here.
And there were still surprises, I'm told.

I was very surprised at the announcement for 100.
I kinda thought we should go back to San Diego as for IETF 1.
(well. Maybe IETF101 should be same as IETF 1... maybe IETF 100 should be
same as IETF 0, and be entirely virtual...)

(I didn't go because I generally have funds for two IETFs a year,
and given the hassle, and my concerns about what I would eat, it was simpler
to skip.  I skipped BA for a combination of economic, but primarily family reasons)


--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-




--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQEVAwUBVwfCfYCLcPvd0N1lAQK2Tgf/Sqva4o03Thm4q9ieojAVScQ2G9SIRcLy
q0yKY9T8OxI2oVAqLuAgHsqWm9i9R5hqP7oCr1DVRyNeTDXX7XO1JtruvnQ2Rd4E
qd7m+mX5wFenB7hyq2ykUWS+QCxkH+MgfbAMKEKdFHogMapxNTXAF4v+v7vKyKtR
kL7qEqaKAMcx/Y8yCG68rkjoXlhJklZAxKah8yzWLvfnSO4/CAiTJQqPC3qZmgqr
RERteljrs3hZCLRZK2W2ZrF22hUU/PDGFvpwuf0YZIoehBql5bioy/4/BCIIUR+S
04mAcsYZPiNZy9S3yxErSnuLQpigF8K1RApJyK9TMZtInqCSQekTig==
=JkaJ
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Fri Apr  8 07:41:02 2016
Return-Path: <eckert@cisco.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 1BA9E127058 for <ietf@ietfa.amsl.com>; Fri,  8 Apr 2016 07:41:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.53
X-Spam-Level: 
X-Spam-Status: No, score=-14.53 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_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 o3AZrFDYux7z for <ietf@ietfa.amsl.com>; Fri,  8 Apr 2016 07:40:58 -0700 (PDT)
Received: from alln-iport-2.cisco.com (alln-iport-2.cisco.com [173.37.142.89]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F0D3112D0CF for <ietf@ietf.org>; Fri,  8 Apr 2016 07:40:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2470; q=dns/txt; s=iport; t=1460126458; x=1461336058; h=from:to:cc:subject:date:message-id:references: in-reply-to:reply-to:mime-version; bh=d2+BMEk+GqQBm9xqZ27OkkH955NLoyUPvIVkbraoqFs=; b=WXqMj7IP4KLPZQaSOavRGEkPgpUN2bQA29+7WlSChM+8MBDBGwGc2lE+ Ob5Gk2iTogURPyrdBUJa2zAf624LcqsBaa+D1XtaDkoXYWX+ctNf3Q4fh BCUwJGxOQ9YsGotKnXLxgfEyLbD5UzqoPlZeJ2JWxJrGOR5gz3I2a7JHT k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AVBgCrwQdX/5ldJa1cgmtMU30BhUWwD?= =?us-ascii?q?IZ0IYQVgVcCgTM7EQEBAQEBAQFlJ4RBAQEBAwEtTAULAgEIBAEJCgklDyMOFwI?= =?us-ascii?q?EAQ0FiB8IDrRsi2EBAQEBAQEBAQEBAQEBAQEBAQEBAQEVimyEDxEBhXQFhi8Jk?= =?us-ascii?q?UwBjguPDY8kATYsgUyCG2yIBYE0AQEB?=
X-IronPort-AV: E=Sophos;i="5.24,454,1454976000";  d="scan'208,217";a="257568453"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by alln-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 08 Apr 2016 14:40:57 +0000
Received: from XCH-RCD-004.cisco.com (xch-rcd-004.cisco.com [173.37.102.14]) by rcdn-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id u38Eeu5O015533 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 8 Apr 2016 14:40:56 GMT
Received: from xch-rcd-003.cisco.com (173.37.102.13) by XCH-RCD-004.cisco.com (173.37.102.14) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Fri, 8 Apr 2016 09:40:56 -0500
Received: from xch-rcd-003.cisco.com ([173.37.102.13]) by XCH-RCD-003.cisco.com ([173.37.102.13]) with mapi id 15.00.1104.009; Fri, 8 Apr 2016 09:40:55 -0500
From: "Toerless Eckert (eckert)" <eckert@cisco.com>
To: Mikael Abrahamsson <swmike@swm.pp.se>, Laurent Ciavaglia <laurent.ciavaglia@nokia.com>
Subject: Re: Concerns about Singapore
Thread-Topic: Concerns about Singapore
Thread-Index: AQHRkOMT4Txyx7b5okKJbeuYe/M/VJ9/KOsAgAAATwCAAAuKAIAACE2AgAACugCAAAKSAIAAFhAAgADq5ID//+Q56g==
Date: Fri, 8 Apr 2016 14:40:55 +0000
Message-ID: <i0k76we3u16irdglfkpkkac2.1460126173782@email.android.com>
References: <0D914666-C3D4-4CCE-AD5E-4E5B34EA1A73@piuha.net> <20160407182936.GA21340@pfrc.org> <CAB75xn780nNDjGa_Cc222J20-+1CCHt09Xp8KHzaK=n0xx51pg@mail.gmail.com> <5706B100.9040509@mnt.se> <CAB75xn6fmj84ROUtG5eUB3GerHx83hrEr3w5vSADY_g=BRg5FA@mail.gmail.com> <5706BA40.3060005@mnt.se> <alpine.DEB.2.02.1604072157240.31096@uplift.swm.pp.se> <5706CEEA.70402@alcatel-lucent.com>, <alpine.DEB.2.02.1604081319150.16013@uplift.swm.pp.se>
In-Reply-To: <alpine.DEB.2.02.1604081319150.16013@uplift.swm.pp.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
Content-Type: multipart/alternative; boundary="_000_i0k76we3u16irdglfkpkkac21460126173782emailandroidcom_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/GKNuBj7zIug14Oje20nbEk1IT60>
Cc: "ietf@ietf.org Discussion" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: "Toerless Eckert \(eckert\)" <eckert@cisco.com>
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: Fri, 08 Apr 2016 14:41:01 -0000

--_000_i0k76we3u16irdglfkpkkac21460126173782emailandroidcom_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable


There is a difference between regulating behavior for everyone equally and =
regulating it selectively based on who you are - and can not or should not =
need to change.






Sent from my Samsung Captivate Glide on AT&T

Mikael Abrahamsson <swmike@swm.pp.se> wrote:
On Thu, 7 Apr 2016, Laurent Ciavaglia wrote:

> On 07/04/2016 22:00, EXT Mikael Abrahamsson wrote:
>> There are no perfect places to go.
> Except Minneapolis. ;)

http://www.dumblaws.com/laws/united-states/minnesota

"It is illegal to sleep naked."
"Oral sex is prohibited."

--
Mikael Abrahamsson    email: swmike@swm.pp.se


--_000_i0k76we3u16irdglfkpkkac21460126173782emailandroidcom_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Exchange Server">
<!-- converted from text --><style><!-- .EmailQuote { margin-left: 1pt; pad=
ding-left: 4pt; border-left: #800000 2px solid; } --></style>
</head>
<body>
<div>
<div><br>
</div>
<div>There is a difference between regulating behavior for everyone equally=
 and regulating it selectively based on who you are - and can not or should=
 not need to change.</div>
<div><br>
</div>
<div>&nbsp;&nbsp;</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div>
<div style=3D"font-size:75%; color:#575757">Sent from my Samsung Captivate =
Glide on AT&amp;T</div>
</div>
<br>
Mikael Abrahamsson &lt;swmike@swm.pp.se&gt; wrote:<br>
</div>
<font size=3D"2"><span style=3D"font-size:10pt;">
<div class=3D"PlainText">On Thu, 7 Apr 2016, Laurent Ciavaglia wrote:<br>
<br>
&gt; On 07/04/2016 22:00, EXT Mikael Abrahamsson wrote:<br>
&gt;&gt; There are no perfect places to go.<br>
&gt; Except Minneapolis. ;)<br>
<br>
<a href=3D"http://www.dumblaws.com/laws/united-states/minnesota">http://www=
.dumblaws.com/laws/united-states/minnesota</a><br>
<br>
&quot;It is illegal to sleep naked.&quot;<br>
&quot;Oral sex is prohibited.&quot;<br>
<br>
-- <br>
Mikael Abrahamsson&nbsp;&nbsp;&nbsp; email: swmike@swm.pp.se<br>
<br>
</div>
</span></font>
</body>
</html>

--_000_i0k76we3u16irdglfkpkkac21460126173782emailandroidcom_--


From nobody Fri Apr  8 07:43:46 2016
Return-Path: <mcr@sandelman.ca>
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 A881512D194 for <ietf@ietfa.amsl.com>; Fri,  8 Apr 2016 07:43:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Level: 
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 G0zvWNbtmbrp for <ietf@ietfa.amsl.com>; Fri,  8 Apr 2016 07:43:43 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0310A12D18A for <ietf@ietf.org>; Fri,  8 Apr 2016 07:43:43 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 5419A2009E; Fri,  8 Apr 2016 10:47:21 -0400 (EDT)
Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 28CEE63755; Fri,  8 Apr 2016 10:43:42 -0400 (EDT)
From: Michael Richardson <mcr@sandelman.ca>
To: Ole Jacobsen <olejacobsen@me.com>
Subject: Re: Concerns about Singapore
In-Reply-To: <alpine.OSX.2.01.1604080418530.36488@rabdullah.local>
References: <CAB75xn6fmj84ROUtG5eUB3GerHx83hrEr3w5vSADY_g=BRg5FA@mail.gmail.com> <1481689286.47880.1460111891664.JavaMail.yahoo@mail.yahoo.com> <alpine.OSX.2.01.1604080418530.36488@rabdullah.local>
X-Mailer: MH-E 8.6; nmh 1.6+dev; GNU Emacs 24.4.2
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <593.1460126622.1@obiwan.sandelman.ca>
Content-Transfer-Encoding: quoted-printable
Date: Fri, 08 Apr 2016 10:43:42 -0400
Message-ID: <594.1460126622@obiwan.sandelman.ca>
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/cmlVs3XQg6cy9TWVkrzAXIhRN9M>
Cc: "ietf@ietf.org 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: Fri, 08 Apr 2016 14:43:44 -0000

Ole Jacobsen <olejacobsen@me.com> wrote:
    > I found this website very interesting in terms of what to expect on
    > the ground in Singapore with respect to the issue at hand:

    > http://www.utopia-asia.com/tipssing.htm

An interesting read.

I think you have been there a few times?
Could a person stay in Skudai (Malaysia), and travel in every day for our =
meetings?


--
]               Never tell me the odds!                 | ipv6 mesh networ=
ks [
]   Michael Richardson, Sandelman Software Works        | network architec=
t  [
]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails =
   [


From nobody Fri Apr  8 07:46:54 2016
Return-Path: <dhc@dcrocker.net>
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 0A86D12D16B for <ietf@ietfa.amsl.com>; Fri,  8 Apr 2016 07:46:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] 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 r17GWCAVWjGL for <ietf@ietfa.amsl.com>; Fri,  8 Apr 2016 07:46:52 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BD0F7127058 for <ietf@ietf.org>; Fri,  8 Apr 2016 07:46:52 -0700 (PDT)
Received: from [192.168.1.168] (76-218-10-206.lightspeed.sntcca.sbcglobal.net [76.218.10.206]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id u38Ekp2c016437 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Fri, 8 Apr 2016 07:46:52 -0700
Subject: Re: Concerns about Singapore
To: Michael Richardson <mcr@sandelman.ca>, Ole Jacobsen <olejacobsen@me.com>
References: <CAB75xn6fmj84ROUtG5eUB3GerHx83hrEr3w5vSADY_g=BRg5FA@mail.gmail.com> <1481689286.47880.1460111891664.JavaMail.yahoo@mail.yahoo.com> <alpine.OSX.2.01.1604080418530.36488@rabdullah.local> <594.1460126622@obiwan.sandelman.ca>
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
Message-ID: <5707C458.7080107@dcrocker.net>
Date: Fri, 8 Apr 2016 07:46:48 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2
MIME-Version: 1.0
In-Reply-To: <594.1460126622@obiwan.sandelman.ca>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Fri, 08 Apr 2016 07:46:52 -0700 (PDT)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/0aLB_ONuEDqsYJo-EPeCAXBlKls>
Cc: "ietf@ietf.org Discussion" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: dcrocker@bbiw.net
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: Fri, 08 Apr 2016 14:46:54 -0000

On 4/8/2016 7:43 AM, Michael Richardson wrote:
> Could a person stay in Skudai (Malaysia), and travel in every day for our meetings?


That's a suburb of Johor, just into Malaysia from Singapore, so I 
believe the answer is yes, though I don't know what the transit times 
will be or whether it's a fully reliable path.  The two countries 
sometimes make that border awkward.

d/

-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net


From nobody Fri Apr  8 07:49:55 2016
Return-Path: <rpelletier@isoc.org>
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 9DADF12D09D for <ietf@ietfa.amsl.com>; Fri,  8 Apr 2016 07:49:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.903
X-Spam-Level: 
X-Spam-Status: No, score=-101.903 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=isoc.onmicrosoft.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 4NTjY3SdcKDv for <ietf@ietfa.amsl.com>; Fri,  8 Apr 2016 07:49:53 -0700 (PDT)
Received: from na01-bl2-obe.outbound.protection.outlook.com (mail-bl2on0077.outbound.protection.outlook.com [65.55.169.77]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C9FA3127058 for <ietf@ietf.org>; Fri,  8 Apr 2016 07:49:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=isoc.onmicrosoft.com;  s=selector1-isoc-org; h=From:To:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=diM2SL0HhKBEX64nNCMhl1cbwLz5QsLwdX3kFlABjnE=; b=x7zfQj54zJBH/dDGDT9+GX+SMpreEhp8I1O5B4xvehnyvCnVoMEqifUYf9JRuAvohvPF91SWm6kut2h5m482tREn2mv5s+smfu+Bkk96jIUOMu+cJBCQs74H7uJjmiIsk4aQ+j9oiML3KMy0N7QhZCPm6lOP5kMIO0kjYvuNry0=
Authentication-Results: piuha.net; dkim=none (message not signed) header.d=none;piuha.net; dmarc=none action=none header.from=isoc.org;
Received: from dhcp-b48d.meeting.ietf.org (31.133.180.141) by BY2PR0601MB1560.namprd06.prod.outlook.com (10.163.107.142) with Microsoft SMTP Server (TLS) id 15.1.447.15; Fri, 8 Apr 2016 14:49:49 +0000
Content-Type: text/plain; charset="windows-1252"
MIME-Version: 1.0 (Mac OS X Mail 9.2 \(3112\))
Subject: Re: A distinction along Pete's dimensions
From: Ray Pelletier <rpelletier@isoc.org>
In-Reply-To: <64652CD9-E9A1-4A4E-A68D-5FF3C8E431DB@piuha.net>
Date: Fri, 8 Apr 2016 11:45:23 -0300
Content-Transfer-Encoding: quoted-printable
Message-ID: <0177D010-C75C-4022-B739-164D75218189@isoc.org>
References: <0D914666-C3D4-4CCE-AD5E-4E5B34EA1A73@piuha.net> <20160407182936.GA21340@pfrc.org> <CAB75xn780nNDjGa_Cc222J20-+1CCHt09Xp8KHzaK=n0xx51pg@mail.gmail.com> <5706B100.9040509@mnt.se> <CAB75xn6fmj84ROUtG5eUB3GerHx83hrEr3w5vSADY_g=BRg5FA@mail.gmail.com> <5706BA40.3060005@mnt.se> <alpine.DEB.2.02.1604072157240.31096@uplift.swm.pp.se> <5706CEEA.70402@alcatel-lucent.com> <D8151E5B-3862-4A77-A3FD-18D63334AA29@mnt.se> <7E3E34E3-346F-49D4-8030-335E802BE150@puck.nether.net> <22E40FD2507C568AB2849D61@JcK-HP8200.jck.com> <5706EAD5.9070408@dcrocker.net> <64652CD9-E9A1-4A4E-A68D-5FF3C8E431DB@piuha.net>
To: Jari Arkko <jari.arkko@piuha.net>
X-Mailer: Apple Mail (2.3112)
X-Originating-IP: [31.133.180.141]
X-ClientProxiedBy: CY1PR14CA0035.namprd14.prod.outlook.com (10.163.13.173) To BY2PR0601MB1560.namprd06.prod.outlook.com (10.163.107.142)
X-MS-Office365-Filtering-Correlation-Id: 842ad0dd-7f63-479e-3108-08d35fbd0a17
X-Microsoft-Exchange-Diagnostics: 1; BY2PR0601MB1560; 2:kfUpJpBjXr+yJzdPyVjkmvxrFzGO1uDs5g6Ej9qNRLIjFMhBYHVXbi+SzPky6Z70DMjVkLjgQvjqYXpLvTXamlB7Vjfu9Zgw1/nk6xj/uJlOtGimh0HK1bcp/lJ7wVOtLy4nkP2miLnwGjnGS+emJGAyiYco3GgCA/0zwsh3ee2yPyp5G3a+KtL4W9yMQSnW; 3:SzPTJYeoldQlCfRTV26fKIYVGKLTLjegp6dTH5roEPU9/aq26UFb3TzXZ3Vx1oi9B48jjgOnaI84R6h6hadhXArAN7QxJR+hhPXQPrRFbl43GxMFiiX7R7JhofHfCsMi; 25:yGF92ECT2oO78h/hsH96BZGwMzbSflQsD8LjcXv1IoEtsf+cVqL1HypgKn4MwWxd/nzmwebpigPm2heWdwpCVdzfPDGohDik6xM8oRJF8GxjFVwSd1w1MAkEjbwrDIB8aEnyHnjFzTL2PUeAHzxML4wobplPItOkpzFjO6Zn5SQpoCfDy9PRt3uNjnNC9nL7wCL1Ys3tDBf+t83sxR3f1SpvbiNK5Ut751XfZ+gn73eCz3dRdOIeSbq3hIrfifBRsg0VUz6CTq6qz6dvXzzpfdMEDAhapuq5cYrWPy6Q1Mv5wu6fJPCK8z+wkRaX0e7ADoTbUwKRulw4pa1vtU/CwVq60HKQZALy/UyO5l35uVKo0bZjOowadkmftGg1yJW0/1/yur9atJj7Y3NA1iFgviuEfnBlzAOFYhCMIeHIDKp1eDDhWdAscvYlquSmT22Kf/j7Mboxf0PqClwdy3nPZ32GRyZwQmtvRM0G6CMO42mNhFSH+twptkDM43+EAZOxH0pcmwbAwqzR7laksutd2SHMxTDzwQkFfDVkIQ0S3YcRKF/T3rmYsGYoAnC1bEa/ttrs04KyE3U9Wn41/CU8l73tPq0SsQpnDQwrhsbcGsRXGq0atA5l4CFFVqGbT0Pe
X-Microsoft-Antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:BY2PR0601MB1560;
X-LD-Processed: 89f84dfb-7285-4810-bc4d-8b9b5794554f,ExtAddr
X-Microsoft-Exchange-Diagnostics: 1; BY2PR0601MB1560; 20:+u7lBi+r7nQV6RDMzFOysF/iD72Rz2b2miuGKaZoHqIQXnhtSg6sUxM1GArZPg/iSNCnjQxf63cNL0f7vxHrvXxXXQB2CccARDjTuG/T3jkgoF0MPHN8dT6FteDofIEONGESXdyGkPwmt7MSRFTute+tMEpFpaVRoDOUFtAaXd0wVvvRCC49xk+Oz42qELpdbn5tmVcKrL0E6KrE5olZMiEyskLLscONcOm8LjgcEM6hR00cNbfMawczZUO7+dYBMaTWyFCcXLx9VI45ZYv9ImYx4pliy2Y9CTMp8t+y2G/rtbKBNNzAviJzYUUyBp6shEG8k6jBHe9/pzaGY4a184gzFC5p40A5FAtAp6ICQ2TL5CMchsos3iB1CH2+fGnE3k4mqyB1COSof6cnyMhATXso2Dx4q5ysNZ/TBJoQ71IQStmn1ofb5j3cv0JWuHjgM3iI44qVoBbXwzGBpCy3aLak4eX+LVhjzqmKwnm4Bn0kQad7+NPe44FFhunHklih; 4:9gXAjqrdPt7q4Nklu6Bi2MPItZUK8TM3VinKj1bUf3MMtdvobGc3iuQztn2reN06z7W6if731CpF7YdggcGDQKtv5qHIt66deDmeLeq9M1vhaQVrOODfM9EmTowhRcPrgilK5Pb2kzVbd7P9xSGxTV16DV7c6Vrj1NCfgSKVUd+Sn2rwANkbpg7coj2gNmioZrr/Z3yx3dh9ARicD8Gci2nfO5eFI1YWUgZH/odfGy3ZDJCx33S0vCUARB7j4NWyjdkCHIf1dr7BX3OvuU4EsuQPsCemqIKms7L6JRQ2mDZSHc9CNylu6aJyVaElRBpWzDq4QlJGoQQhlqkpPJ049fpwMVjn3Y2eKHa6dEuoXH2yWbk32iSJuc2kuTAQaHTk
X-Microsoft-Antispam-PRVS: <BY2PR0601MB156016560D2098AFFC442487B0910@BY2PR0601MB1560.namprd06.prod.outlook.com>
X-Exchange-Antispam-Report-Test: UriScan:;
X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(601004)(2401047)(5005006)(8121501046)(10201501046)(3002001); SRVR:BY2PR0601MB1560; BCL:0; PCL:0; RULEID:; SRVR:BY2PR0601MB1560; 
X-Forefront-PRVS: 0906E83A25
X-Forefront-Antispam-Report: SFV:NSPM; SFS:(10009020)(4630300001)(6009001)(24454002)(377454003)(1096002)(50986999)(76176999)(5008740100001)(110136002)(50226001)(4326007)(2906002)(6116002)(3846002)(586003)(36756003)(92566002)(47776003)(82746002)(189998001)(57306001)(66066001)(86362001)(77096005)(2950100001)(19580405001)(19580395003)(83716003)(81166005)(23746002)(42186005)(5004730100002)(33656002)(50466002)(93886004)(7099028)(104396002); DIR:OUT; SFP:1101; SCL:1; SRVR:BY2PR0601MB1560; H:dhcp-b48d.meeting.ietf.org;  FPR:; SPF:None; MLV:sfv; LANG:en; 
X-Microsoft-Exchange-Diagnostics: =?Windows-1252?Q?1; BY2PR0601MB1560; 23:lZ0XeoH8uQRJL14xxejs5xOqJqc8QjqgH5C?= =?Windows-1252?Q?ZALofs0B6Iiy/5m+QCGWu8AT8QOr8endUrN8TPoGykTVOv8odgOxm5PA?= =?Windows-1252?Q?+6l1IWoZtv/9FmA2n6Kxy3BnYAirhF+z5J2jE71qm+M16JFa0PBtxFDt?= =?Windows-1252?Q?gX/g3X0K5FW4whq4NjZtHaGEdQMeFpohTDejuy6LFFohyAsAWehXHqWP?= =?Windows-1252?Q?NUGv1ookGlNGCoDDfBmDgb8+leHBvgO8sg6DbQleJavHdrCcTyo9Kqay?= =?Windows-1252?Q?G8GfoJpcva32WhG3Xl5B5e0bhqmkNCjYTF3eV0qOLCtvaES7t0MCz7Pk?= =?Windows-1252?Q?1SK6cDHBRXYVvCeohzvbscVPnCgz9reYvxx4QKwjp7j0BGPHEpfAQL6L?= =?Windows-1252?Q?Sz1oN4aR/LbKVwcJ2rBv6CU4hSFf0GX5UjK1dYCp07SF6UR5G5Zt8R7c?= =?Windows-1252?Q?OnIUwM4tESuOptJ/9u4qqUmtxmjF84KCxKQITqebI7MjdAnj8BhgeRwN?= =?Windows-1252?Q?kGeKYkTlBkwTkTFfGxbgmRMwYjqAEWCP3lIPbgZ8+eDTzZgtcN0r84/c?= =?Windows-1252?Q?vfaJMxHF2CJyTKK2ke2iEp7VVP+JJ9rBw1e3FbtOLMrv37BFvPjLcA9Z?= =?Windows-1252?Q?Tzr/M2T+y2xYEkIwqv9eiwtRFe1g37LlPN4mpdo/EUSj/yxsAg3+Qc8W?= =?Windows-1252?Q?96T0UzoHy0Epj07kqcqLnuliNIQM4gcOGD8/iVPvQvbWYSarjeWOz8E4?= =?Windows-1252?Q?H0SLed+kEGo5A3ufeZ1YZ1w8QpQQ6LGSeYOZUtdOW97Djl09jJB5ZI4b?= =?Windows-1252?Q?lBP9IfRXUEQfsu8b/lqt+7Tmf33ja81uIoDkyS2LttL62rruIgzut3Wx?= =?Windows-1252?Q?bWrT8b0dpiIIBHDsaqz0imu00u8XkbsNEP6xOQRhJ4kaLVKFYGKKIPr3?= =?Windows-1252?Q?ZXFh14hWc3vle1BI7RL3O6pncQomJeyGXvvv0RQWw1ovIcOOISPKIp6U?= =?Windows-1252?Q?CEZe0KfyWB3Lp0D7AF27k4MVlMeye9VHyLX3CfQKIj9QdNq/fYZX7SAN?= =?Windows-1252?Q?/r+hjS4/JilzEe+k=3D?=
X-Microsoft-Exchange-Diagnostics: 1; BY2PR0601MB1560; 5:tnuhYJAhID8kHe881tJclRVZC69vp+LXv77XkGqkeuslIxvo/oFAALNl+lqxYwumDnc3YI30wq2zxd9ZOusQQZkmOwkbfhzpfzLxe2k2rpQ88z4/vSZTPUNzYkWmtlOkxHUt+V5YcpO98bXufdN3qw==; 24:nFnImpvL/rMVn/C96+sauuYz6wmmMj2pxW8eS14j07pgRno3dE9YT5E/ZHIMrpQWvNjdaOZ5jHcGAh0UY4qvpp0ZHDoaEzjG3ffGH0pudPk=
SpamDiagnosticOutput: 1:23
SpamDiagnosticMetadata: NSPM
X-OriginatorOrg: isoc.org
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 08 Apr 2016 14:49:49.8683 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BY2PR0601MB1560
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/w2AuEEDIDC4EhmqDYTE152LC_6U>
Cc: John C Klensin <john-ietf@jck.com>, dcrocker@bbiw.net, "ietf@ietf.org 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: Fri, 08 Apr 2016 14:49:54 -0000

+1

ray
> On Apr 8, 2016, at 8:22 AM, Jari Arkko <jari.arkko@piuha.net> wrote:
>=20
>=20
>>  So when a new country or city is being considered -- and by new, I =
think I mean 'we have never been there', but perhaps we need to leave =
room for reconsideration of previously-visited places? -- we float the =
general countries and maybe cities to the community and wait for support =
and objections.
>>=20
>>=20
>> Whatever criteria the community chooses to apply at that time are the =
relevant criteria.  No theory or modeling or documentation or even =
consistency -- and especially no guessing and no errors by an anointed =
body -- are required.
>=20
> This would certainly work for me. There is obviously the question of =
calling what the result of the community discussion is, but I would view =
the community discussion as informing the decision by the meetings =
committee and the IAOC, i.e., the purpose of the crowdsourcing is to =
uncover issues that a smaller set of people might not catch, and then we =
have a better basis for the final decision.
>=20
> (Speaking personally, not representing IAOC or other opinions.)
>=20
> Jari
>=20


From nobody Fri Apr  8 08:05:35 2016
Return-Path: <aallen@blackberry.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 17EBD12D947 for <ietf@ietfa.amsl.com>; Fri,  8 Apr 2016 08:05:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.631
X-Spam-Level: 
X-Spam-Status: No, score=-2.631 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 OM1H_F6vKxBW for <ietf@ietfa.amsl.com>; Fri,  8 Apr 2016 08:05:26 -0700 (PDT)
Received: from smtp-p01.blackberry.com (smtp-p01.blackberry.com [208.65.78.88]) by ietfa.amsl.com (Postfix) with ESMTP id BED4B12D923 for <ietf@ietf.org>; Fri,  8 Apr 2016 08:05:16 -0700 (PDT)
Received: from smtp-pop.rim.net (HELO XCT104CNC.rim.net) ([10.65.161.204]) by mhs212cnc.rim.net with ESMTP/TLS/AES256-SHA; 08 Apr 2016 12:39:42 -0400
Received: from XMB122CNC.rim.net ([fe80::28c6:fa1c:91c6:2e23]) by XCT104CNC.rim.net ([::1]) with mapi id 14.03.0210.002; Fri, 8 Apr 2016 11:05:15 -0400
From: Andrew Allen <aallen@blackberry.com>
To: Dave Crocker <dcrocker@bbiw.net>, Michael Richardson <mcr@sandelman.ca>, Ole Jacobsen <olejacobsen@me.com>
Subject: Re: Concerns about Singapore
Thread-Topic: Concerns about Singapore
Thread-Index: AQHRkOMNjufwcA4TvkK+5mik25hZRp9/GCcAgAAATwCAAAuKAIAACE6AgAD6eICAAAvNgIAAOMwAgAAA3QD//8IaKw==
Date: Fri, 8 Apr 2016 15:05:14 +0000
Message-ID: <20160408150512.6283348.55871.10388@blackberry.com>
References: <CAB75xn6fmj84ROUtG5eUB3GerHx83hrEr3w5vSADY_g=BRg5FA@mail.gmail.com> <1481689286.47880.1460111891664.JavaMail.yahoo@mail.yahoo.com> <alpine.OSX.2.01.1604080418530.36488@rabdullah.local> <594.1460126622@obiwan.sandelman.ca>,<5707C458.7080107@dcrocker.net>
In-Reply-To: <5707C458.7080107@dcrocker.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/2LBJVEe6gGIKnqwSH7S_53jtBZM>
Cc: "ietf@ietf.org 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: Fri, 08 Apr 2016 15:05:34 -0000

According to the Web link posted earlier Malaysia has similar laws.

Sent from my BlackBerry 10 smartphone.
  Original Message
From: Dave Crocker
Sent: Friday, April 8, 2016 11:47
To: Michael Richardson; Ole Jacobsen
Reply To: dcrocker@bbiw.net
Cc: ietf@ietf.org Discussion
Subject: Re: Concerns about Singapore


On 4/8/2016 7:43 AM, Michael Richardson wrote:
> Could a person stay in Skudai (Malaysia), and travel in every day for our=
 meetings?


That's a suburb of Johor, just into Malaysia from Singapore, so I
believe the answer is yes, though I don't know what the transit times
will be or whether it's a fully reliable path.  The two countries
sometimes make that border awkward.

d/

--

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net


From nobody Fri Apr  8 08:14:40 2016
Return-Path: <sob@sobco.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 6433D12D91C for <ietf@ietfa.amsl.com>; Fri,  8 Apr 2016 08:14:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.109
X-Spam-Level: 
X-Spam-Status: No, score=-1.109 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RDNS_NONE=0.793, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=no 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 aZiIXIJDThOC for <ietf@ietfa.amsl.com>; Fri,  8 Apr 2016 08:14:37 -0700 (PDT)
Received: from sobco.sobco.com (unknown [136.248.127.164]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D56DC12D1A2 for <ietf@ietf.org>; Fri,  8 Apr 2016 08:14:37 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by sobco.sobco.com (Postfix) with ESMTP id EC3E81B378A1; Fri,  8 Apr 2016 11:14:36 -0400 (EDT)
X-Virus-Scanned: amavisd-new at sobco.com
Received: from sobco.sobco.com ([127.0.0.1]) by localhost (sobco.sobco.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jHr_4Vby2ENN; Fri,  8 Apr 2016 11:14:36 -0400 (EDT)
Received: from dhcp4.sobco.com (vpn3.sobco.com [136.248.127.174]) by sobco.sobco.com (Postfix) with ESMTPSA id D97E31B37894; Fri,  8 Apr 2016 11:14:35 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Subject: Re: China
From: Scott Bradner <sob@sobco.com>
In-Reply-To: <31709.1460126336@obiwan.sandelman.ca>
Date: Fri, 8 Apr 2016 11:14:33 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <3CE7670A-DBE4-4B47-BB02-DDD202B99480@sobco.com>
References: <0D914666-C3D4-4CCE-AD5E-4E5B34EA1A73@piuha.net> <20160407182936.GA21340@pfrc.org> <CAB75xn780nNDjGa_Cc222J20-+1CCHt09Xp8KHzaK=n0xx51pg@mail.gmail.com> <5706B100.9040509@mnt.se> <CAB75xn6fmj84ROUtG5eUB3GerHx83hrEr3w5vSADY_g=BRg5FA@mail.gmail.com> <5706BA40.3060005@mnt.se> <alpine.DEB.2.02.1604072157240.31096@uplift.swm.pp.se> <A9B63A6D-3102-482F-8FFC-2E57A5FD8336@nic.cz> <CC16B445-2B74-4182-BC58-F9D4BFFA1CCF@chopps.org> <alpine.OSX.2.01.1604080420470.36488@rabdullah.local> <31709.1460126336@obiwan.sandelman.ca>
To: Michael Richardson <mcr+ietf@sandelman.ca>
X-Mailer: Apple Mail (2.3124)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/3HWocbuRfRnHNKfc5Epmg25p-SY>
Cc: "ietf@ietf.org 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: Fri, 08 Apr 2016 15:14:39 -0000

some on the IAOC wanted to go back to SD for IETF 100 but the facilities =
were not available=20
at the right time

Scott

> On Apr 8, 2016, at 10:38 AM, Michael Richardson =
<mcr+ietf@sandelman.ca> wrote:
>=20
>=20
> Ole Jacobsen <olejacobsen@me.com> wrote:
>> I am sorry to hear that. Our "open and inclusive process" comprises
>> many participants from China who have traditionally faced harsh and
>> unpredictable visa problems in North America. In fairness to them, we
>> held that meeting in Beijing. Note that we did so following an
>> extensive discussion on the IETF mailing list and after negotiating
>> the removal of a rather ominous hotel clause, as well as an =
unfiltered
>> network in the meeting venue.
>=20
> Yes, and we did this openly, and I don't feel we did the same thing =
here.
> And there were still surprises, I'm told.
>=20
> I was very surprised at the announcement for 100.
> I kinda thought we should go back to San Diego as for IETF 1.
> (well. Maybe IETF101 should be same as IETF 1... maybe IETF 100 should =
be
> same as IETF 0, and be entirely virtual...)
>=20
> (I didn't go because I generally have funds for two IETFs a year,
> and given the hassle, and my concerns about what I would eat, it was =
simpler
> to skip.  I skipped BA for a combination of economic, but primarily =
family reasons)
>=20
>=20
> --
> Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
> -=3D IPv6 IoT consulting =3D-
>=20
>=20
>=20


From nobody Fri Apr  8 08:19:28 2016
Return-Path: <superuser@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 E6A9712D772 for <ietf@ietfa.amsl.com>; Fri,  8 Apr 2016 08:19:27 -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 nbPS274d7_Uh for <ietf@ietfa.amsl.com>; Fri,  8 Apr 2016 08:19:22 -0700 (PDT)
Received: from mail-vk0-x229.google.com (mail-vk0-x229.google.com [IPv6:2607:f8b0:400c:c05::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 0BFCC12D84C for <ietf@ietf.org>; Fri,  8 Apr 2016 08:19:22 -0700 (PDT)
Received: by mail-vk0-x229.google.com with SMTP id k1so141824157vkb.0 for <ietf@ietf.org>; Fri, 08 Apr 2016 08:19:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=IquSch+KId6kPXbN19TOFCSEcU26e9LBN1hWgGIAupM=; b=TaFFTpJw67t4Eq2Sxh/wNT8J0ZnFZQjHNbW2RNBtuNb5t1a7GmWBii1fvxR1ZI0h2U p581GYqgefK9D+cc8Gg+KgrTOP5nLu2ZTfrICzVB5iZ/TqTR4Vg3LOCxB8anj8gDaQC4 tSG2xE2tKIejydKhpI8RnhGZMz59pJPzumPdR9DQRZ58NnmJAEXfxc6u7qbEEetz7bk6 Rt5iq0qpj+KZm6ZAs1nT14dI72OAy7Oc+zL3FWNhs1bFkzQVh0BwuK/NQYLtgKYKyaPK yVrKo6eUA4+9XzDndumwpSJjpgY0x/6JSxdANB7BgfCmSK6nKBC6wv3A3qwj2rWP+xVd i+xQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=IquSch+KId6kPXbN19TOFCSEcU26e9LBN1hWgGIAupM=; b=IIq48pkJDzwfglWBZVoJzA0a0+rO2VFqvrl18TgxO04+lmEx0E4TEe5kv7q0yGv0KH 7Wwqur4fEbUeVs2m5a5jTz0oViz+HFDHT4wsKgwcvPfmx1jzQnk4fKJz0a5wJ1P3YEvX l9DuDcoAHrMlZJT+KRlPfPv/MiaUOCssCXs1GddINGS/yfKlxQ+utZzJI8kvUNRCGx4L kP8Xy9x9SghcX1CTpHdNtR2je8+lmkCbWPL+43Lu0cDgBPKXOu/XNliEI88MFVsuenpy VcmHvm19ffIZ9QZWgS3c6ffeVCpEd/uDDca8zF6nHMZBiM1/+kHT/h0vwjN6aY5n5Czl Aldw==
X-Gm-Message-State: AD7BkJLTrJ/DAxgIw63XVCd46GDepRE3s45/yO05djhdZf0rxJHGhsN+xQV1dGos5JgsgDiMerrv6t8ffv6Jjw==
X-Received: by 10.159.33.141 with SMTP id 13mr4474117uac.57.1460128760978; Fri, 08 Apr 2016 08:19:20 -0700 (PDT)
MIME-Version: 1.0
References: <CAL0qLwY0FuDp5=RMFEhUMtkK=XNDxX2dogvVY7+OSy88jrrvOQ@mail.gmail.com> <CAPt1N1=SYpo-CiHoc07Ukb04Kb1LGV2=BPPyRLUsaqyLM9Hbwg@mail.gmail.com> <CAL0qLwbhYRqw7fXHzYY0=W-CpmeHeDdaZx3z2Qg0cA2aMrmVwg@mail.gmail.com> <CAPt1N1nqmC7NJyg2M6Na8vUj8T-qObO-1gHFEXZzrobb3oOQhA@mail.gmail.com> <CAL0qLwZHGa5OvSmZ=bTd6AWchsm4r=QaJn2nPqD+YjeWPmH9pA@mail.gmail.com> <24691.1460062367@obiwan.sandelman.ca> <5706CC94.3080804@gmail.com> <CAL0qLwYvCpL9wwHL0E33HRbMvcckpad=gV-VYgAomJpCdiSrpg@mail.gmail.com> <5E36120B-6D4E-4C0D-9905-2C698455D395@att.com> <CAL0qLwak6GRDYAcYqdOewoSmRj6DP5ptQKjqXkOedBaHcKC7WA@mail.gmail.com> <60B61524-EFF7-4489-A0C7-AA4A139FEF6C@att.com> <CAL0qLwYDW_zwfdr4-2=r0vt2Cb1wNFm+-aog0Wubu+8PbaYWEw@mail.gmail.com> <6012C604-0922-4582-A505-F7934B5FD903@att.com> <23201.1460124058@obiwan.sandelman.ca> <CAPt1N1=VL4AUUJC2fdm-YV33kpHhzd54t3Dx0YBh7q0-=RV1Vw@mail.gmail.com>
In-Reply-To: <CAPt1N1=VL4AUUJC2fdm-YV33kpHhzd54t3Dx0YBh7q0-=RV1Vw@mail.gmail.com>
From: "Murray S. Kucherawy" <superuser@gmail.com>
Date: Fri, 08 Apr 2016 15:19:10 +0000
Message-ID: <CAL0qLwaepirx=HRc3yxW6TAFrwGGETmT8VGKUybYoUBh=ckPCA@mail.gmail.com>
Subject: Re: Qualifying for NomCom
To: Ted Lemon <mellon@fugue.com>, Michael Richardson <mcr+ietf@sandelman.ca>
Content-Type: multipart/alternative; boundary=001a113dfcea1fe3cf052ffab854
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/RfMvPzwI3-oUyL7YKS6DkgFGG20>
Cc: ietf <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: Fri, 08 Apr 2016 15:19:28 -0000

--001a113dfcea1fe3cf052ffab854
Content-Type: text/plain; charset=UTF-8

On Fri, Apr 8, 2016, 11:08 Ted Lemon <mellon@fugue.com> wrote:

> There are some issues here.   First, who can challenge a nomcom
> volunteer's elegibility?
>

Anyone, I think. RFC7437 talks about it.

  Second, what process is followed if their eligibility is challenged?
>

I think that's unspecified; the Chair just has to resolve the issue
somehow.

  This actually seems a lot harder than some of the other proposals that
> were put forth, which simply extended eligibility of the same type to more
> IETF participants, rather than creating two classes of IETF participants.
>

Anything more specific seems to create a lot of burden for the a chair who
has to manually vet every applicant in terms of their contributions (which,
I bet, I'd at least as painful as determining consensus on something), and
it can introduce bias. Putting that burden on the community instead seems a
better approach.

-MSK

--001a113dfcea1fe3cf052ffab854
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<br><br><div class=3D"gmail_quote"><div dir=3D"ltr">On Fri, Apr 8, 2016, 11=
:08 Ted Lemon &lt;<a href=3D"mailto:mellon@fugue.com">mellon@fugue.com</a>&=
gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0=
 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr">There a=
re some issues here. =C2=A0 First, who can challenge a nomcom volunteer&#39=
;s elegibility?</div></blockquote></div><div><br></div><div>Anyone, I think=
. RFC7437 talks about it.=C2=A0</div><div><br></div><div class=3D"gmail_quo=
te"><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-lef=
t:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr"> =C2=A0 Second, what pr=
ocess is followed if their eligibility is challenged?</div></blockquote></d=
iv><div><br></div><div>I think that&#39;s unspecified; the Chair just has t=
o resolve the issue somehow.=C2=A0</div><div><br></div><div class=3D"gmail_=
quote"><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-=
left:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr"> =C2=A0 This actuall=
y seems a lot harder than some of the other proposals that were put forth, =
which simply extended eligibility of the same type to more IETF participant=
s, rather than creating two classes of IETF participants.</div></blockquote=
></div><div><br></div><div>Anything more specific seems to create a lot of =
burden for the a chair who has to manually vet every applicant in terms of =
their contributions (which, I bet, I&#39;d at least as painful as determini=
ng consensus on something), and it can introduce bias. Putting that burden =
on the community instead seems a better approach.=C2=A0</div><div><br></div=
><div>-MSK</div>

--001a113dfcea1fe3cf052ffab854--


From nobody Fri Apr  8 08:21:46 2016
Return-Path: <llynch@civil-tongue.net>
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 4F6B612D51D for <ietf@ietfa.amsl.com>; Fri,  8 Apr 2016 08:21:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.901
X-Spam-Level: 
X-Spam-Status: No, score=-6.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001] 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 coKiPkie_ikS for <ietf@ietfa.amsl.com>; Fri,  8 Apr 2016 08:21:43 -0700 (PDT)
Received: from hans.rg.net (hans.rg.net [IPv6:2001:418:1::42]) by ietfa.amsl.com (Postfix) with ESMTP id 065AC12D1B0 for <ietf@ietf.org>; Fri,  8 Apr 2016 08:21:43 -0700 (PDT)
Received: from hans.rg.net (hans.rg.net [IPv6:2001:418:1:0:0:0:0:42]) (authenticated bits=0) by hans.rg.net (8.15.2/8.14.9) with ESMTPSA id u38FLeBl090244 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Fri, 8 Apr 2016 15:21:40 GMT (envelope-from llynch@civil-tongue.net)
Date: Fri, 8 Apr 2016 15:21:40 +0000 (UTC)
From: Lucy Lynch <llynch@civil-tongue.net>
X-X-Sender: llynch@hans.rg.net
To: Ted Lemon <mellon@fugue.com>
Subject: Re: Qualifying for NomCom
In-Reply-To: <CAPt1N1=VL4AUUJC2fdm-YV33kpHhzd54t3Dx0YBh7q0-=RV1Vw@mail.gmail.com>
Message-ID: <alpine.BSF.2.20.1604081516150.41080@hans.rg.net>
References: <CAL0qLwY0FuDp5=RMFEhUMtkK=XNDxX2dogvVY7+OSy88jrrvOQ@mail.gmail.com> <CAPt1N1=SYpo-CiHoc07Ukb04Kb1LGV2=BPPyRLUsaqyLM9Hbwg@mail.gmail.com> <CAL0qLwbhYRqw7fXHzYY0=W-CpmeHeDdaZx3z2Qg0cA2aMrmVwg@mail.gmail.com> <CAPt1N1nqmC7NJyg2M6Na8vUj8T-qObO-1gHFEXZzrobb3oOQhA@mail.gmail.com> <CAL0qLwZHGa5OvSmZ=bTd6AWchsm4r=QaJn2nPqD+YjeWPmH9pA@mail.gmail.com> <24691.1460062367@obiwan.sandelman.ca> <5706CC94.3080804@gmail.com> <CAL0qLwYvCpL9wwHL0E33HRbMvcckpad=gV-VYgAomJpCdiSrpg@mail.gmail.com> <5E36120B-6D4E-4C0D-9905-2C698455D395@att.com> <CAL0qLwak6GRDYAcYqdOewoSmRj6DP5ptQKjqXkOedBaHcKC7WA@mail.gmail.com> <60B61524-EFF7-4489-A0C7-AA4A139FEF6C@att.com> <CAL0qLwYDW_zwfdr4-2=r0vt2Cb1wNFm+-aog0Wubu+8PbaYWEw@mail.gmail.com> <6012C604-0922-4582-A505-F7934B5FD903@att.com> <23201.1460124058@obiwan.sandelman.ca> <CAPt1N1=VL4AUUJC2fdm-YV33kpHhzd54t3Dx0YBh7q0-=RV1Vw@mail.gmail.com>
User-Agent: Alpine 2.20 (BSF 67 2015-01-07)
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset=US-ASCII
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/pzH6ooEpN8K25-qhe1tKzfpgjZU>
Cc: Michael Richardson <mcr+ietf@sandelman.ca>, ietf <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: Fri, 08 Apr 2016 15:21:45 -0000

On Fri, 8 Apr 2016, Ted Lemon wrote:

> There are some issues here.   First, who can challenge a nomcom volunteer's
> elegibility?   Second, what process is followed if their eligibility is
> challenged?   This actually seems a lot harder than some of the other
> proposals that were put forth, which simply extended eligibility of the
> same type to more IETF participants, rather than creating two classes of
> IETF participants.

Thanks Ted -

As the incoming NomCom chair I have some concerns about how exercising 
judgment can scale to possible requests. The current selection and vetting 
process already includes a lot of steps and processing - if you want to 
add a layer here I'd like to feel confident that this was something the 
community really wanted and that the proposed vetting wouldn't leave those 
executing exposed to second guessing after the fact.

- Lucy


> On Fri, Apr 8, 2016 at 11:00 AM, Michael Richardson <mcr+ietf@sandelman.ca>
> wrote:
>
>>
>> So, we'll know by August if the experiment resulted in more volunteers.
>>
>> My only concern is that we decide it was ineffective in getting more
>> diverse
>> volunteers,  and stop; but it might have needed more than 1 year to
>> socialize
>> the ideas out there.
>>
>> A result might also be: the new rules cause no harm and should be kept
>> until
>> such time we have more data.
>>
>> --
>> Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
>>  -= IPv6 IoT consulting =-
>>
>>
>>
>>
>


From nobody Fri Apr  8 08:31:09 2016
Return-Path: <ynir.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 9717E12D673 for <ietf@ietfa.amsl.com>; Fri,  8 Apr 2016 08:31:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 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, RCVD_IN_DNSWL_LOW=-0.7, 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 iqCMYzldUlHs for <ietf@ietfa.amsl.com>; Fri,  8 Apr 2016 08:31:05 -0700 (PDT)
Received: from mail-qk0-x233.google.com (mail-qk0-x233.google.com [IPv6:2607:f8b0:400d:c09::233]) (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 AFE6C12D101 for <ietf@ietf.org>; Fri,  8 Apr 2016 08:31:05 -0700 (PDT)
Received: by mail-qk0-x233.google.com with SMTP id o6so45303887qkc.2 for <ietf@ietf.org>; Fri, 08 Apr 2016 08:31:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=8r0hboJtpcKsom2678Zg97uwInpYsSq4TGTOLu1Ei6s=; b=VSCe+z1jNGDPyV1xwsSNDZVjQazhDHXE+DT5R9ikmqYFyJ4Wsv/5soSNfKn612NuJk hr+aM6VQQbxfQDB2cUNdW595aUQTYEMEPvdip3JHPYSP0RMI4+BiPrgpAWQymAt/93b5 LxxnKBpKuVMJqwjc0aMzzw7EfBbNb6hevRN/FbBo9QZUkDduu1j0pwaTCVohZDRS2bQE ZWABjZhRgfCQUelC4P85NprccyMzgLh27mGF9Bt3BGKWUVWLzzN0BmMLVP4Y881Uv1n8 xlZiEOtrRqrj0D49yrFiT2ArAYI2QOmcyL+y+86N4uF7Pfr6BAGCwV8SG5LRmuWG89Js ijTw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=8r0hboJtpcKsom2678Zg97uwInpYsSq4TGTOLu1Ei6s=; b=Onn7MUzgJ1M8aBdGP1jNBd7O97C2MJW82XnPWLjilU8Ns0BZsE0Ei06HtL5Q2YHdn6 uOHJEl1Edvec8PIEsfp0Dc02uwLy/ys6AyQDxYmP/9VBHcj1fUCnr3DQ03/q/Ug+qhKt PENI8su/ILWce8HhcQfFLITsgK+yq5Ca3ouoOpUAQKG12UvURN/U2iugsgiYug+gYbMV 8AxIPSoAf0bMqYw7WpOQdzo3nbxm+wlUzjSYMjA8CsFb0CULxzxXN/4KOSAv117PrqJV lZr7Gn6GTzJyK+6rBbLJPBqfic3MwualBu7/yexosZSVs+nBsncam5fR1aKZLXGvyOY2 4zOQ==
X-Gm-Message-State: AD7BkJJc7zXcQyGOfovSxsDiAy4jizxWpwd4/jyAV9XLd2kqZOX4yfuGTa3HSyFDkYyCcA==
X-Received: by 10.55.165.3 with SMTP id o3mr10386801qke.0.1460129464817; Fri, 08 Apr 2016 08:31:04 -0700 (PDT)
Received: from ?IPv6:2001:67c:370:176:ed32:896e:2bc8:42cd? ([2001:67c:370:176:ed32:896e:2bc8:42cd]) by smtp.gmail.com with ESMTPSA id x10sm5656786qhc.42.2016.04.08.08.31.01 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Fri, 08 Apr 2016 08:31:03 -0700 (PDT)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Subject: Re: Concerns about Singapore
From: Yoav Nir <ynir.ietf@gmail.com>
In-Reply-To: <20160408150512.6283348.55871.10388@blackberry.com>
Date: Fri, 8 Apr 2016 12:30:59 -0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <A9E6E707-86DD-4E4A-BD5C-A7B0D6E40398@gmail.com>
References: <CAB75xn6fmj84ROUtG5eUB3GerHx83hrEr3w5vSADY_g=BRg5FA@mail.gmail.com> <1481689286.47880.1460111891664.JavaMail.yahoo@mail.yahoo.com> <alpine.OSX.2.01.1604080418530.36488@rabdullah.local> <594.1460126622@obiwan.sandelman.ca> <5707C458.7080107@dcrocker.net> <20160408150512.6283348.55871.10388@blackberry.com>
To: Andrew Allen <aallen@blackberry.com>
X-Mailer: Apple Mail (2.3124)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/_kgNwlszMYT1eQNlP3RhdILGLAA>
Cc: "ietf@ietf.org Discussion" <ietf@ietf.org>, Dave Crocker <dcrocker@bbiw.net>, Michael Richardson <mcr@sandelman.ca>
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: Fri, 08 Apr 2016 15:31:07 -0000

And I can=92t enter Malaysia at all.

> On 8 Apr 2016, at 12:05 PM, Andrew Allen <aallen@blackberry.com> =
wrote:
>=20
> According to the Web link posted earlier Malaysia has similar laws.
>=20
> Sent from my BlackBerry 10 smartphone.
>  Original Message
> From: Dave Crocker
> Sent: Friday, April 8, 2016 11:47
> To: Michael Richardson; Ole Jacobsen
> Reply To: dcrocker@bbiw.net
> Cc: ietf@ietf.org Discussion
> Subject: Re: Concerns about Singapore
>=20
>=20
> On 4/8/2016 7:43 AM, Michael Richardson wrote:
>> Could a person stay in Skudai (Malaysia), and travel in every day for =
our meetings?
>=20
>=20
> That's a suburb of Johor, just into Malaysia from Singapore, so I
> believe the answer is yes, though I don't know what the transit times
> will be or whether it's a fully reliable path.  The two countries
> sometimes make that border awkward.
>=20
> d/
>=20
> --
>=20
>   Dave Crocker
>   Brandenburg InternetWorking
>   bbiw.net
>=20


From nobody Fri Apr  8 08:34:56 2016
Return-Path: <tjc@ecs.soton.ac.uk>
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 AD9F512D1AE for <ietf@ietfa.amsl.com>; Fri,  8 Apr 2016 08:34:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.531
X-Spam-Level: 
X-Spam-Status: No, score=-3.531 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_NEUTRAL=0.779, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ecs.soton.ac.uk
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 4L9A7VN_ecOv for <ietf@ietfa.amsl.com>; Fri,  8 Apr 2016 08:34:52 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [IPv6:2001:630:d0:f102::25e]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1A93712D1A4 for <ietf@ietf.org>; Fri,  8 Apr 2016 08:34:51 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (localhost [127.0.0.1]) by falcon.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id u38FYmMY001022; Fri, 8 Apr 2016 16:34:49 +0100
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk u38FYmMY001022
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=201304; t=1460129689; bh=/Sxr3cSlwn2mnPJKtmlW4d8nSFc=; h=Mime-Version:Subject:From:In-Reply-To:Date:Cc:References:To; b=IGBYxXtkwzu0kzPr38oUSLn/KJcNJRkqOSBJoKFv+cNmqzB7bDPHBrLAEGrC49D1f W89p3aJGhaCuLnLxpkTTqAtLAAd4mmoiAjeHm6LWbv5wxbGXmdfdhWyxnYXrazjH03 qBnDpXfpJLCLAk/BfSr0CfwM1FZCzohlvzqCggkY=
Received: from gander.ecs.soton.ac.uk (gander.ecs.soton.ac.uk [2001:630:d0:f102::25d]) by falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [2001:630:d0:f102::25e]) envelope-from <tjc@ecs.soton.ac.uk> with ESMTP (valid=N/A) id s37GYm0691506569DE ret-id none; Fri, 08 Apr 2016 16:34:49 +0100
Received: from [10.220.17.43] (int-200-49-217-75.movi.com.ar [200.49.217.75] (may be forged)) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id u38FYg37022067; Fri, 8 Apr 2016 16:34:43 +0100
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (1.0)
Subject: Re: China
From: Tim Chown <tjc@ecs.soton.ac.uk>
X-Mailer: iPhone Mail (13E238)
In-Reply-To: <3CE7670A-DBE4-4B47-BB02-DDD202B99480@sobco.com>
Date: Fri, 8 Apr 2016 16:34:41 +0100
Content-Transfer-Encoding: quoted-printable
Message-ID: <EMEW3|1732d6f3eb6217487ddc48b4e7c8e5ces37GYm03tjc|ecs.soton.ac.uk|3548A1F1-F0CF-4609-B307-385E2BAEF897@ecs.soton.ac.uk>
References: <0D914666-C3D4-4CCE-AD5E-4E5B34EA1A73@piuha.net> <20160407182936.GA21340@pfrc.org> <CAB75xn780nNDjGa_Cc222J20-+1CCHt09Xp8KHzaK=n0xx51pg@mail.gmail.com> <5706B100.9040509@mnt.se> <CAB75xn6fmj84ROUtG5eUB3GerHx83hrEr3w5vSADY_g=BRg5FA@mail.gmail.com> <5706BA40.3060005@mnt.se> <alpine.DEB.2.02.1604072157240.31096@uplift.swm.pp.se> <A9B63A6D-3102-482F-8FFC-2E57A5FD8336@nic.cz> <CC16B445-2B74-4182-BC58-F9D4BFFA1CCF@chopps.org> <alpine.OSX.2.01.1604080420470.36488@rabdullah.local> <31709.1460126336@obiwan.sandelman.ca> <3CE7670A-DBE4-4B47-BB02-DDD202B99480@sobco.com> <3548A1F1-F0CF-4609-B307-385E2BAEF897@ecs.soton.ac.uk>
To: Scott Bradner <sob@sobco.com>
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=s37GYm069150656900; tid=s37GYm0691506569DE; client=relay,ipv6; mail=; rcpt=; nrcpt=3:0; fails=0
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: u38FYmMY001022
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/xFR3290ZzaRYllkwuFqlmLViZ34>
Cc: Michael Richardson <mcr+ietf@sandelman.ca>, "ietf@ietf.org 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: Fri, 08 Apr 2016 15:34:54 -0000

On 8 Apr 2016, at 16:14, Scott Bradner <sob@sobco.com> wrote:
>=20
> some on the IAOC wanted to go back to SD for IETF 100 but the facilities w=
ere not available=20
> at the right time

Ah, I was expecting the plenary drumroll to reveal just this - IETF100 at Sa=
n Diego.=20

A shame it couldn't happen, but perhaps an indicator we do need to keep plan=
ning 3-4 years out.

And for the right venue, we should be able to slide the dates forwards/back a=
 week or two.=20

Tim

>=20
> Scott
>=20
>> On Apr 8, 2016, at 10:38 AM, Michael Richardson <mcr+ietf@sandelman.ca> w=
rote:
>>=20
>>=20
>> Ole Jacobsen <olejacobsen@me.com> wrote:
>>> I am sorry to hear that. Our "open and inclusive process" comprises
>>> many participants from China who have traditionally faced harsh and
>>> unpredictable visa problems in North America. In fairness to them, we
>>> held that meeting in Beijing. Note that we did so following an
>>> extensive discussion on the IETF mailing list and after negotiating
>>> the removal of a rather ominous hotel clause, as well as an unfiltered
>>> network in the meeting venue.
>>=20
>> Yes, and we did this openly, and I don't feel we did the same thing here.=

>> And there were still surprises, I'm told.
>>=20
>> I was very surprised at the announcement for 100.
>> I kinda thought we should go back to San Diego as for IETF 1.
>> (well. Maybe IETF101 should be same as IETF 1... maybe IETF 100 should be=

>> same as IETF 0, and be entirely virtual...)
>>=20
>> (I didn't go because I generally have funds for two IETFs a year,
>> and given the hassle, and my concerns about what I would eat, it was simp=
ler
>> to skip.  I skipped BA for a combination of economic, but primarily famil=
y reasons)
>>=20
>>=20
>> --
>> Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
>> -=3D IPv6 IoT consulting =3D-
>>=20
>>=20
>>=20
>=20


From nobody Fri Apr  8 08:49:39 2016
Return-Path: <rpelletier@isoc.org>
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 4291712D101 for <ietf@ietfa.amsl.com>; Fri,  8 Apr 2016 08:49:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.902
X-Spam-Level: 
X-Spam-Status: No, score=-101.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=isoc.onmicrosoft.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 WXXhrEteSs-X for <ietf@ietfa.amsl.com>; Fri,  8 Apr 2016 08:49:34 -0700 (PDT)
Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1on0637.outbound.protection.outlook.com [IPv6:2a01:111:f400:fc10::637]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EA39712D517 for <ietf@ietf.org>; Fri,  8 Apr 2016 08:49:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=isoc.onmicrosoft.com;  s=selector1-isoc-org; h=From:To:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=2CMRlczF9KKIuTqsY+/aBHSpYGqcjk/Waq7tX3jsYUk=; b=FyJO4oqQFHNkfV4UG+eow6PR0/Vu7fNBhqgHExBxwX73Gkky9XN+t+cW5U8W86VTzfyckNHNxsohfVwALL0yirtAGosuRyO85SddxhOMlMUlzqEHM8cWC5ynuQN1HVtyDmRRowFZGWX62JBJskwgaNadELyLO8A5IvcFU4fa5UY=
Authentication-Results: ecs.soton.ac.uk; dkim=none (message not signed) header.d=none;ecs.soton.ac.uk; dmarc=none action=none header.from=isoc.org;
Received: from dhcp-b48d.meeting.ietf.org (31.133.180.141) by SN1PR0601MB1568.namprd06.prod.outlook.com (10.163.202.18) with Microsoft SMTP Server (TLS) id 15.1.447.15; Fri, 8 Apr 2016 15:49:08 +0000
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0 (Mac OS X Mail 9.2 \(3112\))
Subject: Re: China
From: Ray Pelletier <rpelletier@isoc.org>
In-Reply-To: <EMEW3|1732d6f3eb6217487ddc48b4e7c8e5ces37GYm03tjc|ecs.soton.ac.uk|3548A1F1-F0CF-4609-B307-385E2BAEF897@ecs.soton.ac.uk>
Date: Fri, 8 Apr 2016 12:50:53 -0300
Content-Transfer-Encoding: quoted-printable
Message-ID: <F377B008-6D7B-4B2B-ADFC-461CBAE43E23@isoc.org>
References: <0D914666-C3D4-4CCE-AD5E-4E5B34EA1A73@piuha.net> <20160407182936.GA21340@pfrc.org> <CAB75xn780nNDjGa_Cc222J20-+1CCHt09Xp8KHzaK=n0xx51pg@mail.gmail.com> <5706B100.9040509@mnt.se> <CAB75xn6fmj84ROUtG5eUB3GerHx83hrEr3w5vSADY_g=BRg5FA@mail.gmail.com> <5706BA40.3060005@mnt.se> <alpine.DEB.2.02.1604072157240.31096@uplift.swm.pp.se> <A9B63A6D-3102-482F-8FFC-2E57A5FD8336@nic.cz> <CC16B445-2B74-4182-BC58-F9D4BFFA1CCF@chopps.org> <alpine.OSX.2.01.1604080420470.36488@rabdullah.local> <31709.1460126336@obiwan.sandelman.ca> <3CE7670A-DBE4-4B47-BB02-DDD202B99480@sobco.com> <3548A1F1-F0CF-4609-B307-385E2BAEF897@ecs.soton.ac.uk> <EMEW3|1732d6f3eb6217487ddc48b4e7c8e5ces37GYm03tjc|ecs.soton.ac.uk|3548A1F1-F0CF-4609-B307-385E2BAEF897@ecs.soton.ac.uk>
To: Tim Chown <tjc@ecs.soton.ac.uk>
X-Mailer: Apple Mail (2.3112)
X-Originating-IP: [31.133.180.141]
X-ClientProxiedBy: BY1PR14CA0016.namprd14.prod.outlook.com (10.161.91.26) To SN1PR0601MB1568.namprd06.prod.outlook.com (10.163.202.18)
X-MS-Office365-Filtering-Correlation-Id: 4310a1c3-bdc3-4599-5e2a-08d35fc55357
X-Microsoft-Exchange-Diagnostics: 1; SN1PR0601MB1568; 2:z0Od1P/eJljEjXctma1hxlXXWL9qvvZC6tmPcWq3PJNB+yydK2V9nD/6sXpT3OBN2wqfXhJ5ByLV2f1gA6pAtXh62lfjMHPKHg3MxiPU2QlI/z6LQI85qpy7NyyYQAmus4KXC6FyEG3CGOMpq7SMCtA4B8r6acHxyo51qkx5Q2Nq9ubu5Ww15PUZarmXLsoZ; 3:Cb5Tk8O+oOJXHCa+3UYoJ5KadCbOf5axPg+a4O0z6jVQUbxhmWBND4QeAjYEgohFpk/x7Au6EkeMDfZUYX0D0q+kjwynaPSoQqhbklte7Q3/yuc7PGMoJGLbRFp/mUcN; 25:wZT1mbsvrFdvZZdTbuPisoMHYcEBVRhl5RcMnNsd/yA2AsHKMUrAXOujb/dcvGExmjeHqe8UiR15BEy2Qnh41NMVFrxe3DeMS98o0Q2bP4YZT+kIhj/235qSZP9ypaL30P2JnKHWn178mmFuAFy4tMHmJDC3rAmDTpZGKedXfJi5+BRvNFh0hFQgTc6MNDeJ+mcfBoa1B4A7gE4RNdgZtQ6oIzDeDpeFbPMdMhZsXyZQotpiGSrj06OMfvauk5bZjOT4Atf47AkOVJgSsGdt4oiCbSkFYz3rO5pYseIh8oIJvV2YTOFTWB4NGQrefZ6nRmFGNy1fl+lJb9doCOBpcA==
X-Microsoft-Antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:SN1PR0601MB1568;
X-LD-Processed: 89f84dfb-7285-4810-bc4d-8b9b5794554f,ExtAddr
X-Microsoft-Exchange-Diagnostics: 1; SN1PR0601MB1568; 20:GnNRCvnPwcuFSK1+Q5Gvey3CwOb7gG8ncrxjbdU70SwsOFntmf0+FWbHeT+flg75qJlLMU+nT0241LF4GF5SGeyyh8nhe8NDhd47NBF/Pg1zm+05oOHyCVnWdRLiZXZqIRqBcte+Ck8ds09soa9BuwoLUweB1Y5aXQSDOXs9ScQh01OBOalAAOb/zKFQqdSRsPUmgDVAvmeuNNWcBvhU8Yl/ajX7g53bSSUtlXEu1DNmpXH5a/Vynef34/VrIqAKfSELgyZ4548qi61TQ4KHz97CQ7h20bGl2oocqp6J+eG4Xz7GZS4dPtjkDcAnz8v0Gdn0wEEmsFcmFbP0hq9qMeFU/gABX/WeQji6j3Rjs99W+vg3OosQ1OHuWAjlrzcfOUGo7KE1ptpkNi05jD0IXz3FDzS0YRkt09vWwM/Te+zkS9iUjTIwl1oMPX530MMIouOuBaU3JesA6PYZqYkYBv3k76TuB8JbZlXvBhJDXmN0/n0T1nlSXXu+4WmCUq0y; 4:cwAgfaejlDay3qWAkKMgq3i2sDuaF4GqhaTMUkHi/fjLUEJS66Kk4d/fPSoUHDz3tl3aDy+A+CRB/N15vp/budISl8FB97o5bbaRhpn4SeX3Kgv1/nISOwyQ9SU/9kpd0HjL7+iO1DzUOcHpY/KiKguorOFZzfMIwu+bE9e6O7tCOK8aw615LzaZszc9dJOCHdUUzQVqrhZTMwu/Nmkbt0vZHCGa10YqmOacSF9K/5kkNQXro0K4uLn9et6MApRN6kXE575HLAls3gPAQpsRPNa8ntbDaAQUnOjniWwFOxr0tBOlyXVOjBuTG8B2BwKquufLOMEMhgsGd3UnqOwsRA8Ncno0EaAwD1pYFG7VfTWLGKPupausrujzZc4JatjD
X-Microsoft-Antispam-PRVS: <SN1PR0601MB1568518017BC036DFE6D8558B0910@SN1PR0601MB1568.namprd06.prod.outlook.com>
X-Exchange-Antispam-Report-Test: UriScan:;
X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(601004)(2401047)(8121501046)(5005006)(10201501046)(3002001); SRVR:SN1PR0601MB1568; BCL:0; PCL:0; RULEID:; SRVR:SN1PR0601MB1568; 
X-Forefront-PRVS: 0906E83A25
X-Forefront-Antispam-Report: SFV:NSPM; SFS:(10009020)(4630300001)(6009001)(377454003)(24454002)(23676002)(42186005)(33656002)(2906002)(57306001)(3846002)(4326007)(92566002)(6116002)(586003)(189998001)(110136002)(81166005)(3480700003)(221733001)(1096002)(83716003)(5008740100001)(19580395003)(50986999)(86362001)(66066001)(47776003)(76176999)(77096005)(19580405001)(2950100001)(82746002)(36756003)(50466002)(93886004)(50226001)(5004730100002)(7099028)(104396002); DIR:OUT; SFP:1101; SCL:1; SRVR:SN1PR0601MB1568; H:dhcp-b48d.meeting.ietf.org;  FPR:; SPF:None; MLV:sfv; LANG:en; 
X-Microsoft-Exchange-Diagnostics: =?utf-8?B?MTtTTjFQUjA2MDFNQjE1Njg7MjM6Y0NycVBQZno3VVFuTWk0MU1ybmVRSmJs?= =?utf-8?B?SWRYMkVCZEhmSTZ3cUhsRHJBcXFuZW8yVlM1NzRtdGpGbmRveDluYlN0SWZE?= =?utf-8?B?YVRacVVrdkxYM3B4N2gwZXdwUGVMSC9GNUpFSzhxVTNyZWo4RFZnV1VQSUhI?= =?utf-8?B?NURjWm1INEpieGVocTNnNWM3SzFJUXMyM090M0VOc0ZPRlAzM0NsMGE4ZVFK?= =?utf-8?B?dHBHK3ozTlRlKzltcjlQNDNZcDQvYXlhN1BZbHlwcjVlY1JrUVRyU0UwV2Fq?= =?utf-8?B?K280VVBqNHVReTY3RDY3bWdWY1FZbkFPOGY1RFgzRnpGT1l0N1Y0TzBOTFAv?= =?utf-8?B?azlBUzZCVGNFakl5elgzSTJwS3RyeGlHMmowd2lhRTlOMEhjUXBCM1R0bjB2?= =?utf-8?B?dzZ0WXBMRkwrMEl6aDJjVmIwT0pLL2Z5R0dLOEVhYXFjU2tKaGIrQ2V4eWVY?= =?utf-8?B?WDFXNjVNb29YWnFvcGFHcnRDWG1QR2QzaURPSlRZNFdlZGFoTEFFMDRId2ps?= =?utf-8?B?ZFZMT3d0VUpSTmo3VlFxdEhwSWxQb3RPZndpcG1ZcHNtK1N5Y0s3d25haE5m?= =?utf-8?B?QU5XQ0JTTnNVbWp0clRDcHd6S2pwalN6dXJwVzJJaE5meFNiTXNKL3BUMEQx?= =?utf-8?B?QUxpQlBLOWVVakpIdkh2UGRTZEpVN1pwS0IwYitsRTJmaks5ckt3UWpzblZi?= =?utf-8?B?WFVKaGl3ajRZK0IwUWlyRnZodWlMMDR4NEhrN0xPV2szUUNLRC9Ic3BMbzdS?= =?utf-8?B?RzFTOWRVdmZGb3N0MGFsQXNSbDRjNXZ4ancvbTZYWEMvT1BvVS9CYkhIYUxu?= =?utf-8?B?VG9hem5hc252WG5wakl4V1NRQml3UmkxZEkxUXhQd3QxTDlhdnlxOEM4eTY3?= =?utf-8?B?cTJZZVdlRytYemZPNG51UEdpVkdvMHJHdWZsSkp5WUw1TEc4U0s1ZTdlNnQv?= =?utf-8?B?VGFyRm9PMDM0bTdOQ3N4U3pmNlNwKytaL0ttdEN0b3ZkaVRFZml1TmdVVysx?= =?utf-8?B?Q1JJZWlkZUlrU05pNkFDTXAvS3BmZWd6clNtcnFjZzBZM2doVmVMZjZobE9s?= =?utf-8?B?Mndyc2Y5TkQyTlNvdVRLS3ZSTEJvR2Q3L0crbDRlYmhuYjdlODBNRmJDZjIw?= =?utf-8?B?V1VPNjc1eTg3STF3Q29FR2xCWEQ3eTQzNW5KTVZ1M2tWTWcrOC9HSDZ4NGlr?= =?utf-8?B?azV1Q0N6MzQ2NmR2czJkQlVxSXQybGErSEtCRHAvOXV3dXpNMGRCTEhSaGdS?= =?utf-8?B?MC9IM20xZnBSK01sdVluV2pzOHdXNCs4WDRVSEZWL1hRaUVXUWVNMWhseHl1?= =?utf-8?B?bDN3MXliUTA5cDFzN0NqcWFLREFOQ0EzM0RzdWZsRW41UkhxREUydklEM25L?= =?utf-8?B?SnozaWN5WDFlUDAwZXk2cmZPYUI3K1dqNWtnU21hMlE9PQ==?=
X-Microsoft-Exchange-Diagnostics: 1; SN1PR0601MB1568; 5:ZPHwaC4Yd9/ZdlHTCpk2B6+A1xO8HM9qDIDtNLBf9m8edk+t223aytt00VerFtGmbspRqQV9oys2elv0Z+lzRRKo7UzRNONxak4sdii/I6MCT466Hj/G/rnanFioTPHFlHwZO8mOxWVCB72zQkrAhw==; 24:TkfUobYUE4S8l7CEcN7ulWL4Xol2VTiTeokNRqBVxXI/EvGlMjFjLPxaaWKOgHMmZwJikhPNfPcYoDhIWPToCtYIrOf6u2nXGnWzgj/GrWA=
SpamDiagnosticOutput: 1:23
SpamDiagnosticMetadata: NSPM
X-OriginatorOrg: isoc.org
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 08 Apr 2016 15:49:08.5489 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-Transport-CrossTenantHeadersStamped: SN1PR0601MB1568
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/1rDIs-xcDs6QSWhpEjsANCdUdsk>
Cc: Michael Richardson <mcr+ietf@sandelman.ca>, "ietf@ietf.org 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: Fri, 08 Apr 2016 15:49:37 -0000

Tim,

> On Apr 8, 2016, at 12:34 PM, Tim Chown <tjc@ecs.soton.ac.uk> wrote:
>=20
> On 8 Apr 2016, at 16:14, Scott Bradner <sob@sobco.com> wrote:
>>=20
>> some on the IAOC wanted to go back to SD for IETF 100 but the =
facilities were not available=20
>> at the right time
>=20
> Ah, I was expecting the plenary drumroll to reveal just this - IETF100 =
at San Diego.=20
>=20
> A shame it couldn't happen, but perhaps an indicator we do need to =
keep planning 3-4 years out.
>=20
> And for the right venue, we should be able to slide the dates =
forwards/back a week or two.=20

We aggressively pursued venues in San Diego, including the possibly of =
shifting dates before=20
and after the scheduled calendar dates.  The rule is we don=E2=80=99t =
change those dates, but there
was a willingness to consider that for IETF 100. =20

San Diego is one of the most popular venues in the US, so it turned out =
that around our dates=20
there were already city-wide events that made it impossible to secure a =
venue and necessary=20
overflow hotels.

Ray

>=20
> Tim
>=20
>>=20
>> Scott
>>=20
>>> On Apr 8, 2016, at 10:38 AM, Michael Richardson =
<mcr+ietf@sandelman.ca> wrote:
>>>=20
>>>=20
>>> Ole Jacobsen <olejacobsen@me.com> wrote:
>>>> I am sorry to hear that. Our "open and inclusive process" comprises
>>>> many participants from China who have traditionally faced harsh and
>>>> unpredictable visa problems in North America. In fairness to them, =
we
>>>> held that meeting in Beijing. Note that we did so following an
>>>> extensive discussion on the IETF mailing list and after negotiating
>>>> the removal of a rather ominous hotel clause, as well as an =
unfiltered
>>>> network in the meeting venue.
>>>=20
>>> Yes, and we did this openly, and I don't feel we did the same thing =
here.
>>> And there were still surprises, I'm told.
>>>=20
>>> I was very surprised at the announcement for 100.
>>> I kinda thought we should go back to San Diego as for IETF 1.
>>> (well. Maybe IETF101 should be same as IETF 1... maybe IETF 100 =
should be
>>> same as IETF 0, and be entirely virtual...)
>>>=20
>>> (I didn't go because I generally have funds for two IETFs a year,
>>> and given the hassle, and my concerns about what I would eat, it was =
simpler
>>> to skip.  I skipped BA for a combination of economic, but primarily =
family reasons)
>>>=20
>>>=20
>>> --
>>> Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
>>> -=3D IPv6 IoT consulting =3D-
>>>=20
>>>=20
>>>=20
>>=20
>=20


From nobody Fri Apr  8 09:01:32 2016
Return-Path: <mary.h.barnes@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 AFEC812D1B3 for <ietf@ietfa.amsl.com>; Fri,  8 Apr 2016 09:01:29 -0700 (PDT)
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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 mbhGukM-_uDJ for <ietf@ietfa.amsl.com>; Fri,  8 Apr 2016 09:01:27 -0700 (PDT)
Received: from mail-yw0-x235.google.com (mail-yw0-x235.google.com [IPv6:2607:f8b0:4002:c05::235]) (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 BC78A12D1AB for <ietf@ietf.org>; Fri,  8 Apr 2016 09:01:27 -0700 (PDT)
Received: by mail-yw0-x235.google.com with SMTP id t10so139785704ywa.0 for <ietf@ietf.org>; Fri, 08 Apr 2016 09:01:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=2d6dlVnW//E1yTDVbjk6+eejdmucOp2ynAz3MCIUeqw=; b=Goi2CZmAEqutQXhfYtL41xxBrtCmjxpaHjwzgHtZbPJaZStetdycrdVt5bHI8wfBTv 3VptOg57bhfpbs1QCcLiKi1yU0SC19t4FNXuP3skSzPZSeateNTRqyOMrx1orb/5d5I4 /dWYeVLZPxXS9S0/YaCTtSuuwxtQiad+ee4NAvcoCHTuqxjyp5Rli4SzhPLli9thIhCp yiNphyOBAoWCVM+zOh4bRXOeP40zlQnJHdgcoUPyBKQFCzqIQuo4GYnhm4p2+DQfICiB lnx477V2PhatZCk2OJvRllkA0Im1DLlRFoGi7NRCB7Rw1Wkc9YMTl248T0qQNgjgTg4C Mhqg==
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:date :message-id:subject:from:to:cc; bh=2d6dlVnW//E1yTDVbjk6+eejdmucOp2ynAz3MCIUeqw=; b=PsO8QPVtafJM/yinf2zDjWDinHAM7AUEwivliMKKpEOoJgmzBIL1WGCrPB6E8jQ1DH DmS5u7rFCUsnmvCzhfPTntq5brS2W8nXrHnPDfNx0zK5f9eSns9u3vRw4vwdsh2je1kU iWW7TqrstEWMpMhv87T6yhdls8nmUBW76/7KqJJ0GFas/Jq2V7/utmC8INpNSnjbK1Pn yoZlC1u/OMf6BAos1p9sUe5iuRU06H/1GTutl/ac+3TdYs4CWqON3Y4EhGjuYWMVx4gi pOkLELf+zgGvejPmhOQFIXWcy+TpWHIpjSh1KWzeWEyIWnxVX/hqQQCqASEkbC71QU/k gnQw==
X-Gm-Message-State: AD7BkJJ1sNbFKTHOneJ01ak2aHBM+hCSBbHs5yLKAG6XvkEyb3aUhm3/mUrr7OnXhWpi8hv86MwJEv/lWEY7Hg==
MIME-Version: 1.0
X-Received: by 10.37.230.84 with SMTP id d81mr5170849ybh.121.1460131287013; Fri, 08 Apr 2016 09:01:27 -0700 (PDT)
Received: by 10.37.63.197 with HTTP; Fri, 8 Apr 2016 09:01:26 -0700 (PDT)
In-Reply-To: <31709.1460126336@obiwan.sandelman.ca>
References: <0D914666-C3D4-4CCE-AD5E-4E5B34EA1A73@piuha.net> <20160407182936.GA21340@pfrc.org> <CAB75xn780nNDjGa_Cc222J20-+1CCHt09Xp8KHzaK=n0xx51pg@mail.gmail.com> <5706B100.9040509@mnt.se> <CAB75xn6fmj84ROUtG5eUB3GerHx83hrEr3w5vSADY_g=BRg5FA@mail.gmail.com> <5706BA40.3060005@mnt.se> <alpine.DEB.2.02.1604072157240.31096@uplift.swm.pp.se> <A9B63A6D-3102-482F-8FFC-2E57A5FD8336@nic.cz> <CC16B445-2B74-4182-BC58-F9D4BFFA1CCF@chopps.org> <alpine.OSX.2.01.1604080420470.36488@rabdullah.local> <31709.1460126336@obiwan.sandelman.ca>
Date: Fri, 8 Apr 2016 11:01:26 -0500
Message-ID: <CABmDk8mL1w8WvgL7WGXRWFrt9q4mAca3wZ-rHuntBtcP0_1-vA@mail.gmail.com>
Subject: Re: China
From: Mary Barnes <mary.h.barnes@gmail.com>
To: Michael Richardson <mcr+ietf@sandelman.ca>
Content-Type: multipart/alternative; boundary=94eb2c0b1c26b025a1052ffb4ef5
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/BSewIAXlS02wDIMrx4vgHxG_wwc>
Cc: "ietf@ietf.org 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: Fri, 08 Apr 2016 16:01:29 -0000

--94eb2c0b1c26b025a1052ffb4ef5
Content-Type: text/plain; charset=UTF-8

On Fri, Apr 8, 2016 at 9:38 AM, Michael Richardson <mcr+ietf@sandelman.ca>
wrote:

>
> Ole Jacobsen <olejacobsen@me.com> wrote:
>     > I am sorry to hear that. Our "open and inclusive process" comprises
>     > many participants from China who have traditionally faced harsh and
>     > unpredictable visa problems in North America. In fairness to them, we
>     > held that meeting in Beijing. Note that we did so following an
>     > extensive discussion on the IETF mailing list and after negotiating
>     > the removal of a rather ominous hotel clause, as well as an
> unfiltered
>     > network in the meeting venue.
>
> Yes, and we did this openly, and I don't feel we did the same thing here.
> And there were still surprises, I'm told.
>
> I was very surprised at the announcement for 100.
> I kinda thought we should go back to San Diego as for IETF 1.
> (well. Maybe IETF101 should be same as IETF 1... maybe IETF 100 should be
> same as IETF 0, and be entirely virtual...)
>
> (I didn't go because I generally have funds for two IETFs a year,
> and given the hassle, and my concerns about what I would eat, it was
> simpler
> to skip.  I skipped BA for a combination of economic, but primarily family
> reasons)
>
[MB] You would have had no concerns whatsoever about what to eat in
Beijing.  I ended up with basically a private chef (Chef Eric) who I would
ask for when I went to eat at the hotel restaurant and he would prepare
whatever I wanted (gluten free). Although, I honestly have no desire
whatsoever to go back to Beijing due to the air quality - we got really
lucky the week we were there - you could actually see mountains.[/MB]

>
>
> --
> Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
>  -= IPv6 IoT consulting =-
>
>
>
>

--94eb2c0b1c26b025a1052ffb4ef5
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On F=
ri, Apr 8, 2016 at 9:38 AM, Michael Richardson <span dir=3D"ltr">&lt;<a hre=
f=3D"mailto:mcr+ietf@sandelman.ca" target=3D"_blank">mcr+ietf@sandelman.ca<=
/a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:=
0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=3D""><b=
r>
Ole Jacobsen &lt;<a href=3D"mailto:olejacobsen@me.com">olejacobsen@me.com</=
a>&gt; wrote:<br>
=C2=A0 =C2=A0 &gt; I am sorry to hear that. Our &quot;open and inclusive pr=
ocess&quot; comprises<br>
=C2=A0 =C2=A0 &gt; many participants from China who have traditionally face=
d harsh and<br>
=C2=A0 =C2=A0 &gt; unpredictable visa problems in North America. In fairnes=
s to them, we<br>
=C2=A0 =C2=A0 &gt; held that meeting in Beijing. Note that we did so follow=
ing an<br>
=C2=A0 =C2=A0 &gt; extensive discussion on the IETF mailing list and after =
negotiating<br>
=C2=A0 =C2=A0 &gt; the removal of a rather ominous hotel clause, as well as=
 an unfiltered<br>
=C2=A0 =C2=A0 &gt; network in the meeting venue.<br>
<br>
</span>Yes, and we did this openly, and I don&#39;t feel we did the same th=
ing here.<br>
And there were still surprises, I&#39;m told.<br>
<br>
I was very surprised at the announcement for 100.<br>
I kinda thought we should go back to San Diego as for IETF 1.<br>
(well. Maybe IETF101 should be same as IETF 1... maybe IETF 100 should be<b=
r>
same as IETF 0, and be entirely virtual...)<br>
<br>
(I didn&#39;t go because I generally have funds for two IETFs a year,<br>
and given the hassle, and my concerns about what I would eat, it was simple=
r<br>
to skip.=C2=A0 I skipped BA for a combination of economic, but primarily fa=
mily reasons)<br></blockquote><div>[MB] You would have had no concerns what=
soever about what to eat in Beijing.=C2=A0 I ended up with basically a priv=
ate chef (Chef Eric) who I would ask for when I went to eat at the hotel re=
staurant and he would prepare whatever I wanted (gluten free). Although, I =
honestly have no desire whatsoever to go back to Beijing due to the air qua=
lity - we got really lucky the week we were there - you could actually see =
mountains.[/MB]=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margi=
n:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
<br>
--<br>
Michael Richardson &lt;<a href=3D"mailto:mcr%2BIETF@sandelman.ca">mcr+IETF@=
sandelman.ca</a>&gt;, Sandelman Software Works<br>
=C2=A0-=3D IPv6 IoT consulting =3D-<br>
<br>
<br>
<br>
</blockquote></div><br></div></div>

--94eb2c0b1c26b025a1052ffb4ef5--


From nobody Fri Apr  8 09:38:12 2016
Return-Path: <mrex@sap.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 4BC8412D969 for <ietf@ietfa.amsl.com>; Fri,  8 Apr 2016 09:38:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.921
X-Spam-Level: 
X-Spam-Status: No, score=-6.921 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] 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 IQ9y_Yu6KoOf for <ietf@ietfa.amsl.com>; Fri,  8 Apr 2016 09:38:08 -0700 (PDT)
Received: from smtpde01.smtp.sap-ag.de (smtpde01.smtp.sap-ag.de [155.56.68.170]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AC09912D967 for <ietf@ietf.org>; Fri,  8 Apr 2016 09:38:08 -0700 (PDT)
Received: from mail05.wdf.sap.corp (mail05.sap.corp [194.39.131.55]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtpde01.smtp.sap-ag.de (Postfix) with ESMTPS id 8BFB22B1BA; Fri,  8 Apr 2016 18:38:06 +0200 (CEST)
X-purgate-ID: 152705::1460133486-000073AB-8FDEE741/0/0
X-purgate-size: 710
X-purgate: clean
X-purgate: This mail is considered clean (visit http://www.eleven.de for further information)
X-purgate-Ad: Categorized by eleven eXpurgate (R) http://www.eleven.de
X-purgate-type: clean
X-SAP-SPAM-Status: clean
Received: from ld9781.wdf.sap.corp (ld9781.wdf.sap.corp [10.21.82.193]) by mail05.wdf.sap.corp (Postfix) with ESMTP id C79AC40F1F; Fri,  8 Apr 2016 18:38:05 +0200 (CEST)
Received: by ld9781.wdf.sap.corp (Postfix, from userid 10159) id 9E46C1A48A; Fri,  8 Apr 2016 18:38:05 +0200 (CEST)
Subject: Re: SV: Concerns about Singapore
In-Reply-To: <55791011d19e40a792999c45b571ecc2@exchange02.office.nic.se>
To: =?ISO-8859-1?Q?Anne-Marie_Eklund-L=F6winder?= <anne-marie.eklund-lowinder@iis.se>
Date: Fri, 8 Apr 2016 18:38:05 +0200 (CEST)
X-Mailer: ELM [version 2.4ME+ PL125 (25)]
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="ISO-8859-1"
Message-Id: <20160408163805.9E46C1A48A@ld9781.wdf.sap.corp>
From: mrex@sap.com (Martin Rex)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/kPE8VjkPGAHIPl6rWO1WaUfVFKU>
Cc: "ietf@ietf.org Discussion" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: mrex@sap.com
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: Fri, 08 Apr 2016 16:38:11 -0000

Anne-Marie Eklund-L=F6winder wrote:
>=20
> Well, if you start to dance spontaneously on a restaurant in Sweden
> you are in trouble. It's a law against that.
>=20
> The law is from the 1920ies or so. No one bothered to change it.

IETF 83rd was in Paris, France, March 25-30, 2012

At that time there still was a law on the books that women
walking in public in Paris in trousers/pants (rather than dress or skirt)
could be taken into custody by the police.

http://www.telegraph.co.uk/news/worldnews/europe/france/9845545/Women-in-Pa=
ris-finally-allowed-to-wear-trousers.html

Did any women wearing pants in public during IETF 83rd in Paris
got taken into custody by the police?

-Martin


From nobody Fri Apr  8 10:34:34 2016
Return-Path: <dhc@dcrocker.net>
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 1555F12D0E4 for <ietf@ietfa.amsl.com>; Fri,  8 Apr 2016 10:34:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] 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 Y-zET3RsMrZj for <ietf@ietfa.amsl.com>; Fri,  8 Apr 2016 10:34:30 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5878912D102 for <ietf@ietf.org>; Fri,  8 Apr 2016 10:34:29 -0700 (PDT)
Received: from [192.168.1.168] (76-218-10-206.lightspeed.sntcca.sbcglobal.net [76.218.10.206]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id u38HYPFO027937 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Fri, 8 Apr 2016 10:34:26 -0700
Subject: Re: Concerns about Singapore
To: Yoav Nir <ynir.ietf@gmail.com>, Andrew Allen <aallen@blackberry.com>
References: <CAB75xn6fmj84ROUtG5eUB3GerHx83hrEr3w5vSADY_g=BRg5FA@mail.gmail.com> <1481689286.47880.1460111891664.JavaMail.yahoo@mail.yahoo.com> <alpine.OSX.2.01.1604080418530.36488@rabdullah.local> <594.1460126622@obiwan.sandelman.ca> <5707C458.7080107@dcrocker.net> <20160408150512.6283348.55871.10388@blackberry.com> <A9E6E707-86DD-4E4A-BD5C-A7B0D6E40398@gmail.com>
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
Message-ID: <5707EB9E.7030006@dcrocker.net>
Date: Fri, 8 Apr 2016 10:34:22 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2
MIME-Version: 1.0
In-Reply-To: <A9E6E707-86DD-4E4A-BD5C-A7B0D6E40398@gmail.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Fri, 08 Apr 2016 10:34:26 -0700 (PDT)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/I6wrl7OTlsFZRFNQKaal_JsqCpE>
Cc: Michael Richardson <mcr@sandelman.ca>, "ietf@ietf.org Discussion" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: dcrocker@bbiw.net
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: Fri, 08 Apr 2016 17:34:32 -0000

On 4/8/2016 8:30 AM, Yoav Nir wrote:
> And I can’t enter Malaysia at all.


In practical terms, that's mostly correct.  In formal terms, it's not.

The Meetings Committee looked carefully at Malaysia's formal 
requirements for an Israeli to get a Visa.  There /is/ a procedure.  But 
it's quite onerous and far beyond anything we felt tolerable for an IETF 
meeting.

However I also know of cases in which the MY gov't has expedited access 
for Israelis, but it was a special and big deal and, again, 
inappropriate for the IETF to pursue, IMO.


d/

-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net


From nobody Fri Apr  8 10:36:42 2016
Return-Path: <tony@att.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 89BCB12D6AD for <ietf@ietfa.amsl.com>; Fri,  8 Apr 2016 10:36:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.579
X-Spam-Level: 
X-Spam-Status: No, score=-1.579 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, MISSING_HEADERS=1.021, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001] autolearn=no 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 rJYRzt-3RaFr for <ietf@ietfa.amsl.com>; Fri,  8 Apr 2016 10:36:39 -0700 (PDT)
Received: from mx0a-00191d01.pphosted.com (mx0a-00191d01.pphosted.com [67.231.149.140]) (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 85A8712D1CC for <ietf@ietf.org>; Fri,  8 Apr 2016 10:36:39 -0700 (PDT)
Received: from pps.filterd (m0048589.ppops.net [127.0.0.1]) by m0048589.ppops.net-00191d01. (8.15.0.59/8.15.0.59) with SMTP id u38GDqPj026234 for <ietf@ietf.org>; Fri, 8 Apr 2016 12:15:42 -0400
Received: from alpi155.enaf.aldc.att.com (sbcsmtp7.sbc.com [144.160.229.24]) by m0048589.ppops.net-00191d01. with ESMTP id 226f8gh8d4-1 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for <ietf@ietf.org>; Fri, 08 Apr 2016 12:15:42 -0400
Received: from enaf.aldc.att.com (localhost [127.0.0.1]) by alpi155.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id u38GFfsV026630 for <ietf@ietf.org>; Fri, 8 Apr 2016 12:15:41 -0400
Received: from mlpi408.sfdc.sbc.com (mlpi408.sfdc.sbc.com [130.9.128.240]) by alpi155.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id u38GFXZh026443 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for <ietf@ietf.org>; Fri, 8 Apr 2016 12:15:36 -0400
Received: from MISOUT7MSGHUBAF.ITServices.sbc.com (MISOUT7MSGHUBAF.itservices.sbc.com [130.9.129.150]) by mlpi408.sfdc.sbc.com (RSA Interceptor) for <ietf@ietf.org>; Fri, 8 Apr 2016 16:15:16 GMT
Received: from MISOUT7MSGUSRCG.ITServices.sbc.com ([169.254.7.206]) by MISOUT7MSGHUBAF.ITServices.sbc.com ([130.9.129.150]) with mapi id 14.03.0248.002; Fri, 8 Apr 2016 12:15:15 -0400
From: "HANSEN, TONY L" <tony@att.com>
CC: "ietf@ietf.org Discussion" <ietf@ietf.org>
Subject: Re: China
Thread-Topic: China
Thread-Index: AQHRkYncC5j6ufsgwUmk6wltwlp1up+AaLwAgAAXDQD//8DOgA==
Date: Fri, 8 Apr 2016 16:15:15 +0000
Message-ID: <116E482F-641C-4123-AB83-E6A96F5C724B@att.com>
References: <0D914666-C3D4-4CCE-AD5E-4E5B34EA1A73@piuha.net> <20160407182936.GA21340@pfrc.org> <CAB75xn780nNDjGa_Cc222J20-+1CCHt09Xp8KHzaK=n0xx51pg@mail.gmail.com> <5706B100.9040509@mnt.se> <CAB75xn6fmj84ROUtG5eUB3GerHx83hrEr3w5vSADY_g=BRg5FA@mail.gmail.com> <5706BA40.3060005@mnt.se> <alpine.DEB.2.02.1604072157240.31096@uplift.swm.pp.se> <A9B63A6D-3102-482F-8FFC-2E57A5FD8336@nic.cz> <CC16B445-2B74-4182-BC58-F9D4BFFA1CCF@chopps.org> <alpine.OSX.2.01.1604080420470.36488@rabdullah.local> <31709.1460126336@obiwan.sandelman.ca> <CABmDk8mL1w8WvgL7WGXRWFrt9q4mAca3wZ-rHuntBtcP0_1-vA@mail.gmail.com>
In-Reply-To: <CABmDk8mL1w8WvgL7WGXRWFrt9q4mAca3wZ-rHuntBtcP0_1-vA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.110.240.106]
Content-Type: multipart/alternative; boundary="_000_116E482F641C4123AB83E6A96F5C724Battcom_"
MIME-Version: 1.0
X-RSA-Inspected: yes
X-RSA-Classifications: public
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2016-04-08_09:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_policy_notspam policy=outbound_policy 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-1603180000 definitions=main-1604080240
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/9QVZ2_u1ccXWtfKJNBaZXZSItcY>
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: Fri, 08 Apr 2016 17:36:40 -0000

--_000_116E482F641C4123AB83E6A96F5C724Battcom_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

SSBzdGF5ZWQgdGhlIHdlZWsgYWZ0ZXIgdGhlIEJlaWppbmcgbWVldGluZy4gVGhlIGRheSB3ZSBs
ZWZ0IHdhcyB0aGUgZmlyc3QgZGF5IHRoZSBhaXIgcXVhbGl0eSBtZWFzdXJlcyB3ZW50IG9mZiB0
aGUgY2hhcnRzIGZvciB0aGUgaW5zdHJ1bWVudHMgdGhhdCB3ZXJlIGJlaW5nIHVzZWQgYXQgdGhh
dCB0aW1lLiBJIHdhcyBkaXNhcHBvaW50ZWQgYnkgaG93IHdpbmR5IGl0IHdhcyB0aGUgZGF5IHdl
IHdlbnQgdG8gdGhlIEZvcmJpZGRlbiBDaXR5LCBidXQgbGF0ZXIgZGVjaWRlZCB0aGF0IGl0IHdh
cyBhIHJlYWxseSBnb29kIHRoaW5nIGJlY2F1c2UgdGhlIGFpciBxdWFsaXR5IHdhcyBzbyBtdWNo
IGJldHRlci4NCg0KVG9ueQ0KDQpGcm9tOiBpZXRmIDxpZXRmLWJvdW5jZXNAaWV0Zi5vcmc8bWFp
bHRvOmlldGYtYm91bmNlc0BpZXRmLm9yZz4+IG9uIGJlaGFsZiBvZiBNYXJ5IEJhcm5lcyA8bWFy
eS5oLmJhcm5lc0BnbWFpbC5jb208bWFpbHRvOm1hcnkuaC5iYXJuZXNAZ21haWwuY29tPj4NCkRh
dGU6IEZyaWRheSwgQXByaWwgOCwgMjAxNiBhdCAxMjowMSBQTQ0KVG86IE1pY2hhZWwgUmljaGFy
ZHNvbiA8bWNyK2lldGZAc2FuZGVsbWFuLmNhPG1haWx0bzptY3IraWV0ZkBzYW5kZWxtYW4uY2E+
Pg0KQ2M6ICJpZXRmQGlldGYub3JnPG1haWx0bzppZXRmQGlldGYub3JnPiBEaXNjdXNzaW9uIiA8
aWV0ZkBpZXRmLm9yZzxtYWlsdG86aWV0ZkBpZXRmLm9yZz4+DQpTdWJqZWN0OiBSZTogQ2hpbmEN
Cg0KTUJdIOKApiBBbHRob3VnaCwgSSBob25lc3RseSBoYXZlIG5vIGRlc2lyZSB3aGF0c29ldmVy
IHRvIGdvIGJhY2sgdG8gQmVpamluZyBkdWUgdG8gdGhlIGFpciBxdWFsaXR5IC0gd2UgZ290IHJl
YWxseSBsdWNreSB0aGUgd2VlayB3ZSB3ZXJlIHRoZXJlIC0geW91IGNvdWxkIGFjdHVhbGx5IHNl
ZSBtb3VudGFpbnMuWy9NQl0NCg==

--_000_116E482F641C4123AB83E6A96F5C724Battcom_
Content-Type: text/html; charset="utf-8"
Content-ID: <70B689C1E1733040A425823F446FC6A4@LOCAL>
Content-Transfer-Encoding: base64

PGh0bWw+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIgY29udGVudD0i
dGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjwvaGVhZD4NCjxib2R5IHN0eWxlPSJ3b3JkLXdy
YXA6IGJyZWFrLXdvcmQ7IC13ZWJraXQtbmJzcC1tb2RlOiBzcGFjZTsgLXdlYmtpdC1saW5lLWJy
ZWFrOiBhZnRlci13aGl0ZS1zcGFjZTsgY29sb3I6IHJnYigwLCAwLCAwKTsgZm9udC1zaXplOiAx
NHB4OyBmb250LWZhbWlseTogQ2FsaWJyaSwgc2Fucy1zZXJpZjsiPg0KPGRpdj4NCjxkaXY+DQo8
ZGl2Pkkgc3RheWVkIHRoZSB3ZWVrIGFmdGVyIHRoZSBCZWlqaW5nIG1lZXRpbmcuIFRoZSBkYXkg
d2UgbGVmdCB3YXMgdGhlIGZpcnN0IGRheSB0aGUgYWlyIHF1YWxpdHkgbWVhc3VyZXMgd2VudCBv
ZmYgdGhlIGNoYXJ0cyBmb3IgdGhlIGluc3RydW1lbnRzIHRoYXQgd2VyZSBiZWluZyB1c2VkIGF0
IHRoYXQgdGltZS4gSSB3YXMgZGlzYXBwb2ludGVkIGJ5IGhvdyB3aW5keSBpdCB3YXMgdGhlIGRh
eSB3ZSB3ZW50IHRvIHRoZSBGb3JiaWRkZW4gQ2l0eSwNCiBidXQgbGF0ZXIgZGVjaWRlZCB0aGF0
IGl0IHdhcyBhIHJlYWxseSBnb29kIHRoaW5nIGJlY2F1c2UgdGhlIGFpciBxdWFsaXR5IHdhcyBz
byBtdWNoIGJldHRlci48L2Rpdj4NCjxkaXY+PGJyPg0KPC9kaXY+DQo8ZGl2PjxzcGFuIGNsYXNz
PSJBcHBsZS10YWItc3BhbiIgc3R5bGU9IndoaXRlLXNwYWNlOnByZSI+PC9zcGFuPlRvbnk8L2Rp
dj4NCjxkaXY+DQo8ZGl2IGlkPSJNQUNfT1VUTE9PS19TSUdOQVRVUkUiPjwvZGl2Pg0KPC9kaXY+
DQo8L2Rpdj4NCjwvZGl2Pg0KPGRpdj48YnI+DQo8L2Rpdj4NCjxzcGFuIGlkPSJPTEtfU1JDX0JP
RFlfU0VDVElPTiI+DQo8ZGl2IHN0eWxlPSJmb250LWZhbWlseTpDYWxpYnJpOyBmb250LXNpemU6
MTJwdDsgdGV4dC1hbGlnbjpsZWZ0OyBjb2xvcjpibGFjazsgQk9SREVSLUJPVFRPTTogbWVkaXVt
IG5vbmU7IEJPUkRFUi1MRUZUOiBtZWRpdW0gbm9uZTsgUEFERElORy1CT1RUT006IDBpbjsgUEFE
RElORy1MRUZUOiAwaW47IFBBRERJTkctUklHSFQ6IDBpbjsgQk9SREVSLVRPUDogI2I1YzRkZiAx
cHQgc29saWQ7IEJPUkRFUi1SSUdIVDogbWVkaXVtIG5vbmU7IFBBRERJTkctVE9QOiAzcHQiPg0K
PHNwYW4gc3R5bGU9ImZvbnQtd2VpZ2h0OmJvbGQiPkZyb206IDwvc3Bhbj5pZXRmICZsdDs8YSBo
cmVmPSJtYWlsdG86aWV0Zi1ib3VuY2VzQGlldGYub3JnIj5pZXRmLWJvdW5jZXNAaWV0Zi5vcmc8
L2E+Jmd0OyBvbiBiZWhhbGYgb2YgTWFyeSBCYXJuZXMgJmx0OzxhIGhyZWY9Im1haWx0bzptYXJ5
LmguYmFybmVzQGdtYWlsLmNvbSI+bWFyeS5oLmJhcm5lc0BnbWFpbC5jb208L2E+Jmd0Ozxicj4N
CjxzcGFuIHN0eWxlPSJmb250LXdlaWdodDpib2xkIj5EYXRlOiA8L3NwYW4+RnJpZGF5LCBBcHJp
bCA4LCAyMDE2IGF0IDEyOjAxIFBNPGJyPg0KPHNwYW4gc3R5bGU9ImZvbnQtd2VpZ2h0OmJvbGQi
PlRvOiA8L3NwYW4+TWljaGFlbCBSaWNoYXJkc29uICZsdDs8YSBocmVmPSJtYWlsdG86bWNyJiM0
MztpZXRmQHNhbmRlbG1hbi5jYSI+bWNyJiM0MztpZXRmQHNhbmRlbG1hbi5jYTwvYT4mZ3Q7PGJy
Pg0KPHNwYW4gc3R5bGU9ImZvbnQtd2VpZ2h0OmJvbGQiPkNjOiA8L3NwYW4+JnF1b3Q7PGEgaHJl
Zj0ibWFpbHRvOmlldGZAaWV0Zi5vcmciPmlldGZAaWV0Zi5vcmc8L2E+IERpc2N1c3Npb24mcXVv
dDsgJmx0OzxhIGhyZWY9Im1haWx0bzppZXRmQGlldGYub3JnIj5pZXRmQGlldGYub3JnPC9hPiZn
dDs8YnI+DQo8c3BhbiBzdHlsZT0iZm9udC13ZWlnaHQ6Ym9sZCI+U3ViamVjdDogPC9zcGFuPlJl
OiBDaGluYTxicj4NCjwvZGl2Pg0KPGRpdj48YnI+DQo8L2Rpdj4NCjxkaXY+DQo8ZGl2Pg0KPGRp
diBkaXI9Imx0ciI+DQo8ZGl2IGNsYXNzPSJnbWFpbF9leHRyYSI+DQo8ZGl2IGNsYXNzPSJnbWFp
bF9xdW90ZSI+DQo8YmxvY2txdW90ZSBjbGFzcz0iZ21haWxfcXVvdGUiIHN0eWxlPSJtYXJnaW46
MCAwIDAgLjhleDtib3JkZXItbGVmdDoxcHggI2NjYyBzb2xpZDtwYWRkaW5nLWxlZnQ6MWV4Ij4N
CjxzcGFuIGNsYXNzPSIiPk1CXSDigKYgQWx0aG91Z2gsIEkgaG9uZXN0bHkgaGF2ZSBubyBkZXNp
cmUgd2hhdHNvZXZlciB0byBnbyBiYWNrIHRvIEJlaWppbmcgZHVlIHRvIHRoZSBhaXIgcXVhbGl0
eSAtIHdlIGdvdCByZWFsbHkgbHVja3kgdGhlIHdlZWsgd2Ugd2VyZSB0aGVyZSAtIHlvdSBjb3Vs
ZCBhY3R1YWxseSBzZWUgbW91bnRhaW5zLlsvTUJdJm5ic3A7PC9zcGFuPjwvYmxvY2txdW90ZT4N
CjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L3NwYW4+DQo8L2JvZHk+
DQo8L2h0bWw+DQo=

--_000_116E482F641C4123AB83E6A96F5C724Battcom_--


From nobody Fri Apr  8 10:50:34 2016
Return-Path: <olejacobsen@me.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 C34F912D13C for <ietf@ietfa.amsl.com>; Fri,  8 Apr 2016 10:50:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.631
X-Spam-Level: 
X-Spam-Status: No, score=-2.631 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 bKY6qrfvRnUF for <ietf@ietfa.amsl.com>; Fri,  8 Apr 2016 10:50:31 -0700 (PDT)
Received: from mr11p00im-asmtp004.me.com (mr11p00im-asmtp004.me.com [17.110.69.135]) (using TLSv1.2 with cipher DHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 851CD12D0FE for <ietf@ietf.org>; Fri,  8 Apr 2016 10:50:31 -0700 (PDT)
Received: from [10.1.10.8] (173-11-110-134-SFBA.hfc.comcastbusiness.net [173.11.110.134]) by mr11p00im-asmtp004.me.com (Oracle Communications Messaging Server 7.0.5.36.0 64bit (built Sep 8 2015)) with ESMTPSA id <0O5B00471TK2RR10@mr11p00im-asmtp004.me.com> for ietf@ietf.org; Fri, 08 Apr 2016 17:50:31 +0000 (GMT)
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, definitions=2016-04-08_09:,, signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 clxscore=1015 suspectscore=0 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1510270003 definitions=main-1604080262
Date: Fri, 08 Apr 2016 10:50:26 -0700 (PDT)
From: Ole Jacobsen <olejacobsen@me.com>
To: Yoav Nir <ynir.ietf@gmail.com>
Subject: Re: Concerns about Singapore
In-reply-to: <A9E6E707-86DD-4E4A-BD5C-A7B0D6E40398@gmail.com>
Message-id: <alpine.OSX.2.01.1604081047380.37683@rabdullah.local>
References: <CAB75xn6fmj84ROUtG5eUB3GerHx83hrEr3w5vSADY_g=BRg5FA@mail.gmail.com> <1481689286.47880.1460111891664.JavaMail.yahoo@mail.yahoo.com> <alpine.OSX.2.01.1604080418530.36488@rabdullah.local> <594.1460126622@obiwan.sandelman.ca> <5707C458.7080107@dcrocker.net> <20160408150512.6283348.55871.10388@blackberry.com> <A9E6E707-86DD-4E4A-BD5C-A7B0D6E40398@gmail.com>
User-Agent: Alpine 2.01 (OSX 1266 2009-07-14)
MIME-version: 1.0
Content-type: MULTIPART/MIXED; BOUNDARY="0-694377381-1460137831=:37683"
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/BRYZMcnW5dB8fPj_kfdY2Muubj8>
Cc: "ietf@ietf.org Discussion" <ietf@ietf.org>, Dave Crocker <dcrocker@bbiw.net>, Michael Richardson <mcr@sandelman.ca>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: Ole Jacobsen <olejacobsen@me.com>
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: Fri, 08 Apr 2016 17:50:33 -0000

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.

--0-694377381-1460137831=:37683
Content-Type: TEXT/PLAIN; charset=windows-1252
Content-Transfer-Encoding: 8BIT


On Fri, 8 Apr 2016, Yoav Nir wrote:

> And I can’t enter Malaysia at all.
> 

Not completely true, but the obstacles to entry are unfairly high
for your one country which is why we have no plans to go there until
that process is fully streamlined etc, and yes, we would ask the
community first :-)

Ole
--0-694377381-1460137831=:37683--


From nobody Fri Apr  8 11:08:58 2016
Return-Path: <dwm@xpasc.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 CE20C12D0EA for <ietf@ietfa.amsl.com>; Fri,  8 Apr 2016 11:08:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001] 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 CxlFpGmayK1X for <ietf@ietfa.amsl.com>; Fri,  8 Apr 2016 11:08:54 -0700 (PDT)
Received: from dispatch1-us1.ppe-hosted.com (dispatch1-us1.ppe-hosted.com [148.163.129.52]) (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 DC1E112D16E for <ietf@ietf.org>; Fri,  8 Apr 2016 11:08:53 -0700 (PDT)
Received: from mx1-us1.ppe-hosted.com (unknown [10.7.64.20]) by dispatch1-us1.ppe-hosted.com (Proofpoint Essentials ESMTP Server) with ESMTP id 4148420089 for <ietf@ietf.org>; Fri,  8 Apr 2016 18:08:53 +0000 (UTC)
X-Virus-Scanned: Proofpoint Essentials engine
Received: from xpasc.com (h-68-164-244-186.snva.ca.megapath.net [68.164.244.186]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by mx1-us1.ppe-hosted.com (Proofpoint Essentials ESMTP Server) with ESMTPS id DA62B10B for <ietf@ietf.org>; Fri,  8 Apr 2016 18:08:51 +0000 (UTC)
Received: from egate.xpasc.com (egate.xpasc.com [10.1.2.49]) by xpasc.com (8.13.8/8.13.8) with ESMTP id u38I8p6X005852 for <ietf@ietf.org>; Fri, 8 Apr 2016 11:08:51 -0700
Date: Fri, 8 Apr 2016 11:08:51 -0700 (PDT)
From: David Morris <dwm@xpasc.com>
To: ietf@ietf.org
Subject: Re: Concerns about Singapore
In-Reply-To: <5707C458.7080107@dcrocker.net>
Message-ID: <alpine.LRH.2.01.1604081039440.13335@egate.xpasc.com>
References: <CAB75xn6fmj84ROUtG5eUB3GerHx83hrEr3w5vSADY_g=BRg5FA@mail.gmail.com> <1481689286.47880.1460111891664.JavaMail.yahoo@mail.yahoo.com> <alpine.OSX.2.01.1604080418530.36488@rabdullah.local> <594.1460126622@obiwan.sandelman.ca> <5707C458.7080107@dcrocker.net>
User-Agent: Alpine 2.01 (LRH 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-MDID: vujgUQ2CPGx6
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/beo_cNHAjvdywStOWLhUKJNAit4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: ietf@ietf.org
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: Fri, 08 Apr 2016 18:08:56 -0000

I understand from a family memember who made that crossing multiple times
recently, a 3 hour delay is not unusual.

On Fri, 8 Apr 2016, Dave Crocker wrote:

> On 4/8/2016 7:43 AM, Michael Richardson wrote:
> > Could a person stay in Skudai (Malaysia), and travel in every day for our
> > meetings?
>
>
> That's a suburb of Johor, just into Malaysia from Singapore, so I believe the
> answer is yes, though I don't know what the transit times will be or whether
> it's a fully reliable path.  The two countries sometimes make that border
> awkward.
>
> d/
>
> --
>
>   Dave Crocker
>   Brandenburg InternetWorking
>   bbiw.net
>
>
> ----------
>
> This email has been scanned for spam and viruses by Proofpoint Essentials.
> Visit the following link to report this email as spam:
> https://us1.proofpointessentials.com/index01.php?mod_id=11&mod_option=logitem&mail_id=ZYUcyKuA1vKX&rid=113885848&report=1
>


From nobody Fri Apr  8 11:11:03 2016
Return-Path: <olejacobsen@me.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 8D9F312D187 for <ietf@ietfa.amsl.com>; Fri,  8 Apr 2016 11:11:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.631
X-Spam-Level: 
X-Spam-Status: No, score=-2.631 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 FFUW4AkdJl-y for <ietf@ietfa.amsl.com>; Fri,  8 Apr 2016 11:10:59 -0700 (PDT)
Received: from mr11p00im-asmtp003.me.com (mr11p00im-asmtp003.me.com [17.110.69.254]) (using TLSv1.2 with cipher DHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 422FD12D0EA for <ietf@ietf.org>; Fri,  8 Apr 2016 11:10:59 -0700 (PDT)
Received: from [10.1.10.8] (173-11-110-134-SFBA.hfc.comcastbusiness.net [173.11.110.134]) by mr11p00im-asmtp003.me.com (Oracle Communications Messaging Server 7.0.5.36.0 64bit (built Sep 8 2015)) with ESMTPSA id <0O5B0001FUIASZ10@mr11p00im-asmtp003.me.com> for ietf@ietf.org; Fri, 08 Apr 2016 18:10:59 +0000 (GMT)
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, definitions=2016-04-08_09:,, signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 clxscore=1011 suspectscore=0 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1510270003 definitions=main-1604080268
Date: Fri, 08 Apr 2016 11:10:58 -0700 (PDT)
From: Ole Jacobsen <olejacobsen@me.com>
To: Ted Lemon <mellon@fugue.com>
Subject: Re: China
In-reply-to: <CAPt1N1=DVi5MbNVmceX1zA_tTda4jQ=S=zY83ON2U5WQ_AzB_g@mail.gmail.com>
Message-id: <alpine.OSX.2.01.1604081058090.37683@rabdullah.local>
References: <0D914666-C3D4-4CCE-AD5E-4E5B34EA1A73@piuha.net> <20160407182936.GA21340@pfrc.org> <CAB75xn780nNDjGa_Cc222J20-+1CCHt09Xp8KHzaK=n0xx51pg@mail.gmail.com> <5706B100.9040509@mnt.se> <CAB75xn6fmj84ROUtG5eUB3GerHx83hrEr3w5vSADY_g=BRg5FA@mail.gmail.com> <5706BA40.3060005@mnt.se> <alpine.DEB.2.02.1604072157240.31096@uplift.swm.pp.se> <A9B63A6D-3102-482F-8FFC-2E57A5FD8336@nic.cz> <CC16B445-2B74-4182-BC58-F9D4BFFA1CCF@chopps.org> <alpine.OSX.2.01.1604080420470.36488@rabdullah.local> <20160408133914.GB17588@pfrc.org> <CAPt1N1=DVi5MbNVmceX1zA_tTda4jQ=S=zY83ON2U5WQ_AzB_g@mail.gmail.com>
User-Agent: Alpine 2.01 (OSX 1266 2009-07-14)
MIME-version: 1.0
Content-type: TEXT/PLAIN; charset=US-ASCII
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/0fSaUI5x-XkNtMCA1ujZ3VVvs5c>
Cc: "ietf@ietf.org Discussion" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: Ole Jacobsen <olejacobsen@me.com>
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: Fri, 08 Apr 2016 18:11:01 -0000

On Fri, 8 Apr 2016, Ted Lemon wrote:

> There is another side to this, although I don't disagree with either 
> of you on the China observation.

[snip] 

> It breaks my heart to hear stories of the horror that gay couples 
> have gone through because of discrimination of this sort and other 
> sorts.  I am not okay with being party to that happening in the 
> future.
> 
> I agree that engagement is important, but let us bear in mind the 
> risks we are asking our friends and colleagues to bear when we have 
> this discussion.
> 

Right, well I have heard those stories too, but I have not heard them 
in relation to visitors in Singapore. If you look at the statements
on the US State Department website, there is, as has been pointed out,
a section regarding LGBT laws and practices. The absense of warnings
related to medical care does of course neither mean that it isn't
potentially a problem nor that we should not investigate this further.

I know that this is going to sound like an excuse and it certainly 
isn't meant to be, we did miss this topic and we should have brought
it to the community for review. However, the fact that this issue
has not been "flagged" by sister organizations such as ICANN (4 
meetings in Singapore) and APRICOT (2 meetings) at least suggests
that it isn't a frequently encountered problem. 

Ole


From nobody Fri Apr  8 11:15:52 2016
Return-Path: <melinda.shore@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 AABEE12D522 for <ietf@ietfa.amsl.com>; Fri,  8 Apr 2016 11:15:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 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, 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 DK6EG00CIXZO for <ietf@ietfa.amsl.com>; Fri,  8 Apr 2016 11:15:48 -0700 (PDT)
Received: from mail-io0-x229.google.com (mail-io0-x229.google.com [IPv6:2607:f8b0:4001: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 6180212D524 for <ietf@ietf.org>; Fri,  8 Apr 2016 11:15:48 -0700 (PDT)
Received: by mail-io0-x229.google.com with SMTP id 2so141333430ioy.1 for <ietf@ietf.org>; Fri, 08 Apr 2016 11:15:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding; bh=Iy/GprCJHcmx1FUS7/QXJGFGMxrCVPfBKGM+7gB3K0o=; b=BGL3n3R9SMgqa9pb0ZXivt49E4XVVstYcYueL7vq70Q8Sj7MzRsUrgBbclQTcJZtTC sd5G0F7f7C8Bu2QAmUJZhyhE7+8FB399yPnFX7t+sflOaIHlEA0pK9rOimtPz6VEOvjN waPkLKsBZ7Zlb1aYYKJCfQbmJTVPyU37gbzyqvpncN2IW2Rdnf5Um1XVL1DaYTscn0ID vlFWQbmKsdoq2ZkRIdF5C1aY3VBjP6JtswQH92GMz2i/7oliYaO8EejFbMO7MlQq/4jc Nf1+J9Hm8oZqhItVG06Mu7HFf2qUnqnvKqPCGo1TdXv1wMPwB9EYhVr3GuZtkVO9rUT1 R2tA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=Iy/GprCJHcmx1FUS7/QXJGFGMxrCVPfBKGM+7gB3K0o=; b=M/fI/zvsJAc/aUTIIq6vfJHJgK6Ig6aljXQpO5wEhOLXNlMD96fk5tRocsxfgPp5mu uY/edj8zE4Yt7HxIf0Q/rTu9oQCsaWUaFeA98zo2+pBCK3scJfyndKcy1BgQiLh2tx/L zBJ8+TeAOjNOXbZGZcr2veazrObC2sSqSi5x4Uw/w4B/G+Dij+m0jU7dbVWVuNBfFp24 ON8h1u+LAxRogn6kwlCK9derxYAjozZHUAnZYOE/t7QNMkj1rUKZcUMqqFPLEWCX3BVy R6VqnPbmZ8CHGvTEWQ3EWjWawbseH4eHMWGAc1Ewk6kt1DnIJqchCvTDRe6ftwuJR8yq EqZA==
X-Gm-Message-State: AD7BkJKLQJ3tJjF9kxuZGI/8+GXhHDacb+TEFop1tyyLl2sDEPeTVolmRpJgFHfxGyLrcg==
X-Received: by 10.107.2.206 with SMTP id 197mr12827303ioc.8.1460139347661; Fri, 08 Apr 2016 11:15:47 -0700 (PDT)
Received: from Melindas-MacBook-Pro.local ([63.140.88.173]) by smtp.googlemail.com with ESMTPSA id au6sm3277023igc.0.2016.04.08.11.15.46 for <ietf@ietf.org> (version=TLSv1/SSLv3 cipher=OTHER); Fri, 08 Apr 2016 11:15:46 -0700 (PDT)
Subject: Re: China
To: ietf@ietf.org
References: <0D914666-C3D4-4CCE-AD5E-4E5B34EA1A73@piuha.net> <20160407182936.GA21340@pfrc.org> <CAB75xn780nNDjGa_Cc222J20-+1CCHt09Xp8KHzaK=n0xx51pg@mail.gmail.com> <5706B100.9040509@mnt.se> <CAB75xn6fmj84ROUtG5eUB3GerHx83hrEr3w5vSADY_g=BRg5FA@mail.gmail.com> <5706BA40.3060005@mnt.se> <alpine.DEB.2.02.1604072157240.31096@uplift.swm.pp.se> <A9B63A6D-3102-482F-8FFC-2E57A5FD8336@nic.cz> <CC16B445-2B74-4182-BC58-F9D4BFFA1CCF@chopps.org> <alpine.OSX.2.01.1604080420470.36488@rabdullah.local> <20160408133914.GB17588@pfrc.org> <CAPt1N1=DVi5MbNVmceX1zA_tTda4jQ=S=zY83ON2U5WQ_AzB_g@mail.gmail.com> <alpine.OSX.2.01.1604081058090.37683@rabdullah.local>
From: Melinda Shore <melinda.shore@gmail.com>
Message-ID: <5707F5BC.2070209@gmail.com>
Date: Fri, 8 Apr 2016 10:17:32 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:38.0) Gecko/20100101 Thunderbird/38.6.0
MIME-Version: 1.0
In-Reply-To: <alpine.OSX.2.01.1604081058090.37683@rabdullah.local>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/Fybk_mkw8qFV6DZNVciDm7GJUQk>
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: Fri, 08 Apr 2016 18:15:49 -0000

On 4/8/16 10:10 AM, Ole Jacobsen wrote:
> I know that this is going to sound like an excuse and it certainly
> isn't meant to be, we did miss this topic and we should have brought
> it to the community for review. However, the fact that this issue
> has not been "flagged" by sister organizations such as ICANN (4
> meetings in Singapore) and APRICOT (2 meetings) at least suggests
> that it isn't a frequently encountered problem.

Might be a lot more informative to talk to glbt travel specialists.
Why that may not have crossed the mind of the IAOC that this may be a
useful thing to do is left as an exercise, &c.

Melinda


From nobody Fri Apr  8 11:24:06 2016
Return-Path: <olejacobsen@me.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 786F712D597 for <ietf@ietfa.amsl.com>; Fri,  8 Apr 2016 11:24:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.631
X-Spam-Level: 
X-Spam-Status: No, score=-2.631 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 M5Dl8vu-Grbe for <ietf@ietfa.amsl.com>; Fri,  8 Apr 2016 11:24:04 -0700 (PDT)
Received: from mr11p00im-asmtp001.me.com (mr11p00im-asmtp001.me.com [17.110.69.252]) (using TLSv1.2 with cipher DHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 913A412D598 for <ietf@ietf.org>; Fri,  8 Apr 2016 11:24:03 -0700 (PDT)
Received: from [10.1.10.8] (173-11-110-134-SFBA.hfc.comcastbusiness.net [173.11.110.134]) by mr11p00im-asmtp001.me.com (Oracle Communications Messaging Server 7.0.5.36.0 64bit (built Sep 8 2015)) with ESMTPSA id <0O5B009CSV42DA00@mr11p00im-asmtp001.me.com> for ietf@ietf.org; Fri, 08 Apr 2016 18:24:03 +0000 (GMT)
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, definitions=2016-04-08_09:,, signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 clxscore=1015 suspectscore=0 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1510270003 definitions=main-1604080271
Date: Fri, 08 Apr 2016 11:24:02 -0700 (PDT)
From: Ole Jacobsen <olejacobsen@me.com>
To: Melinda Shore <melinda.shore@gmail.com>
Subject: Re: China
In-reply-to: <5707F5BC.2070209@gmail.com>
Message-id: <alpine.OSX.2.01.1604081122520.37683@rabdullah.local>
References: <0D914666-C3D4-4CCE-AD5E-4E5B34EA1A73@piuha.net> <20160407182936.GA21340@pfrc.org> <CAB75xn780nNDjGa_Cc222J20-+1CCHt09Xp8KHzaK=n0xx51pg@mail.gmail.com> <5706B100.9040509@mnt.se> <CAB75xn6fmj84ROUtG5eUB3GerHx83hrEr3w5vSADY_g=BRg5FA@mail.gmail.com> <5706BA40.3060005@mnt.se> <alpine.DEB.2.02.1604072157240.31096@uplift.swm.pp.se> <A9B63A6D-3102-482F-8FFC-2E57A5FD8336@nic.cz> <CC16B445-2B74-4182-BC58-F9D4BFFA1CCF@chopps.org> <alpine.OSX.2.01.1604080420470.36488@rabdullah.local> <20160408133914.GB17588@pfrc.org> <CAPt1N1=DVi5MbNVmceX1zA_tTda4jQ=S=zY83ON2U5WQ_AzB_g@mail.gmail.com> <alpine.OSX.2.01.1604081058090.37683@rabdullah.local> <5707F5BC.2070209@gmail.com>
User-Agent: Alpine 2.01 (OSX 1266 2009-07-14)
MIME-version: 1.0
Content-type: TEXT/PLAIN; charset=US-ASCII
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/4rGnBBALhUwxlSc7ovJ_30DbwGI>
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: Ole Jacobsen <olejacobsen@me.com>
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: Fri, 08 Apr 2016 18:24:05 -0000

On Fri, 8 Apr 2016, Melinda Shore wrote:
> 
> Might be a lot more informative to talk to glbt travel specialists.
> Why that may not have crossed the mind of the IAOC that this may be a
> useful thing to do is left as an exercise, &c.
> 
> Melinda
> 

Point taken and I am sure that is one of the many lessons we have 
learned from this process.

Ole


From nobody Fri Apr  8 11:52:01 2016
Return-Path: <melinda.shore@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 7DAB612D1DE for <ietf@ietfa.amsl.com>; Fri,  8 Apr 2016 11:51:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 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, RCVD_IN_DNSWL_LOW=-0.7, 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 Rsw5HwclTulF for <ietf@ietfa.amsl.com>; Fri,  8 Apr 2016 11:51:56 -0700 (PDT)
Received: from mail-pf0-x232.google.com (mail-pf0-x232.google.com [IPv6:2607:f8b0:400e:c00::232]) (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 BAB2212D1BC for <ietf@ietf.org>; Fri,  8 Apr 2016 11:51:56 -0700 (PDT)
Received: by mail-pf0-x232.google.com with SMTP id n1so80707556pfn.2 for <ietf@ietf.org>; Fri, 08 Apr 2016 11:51:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=xfdL1Tfgan/0eFLkEaaEvHTmpKpP8HgGe/5UJGDVwT8=; b=Aoy858hLrLgvjNyzElIe7PUaiPNfQK73sQLbx/bXAev/SY/CQq4LsJNOUQxyK6vAUe eJ8Uuew7J2FsO/uE3bBJw/HwwZT4n9k8c3uV6J3eeLu+ldL2Ky7flFYIWesEckEQU33F sUsvivYDnUrombC2CLAT6IV8ui8mPC4+WBAO8Jw6ovTnbJhY7TwSd50PkBQeZr8uVy81 y7/Eeu40jD35IfLZqkltC92PxFw9JlsZsgembWadMRz2LutZWYoAJ2QaBcZgqJgFFPLs lg6jiC31fPwmRK34CEON2LYCvjPWNfur0GuY+R87aWhrwc5UReHY/y3vGOVruI3foIF4 vvhg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=xfdL1Tfgan/0eFLkEaaEvHTmpKpP8HgGe/5UJGDVwT8=; b=i2kGniEQ55ytf0YEgGeOx8uAc2aRmWxhDE+ibVLL6rKgI8EXJkFtlTcdhKeBm54L4q 7T92fkrynqL97a5HqS8N6t3GFaD8XfpNV3YLyI7L/PJm92mfKYUUkuzefamTUQo03OzO ru2Oh7mB7URSUvrJ/ApvcKMbolhYsXeZYlCf2dHdtrgTz6VYjhhs1VgtgqYQzJyIPUvZ hnB6OrGpBr/5wMBwSMcm+wD/s0aYm9kdD6odRT/dOgOdQfjeFn/diSKCB6q7uh2cSkDO 9pu6/UtAeEd04hdHQvrjdnASZpPTr8FoJcYXR51oETIKVEN+uBrdTuwIJL2M50FJHWn1 Uj2w==
X-Gm-Message-State: AD7BkJLld+H25RUylhvZnPE7lE9JFYg9YCMNOiMGfpzwSrmlCQjUJbo8q1744Qo8ADNqiA==
X-Received: by 10.98.74.6 with SMTP id x6mr14654422pfa.80.1460141516061; Fri, 08 Apr 2016 11:51:56 -0700 (PDT)
Received: from Melindas-MacBook-Pro.local ([63.140.88.173]) by smtp.googlemail.com with ESMTPSA id tn5sm20336742pac.32.2016.04.08.11.51.54 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 08 Apr 2016 11:51:55 -0700 (PDT)
Subject: Re: China
To: Ole Jacobsen <olejacobsen@me.com>
References: <0D914666-C3D4-4CCE-AD5E-4E5B34EA1A73@piuha.net> <20160407182936.GA21340@pfrc.org> <CAB75xn780nNDjGa_Cc222J20-+1CCHt09Xp8KHzaK=n0xx51pg@mail.gmail.com> <5706B100.9040509@mnt.se> <CAB75xn6fmj84ROUtG5eUB3GerHx83hrEr3w5vSADY_g=BRg5FA@mail.gmail.com> <5706BA40.3060005@mnt.se> <alpine.DEB.2.02.1604072157240.31096@uplift.swm.pp.se> <A9B63A6D-3102-482F-8FFC-2E57A5FD8336@nic.cz> <CC16B445-2B74-4182-BC58-F9D4BFFA1CCF@chopps.org> <alpine.OSX.2.01.1604080420470.36488@rabdullah.local> <20160408133914.GB17588@pfrc.org> <CAPt1N1=DVi5MbNVmceX1zA_tTda4jQ=S=zY83ON2U5WQ_AzB_g@mail.gmail.com> <alpine.OSX.2.01.1604081058090.37683@rabdullah.local> <5707F5BC.2070209@gmail.com> <alpine.OSX.2.01.1604081122520.37683@rabdullah.local>
From: Melinda Shore <melinda.shore@gmail.com>
Message-ID: <5707FE3A.2070108@gmail.com>
Date: Fri, 8 Apr 2016 10:53:46 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:38.0) Gecko/20100101 Thunderbird/38.6.0
MIME-Version: 1.0
In-Reply-To: <alpine.OSX.2.01.1604081122520.37683@rabdullah.local>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/lc748v_I-8sMiKdZGtk7FKRfH-c>
Cc: 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: Fri, 08 Apr 2016 18:51:59 -0000

On 4/8/16 10:24 AM, Ole Jacobsen wrote:
> On Fri, 8 Apr 2016, Melinda Shore wrote:
>> Might be a lot more informative to talk to glbt travel specialists.
>> Why that may not have crossed the mind of the IAOC that this may be a
>> useful thing to do is left as an exercise, &c.

> Point taken and I am sure that is one of the many lessons we have
> learned from this process.

Also, I think it's almost certainly the case that any large company
has someone in their travel office who's looked at this issue (and
related ones), and that it might be worth trying to engage one of those
folks first.

Melinda


From nobody Fri Apr  8 12:48:40 2016
Return-Path: <mcr+ietf@sandelman.ca>
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 974BE12D5F6 for <ietf@ietfa.amsl.com>; Fri,  8 Apr 2016 12:48:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Level: 
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 Z4xDZK2Gq__h for <ietf@ietfa.amsl.com>; Fri,  8 Apr 2016 12:48:36 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3AF9D12D5E2 for <ietf@ietf.org>; Fri,  8 Apr 2016 12:48:36 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 49C2F20183; Fri,  8 Apr 2016 15:52:15 -0400 (EDT)
Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 6249063755; Fri,  8 Apr 2016 15:48:35 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Andrew Allen <aallen@blackberry.com>
Subject: Re: Concerns about Singapore
In-Reply-To: <20160408150512.6283348.55871.10388@blackberry.com>
References: <CAB75xn6fmj84ROUtG5eUB3GerHx83hrEr3w5vSADY_g=BRg5FA@mail.gmail.com> <1481689286.47880.1460111891664.JavaMail.yahoo@mail.yahoo.com> <alpine.OSX.2.01.1604080418530.36488@rabdullah.local> <594.1460126622@obiwan.sandelman.ca>, <5707C458.7080107@dcrocker.net> <20160408150512.6283348.55871.10388@blackberry.com>
X-Mailer: MH-E 8.6; nmh 1.6+dev; GNU Emacs 24.4.2
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Fri, 08 Apr 2016 15:48:35 -0400
Message-ID: <3746.1460144915@obiwan.sandelman.ca>
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/N_K4acOyOXldWmKfLTpXH-A7TbY>
Cc: Dave Crocker <dcrocker@bbiw.net>, "ietf@ietf.org 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: Fri, 08 Apr 2016 19:48:37 -0000

--=-=-=
Content-Type: text/plain


Andrew Allen <aallen@blackberry.com> wrote:
    > According to the Web link posted earlier Malaysia has similar laws.

Yes, I wasn't suggesting it because of laws, but rather because I thought it
might have a larger variety of price ranges in hotels.

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-




--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQEVAwUBVwgLEICLcPvd0N1lAQLmvAf/Y1MpEX6WITvSjlUKc4QZHXci18/xIryv
xVqLotVLolYY/Hsj1gWEULdNnfThzcg3AVbm5BD/MABRf8FsvV+e1cwdTBDdDosE
CAA/3fm/XDSdzITXbPQIhZlWL8IXHbSzc3CwS/fA5Co7CA0ym6NMIty0KewwNGiQ
MOsH7i1uUxiveqRK5EUiUAluFL8y139qaWuuV9ayS/vV1dF145Cm2SuCagl5KEv2
R6q52tDIUy+nF7+pwBPMrHZVWUYg/S+SqSoE9Ue+UflBVLcmxVCbj5anISGWCgIm
WbeLyFbR77MUyFI6cGe5wFYS1X8Vtqf4p6Ebgoh78DVye/pECeCk+g==
=kibX
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Fri Apr  8 13:14:13 2016
Return-Path: <jgs@bgp.nu>
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 1C77612D703 for <ietf@ietfa.amsl.com>; Thu,  7 Apr 2016 18:45:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] 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 wlPQnHiR_C6E for <ietf@ietfa.amsl.com>; Thu,  7 Apr 2016 18:45:25 -0700 (PDT)
Received: from bgp.nu (bgp.nu [147.28.0.53]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8935112D6DB for <ietf@ietf.org>; Thu,  7 Apr 2016 18:45:25 -0700 (PDT)
Received: from ssubron-sslvpn-nc.jnpr.net (unknown [66.129.241.14]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by bgp.nu (Postfix) with ESMTP id C0C3466CF34; Thu,  7 Apr 2016 21:45:22 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Subject: Re: Concerns about Singapore
From: "John G. Scudder" <jgs@bgp.nu>
In-Reply-To: <A9B63A6D-3102-482F-8FFC-2E57A5FD8336@nic.cz>
Date: Thu, 7 Apr 2016 22:45:14 -0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <1070A34B-E88B-4BF3-95D0-15B6BF26A704@bgp.nu>
References: <0D914666-C3D4-4CCE-AD5E-4E5B34EA1A73@piuha.net> <20160407182936.GA21340@pfrc.org> <CAB75xn780nNDjGa_Cc222J20-+1CCHt09Xp8KHzaK=n0xx51pg@mail.gmail.com> <5706B100.9040509@mnt.se> <CAB75xn6fmj84ROUtG5eUB3GerHx83hrEr3w5vSADY_g=BRg5FA@mail.gmail.com> <5706BA40.3060005@mnt.se> <alpine.DEB.2.02.1604072157240.31096@uplift.swm.pp.se> <A9B63A6D-3102-482F-8FFC-2E57A5FD8336@nic.cz>
To: Ladislav Lhotka <lhotka@nic.cz>
X-Mailer: Apple Mail (2.3124)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/IOAMC2rq38bNv_XW4YbsvQo9A1o>
X-Mailman-Approved-At: Fri, 08 Apr 2016 13:14:12 -0700
Cc: "ietf@ietf.org 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: Fri, 08 Apr 2016 01:45:27 -0000

On Apr 7, 2016, at 5:08 PM, Ladislav Lhotka <lhotka@nic.cz> wrote:
> Yes, and speaking of myself, I am prepared, to a reasonable degree, to =
adjust my behaviour to those laws (and cultural habits as well).

It's wonderful for you if you are always able to do so. Not everyone has =
that luxury. I don't think I can say this better, so I'll just quote:

On Apr 7, 2016, at 3:29 PM, Jeffrey Haas <jhaas@pfrc.org> wrote:
> The legal environments of the various countries we consider for venues
> obviously must be a general consideration for our selection criteria.  =
For
> most considerations, these are "here are thing you do not do - they =
are not
> legal".
>=20
> For this particular issue, the consideration is whether the people =
themselves
> are the thing that is illegal.

--John=


From nobody Fri Apr  8 13:19:23 2016
Return-Path: <olejacobsen@me.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 243D712D5FA for <ietf@ietfa.amsl.com>; Fri,  8 Apr 2016 13:19:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.631
X-Spam-Level: 
X-Spam-Status: No, score=-2.631 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 SJ5Dqz7gRx5b for <ietf@ietfa.amsl.com>; Fri,  8 Apr 2016 13:19:20 -0700 (PDT)
Received: from mr11p00im-asmtp001.me.com (mr11p00im-asmtp001.me.com [17.110.69.252]) (using TLSv1.2 with cipher DHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F241E12D655 for <ietf@ietf.org>; Fri,  8 Apr 2016 13:19:15 -0700 (PDT)
Received: from [10.1.10.8] (173-11-110-134-SFBA.hfc.comcastbusiness.net [173.11.110.134]) by mr11p00im-asmtp001.me.com (Oracle Communications Messaging Server 7.0.5.36.0 64bit (built Sep 8 2015)) with ESMTPSA id <0O5C000NI0G2OL00@mr11p00im-asmtp001.me.com> for ietf@ietf.org; Fri, 08 Apr 2016 20:19:15 +0000 (GMT)
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, definitions=2016-04-08_11:,, signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 clxscore=1015 suspectscore=0 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1510270003 definitions=main-1604080300
Date: Fri, 08 Apr 2016 13:19:14 -0700 (PDT)
From: Ole Jacobsen <olejacobsen@me.com>
To: Michael Richardson <mcr+ietf@sandelman.ca>
Subject: Re: Concerns about Singapore
In-reply-to: <3746.1460144915@obiwan.sandelman.ca>
Message-id: <alpine.OSX.2.01.1604081315580.38286@rabdullah.local>
References: <CAB75xn6fmj84ROUtG5eUB3GerHx83hrEr3w5vSADY_g=BRg5FA@mail.gmail.com> <1481689286.47880.1460111891664.JavaMail.yahoo@mail.yahoo.com> <alpine.OSX.2.01.1604080418530.36488@rabdullah.local> <594.1460126622@obiwan.sandelman.ca> <5707C458.7080107@dcrocker.net> <20160408150512.6283348.55871.10388@blackberry.com> <3746.1460144915@obiwan.sandelman.ca>
User-Agent: Alpine 2.01 (OSX 1266 2009-07-14)
MIME-version: 1.0
Content-type: TEXT/PLAIN; charset=US-ASCII
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/XkoVpvU-_w-fkxBFUP_XFWgzaK8>
Cc: Dave Crocker <dcrocker@bbiw.net>, "ietf@ietf.org Discussion" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: Ole Jacobsen <olejacobsen@me.com>
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: Fri, 08 Apr 2016 20:19:22 -0000

Michael,

Check your favorite hotel booking site. There are plenty of
reasonable hotels in Singapore, and it is a small city with
very good and very inexpensive transportation options including
a metro system and reasonable taxis.

I have only one real complaint: it's too hot and humid for my
liking, but then again I could also describe Singapore as a
very large air-conditioned shopping center disguised as a country :-)

Ole


Ole J. Jacobsen
Editor and Publisher
The Internet Protocol Journal
Office:  +1 415-550-9433
Cell:    +1 415-370-4628
docomo: (090) 3337-9311
Web: protocoljournal.org
E-mail: olejacobsen@me.com




On Fri, 8 Apr 2016, Michael Richardson wrote:

> 
> Andrew Allen <aallen@blackberry.com> wrote:
>     > According to the Web link posted earlier Malaysia has similar laws.
> 
> Yes, I wasn't suggesting it because of laws, but rather because I thought it
> might have a larger variety of price ranges in hotels.
> 
> --
> Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
>  -= IPv6 IoT consulting =-
> 
> 
> 
> 


From nobody Fri Apr  8 13:57:26 2016
Return-Path: <cpignata@cisco.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 A0B1712D66A for <ietf@ietfa.amsl.com>; Fri,  8 Apr 2016 13:57:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.531
X-Spam-Level: 
X-Spam-Status: No, score=-14.531 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 sIx2EJOuKieT for <ietf@ietfa.amsl.com>; Fri,  8 Apr 2016 13:57:23 -0700 (PDT)
Received: from aer-iport-2.cisco.com (aer-iport-2.cisco.com [173.38.203.52]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AB27812D1D4 for <ietf@ietf.org>; Fri,  8 Apr 2016 13:57:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2651; q=dns/txt; s=iport; t=1460149042; x=1461358642; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=NtK9xnckBrfQxP49q165InYAcJ1/rhAPdyUbgxiUvcQ=; b=FffeK2j95bkpi5nMCJpl47SXFsJQ2dvUpmfpzzp/D73Y9sO5B5J+9y9Q SvXfg6rc3ktFQAg9nerLvvrnFWzDPCBPPHVPReIKZPe7dcf9uf0i7mf+O TMDMEnRpCvLdLgRfRUT6JwLTkY0L+VFts8pQloC03ziGdjozwyPftav6k w=;
X-Files: signature.asc : 841
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0B9AgB4GghX/xbLJq1chAp9Bro/DoFzF?= =?us-ascii?q?wqFIkoCgWsUAQEBAQEBAWUnhEIBAQQBAQEgSxsCAUcDAgInCxQRAgQTDgaIEw4?= =?us-ascii?q?DrmyRZgEBAQEBAQEBAQEBAQEBAQEBARAEBIYhgXUIig0rgisFh2cChxeEGYRrA?= =?us-ascii?q?YMjgWZtiBWPDYY4iGwBHgFDg2dsiDt+AQEB?=
X-IronPort-AV: E=Sophos;i="5.24,454,1454976000";  d="asc'?scan'208";a="634061986"
Received: from aer-iport-nat.cisco.com (HELO aer-core-1.cisco.com) ([173.38.203.22]) by aer-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 08 Apr 2016 20:57:20 +0000
Received: from XCH-RTP-020.cisco.com (xch-rtp-020.cisco.com [64.101.220.160]) by aer-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id u38KvKaZ006805 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL) for <ietf@ietf.org>; Fri, 8 Apr 2016 20:57:20 GMT
Received: from xch-rtp-020.cisco.com (64.101.220.160) by XCH-RTP-020.cisco.com (64.101.220.160) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Fri, 8 Apr 2016 16:57:19 -0400
Received: from xch-rtp-020.cisco.com ([64.101.220.160]) by XCH-RTP-020.cisco.com ([64.101.220.160]) with mapi id 15.00.1104.009; Fri, 8 Apr 2016 16:57:19 -0400
From: "Carlos Pignataro (cpignata)" <cpignata@cisco.com>
To: IETF discussion list <ietf@ietf.org>
Subject: Follow-ups: Concerns about Singapore
Thread-Topic: Follow-ups: Concerns about Singapore
Thread-Index: AQHRkOMZq+MCcr0Tk0mYGURd2vrzsZ9/GCcAgAAATwCAAAuKAIAACE6AgAD6eICAAAvNgIAAOMwAgAAA3QCAAAUnAIAATyuAgAAIkACAAAqfgA==
Date: Fri, 8 Apr 2016 20:57:19 +0000
Message-ID: <25300889-93D6-48E8-B71D-3CCA27017681@cisco.com>
References: <CAB75xn6fmj84ROUtG5eUB3GerHx83hrEr3w5vSADY_g=BRg5FA@mail.gmail.com> <1481689286.47880.1460111891664.JavaMail.yahoo@mail.yahoo.com> <alpine.OSX.2.01.1604080418530.36488@rabdullah.local> <594.1460126622@obiwan.sandelman.ca> <5707C458.7080107@dcrocker.net> <20160408150512.6283348.55871.10388@blackberry.com> <3746.1460144915@obiwan.sandelman.ca> <alpine.OSX.2.01.1604081315580.38286@rabdullah.local>
In-Reply-To: <alpine.OSX.2.01.1604081315580.38286@rabdullah.local>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.82.247.9]
Content-Type: multipart/signed; boundary="Apple-Mail=_13E7CC2E-F921-47EB-AC3B-C0556B69DAEE"; protocol="application/pgp-signature"; micalg=pgp-sha256
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/oeS4XCp67SUgSTfsSMM5VQlqcVs>
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: Fri, 08 Apr 2016 20:57:24 -0000

--Apple-Mail=_13E7CC2E-F921-47EB-AC3B-C0556B69DAEE
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Hi,

[This note is sent as part of the Facilitators experiment, to maximize =
the effectiveness of discussions at the IETF-Discussion mailing list]

As this thread started with the concerns express during the plenary =
about Singapore as a meeting venue, I wanted to summarize the arguments, =
and refocus and redirect the discussion:

Several details on both the letter and the practicality of the Singapore =
law that discriminates agains LGBTQ, and its implications, followed =
these community-expressed concerns. A number of suggestions, =
recommendations, and additional pieces of information about other =
countries and locations were also shared.

The IAOC and its Meetings Committee acknowledged the issue, and shared a =
two-point plan at [1].

Meeting venue selection and its associated criteria is naturally a =
relevant and most important topic for the community. At this point, the =
most effective channel for providing input and discussion is at the =
MTGVENUE mailing list [2] [3], following the MTGVENUE BoF. That would =
ensure feedback and requirements are appropriately captured.

Thanks!

=E2=80=94 Carlos.

[1] =
https://mailarchive.ietf.org/arch/msg/ietf/hKwBYOwPkE6VTA4mxxf00NTLLF0
[2] https://www.ietf.org/mailman/listinfo/mtgvenue
[3] mailto:mtgvenue@ietf.org


--Apple-Mail=_13E7CC2E-F921-47EB-AC3B-C0556B69DAEE
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="signature.asc"
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iQIcBAEBCAAGBQJXCBsrAAoJEIXgpQGOZny9sD4QAIqsVHXl9eOoDYpcen/SMWDa
DCZvco0nEVtjkS4piBqzzkn6HYv3pX9018K3O6716rF2NwS2Wdv/tRxcEpazEteT
J/EMsOugI60UlLNJGveGxTaOINdX/Y/NaupcqeXJk4fJRnKh7pvJrmKKh4Z+i+Rd
Y7VywbrHTi/jsoSmnkQObONqfmcM+ZRzgKxH+2fkx/UFupjVsA9Zx4FrhRD10SHU
WkLy7e/snyRQKmnsDdsgwJFMf82VhJxeZkLKT7K8hOjLVM2qEhSM9RduCLkdUIBl
pHvLqasjokQ0dtXW3P0XmcikA4xzq3eRn/vepcKD7O+5WHEFDhZJOYy/vrPlfcMp
r/ykApcBuBt8KJXfHzm8DMwVNSm1ZYa7TVU3yFNzY501HZfbxKkOTdXRjn2RR4ui
uT+LXetEwThV6YdoYpnAzgBBq/xNBLjvcvPMPoV89cwDRmWsIwQcH3GYOowCTPXc
mt61uuzE1u7kNcHNkI4Ggpi/dWw4U3g3ITO+IqcV2v+kqZzu685kwHNIieBZ9O+G
DBXiWnynpw8QQ7Il0qzdP3NF1rbn+Qqo73j6q7uLD4NmqO+ZSCK56k7+AgVuNYCW
dyEPpofblcq4jH03vqhAsoPEBSNAuLi8m2BavkOeMsXEI5U1vtripVf/Pi1/PyEP
/V/CE88KsGKDkgNt8kJ6
=uKA8
-----END PGP SIGNATURE-----

--Apple-Mail=_13E7CC2E-F921-47EB-AC3B-C0556B69DAEE--


From nobody Fri Apr  8 14:18:15 2016
Return-Path: <fred@cisco.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 15C6512D129 for <ietf@ietfa.amsl.com>; Fri,  8 Apr 2016 14:18:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -114.531
X-Spam-Level: 
X-Spam-Status: No, score=-114.531 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 1HriJEFWnc9S for <ietf@ietfa.amsl.com>; Fri,  8 Apr 2016 14:18:12 -0700 (PDT)
Received: from rcdn-iport-5.cisco.com (rcdn-iport-5.cisco.com [173.37.86.76]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9953912D0A8 for <ietf@ietf.org>; Fri,  8 Apr 2016 14:18:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2033; q=dns/txt; s=iport; t=1460150292; x=1461359892; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=4F5XSHX8uaVM/EMPL+9fCtvZkFwFKVC7tmUwSGp5Suk=; b=DoNh6s1+TcYKL2iiY3q7C4NbTPUnYpdwbmPBxTpRy2qP3R+XY+Jo88ud NvhEqDZKJYavNVTNPQMbOxeM/XpztXHCOKRs1Ahp1o9Gy1jdbnqW+FOzY 7UYEO6af9vj28Cv44q3FpsxIGhHriMlZf1S+JFLYxFpYO3EAy6mCyAVj5 w=;
X-Files: signature.asc : 833
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AtBQAoHwhX/5RdJa1cgzdTfQauZ41ZI?= =?us-ascii?q?4VqAoEzPBABAQEBAQEBZSeEQgEBBCNGAQ8QAgEIGCoCAiERJQIEDgUOiAQDEg6?= =?us-ascii?q?ud4w9DYUhAQEBAQEBAQEBAQEBAQEBAQEBAQEBDQiIFgiCToJBhH4rgisFl1MxA?= =?us-ascii?q?YMjgWZthiCBdYFRZIxYh0qHWgE3K4NnbAGIOn4BAQE?=
X-IronPort-AV: E=Sophos;i="5.24,454,1454976000";  d="asc'?scan'208";a="91749001"
Received: from rcdn-core-12.cisco.com ([173.37.93.148]) by rcdn-iport-5.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 08 Apr 2016 21:18:11 +0000
Received: from XCH-ALN-015.cisco.com (xch-aln-015.cisco.com [173.36.7.25]) by rcdn-core-12.cisco.com (8.14.5/8.14.5) with ESMTP id u38LIBDX003123 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 8 Apr 2016 21:18:11 GMT
Received: from xch-rcd-013.cisco.com (173.37.102.23) by XCH-ALN-015.cisco.com (173.36.7.25) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Fri, 8 Apr 2016 16:18:10 -0500
Received: from xch-rcd-013.cisco.com ([173.37.102.23]) by XCH-RCD-013.cisco.com ([173.37.102.23]) with mapi id 15.00.1104.009; Fri, 8 Apr 2016 16:18:10 -0500
From: "Fred Baker (fred)" <fred@cisco.com>
To: Paul Wouters <paul@nohats.ca>
Subject: Re: Concerns about Singapore
Thread-Topic: Concerns about Singapore
Thread-Index: AQHRkOMYE5f4WLltSk+KMEq8Vk+KKZ9/KOsAgAAATwCAAAuKAIAACE2AgAD6eICAAAIPgIAAHFeAgACUOgA=
Date: Fri, 8 Apr 2016 21:18:10 +0000
Message-ID: <2CF731C8-41F0-419F-8695-FE391FB79CD1@cisco.com>
References: <CAB75xn6fmj84ROUtG5eUB3GerHx83hrEr3w5vSADY_g=BRg5FA@mail.gmail.com> <1481689286.47880.1460111891664.JavaMail.yahoo@mail.yahoo.com> <6E18B072-412B-474D-963F-7EF20E31979E@gmail.com> <3352E874-D874-4676-B8CA-1C9E099F72F3@nohats.ca>
In-Reply-To: <3352E874-D874-4676-B8CA-1C9E099F72F3@nohats.ca>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-mailer: Apple Mail (2.3124)
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.24.82.70]
Content-Type: multipart/signed; boundary="Apple-Mail=_BA2349E7-9296-4FF0-BCB2-B99DB59AA1AB"; protocol="application/pgp-signature"; micalg=pgp-sha1
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/mc8KeidXlGUcDNQhfGx5_rBsphs>
Cc: "ietf@ietf.org 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: Fri, 08 Apr 2016 21:18:14 -0000

--Apple-Mail=_BA2349E7-9296-4FF0-BCB2-B99DB59AA1AB
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8


On Apr 8, 2016, at 9:26 AM, Paul Wouters <paul@nohats.ca> wrote:
> On Apr 8, 2016, at 07:45, Yoav Nir <ynir.ietf@gmail.com> wrote:
>> On 8 Apr 2016, at 7:38 AM, <nalini.elkins@insidethestack.com> =
<nalini.elkins@insidethestack.com> wrote:
>>> On a positive note:
>>>=20
>>> Pope Francis urges greater acceptance of homosexuals, =
non-traditional families
>>> =
http://edition.cnn.com/2016/04/08/europe/vatican-pope-family/index.html?ad=
key=3Dbn
>>=20
>> That=E2=80=99s fine, but I don=E2=80=99t think the Vatican has a good =
venue for us. :-)
>=20
> But we could adopt the Conclave model of decision making!
>=20
> Paul

We already have running code on that. It's called "the Nomcom".

--Apple-Mail=_BA2349E7-9296-4FF0-BCB2-B99DB59AA1AB
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="signature.asc"
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iQIVAwUBVwgf6kayAOS/EQ8MAQLPDw/+LTt5M1/dh4KiH+u021b6UR/J2Dyen+Ml
ZpuQOmZhcpLWYpCrV4AB5I4z/0jCHA7kcYtyNkh0D9gonzhHM639Hg87A+t36bax
uGEgXRioRJPCubyFx3mppCpeXwOzv4QFzCaK5jtUyWwF6IJnRH75eOd7Hws79yAi
KmISiFVIGrx3bM/yi3BUy+UNmcUx71RCDiQiTazYjb9afi4KK/yG5UMWvHe5PSU+
94BKKkuzrXMozqQBDMU0CZTZs88Gv4c58ZxjLxNixqv1Gq+9vYDDm+uFPKsySX2c
cHHjomSgN79Z6Q2yZ2UkWPCeSUlNLQCuGdCI+A9zNWjPr8LzUe0UaNmg+yfFGBo5
ChzdyD7lhvf2bb4netwYYveaTlRzW+OLVrHW1Qoojayobs452k43mldpgLVBtgSi
tlC5o6GUqdBCu/Nczb0xE5r1Bxb4m45TGh9RnW76wEwQT6+rZQ7hH2JPQVAMFSJs
iBOdVDjp4n9TvNXeFv9v7oyGaZjiHZxW+3+7CSB65SFo0ppsQruIhX/HL+I+Pdm3
HIUE8+mwIV9E0g9o4mXglCLj1DE2X75jSrd4bgUaSuAkB0urSz77Gfywz5OliHVl
8L53I9CQ5SYz3HUSQpMepJWwdWs+WmJ/58CTPGzwlegWuqKwG6VjADKzCrmXfrA5
Vlat6EZqn/o=
=1efe
-----END PGP SIGNATURE-----

--Apple-Mail=_BA2349E7-9296-4FF0-BCB2-B99DB59AA1AB--


From nobody Fri Apr  8 18:22:18 2016
Return-Path: <harish.pillay@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 C817E12D55A for <ietf@ietfa.amsl.com>; Fri,  8 Apr 2016 18:22:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 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, RCVD_IN_DNSWL_LOW=-0.7, 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 0OimV85oSIXB for <ietf@ietfa.amsl.com>; Fri,  8 Apr 2016 18:22:13 -0700 (PDT)
Received: from mail-io0-x232.google.com (mail-io0-x232.google.com [IPv6:2607:f8b0:4001:c06::232]) (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 9D54C12D1DF for <ietf@ietf.org>; Fri,  8 Apr 2016 18:22:13 -0700 (PDT)
Received: by mail-io0-x232.google.com with SMTP id o126so128807186iod.0 for <ietf@ietf.org>; Fri, 08 Apr 2016 18:22:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=lDisGEyKlvBvH8GjYGUmjJa877oyjvSHJa+ImToClzg=; b=riB8a2CipiMRqFWmofVvX/a1jxVhtvp1etMYiThqsrXDOJNeuxCUcqrIJbcqnR+/d5 GB8Se03C40TkdcJnTPIy5yTjC0toqSfemaoiGHdfZmC1L8nVVW2UWtD9NZkDPJdjMeUA EW5+uiqA9zd47zzPSAF//BHhyZSFM4JSdLd5WFLEclt4txWWYABDOFHr05HBu7ypSTLQ 22YiGgsbhI5uleiCoIXR3m9mfemnOcz75SMsxi0AK7dw0Md8/ZcWDKB08a64dta0V+ro OllL9Co8UXn2hjQDOiJWuH23lTUgUByiZ9dUMQIuRHAU7LGyx1dIXTpalACphpdclPN7 +5vw==
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:date :message-id:subject:from:to:cc; bh=lDisGEyKlvBvH8GjYGUmjJa877oyjvSHJa+ImToClzg=; b=CHcTVwuZLC+Xga8EhRECeS9fKqga12ajcvHqikFFjz4zXLEhFbqwuw459nvzDh7TbZ UJn1eJ4MiHdTVdqN3RqUvigYNG5TkUOFmldQQYtEYbTER+MglnQtCzeoDq4D4KFW/TO7 E7VRlobQg1KqbYirJFrdbpd6KYXCv1xPxggW9yq+WkL7OPZdYQH1z4AP0Y7pr8V4rI4F kUV2yoToxUt62orVhXFNKe3D6kyNvVrsCLPk8fCMtTd4ipjfoRk+Aay/yGN7PIkb2iH5 cJzEPelC5uj7nQHvaxcgEixA2Ey3K3lO4XbyQ7lWTPBsfrWDiyxI/0GtKYG4VsGQggzp 9rgQ==
X-Gm-Message-State: AD7BkJKsYIk49pTqjHQA4oRLnVyV/oJCyrps1E+FooCWuoowcbOj9g01HCcIVGYzQ1IYMIWtN7nOmhkHmdYJng==
MIME-Version: 1.0
X-Received: by 10.107.56.196 with SMTP id f187mr12513061ioa.156.1460164932929;  Fri, 08 Apr 2016 18:22:12 -0700 (PDT)
Received: by 10.107.129.214 with HTTP; Fri, 8 Apr 2016 18:22:12 -0700 (PDT)
In-Reply-To: <5707C458.7080107@dcrocker.net>
References: <CAB75xn6fmj84ROUtG5eUB3GerHx83hrEr3w5vSADY_g=BRg5FA@mail.gmail.com> <1481689286.47880.1460111891664.JavaMail.yahoo@mail.yahoo.com> <alpine.OSX.2.01.1604080418530.36488@rabdullah.local> <594.1460126622@obiwan.sandelman.ca> <5707C458.7080107@dcrocker.net>
Date: Sat, 9 Apr 2016 09:22:12 +0800
Message-ID: <CAHkmkwu0dRwyEF8y2YefsAc=R88ZXcTj9F4DxPFZdho3DwFqDw@mail.gmail.com>
Subject: Re: Concerns about Singapore
From: Harish Pillay <harish.pillay@gmail.com>
To: dcrocker@bbiw.net
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/tjZpQaj8wacLbcY_1t7SIzsQnAY>
Cc: Michael Richardson <mcr@sandelman.ca>, "ietf@ietf.org 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: Sat, 09 Apr 2016 01:22:16 -0000

>> Could a person stay in Skudai (Malaysia), and travel in every day for our
>> meetings?
>
> That's a suburb of Johor, just into Malaysia from Singapore, so I believe
> the answer is yes, though I don't know what the transit times will be or
> whether it's a fully reliable path.  The two countries sometimes make that
> border awkward.
>
> d/
>
> --
>
>   Dave Crocker
>   Brandenburg InternetWorking
>   bbiw.net

Doable, but you'd need to take one of two landlinks - the Causeway or
the Second Link. I have colleagues who live in Johor Bahru (the capital
of Johor where Skudai) who commute daily.

Harish


From nobody Fri Apr  8 18:24:36 2016
Return-Path: <harish.pillay@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 D46A412D156 for <ietf@ietfa.amsl.com>; Fri,  8 Apr 2016 18:24:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 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, RCVD_IN_DNSWL_LOW=-0.7, 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 f026P4tFxL8k for <ietf@ietfa.amsl.com>; Fri,  8 Apr 2016 18:24:32 -0700 (PDT)
Received: from mail-io0-x22c.google.com (mail-io0-x22c.google.com [IPv6:2607:f8b0:4001:c06::22c]) (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 AA55A12D131 for <ietf@ietf.org>; Fri,  8 Apr 2016 18:24:32 -0700 (PDT)
Received: by mail-io0-x22c.google.com with SMTP id 2so151159558ioy.1 for <ietf@ietf.org>; Fri, 08 Apr 2016 18:24:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to;  bh=jNzjtgDR519OpRffj59iuYJVp0rRW0Qx6I6+JfiDRmg=; b=naceK6Fcfxhmmhd64j1M/2hOlWET5lguq4SUSrJz631dlCpUnIG3dswkJql9gIBtp2 cLkvtohG2vIxs1ld1c13hiBhLrG5OdExvoo2d5gvMjk1KyVLnH5iQBb99Bn8aW3b966a mWTGH8/Tm5ndHZEN6No43VL/w7i/rjsiCdJYTraiq/PsvJ2B5jpNAk0vbMd6Fg0GIFMM yyNG6jtj3UBETOZhEXqS+LydxY3eKZYAbK1ir5NLCQ/rEGGDzjr067fZvbglmR8f5yg2 qcQ7byYwJ0ETrMrx/SkaKrTMZdxuY5EnczQOxMHS9yxgRKE5uZXbPchbeZMGNCPhxki3 JXAg==
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:date :message-id:subject:from:to; bh=jNzjtgDR519OpRffj59iuYJVp0rRW0Qx6I6+JfiDRmg=; b=cmvw9zTU55JemxTIU2cb3NHIjmG2YnABhbPNuCHMDKFmL3b9rY02VtzqGh/ZI0bmiN PIo9fArCg1x/dttd6hBn5QWaSW9OoZQVDzTizPDf3Cv70JJAB7ttMqFegvxPQPam7/N9 ZFMAV7egdZ+Pa6atnUe/8QDbrb5/ImcUDZgvXFesjpc57HekzZsholHkavSU9Ovij0xz 99UeDJyUcuLSg96vpcjA945hLRd3oaQizSto+cy2EvnLWZYrspSW5sETOpHhovTj8Opu AjdLAFSJSmM0ajB5K7nqwML324h9JJYZlwy7VZp2p2YHcDAERJgtMjdFcDT+IDEma5TX CzWA==
X-Gm-Message-State: AD7BkJLdwjiXSyP9quTpOYCrqJmQtI/VYvCHrmdRPCb/QxH4a7GVS1V6ubca+cHEbY2VJzLp2FvAi4ZOuYASTQ==
MIME-Version: 1.0
X-Received: by 10.107.161.140 with SMTP id k134mr13229335ioe.190.1460165072118;  Fri, 08 Apr 2016 18:24:32 -0700 (PDT)
Received: by 10.107.129.214 with HTTP; Fri, 8 Apr 2016 18:24:31 -0700 (PDT)
In-Reply-To: <alpine.LRH.2.01.1604081039440.13335@egate.xpasc.com>
References: <CAB75xn6fmj84ROUtG5eUB3GerHx83hrEr3w5vSADY_g=BRg5FA@mail.gmail.com> <1481689286.47880.1460111891664.JavaMail.yahoo@mail.yahoo.com> <alpine.OSX.2.01.1604080418530.36488@rabdullah.local> <594.1460126622@obiwan.sandelman.ca> <5707C458.7080107@dcrocker.net> <alpine.LRH.2.01.1604081039440.13335@egate.xpasc.com>
Date: Sat, 9 Apr 2016 09:24:31 +0800
Message-ID: <CAHkmkwv7nZX5XzRsgvMfNLgOvemsykxJQBN7v3fL09jCLzydSw@mail.gmail.com>
Subject: Re: Concerns about Singapore
From: Harish Pillay <harish.pillay@gmail.com>
To: ietf@ietf.org
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/QJPBUMWjUlOAxZ5OSpOfDqN-YaY>
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, 09 Apr 2016 01:24:35 -0000

> I understand from a family memember who made that crossing multiple times
> recently, a 3 hour delay is not unusual.

it is very variable. There are live video feeds of both the land crossing:

http://www.onemotoring.com.sg/publish/onemotoring/en/on_the_roads/traffic_cameras0/tuas.html

that can be used as reference and guide.

Harish


From nobody Fri Apr  8 18:32:43 2016
Return-Path: <harish.pillay@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 F255C12D61E for <ietf@ietfa.amsl.com>; Fri,  8 Apr 2016 18:32:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 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, RCVD_IN_DNSWL_LOW=-0.7, 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 yPAC8xaOz6_f for <ietf@ietfa.amsl.com>; Fri,  8 Apr 2016 18:32:40 -0700 (PDT)
Received: from mail-ig0-x234.google.com (mail-ig0-x234.google.com [IPv6:2607:f8b0:4001:c05::234]) (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 2C02C12D15B for <ietf@ietf.org>; Fri,  8 Apr 2016 18:32:40 -0700 (PDT)
Received: by mail-ig0-x234.google.com with SMTP id ui10so30517127igc.1 for <ietf@ietf.org>; Fri, 08 Apr 2016 18:32:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-transfer-encoding; bh=w7qn/IZvAUCn/4fDRbpSu6jlgca8lkTRo7oHFZ4zzp4=; b=gdDZkyFUBQ1D7fTAybYJRdzkw73yGmZl8n+Dcr1CHntQEhd2X5exOALy3Fz1LojuxI SRr2Zr8CJR5g3sJGlG5nKbHV+6eawySOStQTQNWO+g6vGr0D02ZDL2rRHRZYV0aL7iSK 2/JBBvpqgqxvsXdDEFfSdpxdPnm3yReT1VoMq9g6EunFpfOLDe6JSqbmtWFS7XyPMqmW 3K8f3rTNLA7+QZSZvAgBW255ssxMC16fvL1y/4JL9QAZ2T73fPGlsNhW++BZTHikF/7E sfTnWkYXQxGJUoiAU0HiK/VrX9QEqoZwZFWqnWwUwBAmOGb1/SLUjagwDw0TGjREQdXg PDxQ==
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:date :message-id:subject:from:to:cc:content-transfer-encoding; bh=w7qn/IZvAUCn/4fDRbpSu6jlgca8lkTRo7oHFZ4zzp4=; b=i3Hhewx7AKQfXp67vR8zC1TabB6pV4PRdkmI2vSWSkSwnv3xTzh9kNbFivt8nBVtmT 3Cf3roUzGDHan10I+686IoGmrmSj5pshdsFweqie6HC9i939qgkqXpt/dT9AIneXP8eg mHrhsxxuGYEL0GyUkt550KV1NfxdD2+Pwm803guPF7PbMq2Y3McinegEZS2HXjN5GrWv NrQ2hVDCv8PsGa19dTO2WAojTtzuOZZNp/Hr+SeH+mSclVjmz0n1a7XJdQBDXTa4W2bB jr2e3DLExgNei87LccyT+MoaAWbnUbLKI+Pw/aDauFNw6u3Y7w0fxca9537C507qQmk0 jT7g==
X-Gm-Message-State: AD7BkJLi4XfJ8OwXp9Dqta1bbqeCQQM863SNZmPgy0sEd1wmnPUXMTLHlpb6MCBtqBoNwYnah195Hs0S8eunzQ==
MIME-Version: 1.0
X-Received: by 10.50.66.210 with SMTP id h18mr6832037igt.68.1460165559587; Fri, 08 Apr 2016 18:32:39 -0700 (PDT)
Received: by 10.107.129.214 with HTTP; Fri, 8 Apr 2016 18:32:39 -0700 (PDT)
In-Reply-To: <A9E6E707-86DD-4E4A-BD5C-A7B0D6E40398@gmail.com>
References: <CAB75xn6fmj84ROUtG5eUB3GerHx83hrEr3w5vSADY_g=BRg5FA@mail.gmail.com> <1481689286.47880.1460111891664.JavaMail.yahoo@mail.yahoo.com> <alpine.OSX.2.01.1604080418530.36488@rabdullah.local> <594.1460126622@obiwan.sandelman.ca> <5707C458.7080107@dcrocker.net> <20160408150512.6283348.55871.10388@blackberry.com> <A9E6E707-86DD-4E4A-BD5C-A7B0D6E40398@gmail.com>
Date: Sat, 9 Apr 2016 09:32:39 +0800
Message-ID: <CAHkmkws7DWP2eSFCVkv5_MBENL6m5FyCfi-UCfUwOF2XUuA_Og@mail.gmail.com>
Subject: Re: Concerns about Singapore
From: Harish Pillay <harish.pillay@gmail.com>
To: Yoav Nir <ynir.ietf@gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/LSlTZvGoel72ARWzinvJzioq0WQ>
Cc: Michael Richardson <mcr@sandelman.ca>, "ietf@ietf.org Discussion" <ietf@ietf.org>, Dave Crocker <dcrocker@bbiw.net>
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, 09 Apr 2016 01:32:42 -0000

On Fri, Apr 8, 2016 at 11:30 PM, Yoav Nir <ynir.ietf@gmail.com> wrote:
> And I can=E2=80=99t enter Malaysia at all.

<tongue-in-cheek>
unless you say you are a mexican:
http://www.haaretz.com/a-deep-dark-secret-love-affair-1.128671
</tongue-in-cheek>

In the 1967 when Singapore introduced National Service, the Singapore Armed
Forces looked to Israel for training and related assistance. Those who came=
 here
were labeled "Mexicans". I recall my Dad mentioning that to me back then an=
d
later confirmed in memoirs of some of the Singapore cabinet ministers
from that era.

Harish


From nobody Fri Apr  8 21:19:23 2016
Return-Path: <brian.e.carpenter@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 BB36E12D687 for <ietf@ietfa.amsl.com>; Fri,  8 Apr 2016 21:19:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 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, RCVD_IN_DNSWL_LOW=-0.7, 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 K-6bt5OvSKkL for <ietf@ietfa.amsl.com>; Fri,  8 Apr 2016 21:19:20 -0700 (PDT)
Received: from mail-pa0-x22c.google.com (mail-pa0-x22c.google.com [IPv6:2607:f8b0:400e:c03::22c]) (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 23E0F12D0FC for <ietf@ietf.org>; Fri,  8 Apr 2016 21:19:20 -0700 (PDT)
Received: by mail-pa0-x22c.google.com with SMTP id ot11so2353912pab.1 for <ietf@ietf.org>; Fri, 08 Apr 2016 21:19:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=subject:references:from:organization:to:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=ZPIMTu3fEdl6GzJbQ/yHcoyQ4Sj0Vy4Xi5GKE/CzJ1o=; b=Ac+QTnVb7z0tzxh1ePOj9eOx+6TwB+mwK51/aas8NoxDLN0Q1CB7PTctTz+SVo+KCN hgDAGBE8ViK4e84697/vBt3Cqj/xDguF/hTD1rqt6VvROF/8HVCocibgRwur+JIpfgLX LvpRXSr2GGjooJG8t00VBWjhYpHe0FPOrhr9o8if0F5o+TY4q/o3e0bwpTc47Hj41zsz P017atQWzoscZfguXC6qkdymPfIPnBAce1fjoIvnmYg7sMSwk/8v+LMlWBGKMA7kF4z7 Vn3FKURviABzWrkNrv+0AIj+Zo9+olcMBYiS7TJ6v8AfBQJhu8pmykLIEDWRjmXW83M3 AVtQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:references:from:organization:to :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=ZPIMTu3fEdl6GzJbQ/yHcoyQ4Sj0Vy4Xi5GKE/CzJ1o=; b=OkzfT2sdHiZ5y1g9KSMCkIahScdgs5Hcg9luLNbJjcH64yOWdcAIFGncLuzY7sZf8m KD/dF9mEOV+OLHiWp/dbdpEyVmRjjhfIcCDGkIxKgDr+ejgVBYO6bZZJkhEI3Bp9nWxT 0Do4tCvLVrh/JOQU1UI70QxDo7k/lfDUUHAKFFPBNYygG6g8tBZ6hoWytnVWbJzE6Qh+ jjJPfSPKQyduMQJoQfqaAvRos/7p48XEZpUFwV6XSgQvyF4oslyDxZCzZwOo7IsMrLxJ MQnFRgz4Ninoc6mOyzcYSdApO32ICmrqSOEwnt1X+fOXPcsE1dmAFEpF6OtupfkO9mZb jk7A==
X-Gm-Message-State: AD7BkJK4/D3cz7N5fjW4eeTxKXBwl/xMVf8xW2PXZZrG59dpaY440Dw5Odd9kKQvN771bA==
X-Received: by 10.66.121.97 with SMTP id lj1mr17406996pab.51.1460175559762; Fri, 08 Apr 2016 21:19:19 -0700 (PDT)
Received: from ?IPv6:2406:e007:7c81:1:28cc:dc4c:9703:6781? ([2406:e007:7c81:1:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id tn5sm21768293pac.32.2016.04.08.21.19.16 for <ietf@ietf.org> (version=TLSv1/SSLv3 cipher=OTHER); Fri, 08 Apr 2016 21:19:17 -0700 (PDT)
Subject: Re: I-D Action: draft-kucherawy-nomcom-procexp-00.txt
References: <20160408185636.23101.86017.idtracker@ietfa.amsl.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
To: IETF discussion list <ietf@ietf.org>
Message-ID: <570882CE.9010501@gmail.com>
Date: Sat, 9 Apr 2016 16:19:26 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2
MIME-Version: 1.0
In-Reply-To: <20160408185636.23101.86017.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/ohVY1p0qOHeIaE5jHxgAtOPNC5w>
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, 09 Apr 2016 04:19:21 -0000

>    The
>    purpose of this constraint is to prefer community members that have
>    had an opportunity to observe the contributions and conduct of other
>    members directly rather than purely through remote participation.

s/an opportunity/a recent opportunity/

I think that was really the point - prefer people who had recently been
able to make observations of behaviour, and avoid old-timers who don't
participate much any more.

>    3.  A new reason to challenge a selection is that a specific member
>        who has not attended three of the last five meetings of the IETF
>        is not suitable for the NomCom.  Such a challenge must be
>        accompanied by an explanation of why that particular member is
>        not suitable.

I think this is too general and judgmental. Suggestion:

   3.  A new reason to challenge a selection is that a specific member
       who has not attended three of the last five meetings of the IETF
       does not have enough recent participation of any kind to be an
       effective member of the NomCom.  Such a challenge must be
       accompanied by a specific explanation of why the challenger
       considers this to be the case.

I do think one possible outcome needs to be added:

   X.  That the results of the experiment suggest that the changes made
       in Section 2 are damaging and should not be applied again;

I regard this as unlikely, but I disagree with the comment that the
experiment is bound to succeed. I can think of a number of failure
scenarios, several of which would cause the NomCom chair to abort
the process.

Regards
   Brian


From nobody Fri Apr  8 23:05:53 2016
Return-Path: <prvs=19071d52fb=jordi.palet@consulintel.es>
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 251A012D1BF for <ietf@ietfa.amsl.com>; Fri,  8 Apr 2016 23:05:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.899
X-Spam-Level: 
X-Spam-Status: No, score=-101.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_QP_LONG_LINE=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 iwSAV51zZaFH for <ietf@ietfa.amsl.com>; Fri,  8 Apr 2016 23:05:49 -0700 (PDT)
Received: from mail.consulintel.com (mail.consulintel.com [213.0.69.132]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6D1DF12D143 for <ietf@ietf.org>; Fri,  8 Apr 2016 23:05:49 -0700 (PDT)
X-MDAV-Processed: mail.consulintel.com, Sat, 09 Apr 2016 08:05:46 +0200
Received: from [10.10.10.212] by mail.consulintel.com (MDaemon PRO v11.0.3) with ESMTP id md50000389306.msg for <ietf@ietf.org>; Sat, 09 Apr 2016 08:05:44 +0200
X-Spam-Processed: mail.consulintel.com, Sat, 09 Apr 2016 08:05:44 +0200 (not processed: spam filter heuristic analysis disabled)
X-MDOP-RefID: re=0.000,fgs=0 (_st=1 _vt=0 _iwf=0)
X-Return-Path: prvs=19071d52fb=jordi.palet@consulintel.es
X-Envelope-From: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: ietf@ietf.org
User-Agent: Microsoft-MacOutlook/0.0.0.160212
Date: Sat, 09 Apr 2016 08:05:42 +0200
Subject: Re: China
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: IETF discussion list <ietf@ietf.org>
Message-ID: <00D8FABE-3410-4BF5-AC97-6BBECD1E4AB7@consulintel.es>
Thread-Topic: China
References: <0D914666-C3D4-4CCE-AD5E-4E5B34EA1A73@piuha.net> <20160407182936.GA21340@pfrc.org> <CAB75xn780nNDjGa_Cc222J20-+1CCHt09Xp8KHzaK=n0xx51pg@mail.gmail.com> <5706B100.9040509@mnt.se> <CAB75xn6fmj84ROUtG5eUB3GerHx83hrEr3w5vSADY_g=BRg5FA@mail.gmail.com> <5706BA40.3060005@mnt.se> <alpine.DEB.2.02.1604072157240.31096@uplift.swm.pp.se> <A9B63A6D-3102-482F-8FFC-2E57A5FD8336@nic.cz> <CC16B445-2B74-4182-BC58-F9D4BFFA1CCF@chopps.org> <alpine.OSX.2.01.1604080420470.36488@rabdullah.local> <31709.1460126336@obiwan.sandelman.ca> <3CE7670A-DBE4-4B47-BB02-DDD202B99480@sobco.com> <3548A1F1-F0CF-4609-B307-385E2BAEF897@ecs.soton.ac.uk> <EMEW3|1732d6f3eb6217487ddc48b4e7c8e5ces37GYm03tjc|ecs.soton.ac.uk|3548A1F1-F0CF-4609-B307-385E2BAEF897@ecs.soton.ac.uk> <F377B008-6D7B-4B2B-ADFC-461CBAE43E23@isoc.org>
In-Reply-To: <F377B008-6D7B-4B2B-ADFC-461CBAE43E23@isoc.org>
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/nF-4fnE7tf-QIY6Ve2lUn4Bch4E>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: jordi.palet@consulintel.es
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, 09 Apr 2016 06:05:52 -0000

However San Diego venue is not downtown, which seems it was the main excuse=
 to avoid having it in Madrid, despite the public connections (several bus l=
ines and cheap taxi) between the Madrid venue and downtown is by far much be=
tter than San Diego.

Regards,
Jordi









-----Mensaje original-----
De: ietf <ietf-bounces@ietf.org> en nombre de Ray Pelletier <rpelletier@iso=
c.org>
Responder a: <rpelletier@isoc.org>
Fecha: viernes, 8 de abril de 2016, 17:50
Para: Tim Chown <tjc@ecs.soton.ac.uk>
CC: Michael Richardson <mcr+ietf@sandelman.ca>, "ietf@ietf.org Discussion" =
<ietf@ietf.org>
Asunto: Re: China

>Tim,
>
>> On Apr 8, 2016, at 12:34 PM, Tim Chown <tjc@ecs.soton.ac.uk> wrote:
>>=20
>> On 8 Apr 2016, at 16:14, Scott Bradner <sob@sobco.com> wrote:
>>>=20
>>> some on the IAOC wanted to go back to SD for IETF 100 but the facilitie=
s were not available=20
>>> at the right time
>>=20
>> Ah, I was expecting the plenary drumroll to reveal just this - IETF100 a=
t San Diego.=20
>>=20
>> A shame it couldn't happen, but perhaps an indicator we do need to keep =
planning 3-4 years out.
>>=20
>> And for the right venue, we should be able to slide the dates forwards/b=
ack a week or two.=20
>
>We aggressively pursued venues in San Diego, including the possibly of shi=
fting dates before=20
>and after the scheduled calendar dates.  The rule is we don=E2=80=99t change tho=
se dates, but there
>was a willingness to consider that for IETF 100. =20
>
>San Diego is one of the most popular venues in the US, so it turned out th=
at around our dates=20
>there were already city-wide events that made it impossible to secure a ve=
nue and necessary=20
>overflow hotels.
>
>Ray
>
>>=20
>> Tim
>>=20
>>>=20
>>> Scott
>>>=20
>>>> On Apr 8, 2016, at 10:38 AM, Michael Richardson <mcr+ietf@sandelman.ca=
> wrote:
>>>>=20
>>>>=20
>>>> Ole Jacobsen <olejacobsen@me.com> wrote:
>>>>> I am sorry to hear that. Our "open and inclusive process" comprises
>>>>> many participants from China who have traditionally faced harsh and
>>>>> unpredictable visa problems in North America. In fairness to them, we
>>>>> held that meeting in Beijing. Note that we did so following an
>>>>> extensive discussion on the IETF mailing list and after negotiating
>>>>> the removal of a rather ominous hotel clause, as well as an unfiltere=
d
>>>>> network in the meeting venue.
>>>>=20
>>>> Yes, and we did this openly, and I don't feel we did the same thing he=
re.
>>>> And there were still surprises, I'm told.
>>>>=20
>>>> I was very surprised at the announcement for 100.
>>>> I kinda thought we should go back to San Diego as for IETF 1.
>>>> (well. Maybe IETF101 should be same as IETF 1... maybe IETF 100 should=
 be
>>>> same as IETF 0, and be entirely virtual...)
>>>>=20
>>>> (I didn't go because I generally have funds for two IETFs a year,
>>>> and given the hassle, and my concerns about what I would eat, it was s=
impler
>>>> to skip.  I skipped BA for a combination of economic, but primarily fa=
mily reasons)
>>>>=20
>>>>=20
>>>> --
>>>> Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
>>>> -=3D IPv6 IoT consulting =3D-
>>>>=20
>>>>=20
>>>>=20
>>>=20
>>=20
>
>



From nobody Sat Apr  9 00:49:55 2016
Return-Path: <rpelletier@isoc.org>
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 BE4BF12D0CF for <ietf@ietfa.amsl.com>; Sat,  9 Apr 2016 00:49:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.903
X-Spam-Level: 
X-Spam-Status: No, score=-101.903 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=isoc.onmicrosoft.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 yGD3PryZy5QC for <ietf@ietfa.amsl.com>; Sat,  9 Apr 2016 00:49:51 -0700 (PDT)
Received: from na01-by2-obe.outbound.protection.outlook.com (mail-by2on0055.outbound.protection.outlook.com [207.46.100.55]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 81D3812D16E for <ietf@ietf.org>; Sat,  9 Apr 2016 00:49:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=isoc.onmicrosoft.com;  s=selector1-isoc-org; h=From:To:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=oXWnY/BZy8Ug0Qha0274ybsJfTqCJIexZkB+hUNFVDk=; b=AUgDaGnkrvEkYxdbhxWDMclC6prZbKAE1Kp/2GnvAf2N90s9vty8RujLyCFO9C0GY+TJg488ayzlmeUQ0V6ZxHpXOIHyWZMJLVef5h177MTRDAstT2he+4DHOsdsp/GXktxbE/Ty1sWIHQeJRF1MT4C8ed+8oqn36auU6kUbi5M=
Authentication-Results: consulintel.es; dkim=none (message not signed) header.d=none;consulintel.es; dmarc=none action=none header.from=isoc.org;
Received: from [IPv6:2001:67c:370:144:3527:3c66:db48:a0b5] (2001:67c:370:144:3527:3c66:db48:a0b5) by BLUPR0601MB1556.namprd06.prod.outlook.com (10.163.211.146) with Microsoft SMTP Server (TLS) id 15.1.453.26; Sat, 9 Apr 2016 07:49:47 +0000
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0 (Mac OS X Mail 9.2 \(3112\))
Subject: Re: China
From: Ray Pelletier <rpelletier@isoc.org>
In-Reply-To: <00D8FABE-3410-4BF5-AC97-6BBECD1E4AB7@consulintel.es>
Date: Sat, 9 Apr 2016 04:51:33 -0300
Content-Transfer-Encoding: quoted-printable
Message-ID: <E49960BE-D8E2-45B5-AB2A-AE1F57511B84@isoc.org>
References: <0D914666-C3D4-4CCE-AD5E-4E5B34EA1A73@piuha.net> <20160407182936.GA21340@pfrc.org> <CAB75xn780nNDjGa_Cc222J20-+1CCHt09Xp8KHzaK=n0xx51pg@mail.gmail.com> <5706B100.9040509@mnt.se> <CAB75xn6fmj84ROUtG5eUB3GerHx83hrEr3w5vSADY_g=BRg5FA@mail.gmail.com> <5706BA40.3060005@mnt.se> <alpine.DEB.2.02.1604072157240.31096@uplift.swm.pp.se> <A9B63A6D-3102-482F-8FFC-2E57A5FD8336@nic.cz> <CC16B445-2B74-4182-BC58-F9D4BFFA1CCF@chopps.org> <alpine.OSX.2.01.1604080420470.36488@rabdullah.local> <31709.1460126336@obiwan.sandelman.ca> <3CE7670A-DBE4-4B47-BB02-DDD202B99480@sobco.com> <3548A1F1-F0CF-4609-B307-385E2BAEF897@ecs.soton.ac.uk> <EMEW3|1732d6f3eb6217487ddc48b4e7c8e5ces37GYm03tjc|ecs.soton.ac.uk|3548A1F1-F0CF-4609-B307-385E2BAEF897@ecs.soton.ac.uk> <F377B008-6D7B-4B2B-ADFC-461CBAE43E23@isoc.org> <00D8FABE-3410-4BF5-AC97-6BBECD1E4AB7@consulintel.es>
To: <jordi.palet@consulintel.es>
X-Mailer: Apple Mail (2.3112)
X-Originating-IP: [2001:67c:370:144:3527:3c66:db48:a0b5]
X-ClientProxiedBy: CY1PR08CA0018.namprd08.prod.outlook.com (10.163.94.156) To BLUPR0601MB1556.namprd06.prod.outlook.com (10.163.211.146)
X-MS-Office365-Filtering-Correlation-Id: c46248f7-1a10-4763-e5c4-08d3604b86cd
X-Microsoft-Exchange-Diagnostics: 1; BLUPR0601MB1556; 2:nzQmbcxJUF4Y8oWHIOQLhf2vjgnKWUCDWHP4TXU0v0kqdz9pqYkeHm/JtuQKjKr3/I85cMfFzxTICBZq1wYKxGV/I1WQAXAArU3IkjzCep9/67MrqqAn+s0HTXyEkon846fb9FrmgRqutIFwyadPp+YQFopwOF1bW2Vuo/TihUq80pSg5W8qrR/z+TWilpYT; 3:uLBvKjeP6Y9diIJtF0R5P0OGC6SP7c0Lo0piOWdJsk/aJthNF7sYpLScljA8TE5QhEgyln07hkQSH2cTXH6O/NKeNGjaAkj/URK+3W0X/28CTwsSGC8Ud6ghMJH3wVTG; 25:1IrhA7vgfPyHeEFJlmGxzfFYwGu+VgaZbxMIBnJWlrZvn5YrvOcJUk3Zvrmo5idNcmmAtK8lD/EIpqcaInn8sqSYjZNxs0ogQ5la3ASgsvs88GBZx6wOSGTxXKcR0uEWCDQpRC4bskTG/cd97zHEt6UPsRXYm4SV/lO51DyL4TDK7C8U7z3BdTS0p3TwB5rhiL+6HqmaI2Xo2GPIAK3sMAxpvRIrKXnaOu/8FcLs1z4OLQm9EAvx8RrsNoxpd58pCc0iD3qGue9RlicTmE6HrlbUFwoGzSCNIVGtvo/DOSlCWF+IpP5bi7dPgjFXYsbpyq7y+10xDA9ucQb4o3kXCw==
X-Microsoft-Antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:BLUPR0601MB1556;
X-Microsoft-Exchange-Diagnostics: 1; BLUPR0601MB1556; 20:ED6ozjp2d1yyA49EmPi3Z/wSAiTpCkpKjz3zhJZhQTY5Blg08ZFGKN95boN4QwqAFkh1SAj6kajhi9iGQB67PiNji/HHWDsna7Z3C3/OB1bWEdV26rr1jG8Xv0UUER+8Qc5Ie9p8bHQEg6EvZihvtrWjj9Da+ISSAPdDfJ2WLXfyvxa+rDWUepyhQD+06weDdoilsvzqGbGr61l+nuVaIaPO/lOxyWV3RG7zcuuQw6baDZ1D349XvsjqSGHbAoDvAOoEQPEh1KMJZaKDEd0jKqjieLlE5k1g4EgMjV0u11IcdLMCc2NuqMKE3cBIUrYnyOYsw+QvALno12XrkK1D/tO0B3AUoo6TzsQIRJy2XurD6X4J1YudHvwL8WHf3uPDs/kK02KBX8KLcib1e1xeRPBY126VNBefi/sZN87sWqfsUX8gp/uzozTiU2a0LlyfyI1wlgh7FjIt7i+3mjvDwgpK9buTRxEEfDaYmegcTTtJBgHk1qCVYceSFIERZN+4; 4:vHZfyLDfl7iF/JxK5CbFZA8nGb1EtpYM0A0w/TSlS9fNN2NRhfxSUJj6F4xwzno7/STfLLwwvWEZq7pI4k+MOt+gllVtrBQdgoLX26R5x8p7Gonb3YNCcT/r8+/WwUqdSHc+BpXIM9vdfVcq0RlwuUN8evFovYhB8zDjD11H08bD6UrX6YyE41ypjHZTBVwBoKw7o8cLe/sm7Bi+o6bfaeh3w79Jj3nP/8oOKMOfMYs4IW3Y9WpC1sW4JxCdK6lUViNoltq2l9HMN1s06ZimGP5yQfml5GiTSwacnOJi29EAMu81iwA3zYOE4vQBPaEcKUMOckcz07t9iDn1ePfQ9uJOraKfxfsCxpHZTYG2LkK4N4GVzFRPmHrgos56UViV
X-Microsoft-Antispam-PRVS: <BLUPR0601MB155675DD12936AFC5A5FD48CB0920@BLUPR0601MB1556.namprd06.prod.outlook.com>
X-Exchange-Antispam-Report-Test: UriScan:;
X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(601004)(2401047)(5005006)(8121501046)(10201501046)(3002001); SRVR:BLUPR0601MB1556; BCL:0; PCL:0; RULEID:; SRVR:BLUPR0601MB1556; 
X-Forefront-PRVS: 0907F58A24
X-Forefront-Antispam-Report: SFV:NSPM; SFS:(10009020)(4630300001)(6009001)(59124004)(377454003)(24454002)(92566002)(2906002)(81166005)(57306001)(47776003)(23676002)(3480700003)(36756003)(50226001)(5008740100001)(110136002)(19580395003)(4326007)(19580405001)(189998001)(82746002)(33656002)(42186005)(6116002)(2950100001)(586003)(1096002)(221733001)(83716003)(77096005)(86362001)(50466002)(50986999)(76176999)(2351001)(5004730100002)(3826002)(104396002); DIR:OUT; SFP:1101; SCL:1; SRVR:BLUPR0601MB1556; H:[IPv6:2001:67c:370:144:3527:3c66:db48:a0b5]; FPR:; SPF:None; MLV:sfv; LANG:en; 
X-Microsoft-Exchange-Diagnostics: =?utf-8?B?MTtCTFVQUjA2MDFNQjE1NTY7MjM6QTlwTVNoZ3ZGYWczK2hEVUNtUG1IMVoz?= =?utf-8?B?a1N1cURFNTlmMEtqLzhtUFFpZkM3cVJJZGlMSTVUb01KU0NLaE5MQllzZFlJ?= =?utf-8?B?K0pjcERhY0lNcUg2UnZCVmV2Uk96ZjFrZ0hnZkt2VWRCQkdQZmZMWGVGK1F2?= =?utf-8?B?cml3QUowSTVOdVNJMUVZZ3ZpalViN0xoUk12KzNBdk1QSXUvaDBDVkorVkJm?= =?utf-8?B?TEQ2cTVTSC96Q2Z4UEdNcERWNTQ5Y0w3Rm0vL0czQjhGZzh1dWM4bkJhSWtt?= =?utf-8?B?TUhXa3ZYMU0vV1U2NkZBRDZsSTNHYlhscXlXZVdENWpxZTQ4UHJlMlgzd25j?= =?utf-8?B?bmRCUWc5ZXJsRFdhemMwWE0zQ1FuUlQ0YlBlc3R2ekZzcHo4cENDbmtrUHh6?= =?utf-8?B?ZnV5cVo3ZSsrUy9ua2Fzd2t3TXlsRzRiRkpSWEhEdVJyU0EreFo5YlBSeWlJ?= =?utf-8?B?cjJTc3Jjd0NmSVc3K0FSRlNsZnc1QUlxMkpRTkErMXBMWmVzdjNUeFhjZTFE?= =?utf-8?B?ZS9wWko1MjJLczE2YUZlcHBnYU5XVzJBRmtUZThreVNDTno5YkN4U2JKYVRv?= =?utf-8?B?NFFNdXZ2OG10NEpxMFN2SUlSSXRaTCtXNERNUDBwakxQU29YdDNHajZjRVhG?= =?utf-8?B?NER6ZkFkNUk4Qk8yUVM5TjZnV2IrY2xFWkFOc1oxdytmM0V5eTJDeGFsSlJN?= =?utf-8?B?SzNzWFRCWmIreEFQODNNMGlVZnYzejIyVVB5N1JPMEQ2RVFHeFNlcTloanZJ?= =?utf-8?B?M0hWMGNFOG9GZ0FkYkplOHBhZExsQ1dxMSttUk4zTGsvM20waUVhZFNFMmk0?= =?utf-8?B?QVBkUDFjZDg3WHROQy82RWNldlk4SGJEVVRHSzg4eFNVdllYT0pXY3ZCaDJE?= =?utf-8?B?SUtqcUZQZlMrd2M0UG9rdHIvblA5VjYxMGpCaTFPTEcyWUMwV3lGaUhrazEz?= =?utf-8?B?SmoycEZpeWlXZVFZWVYxeXJRU0s0RVNQbnZDWTlEMUQyT3NpT2VnQWp0Zm5Q?= =?utf-8?B?MkZrbm5rcldRVmkyT0pLQXllWXE4WWJYbmt6WktZY3p5ejVxSjZZNm9xN3Vk?= =?utf-8?B?aEhLeUNyZ0hHNDZuOEVaYTVMVDM3eTQvcWpsQXN2RjVwbHdQa052dU9qZisw?= =?utf-8?B?c0JROHhYbTlYYVZWZXBxREErRjZWdllvVkd0aVpodTRLWGpJSm1rSDM4TEhH?= =?utf-8?B?M0xtcjEwSjJsOUlpMlRBVXpaUjVWMHNWbUdidVl1ZzlpNktmUTU3SGxKR0pa?= =?utf-8?B?czNsMUN6WWE4cmJxeWluOFU3Y2hPaFVKempQWGozS0tBaXFqc2lrSGlHSUhj?= =?utf-8?B?RDIzeExMNVB4bzhQbEpwWEt5aXBpUW1VcUJpK2ZrSWQ4QmRkbG1jV1ViUFE0?= =?utf-8?Q?jGmJP4YNjI?=
X-Microsoft-Exchange-Diagnostics: 1; BLUPR0601MB1556; 5:G9FnaS1PHTvOvNYBMP/VMXoKz3jl/LNdJTW9OJzw1E3Az81yu/xp/P68PuyQ1Xglsg6+J0uxzLZoRRaXAStaaNcmzI+OD8RO9LrpDBnjcB8iO4fbhbK3WEgG9yTLeLRAKStjtPXDp1oJPB2v3NB15A==; 24:pJS3NAq2dnqT/nCbbLe+3Tn/qH/Z0y0FFtrSiVUgftqZbB1l8gzXGvm2fy02ipx7rfKRfddrLzoutYRp5jMpAahp73Kmk0EfgcW8QVnNzjk=
SpamDiagnosticOutput: 1:23
SpamDiagnosticMetadata: NSPM
X-OriginatorOrg: isoc.org
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 09 Apr 2016 07:49:47.9669 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BLUPR0601MB1556
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/usZVrxE2dyzHdLpdCQ6HTC6k9Ps>
Cc: IETF discussion list <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: Sat, 09 Apr 2016 07:49:53 -0000

Jordi

San Diego has changed.

There is a Convention Center downtown surrounded by hotels.

We would not have to be down near the marina and isolated.

Ray
> On Apr 9, 2016, at 3:05 AM, JORDI PALET MARTINEZ =
<jordi.palet@consulintel.es> wrote:
>=20
> However San Diego venue is not downtown, which seems it was the main =
excuse to avoid having it in Madrid, despite the public connections =
(several bus lines and cheap taxi) between the Madrid venue and downtown =
is by far much better than San Diego.
>=20
> Regards,
> Jordi
>=20
>=20
>=20
>=20
>=20
>=20
>=20
>=20
>=20
> -----Mensaje original-----
> De: ietf <ietf-bounces@ietf.org> en nombre de Ray Pelletier =
<rpelletier@isoc.org>
> Responder a: <rpelletier@isoc.org>
> Fecha: viernes, 8 de abril de 2016, 17:50
> Para: Tim Chown <tjc@ecs.soton.ac.uk>
> CC: Michael Richardson <mcr+ietf@sandelman.ca>, "ietf@ietf.org =
Discussion" <ietf@ietf.org>
> Asunto: Re: China
>=20
>> Tim,
>>=20
>>> On Apr 8, 2016, at 12:34 PM, Tim Chown <tjc@ecs.soton.ac.uk> wrote:
>>>=20
>>> On 8 Apr 2016, at 16:14, Scott Bradner <sob@sobco.com> wrote:
>>>>=20
>>>> some on the IAOC wanted to go back to SD for IETF 100 but the =
facilities were not available=20
>>>> at the right time
>>>=20
>>> Ah, I was expecting the plenary drumroll to reveal just this - =
IETF100 at San Diego.=20
>>>=20
>>> A shame it couldn't happen, but perhaps an indicator we do need to =
keep planning 3-4 years out.
>>>=20
>>> And for the right venue, we should be able to slide the dates =
forwards/back a week or two.=20
>>=20
>> We aggressively pursued venues in San Diego, including the possibly =
of shifting dates before=20
>> and after the scheduled calendar dates.  The rule is we don=E2=80=99t =
change those dates, but there
>> was a willingness to consider that for IETF 100. =20
>>=20
>> San Diego is one of the most popular venues in the US, so it turned =
out that around our dates=20
>> there were already city-wide events that made it impossible to secure =
a venue and necessary=20
>> overflow hotels.
>>=20
>> Ray
>>=20
>>>=20
>>> Tim
>>>=20
>>>>=20
>>>> Scott
>>>>=20
>>>>> On Apr 8, 2016, at 10:38 AM, Michael Richardson =
<mcr+ietf@sandelman.ca> wrote:
>>>>>=20
>>>>>=20
>>>>> Ole Jacobsen <olejacobsen@me.com> wrote:
>>>>>> I am sorry to hear that. Our "open and inclusive process" =
comprises
>>>>>> many participants from China who have traditionally faced harsh =
and
>>>>>> unpredictable visa problems in North America. In fairness to =
them, we
>>>>>> held that meeting in Beijing. Note that we did so following an
>>>>>> extensive discussion on the IETF mailing list and after =
negotiating
>>>>>> the removal of a rather ominous hotel clause, as well as an =
unfiltered
>>>>>> network in the meeting venue.
>>>>>=20
>>>>> Yes, and we did this openly, and I don't feel we did the same =
thing here.
>>>>> And there were still surprises, I'm told.
>>>>>=20
>>>>> I was very surprised at the announcement for 100.
>>>>> I kinda thought we should go back to San Diego as for IETF 1.
>>>>> (well. Maybe IETF101 should be same as IETF 1... maybe IETF 100 =
should be
>>>>> same as IETF 0, and be entirely virtual...)
>>>>>=20
>>>>> (I didn't go because I generally have funds for two IETFs a year,
>>>>> and given the hassle, and my concerns about what I would eat, it =
was simpler
>>>>> to skip.  I skipped BA for a combination of economic, but =
primarily family reasons)
>>>>>=20
>>>>>=20
>>>>> --
>>>>> Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software =
Works
>>>>> -=3D IPv6 IoT consulting =3D-
>>>>>=20
>>>>>=20
>>>>>=20
>>>>=20
>>>=20
>>=20
>>=20
>=20
>=20


From nobody Sat Apr  9 01:06:16 2016
Return-Path: <stewart.bryant@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 6F53012D09D for <ietf@ietfa.amsl.com>; Sat,  9 Apr 2016 01:06:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 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, RCVD_IN_DNSWL_LOW=-0.7, 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 dxBsOw0n8OXs for <ietf@ietfa.amsl.com>; Sat,  9 Apr 2016 01:06:14 -0700 (PDT)
Received: from mail-wm0-x22b.google.com (mail-wm0-x22b.google.com [IPv6:2a00:1450:400c:c09::22b]) (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 F187A12D0C7 for <ietf@ietf.org>; Sat,  9 Apr 2016 01:06:13 -0700 (PDT)
Received: by mail-wm0-x22b.google.com with SMTP id u206so46525147wme.1 for <ietf@ietf.org>; Sat, 09 Apr 2016 01:06:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=/anfdsdk8nBmEAC4jl60V7igW1kqDJC9/U7ERBltLjA=; b=d4Q1/RqvaUTT9I2vVWdRXTzMSHwVFtj/pXJw5OvN0ltxbfdgUmaWsJYeRs6sZzLabq KD3g74+eGyCB12DqGDMBARPmNnAFrG2Zdruc5nFNeRYwF1SA8UjEVPuNHvWEoY+v6Tk0 b0+21tcUsC6d+Inv2KvMCTu27y69huzFNBmEr/KBBDCZvp7Ymf1kkrtmRFpMmxQ7YIev HKQbf3NNEf7SwkfhGAOJO1vybYPwr+fJ+JO4BFp/GQ4+9juECLDJIaAa5NhgItcmfpAW Ap7oDbId4+jYiKjb/urG8BRo/7OeKT+IPQW6Qnbap4n9V+fy2Be+DGbk1Uej+jCEqqPV iL+A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=/anfdsdk8nBmEAC4jl60V7igW1kqDJC9/U7ERBltLjA=; b=MCgiTGSWSQwZ6nLNgiJDzc99Vv6Ff7aynxPmQIZzcWO+nCqhDfWxfgjBCPc/TshQte K9WaPKY3mekag0TmWuCPrURccW2NritwPT0DJcjpZxONVGvYXgXzOt6mjjskWXs+w5rg DBjcQbaSHqgTLymwhXmRiZzAM8vvylXw2bQNfvQinNMClT4yUQqQ72IW7gEv5XnkruGN JTZi0SP2PYmQWWND/e5+sOi9+Fb1En8RM6Eg6uu30/b9qnEN4f2kIiyY59pWAjOyVSQ0 iMjHYypA0RIaLUyxp4JSajXz+9tIESSuYW4AfY7DPXUrCuf4yyqTjChcv+6B+lEQb2d2 w54w==
X-Gm-Message-State: AD7BkJJkaJRvFWgrXb/uoLuo1EZ06aQpoUgNcyHj3igYLxvcCItiGopoIKS76RtrUFelTA==
X-Received: by 10.194.205.103 with SMTP id lf7mr13452204wjc.147.1460189172407;  Sat, 09 Apr 2016 01:06:12 -0700 (PDT)
Received: from [192.168.2.126] (host213-123-124-182.in-addr.btopenworld.com. [213.123.124.182]) by smtp.gmail.com with ESMTPSA id qb8sm17019795wjc.24.2016.04.09.01.06.10 (version=TLSv1/SSLv3 cipher=OTHER); Sat, 09 Apr 2016 01:06:10 -0700 (PDT)
Subject: Re: China
To: Ray Pelletier <rpelletier@isoc.org>, jordi.palet@consulintel.es
References: <0D914666-C3D4-4CCE-AD5E-4E5B34EA1A73@piuha.net> <20160407182936.GA21340@pfrc.org> <CAB75xn780nNDjGa_Cc222J20-+1CCHt09Xp8KHzaK=n0xx51pg@mail.gmail.com> <5706B100.9040509@mnt.se> <CAB75xn6fmj84ROUtG5eUB3GerHx83hrEr3w5vSADY_g=BRg5FA@mail.gmail.com> <5706BA40.3060005@mnt.se> <alpine.DEB.2.02.1604072157240.31096@uplift.swm.pp.se> <A9B63A6D-3102-482F-8FFC-2E57A5FD8336@nic.cz> <CC16B445-2B74-4182-BC58-F9D4BFFA1CCF@chopps.org> <alpine.OSX.2.01.1604080420470.36488@rabdullah.local> <31709.1460126336@obiwan.sandelman.ca> <3CE7670A-DBE4-4B47-BB02-DDD202B99480@sobco.com> <3548A1F1-F0CF-4609-B307-385E2BAEF897@ecs.soton.ac.uk> <EMEW3|1732d6f3eb6217487ddc48b4e7c8e5ces37GYm03tjc|ecs.soton.ac.uk|3548A1F1-F0CF-4609-B307-385E2BAEF897@ecs.soton.ac.uk> <F377B008-6D7B-4B2B-ADFC-461CBAE43E23@isoc.org> <00D8FABE-3410-4BF5-AC97-6BBECD1E4AB7@consulintel.es> <E49960BE-D8E2-45B5-AB2A-AE1F57511B84@isoc.org>
From: Stewart Bryant <stewart.bryant@gmail.com>
Message-ID: <5708B7F0.8060007@gmail.com>
Date: Sat, 9 Apr 2016 09:06:08 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.7.0
MIME-Version: 1.0
In-Reply-To: <E49960BE-D8E2-45B5-AB2A-AE1F57511B84@isoc.org>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/gm-c7yh5S1VeFodXpJH6ZdKuzik>
Cc: IETF discussion list <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: Sat, 09 Apr 2016 08:06:15 -0000

Oh, shame, I liked it by the marina.

Stewart



From nobody Sat Apr  9 04:41:08 2016
Return-Path: <olejacobsen@me.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 49A1B12D5E5 for <ietf@ietfa.amsl.com>; Sat,  9 Apr 2016 04:41:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.631
X-Spam-Level: 
X-Spam-Status: No, score=-2.631 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 zpZqVRstZ9R4 for <ietf@ietfa.amsl.com>; Sat,  9 Apr 2016 04:41:04 -0700 (PDT)
Received: from mr11p00im-asmtp003.me.com (mr11p00im-asmtp003.me.com [17.110.69.254]) (using TLSv1.2 with cipher DHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 501C912D171 for <ietf@ietf.org>; Sat,  9 Apr 2016 04:41:04 -0700 (PDT)
Received: from [10.1.10.8] (173-11-110-134-SFBA.hfc.comcastbusiness.net [173.11.110.134]) by mr11p00im-asmtp003.me.com (Oracle Communications Messaging Server 7.0.5.36.0 64bit (built Sep 8 2015)) with ESMTPSA id <0O5D004K574B9X00@mr11p00im-asmtp003.me.com> for ietf@ietf.org; Sat, 09 Apr 2016 11:41:04 +0000 (GMT)
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, definitions=2016-04-09_09:,, signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 clxscore=1015 suspectscore=0 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1510270003 definitions=main-1604090174
Date: Sat, 09 Apr 2016 04:40:58 -0700 (PDT)
From: Ole Jacobsen <olejacobsen@me.com>
To: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
Subject: Re: China
In-reply-to: <00D8FABE-3410-4BF5-AC97-6BBECD1E4AB7@consulintel.es>
Message-id: <alpine.OSX.2.01.1604090440270.40760@rabdullah.local>
References: <0D914666-C3D4-4CCE-AD5E-4E5B34EA1A73@piuha.net> <20160407182936.GA21340@pfrc.org> <CAB75xn780nNDjGa_Cc222J20-+1CCHt09Xp8KHzaK=n0xx51pg@mail.gmail.com> <5706B100.9040509@mnt.se> <CAB75xn6fmj84ROUtG5eUB3GerHx83hrEr3w5vSADY_g=BRg5FA@mail.gmail.com> <5706BA40.3060005@mnt.se> <alpine.DEB.2.02.1604072157240.31096@uplift.swm.pp.se> <A9B63A6D-3102-482F-8FFC-2E57A5FD8336@nic.cz> <CC16B445-2B74-4182-BC58-F9D4BFFA1CCF@chopps.org> <alpine.OSX.2.01.1604080420470.36488@rabdullah.local> <31709.1460126336@obiwan.sandelman.ca> <3CE7670A-DBE4-4B47-BB02-DDD202B99480@sobco.com> <3548A1F1-F0CF-4609-B307-385E2BAEF897@ecs.soton.ac.uk> <EMEW3|1732d6f3eb6217487ddc48b4e7c8e5ces37GYm03tjc|ecs.soton.ac.uk|3548A1F1-F0CF-4609-B307-385E2BAEF897@ecs.soton.ac.uk> <F377B008-6D7B-4B2B-ADFC-461CBAE43E23@isoc.org> <00D8FABE-3410-4BF5-AC97-6BBECD1E4AB7@consulintel.es>
User-Agent: Alpine 2.01 (OSX 1266 2009-07-14)
MIME-version: 1.0
Content-type: TEXT/PLAIN; charset=US-ASCII
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/Xf3Unz-zRKxbkdIM2tyclsNvA_w>
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: Ole Jacobsen <olejacobsen@me.com>
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, 09 Apr 2016 11:41:06 -0000

On Sat, 9 Apr 2016, JORDI PALET MARTINEZ wrote:

> However San Diego venue is not downtown, which seems it was the main 
> excuse to avoid having it in Madrid, despite the public connections 
> (several bus lines and cheap taxi) between the Madrid venue and 
> downtown is by far much better than San Diego.
> 
> Regards,
> Jordi
> 

There is more than one venue in San Diego.


From nobody Sat Apr  9 05:05:24 2016
Return-Path: <randy@psg.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 E469612D168 for <ietf@ietfa.amsl.com>; Sat,  9 Apr 2016 05:05:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.91
X-Spam-Level: 
X-Spam-Status: No, score=-6.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, T_RP_MATCHES_RCVD=-0.01] 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 2gqMCpP4lZpu for <ietf@ietfa.amsl.com>; Sat,  9 Apr 2016 05:05:21 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9650512D15A for <ietf@ietf.org>; Sat,  9 Apr 2016 05:05:21 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com) by ran.psg.com with esmtp (Exim 4.82) (envelope-from <randy@psg.com>) id 1aordf-0007l4-Og; Sat, 09 Apr 2016 12:05:19 +0000
Date: Sat, 09 Apr 2016 09:05:22 -0300
Message-ID: <m27fg77zst.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Michael Richardson <mcr+ietf@sandelman.ca>
Subject: Re: Concerns about Singapore
In-Reply-To: <16925.1460122349@obiwan.sandelman.ca>
References: <0D914666-C3D4-4CCE-AD5E-4E5B34EA1A73@piuha.net> <20160407182936.GA21340@pfrc.org> <CAB75xn780nNDjGa_Cc222J20-+1CCHt09Xp8KHzaK=n0xx51pg@mail.gmail.com> <5706B100.9040509@mnt.se> <CAB75xn6fmj84ROUtG5eUB3GerHx83hrEr3w5vSADY_g=BRg5FA@mail.gmail.com> <5706BA40.3060005@mnt.se> <alpine.DEB.2.02.1604072157240.31096@uplift.swm.pp.se> <A9B63A6D-3102-482F-8FFC-2E57A5FD8336@nic.cz> <16925.1460122349@obiwan.sandelman.ca>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/3anDO7rNiTjy6EvWsBhBi7wm1IE>
Cc: "ietf@ietf.org 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: Sat, 09 Apr 2016 12:05:23 -0000

> yes, we tried that.  My impression is that there were two changes we
> made, one was known in advance (closed network)

the ietf network in beijing was open as normal, thanks to the work of
many.  it had registration, as had maastricht.  and we have passwording
now.

> the other was unknown (badges being checked)

cf. rfid discussion in hiroshima.  checking badges has a varied history.
beijing was conservative.

randy


From nobody Sat Apr  9 05:06:51 2016
Return-Path: <randy@psg.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 A404612D15A for <ietf@ietfa.amsl.com>; Sat,  9 Apr 2016 05:06:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.91
X-Spam-Level: 
X-Spam-Status: No, score=-6.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, T_RP_MATCHES_RCVD=-0.01] 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 qnsUckRv23EV for <ietf@ietfa.amsl.com>; Sat,  9 Apr 2016 05:06:48 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DEEF712D169 for <ietf@ietf.org>; Sat,  9 Apr 2016 05:06:47 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com) by ran.psg.com with esmtp (Exim 4.82) (envelope-from <randy@psg.com>) id 1aorev-0007lX-HD; Sat, 09 Apr 2016 12:06:37 +0000
Date: Sat, 09 Apr 2016 09:06:39 -0300
Message-ID: <m260vr7zqo.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Yoav Nir <ynir.ietf@gmail.com>
Subject: Re: Concerns about Singapore
In-Reply-To: <A9E6E707-86DD-4E4A-BD5C-A7B0D6E40398@gmail.com>
References: <CAB75xn6fmj84ROUtG5eUB3GerHx83hrEr3w5vSADY_g=BRg5FA@mail.gmail.com> <1481689286.47880.1460111891664.JavaMail.yahoo@mail.yahoo.com> <alpine.OSX.2.01.1604080418530.36488@rabdullah.local> <594.1460126622@obiwan.sandelman.ca> <5707C458.7080107@dcrocker.net> <20160408150512.6283348.55871.10388@blackberry.com> <A9E6E707-86DD-4E4A-BD5C-A7B0D6E40398@gmail.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.7 - "Harue")
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/c9QPoCTxcmB-ooLLcGXQWsq9c_E>
Cc: Michael Richardson <mcr@sandelman.ca>, "ietf@ietf.org Discussion" <ietf@ietf.org>, Dave Crocker <dcrocker@bbiw.net>
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, 09 Apr 2016 12:06:49 -0000

> And I can=E2=80=99t enter Malaysia at all.

what you mean is that the malaysians have you go through a visa process
as the emericans do to the chinese, ...

randy


From nobody Sat Apr  9 05:08:07 2016
Return-Path: <randy@psg.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 588ED12D60A for <ietf@ietfa.amsl.com>; Sat,  9 Apr 2016 05:08:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.91
X-Spam-Level: 
X-Spam-Status: No, score=-6.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, T_RP_MATCHES_RCVD=-0.01] 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 iYlmyQMHyk_U for <ietf@ietfa.amsl.com>; Sat,  9 Apr 2016 05:08:05 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3478012D169 for <ietf@ietf.org>; Sat,  9 Apr 2016 05:08:05 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com) by ran.psg.com with esmtp (Exim 4.82) (envelope-from <randy@psg.com>) id 1aorgG-0007lu-L9; Sat, 09 Apr 2016 12:08:01 +0000
Date: Sat, 09 Apr 2016 09:08:01 -0300
Message-ID: <m24mbb7zoe.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Ole Jacobsen <olejacobsen@me.com>
Subject: Re: Concerns about Singapore
In-Reply-To: <alpine.OSX.2.01.1604081315580.38286@rabdullah.local>
References: <CAB75xn6fmj84ROUtG5eUB3GerHx83hrEr3w5vSADY_g=BRg5FA@mail.gmail.com> <1481689286.47880.1460111891664.JavaMail.yahoo@mail.yahoo.com> <alpine.OSX.2.01.1604080418530.36488@rabdullah.local> <594.1460126622@obiwan.sandelman.ca> <5707C458.7080107@dcrocker.net> <20160408150512.6283348.55871.10388@blackberry.com> <3746.1460144915@obiwan.sandelman.ca> <alpine.OSX.2.01.1604081315580.38286@rabdullah.local>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/D7jbTr8HL4DSbuKj-__XvhJScFE>
Cc: Michael Richardson <mcr+ietf@sandelman.ca>, Dave Crocker <dcrocker@bbiw.net>, "ietf@ietf.org 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: Sat, 09 Apr 2016 12:08:06 -0000

> I have only one real complaint: it's too hot and humid for my liking,
> but then again I could also describe Singapore as a very large
> air-conditioned shopping center disguised as a country :-)

bingo


From nobody Sat Apr  9 05:48:02 2016
Return-Path: <olejacobsen@me.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 E009F12D65F for <ietf@ietfa.amsl.com>; Sat,  9 Apr 2016 05:48:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.631
X-Spam-Level: 
X-Spam-Status: No, score=-2.631 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 qnDFabDpWqyk for <ietf@ietfa.amsl.com>; Sat,  9 Apr 2016 05:47:57 -0700 (PDT)
Received: from mr11p00im-asmtp003.me.com (mr11p00im-asmtp003.me.com [17.110.69.254]) (using TLSv1.2 with cipher DHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A283D12D666 for <ietf@ietf.org>; Sat,  9 Apr 2016 05:47:57 -0700 (PDT)
Received: from [10.1.10.8] (173-11-110-134-SFBA.hfc.comcastbusiness.net [173.11.110.134]) by mr11p00im-asmtp003.me.com (Oracle Communications Messaging Server 7.0.5.36.0 64bit (built Sep 8 2015)) with ESMTPSA id <0O5D00FOSA7SZB00@mr11p00im-asmtp003.me.com> for ietf@ietf.org; Sat, 09 Apr 2016 12:47:57 +0000 (GMT)
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, definitions=2016-04-09_10:,, signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 clxscore=1015 suspectscore=0 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1510270003 definitions=main-1604090192
Date: Sat, 09 Apr 2016 05:47:52 -0700 (PDT)
From: Ole Jacobsen <olejacobsen@me.com>
To: Randy Bush <randy@psg.com>
Subject: Re: Concerns about Singapore
In-reply-to: <m260vr7zqo.wl%randy@psg.com>
Message-id: <alpine.OSX.2.01.1604090545200.40954@rabdullah.local>
References: <CAB75xn6fmj84ROUtG5eUB3GerHx83hrEr3w5vSADY_g=BRg5FA@mail.gmail.com> <1481689286.47880.1460111891664.JavaMail.yahoo@mail.yahoo.com> <alpine.OSX.2.01.1604080418530.36488@rabdullah.local> <594.1460126622@obiwan.sandelman.ca> <5707C458.7080107@dcrocker.net> <20160408150512.6283348.55871.10388@blackberry.com> <A9E6E707-86DD-4E4A-BD5C-A7B0D6E40398@gmail.com> <m260vr7zqo.wl%randy@psg.com>
User-Agent: Alpine 2.01 (OSX 1266 2009-07-14)
MIME-version: 1.0
Content-type: MULTIPART/MIXED; BOUNDARY="0-1508982354-1460206077=:40954"
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/OL9XVtSPJcSYLQ7mzDOZvFrCmDs>
Cc: Dave Crocker <dcrocker@bbiw.net>, Michael Richardson <mcr@sandelman.ca>, "ietf@ietf.org Discussion" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: Ole Jacobsen <olejacobsen@me.com>
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, 09 Apr 2016 12:48:01 -0000

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.

--0-1508982354-1460206077=:40954
Content-Type: TEXT/PLAIN; charset=UTF-8
Content-Transfer-Encoding: 8BIT


Randy,

Sorry, no that is not what he means. Malaysia has no diplomatic 
relations with Israel and it is thus not possible for him to apply
for a visa through the normal process (embassy, consulate, fee,
sticker in passport, etc).

There *are* ways for a group to apply to for exceptions, but this
cannot in any way be compared to visas from or to China.

Ole


Ole J. Jacobsen
Editor and Publisher
The Internet Protocol Journal
Office:  +1 415-550-9433
Cell:    +1 415-370-4628
docomo: (090) 3337-9311
Web: protocoljournal.org
E-mail: olejacobsen@me.com




On Sat, 9 Apr 2016, Randy Bush wrote:

> > And I canâ€™t enter Malaysia at all.
> 
> what you mean is that the malaysians have you go through a visa process
> as the emericans do to the chinese, ...
> 
> randy
> 
> 
--0-1508982354-1460206077=:40954--


From nobody Sat Apr  9 06:50:14 2016
Return-Path: <john-ietf@jck.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 37C5912D63D for <ietf@ietfa.amsl.com>; Sat,  9 Apr 2016 06:50:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] 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 8I8uP10Kbjv3 for <ietf@ietfa.amsl.com>; Sat,  9 Apr 2016 06:50:12 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 784C012D160 for <ietf@ietf.org>; Sat,  9 Apr 2016 06:50:12 -0700 (PDT)
Received: from [198.252.137.10] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1aotGy-000CON-Il; Sat, 09 Apr 2016 09:50:00 -0400
Date: Sat, 09 Apr 2016 09:49:55 -0400
From: John C Klensin <john-ietf@jck.com>
To: Randy Bush <randy@psg.com>, Ole Jacobsen <olejacobsen@me.com>
Subject: Re: Concerns about Singapore
Message-ID: <7C061FD4097D0EEF5B3C92E6@JcK-HP8200.jck.com>
In-Reply-To: <m24mbb7zoe.wl%randy@psg.com>
References: <CAB75xn6fmj84ROUtG5eUB3GerHx83hrEr3w5vSADY_g=BRg5FA@mail.gmail.com> <1481689286.47880.1460111891664.JavaMail.yahoo@mail.yahoo.com> <alpine.OSX.2.01.1604080418530.36488@rabdullah.local> <594.1460126622@obiwan.sandelman.ca> <5707C458.7080107@dcrocker.net> <20160408150512.6283348.55871.10388@blackberry.com> <3746.1460144915@obiwan.sandelman.ca> <alpine.OSX.2.01.1604081315580.38286@rabdullah.local> <m24mbb7zoe.wl%randy@psg.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/yvy5ZzT6Hn4wQ5VKHJQfRKN4BO0>
Cc: Michael Richardson <mcr+ietf@sandelman.ca>, Dave Crocker <dcrocker@bbiw.net>, "ietf@ietf.org 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: Sat, 09 Apr 2016 13:50:14 -0000

--On Saturday, April 09, 2016 09:08 -0300 Randy Bush
<randy@psg.com> wrote:

>> I have only one real complaint: it's too hot and humid for my
>> liking, but then again I could also describe Singapore as a
>> very large air-conditioned shopping center disguised as a
>> country :-)
> 
> bingo

Is that very different from describing downtown Minneapolis (at
the wrong time of year) as a very large heated shopping mall and
hotel complex disguised as a city?

  john




From nobody Sat Apr  9 07:12:50 2016
Return-Path: <ynir.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 31BE212D6FA for <ietf@ietfa.amsl.com>; Sat,  9 Apr 2016 07:12:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 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, RCVD_IN_DNSWL_LOW=-0.7, 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 yz4jPHjd0xiy for <ietf@ietfa.amsl.com>; Sat,  9 Apr 2016 07:12:46 -0700 (PDT)
Received: from mail-wm0-x229.google.com (mail-wm0-x229.google.com [IPv6:2a00:1450:400c:c09::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 623EB12D6EA for <ietf@ietf.org>; Sat,  9 Apr 2016 07:12:46 -0700 (PDT)
Received: by mail-wm0-x229.google.com with SMTP id n3so53112575wmn.0 for <ietf@ietf.org>; Sat, 09 Apr 2016 07:12:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=Cdhf9SO+0zO8lDjML7cUv6ztRKj+F81C9El3RP3IsjM=; b=cpe9Y2p9QmJ2OArlsP+9dphuBsTg/PlgfJlHo71spYsHNmfFm+Aj1apQOOCN6GhebP 7JuidU/BsXffH9vR2MGu+Qd8cURAzb84udRc4W3JePr89v0O62eED7CnxJv7ZTRP2TuX yQtJQ8xU7KR7uXdpC/iBNXEzWShQ/bKSamyoP5oYRyxNsGoQ+2WLxTRKCQOPGEiRJ5qe RHTI6JdBaeEkE8Rp33Glle6jXnpJYueMAWdiRpk1OIoOxZ6Sy28xiU9BCeFTR2Hopya/ H+Yu9by1zWLg8UeRrcTtNtGnFkN+X6hNZZ0cD30AqvPhjqr3pUmc5UkpZlSFs8ZKRRwy bhGQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=Cdhf9SO+0zO8lDjML7cUv6ztRKj+F81C9El3RP3IsjM=; b=kJ+Clw/9D2W82qx91A3cDgR2t1I+f5+Z8HUadkTCn1eiQw9OSxLC6W6GtasphUukgj obKG8aDH+76PrZWZsauJbxf5k0DL+385khtH0cfuk5Rmx/L+vf1fBWC9B/SoqUwOMlw1 kIT5JzLxiQvKYLe7ROn4gZ5Rhuc90QE16Vg/J8Wwh6U5ijacKg0XvfOmbETwYYhYOzKm H0TPHIb7DI51L4yhUcS0PGMv0P2sFBEKWQx1QgoG2ixoybgFUvJ2w6jfgtqhSc2ysoR2 egIyhEbj83zfh/lVSOqX+TJqjefZf5ZTK1F+qjsgCszNaP9IlhGnInjHee001J/BznJf WpLw==
X-Gm-Message-State: AD7BkJKyEAa5+GEOBbeDWaXkahfeADTw8tSygHt3toD0SBCLm4F9ZVMDwf0sXKxte3Lyig==
X-Received: by 10.28.141.141 with SMTP id p135mr8947247wmd.8.1460211164870; Sat, 09 Apr 2016 07:12:44 -0700 (PDT)
Received: from [10.81.8.143] ([195.76.232.154]) by smtp.gmail.com with ESMTPSA id n3sm18335826wja.6.2016.04.09.07.12.43 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Sat, 09 Apr 2016 07:12:44 -0700 (PDT)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Subject: Re: Concerns about Singapore
From: Yoav Nir <ynir.ietf@gmail.com>
In-Reply-To: <m260vr7zqo.wl%randy@psg.com>
Date: Sat, 9 Apr 2016 11:12:42 -0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <D59E7B42-2FE7-438C-A865-7326B61EA4CC@gmail.com>
References: <CAB75xn6fmj84ROUtG5eUB3GerHx83hrEr3w5vSADY_g=BRg5FA@mail.gmail.com> <1481689286.47880.1460111891664.JavaMail.yahoo@mail.yahoo.com> <alpine.OSX.2.01.1604080418530.36488@rabdullah.local> <594.1460126622@obiwan.sandelman.ca> <5707C458.7080107@dcrocker.net> <20160408150512.6283348.55871.10388@blackberry.com> <A9E6E707-86DD-4E4A-BD5C-A7B0D6E40398@gmail.com> <m260vr7zqo.wl%randy@psg.com>
To: Randy Bush <randy@psg.com>
X-Mailer: Apple Mail (2.3124)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/E6XCd8nSVf72RXqY7wsfGj1tmcI>
Cc: "ietf@ietf.org 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: Sat, 09 Apr 2016 14:12:48 -0000

> On 9 Apr 2016, at 9:06 AM, Randy Bush <randy@psg.com> wrote:
>=20
>> And I can=E2=80=99t enter Malaysia at all.
>=20
> what you mean is that the malaysians have you go through a visa =
process
> as the emericans do to the chinese, =E2=80=A6

No. The Americans do that to me as well. But any Israeli and Chinese is =
eligible for a US visa unless the embassy official suspects that you are =
going to use this visa to enter the US and work there illegally. =
Israelis can get a Malaysia visit only on a special-case basis. Mostly =
when a sporting event of conference threatens to not meet there unless =
they allow everyone to visit.

Not even close to being the same thing.

Yoav




From nobody Sat Apr  9 07:45:45 2016
Return-Path: <ynir.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 B819E12B007 for <ietf@ietfa.amsl.com>; Sat,  9 Apr 2016 07:45:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.42
X-Spam-Level: 
X-Spam-Status: No, score=-0.42 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, NO_DNS_FOR_FROM=0.379, RCVD_IN_DNSWL_LOW=-0.7] 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 sOSbKmZ1uZeA for <ietf@ietfa.amsl.com>; Sat,  9 Apr 2016 07:45:36 -0700 (PDT)
Received: from mail-wm0-x231.google.com (mail-wm0-x231.google.com [IPv6:2a00:1450:400c:c09::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 D740B12B004 for <ietf@ietf.org>; Sat,  9 Apr 2016 07:45:35 -0700 (PDT)
Received: by mail-wm0-x231.google.com with SMTP id v188so43304571wme.1 for <ietf@ietf.org>; Sat, 09 Apr 2016 07:45:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=ipOWEW0KzRgsYgGttqiN/bANd6SuMyOFWrMwrREebQo=; b=bvkgAZl95fg644wYjjBxJMe1ADM9Qa+PaBLcLx+SUhPVmRaJTGPbNTxIPsZnCd1udF rbhUT2gR0hpUxpJxSPY/Lq4tePin/8+Q3OH2vJBsXJAFbiAUPmsK+EwDxqOpdOs3foIB cRq9nVbc9UFkLHmHT1WkIpO268exkl2NAslRWtipAOBghIzjcUpX2pc8ZdpUUhy8k6Vb XRkycnV+Der3G26LW4aYZNyM9IletquCypOuSI133qdMEvW4D1jNcP4A6aSHLoHr7Sdu T/3RfvKW5MlvuCYtFksWLM4zaBrqQjM8MTbfLJOTVAaLnj+qVNZnO6AUbGKqjPJJDVMD Iqeg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=ipOWEW0KzRgsYgGttqiN/bANd6SuMyOFWrMwrREebQo=; b=J8Wle0Ute5SmrRFm7UIyfa172URQOFFVibzrLcYThIGInR5KF9W6+DoaLMWQhljZOd d9LPf4+YV5MxnTIqu4IPHj1wNqOEMlbkCvUAKqcGca0NsDtykZKbmwHezHYKJbXhLjad fFCISrXKukiDEz/EuxLsf67yhpqAzwxOWaVGtVx06vNJbNBmARTsHBiQKUpR/VInSkhd sHmfGagm7X5GGH94CTQZwnwlc9lR3jrZaBSE6nLo0akIeYQC/J3OHHI5QSv4AEqincuR J/NByuFLEma26H+DjpYo6CTqkgx6BTmwsN59t+WTyZGm/yGGDmjYBNDikdsh/JZgH33M GevQ==
X-Gm-Message-State: AD7BkJKmH8QJ+TH2Cg4agVh+jjBGOgBuxTj9t0kEY1lgPj6azDUyMSCBf0N7eQZ7uT7OkA==
X-Received: by 10.28.183.213 with SMTP id h204mr9159639wmf.96.1460213134243; Sat, 09 Apr 2016 07:45:34 -0700 (PDT)
Received: from [10.81.8.143] ([195.76.232.154]) by smtp.gmail.com with ESMTPSA id lh1sm18508042wjb.20.2016.04.09.07.45.33 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Sat, 09 Apr 2016 07:45:33 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Subject: Re: I-D Action: draft-kucherawy-nomcom-procexp-00.txt
From: Yoav Nir <ynir.ietf@gmail.com>
In-Reply-To: <570882CE.9010501@gmail.com>
Date: Sat, 9 Apr 2016 16:45:32 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <092739B8-1D35-4539-961A-EDAC7033218A@gmail.com>
References: <20160408185636.23101.86017.idtracker@ietfa.amsl.com> <570882CE.9010501@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.3124)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/Do4MwbolKBkmA0kseAi72iQAXaA>
Cc: IETF discussion list <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: Sat, 09 Apr 2016 14:45:40 -0000

On 9 Apr 2016, at 6:19 AM, Brian E Carpenter =
<brian.e.carpenter@gmail.com> wrote:

> I do think one possible outcome needs to be added:
>=20
>   X.  That the results of the experiment suggest that the changes made
>       in Section 2 are damaging and should not be applied again;
>=20
> I regard this as unlikely, but I disagree with the comment that the
> experiment is bound to succeed. I can think of a number of failure
> scenarios, several of which would cause the NomCom chair to abort
> the process.

My comment was that anything short of a disaster is bound to be =
considered a success. IOW an outcome that is somewhat worse than the =
current situation will be indistinguishable from success.

Yoav


From nobody Sat Apr  9 08:53:17 2016
Return-Path: <aallen@blackberry.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 D553012B032 for <ietf@ietfa.amsl.com>; Sat,  9 Apr 2016 08:53:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.716
X-Spam-Level: 
X-Spam-Status: No, score=-1.716 tagged_above=-999 required=5 tests=[HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.996, SPF_PASS=-0.001] 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 uo_g4ybw-vAJ for <ietf@ietfa.amsl.com>; Sat,  9 Apr 2016 08:53:13 -0700 (PDT)
Received: from smtp-p01.blackberry.com (smtp-p01.blackberry.com [208.65.78.88]) by ietfa.amsl.com (Postfix) with ESMTP id 5B37C12B027 for <ietf@ietf.org>; Sat,  9 Apr 2016 08:53:12 -0700 (PDT)
Received: from xct104cnc.rim.net ([10.65.161.204]) by mhs210cnc.rim.net with ESMTP/TLS/AES256-SHA; 09 Apr 2016 12:20:19 -0400
Received: from XMB122CNC.rim.net ([fe80::28c6:fa1c:91c6:2e23]) by XCT104CNC.rim.net ([::1]) with mapi id 14.03.0210.002; Sat, 9 Apr 2016 11:53:04 -0400
From: Andrew Allen <aallen@blackberry.com>
To: David Conrad <drc@virtualized.org>, Dhruv Dhody <dhruv.ietf@gmail.com>
Subject: Re: Concerns about Singapore
Thread-Topic: Concerns about Singapore
Thread-Index: AQHRkOMNjufwcA4TvkK+5mik25hZRp9/GCcAgAAATwCAAAuKAIAACE6AgAAKzACAAtn2AA==
Date: Sat, 9 Apr 2016 15:53:03 +0000
Message-ID: <20160409155300.6283348.41255.10529@blackberry.com>
References: <0D914666-C3D4-4CCE-AD5E-4E5B34EA1A73@piuha.net> <20160407182936.GA21340@pfrc.org> <CAB75xn780nNDjGa_Cc222J20-+1CCHt09Xp8KHzaK=n0xx51pg@mail.gmail.com> <5706B100.9040509@mnt.se> <CAB75xn6fmj84ROUtG5eUB3GerHx83hrEr3w5vSADY_g=BRg5FA@mail.gmail.com> <9B723FB0-6B93-4C85-ADD9-D423F873CF08@virtualized.org>
In-Reply-To: <9B723FB0-6B93-4C85-ADD9-D423F873CF08@virtualized.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: multipart/alternative; boundary="_000_2016040915530062833484125510529blackberrycom_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/E0to5GehTI-AFMjsfd4Di7gr4Ck>
Cc: "ietf@ietf.org 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: Sat, 09 Apr 2016 15:53:16 -0000

--_000_2016040915530062833484125510529blackberrycom_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

TXkgZmV3IHBlc29zIHdvcnRoIG9uIHRoaXMgdG9waWMuDQoNClRoZSB3ZWJzaXRlIGxpbmsgcHJv
dmlkZWQgYWxzbyBpZGVudGlmaWVzIDEzIFVTIHN0YXRlcyDigI53aGVyZSBzdWNoIGxhd3Mgc3Rp
bGwgZXhpc3RzIG9uIHRoZSBib29rcyBhbmQgYWx0aG91Z2ggZHVlIHRvIGEgMjAwMyBTdXByZW1l
IENvdXJ0IGRlY2lzaW9uIHBlb3BsZSBhcmUgbm8gbG9uZ2VyIHByb3NlY3V0ZWQgZm9yIHZpb2xh
dGlvbnMgdGhlcmUgaGF2ZSBhY2NvcmRpbmcgdG8gdGhlIHNpdGUgc3RpbGwgYmVlbiBhcnJlc3Rz
IHVuZGVyIHRoZXNlIGxhd3MuDQoNClR3byBvZiB0aGUgc3RhdGUncyBsaXN0ZWQgKEZsb3JpZGEg
YW5kIFRleGFzKSB3ZXJlIGxvY2F0aW9ucyBmb3IgMiBvZiB0aGUgbGFzdCAzIElFVEYgbWVldGlu
Z3MgaG9zdGVkIGluIHRoZSBVU0EuDQoNCuKAjkFyZSB3ZSBub3cgc2F5aW5nIHRoYXQgdGhlc2Ux
MyBVUyBTdGF0ZXMgYXJlIGFsc28gbm93IG9mZiB0aGUgbGlzdCBvZiBwb3NzaWJsZSBsb2NhdGlv
bnMgZXZlbiB0aG91Z2ggd2UgaGF2ZSBoYWQgc2V2ZXJhbCBtZWV0aW5ncyBpbiBzb21lIG9mIHRo
ZXNlIHN0YXRlcyB3aXRob3V0IGFueSBpc3N1ZXM/DQoNCuKAjkkgdGhpbmsgYXMgYSBiYXNpYyAg
cHJpbmNpcGxlIHdlIHNob3VsZCBlbnN1cmUgdGhhdCBtZWV0aW5nIGxvY2F0aW9ucyBhcmUgYWNj
ZXNzaWJsZSB0byBhbGwgdGhlIGNvbW11bml0eSBhbmQgbm8gb25lIHNob3VsZCBiZSBkZW5pZWQg
YXR0ZW5kYW5jZSBiZWNhdXNlIG9mIHdobyB0aGV5IGFyZSwgdGhlaXIgcmFjZSwgIG9yaWVudGF0
aW9uLCByZWxpZ2lvbiwgcG9saXRpY3MgIG9yIHdoZXJlIHRoZXkgYXJlIGZyb20gZXRjLg0KDQpJ
dCBpcyBob3dldmVyIGEgbGl0dGxlIGRpZmZlcmVudCBpZiB0aGUgbG9jYXRpb24ncyAgbGF3cyBi
YXIgY2VydGFpbiBwZXJzb25hbCBhY3Rpdml0aWVzIGluY2x1ZGluZyBmb3IgZXhhbXBsZSB3aGF0
IHN1YnN0YW5jZXMgeW91IGluZ2VzdCB0aGF0IG1heSBiZSBsZWdhbCBpbiBzb21lIHBsYWNlcyBh
bmQgbm90IG90aGVycyBvciBkaWZmZXJlbnQgbGF3cyByZWdhcmRpbmcgdGhlIHB1YmxpYyB1c2Ug
b2YgdG9iYWNjbyBhcyB3ZWxsIGFzIG90aGVyIG1vcmUgIHBlcnNvbmFsIGFjdGl2aXRpZXMsIGlu
Y2x1ZGluZyB3aGF0IGFnZSB5b3UgbmVlZCB0byBiZSB0byBkbyBzbyBsZWdhbGx5LiDigI5JIGRv
bid0IHRoaW5rIGl0IGlzIGVudGlyZWx5IHVucmVhc29uYWJsZSBmb3IgcGVvcGxlIHRvIGFic3Rh
aW4gZm9yIDYgZGF5cyBmcm9tIHBlcnNvbmFsIGFjdGl2aXRpZXMgbGVnYWwgaW4gdGhlaXIgb3du
IGNvdW50cnkgdGhhdCBtYXkgYmUgYWdhaW5zdCBsb2NhbCBsYXdzIGluIG9yZGVyIHRvIGF0dGVu
ZCBhbiBJRVRGIG1lZXRpbmcgcmVnYXJkbGVzcyBvZiBob3cgdW5yZWFzb25hYmxlIG9yIG9ibm94
aW91cyAgdGhvc2UgbGF3cyBtYXkgYmUgdG8gdXMuDQoNCkkgdGhpbmsgd2UgbmVlZCB0byBhY2Nl
cHQgdGhhdCBkaWZmZXJlbnQgcGxhY2VzIGluIHRoZSB3b3JsZCBoYXZlIGRpZmZlcmVudCBjdWx0
dXJlcyBhbmQgZGlmZmVyZW50IGxhd3MgYW5kIHNvIGxvbmcgYXMgdGhvc2UgbGF3cyBkb24ndCBh
Y3R1YWxseSBwcmV2ZW50IHlvdSBlbnRlcmluZyB0aGUgY291bnRyeSBvciBvYnRhaW5pbmcgc3Vp
dGFibGUgYWNjb21tb2RhdGlvbiBvciBjYXVzZSB5b3UgdG8gaGF2ZSAgdG8gbGllIGluIG9yZGVy
IHRvIGRvIHNvIG9yIHNpZ25pZmljYW50bHkgYWZmZWN0IHlvdXIgcGVyc29uYWwgc2FmZXR5IHRo
ZXNlIHNob3VsZG4ndCBjb21wbGV0ZWx5IHJ1bGUgb3V0IGEgbG9jYXRpb24gYWx0aG91Z2ggdGhl
eSBtYXkgYmUgYSBjb25zaWRlcmF0aW9uIHdoZW4gZXZhbHVhdGluZyBiZXR3ZWVuIGxvY2F0aW9u
cyAuDQoNCkhhdmluZyBiZWVuIHRvIFNpbmdhcG9yZSBvbmNlIGJlZm9yZSBJIGFtIGNlcnRhaW4g
dGhlcmUgYXJlIG5vIHJvb20gcG9saWNlIHBhdHJvbGxpbmcgdGhlIGhvdGVsIGNvcnJpZG9ycyB0
cnlpbmcgdG8gYXNjZXJ0YWluIHdoYXQgYWN0aXZpdGllcyB0aGUgZ3Vlc3RzIGFyZSB1cCB0byBp
biB0aGVpciBvd24gcm9vbXMuIFRoZXJlIHdlcmUgYWxzbyBubyBwZXJzb25hbCBxdWVzdGlvbnMg
YXNrZWQgYXQgaG90ZWwgcmVnaXN0cmF0aW9uIGFzIGZhciBhcyBJIHJlY2FsbCAoIEkgYW0gc3Vy
ZSBJIHdvdWxkIGhhdmUgcmVtZW1iZXJlZCB0aGF0KSBzbyBJIGRvbid0IHNlZSBpdCBhcyBhbiBl
c3BlY2lhbGx5IGhvc3RpbGUgZW52aXJvbm1lbnQu4oCOIEkgdGhpbmsgdGhlIElFVEYgc2hvdWxk
IGNvbmZpcm0gd2l0aCB0aGUgbWVldGluZyBob3RlbHMgdGhhdCB0aGVyZSB3aWxsIGJlIG5vIGlz
c3VlcyBpbiB0aGF0IHJlZ2FyZCBhbmQgYWxzbyBhIGNoZWNrIHdpdGggdGhlIFNpbmdhcG9yZSBh
dXRob3JpdGllcyB0aGF0IHRoZXJlIHdpbGwgYmUgbm8gdGhyZWF0IHRvIElFVEYgcGFydGljaXBh
bnRzIGJlY2F1c2Ugb2YgdGhlaXIgb3JpZW50YXRpb24gb3IgbWFyaXRhbCBzdGF0dXMgd291bGQg
YmUgYSBzZW5zaWJsZSBtZWFzdXJlLg0KDQpJIHVuZGVyc3RhbmQgdGhhdCBjZXJ0YWluIGxhd3Mg
YW5kIGN1bHR1cmFsIOKAjmF0dGl0dWRlcyBpbiBzb21lIHBsYWNlcyBtYXkgbWFrZSBzb21lIGZl
ZWwgdW5jb21mb3J0YWJsZS4gQXMgYSBCcml0aXNoIGNpdGl6ZW4gc2VlaW5nIE1hbHZpbmFzIFNv
biBBcmVudGluYXMgcG9zdGVycyBhbGwgb3ZlciBCdWVub3MgQWlyZXMgd2FzIG5vdCB0aGUgbW9z
dCB3ZWxjb21lIHNpZ2h0IHRvIG1lIGFuZCB0byBhIGRlZ3JlZSBvZmZlbmRzIHNvbWUgb2YgbXkg
cGFydGljdWxhciBzZW5zaWJpbGl0aWVzIGFuZCBpZiBJIHdhbGtlZCBhcm91bmQgUGxhemEgZGUg
TWF5byB3ZWFyaW5nIGEgdW5pb24gamFjayB0LSBzaGlydCBJIHRoaW5rIEkgbWlnaHQgZ2V0IGEg
aG9zdGlsZSByZWFjdGlvbiBidXQgdGhhdCBkb2Vzbid0IG1lYW4gQXJnZW50aW5hIHNob3VsZCBi
ZSBvZmYgbGltaXRzIHRvIElFVEYuIFdoZW4gdmlzaXRpbmcgYW5vdGhlciBjb3VudHJ5IHlvdSBh
cmUgYSBndWVzdCB0aGVyZSBhbmQgeW91IG5lZWQgdG8gYmUgd2lsbGluZyB0byBjb25mb3JtIHlv
dXIgcHVibGljIGJlaGF2aW9yIGluIG9yZGVyIHRvIG5vdCBvZmZlbmQgdGhlIGhvc3RzIGFuZCBu
b3QgdmlvbGF0ZSBsb2NhbCBsYXdzIGFuZCB0aGF0IHlvdSBtYXkgaGF2ZSB0byBhY2NlcHQgdGhh
dCB5b3UgbWF5IG5vdCBhbHdheXMgaGF2ZSB0aGUgc2FtZSBmcmVlZG9tcyB5b3UgZW5qb3kgYXQg
aG9tZS4gV2hlbiBpbiBSb21lLi4uLi4NCg0KSSBkb24ndCB0aGluayB0aGUgSUVURiBzaG91bGQg
Ym95Y290dCBsb2NhdGlvbnMganVzdCBiZWNhdXNlIHRoZSBjb21tdW5pdHkgZG9lc24ndCBsaWtl
IHNvbWUgb2YgdGhlIGxhd3Mgb2YgdGhhdCBjb3VudHJ5IG9yIGFzcGVjdHMgb2YgdGhhdCBjb3Vu
dHJpZXMgZ292ZXJubWVudHMgcG9saWNpZXPigI4uICBUaGF0IGlzIGEgdmVyeSBzbGlwcGVyeSBz
bG9wZSB0aGF0IGNvdWxkIHNpZ25pZmljYW50bHkgcmVkdWNlIHRoZSBudW1iZXIgb2YgcG9zc2li
bGUgbWVldGluZyBsb2NhdGlvbnMgYW5kIGFsc28gZGlzdHJhY3QgZnJvbSB0aGUgSUVURiBtaXNz
aW9uLg0KDQpJIHRoaW5rIHRoZSBoYXJkIGFuZCBmYXN0IGNyaXRlcmlhIHNob3VsZCBiZSBpcyB0
aGUgbG9jYXRpb24gIGluIHByYWN0aWNlIG9wZW4gZm9yIGV2ZXJ54oCOYm9keSB0byBhdHRlbmQg
YW5kIHdpbGwgdGhlIGF0dGVuZGVlcyBiZSByZWFzb25hYmx5IHNhZmUgdGhlcmUuDQoNCkFuZHJl
dw0KDQpTZW50IGZyb20gbXkgQmxhY2tCZXJyeSAxMCBzbWFydHBob25lLg0KRnJvbTogRGF2aWQg
Q29ucmFkDQpTZW50OiBUaHVyc2RheSwgQXByaWwgNywgMjAxNiAxNzoyMA0KVG86IERocnV2IERo
b2R5DQpDYzogaWV0ZkBpZXRmLm9yZyBEaXNjdXNzaW9uDQpTdWJqZWN0OiBSZTogQ29uY2VybnMg
YWJvdXQgU2luZ2Fwb3JlDQoNCg0K4oCLTm8sIEkgbWVhbnQgdGhhdCBJRVRGIHdvdWxkIGJlIGRv
aW5nIGEgZGlzc2VydmljZSB0byBhIGxhcmdlIHBhcnQgb2YgdGhlIHdvcmxkICh0aGF0IGhhcyBv
biBpdHMgYm9va3MgdGhlc2UgbGF3cykuDQoNCkZvciByZWZlcmVuY2U6DQoNCmh0dHA6Ly83NmNy
aW1lcy5jb20vNzYtY291bnRyaWVzLXdoZXJlLWhvbW9zZXh1YWxpdHktaXMtaWxsZWdhbC8NCg0K
KGhhdmVuJ3QgdmVyaWZpZWQsIGJ1dCBJIHJlYWQgaXQgb24gdGhlIEludGVybmV0IHNvIGl0IG11
c3QgYmUgdHJ1ZSkNCg0KUmVnYXJkcywNCi1kcmMNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0K
DQoNCg==

--_000_2016040915530062833484125510529blackberrycom_
Content-Type: text/html; charset="utf-8"
Content-ID: <57DC63123283C845A0D5359EFCED7DA8@rim.com>
Content-Transfer-Encoding: base64

PGh0bWw+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIgY29udGVudD0i
dGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjwvaGVhZD4NCjxib2R5IGNsYXNzPSIiIGxhbmc9
ImVuLVVTIiBzdHlsZT0iYmFja2dyb3VuZC1jb2xvcjogcmdiKDI1NSwgMjU1LCAyNTUpOyBsaW5l
LWhlaWdodDogaW5pdGlhbDsiPg0KPGRpdiBzdHlsZT0id2lkdGg6IDEwMCU7IGZvbnQtc2l6ZTog
aW5pdGlhbDsgZm9udC1mYW1pbHk6IENhbGlicmksICdTbGF0ZSBQcm8nLCBzYW5zLXNlcmlmLCBz
YW5zLXNlcmlmOyBjb2xvcjogcmdiKDMxLCA3MywgMTI1KTsgdGV4dC1hbGlnbjogaW5pdGlhbDsg
YmFja2dyb3VuZC1jb2xvcjogcmdiKDI1NSwgMjU1LCAyNTUpOyI+DQo8c3BhbiBzdHlsZT0iZm9u
dC1zaXplOiBpbml0aWFsOyB0ZXh0LWFsaWduOiBpbml0aWFsOyBsaW5lLWhlaWdodDogaW5pdGlh
bDsiPk15IGZldyBwZXNvcyB3b3J0aCBvbiB0aGlzIHRvcGljLiZuYnNwOzwvc3Bhbj48L2Rpdj4N
CjxkaXYgc3R5bGU9IndpZHRoOiAxMDAlOyBmb250LXNpemU6IGluaXRpYWw7IGZvbnQtZmFtaWx5
OiBDYWxpYnJpLCAnU2xhdGUgUHJvJywgc2Fucy1zZXJpZiwgc2Fucy1zZXJpZjsgY29sb3I6IHJn
YigzMSwgNzMsIDEyNSk7IHRleHQtYWxpZ246IGluaXRpYWw7IGJhY2tncm91bmQtY29sb3I6IHJn
YigyNTUsIDI1NSwgMjU1KTsiPg0KPHNwYW4gc3R5bGU9ImZvbnQtc2l6ZTogaW5pdGlhbDsgdGV4
dC1hbGlnbjogaW5pdGlhbDsgbGluZS1oZWlnaHQ6IGluaXRpYWw7Ij48YnI+DQo8L3NwYW4+PC9k
aXY+DQo8ZGl2IHN0eWxlPSJ3aWR0aDogMTAwJTsgZm9udC1zaXplOiBpbml0aWFsOyBmb250LWZh
bWlseTogQ2FsaWJyaSwgJ1NsYXRlIFBybycsIHNhbnMtc2VyaWYsIHNhbnMtc2VyaWY7IGNvbG9y
OiByZ2IoMzEsIDczLCAxMjUpOyB0ZXh0LWFsaWduOiBpbml0aWFsOyBiYWNrZ3JvdW5kLWNvbG9y
OiByZ2IoMjU1LCAyNTUsIDI1NSk7Ij4NCjxzcGFuIHN0eWxlPSJmb250LXNpemU6IGluaXRpYWw7
IHRleHQtYWxpZ246IGluaXRpYWw7IGxpbmUtaGVpZ2h0OiBpbml0aWFsOyI+VGhlIHdlYnNpdGUg
bGluayBwcm92aWRlZCBhbHNvIGlkZW50aWZpZXMgMTMgVVMgc3RhdGVzIOKAjndoZXJlIHN1Y2gg
bGF3cyBzdGlsbCBleGlzdHMgb24gdGhlIGJvb2tzIGFuZCBhbHRob3VnaCBkdWUgdG8gYSAyMDAz
IFN1cHJlbWUgQ291cnQgZGVjaXNpb24gcGVvcGxlIGFyZSBubyBsb25nZXIgcHJvc2VjdXRlZA0K
IGZvciB2aW9sYXRpb25zIHRoZXJlIGhhdmUgYWNjb3JkaW5nIHRvIHRoZSBzaXRlIHN0aWxsIGJl
ZW4gYXJyZXN0cyB1bmRlciB0aGVzZSBsYXdzLiZuYnNwOzwvc3Bhbj48L2Rpdj4NCjxkaXYgc3R5
bGU9IndpZHRoOiAxMDAlOyBmb250LXNpemU6IGluaXRpYWw7IGZvbnQtZmFtaWx5OiBDYWxpYnJp
LCAnU2xhdGUgUHJvJywgc2Fucy1zZXJpZiwgc2Fucy1zZXJpZjsgY29sb3I6IHJnYigzMSwgNzMs
IDEyNSk7IHRleHQtYWxpZ246IGluaXRpYWw7IGJhY2tncm91bmQtY29sb3I6IHJnYigyNTUsIDI1
NSwgMjU1KTsiPg0KPGJyPg0KPC9kaXY+DQo8ZGl2IHN0eWxlPSJ3aWR0aDogMTAwJTsgZm9udC1z
aXplOiBpbml0aWFsOyBmb250LWZhbWlseTogQ2FsaWJyaSwgJ1NsYXRlIFBybycsIHNhbnMtc2Vy
aWYsIHNhbnMtc2VyaWY7IGNvbG9yOiByZ2IoMzEsIDczLCAxMjUpOyB0ZXh0LWFsaWduOiBpbml0
aWFsOyBiYWNrZ3JvdW5kLWNvbG9yOiByZ2IoMjU1LCAyNTUsIDI1NSk7Ij4NClR3byBvZiB0aGUg
c3RhdGUncyBsaXN0ZWQgKEZsb3JpZGEgYW5kIFRleGFzKSB3ZXJlIGxvY2F0aW9ucyBmb3IgMiBv
ZiB0aGUgbGFzdCAzIElFVEYgbWVldGluZ3MgaG9zdGVkIGluIHRoZSBVU0EuPC9kaXY+DQo8ZGl2
IHN0eWxlPSJ3aWR0aDogMTAwJTsgZm9udC1zaXplOiBpbml0aWFsOyBmb250LWZhbWlseTogQ2Fs
aWJyaSwgJ1NsYXRlIFBybycsIHNhbnMtc2VyaWYsIHNhbnMtc2VyaWY7IGNvbG9yOiByZ2IoMzEs
IDczLCAxMjUpOyB0ZXh0LWFsaWduOiBpbml0aWFsOyBiYWNrZ3JvdW5kLWNvbG9yOiByZ2IoMjU1
LCAyNTUsIDI1NSk7Ij4NCjxicj4NCjwvZGl2Pg0KPGRpdiBzdHlsZT0id2lkdGg6IDEwMCU7IGZv
bnQtc2l6ZTogaW5pdGlhbDsgZm9udC1mYW1pbHk6IENhbGlicmksICdTbGF0ZSBQcm8nLCBzYW5z
LXNlcmlmLCBzYW5zLXNlcmlmOyBjb2xvcjogcmdiKDMxLCA3MywgMTI1KTsgdGV4dC1hbGlnbjog
aW5pdGlhbDsgYmFja2dyb3VuZC1jb2xvcjogcmdiKDI1NSwgMjU1LCAyNTUpOyI+DQrigI5BcmUg
d2Ugbm93IHNheWluZyB0aGF0IHRoZXNlMTMgVVMgU3RhdGVzIGFyZSBhbHNvIG5vdyBvZmYgdGhl
IGxpc3Qgb2YgcG9zc2libGUgbG9jYXRpb25zIGV2ZW4gdGhvdWdoIHdlIGhhdmUgaGFkIHNldmVy
YWwgbWVldGluZ3MgaW4gc29tZSBvZiB0aGVzZSBzdGF0ZXMgd2l0aG91dCBhbnkgaXNzdWVzPzwv
ZGl2Pg0KPGRpdiBzdHlsZT0id2lkdGg6IDEwMCU7IGZvbnQtc2l6ZTogaW5pdGlhbDsgZm9udC1m
YW1pbHk6IENhbGlicmksICdTbGF0ZSBQcm8nLCBzYW5zLXNlcmlmLCBzYW5zLXNlcmlmOyBjb2xv
cjogcmdiKDMxLCA3MywgMTI1KTsgdGV4dC1hbGlnbjogaW5pdGlhbDsgYmFja2dyb3VuZC1jb2xv
cjogcmdiKDI1NSwgMjU1LCAyNTUpOyI+DQo8YnI+DQo8L2Rpdj4NCjxkaXYgc3R5bGU9IndpZHRo
OiAxMDAlOyBmb250LXNpemU6IGluaXRpYWw7IGZvbnQtZmFtaWx5OiBDYWxpYnJpLCAnU2xhdGUg
UHJvJywgc2Fucy1zZXJpZiwgc2Fucy1zZXJpZjsgY29sb3I6IHJnYigzMSwgNzMsIDEyNSk7IHRl
eHQtYWxpZ246IGluaXRpYWw7IGJhY2tncm91bmQtY29sb3I6IHJnYigyNTUsIDI1NSwgMjU1KTsi
Pg0K4oCOSSB0aGluayBhcyBhIGJhc2ljICZuYnNwO3ByaW5jaXBsZSB3ZSBzaG91bGQgZW5zdXJl
IHRoYXQgbWVldGluZyBsb2NhdGlvbnMgYXJlIGFjY2Vzc2libGUgdG8gYWxsIHRoZSBjb21tdW5p
dHkgYW5kIG5vIG9uZSBzaG91bGQgYmUgZGVuaWVkIGF0dGVuZGFuY2UgYmVjYXVzZSBvZiB3aG8g
dGhleSBhcmUsIHRoZWlyIHJhY2UsICZuYnNwO29yaWVudGF0aW9uLCByZWxpZ2lvbiwgcG9saXRp
Y3MgJm5ic3A7b3Igd2hlcmUgdGhleSBhcmUgZnJvbSBldGMuJm5ic3A7PC9kaXY+DQo8ZGl2IHN0
eWxlPSJ3aWR0aDogMTAwJTsgZm9udC1zaXplOiBpbml0aWFsOyBmb250LWZhbWlseTogQ2FsaWJy
aSwgJ1NsYXRlIFBybycsIHNhbnMtc2VyaWYsIHNhbnMtc2VyaWY7IGNvbG9yOiByZ2IoMzEsIDcz
LCAxMjUpOyB0ZXh0LWFsaWduOiBpbml0aWFsOyBiYWNrZ3JvdW5kLWNvbG9yOiByZ2IoMjU1LCAy
NTUsIDI1NSk7Ij4NCjxicj4NCjwvZGl2Pg0KPGRpdiBzdHlsZT0id2lkdGg6IDEwMCU7IGZvbnQt
c2l6ZTogaW5pdGlhbDsgZm9udC1mYW1pbHk6IENhbGlicmksICdTbGF0ZSBQcm8nLCBzYW5zLXNl
cmlmLCBzYW5zLXNlcmlmOyBjb2xvcjogcmdiKDMxLCA3MywgMTI1KTsgdGV4dC1hbGlnbjogaW5p
dGlhbDsgYmFja2dyb3VuZC1jb2xvcjogcmdiKDI1NSwgMjU1LCAyNTUpOyI+DQpJdCBpcyBob3dl
dmVyIGEgbGl0dGxlIGRpZmZlcmVudCBpZiB0aGUgbG9jYXRpb24ncyAmbmJzcDtsYXdzIGJhciBj
ZXJ0YWluIHBlcnNvbmFsIGFjdGl2aXRpZXMgaW5jbHVkaW5nIGZvciBleGFtcGxlIHdoYXQgc3Vi
c3RhbmNlcyB5b3UgaW5nZXN0IHRoYXQgbWF5IGJlIGxlZ2FsIGluIHNvbWUgcGxhY2VzIGFuZCBu
b3Qgb3RoZXJzIG9yIGRpZmZlcmVudCBsYXdzIHJlZ2FyZGluZyB0aGUgcHVibGljIHVzZSBvZiB0
b2JhY2NvIGFzIHdlbGwgYXMgb3RoZXINCiBtb3JlICZuYnNwO3BlcnNvbmFsIGFjdGl2aXRpZXMs
IGluY2x1ZGluZyB3aGF0IGFnZSB5b3UgbmVlZCB0byBiZSB0byBkbyBzbyBsZWdhbGx5LiDigI5J
IGRvbid0IHRoaW5rIGl0IGlzIGVudGlyZWx5IHVucmVhc29uYWJsZSBmb3IgcGVvcGxlIHRvIGFi
c3RhaW4gZm9yIDYgZGF5cyBmcm9tIHBlcnNvbmFsIGFjdGl2aXRpZXMgbGVnYWwgaW4gdGhlaXIg
b3duIGNvdW50cnkgdGhhdCBtYXkgYmUgYWdhaW5zdCBsb2NhbCBsYXdzIGluIG9yZGVyIHRvIGF0
dGVuZA0KIGFuIElFVEYgbWVldGluZyByZWdhcmRsZXNzIG9mIGhvdyB1bnJlYXNvbmFibGUgb3Ig
b2Jub3hpb3VzICZuYnNwO3Rob3NlIGxhd3MgbWF5IGJlIHRvIHVzLjwvZGl2Pg0KPGRpdiBzdHls
ZT0id2lkdGg6IDEwMCU7IGZvbnQtc2l6ZTogaW5pdGlhbDsgZm9udC1mYW1pbHk6IENhbGlicmks
ICdTbGF0ZSBQcm8nLCBzYW5zLXNlcmlmLCBzYW5zLXNlcmlmOyBjb2xvcjogcmdiKDMxLCA3Mywg
MTI1KTsgdGV4dC1hbGlnbjogaW5pdGlhbDsgYmFja2dyb3VuZC1jb2xvcjogcmdiKDI1NSwgMjU1
LCAyNTUpOyI+DQo8YnI+DQo8L2Rpdj4NCjxkaXYgc3R5bGU9IndpZHRoOiAxMDAlOyBmb250LXNp
emU6IGluaXRpYWw7IGZvbnQtZmFtaWx5OiBDYWxpYnJpLCAnU2xhdGUgUHJvJywgc2Fucy1zZXJp
Ziwgc2Fucy1zZXJpZjsgY29sb3I6IHJnYigzMSwgNzMsIDEyNSk7IHRleHQtYWxpZ246IGluaXRp
YWw7IGJhY2tncm91bmQtY29sb3I6IHJnYigyNTUsIDI1NSwgMjU1KTsiPg0KSSB0aGluayB3ZSBu
ZWVkIHRvIGFjY2VwdCB0aGF0IGRpZmZlcmVudCBwbGFjZXMgaW4gdGhlIHdvcmxkIGhhdmUgZGlm
ZmVyZW50IGN1bHR1cmVzIGFuZCBkaWZmZXJlbnQgbGF3cyBhbmQgc28gbG9uZyBhcyB0aG9zZSBs
YXdzIGRvbid0IGFjdHVhbGx5IHByZXZlbnQgeW91IGVudGVyaW5nIHRoZSBjb3VudHJ5IG9yIG9i
dGFpbmluZyBzdWl0YWJsZSBhY2NvbW1vZGF0aW9uIG9yIGNhdXNlIHlvdSB0byBoYXZlICZuYnNw
O3RvIGxpZSBpbiBvcmRlciB0byBkbw0KIHNvIG9yIHNpZ25pZmljYW50bHkgYWZmZWN0IHlvdXIg
cGVyc29uYWwgc2FmZXR5IHRoZXNlIHNob3VsZG4ndCBjb21wbGV0ZWx5IHJ1bGUgb3V0IGEgbG9j
YXRpb24gYWx0aG91Z2ggdGhleSBtYXkgYmUgYSBjb25zaWRlcmF0aW9uIHdoZW4gZXZhbHVhdGlu
ZyBiZXR3ZWVuIGxvY2F0aW9ucyAuJm5ic3A7PC9kaXY+DQo8ZGl2IHN0eWxlPSJ3aWR0aDogMTAw
JTsgZm9udC1zaXplOiBpbml0aWFsOyBmb250LWZhbWlseTogQ2FsaWJyaSwgJ1NsYXRlIFBybycs
IHNhbnMtc2VyaWYsIHNhbnMtc2VyaWY7IGNvbG9yOiByZ2IoMzEsIDczLCAxMjUpOyB0ZXh0LWFs
aWduOiBpbml0aWFsOyBiYWNrZ3JvdW5kLWNvbG9yOiByZ2IoMjU1LCAyNTUsIDI1NSk7Ij4NCjxi
cj4NCjwvZGl2Pg0KPGRpdiBzdHlsZT0id2lkdGg6IDEwMCU7IGZvbnQtc2l6ZTogaW5pdGlhbDsg
Zm9udC1mYW1pbHk6IENhbGlicmksICdTbGF0ZSBQcm8nLCBzYW5zLXNlcmlmLCBzYW5zLXNlcmlm
OyBjb2xvcjogcmdiKDMxLCA3MywgMTI1KTsgdGV4dC1hbGlnbjogaW5pdGlhbDsgYmFja2dyb3Vu
ZC1jb2xvcjogcmdiKDI1NSwgMjU1LCAyNTUpOyI+DQpIYXZpbmcgYmVlbiB0byBTaW5nYXBvcmUg
b25jZSBiZWZvcmUgSSBhbSBjZXJ0YWluIHRoZXJlIGFyZSBubyByb29tIHBvbGljZSBwYXRyb2xs
aW5nIHRoZSBob3RlbCBjb3JyaWRvcnMgdHJ5aW5nIHRvIGFzY2VydGFpbiB3aGF0IGFjdGl2aXRp
ZXMgdGhlIGd1ZXN0cyBhcmUgdXAgdG8gaW4gdGhlaXIgb3duIHJvb21zLiBUaGVyZSB3ZXJlIGFs
c28gbm8gcGVyc29uYWwgcXVlc3Rpb25zIGFza2VkIGF0IGhvdGVsIHJlZ2lzdHJhdGlvbiBhcyBm
YXIgYXMNCiBJIHJlY2FsbCAoIEkgYW0gc3VyZSBJIHdvdWxkIGhhdmUgcmVtZW1iZXJlZCB0aGF0
KSBzbyBJIGRvbid0IHNlZSBpdCBhcyBhbiBlc3BlY2lhbGx5IGhvc3RpbGUgZW52aXJvbm1lbnQu
4oCOIEkgdGhpbmsgdGhlIElFVEYgc2hvdWxkIGNvbmZpcm0gd2l0aCB0aGUgbWVldGluZyBob3Rl
bHMgdGhhdCB0aGVyZSB3aWxsIGJlIG5vIGlzc3VlcyBpbiB0aGF0IHJlZ2FyZCBhbmQgYWxzbyBh
IGNoZWNrIHdpdGggdGhlIFNpbmdhcG9yZSBhdXRob3JpdGllcw0KIHRoYXQgdGhlcmUgd2lsbCBi
ZSBubyB0aHJlYXQgdG8gSUVURiBwYXJ0aWNpcGFudHMgYmVjYXVzZSBvZiB0aGVpciBvcmllbnRh
dGlvbiBvciBtYXJpdGFsIHN0YXR1cyB3b3VsZCBiZSBhIHNlbnNpYmxlIG1lYXN1cmUuPC9kaXY+
DQo8ZGl2IHN0eWxlPSJ3aWR0aDogMTAwJTsgZm9udC1zaXplOiBpbml0aWFsOyBmb250LWZhbWls
eTogQ2FsaWJyaSwgJ1NsYXRlIFBybycsIHNhbnMtc2VyaWYsIHNhbnMtc2VyaWY7IGNvbG9yOiBy
Z2IoMzEsIDczLCAxMjUpOyB0ZXh0LWFsaWduOiBpbml0aWFsOyBiYWNrZ3JvdW5kLWNvbG9yOiBy
Z2IoMjU1LCAyNTUsIDI1NSk7Ij4NCjxicj4NCjwvZGl2Pg0KPGRpdiBzdHlsZT0id2lkdGg6IDEw
MCU7IGZvbnQtc2l6ZTogaW5pdGlhbDsgZm9udC1mYW1pbHk6IENhbGlicmksICdTbGF0ZSBQcm8n
LCBzYW5zLXNlcmlmLCBzYW5zLXNlcmlmOyBjb2xvcjogcmdiKDMxLCA3MywgMTI1KTsgdGV4dC1h
bGlnbjogaW5pdGlhbDsgYmFja2dyb3VuZC1jb2xvcjogcmdiKDI1NSwgMjU1LCAyNTUpOyI+DQpJ
IHVuZGVyc3RhbmQgdGhhdCBjZXJ0YWluIGxhd3MgYW5kIGN1bHR1cmFsIOKAjmF0dGl0dWRlcyBp
biBzb21lIHBsYWNlcyBtYXkgbWFrZSBzb21lIGZlZWwgdW5jb21mb3J0YWJsZS4gQXMgYSBCcml0
aXNoIGNpdGl6ZW4gc2VlaW5nIE1hbHZpbmFzIFNvbiBBcmVudGluYXMgcG9zdGVycyBhbGwgb3Zl
ciBCdWVub3MgQWlyZXMgd2FzIG5vdCB0aGUgbW9zdCB3ZWxjb21lIHNpZ2h0IHRvIG1lIGFuZCB0
byBhIGRlZ3JlZSBvZmZlbmRzIHNvbWUgb2YgbXkNCiBwYXJ0aWN1bGFyIHNlbnNpYmlsaXRpZXMg
YW5kIGlmIEkgd2Fsa2VkIGFyb3VuZCBQbGF6YSBkZSBNYXlvIHdlYXJpbmcgYSB1bmlvbiBqYWNr
IHQtIHNoaXJ0IEkgdGhpbmsgSSBtaWdodCBnZXQgYSBob3N0aWxlIHJlYWN0aW9uIGJ1dCB0aGF0
IGRvZXNuJ3QgbWVhbiBBcmdlbnRpbmEgc2hvdWxkIGJlIG9mZiBsaW1pdHMgdG8gSUVURi4gV2hl
biB2aXNpdGluZyBhbm90aGVyIGNvdW50cnkgeW91IGFyZSBhIGd1ZXN0IHRoZXJlIGFuZCB5b3Ug
bmVlZA0KIHRvIGJlIHdpbGxpbmcgdG8gY29uZm9ybSB5b3VyIHB1YmxpYyBiZWhhdmlvciBpbiBv
cmRlciB0byBub3Qgb2ZmZW5kIHRoZSBob3N0cyBhbmQgbm90IHZpb2xhdGUgbG9jYWwgbGF3cyBh
bmQgdGhhdCB5b3UgbWF5IGhhdmUgdG8gYWNjZXB0IHRoYXQgeW91IG1heSBub3QgYWx3YXlzIGhh
dmUgdGhlIHNhbWUgZnJlZWRvbXMgeW91IGVuam95IGF0IGhvbWUuIFdoZW4gaW4gUm9tZS4uLi4u
PC9kaXY+DQo8ZGl2IHN0eWxlPSJ3aWR0aDogMTAwJTsgZm9udC1zaXplOiBpbml0aWFsOyBmb250
LWZhbWlseTogQ2FsaWJyaSwgJ1NsYXRlIFBybycsIHNhbnMtc2VyaWYsIHNhbnMtc2VyaWY7IGNv
bG9yOiByZ2IoMzEsIDczLCAxMjUpOyB0ZXh0LWFsaWduOiBpbml0aWFsOyBiYWNrZ3JvdW5kLWNv
bG9yOiByZ2IoMjU1LCAyNTUsIDI1NSk7Ij4NCjxicj4NCjwvZGl2Pg0KPGRpdiBzdHlsZT0id2lk
dGg6IDEwMCU7IGZvbnQtc2l6ZTogaW5pdGlhbDsgZm9udC1mYW1pbHk6IENhbGlicmksICdTbGF0
ZSBQcm8nLCBzYW5zLXNlcmlmLCBzYW5zLXNlcmlmOyBjb2xvcjogcmdiKDMxLCA3MywgMTI1KTsg
dGV4dC1hbGlnbjogaW5pdGlhbDsgYmFja2dyb3VuZC1jb2xvcjogcmdiKDI1NSwgMjU1LCAyNTUp
OyI+DQpJIGRvbid0IHRoaW5rIHRoZSBJRVRGIHNob3VsZCBib3ljb3R0IGxvY2F0aW9ucyBqdXN0
IGJlY2F1c2UgdGhlIGNvbW11bml0eSBkb2Vzbid0IGxpa2Ugc29tZSBvZiB0aGUgbGF3cyBvZiB0
aGF0IGNvdW50cnkgb3IgYXNwZWN0cyBvZiB0aGF0IGNvdW50cmllcyBnb3Zlcm5tZW50cyBwb2xp
Y2llc+KAji4gJm5ic3A7VGhhdCBpcyBhIHZlcnkgc2xpcHBlcnkgc2xvcGUgdGhhdCBjb3VsZCBz
aWduaWZpY2FudGx5IHJlZHVjZSB0aGUgbnVtYmVyIG9mIHBvc3NpYmxlDQogbWVldGluZyBsb2Nh
dGlvbnMgYW5kIGFsc28gZGlzdHJhY3QgZnJvbSB0aGUgSUVURiBtaXNzaW9uLjwvZGl2Pg0KPGRp
diBzdHlsZT0id2lkdGg6IDEwMCU7IGZvbnQtc2l6ZTogaW5pdGlhbDsgZm9udC1mYW1pbHk6IENh
bGlicmksICdTbGF0ZSBQcm8nLCBzYW5zLXNlcmlmLCBzYW5zLXNlcmlmOyBjb2xvcjogcmdiKDMx
LCA3MywgMTI1KTsgdGV4dC1hbGlnbjogaW5pdGlhbDsgYmFja2dyb3VuZC1jb2xvcjogcmdiKDI1
NSwgMjU1LCAyNTUpOyI+DQo8YnI+DQo8L2Rpdj4NCjxkaXYgc3R5bGU9IndpZHRoOiAxMDAlOyBm
b250LXNpemU6IGluaXRpYWw7IGZvbnQtZmFtaWx5OiBDYWxpYnJpLCAnU2xhdGUgUHJvJywgc2Fu
cy1zZXJpZiwgc2Fucy1zZXJpZjsgY29sb3I6IHJnYigzMSwgNzMsIDEyNSk7IHRleHQtYWxpZ246
IGluaXRpYWw7IGJhY2tncm91bmQtY29sb3I6IHJnYigyNTUsIDI1NSwgMjU1KTsiPg0KSSB0aGlu
ayB0aGUgaGFyZCBhbmQgZmFzdCBjcml0ZXJpYSBzaG91bGQgYmUgaXMgdGhlIGxvY2F0aW9uICZu
YnNwO2luIHByYWN0aWNlIG9wZW4gZm9yIGV2ZXJ54oCOYm9keSB0byBhdHRlbmQgYW5kIHdpbGwg
dGhlIGF0dGVuZGVlcyBiZSByZWFzb25hYmx5IHNhZmUgdGhlcmUuPC9kaXY+DQo8ZGl2IHN0eWxl
PSJ3aWR0aDogMTAwJTsgZm9udC1zaXplOiBpbml0aWFsOyBmb250LWZhbWlseTogQ2FsaWJyaSwg
J1NsYXRlIFBybycsIHNhbnMtc2VyaWYsIHNhbnMtc2VyaWY7IGNvbG9yOiByZ2IoMzEsIDczLCAx
MjUpOyB0ZXh0LWFsaWduOiBpbml0aWFsOyBiYWNrZ3JvdW5kLWNvbG9yOiByZ2IoMjU1LCAyNTUs
IDI1NSk7Ij4NCjxicj4NCjwvZGl2Pg0KPGRpdiBzdHlsZT0id2lkdGg6IDEwMCU7IGZvbnQtc2l6
ZTogaW5pdGlhbDsgZm9udC1mYW1pbHk6IENhbGlicmksICdTbGF0ZSBQcm8nLCBzYW5zLXNlcmlm
LCBzYW5zLXNlcmlmOyBjb2xvcjogcmdiKDMxLCA3MywgMTI1KTsgdGV4dC1hbGlnbjogaW5pdGlh
bDsgYmFja2dyb3VuZC1jb2xvcjogcmdiKDI1NSwgMjU1LCAyNTUpOyI+DQpBbmRyZXcgPC9kaXY+
DQo8ZGl2IHN0eWxlPSJ3aWR0aDogMTAwJTsgZm9udC1zaXplOiBpbml0aWFsOyBmb250LWZhbWls
eTogQ2FsaWJyaSwgJ1NsYXRlIFBybycsIHNhbnMtc2VyaWYsIHNhbnMtc2VyaWY7IGNvbG9yOiBy
Z2IoMzEsIDczLCAxMjUpOyB0ZXh0LWFsaWduOiBpbml0aWFsOyBiYWNrZ3JvdW5kLWNvbG9yOiBy
Z2IoMjU1LCAyNTUsIDI1NSk7Ij4NCjxicj4NCjwvZGl2Pg0KPGRpdiBzdHlsZT0iZm9udC1zaXpl
OiBpbml0aWFsOyBmb250LWZhbWlseTogQ2FsaWJyaSwgJ1NsYXRlIFBybycsIHNhbnMtc2VyaWYs
IHNhbnMtc2VyaWY7IGNvbG9yOiByZ2IoMzEsIDczLCAxMjUpOyB0ZXh0LWFsaWduOiBpbml0aWFs
OyBiYWNrZ3JvdW5kLWNvbG9yOiByZ2IoMjU1LCAyNTUsIDI1NSk7Ij4NClNlbnQmbmJzcDtmcm9t
Jm5ic3A7bXkmbmJzcDtCbGFja0JlcnJ5Jm5ic3A7MTAmbmJzcDtzbWFydHBob25lLjwvZGl2Pg0K
PHRhYmxlIHdpZHRoPSIxMDAlIiBzdHlsZT0iYmFja2dyb3VuZC1jb2xvcjp3aGl0ZTtib3JkZXIt
c3BhY2luZzowcHg7Ij4NCjx0Ym9keT4NCjx0cj4NCjx0ZCBjb2xzcGFuPSIyIiBzdHlsZT0iZm9u
dC1zaXplOiBpbml0aWFsOyB0ZXh0LWFsaWduOiBpbml0aWFsOyBiYWNrZ3JvdW5kLWNvbG9yOiBy
Z2IoMjU1LCAyNTUsIDI1NSk7Ij4NCjxkaXYgc3R5bGU9ImJvcmRlci1zdHlsZTogc29saWQgbm9u
ZSBub25lOyBib3JkZXItdG9wLWNvbG9yOiByZ2IoMTgxLCAxOTYsIDIyMyk7IGJvcmRlci10b3At
d2lkdGg6IDFwdDsgcGFkZGluZzogM3B0IDBpbiAwaW47IGZvbnQtZmFtaWx5OiBUYWhvbWEsICdC
QiBBbHBoYSBTYW5zJywgJ1NsYXRlIFBybyc7IGZvbnQtc2l6ZTogMTBwdDsiPg0KPGRpdj48Yj5G
cm9tOiA8L2I+RGF2aWQgQ29ucmFkPC9kaXY+DQo8ZGl2PjxiPlNlbnQ6IDwvYj5UaHVyc2RheSwg
QXByaWwgNywgMjAxNiAxNzoyMDwvZGl2Pg0KPGRpdj48Yj5UbzogPC9iPkRocnV2IERob2R5PC9k
aXY+DQo8ZGl2PjxiPkNjOiA8L2I+aWV0ZkBpZXRmLm9yZyBEaXNjdXNzaW9uPC9kaXY+DQo8ZGl2
PjxiPlN1YmplY3Q6IDwvYj5SZTogQ29uY2VybnMgYWJvdXQgU2luZ2Fwb3JlPC9kaXY+DQo8L2Rp
dj4NCjwvdGQ+DQo8L3RyPg0KPC90Ym9keT4NCjwvdGFibGU+DQo8ZGl2IHN0eWxlPSJib3JkZXIt
c3R5bGU6IHNvbGlkIG5vbmUgbm9uZTsgYm9yZGVyLXRvcC1jb2xvcjogcmdiKDE4NiwgMTg4LCAy
MDkpOyBib3JkZXItdG9wLXdpZHRoOiAxcHQ7IGZvbnQtc2l6ZTogaW5pdGlhbDsgdGV4dC1hbGln
bjogaW5pdGlhbDsgYmFja2dyb3VuZC1jb2xvcjogcmdiKDI1NSwgMjU1LCAyNTUpOyI+DQo8L2Rp
dj4NCjxicj4NCjxkaXYgaWQ9Il9vcmlnaW5hbENvbnRlbnQiIHN0eWxlPSIiPg0KPGRpdj4NCjxi
bG9ja3F1b3RlIHR5cGU9ImNpdGUiIGNsYXNzPSIiPg0KPGRpdiBjbGFzcz0iIj4NCjxkaXYgZGly
PSJsdHIiIGNsYXNzPSIiPg0KPGRpdiBjbGFzcz0iZ21haWxfZXh0cmEiPg0KPGRpdiBjbGFzcz0i
Z21haWxfcXVvdGUiPg0KPGRpdiBjbGFzcz0iIj4NCjxkaXYgY2xhc3M9ImdtYWlsX2RlZmF1bHQi
IHN0eWxlPSJmb250LWZhbWlseTomcXVvdDt0cmVidWNoZXQgbXMmcXVvdDssc2Fucy1zZXJpZjtj
b2xvcjpyZ2IoNzYsMTcsNDgpIj4NCuKAi05vLCBJIG1lYW50IHRoYXQgSUVURiB3b3VsZCBiZSBk
b2luZyBhIGRpc3NlcnZpY2UgdG8gYSBsYXJnZSBwYXJ0IG9mIHRoZSB3b3JsZCAodGhhdCBoYXMg
b24gaXRzIGJvb2tzIHRoZXNlIGxhd3MpLg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+
DQo8L2Rpdj4NCjwvZGl2Pg0KPC9ibG9ja3F1b3RlPg0KPGRpdj48YnIgY2xhc3M9IiI+DQo8L2Rp
dj4NCjxkaXY+Rm9yIHJlZmVyZW5jZTo8L2Rpdj4NCjxkaXY+PGJyIGNsYXNzPSIiPg0KPC9kaXY+
DQo8ZGl2PjxhIGhyZWY9Imh0dHA6Ly83NmNyaW1lcy5jb20vNzYtY291bnRyaWVzLXdoZXJlLWhv
bW9zZXh1YWxpdHktaXMtaWxsZWdhbC8iIGNsYXNzPSIiPmh0dHA6Ly83NmNyaW1lcy5jb20vNzYt
Y291bnRyaWVzLXdoZXJlLWhvbW9zZXh1YWxpdHktaXMtaWxsZWdhbC88L2E+PC9kaXY+DQo8ZGl2
PjxiciBjbGFzcz0iIj4NCjwvZGl2Pg0KPGRpdj4oaGF2ZW4ndCB2ZXJpZmllZCwgYnV0IEkgcmVh
ZCBpdCBvbiB0aGUgSW50ZXJuZXQgc28gaXQgbXVzdCBiZSB0cnVlKTwvZGl2Pg0KPGRpdj48YnIg
Y2xhc3M9IiI+DQo8L2Rpdj4NCjxkaXY+UmVnYXJkcyw8L2Rpdj4NCjxkaXY+LWRyYzwvZGl2Pg0K
PGRpdj48YnIgY2xhc3M9IiI+DQo8L2Rpdj4NCjwvZGl2Pg0KPGJyPg0KPCEtLWVuZCBvZiBfb3Jp
Z2luYWxDb250ZW50IC0tPjwvZGl2Pg0KPGJyPg0KPGJyPg0KPGJyPg0KPGJyPg0KPGJyPg0KPGJy
Pg0KPGJyPg0KPGJyPg0KPGJyPg0KPGJyPg0KPGJyPg0KPGJyPg0KPGJyPg0KPC9ib2R5Pg0KPC9o
dG1sPg0K

--_000_2016040915530062833484125510529blackberrycom_--


From nobody Sat Apr  9 10:15:27 2016
Return-Path: <ynir.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 0113312B009 for <ietf@ietfa.amsl.com>; Sat,  9 Apr 2016 10:15:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.799
X-Spam-Level: 
X-Spam-Status: No, score=-0.799 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 g89maiweqZuY for <ietf@ietfa.amsl.com>; Sat,  9 Apr 2016 10:15:24 -0700 (PDT)
Received: from mail-wm0-x22a.google.com (mail-wm0-x22a.google.com [IPv6:2a00:1450:400c:c09::22a]) (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 71A5912B004 for <ietf@ietf.org>; Sat,  9 Apr 2016 10:15:24 -0700 (PDT)
Received: by mail-wm0-x22a.google.com with SMTP id n3so56207762wmn.0 for <ietf@ietf.org>; Sat, 09 Apr 2016 10:15:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:subject:from:in-reply-to:date:cc:message-id:references :to; bh=OOF/tpTMd7oJGUagniu2xLNNI46Fa71redmAxQ/9hno=; b=r0X2j4oqo/p6iL2gtTJw/BGtNLmNqe54nrKmT1MdM4yEe3Es+to7OIl6zz+OWAmCdB o9xn6CLiYznv3p5FH6x0XaKuulzOffKQIcHBzi6FNZ563ShIbq/qGmeNceTwUUqO3CFy eLXYD98cR5uQD52l0wdF4P+k4fhnszosU4eZF87noTHWqh/4lMcLYmeEJFFF3TeA6/ZK pCfbM8rRV0advSBfdlOJ8E7YkUgai/WWSNO7jrAhcWIRwoKwGPdCFgBhQUoo19Y1uAxH +eXzQSje3foE27eXUEZjFqXI3GVKqbamve0pcItgJOncErN5PoXP6qYMcAE8W2svpBeJ fHYA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :message-id:references:to; bh=OOF/tpTMd7oJGUagniu2xLNNI46Fa71redmAxQ/9hno=; b=KllMp4Vm/e14aASkcu9ZI4KyFtD4BIxVoXslzZmaS50sv100ONSeAGOg1YsmRZfx/O OMDCopt+lY3fBZxyRFey+Sf/ZCsmh3fY73DIqtULRJqXRvCQ7wy0xy+565PfYxNax/FF KRZuOWOHBTBlqnoTP6/JTjdpkYimb6m777tmTulECmKced6PNzDqpUL9z0cBNRWEjtUD Cz3cFKOG6m1sSKYrf97PR5ptkxniIc0g3mT5baxkKMuAS8orKMXxhMn86badZDHXFc0r 9xVq2kw55LJPROjrgN19GduoFOs6M+ZNMO7vzW1LiURBiFui9mOY5wbLq7lTzuvqAQGm w3Lg==
X-Gm-Message-State: AD7BkJKhbRX0RzAsOIPmjSfIX9YdJoTYMB1DiwY35b7lNgdJ04wqQcXUlcSXoJVJRNoDRw==
X-Received: by 10.194.192.106 with SMTP id hf10mr14836095wjc.134.1460222122982;  Sat, 09 Apr 2016 10:15:22 -0700 (PDT)
Received: from [10.81.8.143] ([195.76.232.154]) by smtp.gmail.com with ESMTPSA id d123sm8598287wmd.9.2016.04.09.10.15.21 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Sat, 09 Apr 2016 10:15:22 -0700 (PDT)
Content-Type: multipart/alternative; boundary="Apple-Mail=_DD194944-C96A-4ED4-A3F8-BFAB569BA831"
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Subject: Re: Concerns about Singapore
From: Yoav Nir <ynir.ietf@gmail.com>
In-Reply-To: <20160409155300.6283348.41255.10529@blackberry.com>
Date: Sat, 9 Apr 2016 19:15:21 +0200
Message-Id: <ADC8666A-436C-4AD4-BD48-9277601069F8@gmail.com>
References: <0D914666-C3D4-4CCE-AD5E-4E5B34EA1A73@piuha.net> <20160407182936.GA21340@pfrc.org> <CAB75xn780nNDjGa_Cc222J20-+1CCHt09Xp8KHzaK=n0xx51pg@mail.gmail.com> <5706B100.9040509@mnt.se> <CAB75xn6fmj84ROUtG5eUB3GerHx83hrEr3w5vSADY_g=BRg5FA@mail.gmail.com> <9B723FB0-6B93-4C85-ADD9-D423F873CF08@virtualized.org> <20160409155300.6283348.41255.10529@blackberry.com>
To: Andrew Allen <aallen@blackberry.com>
X-Mailer: Apple Mail (2.3124)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/n_2UqR6NBhk4c7wvUq6_KcK4ock>
Cc: "ietf@ietf.org 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: Sat, 09 Apr 2016 17:15:26 -0000

--Apple-Mail=_DD194944-C96A-4ED4-A3F8-BFAB569BA831
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Hi, Andrew


> I don't think the IETF should boycott locations just because the =
community doesn't like some of the laws of that country or aspects of =
that countries governments policies=E2=80=8E.  That is a very slippery =
slope that could significantly reduce the number of possible meeting =
locations and also distract from the IETF mission.

I generally agree with this. However:

> Having been to Singapore once before I am certain there are no room =
police patrolling the hotel corridors trying to ascertain what =
activities the guests are up to in their own rooms. There were also no =
personal questions asked at hotel registration as far as I recall ( I am =
sure I would have remembered that) so I don't see it as an especially =
hostile environment.=E2=80=8E I think the IETF should confirm with the =
meeting hotels that there will be no issues in that regard and also a =
check with the Singapore authorities that there will be no threat to =
IETF participants because of their orientation or marital status would =
be a sensible measure.

I=E2=80=99m sure they didn=E2=80=99t ask *you* any questions. But you =
might have gotten some response if you tried to check in with another =
man into a room that had just one bed.  I=E2=80=99m not saying that you =
would. I don=E2=80=99t know, having never been in Singapore, but I can =
understand that it would be a concern.=20

Yoav


--Apple-Mail=_DD194944-C96A-4ED4-A3F8-BFAB569BA831
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D"">Hi, Andrew<div class=3D""><br class=3D""></div><div =
class=3D""><br class=3D""></div><div class=3D""><blockquote type=3D"cite" =
class=3D""><div class=3D"" lang=3D"en-US" style=3D"background-color: =
rgb(255, 255, 255); line-height: initial;"><div class=3D"" style=3D"width:=
 1222px; font-size: initial; font-family: Calibri, 'Slate Pro', =
sans-serif, sans-serif; color: rgb(31, 73, 125); text-align: initial;">I =
don't think the IETF should boycott locations just because the community =
doesn't like some of the laws of that country or aspects of that =
countries governments policies=E2=80=8E. &nbsp;That is a very slippery =
slope that could significantly reduce the number of possible meeting =
locations and also distract from the IETF =
mission.</div></div></blockquote><div class=3D""><br class=3D""></div>I =
generally agree with this. However:</div><div class=3D""><br =
class=3D""></div><div class=3D""><blockquote type=3D"cite" class=3D""><div=
 class=3D"" lang=3D"en-US" style=3D"background-color: rgb(255, 255, =
255); line-height: initial;"><div class=3D"" style=3D"width: 1222px; =
font-size: initial; font-family: Calibri, 'Slate Pro', sans-serif, =
sans-serif; color: rgb(31, 73, 125); text-align: initial;">Having been =
to Singapore once before I am certain there are no room police =
patrolling the hotel corridors trying to ascertain what activities the =
guests are up to in their own rooms. There were also no personal =
questions asked at hotel registration as far as I recall ( I am sure I =
would have remembered that) so I don't see it as an especially hostile =
environment.=E2=80=8E I think the IETF should confirm with the meeting =
hotels that there will be no issues in that regard and also a check with =
the Singapore authorities that there will be no threat to IETF =
participants because of their orientation or marital status would be a =
sensible measure.</div></div></blockquote><div class=3D""><br =
class=3D""></div>I=E2=80=99m sure they didn=E2=80=99t ask *you* any =
questions. But you might have gotten some response if you tried to check =
in with another man into a room that had just one bed. &nbsp;I=E2=80=99m =
not saying that you would. I don=E2=80=99t know, having never been in =
Singapore, but I can understand that it would be a concern.&nbsp;<br =
class=3D""><br class=3D"">Yoav</div><div class=3D""><br =
class=3D""></div></body></html>=

--Apple-Mail=_DD194944-C96A-4ED4-A3F8-BFAB569BA831--


From nobody Sat Apr  9 10:30:54 2016
Return-Path: <melinda.shore@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 475C712B064 for <ietf@ietfa.amsl.com>; Sat,  9 Apr 2016 10:30:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.8
X-Spam-Level: 
X-Spam-Status: No, score=-0.8 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 MMXoQkhXIZAV for <ietf@ietfa.amsl.com>; Sat,  9 Apr 2016 10:30:51 -0700 (PDT)
Received: from mail-pf0-x234.google.com (mail-pf0-x234.google.com [IPv6:2607:f8b0:400e:c00::234]) (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 27E8812B049 for <ietf@ietf.org>; Sat,  9 Apr 2016 10:30:51 -0700 (PDT)
Received: by mail-pf0-x234.google.com with SMTP id 184so95525514pff.0 for <ietf@ietf.org>; Sat, 09 Apr 2016 10:30:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding; bh=ZG+iYD7K0MaQ/8A+ecrt97h/avTwTmJGk+u9MPlP1x0=; b=hb2bceg28h6jFCOPdKiI+TgYqk7I1iflQ/LFDuUVWJYj+mS5lg2NLokqOYuwSqK7J2 PqNxbfFh7qojyANn23utG21GvJsm+IS5tFvKzYQV/B7u5yzjxi1HdJScZG2MX//KhmF/ u6dMo1ziLDjRli4s9uz6vCHJ6NeB2v9iQwbSOpofVJg/pNzHxv9dRfSDqyfiu1sB60J7 BQ+Hu/kXYBZTRXKYUpA3AJUGKPqXOVSTeWT3UwultTyBtab8xCtBdKt+9LmnMlwAZLav 2BUYA/XJ6Nx0C2NvKqde/h9kn2ymdFVV7rqEMymQLFOsRk9uGQsSXFgRxrscU6SAQNa/ A+BQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=ZG+iYD7K0MaQ/8A+ecrt97h/avTwTmJGk+u9MPlP1x0=; b=DUxRYCX6r5tw1J6KQs8RM4QhK58jjcZAb3kKzOh/tD258JfbMs9NHodQLoYv3Hu6xH VlbRLet+raqOm9DIM0OW/Ca5kMvL3OV2Z8AkT4CblvVxAiyTLN1Vlvli32G5u/pPGMqS VVNlwh5jnhM77Wz/ew1Y0BUOIMTdBmdw9k8jiAX6GbVIWCkDEXLLulpwhhRd2KRqrQ/2 j2YpB7lefmr+eSdVLONIb6cClExSXylGNs4MmdvLsjCRfGXsH925art8G8gLJm98qCOx ZVsROFv0h0ODCagu+JwMViWNj9UuAZUxiOE7wHHPSEylWNGP/36dcia5xwkyya1OG4Yi MBNQ==
X-Gm-Message-State: AD7BkJLepCCJAFUqMAzrSNQieSdwH9z4dryCvwTkX0/dOCuRGK7/ChP1MMlKLKa3geRzVQ==
X-Received: by 10.98.67.67 with SMTP id q64mr21289524pfa.44.1460223050732; Sat, 09 Apr 2016 10:30:50 -0700 (PDT)
Received: from Melindas-MacBook-Pro.local (63-140-90-11-radius.dynamic.acsalaska.net. [63.140.90.11]) by smtp.googlemail.com with ESMTPSA id p75sm26180545pfi.29.2016.04.09.10.30.49 for <ietf@ietf.org> (version=TLSv1/SSLv3 cipher=OTHER); Sat, 09 Apr 2016 10:30:49 -0700 (PDT)
Subject: Re: Concerns about Singapore
To: ietf@ietf.org
References: <0D914666-C3D4-4CCE-AD5E-4E5B34EA1A73@piuha.net> <20160407182936.GA21340@pfrc.org> <CAB75xn780nNDjGa_Cc222J20-+1CCHt09Xp8KHzaK=n0xx51pg@mail.gmail.com> <5706B100.9040509@mnt.se> <CAB75xn6fmj84ROUtG5eUB3GerHx83hrEr3w5vSADY_g=BRg5FA@mail.gmail.com> <9B723FB0-6B93-4C85-ADD9-D423F873CF08@virtualized.org> <20160409155300.6283348.41255.10529@blackberry.com> <ADC8666A-436C-4AD4-BD48-9277601069F8@gmail.com>
From: Melinda Shore <melinda.shore@gmail.com>
Message-ID: <57093CD3.3050502@gmail.com>
Date: Sat, 9 Apr 2016 09:33:07 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:38.0) Gecko/20100101 Thunderbird/38.6.0
MIME-Version: 1.0
In-Reply-To: <ADC8666A-436C-4AD4-BD48-9277601069F8@gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/WeLJDTQhdFBPLhTkE0FbaBFWFD8>
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, 09 Apr 2016 17:30:52 -0000

On 4/9/16 9:15 AM, Yoav Nir wrote:
> Iâ€™m sure they didnâ€™t ask *you* any questions. But you might have gotten
> some response if you tried to check in with another man into a room that
> had just one bed.  Iâ€™m not saying that you would. I donâ€™t know, having
> never been in Singapore, but I can understand that it would be a concern.

I was discussing this a little bit with my partner this morning
and she pointed out that in many cases where we would find the
laws ridiculous, those laws are not actually enforceable (for
example, French laws against women wearing pants).  The problem
with the situation in Singapore is that the laws that are on
the books appear to be quite enforceable, with the Singapore
Supreme Court having upheld laws banning consensual same-sex
relationships as recently as late 2014 (one of the plaintiffs
had been arrested in 2010).

To the extent that these laws appears to be enforceable and
that there is uncertainty about whether or not some of our
participants are likely to run into issues with public
accommodation, etc., I'm grateful that the IAOC is treating
this as a serious issue.

Melinda


From nobody Sat Apr  9 11:58:22 2016
Return-Path: <joelja@bogus.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 B8A1D12D0F2 for <ietf@ietfa.amsl.com>; Sat,  9 Apr 2016 11:58:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.996
X-Spam-Level: 
X-Spam-Status: No, score=-5.996 tagged_above=-999 required=5 tests=[RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.996] 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 RYPhYU2PNYif for <ietf@ietfa.amsl.com>; Sat,  9 Apr 2016 11:58:19 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) (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 9AE5112D0C2 for <ietf@ietf.org>; Sat,  9 Apr 2016 11:58:19 -0700 (PDT)
Received: from mb-2.local (201-250-43-110.speedy.com.ar [201.250.43.110] (may be forged)) (authenticated bits=0) by nagasaki.bogus.com (8.14.9/8.14.9) with ESMTP id u39IwBnC038635 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Sat, 9 Apr 2016 18:58:15 GMT (envelope-from joelja@bogus.com)
Subject: Re: Concerns about Singapore
To: Melinda Shore <melinda.shore@gmail.com>, ietf@ietf.org
References: <0D914666-C3D4-4CCE-AD5E-4E5B34EA1A73@piuha.net> <20160407182936.GA21340@pfrc.org> <CAB75xn780nNDjGa_Cc222J20-+1CCHt09Xp8KHzaK=n0xx51pg@mail.gmail.com> <5706B100.9040509@mnt.se> <CAB75xn6fmj84ROUtG5eUB3GerHx83hrEr3w5vSADY_g=BRg5FA@mail.gmail.com> <9B723FB0-6B93-4C85-ADD9-D423F873CF08@virtualized.org> <20160409155300.6283348.41255.10529@blackberry.com> <ADC8666A-436C-4AD4-BD48-9277601069F8@gmail.com> <57093CD3.3050502@gmail.com>
From: joel jaeggli <joelja@bogus.com>
Message-ID: <f5b1ceec-4cd5-55b5-5089-4a499ed0586c@bogus.com>
Date: Sat, 9 Apr 2016 15:58:02 -0300
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.0
MIME-Version: 1.0
In-Reply-To: <57093CD3.3050502@gmail.com>
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="39F37NKFngK9XI52oQUPtmdI2GIiU8nUb"
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/jllA5pLQi01CL3mfG6rcvQreJ-Y>
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, 09 Apr 2016 18:58:20 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--39F37NKFngK9XI52oQUPtmdI2GIiU8nUb
Content-Type: multipart/mixed; boundary="kQk4OMwEp9RcUndQ0qX0Vu3UNtLjoxkwG"
From: joel jaeggli <joelja@bogus.com>
To: Melinda Shore <melinda.shore@gmail.com>, ietf@ietf.org
Message-ID: <f5b1ceec-4cd5-55b5-5089-4a499ed0586c@bogus.com>
Subject: Re: Concerns about Singapore
References: <0D914666-C3D4-4CCE-AD5E-4E5B34EA1A73@piuha.net>
 <20160407182936.GA21340@pfrc.org>
 <CAB75xn780nNDjGa_Cc222J20-+1CCHt09Xp8KHzaK=n0xx51pg@mail.gmail.com>
 <5706B100.9040509@mnt.se>
 <CAB75xn6fmj84ROUtG5eUB3GerHx83hrEr3w5vSADY_g=BRg5FA@mail.gmail.com>
 <9B723FB0-6B93-4C85-ADD9-D423F873CF08@virtualized.org>
 <20160409155300.6283348.41255.10529@blackberry.com>
 <ADC8666A-436C-4AD4-BD48-9277601069F8@gmail.com> <57093CD3.3050502@gmail.com>
In-Reply-To: <57093CD3.3050502@gmail.com>

--kQk4OMwEp9RcUndQ0qX0Vu3UNtLjoxkwG
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

On 4/9/16 2:33 PM, Melinda Shore wrote:
> On 4/9/16 9:15 AM, Yoav Nir wrote:
>> I=E2=80=99m sure they didn=E2=80=99t ask *you* any questions. But you =
might have gotten
>> some response if you tried to check in with another man into a room th=
at
>> had just one bed.  I=E2=80=99m not saying that you would. I don=E2=80=99=
t know, having
>> never been in Singapore, but I can understand that it would be a conce=
rn.
>=20
> I was discussing this a little bit with my partner this morning
> and she pointed out that in many cases where we would find the
> laws ridiculous, those laws are not actually enforceable (for
> example, French laws against women wearing pants). =20

"Loi interdisant la dissimulation du visage dans l'espace public" is
probably also ridiculous but readily enforced and fairly recently
upheld, so it's not like interdictions on personal freedom, self
expression or conscience are not still being readily or facilely adopted
in Europe.  Which is not to say that  one views all such restrictions
as qualitatively the same, I do not.



> The problem
> with the situation in Singapore is that the laws that are on
> the books appear to be quite enforceable, with the Singapore
> Supreme Court having upheld laws banning consensual same-sex
> relationships as recently as late 2014 (one of the plaintiffs
> had been arrested in 2010).
>=20
> To the extent that these laws appears to be enforceable and
> that there is uncertainty about whether or not some of our
> participants are likely to run into issues with public
> accommodation, etc., I'm grateful that the IAOC is treating
> this as a serious issue.
>=20
> Melinda
>=20



--kQk4OMwEp9RcUndQ0qX0Vu3UNtLjoxkwG--

--39F37NKFngK9XI52oQUPtmdI2GIiU8nUb
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2
Comment: GPGTools - http://gpgtools.org

iEYEARECAAYFAlcJULsACgkQ8AA1q7Z/VrJuzgCfeQ2idlcBfwdTc0xXhkOK2q8+
LA8An3py0jYJJ4/C5EirwTtVp+/jQ6re
=lw74
-----END PGP SIGNATURE-----

--39F37NKFngK9XI52oQUPtmdI2GIiU8nUb--


From nobody Sat Apr  9 12:01:19 2016
Return-Path: <fred@cisco.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 A477412D105 for <ietf@ietfa.amsl.com>; Sat,  9 Apr 2016 12:01:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -113.617
X-Spam-Level: 
X-Spam-Status: No, score=-113.617 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.996, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 AO4XqokPsXf1 for <ietf@ietfa.amsl.com>; Sat,  9 Apr 2016 12:01:17 -0700 (PDT)
Received: from alln-iport-1.cisco.com (alln-iport-1.cisco.com [173.37.142.88]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A4C2E12D0FA for <ietf@ietf.org>; Sat,  9 Apr 2016 12:01:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3264; q=dns/txt; s=iport; t=1460228476; x=1461438076; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=G/jcEIR3OYItjfjHuuv2VDlxqEbiwLaEJYwGRhKxisw=; b=T/vqzNSbmXpGM3V99p358i1dXhUjNbUhXVnvpLgq5LynrSYmdDr+Ekjp J8AjFbu6szrH3oWT5AIlufonNbzPK/0oaH9ODQXeOWPkbvjpMzE4wJZJP w/JIw+IHujN+JcRx8Ms+0zCutEfl/Lp4Lv3ooMf0d8z53hEsGvRrJfVqj 0=;
X-Files: signature.asc : 833
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0BaBQCNUAlX/4ENJK1cgzeBUAa6XIFzh?= =?us-ascii?q?g0CgSo6EgEBAQEBAQFlJ4RBAQEBAwEjTgEHBQsCAQgYKgICMiUCBA4FDogRCKk?= =?us-ascii?q?BkTgBAQEBAQEBAQEBAQEBAQEBAQEBAQENCIgWCIJOhz8rgisFmAQBgyOBZokCj?= =?us-ascii?q?w2PJQEnBjWDZ2yILn4BAQE?=
X-IronPort-AV: E=Sophos;i="5.24,460,1454976000";  d="asc'?scan'208";a="259567977"
Received: from alln-core-9.cisco.com ([173.36.13.129]) by alln-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 09 Apr 2016 19:01:15 +0000
Received: from XCH-RCD-015.cisco.com (xch-rcd-015.cisco.com [173.37.102.25]) by alln-core-9.cisco.com (8.14.5/8.14.5) with ESMTP id u39J1Flb009760 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Sat, 9 Apr 2016 19:01:15 GMT
Received: from xch-rcd-013.cisco.com (173.37.102.23) by XCH-RCD-015.cisco.com (173.37.102.25) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Sat, 9 Apr 2016 14:01:14 -0500
Received: from xch-rcd-013.cisco.com ([173.37.102.23]) by XCH-RCD-013.cisco.com ([173.37.102.23]) with mapi id 15.00.1104.009; Sat, 9 Apr 2016 14:01:14 -0500
From: "Fred Baker (fred)" <fred@cisco.com>
To: joel jaeggli <joelja@bogus.com>
Subject: Re: Concerns about Singapore
Thread-Topic: Concerns about Singapore
Thread-Index: AQHRkOMYE5f4WLltSk+KMEq8Vk+KKZ9/KOsAgAAATwCAAAuKAIAACE2AgAAKzQCAAtn5gIAAFv+AgAAE94CAABe5AIAAAOSA
Date: Sat, 9 Apr 2016 19:01:14 +0000
Message-ID: <F2D3ACF5-C7BD-4D0C-8518-665D2EDAA6CA@cisco.com>
References: <0D914666-C3D4-4CCE-AD5E-4E5B34EA1A73@piuha.net> <20160407182936.GA21340@pfrc.org> <CAB75xn780nNDjGa_Cc222J20-+1CCHt09Xp8KHzaK=n0xx51pg@mail.gmail.com> <5706B100.9040509@mnt.se> <CAB75xn6fmj84ROUtG5eUB3GerHx83hrEr3w5vSADY_g=BRg5FA@mail.gmail.com> <9B723FB0-6B93-4C85-ADD9-D423F873CF08@virtualized.org> <20160409155300.6283348.41255.10529@blackberry.com> <ADC8666A-436C-4AD4-BD48-9277601069F8@gmail.com> <57093CD3.3050502@gmail.com> <f5b1ceec-4cd5-55b5-5089-4a499ed0586c@bogus.com>
In-Reply-To: <f5b1ceec-4cd5-55b5-5089-4a499ed0586c@bogus.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-mailer: Apple Mail (2.3124)
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.19.64.119]
Content-Type: multipart/signed; boundary="Apple-Mail=_85FD2C08-B532-485F-B800-5A9579A8C9EF"; protocol="application/pgp-signature"; micalg=pgp-sha1
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/zYhZ7HH1RI9md3MhdLzGfFVQpXg>
Cc: "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: Sat, 09 Apr 2016 19:01:18 -0000

--Apple-Mail=_85FD2C08-B532-485F-B800-5A9579A8C9EF
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

One could mention sodomy laws in Texas; we have met in Houstaon and =
Dalls, I believe, there times.

> On Apr 9, 2016, at 11:58 AM, joel jaeggli <joelja@bogus.com> wrote:
>=20
> On 4/9/16 2:33 PM, Melinda Shore wrote:
>> On 4/9/16 9:15 AM, Yoav Nir wrote:
>>> I=E2=80=99m sure they didn=E2=80=99t ask *you* any questions. But =
you might have gotten
>>> some response if you tried to check in with another man into a room =
that
>>> had just one bed.  I=E2=80=99m not saying that you would. I don=E2=80=99=
t know, having
>>> never been in Singapore, but I can understand that it would be a =
concern.
>>=20
>> I was discussing this a little bit with my partner this morning
>> and she pointed out that in many cases where we would find the
>> laws ridiculous, those laws are not actually enforceable (for
>> example, French laws against women wearing pants).
>=20
> "Loi interdisant la dissimulation du visage dans l'espace public" is
> probably also ridiculous but readily enforced and fairly recently
> upheld, so it's not like interdictions on personal freedom, self
> expression or conscience are not still being readily or facilely =
adopted
> in Europe.  Which is not to say that  one views all such restrictions
> as qualitatively the same, I do not.
>=20
>=20
>=20
>> The problem
>> with the situation in Singapore is that the laws that are on
>> the books appear to be quite enforceable, with the Singapore
>> Supreme Court having upheld laws banning consensual same-sex
>> relationships as recently as late 2014 (one of the plaintiffs
>> had been arrested in 2010).
>>=20
>> To the extent that these laws appears to be enforceable and
>> that there is uncertainty about whether or not some of our
>> participants are likely to run into issues with public
>> accommodation, etc., I'm grateful that the IAOC is treating
>> this as a serious issue.
>>=20
>> Melinda
>>=20
>=20
>=20


--Apple-Mail=_85FD2C08-B532-485F-B800-5A9579A8C9EF
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="signature.asc"
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iQIVAwUBVwlReUayAOS/EQ8MAQIg1xAAiM9HfN8Hv6KUo2T2plHUJxkxdpVbW9XC
+2oPtRaeFbGWqBxllB6Cbmg5m1t1iKZXBP8QfO/JwsYpw4p36cdsU2BgOeVkJ+BE
HOAYuGuPzn9pPH15TPlFXuJg0ecw44Y8J3Hhd7Z55285VaPjsJd1me+wQ+AZexeH
8F9mZyyvGIMk4wxvvzzhblMw9+Pgfj27BoJgZXKZANxaOPJt59UAk9HsyHr2TVV7
uqIUWgyVjpehKx0noJHFnJg4nvwnkU41fUwNhA/evmdCrn1FM0VA49pP/OAj/C3x
JJjDAsDs8RYowO+lCBAkULZkuELS605r6aQuKpTQr4SJ5hGbjOVCYFJaAB4FZMsa
2TF7d5NCsJbM5t3OMvtbOMMBvcgBR4yvI1+5zwBceMRyNcGW+QH4qXzHgJdopu9Z
KO0gXTKNcWvWTHdPuGyUDzLG94MCrlT8Wtet6Ekt2dhisoMFC6R9x7bHMcZtVoMX
pXm0bpiB+zivm3ti5eO2o9UhJ+9xtMoWCz4zHE5jBiUnXn24khIJPBZuxzpAGWuA
vlM32bFiCRRk+sYWA9coVS7v8EJJloKJosRpAdDuROX4e+bgRpiZsrtgai6blzdK
fTXIqWS08ICv/2Nr3aVFNV1KFbgZy/UzDfzbEXujpQVoeBu0TIgPKk3jam3YtkLz
Y3mfPUqw/M8=
=2rOw
-----END PGP SIGNATURE-----

--Apple-Mail=_85FD2C08-B532-485F-B800-5A9579A8C9EF--


From nobody Sat Apr  9 12:17:48 2016
Return-Path: <melinda.shore@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 0556F12D10F for <ietf@ietfa.amsl.com>; Sat,  9 Apr 2016 12:17:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.8
X-Spam-Level: 
X-Spam-Status: No, score=-0.8 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 3KBchaSAYZt4 for <ietf@ietfa.amsl.com>; Sat,  9 Apr 2016 12:17:46 -0700 (PDT)
Received: from mail-ig0-x235.google.com (mail-ig0-x235.google.com [IPv6:2607:f8b0:4001:c05::235]) (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 E55C812D0FF for <ietf@ietf.org>; Sat,  9 Apr 2016 12:17:45 -0700 (PDT)
Received: by mail-ig0-x235.google.com with SMTP id f1so34994739igr.1 for <ietf@ietf.org>; Sat, 09 Apr 2016 12:17:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=sqdUZVykVdXX0erQ0S6G9GIIvNwYHjdb/qiCheTK1kc=; b=wEJjQ4I1ExeB3xPeO9wofk2X70fQgtrY6GxMjV8B1Drs0hXtqd1x4TBVU8jT7PLVwy MoQaPJSSIaw55ku4QdXuAoRIy5z0zAl2IqWpt1qiBUocd+L/J6JEX1HQSkWEM3RnEZYB nS59WeYl92iYBtF86WllHMbW4xjqztLdXVqpfuOleRkcK9Dp0UWro42X9Wvxt/sI/ITz B199/hQXjq5mPMIOOgeuYTDamTvr4VEfXjsQimpDx21K8saX0X+wi0vvxgt3npAaUxF3 QG2s2K57AHNQgsKqf7l9Q3LMX9t6N9VLTFAPz59OfUO2sVWtNYWXd6XKXb1ignWFINOe 4c0Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=sqdUZVykVdXX0erQ0S6G9GIIvNwYHjdb/qiCheTK1kc=; b=kyuFr1iV/pp9UzN4GkSuCIYgiMskfHhnhwJVMeObrnWgYCtN+SZ4FZdUEVu9p62TyZ 6j2Mq94Da0yPY/6yeqVJqSZJhPd8akElHZH0yDzbxvqFVpUYhFswTI9iCz8CwymrehIs f6f+SH0JnYHfkvy2lSNjZs31IE+AMp4OTGiCYM82Jc4uQBPpnhE3GdVztSmqW/vNT+/1 HGfy7OYyyBYaVv2WdxjvJEbd54mgMY0mLhj1ViqfQ3AMDrY/XSmjfEWXVnF/Ddu5o/mU jgU/dahGlSYMHR0kMrCvEj/KjMEF5Gmcj2LgzERnM1/5cphHHgK9fX6tT/FfFXETYXC9 Z1Dg==
X-Gm-Message-State: AD7BkJJSMM16MRbb54ATRflwbOmm54RkynHzFMcmN+ZTT8Ziq0gitCehU7c0SuSl075jnA==
X-Received: by 10.50.90.193 with SMTP id by1mr10861222igb.53.1460229465184; Sat, 09 Apr 2016 12:17:45 -0700 (PDT)
Received: from Melindas-MacBook-Pro.local (63-140-90-11-radius.dynamic.acsalaska.net. [63.140.90.11]) by smtp.googlemail.com with ESMTPSA id cl9sm6254122igc.10.2016.04.09.12.17.42 (version=TLSv1/SSLv3 cipher=OTHER); Sat, 09 Apr 2016 12:17:43 -0700 (PDT)
Subject: Re: Concerns about Singapore
To: "Fred Baker (fred)" <fred@cisco.com>, joel jaeggli <joelja@bogus.com>
References: <0D914666-C3D4-4CCE-AD5E-4E5B34EA1A73@piuha.net> <20160407182936.GA21340@pfrc.org> <CAB75xn780nNDjGa_Cc222J20-+1CCHt09Xp8KHzaK=n0xx51pg@mail.gmail.com> <5706B100.9040509@mnt.se> <CAB75xn6fmj84ROUtG5eUB3GerHx83hrEr3w5vSADY_g=BRg5FA@mail.gmail.com> <9B723FB0-6B93-4C85-ADD9-D423F873CF08@virtualized.org> <20160409155300.6283348.41255.10529@blackberry.com> <ADC8666A-436C-4AD4-BD48-9277601069F8@gmail.com> <57093CD3.3050502@gmail.com> <f5b1ceec-4cd5-55b5-5089-4a499ed0586c@bogus.com> <F2D3ACF5-C7BD-4D0C-8518-665D2EDAA6CA@cisco.com>
From: Melinda Shore <melinda.shore@gmail.com>
Message-ID: <570955E3.2010205@gmail.com>
Date: Sat, 9 Apr 2016 11:20:03 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:38.0) Gecko/20100101 Thunderbird/38.6.0
MIME-Version: 1.0
In-Reply-To: <F2D3ACF5-C7BD-4D0C-8518-665D2EDAA6CA@cisco.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/aGDUBPWd1M-mENYftXp8tAy338k>
Cc: "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: Sat, 09 Apr 2016 19:17:47 -0000

On 4/9/16 11:01 AM, Fred Baker (fred) wrote:
> One could mention sodomy laws in Texas; we have met in Houstaon and
> Dalls, I believe, there times.

That goes, I think, to the question of unenforceable laws
(Lawrence v. Texas).  I'm interested in the question of where
the line is between issues that the IETF needs to deal with
and matters of personal conscience, and I tend to think it
comes down to questions of whether or not meeting participants
will be treated equally when it comes to public accommodation,
etc.

As we're seeing, businesses are responding to the recent spate of
anti-gay legislation and transphobic potty laws by announcing that
they're not  opening planned facilities in those states, not allowing
their employees to take business travel there, and so on.  So, there's
an actual question about whether or not the IETF would be able to
meet in a place that's recently passed anti-gay legislation, given
some corporate travel restrictions.  As far as I know there are
no corporate bans on travel to Singapore, but civil liberties
organizations like Civil Rights Watch have identified Singapore as
a place where LGBT people still face active legal discrimination
and it seems clear that there's a legitimate question about what
sort of treatment some meeting participants can expect to receive.

Melinda


From nobody Sat Apr  9 13:56:00 2016
Return-Path: <brian.e.carpenter@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 9006F12D122 for <ietf@ietfa.amsl.com>; Sat,  9 Apr 2016 13:55:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.8
X-Spam-Level: 
X-Spam-Status: No, score=-0.8 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 wCvUhAYR95yy for <ietf@ietfa.amsl.com>; Sat,  9 Apr 2016 13:55:57 -0700 (PDT)
Received: from mail-pf0-x233.google.com (mail-pf0-x233.google.com [IPv6:2607:f8b0:400e:c00::233]) (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 DB92A12D0C6 for <ietf@ietf.org>; Sat,  9 Apr 2016 13:55:56 -0700 (PDT)
Received: by mail-pf0-x233.google.com with SMTP id n1so97163560pfn.2 for <ietf@ietf.org>; Sat, 09 Apr 2016 13:55:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=subject:to:references:cc:from:organization:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=wQiviMaEUVW6wdHgcjnTFA0TfNLP/c1Y8C0hwBoDfas=; b=Z2ctxS7S0tQWpXdWWpGf4Xo25xMSVr0KZRu1MjpvCj6MmhDXM5wRBrW3It/8R4Derc 9UESbxi5CBGs1LiooOEuRgVC3KeCAPITbUBGM6CWFPdvKtP5SSD+F/Kwv+pJjaxbV49B T7bVwbUQNvaTmymipx1nGp9hRalxEBXBmyH4BMwa/6FVxPRnXAr/4zoleLP96mG0P+mO 2JKZuPJcnLTqxSdULLMzuth44BfT0t5GJJJVsScHZYMQ8jOt/e9GTzUsv17Kjvb1g3w0 kPmmWHxQT9nxerSrFwhSCJlAWuGkUcRlqcCVYNCGF722UBk0jRNKTEFNFRJHH8wa//g2 x10A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:cc:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=wQiviMaEUVW6wdHgcjnTFA0TfNLP/c1Y8C0hwBoDfas=; b=aqmpwqfxr6gcg+HSnxZmJuvaZUOh3ShsGge6Uo7e1BEqpDHdh4HRLAPFVhRnOSeS76 3EXEtF24Wf4y0HjxmTjsvZxqwKXXP6Z/Bt8yVV7Xc8aUcc1FFNzLPzRFopc3A7xa/aVg VWUg3q2DPyHpcJRgfnAfwVr9pdKNn/pnJ0+2Cmj5C4iaNEKfUunPm4NDdmhfbbgANjKj Hykd5anS+kORDGjdLaaVO+6bIfAndveTFw6wQSfGTSdDvLl/3UBU1sfCsRGdIFokecV9 0VA/iAlTgUjQpVxVhd/HoV1isEUYK0SdjmFdPKaqsA73H4t8e4lK6Hqf8CjbXmrYTKbE gzMw==
X-Gm-Message-State: AD7BkJKE5S+JyQsUggUj2j4GzUrh4B768yYpbmZwf8JW7N2gfKgJ+S5OzuoNZ3UWwfcApw==
X-Received: by 10.98.74.17 with SMTP id x17mr22103130pfa.14.1460235356486; Sat, 09 Apr 2016 13:55:56 -0700 (PDT)
Received: from ?IPv6:2406:e007:74e8:1:28cc:dc4c:9703:6781? ([2406:e007:74e8:1:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id 87sm26724936pfq.93.2016.04.09.13.55.53 (version=TLSv1/SSLv3 cipher=OTHER); Sat, 09 Apr 2016 13:55:55 -0700 (PDT)
Subject: Re: Concerns about Singapore
To: Melinda Shore <melinda.shore@gmail.com>, "Fred Baker (fred)" <fred@cisco.com>, joel jaeggli <joelja@bogus.com>
References: <0D914666-C3D4-4CCE-AD5E-4E5B34EA1A73@piuha.net> <20160407182936.GA21340@pfrc.org> <CAB75xn780nNDjGa_Cc222J20-+1CCHt09Xp8KHzaK=n0xx51pg@mail.gmail.com> <5706B100.9040509@mnt.se> <CAB75xn6fmj84ROUtG5eUB3GerHx83hrEr3w5vSADY_g=BRg5FA@mail.gmail.com> <9B723FB0-6B93-4C85-ADD9-D423F873CF08@virtualized.org> <20160409155300.6283348.41255.10529@blackberry.com> <ADC8666A-436C-4AD4-BD48-9277601069F8@gmail.com> <57093CD3.3050502@gmail.com> <f5b1ceec-4cd5-55b5-5089-4a499ed0586c@bogus.com> <F2D3ACF5-C7BD-4D0C-8518-665D2EDAA6CA@cisco.com> <570955E3.2010205@gmail.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <57096C65.7020409@gmail.com>
Date: Sun, 10 Apr 2016 08:56:05 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2
MIME-Version: 1.0
In-Reply-To: <570955E3.2010205@gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/7zrfBj2k7TdacZrAg0XufbwU50w>
Cc: "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: Sat, 09 Apr 2016 20:55:58 -0000

On 10/04/2016 07:20, Melinda Shore wrote:
> On 4/9/16 11:01 AM, Fred Baker (fred) wrote:
>> One could mention sodomy laws in Texas; we have met in Houstaon and
>> Dalls, I believe, there times.
> 
> That goes, I think, to the question of unenforceable laws
> (Lawrence v. Texas).  I'm interested in the question of where
> the line is between issues that the IETF needs to deal with
> and matters of personal conscience, and I tend to think it
> comes down to questions of whether or not meeting participants
> will be treated equally when it comes to public accommodation,
> etc.

I think that's the point, and unfortunately, like so many things, it
ends up as a judgment call.

Are transgender people treated equally when getting haircuts? Not always,
it turns out:
http://m.nzherald.co.nz/nz/news/article.cfm?c_id=1&objectid=11618046

Does this disqualify Auckland? Probably not, and it's less serious than
being denied a hotel room or worse. But my point is: this issue just goes
in the balance along with everything else, and the problem here seems to be
that the IAOC overlooked it. I sympathise, because I'd probably have
overlooked it too.

otoh, the IETF boycotting SG would not have the same impact as Springsteen
boycotting NC.

   Brian

> 
> As we're seeing, businesses are responding to the recent spate of
> anti-gay legislation and transphobic potty laws by announcing that
> they're not  opening planned facilities in those states, not allowing
> their employees to take business travel there, and so on.  So, there's
> an actual question about whether or not the IETF would be able to
> meet in a place that's recently passed anti-gay legislation, given
> some corporate travel restrictions.  As far as I know there are
> no corporate bans on travel to Singapore, but civil liberties
> organizations like Civil Rights Watch have identified Singapore as
> a place where LGBT people still face active legal discrimination
> and it seems clear that there's a legitimate question about what
> sort of treatment some meeting participants can expect to receive.
> 
> Melinda
> 
> 


From nobody Sat Apr  9 14:05:10 2016
Return-Path: <olejacobsen@me.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 BD97912D188 for <ietf@ietfa.amsl.com>; Sat,  9 Apr 2016 14:05:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.617
X-Spam-Level: 
X-Spam-Status: No, score=-3.617 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.996, SPF_PASS=-0.001] 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 0InbQbdC3E1J for <ietf@ietfa.amsl.com>; Sat,  9 Apr 2016 14:05:07 -0700 (PDT)
Received: from mr11p00im-asmtp002.me.com (mr11p00im-asmtp002.me.com [17.110.69.253]) (using TLSv1.2 with cipher DHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AB31012D185 for <ietf@ietf.org>; Sat,  9 Apr 2016 14:05:07 -0700 (PDT)
Received: from [10.1.10.8] (173-11-110-134-SFBA.hfc.comcastbusiness.net [173.11.110.134]) by mr11p00im-asmtp002.me.com (Oracle Communications Messaging Server 7.0.5.36.0 64bit (built Sep 8 2015)) with ESMTPSA id <0O5D00A44X8I4Y30@mr11p00im-asmtp002.me.com> for ietf@ietf.org; Sat, 09 Apr 2016 21:05:07 +0000 (GMT)
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, definitions=2016-04-09_12:,, signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 clxscore=1011 suspectscore=0 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1510270003 definitions=main-1604090321
Date: Sat, 09 Apr 2016 14:05:06 -0700 (PDT)
From: Ole Jacobsen <olejacobsen@me.com>
To: Melinda Shore <melinda.shore@gmail.com>
Subject: Re: Concerns about Singapore
In-reply-to: <570955E3.2010205@gmail.com>
Message-id: <alpine.OSX.2.01.1604091401420.42313@rabdullah.local>
References: <0D914666-C3D4-4CCE-AD5E-4E5B34EA1A73@piuha.net> <20160407182936.GA21340@pfrc.org> <CAB75xn780nNDjGa_Cc222J20-+1CCHt09Xp8KHzaK=n0xx51pg@mail.gmail.com> <5706B100.9040509@mnt.se> <CAB75xn6fmj84ROUtG5eUB3GerHx83hrEr3w5vSADY_g=BRg5FA@mail.gmail.com> <9B723FB0-6B93-4C85-ADD9-D423F873CF08@virtualized.org> <20160409155300.6283348.41255.10529@blackberry.com> <ADC8666A-436C-4AD4-BD48-9277601069F8@gmail.com> <57093CD3.3050502@gmail.com> <f5b1ceec-4cd5-55b5-5089-4a499ed0586c@bogus.com> <F2D3ACF5-C7BD-4D0C-8518-665D2EDAA6CA@cisco.com> <570955E3.2010205@gmail.com>
User-Agent: Alpine 2.01 (OSX 1266 2009-07-14)
MIME-version: 1.0
Content-type: TEXT/PLAIN; charset=US-ASCII
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/C-CR0HpfW6i_hTVvElKHFSMYMJA>
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: Ole Jacobsen <olejacobsen@me.com>
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, 09 Apr 2016 21:05:09 -0000

On Sat, 9 Apr 2016, Melinda Shore wrote:


> That goes, I think, to the question of unenforceable laws (Lawrence 
> v. Texas).  I'm interested in the question of where the line is 
> between issues that the IETF needs to deal with and matters of 
> personal conscience, and I tend to think it comes down to questions 
> of whether or not meeting participants will be treated equally when 
> it comes to public accommodation, etc.
> 
> As we're seeing, businesses are responding to the recent spate of 
> anti-gay legislation and transphobic potty laws by announcing that 
> they're not opening planned facilities in those states, not allowing 
> their employees to take business travel there, and so on.  So, 
> there's an actual question about whether or not the IETF would be 
> able to meet in a place that's recently passed anti-gay legislation, 
> given some corporate travel restrictions.  As far as I know there 
> are no corporate bans on travel to Singapore, but civil liberties 
> organizations like Civil Rights Watch have identified Singapore as a 
> place where LGBT people still face active legal discrimination and 
> it seems clear that there's a legitimate question about what sort of 
> treatment some meeting participants can expect to receive.
> 
> Melinda

There are several sources online for this information, including the 
US State Department, but we are also actively seeking clarification 
from contacts in Singapore about these issues. So far, I am fairly
certain that our attendees won't notice any issues at all, but stay
tuned as we gather the facts.

Ole


From nobody Sat Apr  9 14:13:48 2016
Return-Path: <mstjohns@comcast.net>
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 A1BE312D150 for <ietf@ietfa.amsl.com>; Sat,  9 Apr 2016 14:13:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.696
X-Spam-Level: 
X-Spam-Status: No, score=-3.696 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, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.996, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=comcast.net
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 s7wrM86tJ0eW for <ietf@ietfa.amsl.com>; Sat,  9 Apr 2016 14:13:43 -0700 (PDT)
Received: from resqmta-ch2-10v.sys.comcast.net (resqmta-ch2-10v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:42]) (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 295FA12D191 for <ietf@ietf.org>; Sat,  9 Apr 2016 14:13:43 -0700 (PDT)
Received: from resomta-ch2-03v.sys.comcast.net ([69.252.207.99]) by comcast with SMTP id p0BQa5rlspUrhp0CMaT57X; Sat, 09 Apr 2016 21:13:42 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1460236422; bh=itluTk9iWM3snSICCWqqLHdWNmpRMvb6gM0RGVQrlww=; h=Received:Received:Subject:To:From:Message-ID:Date:MIME-Version: Content-Type; b=poyPiPMhrTp0deUDO7u0TdQq6ttu4Dg5Xj7LXSCh9QMh2of4yV1gBVfu5INzKpSDl FGC91j0stiZrV8beCQCd70KdaMPPFBr2ThqOCe2IlZzDkmcDM9BP3nBTrvNdQ9mwxn u3NNbylirrw316vbpaiQqocCs5+lfF8r0+TwPSplRZmEgyZA1jRFyNX4bM1pT5XnQU 6HyfA3lTN6TSPKSlhf2yYeZAb/u4h7STsBPFId8xtpgyIJr1AIYVdqKVDLFV5G4JZk CNfXEu+Dl75WMUTygrdGIBvj8JbaiMIQBv1dVpcMEFSRXcQ47K/RUv2heX7rWsZwW2 Yzm+clqKtpyjA==
Received: from [192.168.1.113] ([69.255.115.150]) by resomta-ch2-03v.sys.comcast.net with comcast id gMDi1s0043Em2Kp01MDiY2; Sat, 09 Apr 2016 21:13:42 +0000
Subject: Re: Concerns about Singapore
To: ietf@ietf.org
References: <0D914666-C3D4-4CCE-AD5E-4E5B34EA1A73@piuha.net> <20160407182936.GA21340@pfrc.org> <CAB75xn780nNDjGa_Cc222J20-+1CCHt09Xp8KHzaK=n0xx51pg@mail.gmail.com> <5706B100.9040509@mnt.se> <CAB75xn6fmj84ROUtG5eUB3GerHx83hrEr3w5vSADY_g=BRg5FA@mail.gmail.com> <5706BA40.3060005@mnt.se> <alpine.DEB.2.02.1604072157240.31096@uplift.swm.pp.se> <A9B63A6D-3102-482F-8FFC-2E57A5FD8336@nic.cz> <16925.1460122349@obiwan.sandelman.ca> <m27fg77zst.wl%randy@psg.com>
From: Michael StJohns <mstjohns@comcast.net>
Message-ID: <57097077.7040703@comcast.net>
Date: Sat, 9 Apr 2016 17:13:27 -0400
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.7.1
MIME-Version: 1.0
In-Reply-To: <m27fg77zst.wl%randy@psg.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/GnS2dUewJ17phRqBTiXJ7dnDpYM>
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, 09 Apr 2016 21:13:44 -0000

On 4/9/2016 8:05 AM, Randy Bush wrote:
>> yes, we tried that.  My impression is that there were two changes we
>> made, one was known in advance (closed network)
> the ietf network in beijing was open as normal, thanks to the work of
> many.  it had registration, as had maastricht.  and we have passwording
> now.
Most of these things are not like the others:

We have ietf/ietf now - mainly for the benefit of the individual users 
(per client encryption keys), not the per user userid/password that we 
had in Beijing that was only available to registered attendees.

Calling the Beijing meeting network open isn't really correct - we had a 
reverse VPN to the Internet as it exists outside of the PRC.

We did registration in Maastricht simply to figure out the details 
before we got to Beijing - I'm fairly confident that Maastricht wouldn't 
have been different from the previous IETF's without the upcoming 
Beijing meeting.
>
>> the other was unknown (badges being checked)
> cf. rfid discussion in hiroshima.  checking badges has a varied history.
> beijing was conservative.
>
> randy
>

Beijing was the first and only time I can think of where the hotel/host 
provided us with guards (excepting watchmen for the terminal room).  It 
was also the first time that said guards actually kept out someone with 
a valid conference badge. Granted, the badge did not have the holders 
name on it, but it's really never been the IETF's policy to be overly 
concerned about who shows up as long as they are minimally dressed, not 
disruptive to the process and have attained reasonable standards of 
hygiene.  And even those standards have been waived at times.

I'll also note that we neither asked for the guards nor were asked for 
consent for the guards to be placed.  [I believe the previous statement 
to be true, but its possible that I was misinformed.]

It's a little late for this, but I'm suddenly wondering what percentage 
of the on-site registrants  in Beijing were local, and how that 
percentage compares with other meetings.

In any event, each location we've been to has had a challenge or two 
that we've either ignored or overcome.  Some candidate places will have 
challenges that we can neither ignore or overcome and should hopefully 
be down-selected in the meeting planning process.

Later, Mike



From nobody Sat Apr  9 14:14:51 2016
Return-Path: <mcr+ietf@sandelman.ca>
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 95BE412D150 for <ietf@ietfa.amsl.com>; Sat,  9 Apr 2016 14:14:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.897
X-Spam-Level: 
X-Spam-Status: No, score=-2.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.996, SPF_PASS=-0.001] 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 eBVlJh6tvZ62 for <ietf@ietfa.amsl.com>; Sat,  9 Apr 2016 14:14:47 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9C18712D198 for <ietf@ietf.org>; Sat,  9 Apr 2016 14:14:47 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id 4127C2009E; Sat,  9 Apr 2016 17:18:30 -0400 (EDT)
Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 4E7A463755; Sat,  9 Apr 2016 17:14:46 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: I-D Action: draft-kucherawy-nomcom-procexp-00.txt
In-Reply-To: <570882CE.9010501@gmail.com>
References: <20160408185636.23101.86017.idtracker@ietfa.amsl.com> <570882CE.9010501@gmail.com>
X-Mailer: MH-E 8.6; nmh 1.6+dev; GNU Emacs 24.4.2
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Sat, 09 Apr 2016 17:14:46 -0400
Message-ID: <13214.1460236486@obiwan.sandelman.ca>
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/on64B57WmzQYk2SU9Q4fAWaiQoE>
Cc: IETF discussion list <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: Sat, 09 Apr 2016 21:14:49 -0000

--=-=-=
Content-Type: text/plain


Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
    > I think this is too general and judgmental. Suggestion:

    > 3.  A new reason to challenge a selection is that a specific member
    > who has not attended three of the last five meetings of the IETF
    > does not have enough recent participation of any kind to be an
    > effective member of the NomCom.  Such a challenge must be
    > accompanied by a specific explanation of why the challenger
    > considers this to be the case.

Is this challenge public?
I think that it is, but I'm not certain if all of it is public.

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-




--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQEVAwUBVwlww4CLcPvd0N1lAQLEjQf/c7fwiW27frgyO/WK+wSJHOz/xFCMVPch
muKkQyLVSJu+/up4jn9GR95QaS7UT24I1gLqqRiiPIRwokU3wmGvcCr8jvOHG7NX
2Drg7hG5x+7YLCXGvhs6B4XGSiISFvPQuPXSXkyLgskwXUGtkOZidPQl+5GzLkdQ
QcR8id8Jr+GMyrcx6GMdX/IeZ9S4xvGPvDeymwuMHF6A08VVtVXK64vYxbxifkMn
QV0ZZbtuipSNmEtCzagwX80MEY8PAdxLE8r69dk34fQ0OLtaPRAL8XNUS8eWnfv/
0C5phoYF84VKI/Oy2E+fKZEFb8dlWjSrIB/jQ/MZg7AmShCMZqcDnQ==
=nku/
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Sat Apr  9 14:17:42 2016
Return-Path: <melinda.shore@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 1690212D1A3 for <ietf@ietfa.amsl.com>; Sat,  9 Apr 2016 14:17:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 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, RCVD_IN_DNSWL_LOW=-0.7, 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 6HATTmC0Fcne for <ietf@ietfa.amsl.com>; Sat,  9 Apr 2016 14:17:41 -0700 (PDT)
Received: from mail-io0-x22e.google.com (mail-io0-x22e.google.com [IPv6:2607:f8b0:4001:c06::22e]) (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 D478012D19E for <ietf@ietf.org>; Sat,  9 Apr 2016 14:17:40 -0700 (PDT)
Received: by mail-io0-x22e.google.com with SMTP id o126so146261854iod.0 for <ietf@ietf.org>; Sat, 09 Apr 2016 14:17:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=N6yQCw860x5REJlsobfNzTpK2Wb3novihh+lRyvLFg0=; b=bJaZSE3zksbnPtyYvACrFFr9tLllOvOelGtuCG7rMSfXhHtVoL/FH+lpsq5QmSCaLo avS82OiUNzX+fvwICK7WRrzbOn9KPntIFmhRmAXFrtcpZ2e6U6DL+GJyWTomdo26bZJT gTOD7a0VX6VSQ7OK+SaviYflpwB4DL9kD0XhVrDY3RYgtoeDVBVe2tqEzrIR5gA3m9FJ PiGJfqqGL59bahb3mc1y104GtjL4hDH5KQGq+egHJNl+j/HpiI1tpIyZtG9OFxPphWvM Q2hZkaFltXYwShzv8Um0ADYElsf4N2D/7ZkhykkAu8ycB5zxLsGJssEMmaauvsxlMmgD sZsA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=N6yQCw860x5REJlsobfNzTpK2Wb3novihh+lRyvLFg0=; b=etjNObcCpdF8b/ZzG1+N55Uj7NinyZKvKYrSu4frAXbhjxZiPQva7NecYZ75EFnJ7r U4tpQMw3fzBG82yfhd15AqbhqPkGEbZXenV0K60uTZdDj/yFxcFyDJGzgUyFfqurHiLr uuIJMB8OI1c1r6oXmeF7XV695Rr1UhpbiiY5Rhkgo3CoBnu3Vxc7bxIyEbeo/uT/7IH8 tZE1JFCYPembT4A5vtAY+im88i8swB31bAfdEcIkm5w1Eb2PUurbQCi81AU0NZv4a/qx minB5y8/SO8u8wQ/CsmfY5Zg934pxZpVrbNXEBLyg2vVUORuJ+n+Xt2LlrV6ApGscxGg 8qfg==
X-Gm-Message-State: AOPr4FUYVVtzlx6aQO5WzFVijiuotbFfczuHmT/d3vIM+2vpXeFO9zV4I7Z00c09RaBFFA==
X-Received: by 10.107.187.132 with SMTP id l126mr8929598iof.10.1460236660211;  Sat, 09 Apr 2016 14:17:40 -0700 (PDT)
Received: from Melindas-MacBook-Pro.local (63-140-90-11-radius.dynamic.acsalaska.net. [63.140.90.11]) by smtp.googlemail.com with ESMTPSA id n19sm6494336igi.19.2016.04.09.14.17.38 (version=TLSv1/SSLv3 cipher=OTHER); Sat, 09 Apr 2016 14:17:39 -0700 (PDT)
Subject: Re: Concerns about Singapore
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
References: <0D914666-C3D4-4CCE-AD5E-4E5B34EA1A73@piuha.net> <20160407182936.GA21340@pfrc.org> <CAB75xn780nNDjGa_Cc222J20-+1CCHt09Xp8KHzaK=n0xx51pg@mail.gmail.com> <5706B100.9040509@mnt.se> <CAB75xn6fmj84ROUtG5eUB3GerHx83hrEr3w5vSADY_g=BRg5FA@mail.gmail.com> <9B723FB0-6B93-4C85-ADD9-D423F873CF08@virtualized.org> <20160409155300.6283348.41255.10529@blackberry.com> <ADC8666A-436C-4AD4-BD48-9277601069F8@gmail.com> <57093CD3.3050502@gmail.com> <f5b1ceec-4cd5-55b5-5089-4a499ed0586c@bogus.com> <F2D3ACF5-C7BD-4D0C-8518-665D2EDAA6CA@cisco.com> <570955E3.2010205@gmail.com> <57096C65.7020409@gmail.com>
From: Melinda Shore <melinda.shore@gmail.com>
Message-ID: <57097200.5050503@gmail.com>
Date: Sat, 9 Apr 2016 13:20:00 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:38.0) Gecko/20100101 Thunderbird/38.6.0
MIME-Version: 1.0
In-Reply-To: <57096C65.7020409@gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/VOivR7G-zocvcOTcBqDQgpz21DA>
Cc: "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: Sat, 09 Apr 2016 21:17:42 -0000

On 4/9/16 12:56 PM, Brian E Carpenter wrote:
> I think that's the point, and unfortunately, like so many things, it
> ends up as a judgment call.

Not really - Singapore has laws on the books that criminalize
gay relationships.  That's a fact, not a judgment call.  It's
also a fact that a law criminalizing consensual physical relationships
between adult men was upheld by the Singapore Supreme Court less
than two years ago and apparently has been inconsistently and
selectively enforced (that's not a good thing).

Melinda


From nobody Sat Apr  9 15:35:48 2016
Return-Path: <john-ietf@jck.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 4757B12D195 for <ietf@ietfa.amsl.com>; Sat,  9 Apr 2016 15:35:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.896
X-Spam-Level: 
X-Spam-Status: No, score=-2.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.996] 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 GEhqUCKzHp4S for <ietf@ietfa.amsl.com>; Sat,  9 Apr 2016 15:35:46 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2613A12D18D for <ietf@ietf.org>; Sat,  9 Apr 2016 15:35:46 -0700 (PDT)
Received: from [198.252.137.10] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1ap1Tj-000Cz7-JZ; Sat, 09 Apr 2016 18:35:43 -0400
Date: Sat, 09 Apr 2016 18:35:38 -0400
From: John C Klensin <john-ietf@jck.com>
To: Melinda Shore <melinda.shore@gmail.com>, Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: Concerns about Singapore
Message-ID: <2C0674FBC5C419DAC427E4BC@JcK-HP8200.jck.com>
In-Reply-To: <57097200.5050503@gmail.com>
References: <0D914666-C3D4-4CCE-AD5E-4E5B34EA1A73@piuha.net> <20160407182936.GA21340@pfrc.org> <CAB75xn780nNDjGa_Cc222J20-+1CCHt09Xp8KHzaK=n0xx51pg@mail.gmail.com> <5706B100.9040509@mnt.se> <CAB75xn6fmj84ROUtG5eUB3GerHx83hrEr3w5vSADY_g=BRg5FA@mail.gmail.com> <9B723FB0-6B93-4C85-ADD9-D423F873CF08@virtualized.org> <20160409155300.6283348.41255.10529@blackberry.com> <ADC8666A-436C-4AD4-BD48-9277601069F8@gmail.com> <57093CD3.3050502@gmail.com> <f5b1ceec-4cd5-55b5-5089-4a499ed0586c@bogus.com> <F2D3ACF5-C7BD-4D0C-8518-665D2EDAA6CA@cisco.com> <570955E3.2010205@gmail.com> <57096C65.7020409@gmail.com> <57097200.5050503@gmail.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/LzHGKocoYNc2Kl4eHBVithXE1_g>
Cc: 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: Sat, 09 Apr 2016 22:35:47 -0000

--On Saturday, April 09, 2016 13:20 -0800 Melinda Shore
<melinda.shore@gmail.com> wrote:

> On 4/9/16 12:56 PM, Brian E Carpenter wrote:
>> I think that's the point, and unfortunately, like so many
>> things, it ends up as a judgment call.
 
> Not really - Singapore has laws on the books that criminalize
> gay relationships.  That's a fact, not a judgment call.  It's
> also a fact that a law criminalizing consensual physical
> relationships between adult men was upheld by the Singapore
> Supreme Court less than two years ago and apparently has been
> inconsistently and selectively enforced (that's not a good
> thing).

This has been said several times and I think needs to be
stressed.  There is a huge practical difference between 

	* Having an obnoxious (to use a deliberately-mild term)
	law on the books that has not been enforced for many
	years, for which there is no reasonable expectation that
	it would be enforced, _and_ for which there are
	reasonable grounds for assuming that any attempt to
	enforce it would result in the rapid elimination of the
	law itself -- rapid enough to act as a further deterrent
	to attempts to enforce it, rather than causing IETF
	community members to feel "not very much" pain and
	suffering.
	
	* Having a law that has been enforced in recent memory,
	especially if it has also been validated (or "upheld")
	in recent memory by courts or other relevant authorities
	and/or created in recent years (as in the North Carolina
	situation that has been cited as an example). 

Referring to what Pete said at the plenary, the second set of
cases should (actually MUST) never be treated as a matter of a
judgment call or balancing factors.   By analogy with the visa
issue, a situation in which regular participants from some
countries will find obtaining visas to be a major pain in the
anatomy involves a judgment call; one in which participants from
some countries cannot, under normal circumstances, obtain visas
or in-meeting-country protections as citizens of their origin
countries because the potential countries deliberately does not
maintain diplomatic recognition or relations with those origin
countries is a showstopper.

I agree with Melinda that inconsistent and selective enforcement
is bad news (and because it includes non-zero frequency of
enforcement, moves a potential venue into the second category).
I also think it is worth stressing that, especially in an area
where rights to free speech and/or assembly and/or to hold
demonstrations about a political position are even nominally
valued, the ability to hold a parade or demonstration in favor
of particular rights or legally-prohibited behavior without
interference is of approximately zero value in predicting
whether actual exercise of those rights or behavior would result
in enforcement actions.

I hope that, as the IAOC continues "actively seeking
clarification", the distinction between the ability to express
support without getting arrested and the ability to practice the
nominally-criminal behavior without getting arrested (even
occasionally) is well understood.

It may be just me, but the distinctions really seem a lot more
clear than the length of this discussion thread would seem to
imply.

     john


From nobody Sat Apr  9 15:36:57 2016
Return-Path: <paf@frobbit.se>
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 2722612D1E1 for <ietf@ietfa.amsl.com>; Sat,  9 Apr 2016 15:36:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.597
X-Spam-Level: 
X-Spam-Status: No, score=-3.597 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.996, SPF_PASS=-0.001] 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 XqTDUznRd6_q for <ietf@ietfa.amsl.com>; Sat,  9 Apr 2016 15:36:55 -0700 (PDT)
Received: from mail.frobbit.se (mail.frobbit.se [IPv6:2a02:80:3ffe::176]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D195812D195 for <ietf@ietf.org>; Sat,  9 Apr 2016 15:36:54 -0700 (PDT)
Received: from [192.165.72.17] (unknown [192.165.72.17]) by mail.frobbit.se (Postfix) with ESMTPSA id 1A148227E4; Sun, 10 Apr 2016 00:36:53 +0200 (CEST)
From: "Patrik =?utf-8?b?RsOkbHRzdHLDtm0=?=" <paf@frobbit.se>
To: "Ole Jacobsen" <olejacobsen@me.com>
Subject: Re: Concerns about Singapore
Date: Sun, 10 Apr 2016 00:36:53 +0200
Message-ID: <429DD401-DB4F-4B09-9EF8-035EFB089488@frobbit.se>
In-Reply-To: <alpine.OSX.2.01.1604091401420.42313@rabdullah.local>
References: <0D914666-C3D4-4CCE-AD5E-4E5B34EA1A73@piuha.net> <20160407182936.GA21340@pfrc.org> <CAB75xn780nNDjGa_Cc222J20-+1CCHt09Xp8KHzaK=n0xx51pg@mail.gmail.com> <5706B100.9040509@mnt.se> <CAB75xn6fmj84ROUtG5eUB3GerHx83hrEr3w5vSADY_g=BRg5FA@mail.gmail.com> <9B723FB0-6B93-4C85-ADD9-D423F873CF08@virtualized.org> <20160409155300.6283348.41255.10529@blackberry.com> <ADC8666A-436C-4AD4-BD48-9277601069F8@gmail.com> <57093CD3.3050502@gmail.com> <f5b1ceec-4cd5-55b5-5089-4a499ed0586c@bogus.com> <F2D3ACF5-C7BD-4D0C-8518-665D2EDAA6CA@cisco.com> <570955E3.2010205@gmail.com> <alpine.OSX.2.01.1604091401420.42313@rabdullah.local>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=_MailMate_B5198C83-93AC-4AD1-A297-6B4257F6774D_="; micalg=pgp-sha1; protocol="application/pgp-signature"
X-Mailer: MailMate (1.9.4r5234)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/NTwBkMA60Ig-j1Ug168WVlhNCEk>
Cc: "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: Sat, 09 Apr 2016 22:36:56 -0000

This is an OpenPGP/MIME signed message (RFC 3156 and 4880).

--=_MailMate_B5198C83-93AC-4AD1-A297-6B4257F6774D_=
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

On 9 Apr 2016, at 23:05, Ole Jacobsen wrote:

> There are several sources online for this information, including the
> US State Department, but we are also actively seeking clarification
> from contacts in Singapore about these issues. So far, I am fairly
> certain that our attendees won't notice any issues at all, but stay
> tuned as we gather the facts.

FWIW, ICANN has met in Singapore a few times recently and I have not hear=
d about any issues what so ever.

   Patrik

--=_MailMate_B5198C83-93AC-4AD1-A297-6B4257F6774D_=
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename=signature.asc
Content-Type: application/pgp-signature; name=signature.asc

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iEYEARECAAYFAlcJhAUACgkQrMabGguI1833LgCfTRSTt7Cba9AfbIv1s0kzLmpE
tM4AnRzN2lLTkaorWc27qml/8IMT2zRi
=24fW
-----END PGP SIGNATURE-----

--=_MailMate_B5198C83-93AC-4AD1-A297-6B4257F6774D_=--


From nobody Sat Apr  9 15:57:41 2016
Return-Path: <randy@psg.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 96DAB12D14B for <ietf@ietfa.amsl.com>; Sat,  9 Apr 2016 15:57:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.896
X-Spam-Level: 
X-Spam-Status: No, score=-7.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.996] 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 0894EEhEwnbm for <ietf@ietfa.amsl.com>; Sat,  9 Apr 2016 15:57:39 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A6E7B12D11D for <ietf@ietf.org>; Sat,  9 Apr 2016 15:57:39 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com) by ran.psg.com with esmtp (Exim 4.82) (envelope-from <randy@psg.com>) id 1ap1ov-0000ks-Lb; Sat, 09 Apr 2016 22:57:38 +0000
Date: Sat, 09 Apr 2016 19:57:35 -0300
Message-ID: <m2fuuu75ls.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Michael StJohns <mstjohns@comcast.net>
Subject: Re: Concerns about Singapore
In-Reply-To: <57097077.7040703@comcast.net>
References: <0D914666-C3D4-4CCE-AD5E-4E5B34EA1A73@piuha.net> <20160407182936.GA21340@pfrc.org> <CAB75xn780nNDjGa_Cc222J20-+1CCHt09Xp8KHzaK=n0xx51pg@mail.gmail.com> <5706B100.9040509@mnt.se> <CAB75xn6fmj84ROUtG5eUB3GerHx83hrEr3w5vSADY_g=BRg5FA@mail.gmail.com> <5706BA40.3060005@mnt.se> <alpine.DEB.2.02.1604072157240.31096@uplift.swm.pp.se> <A9B63A6D-3102-482F-8FFC-2E57A5FD8336@nic.cz> <16925.1460122349@obiwan.sandelman.ca> <m27fg77zst.wl%randy@psg.com> <57097077.7040703@comcast.net>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/vuyIjtudiia9M47_fQaRnVdJeUY>
Cc: 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: Sat, 09 Apr 2016 22:57:40 -0000

> Calling the Beijing meeting network open isn't really correct - we had
> a reverse VPN to the Internet as it exists outside of the PRC.

false.  and i was the noc guy working it.

> We did registration in Maastricht simply to figure out the details
> before we got to Beijing - I'm fairly confident that Maastricht
> wouldn't have been different from the previous IETF's without the
> upcoming Beijing meeting.

correct, but misleading.  maastrict was the same as beijing, though for
different reasons.

randy


From nobody Sat Apr  9 16:03:15 2016
Return-Path: <john-ietf@jck.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 16F8612D1E5 for <ietf@ietfa.amsl.com>; Sat,  9 Apr 2016 16:03:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.896
X-Spam-Level: 
X-Spam-Status: No, score=-2.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.996] 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 syMZkgKZyJdg for <ietf@ietfa.amsl.com>; Sat,  9 Apr 2016 16:03:12 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A977D12D1E1 for <ietf@ietf.org>; Sat,  9 Apr 2016 16:03:12 -0700 (PDT)
Received: from [198.252.137.10] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1ap1uH-000D0v-5R; Sat, 09 Apr 2016 19:03:09 -0400
Date: Sat, 09 Apr 2016 19:03:04 -0400
From: John C Klensin <john-ietf@jck.com>
To: =?UTF-8?Q?Patrik_F=C3=A4ltstr=C3=B6m?= <paf@frobbit.se>, Ole Jacobsen <olejacobsen@me.com>
Subject: Re: Concerns about Singapore
Message-ID: <462C1DAFA4ADFB73351A1CB0@JcK-HP8200.jck.com>
In-Reply-To: <429DD401-DB4F-4B09-9EF8-035EFB089488@frobbit.se>
References: <0D914666-C3D4-4CCE-AD5E-4E5B34EA1A73@piuha.net> <20160407182936.GA21340@pfrc.org> <CAB75xn780nNDjGa_Cc222J20-+1CCHt09Xp8KHzaK=n0xx51pg@mail.gmail.com> <5706B100.9040509@mnt.se> <CAB75xn6fmj84ROUtG5eUB3GerHx83hrEr3w5vSADY_g=BRg5FA@mail.gmail.com> <9B723FB0-6B93-4C85-ADD9-D423F873CF08@virtualized.org> <20160409155300.6283348.41255.10529@blackberry.com> <ADC8666A-436C-4AD4-BD48-9277601069F8@gmail.com> <57093CD3.3050502@gmail.com> <f5b1ceec-4cd5-55b5-5089-4a499ed0586c@bogus.com> <F2D3ACF5-C7BD-4D0C-8518-665D2EDAA6CA@cisco.com> <570955E3.2010205@gmail.com> <alpine.OSX.2.01.1604091401420.42313@rabdullah.local> <429DD401-DB4F-4B09-9EF8-035EFB089488@frobbit.se>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/5WYF8lQoXFHP2sKaVIMlxUsK1zQ>
Cc: 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: Sat, 09 Apr 2016 23:03:14 -0000

--On Sunday, April 10, 2016 00:36 +0200 Patrik =
F=C3=A4ltstr=C3=B6m
<paf@frobbit.se> wrote:

> On 9 Apr 2016, at 23:05, Ole Jacobsen wrote:
>=20
>> There are several sources online for this information,
>> including the US State Department, but we are also actively
>> seeking clarification from contacts in Singapore about these
>> issues. So far, I am fairly certain that our attendees won't
>> notice any issues at all, but stay tuned as we gather the
>> facts.
>=20
> FWIW, ICANN has met in Singapore a few times recently and I
> have not heard about any issues what so ever.

Patrik,

This has been mentioned several times.  Let me make an
observation about ICANN meetings.  Especially in recent years,
they are very political.  Especially in smaller or less
developed countries, they usually occur at the invitation of the
government or with the fairly explicit permission and
involvement of the government.  Part of selective enforcement
(see Melinda's recent note) is that attendees at such meetings
are rarely messed with unless their behavior is impossible to
ignore and sometimes not then.  ICANN is further down that scale
than actual UN or diplomatic meetings: I've been in countries
where, had I come (to tried to come) as, e.g., a tourist or
random meeting attendee, I would have been a prohibited person
but, because I was traveling on UN papers, I had great
confidence that no one was going to interfere with me.

Singapore, for better or worse, has a well-established
reputation as a rather pragmatic place.  Because of the above,
an attendee at an ICANN meeting is less likely to be interfered
with than, e.g., one at an APNIC or Apricot one.   I suspect the
latter are less likely to be interfered with than an IETF
attendee just because of different relationships between the
organizations and their members and the long-term interests of
the country.  An IETF attendee is less likely to be interfered
with than a permanent resident of the country.  But the laws are
there, they are apparently intermittently enforced, and no IETF
participant should need to worry about whether they or their
families are going to be in the wrong place at a time when a
hotel staff member or law enforcement official is having a bad
day (or an attack of religious or other zeal) and looking for
someone to take it out on.

I could also note that ICANN, given the view of its role by some
of its leadership in recent years, had found it desirable or
necessary to cozy up to some of the world's more problematic
autocratic regimes.  Whether side deals are made with those
regimes or not, that behavior certainly should not set a
standard for the IETF to follow.

     john


From nobody Sat Apr  9 16:32:41 2016
Return-Path: <warren@kumari.net>
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 2A75212D14C for <ietf@ietfa.amsl.com>; Sat,  9 Apr 2016 16:32:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=kumari-net.20150623.gappssmtp.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 xiqWRz_vWMeq for <ietf@ietfa.amsl.com>; Sat,  9 Apr 2016 16:32:36 -0700 (PDT)
Received: from mail-qk0-x229.google.com (mail-qk0-x229.google.com [IPv6:2607:f8b0:400d:c09::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 6042012D0E0 for <ietf@ietf.org>; Sat,  9 Apr 2016 16:32:36 -0700 (PDT)
Received: by mail-qk0-x229.google.com with SMTP id i4so57751619qkc.3 for <ietf@ietf.org>; Sat, 09 Apr 2016 16:32:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kumari-net.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=HSINzQCsBMVkuB75UFxNM2tqp+J4WRVi7SFQuc6f+z8=; b=LWFP9p+5xl4BmPEF0EdRiROZ/B4OuyZRWTp3g9UkFUQX6iYGzjqkud9z20Ymx/MOzn Wk6ScQ/V2mOORtzM+bgZZqRvOLu50aRdaObujWwDgf6nXiZqDK+eAHttFFe1dMCYBhDt fobPlt+wvF2zxLwpESxUv6AGMDcBrJkVKTHF5XhTibqRbMZociShDVE6tdv/sn9Q1n73 zPf+utmxdaqrL1CB6XoOKVLjcxuLgvDbXr0QyMzJdKf4NKDWMZloNf6hn5quzNxdKQDy 1vRqXFLuGvLFfFVBb6B0YBvOWhNps2EDbFoBKHy/NERAchJSzIGhNM5FCBX8tcAVmrea RXSg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=HSINzQCsBMVkuB75UFxNM2tqp+J4WRVi7SFQuc6f+z8=; b=Fe9jJNNEN9D7+AIokUl1QX0WY2+SDS5P1LdzY6IlJ3R7nQGNT/K3wafH91VLK5DTTT iSoBNfZGvFOLnlryIS0BeoO+5xvM2y8h+4MGdV94gJ+cDZuUCJPef3s19f/LAFabNs0g uOvYboFyUqWbwJTuos+QZ6MdWod1S4axDHCixlMN+fSEas6KMjOI/fNZLBWd1ljw6vZY lSl+wJTw6t7U2l3Z9RexGuF1dQrrgmObNuruUo+1H3dYWLL6llr7BRTq8RlQxYtSyjT5 YXZBxmMV6izHb+R4iJDvnh/dS5vTl6Ea3F7tjdyBdMw/RISL0UM2fQLnLk5rr/Ii2ebX lb4w==
X-Gm-Message-State: AD7BkJJqH+gpIrwWbxfErywHmgfG7FF5rHPuQpxVwjj02J1PEIeItcoPxj2fa8gfdn0QK8QNis2jsGkXkbZ1Bvgq
X-Received: by 10.55.72.86 with SMTP id v83mr19955241qka.72.1460244755430; Sat, 09 Apr 2016 16:32:35 -0700 (PDT)
MIME-Version: 1.0
References: <0D914666-C3D4-4CCE-AD5E-4E5B34EA1A73@piuha.net> <20160407182936.GA21340@pfrc.org> <CAB75xn780nNDjGa_Cc222J20-+1CCHt09Xp8KHzaK=n0xx51pg@mail.gmail.com> <5706B100.9040509@mnt.se> <CAB75xn6fmj84ROUtG5eUB3GerHx83hrEr3w5vSADY_g=BRg5FA@mail.gmail.com> <9B723FB0-6B93-4C85-ADD9-D423F873CF08@virtualized.org> <20160409155300.6283348.41255.10529@blackberry.com> <ADC8666A-436C-4AD4-BD48-9277601069F8@gmail.com> <57093CD3.3050502@gmail.com> <f5b1ceec-4cd5-55b5-5089-4a499ed0586c@bogus.com> <F2D3ACF5-C7BD-4D0C-8518-665D2EDAA6CA@cisco.com> <570955E3.2010205@gmail.com> <alpine.OSX.2.01.1604091401420.42313@rabdullah.local> <429DD401-DB4F-4B09-9EF8-035EFB089488@frobbit.se>
In-Reply-To: <429DD401-DB4F-4B09-9EF8-035EFB089488@frobbit.se>
From: Warren Kumari <warren@kumari.net>
Date: Sat, 09 Apr 2016 23:32:25 +0000
Message-ID: <CAHw9_iLfBv-dzJcpqJdVwoMCjaK37JH0WimzWec4v4QaprpowA@mail.gmail.com>
Subject: Re: Concerns about Singapore
To: Ole Jacobsen <olejacobsen@me.com>, =?UTF-8?B?UGF0cmlrIEbDpGx0c3Ryw7Zt?= <paf@frobbit.se>
Content-Type: multipart/alternative; boundary=001a11487656eee5eb053015b976
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/RwUlhoTEPZ8BfETCK3v-BsGLaOM>
Cc: "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: Sat, 09 Apr 2016 23:32:39 -0000

--001a11487656eee5eb053015b976
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

ICANN has also met in Sengal and Morocco recently -- while I didn't hear of
any issues there either, they are not exactly shining bastions in the human
rights areas. Just because we didn't hear about issues doesn't mean people
were comfortable there...

W

On Sat, Apr 9, 2016 at 7:36 PM Patrik F=C3=A4ltstr=C3=B6m <paf@frobbit.se> =
wrote:

> On 9 Apr 2016, at 23:05, Ole Jacobsen wrote:
>
> > There are several sources online for this information, including the
> > US State Department, but we are also actively seeking clarification
> > from contacts in Singapore about these issues. So far, I am fairly
> > certain that our attendees won't notice any issues at all, but stay
> > tuned as we gather the facts.
>
> FWIW, ICANN has met in Singapore a few times recently and I have not hear=
d
> about any issues what so ever.
>
>    Patrik
>

--001a11487656eee5eb053015b976
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div style=3D"white-space:pre-wrap">ICANN has also met in Sengal and Morocc=
o recently -- while I didn&#39;t hear of any issues there either, they are =
not exactly shining bastions in the human rights areas. Just because we did=
n&#39;t hear about issues doesn&#39;t mean people were comfortable there...=
<br><br>W</div><br><div class=3D"gmail_quote"><div dir=3D"ltr">On Sat, Apr =
9, 2016 at 7:36 PM Patrik F=C3=A4ltstr=C3=B6m &lt;<a href=3D"mailto:paf@fro=
bbit.se">paf@frobbit.se</a>&gt; wrote:<br></div><blockquote class=3D"gmail_=
quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1=
ex">On 9 Apr 2016, at 23:05, Ole Jacobsen wrote:<br>
<br>
&gt; There are several sources online for this information, including the<b=
r>
&gt; US State Department, but we are also actively seeking clarification<br=
>
&gt; from contacts in Singapore about these issues. So far, I am fairly<br>
&gt; certain that our attendees won&#39;t notice any issues at all, but sta=
y<br>
&gt; tuned as we gather the facts.<br>
<br>
FWIW, ICANN has met in Singapore a few times recently and I have not heard =
about any issues what so ever.<br>
<br>
=C2=A0 =C2=A0Patrik<br>
</blockquote></div>

--001a11487656eee5eb053015b976--


From nobody Sat Apr  9 18:07:14 2016
Return-Path: <brian.e.carpenter@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 3E7A012D525 for <ietf@ietfa.amsl.com>; Sat,  9 Apr 2016 18:07:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 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, 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 Y959PRPFYbao for <ietf@ietfa.amsl.com>; Sat,  9 Apr 2016 18:07:11 -0700 (PDT)
Received: from mail-pf0-x229.google.com (mail-pf0-x229.google.com [IPv6:2607:f8b0:400e:c00::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 3BBDF12D519 for <ietf@ietf.org>; Sat,  9 Apr 2016 18:07:11 -0700 (PDT)
Received: by mail-pf0-x229.google.com with SMTP id e128so99445854pfe.3 for <ietf@ietf.org>; Sat, 09 Apr 2016 18:07:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=subject:to:references:cc:from:organization:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=5akyprBhoajDaPYimMICJX3eKyxVCfamNP7wUypSTi8=; b=Wr1BN0UNNyXLWUcJjBR94v9c425xNvoEOiZLLIlwrG5biiAi++nhlqwOZeyRmJ3Lb5 VBASz3M6V8WoWSsmqJLE3Dfmy2Mx9pMEzGJVpk8L5q5HbEc88elNoz+fNb3Z38fJdSgD 1Vj+shf8hy7pp29uW5kV0qyTZHh9TkrGrqbBHSIug99DcM5NkMmbjOwwGHPoAH44v55r RQnpnIixhnuAaIEDhA9rDbFBXSPj/XD870E9iNWJCzfdSJ45tNU3cevifx5GbaLVGQlA g+WBcuNIMPqViKqQD5jDaQPmpqdVoOg/CFP2wh9Q2U/Atu4wSAWyE/keCcq0rwK0+C4f sEGg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:cc:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=5akyprBhoajDaPYimMICJX3eKyxVCfamNP7wUypSTi8=; b=J3zizxLSplbMse/glTjja5UEXzR0WM4Bsvydhs2kbTIk9a07uu7VOCwr392Ooz0+kl wm3x1JtRBnMSJbxiFxm6ctdVAgQQ+al4/QF8Le6LsyjfzuEdSoELpYmaBRAWhKKPB219 Cs7ny/YiQ7Y2fbLOs/QIveM7InFDDCtBPygIm5aV9RwIGveXbJzrQIwV2wJRpAXoAH6p zMSvswq4et7TNID1qJTUmOkKBr1m2sm/Aprvvx7vQWlaOTt1rsgZuSOn7qeEZpdPbgRu pqzcPPI8Edh9WEw7aelTnTc++wEKuY00mDTXWoE+jhHwCXEy7D0HqlGQEzpce9aUIUfJ m9LA==
X-Gm-Message-State: AD7BkJIeGw8CAjMs/vopkMDW9HV1EeMrYB9LQMjlB5uzyf9eo9REHDDh1Pe6wZ2T4N8Fwg==
X-Received: by 10.98.7.153 with SMTP id 25mr23188871pfh.38.1460250430819; Sat, 09 Apr 2016 18:07:10 -0700 (PDT)
Received: from ?IPv6:2406:e007:74e8:1:28cc:dc4c:9703:6781? ([2406:e007:74e8:1:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id r65sm27274827pfa.27.2016.04.09.18.07.07 (version=TLSv1/SSLv3 cipher=OTHER); Sat, 09 Apr 2016 18:07:09 -0700 (PDT)
Subject: Re: Concerns about Singapore
To: John C Klensin <john-ietf@jck.com>, Melinda Shore <melinda.shore@gmail.com>
References: <0D914666-C3D4-4CCE-AD5E-4E5B34EA1A73@piuha.net> <20160407182936.GA21340@pfrc.org> <CAB75xn780nNDjGa_Cc222J20-+1CCHt09Xp8KHzaK=n0xx51pg@mail.gmail.com> <5706B100.9040509@mnt.se> <CAB75xn6fmj84ROUtG5eUB3GerHx83hrEr3w5vSADY_g=BRg5FA@mail.gmail.com> <9B723FB0-6B93-4C85-ADD9-D423F873CF08@virtualized.org> <20160409155300.6283348.41255.10529@blackberry.com> <ADC8666A-436C-4AD4-BD48-9277601069F8@gmail.com> <57093CD3.3050502@gmail.com> <f5b1ceec-4cd5-55b5-5089-4a499ed0586c@bogus.com> <F2D3ACF5-C7BD-4D0C-8518-665D2EDAA6CA@cisco.com> <570955E3.2010205@gmail.com> <57096C65.7020409@gmail.com> <57097200.5050503@gmail.com> <2C0674FBC5C419DAC427E4BC@JcK-HP8200.jck.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <5709A748.3030804@gmail.com>
Date: Sun, 10 Apr 2016 13:07:20 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2
MIME-Version: 1.0
In-Reply-To: <2C0674FBC5C419DAC427E4BC@JcK-HP8200.jck.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/dqjIWeJ22UVSRgLQq3OGl4HkVKI>
Cc: 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: Sun, 10 Apr 2016 01:07:12 -0000

On 10/04/2016 10:35, John C Klensin wrote:
...
> I hope that, as the IAOC continues "actively seeking
> clarification", the distinction between the ability to express
> support without getting arrested and the ability to practice the
> nominally-criminal behavior without getting arrested (even
> occasionally) is well understood.
> 
> It may be just me, but the distinctions really seem a lot more
> clear than the length of this discussion thread would seem to
> imply.

The distinction is quite clear, but my point and the reason I broke
my silence on this thread is that even so, it's *still* a judgment
call, whether the issue is freedom of speech, freedom of behaviour,
personal risk, or even old-fashioned discrimination as in the example
I gave.

   Brian


From nobody Sat Apr  9 20:21:17 2016
Return-Path: <robert.w.withers@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 4513E12D1DC for <ietf@ietfa.amsl.com>; Sat,  9 Apr 2016 20:21:15 -0700 (PDT)
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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 Blx4ykh3E8Nr for <ietf@ietfa.amsl.com>; Sat,  9 Apr 2016 20:21:13 -0700 (PDT)
Received: from mail-yw0-x22f.google.com (mail-yw0-x22f.google.com [IPv6:2607:f8b0:4002:c05::22f]) (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 620E912D094 for <ietf@ietf.org>; Sat,  9 Apr 2016 20:21:13 -0700 (PDT)
Received: by mail-yw0-x22f.google.com with SMTP id o66so83442933ywc.3 for <ietf@ietf.org>; Sat, 09 Apr 2016 20:21:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=subject:references:to:from:message-id:date:user-agent:mime-version :in-reply-to; bh=/i7EHvtbjXBnwIiU7nHGNg70B5O4FuCS5BHJGA2C63k=; b=t7nuab/ukK2915t1KMygWre5c0kihmYOn0qe2y5n5UcyzSsonC0hAVIeB6mwnlbwfb ypka2xKFh8kryOqzITAhubqsPqovlWr5NL2q6yGEMs0Sps/BrbKcflvN2oqRTZIZ23C1 OdHHsZ4aai1uNtxk4rPvVNf6s00WkXxsNdxdjQVEJD0SZ1cGoFhNXoFLXnF8htuGxeBv A2cEKbO3RZp0REsyT0QijNE+pUfF/mS6AFhKKtdVNZwV5kChnw2sz038uPS8EWwCdEhe mPXYsC1I8xcam7JnTQGS2gpmVytGkk5gHPPVi+RH8MpvEbdDZUl71Crm3nMPtIqDvE/D T8Ew==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:references:to:from:message-id:date :user-agent:mime-version:in-reply-to; bh=/i7EHvtbjXBnwIiU7nHGNg70B5O4FuCS5BHJGA2C63k=; b=b2R2qWMLLbk/8cZgMdJAql0VsrrQ75Wh+40YNzWoTU9mBJIuCPQkMf911m+JNxOg+e gPnGiMFHu/CVAMl5SAHltUH37J7Wu3JVmUKxj78J9+xEk1HQhfg3h3Z4p0i2e9/s+ek0 fSQ8rrI1pbMAFef7brJBqT657kkaEWXKf6Iz1k/nmsz/+mTIoVNzusw5i8PeQhTTPjw5 msOvx0YPP2SzshuR1C+chkD0RwK5IuUkqrC/SG4hNSleLvPIlaYP6VWJjvlXCN0eoem9 jLniYvP6r6eQqXVaHeqEursrAm10UsNQVMmErLYWv4kmvohlwaI+Mo/jkYXa2rX1B/90 4wkw==
X-Gm-Message-State: AD7BkJKe/hPKBHTss/hJ55MRXEr1TvilzTcnu+gWJ+53JvFhE+M/mvPjVR8QTJLW3+Nw9w==
X-Received: by 10.129.95.84 with SMTP id t81mr9235709ywb.16.1460258472624; Sat, 09 Apr 2016 20:21:12 -0700 (PDT)
Received: from [192.168.2.2] (cpe-107-15-45-203.nc.res.rr.com. [107.15.45.203]) by smtp.gmail.com with ESMTPSA id i125sm11633546ywb.24.2016.04.09.20.21.11 for <ietf@ietf.org> (version=TLSv1/SSLv3 cipher=OTHER); Sat, 09 Apr 2016 20:21:11 -0700 (PDT)
Subject: Fwd: SecureSessionV1Server
References: <5709C0B7.4070604@gmail.com>
To: IETF Discussion <ietf@ietf.org>
From: Robert Withers <robert.w.withers@gmail.com>
X-Forwarded-Message-Id: <5709C0B7.4070604@gmail.com>
Message-ID: <5709C6A5.8050603@gmail.com>
Date: Sat, 9 Apr 2016 23:21:09 -0400
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:38.0) Gecko/20100101 Thunderbird/38.6.0
MIME-Version: 1.0
In-Reply-To: <5709C0B7.4070604@gmail.com>
Content-Type: multipart/alternative; boundary="------------030906050007000609060001"
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/Fhr1bXC3qPZJdHO29xdXVkEbiEk>
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: Sun, 10 Apr 2016 03:21:15 -0000

This is a multi-part message in MIME format.
--------------030906050007000609060001
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit

Please find a squeak implementation of the frame design I published here 
some months ago.

Robert

-------- Forwarded Message --------
Subject: 	SecureSessionV1Server
Date: 	Sat, 9 Apr 2016 22:55:51 -0400
From: 	Robert Withers <robert.w.withers@gmail.com>
To: 	The general-purpose Squeak developers list 
<squeak-dev@lists.squeakfoundation.org>, Pharo Development List 
<pharo-dev@lists.pharo.org>, Cryptography Mailing List 
<cryptography@lists.squeakfoundation.org>



Over the course of several months, I've been working on the
implementation of SecureSessionV1 to adopt new protocol and message
frame definitions. As to the original connection protocol and frames, I
preserved it as a backwards compatible Vintage implementation. This
change simplified a fair bit of code and will allow for some further
modifications.

I apologize for my habit in using the code and unit tests to document
the system, an old habit to try for a self-describing domain language of
secure sessions. Please look in SecureSession-Tests for examples in
using both the Vintage and V1 protocols. The key classes for the Vintage
version remain SecureSessionServer and SecureSessionTerminal, while the
V1 version use SecureSessionV1Server and SecureSessionV1Terminal.

Here are some helpful links..

The V1 Frame Design is http://jmp.sh/1Uo0dr7, though I should note there
are changes to the DataHeader, which holds the mac and the plaintextLength.

The code is found in http://www.squeaksource.com/Cryptography and the
SecureSession package requires the Cryptography package and for a
notable speed improvements the Cryptography plugins build for your VM.

- Robert




--------------030906050007000609060001
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 7bit

<html>
  <head>

    <meta http-equiv="content-type" content="text/html; charset=utf-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    Please find a squeak implementation of the frame design I published
    here some months ago.<br>
    <div class="moz-forward-container"><br>
      Robert<br>
      <br>
      -------- Forwarded Message --------
      <table class="moz-email-headers-table" border="0" cellpadding="0"
        cellspacing="0">
        <tbody>
          <tr>
            <th nowrap="nowrap" valign="BASELINE" align="RIGHT">Subject:
            </th>
            <td>SecureSessionV1Server</td>
          </tr>
          <tr>
            <th nowrap="nowrap" valign="BASELINE" align="RIGHT">Date: </th>
            <td>Sat, 9 Apr 2016 22:55:51 -0400</td>
          </tr>
          <tr>
            <th nowrap="nowrap" valign="BASELINE" align="RIGHT">From: </th>
            <td>Robert Withers <a class="moz-txt-link-rfc2396E" href="mailto:robert.w.withers@gmail.com">&lt;robert.w.withers@gmail.com&gt;</a></td>
          </tr>
          <tr>
            <th nowrap="nowrap" valign="BASELINE" align="RIGHT">To: </th>
            <td>The general-purpose Squeak developers list
              <a class="moz-txt-link-rfc2396E" href="mailto:squeak-dev@lists.squeakfoundation.org">&lt;squeak-dev@lists.squeakfoundation.org&gt;</a>, Pharo
              Development List <a class="moz-txt-link-rfc2396E" href="mailto:pharo-dev@lists.pharo.org">&lt;pharo-dev@lists.pharo.org&gt;</a>,
              Cryptography Mailing List
              <a class="moz-txt-link-rfc2396E" href="mailto:cryptography@lists.squeakfoundation.org">&lt;cryptography@lists.squeakfoundation.org&gt;</a></td>
          </tr>
        </tbody>
      </table>
      <br>
      <br>
      <pre>Over the course of several months, I've been working on the 
implementation of SecureSessionV1 to adopt new protocol and message 
frame definitions. As to the original connection protocol and frames, I 
preserved it as a backwards compatible Vintage implementation. This 
change simplified a fair bit of code and will allow for some further 
modifications.

I apologize for my habit in using the code and unit tests to document 
the system, an old habit to try for a self-describing domain language of 
secure sessions. Please look in SecureSession-Tests for examples in 
using both the Vintage and V1 protocols. The key classes for the Vintage 
version remain SecureSessionServer and SecureSessionTerminal, while the 
V1 version use SecureSessionV1Server and SecureSessionV1Terminal.

Here are some helpful links..

The V1 Frame Design is <a class="moz-txt-link-freetext" href="http://jmp.sh/1Uo0dr7">http://jmp.sh/1Uo0dr7</a>, though I should note there 
are changes to the DataHeader, which holds the mac and the plaintextLength.

The code is found in <a class="moz-txt-link-freetext" href="http://www.squeaksource.com/Cryptography">http://www.squeaksource.com/Cryptography</a> and the 
SecureSession package requires the Cryptography package and for a 
notable speed improvements the Cryptography plugins build for your VM.

- Robert
</pre>
      <br>
    </div>
    <br>
  </body>
</html>

--------------030906050007000609060001--


From nobody Sat Apr  9 20:49:17 2016
Return-Path: <superuser@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 B0EBB12D562 for <ietf@ietfa.amsl.com>; Sat,  9 Apr 2016 20:49:16 -0700 (PDT)
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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 lWnE_pGRDK1W for <ietf@ietfa.amsl.com>; Sat,  9 Apr 2016 20:49:15 -0700 (PDT)
Received: from mail-vk0-x229.google.com (mail-vk0-x229.google.com [IPv6:2607:f8b0:400c:c05::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 6901512D56F for <ietf@ietf.org>; Sat,  9 Apr 2016 20:49:15 -0700 (PDT)
Received: by mail-vk0-x229.google.com with SMTP id c4so177848870vkb.3 for <ietf@ietf.org>; Sat, 09 Apr 2016 20:49:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=JfeZKxHo2crwzNoCi4Ib8RVKe3ABzziOc1jHOebVhuA=; b=Eqlpyz9bRVzk4p0VnQWicn9G+7XBrM8ut9NpvPoeYfqTsRXVaz2vhsxXFgEIauAKZq Prv+dK+bSJQsObC327/EtBiHFqXXNJukUtzXBVf5vlnaQYnrJD0G9Xa2gbbgEeWvHJtI 4fPJqLY8wVhiKvPA9812NyP4D/idKWNH6fSQWKPTRt8bPYYClTSdkdUaDu21l5E00JMG y+NKMBcBWsa/fPnqoKnQJLdGedEsAv94hAl+r0i2loqsddbv0MHXy+3QHdrvrAGJj0q9 97WJ+2ZbnI35vcrrek+4gVZapN1yMSQBiTcp2AJYFShH8UYts83mkq8GRKd+arVt090d 0+iw==
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:date :message-id:subject:from:to:cc; bh=JfeZKxHo2crwzNoCi4Ib8RVKe3ABzziOc1jHOebVhuA=; b=k3+Oy85j0mGJOkFmCq5kG27YFavejOf7AGtDp3Woi2iq1pOFTXkDg3GO3Xz9eSCd1b w+3vW2VuG+KB8SVaffJCmn5Vv1LIUy0k3nI0jd8u3H1xyWYrSMT8wREWvAjqzlq3kaK8 3fZDrsZs+gIGhY9cTHvRCFcXk1/A5pOQz0RtFbNjnFmejAr/AEONbBc+h4XOmW6Al0gf CSwskKz1d2BroJcWzHnnX83wEYQTyTDJGnaX3u3nQNDltfvNy2NgnU6/1pJZ4gVIBywE XYVw5ERbOIAWPGlNm9Yhd7APN1rARYNZLZVm0/6LFgF8QJi5C8h5TGQuWHPAI5xrkLiG Xf/Q==
X-Gm-Message-State: AD7BkJJGObfpE+hAB0MMDRv+jcVcoOgIuJQCdnpj4G8muEybZOVwa1IeIATtNiPe0VyryJACpPC1bhmx/4yqbg==
MIME-Version: 1.0
X-Received: by 10.31.54.139 with SMTP id d133mr8095993vka.132.1460260154533; Sat, 09 Apr 2016 20:49:14 -0700 (PDT)
Received: by 10.103.43.5 with HTTP; Sat, 9 Apr 2016 20:49:14 -0700 (PDT)
In-Reply-To: <13214.1460236486@obiwan.sandelman.ca>
References: <20160408185636.23101.86017.idtracker@ietfa.amsl.com> <570882CE.9010501@gmail.com> <13214.1460236486@obiwan.sandelman.ca>
Date: Sat, 9 Apr 2016 20:49:14 -0700
Message-ID: <CAL0qLwYKbB3_PQcUAUDqJwnddc4oywffVD+sVusOK2xiBYu4PA@mail.gmail.com>
Subject: Re: I-D Action: draft-kucherawy-nomcom-procexp-00.txt
From: "Murray S. Kucherawy" <superuser@gmail.com>
To: Michael Richardson <mcr+ietf@sandelman.ca>
Content-Type: multipart/alternative; boundary=001a11438350ca6cd40530194fcc
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/sh7oZHpQStQZ0Yy6bzpKLGQtfSE>
Cc: IETF discussion list <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: Sun, 10 Apr 2016 03:49:16 -0000

--001a11438350ca6cd40530194fcc
Content-Type: text/plain; charset=UTF-8

On Sat, Apr 9, 2016 at 2:14 PM, Michael Richardson <mcr+ietf@sandelman.ca>
wrote:

>
> Is this challenge public?
> I think that it is, but I'm not certain if all of it is public.
>
>
Looks like it doesn't have to be, as I read Section 4.17 of RFC7437.

-MSK

--001a11438350ca6cd40530194fcc
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">On Sat, Apr 9, 2016 at 2:14 PM, Michael Richardson <span d=
ir=3D"ltr">&lt;<a href=3D"mailto:mcr+ietf@sandelman.ca" target=3D"_blank">m=
cr+ietf@sandelman.ca</a>&gt;</span> wrote:<br><div class=3D"gmail_extra"><d=
iv class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margin:=
0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=3D""></=
span><span class=3D""><br>
</span>Is this challenge public?<br>
I think that it is, but I&#39;m not certain if all of it is public.<br>
<br></blockquote><div><br></div><div>Looks like it doesn&#39;t have to be, =
as I read Section 4.17 of RFC7437.<br><br></div><div>-MSK <br></div></div><=
/div></div>

--001a11438350ca6cd40530194fcc--


From nobody Sat Apr  9 20:53:21 2016
Return-Path: <brian.e.carpenter@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 D00B612D534 for <ietf@ietfa.amsl.com>; Sat,  9 Apr 2016 20:53:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 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, RCVD_IN_DNSWL_LOW=-0.7, 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 0wO3m-7ksiVU for <ietf@ietfa.amsl.com>; Sat,  9 Apr 2016 20:53:18 -0700 (PDT)
Received: from mail-pf0-x230.google.com (mail-pf0-x230.google.com [IPv6:2607:f8b0:400e:c00::230]) (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 AF79012D1E0 for <ietf@ietf.org>; Sat,  9 Apr 2016 20:53:18 -0700 (PDT)
Received: by mail-pf0-x230.google.com with SMTP id c20so101108382pfc.1 for <ietf@ietf.org>; Sat, 09 Apr 2016 20:53:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=subject:to:references:cc:from:organization:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=ZQxMF/oYTnjO4QKhIHW8cIl55JVr8NeZaO+Y8tsGq5M=; b=hveMlW7LtAZxUaiD5q+5bgnpBubYylLFlckxWf2gT1TLQs+alJn1dd9xXiMgWgNcpa QskuajmOyriN0V2W/4b6+GUZFMhJ26OePYjBfOP6yYY0BE0eQ/git41OnVoPUKax+qRn RsytuEisjpsVJQNHyFWuTKykXa/sk9cwJeAnybLogs6WjWoZnKxnW/CTv9ZXQCxvd5pL aJhODX1bARWbJWb3YC08eQ2p/eY3HMUUwhsmxm3roord4G4hk20h/vZU9AEfzEBRGwlb 1pbJ7SG7e6w6hTrYJN98AtR8KT5xtM/ToWEmIMURpSqebxKdMo9yk6jy7/8ZXlRiECn7 CUGA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:cc:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=ZQxMF/oYTnjO4QKhIHW8cIl55JVr8NeZaO+Y8tsGq5M=; b=Ovv5U5/CAX40mHvEY9cw0FrnobCHomLzzTHfFl6xIg1qVYls59XdfPEhaiWSB0Qy/a iCSfFRC5E9/JLDG3uTxLeldoz/sTnHd83OP6988WzhGY11X+DETrV5noN48UcVRUGhq4 mt6buz35UQuvBXbf6+GD9/UqafUkWtUbC3yAxYUS/YudUW4gvVrsZ00oDFNToXSNiysU WAtFNx41ELCHU5GKIG/HxuAzfwDVtvatBKohq6mbYW5cyPpcD/RZjOmaqFZzr1kKPEIs ZWwEtqy9WoUVPTf2nkpc1WrZkiDeGKjb+RzMDwShFkKU7rk7TNs4hrUGlRp8BURVIVtH l8gg==
X-Gm-Message-State: AD7BkJJ8Lowg3gryg9UWB3rtoIQXQRBCl9Di9m4MWG6qall5iYhJFsm7eIWUgtN+tRR1Hg==
X-Received: by 10.98.18.1 with SMTP id a1mr23940625pfj.39.1460260398277; Sat, 09 Apr 2016 20:53:18 -0700 (PDT)
Received: from ?IPv6:2406:e007:74e8:1:28cc:dc4c:9703:6781? ([2406:e007:74e8:1:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id u2sm8762041pan.45.2016.04.09.20.53.15 (version=TLSv1/SSLv3 cipher=OTHER); Sat, 09 Apr 2016 20:53:16 -0700 (PDT)
Subject: Re: I-D Action: draft-kucherawy-nomcom-procexp-00.txt
To: "Murray S. Kucherawy" <superuser@gmail.com>, Michael Richardson <mcr+ietf@sandelman.ca>
References: <20160408185636.23101.86017.idtracker@ietfa.amsl.com> <570882CE.9010501@gmail.com> <13214.1460236486@obiwan.sandelman.ca> <CAL0qLwYKbB3_PQcUAUDqJwnddc4oywffVD+sVusOK2xiBYu4PA@mail.gmail.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <5709CE36.3040605@gmail.com>
Date: Sun, 10 Apr 2016 15:53:26 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2
MIME-Version: 1.0
In-Reply-To: <CAL0qLwYKbB3_PQcUAUDqJwnddc4oywffVD+sVusOK2xiBYu4PA@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/ZFFiGqdGe-WskgbbJhaXqYJzROs>
Cc: IETF discussion list <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: Sun, 10 Apr 2016 03:53:20 -0000

On 10/04/2016 15:49, Murray S. Kucherawy wrote:
> On Sat, Apr 9, 2016 at 2:14 PM, Michael Richardson <mcr+ietf@sandelman.ca>
> wrote:
> 
>>
>> Is this challenge public?
>> I think that it is, but I'm not certain if all of it is public.
>>
>>
> Looks like it doesn't have to be, as I read Section 4.17 of RFC7437.

Regardless, I would think we would want challenges that said things
like "Brian Carpenter really hasn't been active enough in the last
couple of years to be able to evaluate the candidates" rather than
vaguely suggest that he is isn't suitable.


From nobody Sat Apr  9 21:46:58 2016
Return-Path: <superuser@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 52D3712D59D for <ietf@ietfa.amsl.com>; Sat,  9 Apr 2016 21:46:57 -0700 (PDT)
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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 AJwiUo2dVSrC for <ietf@ietfa.amsl.com>; Sat,  9 Apr 2016 21:46:56 -0700 (PDT)
Received: from mail-vk0-x230.google.com (mail-vk0-x230.google.com [IPv6:2607:f8b0:400c:c05::230]) (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 9F80B12D597 for <ietf@ietf.org>; Sat,  9 Apr 2016 21:46:55 -0700 (PDT)
Received: by mail-vk0-x230.google.com with SMTP id c4so178408765vkb.3 for <ietf@ietf.org>; Sat, 09 Apr 2016 21:46:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=GBcO0rtTnAYvePcBXhcC5FVnunaTtcmeGhrUoQFdikw=; b=wIWR8R+SSNgen8f1cLd1qDKCFFo/Eiw7Nn4t9CsG+17/3RNRwYPzJ4BKgeAJPB/7KZ dwZKGCKgJyktR3IZr8IibTTnLds7ZWh/0aP1gb8+FuNnZShmsUgEH5OZgKGmeQSoVunp XynNeVcW6Z5XzdYeXDXxDlHZDoojnwdKIAjPq+mW9ODKWXGrV3j0qLsVR7QkYhHULRNI arPimOmHlI0GRG4kbDzV/r88E71oWhoYymufimhx5EcVY8PkoWetl99Q0Q33O4Q+tEbj RWeY+EL495MjDdKOc7undKxs+vWu4PqFUEaF6UVv3pM0Aepuw2bES0ec5xILfDxbaneB SdFg==
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:date :message-id:subject:from:to:cc; bh=GBcO0rtTnAYvePcBXhcC5FVnunaTtcmeGhrUoQFdikw=; b=ZXlQamw9UqmhklwsV0+5DwQuFJhtySavsJDdAo4k6pzxRunc/r0rHeyeG8Cm7weyJ9 cITriQWHnzVnq27GXDgxU41gZ79iSUO7M5OxSnnOm+FFH+fKckPT8bcgVJkwdTmvV++k BRUMv/yHI9Ed8a2gvd1jiSMzXO3Tb1MBjnR+bLe6Bquij9s/OS9J3XtFbDaAUReQogbd s9cXD5vYHDvEk3kcI9wmq94AiSF5WrRGM6smIHSb4PXd6w9NDFQ5RhuHfrdTufAVNGbt hA77H9RAocyvfTQ1X9GkYGsCugWPhQLqsol+TXXo/tLBEUox2VpOkYUy6U5Ap70yokJl nyIQ==
X-Gm-Message-State: AD7BkJIamzUO2G9xwrdOwzly9JApVLsAfTvCekHyHTSAEGv1+SUbAzPRvlvLRjdYjCYjDlLVfBlSeSgCpB6kvw==
MIME-Version: 1.0
X-Received: by 10.31.151.11 with SMTP id z11mr8141369vkd.131.1460263614730; Sat, 09 Apr 2016 21:46:54 -0700 (PDT)
Received: by 10.103.43.5 with HTTP; Sat, 9 Apr 2016 21:46:54 -0700 (PDT)
In-Reply-To: <5709CE36.3040605@gmail.com>
References: <20160408185636.23101.86017.idtracker@ietfa.amsl.com> <570882CE.9010501@gmail.com> <13214.1460236486@obiwan.sandelman.ca> <CAL0qLwYKbB3_PQcUAUDqJwnddc4oywffVD+sVusOK2xiBYu4PA@mail.gmail.com> <5709CE36.3040605@gmail.com>
Date: Sat, 9 Apr 2016 21:46:54 -0700
Message-ID: <CAL0qLwbROnW8pKKtd=7hkHHyP=xA-_eNoBuoKqPpaGjjpgUH+Q@mail.gmail.com>
Subject: Re: I-D Action: draft-kucherawy-nomcom-procexp-00.txt
From: "Murray S. Kucherawy" <superuser@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Content-Type: multipart/alternative; boundary=001a1140f86a08d7b605301a1ec0
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/4JeVxkQxQoQDY_xkmAIAV4SOSGI>
Cc: Michael Richardson <mcr+ietf@sandelman.ca>, IETF discussion list <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: Sun, 10 Apr 2016 04:46:57 -0000

--001a1140f86a08d7b605301a1ec0
Content-Type: text/plain; charset=UTF-8

On Sat, Apr 9, 2016 at 8:53 PM, Brian E Carpenter <
brian.e.carpenter@gmail.com> wrote:

>
> Regardless, I would think we would want challenges that said things
> like "Brian Carpenter really hasn't been active enough in the last
> couple of years to be able to evaluate the candidates" rather than
> vaguely suggest that he is isn't suitable.
>

Does bullet 3 in Section 2 need to say more than it does now on that topic?

-MSK

--001a1140f86a08d7b605301a1ec0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">On Sat, Apr 9, 2016 at 8:53 PM, Brian E Carpenter <span di=
r=3D"ltr">&lt;<a href=3D"mailto:brian.e.carpenter@gmail.com" target=3D"_bla=
nk">brian.e.carpenter@gmail.com</a>&gt;</span> wrote:<br><div class=3D"gmai=
l_extra"><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=
=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span cl=
ass=3D""><br>
</span>Regardless, I would think we would want challenges that said things<=
br>
like &quot;Brian Carpenter really hasn&#39;t been active enough in the last=
<br>
couple of years to be able to evaluate the candidates&quot; rather than<br>
vaguely suggest that he is isn&#39;t suitable.<br>
</blockquote></div><br></div><div class=3D"gmail_extra">Does bullet 3 in Se=
ction 2 need to say more than it does now on that topic?<br><br></div><div =
class=3D"gmail_extra">-MSK<br></div></div>

--001a1140f86a08d7b605301a1ec0--


From nobody Sat Apr  9 22:26:49 2016
Return-Path: <aallen@blackberry.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 41D9B12D5BA for <ietf@ietfa.amsl.com>; Sat,  9 Apr 2016 22:26:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.617
X-Spam-Level: 
X-Spam-Status: No, score=-3.617 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.996, SPF_PASS=-0.001] 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 p2YnKfuGJiKI for <ietf@ietfa.amsl.com>; Sat,  9 Apr 2016 22:26:42 -0700 (PDT)
Received: from smtp-p02.blackberry.com (smtp-p02.blackberry.com [208.65.78.89]) by ietfa.amsl.com (Postfix) with ESMTP id ABBEF12D5B1 for <ietf@ietf.org>; Sat,  9 Apr 2016 22:26:42 -0700 (PDT)
Received: from xct104cnc.rim.net ([10.65.161.204]) by mhs213cnc.rim.net with ESMTP/TLS/AES256-SHA; 10 Apr 2016 03:01:29 -0400
Received: from XMB122CNC.rim.net ([fe80::28c6:fa1c:91c6:2e23]) by XCT104CNC.rim.net ([::1]) with mapi id 14.03.0210.002; Sun, 10 Apr 2016 01:26:37 -0400
From: Andrew Allen <aallen@blackberry.com>
To: Michael Richardson <mcr+ietf@sandelman.ca>
Subject: Re: Concerns about Singapore
Thread-Topic: Concerns about Singapore
Thread-Index: AQHRkOMNjufwcA4TvkK+5mik25hZRp9/GCcAgAAATwCAAAuKAIAACE6AgAD6eICAAAvNgIAAOMwAgAAA3QD//8IaK4AAkjiAgAHwxu4=
Date: Sun, 10 Apr 2016 05:26:36 +0000
Message-ID: <20160410052634.6283348.15018.10533@blackberry.com>
References: <CAB75xn6fmj84ROUtG5eUB3GerHx83hrEr3w5vSADY_g=BRg5FA@mail.gmail.com> <1481689286.47880.1460111891664.JavaMail.yahoo@mail.yahoo.com> <alpine.OSX.2.01.1604080418530.36488@rabdullah.local> <594.1460126622@obiwan.sandelman.ca>,<5707C458.7080107@dcrocker.net> <20160408150512.6283348.55871.10388@blackberry.com>, <3746.1460144915@obiwan.sandelman.ca>
In-Reply-To: <3746.1460144915@obiwan.sandelman.ca>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/5avfCUVKCB7iPxI1lW3TR5sYCUs>
Cc: Dave Crocker <dcrocker@bbiw.net>, "ietf@ietf.org 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: Sun, 10 Apr 2016 05:26:47 -0000

I would have thought the cost of transportation would likely more than offs=
et the savings in terms of hotels. Not sure how practical it would be to us=
e cheap public transportation to make that trip every day to attend a meeti=
ng .

Although Singapore may be called a city state like Hong Kong there is quite=
 a bit more to it than just the city and the causeway to Malaysia is the ot=
her side of the island from the Metropolitan area.

In the case of HK the MTR does go all the way to the border and then the Sc=
henzhen subway is accessible from the other side, however I wouldn't think =
it would be very practical to try to commute every day between HK and Schen=
zhen either and I expect a similar or worse situation exists between Singap=
ore and Malaysia.

This is coming from someone who commuted every day to Yokohama from downtow=
n Tokyo which was actually quite cheap (about $5 US each way) although it t=
ook about and hour each way.

Andrew

Sent from my BlackBerry 10 smartphone.
  Original Message
From: Michael Richardson
Sent: Friday, April 8, 2016 20:48
To: Andrew Allen
Cc: Dave Crocker; Ole Jacobsen; ietf@ietf.org Discussion
Subject: Re: Concerns about Singapore


Andrew Allen <aallen@blackberry.com> wrote:
    > According to the Web link posted earlier Malaysia has similar laws.

Yes, I wasn't suggesting it because of laws, but rather because I thought i=
t
might have a larger variety of price ranges in hotels.

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -=3D IPv6 IoT consulting =3D-




From nobody Sat Apr  9 22:26:53 2016
Return-Path: <aallen@blackberry.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 6F14012D5BE for <ietf@ietfa.amsl.com>; Sat,  9 Apr 2016 22:26:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.617
X-Spam-Level: 
X-Spam-Status: No, score=-3.617 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.996, SPF_PASS=-0.001] 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 TFYLAAvDhPEW for <ietf@ietfa.amsl.com>; Sat,  9 Apr 2016 22:26:45 -0700 (PDT)
Received: from smtp-p01.blackberry.com (smtp-p01.blackberry.com [208.65.78.88]) by ietfa.amsl.com (Postfix) with ESMTP id ABA8C12D0B7 for <ietf@ietf.org>; Sat,  9 Apr 2016 22:26:42 -0700 (PDT)
Received: from xct102cnc.rim.net ([10.65.161.202]) by mhs211cnc.rim.net with ESMTP/TLS/AES256-SHA; 10 Apr 2016 03:01:41 -0400
Received: from XMB122CNC.rim.net ([fe80::28c6:fa1c:91c6:2e23]) by XCT102CNC.rim.net ([fe80::2066:5d4f:8c45:af55%17]) with mapi id 14.03.0210.002; Sun, 10 Apr 2016 01:26:41 -0400
From: Andrew Allen <aallen@blackberry.com>
To: Michael Richardson <mcr+ietf@sandelman.ca>
Subject: Re: Concerns about Singapore
Thread-Topic: Concerns about Singapore
Thread-Index: AQHRkOMNjufwcA4TvkK+5mik25hZRg==
Date: Sun, 10 Apr 2016 05:26:40 +0000
Message-ID: <20160410052639.6283348.89373.10535@blackberry.com>
References: <20160410052634.6283348.15018.10533@blackberry.com>
Accept-Language: en-CA, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <7570B30C0FC06C4193C94174B9C62D01@rim.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/Y_Ld2uVDBwh0AD8783k8sgwuT6A>
Cc: Dave Crocker <dcrocker@bbiw.net>, "ietf@ietf.org 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: Sun, 10 Apr 2016 05:26:50 -0000

I would have thought the cost of transportation would likely more than offs=
et the savings in terms of hotels. Not sure how practical it would be to us=
e cheap public transportation to make that trip every day to attend a meeti=
ng .

Although Singapore may be called a city state like Hong Kong there is quite=
 a bit more to it than just the city and the causeway to Malaysia is the ot=
her side of the island from the Metropolitan area.=A0

In the case of HK the MTR does go all the way to the border and then the Sc=
henzhen subway is accessible from the other side, however I wouldn't think =
it would be very practical to try to commute every day between HK and Schen=
zhen either and I expect a similar or worse situation exists between Singap=
ore and Malaysia.

This is coming from someone who commuted every day to Yokohama from downtow=
n Tokyo which was actually quite cheap (about $5 US each way) although it t=
ook about an hour each way.

Andrew

Sent=A0from=A0my=A0BlackBerry=A010 smartphone.
=A0 Original Message =A0
From: Michael Richardson
Sent: Friday, April 8, 2016 20:48
To: Andrew Allen
Cc: Dave Crocker; Ole Jacobsen; ietf@ietf.org Discussion
Subject: Re: Concerns about Singapore


Andrew Allen <aallen@blackberry.com> wrote:
> According to the Web link posted earlier Malaysia has similar laws.

Yes, I wasn't suggesting it because of laws, but rather because I thought i=
t
might have a larger variety of price ranges in hotels.

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
-=3D IPv6 IoT consulting =3D-




From nobody Sat Apr  9 23:36:13 2016
Return-Path: <aallen@blackberry.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 4292A12D124 for <ietf@ietfa.amsl.com>; Sat,  9 Apr 2016 23:36:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.616
X-Spam-Level: 
X-Spam-Status: No, score=-3.616 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.996, SPF_PASS=-0.001] 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 7sQe4ms3LiyS for <ietf@ietfa.amsl.com>; Sat,  9 Apr 2016 23:36:10 -0700 (PDT)
Received: from smtp-p02.blackberry.com (smtp-p02.blackberry.com [208.65.78.89]) by ietfa.amsl.com (Postfix) with ESMTP id 1950C12D0AB for <ietf@ietf.org>; Sat,  9 Apr 2016 23:36:09 -0700 (PDT)
Received: from xct107cnc.rim.net ([10.65.161.207]) by mhs215cnc.rim.net with ESMTP/TLS/AES256-SHA; 10 Apr 2016 04:08:54 -0400
Received: from XCT116CNC.rim.net (10.65.161.216) by XCT107CNC.rim.net (10.65.161.207) with Microsoft SMTP Server (TLS) id 14.3.210.2; Sun, 10 Apr 2016 02:36:07 -0400
Received: from XMB122CNC.rim.net ([fe80::28c6:fa1c:91c6:2e23]) by XCT116CNC.rim.net ([::1]) with mapi id 14.03.0210.002; Sun, 10 Apr 2016 02:36:07 -0400
From: Andrew Allen <aallen@blackberry.com>
To: Yoav Nir <ynir.ietf@gmail.com>
Subject: Re: Concerns about Singapore
Thread-Topic: Concerns about Singapore
Thread-Index: AQHRkOMNjufwcA4TvkK+5mik25hZRp9/GCcAgAAATwCAAAuKAIAACE6AgAAKzACAAtn2AIAAFwKAgACcreg=
Date: Sun, 10 Apr 2016 06:36:06 +0000
Message-ID: <20160410063603.6283348.44889.10575@blackberry.com>
References: <0D914666-C3D4-4CCE-AD5E-4E5B34EA1A73@piuha.net> <20160407182936.GA21340@pfrc.org> <CAB75xn780nNDjGa_Cc222J20-+1CCHt09Xp8KHzaK=n0xx51pg@mail.gmail.com> <5706B100.9040509@mnt.se> <CAB75xn6fmj84ROUtG5eUB3GerHx83hrEr3w5vSADY_g=BRg5FA@mail.gmail.com> <9B723FB0-6B93-4C85-ADD9-D423F873CF08@virtualized.org> <20160409155300.6283348.41255.10529@blackberry.com>, <ADC8666A-436C-4AD4-BD48-9277601069F8@gmail.com>
In-Reply-To: <ADC8666A-436C-4AD4-BD48-9277601069F8@gmail.com>
Accept-Language: en-CA, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: multipart/alternative; boundary="_000_2016041006360362833484488910575blackberrycom_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/Wa2RQ_T_N8UEURxbgrqjKndQwqE>
Cc: "ietf@ietf.org 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: Sun, 10 Apr 2016 06:36:12 -0000

--_000_2016041006360362833484488910575blackberrycom_
Content-Type: text/plain; charset="windows-1256"
Content-Transfer-Encoding: quoted-printable


That's why I proposed that IETF check with the hotels that this isn't going=
 to be an issue. The other potential issue I foresee which needs checking w=
ith the authorities is if there will be a problem with customs and immigrat=
ion forms with questions regarding marital status and number of family memb=
ers traveling with you.

Sent from my BlackBerry 10 smartphone.
From: Yoav Nir
Sent: Saturday, April 9, 2016 18:15
To: Andrew Allen
Cc: David Conrad; Dhruv Dhody; ietf@ietf.org Discussion
Subject: Re: Concerns about Singapore


Hi, Andrew


I don't think the IETF should boycott locations just because the community =
doesn't like some of the laws of that country or aspects of that countries =
governments policies=FD.  That is a very slippery slope that could signific=
antly reduce the number of possible meeting locations and also distract fro=
m the IETF mission.

I generally agree with this. However:

Having been to Singapore once before I am certain there are no room police =
patrolling the hotel corridors trying to ascertain what activities the gues=
ts are up to in their own rooms. There were also no personal questions aske=
d at hotel registration as far as I recall ( I am sure I would have remembe=
red that) so I don't see it as an especially hostile environment.=FD I thin=
k the IETF should confirm with the meeting hotels that there will be no iss=
ues in that regard and also a check with the Singapore authorities that the=
re will be no threat to IETF participants because of their orientation or m=
arital status would be a sensible measure.

I=92m sure they didn=92t ask *you* any questions. But you might have gotten=
 some response if you tried to check in with another man into a room that h=
ad just one bed.  I=92m not saying that you would. I don=92t know, having n=
ever been in Singapore, but I can understand that it would be a concern.

Yoav


--_000_2016041006360362833484488910575blackberrycom_
Content-Type: text/html; charset="windows-1256"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dwindows-1=
256">
</head>
<body class=3D"" style=3D"word-wrap:break-word">
<div style=3D"width:100%; font-size:initial; font-family:Calibri,'Slate Pro=
',sans-serif,sans-serif; color:rgb(31,73,125); text-align:initial; backgrou=
nd-color:rgb(255,255,255)">
<br>
</div>
<div style=3D"width:100%; font-size:initial; font-family:Calibri,'Slate Pro=
',sans-serif,sans-serif; color:rgb(31,73,125); text-align:initial; backgrou=
nd-color:rgb(255,255,255)">
That's why I proposed that IETF check with the hotels that this isn't going=
 to be an issue. The other potential issue I foresee which needs checking w=
ith the authorities is if there will be a problem with customs and immigrat=
ion forms with questions regarding
 marital status and number of family members traveling with you.</div>
<div style=3D"width:100%; font-size:initial; font-family:Calibri,'Slate Pro=
',sans-serif,sans-serif; color:rgb(31,73,125); text-align:initial; backgrou=
nd-color:rgb(255,255,255)">
<br style=3D"display:initial">
</div>
<div style=3D"font-size:initial; font-family:Calibri,'Slate Pro',sans-serif=
,sans-serif; color:rgb(31,73,125); text-align:initial; background-color:rgb=
(255,255,255)">
Sent&nbsp;from&nbsp;my&nbsp;BlackBerry&nbsp;10&nbsp;smartphone.</div>
<table width=3D"100%" style=3D"background-color:white; border-spacing:0px">
<tbody>
<tr>
<td colspan=3D"2" style=3D"font-size:initial; text-align:initial; backgroun=
d-color:rgb(255,255,255)">
<div style=3D"border-style:solid none none; border-top-color:rgb(181,196,22=
3); border-top-width:1pt; padding:3pt 0in 0in; font-family:Tahoma,'BB Alpha=
 Sans','Slate Pro'; font-size:10pt">
<div><b>From: </b>Yoav Nir</div>
<div><b>Sent: </b>Saturday, April 9, 2016 18:15</div>
<div><b>To: </b>Andrew Allen</div>
<div><b>Cc: </b>David Conrad; Dhruv Dhody; ietf@ietf.org Discussion</div>
<div><b>Subject: </b>Re: Concerns about Singapore</div>
</div>
</td>
</tr>
</tbody>
</table>
<div style=3D"border-style:solid none none; border-top-color:rgb(186,188,20=
9); border-top-width:1pt; font-size:initial; text-align:initial; background=
-color:rgb(255,255,255)">
</div>
<br>
<div>Hi, Andrew
<div class=3D""><br class=3D"">
</div>
<div class=3D""><br class=3D"">
</div>
<div class=3D"">
<blockquote type=3D"cite" class=3D"">
<div class=3D"" lang=3D"en-US" style=3D"background-color:rgb(255,255,255); =
line-height:initial">
<div class=3D"" style=3D"width:1222px; font-size:initial; font-family:Calib=
ri,'Slate Pro',sans-serif,sans-serif; color:rgb(31,73,125); text-align:init=
ial">
I don't think the IETF should boycott locations just because the community =
doesn't like some of the laws of that country or aspects of that countries =
governments policies=FD. &nbsp;That is a very slippery slope that could sig=
nificantly reduce the number of possible
 meeting locations and also distract from the IETF mission.</div>
</div>
</blockquote>
<div class=3D""><br class=3D"">
</div>
I generally agree with this. However:</div>
<div class=3D""><br class=3D"">
</div>
<div class=3D"">
<blockquote type=3D"cite" class=3D"">
<div class=3D"" lang=3D"en-US" style=3D"background-color:rgb(255,255,255); =
line-height:initial">
<div class=3D"" style=3D"width:1222px; font-size:initial; font-family:Calib=
ri,'Slate Pro',sans-serif,sans-serif; color:rgb(31,73,125); text-align:init=
ial">
Having been to Singapore once before I am certain there are no room police =
patrolling the hotel corridors trying to ascertain what activities the gues=
ts are up to in their own rooms. There were also no personal questions aske=
d at hotel registration as far as
 I recall ( I am sure I would have remembered that) so I don't see it as an=
 especially hostile environment.=FD I think the IETF should confirm with th=
e meeting hotels that there will be no issues in that regard and also a che=
ck with the Singapore authorities
 that there will be no threat to IETF participants because of their orienta=
tion or marital status would be a sensible measure.</div>
</div>
</blockquote>
<div class=3D""><br class=3D"">
</div>
I=92m sure they didn=92t ask *you* any questions. But you might have gotten=
 some response if you tried to check in with another man into a room that h=
ad just one bed. &nbsp;I=92m not saying that you would. I don=92t know, hav=
ing never been in Singapore, but I can understand
 that it would be a concern.&nbsp;<br class=3D"">
<br class=3D"">
Yoav</div>
<div class=3D""><br class=3D"">
</div>
</div>
</body>
</html>

--_000_2016041006360362833484488910575blackberrycom_--


From nobody Sun Apr 10 03:42:12 2016
Return-Path: <leifj@mnt.se>
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 4ADC512B067 for <ietf@ietfa.amsl.com>; Sun, 10 Apr 2016 03:42:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mnt-se.20150623.gappssmtp.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 OF6CQlW__1YP for <ietf@ietfa.amsl.com>; Sun, 10 Apr 2016 03:42:09 -0700 (PDT)
Received: from mail-lf0-x229.google.com (mail-lf0-x229.google.com [IPv6:2a00:1450:4010:c07::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 5976312B04A for <ietf@ietf.org>; Sun, 10 Apr 2016 03:42:09 -0700 (PDT)
Received: by mail-lf0-x229.google.com with SMTP id c126so123726491lfb.2 for <ietf@ietf.org>; Sun, 10 Apr 2016 03:42:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mnt-se.20150623.gappssmtp.com; s=20150623; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=deWTneOcYWE6317mKJD0gjdXw8MWmkmAXDi3P/1xNoE=; b=heJT6yza1fzM/qf8eYoxmPsJBGRrTOchjsrVumiQTogv226AlFfHxKTxYpvP53JO+k WUEcvhyRfSBdZH+TAECqTYb9sX7baa+elPEv8N7QzJtNSAjqNhNaj2v8Vnk3WD6CYVjE 4tkpHAMcR0fNaGHA8FnJHB5bZJjwMr8pWeVibm84dOnEyTAJpDYmQBQ1OGGoQUAQU1uz 6aHIugdpnwiVxEaK44G4CsdTyeuzhgKIl+0ehW7aF6JK7BI48dTrK2Z/M2yBS6h14dNT WRA7jdqc+CLvL5sQZSDoKmpQ492XTmJ5lXQk7suDeyBY17JSeNOygJwO5zGheug6jYyR Xhrg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=deWTneOcYWE6317mKJD0gjdXw8MWmkmAXDi3P/1xNoE=; b=Quw7CiTiy54HsFODYcw4oPNxENZ2KIrURvGBxkoCoPKmylbb+12RI9r7qMibxAQt1I cr6DFEJkOYFMXifn8dee1KmoHo5uBFppbyxmodk4NSmKActprS+wYALzUqLJmguYDdGh bgxLCCdIWxtysqj+DDrxlk50gFldGJ7Pjzzt8sMrMBJ97+40wD0eIoZtCCTIOivDH/Mu eOBMDsfLBStYHODTFRduwIm5tOZppyBw/P5fTy2uKwcvsuq+aRVy5EnMJaR8czY4Vg60 PkiX/5zgPRRFliPvSTQ/Ed8kfTLWjh7X+g0kPyv+BuonY7uHMUgNnfHt8QuBFkfR0E4R TPyg==
X-Gm-Message-State: AD7BkJI4pM7S7ydFLGjnMAmJ5dKqk/oW/RFpWg4c6yOMfCLnyvFK05pNdfkrHp1fOPkvdA==
X-Received: by 10.25.165.20 with SMTP id o20mr6717598lfe.105.1460284927504; Sun, 10 Apr 2016 03:42:07 -0700 (PDT)
Received: from [10.0.0.139] (tb62-102-145-131.cust.teknikbyran.com. [62.102.145.131]) by smtp.gmail.com with ESMTPSA id um4sm3538997lbb.1.2016.04.10.03.42.05 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 10 Apr 2016 03:42:06 -0700 (PDT)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (1.0)
Subject: Re: Concerns about Singapore
From: Leif Johansson <leifj@mnt.se>
X-Mailer: iPhone Mail (13E234)
In-Reply-To: <m2fuuu75ls.wl%randy@psg.com>
Date: Sun, 10 Apr 2016 12:42:05 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <A74EB3D5-20E5-4788-9B49-93D31AE1382F@mnt.se>
References: <0D914666-C3D4-4CCE-AD5E-4E5B34EA1A73@piuha.net> <20160407182936.GA21340@pfrc.org> <CAB75xn780nNDjGa_Cc222J20-+1CCHt09Xp8KHzaK=n0xx51pg@mail.gmail.com> <5706B100.9040509@mnt.se> <CAB75xn6fmj84ROUtG5eUB3GerHx83hrEr3w5vSADY_g=BRg5FA@mail.gmail.com> <5706BA40.3060005@mnt.se> <alpine.DEB.2.02.1604072157240.31096@uplift.swm.pp.se> <A9B63A6D-3102-482F-8FFC-2E57A5FD8336@nic.cz> <16925.1460122349@obiwan.sandelman.ca> <m27fg77zst.wl%randy@psg.com> <57097077.7040703@comcast.net> <m2fuuu75ls.wl%randy@psg.com>
To: Randy Bush <randy@psg.com>
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/u2R6jV_RdpmFJdgMuCkFoCo95SY>
Cc: 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: Sun, 10 Apr 2016 10:42:11 -0000

Skickat fr=C3=A5n min iPhone

10 apr. 2016 kl. 00:57 skrev Randy Bush <randy@psg.com>:

>> Calling the Beijing meeting network open isn't really correct - we had
>> a reverse VPN to the Internet as it exists outside of the PRC.
>=20
> false.  and i was the noc guy working it.
>=20
>> We did registration in Maastricht simply to figure out the details
>> before we got to Beijing - I'm fairly confident that Maastricht
>> wouldn't have been different from the previous IETF's without the
>> upcoming Beijing meeting.
>=20
> correct, but misleading.  maastrict was the same as beijing, though for
> different reasons.

That was the VAT issue, right?
>=20
> randy
>=20


From nobody Sun Apr 10 06:12:22 2016
Return-Path: <nalini.elkins@insidethestack.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 DE9C912D573 for <ietf@ietfa.amsl.com>; Sun, 10 Apr 2016 06:12:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.62
X-Spam-Level: 
X-Spam-Status: No, score=-2.62 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=yahoo.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 Xm9ei0d4MFhv for <ietf@ietfa.amsl.com>; Sun, 10 Apr 2016 06:12:19 -0700 (PDT)
Received: from nm32-vm3.bullet.mail.ne1.yahoo.com (nm32-vm3.bullet.mail.ne1.yahoo.com [98.138.229.51]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1939F12D569 for <ietf@ietf.org>; Sun, 10 Apr 2016 06:12:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1460293938; bh=f9UKWg6Eg2WBIkp/YU42HlES2A8vdbbFQVVzQbtwFzU=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:From:Subject; b=fczdg4PUnfP7JC8g5dW5OIhzc2i8nCO4jse+UMHah7MTKZV/BN8PRYQKaKZC1aTSGglSdEpgev/32La/4N0MFSrNVIAcW01kojoNXoSDQC0apR7ES/ZpGkqQDfBD8rKRGKANjha8XbeXyGQvbejMAxZtWDgf3lgO0UoeS/492rVlODC2GSNVgJanWVXnw07JigtTJ3CRqlSrlRfRPVJkcXyJc19kEoQ81NeDZzBOtT7M9iI/0g41SafTWbA7F5pdjl6aLlEY2gukSSRUBHk623yd4mhrWHOQhfYHFHVZF1BhIvDs10yFs5q1ml/xo/2xVjKMXUjD5ZKAx/o+rXzrvg==
Received: from [127.0.0.1] by nm32.bullet.mail.ne1.yahoo.com with NNFMP; 10 Apr 2016 13:12:18 -0000
Received: from [98.138.226.177] by nm32.bullet.mail.ne1.yahoo.com with NNFMP;  10 Apr 2016 13:09:25 -0000
Received: from [98.138.89.245] by tm12.bullet.mail.ne1.yahoo.com with NNFMP; 10 Apr 2016 13:09:25 -0000
Received: from [127.0.0.1] by omp1059.mail.ne1.yahoo.com with NNFMP; 10 Apr 2016 13:09:25 -0000
X-Yahoo-Newman-Property: ymail-4
X-Yahoo-Newman-Id: 695364.99873.bm@omp1059.mail.ne1.yahoo.com
X-YMail-OSG: Wp7yJucVM1lah80rDWtOWL_W4dnmTtJEZY0ig.gWeo22ofRzewXy2JBhVOvC_z. OXTK8xfwUWRRE1LpkEWW4tGGSs5UQ3zRCMXIiwryLvV_T.it_fUQPYU_WOsUPYhd58Q9_TzjnDGA 61ptnC1bXC1sPudFEFpGwkJmzsznEY145FUWSo83r9t4lKUTvgHBFNiPAgaMCNcfZEWVkO78Vh1i qTOCNq_v8tEvJ_osYwLwaIvKC523xVzM8Hjsk_l2akPUCCjcNKh.7I5GdMNP4EqRs09CFOf55UI1 .4QAy_V5UcS6WtNi5Bv6qlUrYoV0hBo3oajV.gXJ.OoIrtrrBuf8JWskMmMNU2J2CtdR2DClqbZ. WZkdlJyDMb.MlA1S8Zvax4iKMGMaD7Ywxsb.Da0IfokR._LUKi9RJNl4Z_JyxW7TkBKf0jXM1DbH jIAlaeeeKR_X1GVNNFpFmrbDFVukhli6.fXHEA70qfEeUeOXwEC_DNo7bwAdkSs_0UziCPyfVS5_ 1SPrFFaig8OFQMQLHJzLJf2oro1FL4A--
Received: by 98.138.105.197; Sun, 10 Apr 2016 13:09:25 +0000 
Date: Sun, 10 Apr 2016 13:08:37 +0000 (UTC)
From: <nalini.elkins@insidethestack.com>
To: Andrew Allen <aallen@blackberry.com>, Yoav Nir <ynir.ietf@gmail.com>
Message-ID: <459690655.171220.1460293717474.JavaMail.yahoo@mail.yahoo.com>
In-Reply-To: <20160410063603.6283348.44889.10575@blackberry.com>
References: <20160410063603.6283348.44889.10575@blackberry.com>
Subject: Re: Concerns about Singapore
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/NTuPFMrQnCARzOMQ348IWfiPFdc>
Cc: "ietf@ietf.org Discussion" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: nalini.elkins@insidethestack.com
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: Sun, 10 Apr 2016 13:12:21 -0000

>>Having been to Singapore once before I am certain there are no room polic=
e patrolling the hotel corridors trying to ascertain what activities the gu=
ests are up to in their own rooms. There were also >>no personal questions =
asked at hotel registration as far as I recall ( I am sure I would have rem=
embered that) so I don't see it as an especially hostile environment.=E2=80=
=8E I think the IETF should confirm >>with the meeting hotels that there wi=
ll be no issues in that regard and also a check with the Singapore authorit=
ies that there will be no threat to IETF participants because of their orie=
ntation or >>marital status would be a sensible measure.


>I=E2=80=99m sure they didn=E2=80=99t ask *you* any questions. But you migh=
t have gotten some response if you tried to check in with another man into =
a room that had just one bed.  I=E2=80=99m not saying that you would. I >do=
n=E2=80=99t know, having never been in Singapore, but I can understand that=
 it would be a concern.=20
=20
Guys, believe me, I am not for discrimination in any form whatsoever and of=
 course, it is wonderful if IETFers want to bring their family with them to=
 locations but isn't it more important for the IETFer themselves to attend =
and to not be harassed?   Does IETF need to plan for not just attendees but=
 attendee's families?


A lot of us have never said anything but people might want to read the sect=
ion that is in Wikipedia on "White Privilege".=20
https://en.wikipedia.org/wiki/White_privilege

This might help put a different perspective on this discussion.

I know at least one participant at IETF95 who was searched multiple times a=
t the same airport because his skin was brown and we suspect that he was pr=
ofiled.  You may look at compilations which have rank countries by racist a=
ttitudes and in some, the United States comes in first.

But, you do not hear us talking about this or even complaining or suggestin=
g that we are getting an unfair deal.  We just work harder and try to suppo=
rt each other.

And, this kind of thing - getting hassled, ignored in restaurants, possibly=
 physically assaulted if we are in the wrong area, etc.etc. is for IETF par=
ticipants.  Not, IETFer's bringing their families - which I will add is not=
 an option for many in the developing world because it is far too expensive=
.  It is hard enough for the IETFer himself / herself to attend - much less=
 bring their family.

Don't get me wrong, I am definitely not saying that discrimination against =
our LGBT brothers & sisters is to be discounted.  There is a young gay man =
who grew up with my daughter who is like a son to me & even in the very lib=
eral environment of Berkeley, California, there are issues with him being o=
penly gay.  Just as there are issues with me being a woman of color.

No one has an exclusive on being treated badly.  Unfortunately.

Let's try to work with each other and support each other to bring the colla=
borative attitudes and openness that underlie the Internet and the openness=
 of the IETF to the developing world.  I think that we are agents of change=
 just as the Internet is an agent of change.  Unfortunately, sometimes, the=
re are costs to be borne for this.  We need to look at the greater good.

Just my 2 cents.

Thanks,
Nalini


From nobody Sun Apr 10 06:38:46 2016
Return-Path: <chopps@chopps.org>
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 1CF9B12D592 for <ietf@ietfa.amsl.com>; Sun, 10 Apr 2016 06:38:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.896
X-Spam-Level: 
X-Spam-Status: No, score=-2.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.996] 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 PpufqOVMATXP for <ietf@ietfa.amsl.com>; Sun, 10 Apr 2016 06:38:43 -0700 (PDT)
Received: from smtp.chopps.org (smtp.chopps.org [54.88.81.56]) by ietfa.amsl.com (Postfix) with ESMTP id 33EE912D570 for <ietf@ietf.org>; Sun, 10 Apr 2016 06:38:43 -0700 (PDT)
Received: from tops.chopps.org (24-247-68-31.dhcp.trcy.mi.charter.com [24.247.68.31]) (using TLSv1.2 with cipher AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by smtp.chopps.org (Postfix) with ESMTPSA id 5C73E61176; Sun, 10 Apr 2016 13:38:42 +0000 (UTC)
References: <0D914666-C3D4-4CCE-AD5E-4E5B34EA1A73@piuha.net> <20160407182936.GA21340@pfrc.org> <CAB75xn780nNDjGa_Cc222J20-+1CCHt09Xp8KHzaK=n0xx51pg@mail.gmail.com> <5706B100.9040509@mnt.se> <CAB75xn6fmj84ROUtG5eUB3GerHx83hrEr3w5vSADY_g=BRg5FA@mail.gmail.com> <5706BA40.3060005@mnt.se> <alpine.DEB.2.02.1604072157240.31096@uplift.swm.pp.se> <A9B63A6D-3102-482F-8FFC-2E57A5FD8336@nic.cz> <16925.1460122349@obiwan.sandelman.ca> <m27fg77zst.wl%randy@psg.com> <57097077.7040703@comcast.net> <m2fuuu75ls.wl%randy@psg.com>
User-agent: mu4e 0.9.16; emacs 24.5.1
From: <chopps@chopps.org>
To: Randy Bush <randy@psg.com>
Subject: Re: Concerns about Singapore
In-reply-to: <m2fuuu75ls.wl%randy@psg.com>
Date: Sun, 10 Apr 2016 09:38:41 -0400
Message-ID: <87wpo5a8im.fsf@tops.chopps.org>
MIME-Version: 1.0
Content-Type: text/plain
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/lHl6CCkCSASbYG85T-5RTNtZrfg>
Cc: 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: Sun, 10 Apr 2016 13:38:44 -0000

Randy Bush <randy@psg.com> writes:

>> Calling the Beijing meeting network open isn't really correct - we had
>> a reverse VPN to the Internet as it exists outside of the PRC.
>
> false.  and i was the noc guy working it.

I'm curious how it was different. I was certainly was under the
impression that IETF was treated differently than the general populous,
making some/most people OK with the meeting being held there.

Thanks,
Chris.


From nobody Sun Apr 10 06:56:24 2016
Return-Path: <randy@psg.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 8B47512D5A4 for <ietf@ietfa.amsl.com>; Sun, 10 Apr 2016 06:56:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.896
X-Spam-Level: 
X-Spam-Status: No, score=-7.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.996] 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 v8X895LyHN4H for <ietf@ietfa.amsl.com>; Sun, 10 Apr 2016 06:56:22 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6C26A12D598 for <ietf@ietf.org>; Sun, 10 Apr 2016 06:56:22 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com) by ran.psg.com with esmtp (Exim 4.82) (envelope-from <randy@psg.com>) id 1apFqe-00036s-6O; Sun, 10 Apr 2016 13:56:20 +0000
Date: Sun, 10 Apr 2016 08:56:17 -0500
Message-ID: <m260vp7eke.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Christian Hopps <chopps@chopps.org>
Subject: Re: Concerns about Singapore
In-Reply-To: <87wpo5a8im.fsf@tops.chopps.org>
References: <0D914666-C3D4-4CCE-AD5E-4E5B34EA1A73@piuha.net> <20160407182936.GA21340@pfrc.org> <CAB75xn780nNDjGa_Cc222J20-+1CCHt09Xp8KHzaK=n0xx51pg@mail.gmail.com> <5706B100.9040509@mnt.se> <CAB75xn6fmj84ROUtG5eUB3GerHx83hrEr3w5vSADY_g=BRg5FA@mail.gmail.com> <5706BA40.3060005@mnt.se> <alpine.DEB.2.02.1604072157240.31096@uplift.swm.pp.se> <A9B63A6D-3102-482F-8FFC-2E57A5FD8336@nic.cz> <16925.1460122349@obiwan.sandelman.ca> <m27fg77zst.wl%randy@psg.com> <57097077.7040703@comcast.net> <m2fuuu75ls.wl%randy@psg.com> <87wpo5a8im.fsf@tops.chopps.org>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/Ywk1vkE26XuA1UqDlMfDg-MeF3g>
Cc: IETF Disgust List <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: Sun, 10 Apr 2016 13:56:23 -0000

>>> Calling the Beijing meeting network open isn't really correct - we had
>>> a reverse VPN to the Internet as it exists outside of the PRC.
>>
>> false.  and i was the noc guy working it.
> 
> I'm curious how it was different. I was certainly was under the
> impression that IETF was treated differently than the general
> populous, making some/most people OK with the meeting being held
> there.

it was clean unfettered Internet.  some local folk stuck their necks out
very far to accomplish this.  it was definitely different than one got
outside of the ietf meeting network.  this has been a condition placed
on hosts and beijing was no exception.  

there were a few gl!tches, as there always are, but they were debugged.
ticket history is the only PII data pile we do not delete at the end of
the meeting, so we may be able to see if mike actually had a ticket and
if it was fixed.

the noc does occasionally discuss that it might be interesting for us to
experience the local internet policies, bandwidth, etc.; a little
reality therapy.  at the dubai ripe meeting, one could not reach
facebook et alia.  is that a major loss?  did riparians learn from it?
would it prevent ietfers to get useful work done?  [ an amusing side
note is that such sites are available in riyadh, which we consider a
much more conservative city. ]

btw, all traffic in and out of singapore, voice and data, has been spied
upon at the most intimate and detailed level for a very long time.
luckily the usa, land of the free, is ..., oh wait.

randy


From nobody Sun Apr 10 07:34:19 2016
Return-Path: <mstjohns@comcast.net>
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 4730D12D5A0 for <ietf@ietfa.amsl.com>; Sun, 10 Apr 2016 07:34:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.696
X-Spam-Level: 
X-Spam-Status: No, score=-3.696 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, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.996, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=comcast.net
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 ImgcU6uphf7q for <ietf@ietfa.amsl.com>; Sun, 10 Apr 2016 07:34:16 -0700 (PDT)
Received: from resqmta-ch2-03v.sys.comcast.net (resqmta-ch2-03v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:35]) (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 2341D12D160 for <ietf@ietf.org>; Sun, 10 Apr 2016 07:34:16 -0700 (PDT)
Received: from resomta-ch2-17v.sys.comcast.net ([69.252.207.113]) by comcast with SMTP id pGRGaIionLCmUpGRLaM1vi; Sun, 10 Apr 2016 14:34:15 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1460298855; bh=7kVaV1NUtoiET/PIzJG3beh0+9IaN3h3WXhBe9TjABs=; h=Received:Received:Subject:To:From:Message-ID:Date:MIME-Version: Content-Type; b=AyFNK7zMRtBpGlEvCfFZKB7bckhZdMbqzUPWMOEWMeyEYa9wY2CWnaZhswE3GU/z/ DHJpml5X4Ww7/5KMWLYDL/Xof5ywLJDWC7700Rn7ptP/9+kOD+YtwSzITRe16X9qo+ 5C2xDMS4PDnHB8w7Kl06h2xx7i4jg/8RVJu2Kw0IDL2qTWnEUC0/yvPBNDSzWuBVgl RiXkagID4qdYPT0gS/Kf82CrDVxY6RSJCNkOMnJBiCGnfDFK0HcicQID00uArjarwB Qo6+lEBUNgG05lTFe1DYH646EvH4ksJQ+wrZvOuizN8JJYtqNrCc8/tX9M+L+r63rl QtJmJ3+OjIdMQ==
Received: from [192.168.1.113] ([69.255.115.150]) by resomta-ch2-17v.sys.comcast.net with comcast id geaE1s00Q3Em2Kp01eaEH5; Sun, 10 Apr 2016 14:34:15 +0000
Subject: Re: Concerns about Singapore
To: Randy Bush <randy@psg.com>, Christian Hopps <chopps@chopps.org>
References: <0D914666-C3D4-4CCE-AD5E-4E5B34EA1A73@piuha.net> <20160407182936.GA21340@pfrc.org> <CAB75xn780nNDjGa_Cc222J20-+1CCHt09Xp8KHzaK=n0xx51pg@mail.gmail.com> <5706B100.9040509@mnt.se> <CAB75xn6fmj84ROUtG5eUB3GerHx83hrEr3w5vSADY_g=BRg5FA@mail.gmail.com> <5706BA40.3060005@mnt.se> <alpine.DEB.2.02.1604072157240.31096@uplift.swm.pp.se> <A9B63A6D-3102-482F-8FFC-2E57A5FD8336@nic.cz> <16925.1460122349@obiwan.sandelman.ca> <m27fg77zst.wl%randy@psg.com> <57097077.7040703@comcast.net> <m2fuuu75ls.wl%randy@psg.com> <87wpo5a8im.fsf@tops.chopps.org> <m260vp7eke.wl%randy@psg.com>
From: Michael StJohns <mstjohns@comcast.net>
Message-ID: <570A6458.3050206@comcast.net>
Date: Sun, 10 Apr 2016 10:34:00 -0400
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.7.1
MIME-Version: 1.0
In-Reply-To: <m260vp7eke.wl%randy@psg.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/dHGIT0t4xeaEaRmYakqdm392FHs>
Cc: IETF Disgust List <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: Sun, 10 Apr 2016 14:34:17 -0000

On 4/10/2016 9:56 AM, Randy Bush wrote:
>> I'm curious how it was different. I was certainly was under the
>> >impression that IETF was treated differently than the general
>> >populous, making some/most people OK with the meeting being held
>> >there.
> it was clean unfettered Internet.  some local folk stuck their necks out
> very far to accomplish this.  it was definitely different than one got
> outside of the ietf meeting network.  this has been a condition placed
> on hosts and beijing was no exception.

This surprises me - "this has been a condition placed on hosts...". 
Could you enlighten us as to which [and I'll try to be precise here] 
other IETFs had a condition where the content accessible by the IETF 
network was markedly different from the content of say the network at a 
local Starbuck's equivalent wifi hot spot just down the street from the 
IETF and where that was mandated by the hosts and/or local laws?  I mean 
besides Beijing?   Key words "markedly different" and "content accessible".

Mike




From nobody Sun Apr 10 07:41:11 2016
Return-Path: <olejacobsen@me.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 2623912B005 for <ietf@ietfa.amsl.com>; Sun, 10 Apr 2016 07:41:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.617
X-Spam-Level: 
X-Spam-Status: No, score=-3.617 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.996, SPF_PASS=-0.001] 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 LSMtLPwIT_RK for <ietf@ietfa.amsl.com>; Sun, 10 Apr 2016 07:41:09 -0700 (PDT)
Received: from mr11p00im-asmtp002.me.com (mr11p00im-asmtp002.me.com [17.110.69.253]) (using TLSv1.2 with cipher DHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 30F9C126D74 for <ietf@ietf.org>; Sun, 10 Apr 2016 07:41:09 -0700 (PDT)
Received: from [10.1.10.8] (173-11-110-134-SFBA.hfc.comcastbusiness.net [173.11.110.134]) by mr11p00im-asmtp002.me.com (Oracle Communications Messaging Server 7.0.5.36.0 64bit (built Sep 8 2015)) with ESMTPSA id <0O5F00EVVA4KH320@mr11p00im-asmtp002.me.com> for ietf@ietf.org; Sun, 10 Apr 2016 14:41:08 +0000 (GMT)
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, definitions=2016-04-10_08:,, signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 clxscore=1015 suspectscore=0 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1510270003 definitions=main-1604100219
Date: Sun, 10 Apr 2016 07:41:08 -0700 (PDT)
From: Ole Jacobsen <olejacobsen@me.com>
To: Michael StJohns <mstjohns@comcast.net>
Subject: Re: Concerns about Singapore
In-reply-to: <570A6458.3050206@comcast.net>
Message-id: <alpine.OSX.2.01.1604100736080.45987@rabdullah.local>
References: <0D914666-C3D4-4CCE-AD5E-4E5B34EA1A73@piuha.net> <20160407182936.GA21340@pfrc.org> <CAB75xn780nNDjGa_Cc222J20-+1CCHt09Xp8KHzaK=n0xx51pg@mail.gmail.com> <5706B100.9040509@mnt.se> <CAB75xn6fmj84ROUtG5eUB3GerHx83hrEr3w5vSADY_g=BRg5FA@mail.gmail.com> <5706BA40.3060005@mnt.se> <alpine.DEB.2.02.1604072157240.31096@uplift.swm.pp.se> <A9B63A6D-3102-482F-8FFC-2E57A5FD8336@nic.cz> <16925.1460122349@obiwan.sandelman.ca> <m27fg77zst.wl%randy@psg.com> <57097077.7040703@comcast.net> <m2fuuu75ls.wl%randy@psg.com> <87wpo5a8im.fsf@tops.chopps.org> <m260vp7eke.wl%randy@psg.com> <570A6458.3050206@comcast.net>
User-Agent: Alpine 2.01 (OSX 1266 2009-07-14)
MIME-version: 1.0
Content-type: TEXT/PLAIN; charset=US-ASCII
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/RFVJID-y2tMs1prRZK663L6SkNM>
Cc: IETF Disgust List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: Ole Jacobsen <olejacobsen@me.com>
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: Sun, 10 Apr 2016 14:41:10 -0000

On Sun, 10 Apr 2016, Michael StJohns wrote:
> 
> This surprises me - "this has been a condition placed on hosts...". Could you
> enlighten us as to which [and I'll try to be precise here] other IETFs had a
> condition where the content accessible by the IETF network was markedly
> different from the content of say the network at a local Starbuck's equivalent
> wifi hot spot just down the street from the IETF and where that was mandated
> by the hosts and/or local laws?  I mean besides Beijing?   Key words "markedly
> different" and "content accessible".
> 
> Mike
> 

The IETF has a meeting network requirements document that specifies a 
number of parameters which includes no blocking. Markedly different in
terms of content may not apply in most places, reasonable bandwidth 
most certainly does, as does port restrictions (usually by stupid 
configuration by clueless operators). And if you've ever stayed in 
some random hotel you will know what I mean.

Ole


From nobody Sun Apr 10 07:45:59 2016
Return-Path: <randy@psg.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 EA74E12D5CD for <ietf@ietfa.amsl.com>; Sun, 10 Apr 2016 07:45:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.896
X-Spam-Level: 
X-Spam-Status: No, score=-7.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.996] 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 gDCiZOXhtZ3C for <ietf@ietfa.amsl.com>; Sun, 10 Apr 2016 07:45:56 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E522312B028 for <ietf@ietf.org>; Sun, 10 Apr 2016 07:45:54 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com) by ran.psg.com with esmtp (Exim 4.82) (envelope-from <randy@psg.com>) id 1apGcb-0003Gb-3X; Sun, 10 Apr 2016 14:45:53 +0000
Date: Sun, 10 Apr 2016 09:45:50 -0500
Message-ID: <m21t6d7c9t.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Michael StJohns <mstjohns@comcast.net>
Subject: Re: Concerns about Singapore
In-Reply-To: <570A6458.3050206@comcast.net>
References: <0D914666-C3D4-4CCE-AD5E-4E5B34EA1A73@piuha.net> <20160407182936.GA21340@pfrc.org> <CAB75xn780nNDjGa_Cc222J20-+1CCHt09Xp8KHzaK=n0xx51pg@mail.gmail.com> <5706B100.9040509@mnt.se> <CAB75xn6fmj84ROUtG5eUB3GerHx83hrEr3w5vSADY_g=BRg5FA@mail.gmail.com> <5706BA40.3060005@mnt.se> <alpine.DEB.2.02.1604072157240.31096@uplift.swm.pp.se> <A9B63A6D-3102-482F-8FFC-2E57A5FD8336@nic.cz> <16925.1460122349@obiwan.sandelman.ca> <m27fg77zst.wl%randy@psg.com> <57097077.7040703@comcast.net> <m2fuuu75ls.wl%randy@psg.com> <87wpo5a8im.fsf@tops.chopps.org> <m260vp7eke.wl%randy@psg.com> <570A6458.3050206@comcast.net>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/NOjXXTuT4cpyp8fnyqtiB15O7P0>
Cc: IETF Disgust List <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: Sun, 10 Apr 2016 14:45:58 -0000

>> it was clean unfettered Internet.  some local folk stuck their necks out
>> very far to accomplish this.  it was definitely different than one got
>> outside of the ietf meeting network.  this has been a condition placed
>> on hosts and beijing was no exception.
> 
> This surprises me - "this has been a condition placed on hosts...". 

it was even in the hour of embarrassing babble fred used to prevent
people from talking about real problems at the bof

> Could you enlighten us as to which [and I'll try to be precise here]
> other IETFs had a condition where the content accessible by the IETF
> network was markedly different from the content of say the network at
> a local Starbuck's equivalent wifi hot spot just down the street from
> the IETF and where that was mandated by the hosts and/or local laws?
> I mean besides Beijing?  Key words "markedly different" and "content
> accessible".

we don't specify it's 'different'.  among other silly distractions, it
would require a 'different from precisely what and in what ways?'

we simply specifiy open and unfettered

rndy


From nobody Sun Apr 10 07:48:17 2016
Return-Path: <mstjohns@comcast.net>
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 BDF1B12D5CD for <ietf@ietfa.amsl.com>; Sun, 10 Apr 2016 07:48:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.696
X-Spam-Level: 
X-Spam-Status: No, score=-3.696 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, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.996, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=comcast.net
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 35QfqlQL8XPH for <ietf@ietfa.amsl.com>; Sun, 10 Apr 2016 07:48:14 -0700 (PDT)
Received: from resqmta-ch2-09v.sys.comcast.net (resqmta-ch2-09v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:41]) (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 739E212D5A0 for <ietf@ietf.org>; Sun, 10 Apr 2016 07:48:14 -0700 (PDT)
Received: from resomta-ch2-01v.sys.comcast.net ([69.252.207.97]) by comcast with SMTP id pGeYaamYVO4QFpGera49rS; Sun, 10 Apr 2016 14:48:13 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1460299693; bh=cVYnyahunTZ20j6Gub5jKMWMqhLS5n5U8k+FJgE1eGs=; h=Received:Received:Subject:To:From:Message-ID:Date:MIME-Version: Content-Type; b=SLDiNoQ8nJHtN7mrqGUStL7bE6mDXsN7Pk3Lo3KBVVnGCP3plzSf7EIcnf3RA03PJ KF2Vas9T1iiXALjCh890mHSWgpGndtnwOC+aUj2qahOIvMoSN/y6LWOVT8eEnlNygJ aAg6/sD+1ZQZ686WZOE0wJitfsuiVh3WTQy9svkuVWjexycaQHq1AKwvwyDimkAKwk 0QcJSDqEWk0ptErDLlsl5ucA9S/W4aUkILNK9hPtgE/ZKBAvDBSmkrVXgsEqwmoKNo dr25NzmgTP24xOmzv0DkpEJ6WPrCZw5TR4T7VKAWrM3RCFoRj6BA4XONHYP8SWNPCy o+yAPp1iiC+Sw==
Received: from [192.168.1.113] ([69.255.115.150]) by resomta-ch2-01v.sys.comcast.net with comcast id geoD1s00D3Em2Kp01eoDi8; Sun, 10 Apr 2016 14:48:13 +0000
Subject: Re: Concerns about Singapore
To: Randy Bush <randy@psg.com>
References: <0D914666-C3D4-4CCE-AD5E-4E5B34EA1A73@piuha.net> <20160407182936.GA21340@pfrc.org> <CAB75xn780nNDjGa_Cc222J20-+1CCHt09Xp8KHzaK=n0xx51pg@mail.gmail.com> <5706B100.9040509@mnt.se> <CAB75xn6fmj84ROUtG5eUB3GerHx83hrEr3w5vSADY_g=BRg5FA@mail.gmail.com> <5706BA40.3060005@mnt.se> <alpine.DEB.2.02.1604072157240.31096@uplift.swm.pp.se> <A9B63A6D-3102-482F-8FFC-2E57A5FD8336@nic.cz> <16925.1460122349@obiwan.sandelman.ca> <m27fg77zst.wl%randy@psg.com> <57097077.7040703@comcast.net> <m2fuuu75ls.wl%randy@psg.com> <87wpo5a8im.fsf@tops.chopps.org> <m260vp7eke.wl%randy@psg.com> <570A6458.3050206@comcast.net> <m21t6d7c9t.wl%randy@psg.com>
From: Michael StJohns <mstjohns@comcast.net>
Message-ID: <570A67B4.3010206@comcast.net>
Date: Sun, 10 Apr 2016 10:48:20 -0400
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.7.1
MIME-Version: 1.0
In-Reply-To: <m21t6d7c9t.wl%randy@psg.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/KZB8bwfBxHVT4DMthnsVFlxcPaA>
Cc: IETF Disgust List <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: Sun, 10 Apr 2016 14:48:15 -0000

On 4/10/2016 10:45 AM, Randy Bush wrote:
>>> it was clean unfettered Internet.  some local folk stuck their necks out
>>> very far to accomplish this.  it was definitely different than one got
>>> outside of the ietf meeting network.  this has been a condition placed
>>> on hosts and beijing was no exception.
>> This surprises me - "this has been a condition placed on hosts...".
> it was even in the hour of embarrassing babble fred used to prevent
> people from talking about real problems at the bof
>
>> Could you enlighten us as to which [and I'll try to be precise here]
>> other IETFs had a condition where the content accessible by the IETF
>> network was markedly different from the content of say the network at
>> a local Starbuck's equivalent wifi hot spot just down the street from
>> the IETF and where that was mandated by the hosts and/or local laws?
>> I mean besides Beijing?  Key words "markedly different" and "content
>> accessible".
> we don't specify it's 'different'.  among other silly distractions, it
> would require a 'different from precisely what and in what ways?'
>
> we simply specifiy open and unfettered

I repeat - "where" have the local hosts/laws specified conditions that 
resulted in the IETF network content access being markedly different 
than that accessible to the random local citizen?


>
> rndy


From nobody Sun Apr 10 07:50:44 2016
Return-Path: <dhc@dcrocker.net>
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 9A0DA12B00E for <ietf@ietfa.amsl.com>; Sun, 10 Apr 2016 07:50:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] 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 OJ9IUBITm_5Q for <ietf@ietfa.amsl.com>; Sun, 10 Apr 2016 07:50:41 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7A6E8126D74 for <ietf@ietf.org>; Sun, 10 Apr 2016 07:50:41 -0700 (PDT)
Received: from [192.168.1.168] (76-218-10-206.lightspeed.sntcca.sbcglobal.net [76.218.10.206]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id u3AEoeoA028118 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT) for <ietf@ietf.org>; Sun, 10 Apr 2016 07:50:41 -0700
Subject: Re: Concerns about Singapore
References: <0D914666-C3D4-4CCE-AD5E-4E5B34EA1A73@piuha.net> <20160407182936.GA21340@pfrc.org> <CAB75xn780nNDjGa_Cc222J20-+1CCHt09Xp8KHzaK=n0xx51pg@mail.gmail.com> <5706B100.9040509@mnt.se> <CAB75xn6fmj84ROUtG5eUB3GerHx83hrEr3w5vSADY_g=BRg5FA@mail.gmail.com> <5706BA40.3060005@mnt.se> <alpine.DEB.2.02.1604072157240.31096@uplift.swm.pp.se> <A9B63A6D-3102-482F-8FFC-2E57A5FD8336@nic.cz> <16925.1460122349@obiwan.sandelman.ca> <m27fg77zst.wl%randy@psg.com> <57097077.7040703@comcast.net> <m2fuuu75ls.wl%randy@psg.com> <87wpo5a8im.fsf@tops.chopps.org> <m260vp7eke.wl%randy@psg.com> <570A6458.3050206@comcast.net>
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
To: IETF Discussion <ietf@ietf.org>
Message-ID: <570A683C.8030508@dcrocker.net>
Date: Sun, 10 Apr 2016 07:50:36 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2
MIME-Version: 1.0
In-Reply-To: <570A6458.3050206@comcast.net>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Sun, 10 Apr 2016 07:50:41 -0700 (PDT)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/C2EhPuKfU8MY9XwsdX_8LcAK0N8>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: dcrocker@bbiw.net
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: Sun, 10 Apr 2016 14:50:42 -0000

> This surprises me - "this has been a condition placed on hosts...".
> Could you enlighten us as to which [and I'll try to be precise here]
> other IETFs had a condition where the content accessible by the IETF
> network was markedly different from the content of say the network at a
> local Starbuck's equivalent wifi hot spot just down the street from the
> IETF and where that was mandated by the hosts and/or local laws?


A basic issue that seems to distinguish a number of venue concerns is 
whether constraints are state-imposed or are only the choice of the 
local site operator.  Negotiating variations for site-imposed 
constraints is fundamentally different and fundamentally more 
problematic (or impossible) than for state-imposed ones.

As far as I'm aware, Beijing has been the only venue where Internet 
access issues ran into state-imposed restrictions.

If I've heard folk correctly, that distinction seems to be the essence 
of what is being expressed against Singapore.

d/


-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net


From nobody Sun Apr 10 08:01:15 2016
Return-Path: <spencerdawkins.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 0C08012D1D8 for <ietf@ietfa.amsl.com>; Sun, 10 Apr 2016 08:01:14 -0700 (PDT)
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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 BNrvxNrgrdG2 for <ietf@ietfa.amsl.com>; Sun, 10 Apr 2016 08:01:12 -0700 (PDT)
Received: from mail-yw0-x230.google.com (mail-yw0-x230.google.com [IPv6:2607:f8b0:4002:c05::230]) (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 AE4B212D1A5 for <ietf@ietf.org>; Sun, 10 Apr 2016 08:01:12 -0700 (PDT)
Received: by mail-yw0-x230.google.com with SMTP id t10so182767694ywa.0 for <ietf@ietf.org>; Sun, 10 Apr 2016 08:01:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=bvXG6/GCR/LSmPGOhvHqIMhJkD3yGII77kvIXIpSIDc=; b=HXGObJ0Ovjy+YzY+xf9dUObouWL9fYq/wgiThqDwly6+mnrfh4Ec2T7hGhHHaJm0Dz 0sw+7OhlSlFzPn/NgztVjMX73VbMVQOrKH0PbT2iHY8r8Ob6o728RadprszpbzcYLXJB kAcwE2u0BPiOzmstQoSzL+S2lUdfy4crdFvY/Z3jJ0zbz+kIfiv8LSrqI+CHtPJkKOQX we7h0DVLRbevwQ7l9OXdD6KULey77tsTTPW31wWrg/J5j5bWMJpDVy9koTjRqx7YVjFq 8lQVJwyvYQRxe/qz3tqFRklkmKE+LaIHXXJzTyGbz9uPc+LaKJ+ZZVhqrJJdq5bziMi3 +NSQ==
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:date :message-id:subject:from:to:cc; bh=bvXG6/GCR/LSmPGOhvHqIMhJkD3yGII77kvIXIpSIDc=; b=KpRYvWuKVErD6ZvErz6KtoCVb9kmdNAd7ci1dDoaF9Yd4if6VyxDCwETPWOLBup1sd DMvT71cs9rkGBEDIBUTmEmw+AUA0DDkkRQTZYTvQP3eAhKLuz25LMJN2a2dY3N4Wa+ek wWaj/ZHMzaOnYvVYnz14OB0bTcCB4IA5divK/tgYBwCV18mLndvYmkVd22MupwDybxiJ 5AUOKjuhNfBBzGhoNbu/AUSjpGoH5ZzqY4+CD9TFwOzu3A6v5OGw6v219URbva+jiA5w UpsXZxR7vY7BUq0IzXqyHkiPFXe4JA/paAWa9SKQwZNqwDZoVHQWnxkpKxK586rc9fXl QMjQ==
X-Gm-Message-State: AD7BkJL1xJagXP3FRonBPRYOsBqO/bdBNaIKI6QZOYFug6G1iO5JjoCPPuwOQD/twI2Y9NyvwJKqviR7JSrZ6Q==
MIME-Version: 1.0
X-Received: by 10.129.2.9 with SMTP id 9mr9862522ywc.78.1460300471894; Sun, 10 Apr 2016 08:01:11 -0700 (PDT)
Received: by 10.37.207.211 with HTTP; Sun, 10 Apr 2016 08:01:11 -0700 (PDT)
Received: by 10.37.207.211 with HTTP; Sun, 10 Apr 2016 08:01:11 -0700 (PDT)
In-Reply-To: <20160410063603.6283348.44889.10575@blackberry.com>
References: <0D914666-C3D4-4CCE-AD5E-4E5B34EA1A73@piuha.net> <20160407182936.GA21340@pfrc.org> <CAB75xn780nNDjGa_Cc222J20-+1CCHt09Xp8KHzaK=n0xx51pg@mail.gmail.com> <5706B100.9040509@mnt.se> <CAB75xn6fmj84ROUtG5eUB3GerHx83hrEr3w5vSADY_g=BRg5FA@mail.gmail.com> <9B723FB0-6B93-4C85-ADD9-D423F873CF08@virtualized.org> <20160409155300.6283348.41255.10529@blackberry.com> <ADC8666A-436C-4AD4-BD48-9277601069F8@gmail.com> <20160410063603.6283348.44889.10575@blackberry.com>
Date: Sun, 10 Apr 2016 12:01:11 -0300
Message-ID: <CAKKJt-cjYe-FgRW9n-Ve7KWPq2ALYUDwQb=nuAHONQFpbGb8Fw@mail.gmail.com>
Subject: Re: Concerns about Singapore
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
To: Andrew Allen <aallen@blackberry.com>
Content-Type: multipart/alternative; boundary=001a1140be12e48b56053022b28a
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/Gk1BziV5ylg4A7gHsBcaE0ZY0ws>
Cc: 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: Sun, 10 Apr 2016 15:01:14 -0000

--001a1140be12e48b56053022b28a
Content-Type: text/plain; charset=UTF-8

This has been a wide-ranging conversation that I've been content to watch
quietly, but Andrew just stepped on the land mine ...

On Apr 10, 2016 01:36, "Andrew Allen" <aallen@blackberry.com> wrote:
>
>
> That's why I proposed that IETF check with the hotels that this isn't
going to be an issue. The other potential issue I foresee which needs
checking with the authorities is if there will be a problem with customs
and immigration forms with questions regarding marital status and number of
family members traveling with you.

Bingo.

I've been coming to the IETF since 1996, and I know a fair number of GLBTQ
IETF participants, but I knew most of them for years, and in a few cases
for more than a decade, before realizing that.

For my GLBTQ friends from the US, it has been relatively recent for most of
them to live their lives openly.

The gay man who automatically came to IETF meetings even ten years ago with
no "paper trail" ten years ago is now much more likely to show up with a
paper train now.

If he shows up with another man with the same last name, the same address
on IDs, each other as emergency contacts on every form that asks for that,
and (for extra credit) one or more kids with the same last name in tow,
it's a lot harder to miss in 2016 than it was in 2006, and at least some of
that is still visible even if he leaves the family at home.

Our friends who were forced to suffer in silence until recently would have
a much more difficult time doing that today, even if they wanted to.

Spencer

--001a1140be12e48b56053022b28a
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<p dir=3D"ltr">This has been a wide-ranging conversation that I&#39;ve been=
 content to watch quietly, but Andrew just stepped on the land mine ...</p>
<p dir=3D"ltr">On Apr 10, 2016 01:36, &quot;Andrew Allen&quot; &lt;<a href=
=3D"mailto:aallen@blackberry.com">aallen@blackberry.com</a>&gt; wrote:<br>
&gt;<br>
&gt;<br>
&gt; That&#39;s why I proposed that IETF check with the hotels that this is=
n&#39;t going to be an issue. The other potential issue I foresee which nee=
ds checking with the authorities is if there will be a problem with customs=
 and immigration forms with questions regarding marital status and number o=
f family members traveling with you.</p>
<p dir=3D"ltr">Bingo.</p>
<p dir=3D"ltr">I&#39;ve been coming to the IETF since 1996, and I know a fa=
ir number of GLBTQ IETF participants, but I knew most of them for years, an=
d in a few cases for more than a decade, before realizing that.</p>
<p dir=3D"ltr">For my GLBTQ friends from the US, it has been relatively rec=
ent for most of them to live their lives openly. </p>
<p dir=3D"ltr">The gay man who automatically came to IETF meetings even ten=
 years ago with no &quot;paper trail&quot; ten years ago is now much more l=
ikely to show up with a paper train now.</p>
<p dir=3D"ltr">If he shows up with another man with the same last name, the=
 same address on IDs, each other as emergency contacts on every form that a=
sks for that, and (for extra credit) one or more kids with the same last na=
me in tow, it&#39;s a lot harder to miss in 2016 than it was in 2006, and a=
t least some of that is still visible even if he leaves the family at home.=
</p>
<p dir=3D"ltr">Our friends who were forced to suffer in silence until recen=
tly would have a much more difficult time doing that today, even if they wa=
nted to.</p>
<p dir=3D"ltr">Spencer</p>

--001a1140be12e48b56053022b28a--


From nobody Sun Apr 10 08:08:23 2016
Return-Path: <olejacobsen@me.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 1081D12D5BF for <ietf@ietfa.amsl.com>; Sun, 10 Apr 2016 08:08:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.596
X-Spam-Level: 
X-Spam-Status: No, score=-3.596 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001, RP_MATCHES_RCVD=-0.996, SPF_PASS=-0.001] 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 iEpARnxovSon for <ietf@ietfa.amsl.com>; Sun, 10 Apr 2016 08:08:20 -0700 (PDT)
Received: from st11p02im-asmtp002.me.com (st11p02im-asmtp002.me.com [17.172.220.114]) (using TLSv1.2 with cipher DHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6DD4C12D16C for <ietf@ietf.org>; Sun, 10 Apr 2016 08:08:20 -0700 (PDT)
Received: from [31.133.164.144] (dhcp-a490.meeting.ietf.org [31.133.164.144]) by st11p02im-asmtp002.me.com (Oracle Communications Messaging Server 7.0.5.36.0 64bit (built Sep 8 2015)) with ESMTPSA id <0O5F009A9BDSA710@st11p02im-asmtp002.me.com> for ietf@ietf.org; Sun, 10 Apr 2016 15:08:19 +0000 (GMT)
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, definitions=2016-04-10_08:,, signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 clxscore=1015 suspectscore=0 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1510270003 definitions=main-1604100226
Content-type: multipart/alternative; boundary=Apple-Mail-131EC800-0DE7-4D34-B88F-6C9506008312
MIME-version: 1.0 (1.0)
Subject: Re: Concerns about Singapore
From: Ole Jacobsen <olejacobsen@me.com>
X-Mailer: iPhone Mail (13E238)
In-reply-to: <CAKKJt-cjYe-FgRW9n-Ve7KWPq2ALYUDwQb=nuAHONQFpbGb8Fw@mail.gmail.com>
Date: Sun, 10 Apr 2016 12:08:16 -0300
Content-transfer-encoding: 7bit
Message-id: <BE6114E3-5CFA-4416-8C36-DB05B0239F18@me.com>
References: <0D914666-C3D4-4CCE-AD5E-4E5B34EA1A73@piuha.net> <20160407182936.GA21340@pfrc.org> <CAB75xn780nNDjGa_Cc222J20-+1CCHt09Xp8KHzaK=n0xx51pg@mail.gmail.com> <5706B100.9040509@mnt.se> <CAB75xn6fmj84ROUtG5eUB3GerHx83hrEr3w5vSADY_g=BRg5FA@mail.gmail.com> <9B723FB0-6B93-4C85-ADD9-D423F873CF08@virtualized.org> <20160409155300.6283348.41255.10529@blackberry.com> <ADC8666A-436C-4AD4-BD48-9277601069F8@gmail.com> <20160410063603.6283348.44889.10575@blackberry.com> <CAKKJt-cjYe-FgRW9n-Ve7KWPq2ALYUDwQb=nuAHONQFpbGb8Fw@mail.gmail.com>
To: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/_3gjljS5g1VMP0N7OW7-WEIXBUg>
Cc: 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: Sun, 10 Apr 2016 15:08:22 -0000

--Apple-Mail-131EC800-0DE7-4D34-B88F-6C9506008312
Content-Type: text/plain;
	charset=us-ascii
Content-Transfer-Encoding: quoted-printable

Please rest assured that we are gathering information on precisely these iss=
ues!

Ole J. Jacobsen
Editor & Publisher
The Internet Protocol Journal
Cell: +1 415 370-4628
docomo: (090) 3337 9311
http://protocoljournal.org

Sent from my iPhone

> On Apr 10, 2016, at 12:01, Spencer Dawkins at IETF <spencerdawkins.ietf@gm=
ail.com> wrote:
>=20
> This has been a wide-ranging conversation that I've been content to watch q=
uietly, but Andrew just stepped on the land mine ...
>=20
> On Apr 10, 2016 01:36, "Andrew Allen" <aallen@blackberry.com> wrote:
> >
> >
> > That's why I proposed that IETF check with the hotels that this isn't go=
ing to be an issue. The other potential issue I foresee which needs checking=
 with the authorities is if there will be a problem with customs and immigra=
tion forms with questions regarding marital status and number of family memb=
ers traveling with you.
>=20
> Bingo.
>=20
> I've been coming to the IETF since 1996, and I know a fair number of GLBTQ=
 IETF participants, but I knew most of them for years, and in a few cases fo=
r more than a decade, before realizing that.
>=20
> For my GLBTQ friends from the US, it has been relatively recent for most o=
f them to live their lives openly.
>=20
> The gay man who automatically came to IETF meetings even ten years ago wit=
h no "paper trail" ten years ago is now much more likely to show up with a p=
aper train now.
>=20
> If he shows up with another man with the same last name, the same address o=
n IDs, each other as emergency contacts on every form that asks for that, an=
d (for extra credit) one or more kids with the same last name in tow, it's a=
 lot harder to miss in 2016 than it was in 2006, and at least some of that i=
s still visible even if he leaves the family at home.
>=20
> Our friends who were forced to suffer in silence until recently would have=
 a much more difficult time doing that today, even if they wanted to.
>=20
> Spencer

--Apple-Mail-131EC800-0DE7-4D34-B88F-6C9506008312
Content-Type: text/html;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable

<html><head><meta http-equiv=3D"content-type" content=3D"text/html; charset=3D=
utf-8"></head><body dir=3D"auto"><div>Please rest assured that we are gather=
ing information on precisely these issues!<br><br><div><div style=3D"font-fa=
mily: UICTFontTextStyleBody; font-size: 18px; -webkit-text-size-adjust: auto=
;">Ole J. Jacobsen</div><div style=3D"font-family: UICTFontTextStyleBody; fo=
nt-size: 18px; -webkit-text-size-adjust: auto;">Editor &amp; Publisher</div>=
<div style=3D"font-family: UICTFontTextStyleBody; font-size: 18px; -webkit-t=
ext-size-adjust: auto;">The Internet Protocol Journal</div><div style=3D"fon=
t-family: UICTFontTextStyleBody; font-size: 18px; -webkit-text-size-adjust: a=
uto;">Cell: +1 415 370-4628</div><div style=3D"font-family: UICTFontTextStyl=
eBody; font-size: 18px; -webkit-text-size-adjust: auto;">docomo: (090) 3337 9=
311</div></div><div style=3D"font-family: UICTFontTextStyleBody; font-size: 1=
8px; -webkit-text-size-adjust: auto;"><a href=3D"http://protocoljournal.org"=
>http://protocoljournal.org</a></div><div><br></div>Sent from my iPhone</div=
><div><br>On Apr 10, 2016, at 12:01, Spencer Dawkins at IETF &lt;<a href=3D"=
mailto:spencerdawkins.ietf@gmail.com">spencerdawkins.ietf@gmail.com</a>&gt; w=
rote:<br><br></div><blockquote type=3D"cite"><div><p dir=3D"ltr">This has be=
en a wide-ranging conversation that I've been content to watch quietly, but A=
ndrew just stepped on the land mine ...</p>
<p dir=3D"ltr">On Apr 10, 2016 01:36, "Andrew Allen" &lt;<a href=3D"mailto:a=
allen@blackberry.com">aallen@blackberry.com</a>&gt; wrote:<br>
&gt;<br>
&gt;<br>
&gt; That's why I proposed that IETF check with the hotels that this isn't g=
oing to be an issue. The other potential issue I foresee which needs checkin=
g with the authorities is if there will be a problem with customs and immigr=
ation forms with questions regarding marital status and number of family mem=
bers traveling with you.</p>
<p dir=3D"ltr">Bingo.</p>
<p dir=3D"ltr">I've been coming to the IETF since 1996, and I know a fair nu=
mber of GLBTQ IETF participants, but I knew most of them for years, and in a=
 few cases for more than a decade, before realizing that.</p>
<p dir=3D"ltr">For my GLBTQ friends from the US, it has been relatively rece=
nt for most of them to live their lives openly. </p>
<p dir=3D"ltr">The gay man who automatically came to IETF meetings even ten y=
ears ago with no "paper trail" ten years ago is now much more likely to show=
 up with a paper train now.</p>
<p dir=3D"ltr">If he shows up with another man with the same last name, the s=
ame address on IDs, each other as emergency contacts on every form that asks=
 for that, and (for extra credit) one or more kids with the same last name i=
n tow, it's a lot harder to miss in 2016 than it was in 2006, and at least s=
ome of that is still visible even if he leaves the family at home.</p>
<p dir=3D"ltr">Our friends who were forced to suffer in silence until recent=
ly would have a much more difficult time doing that today, even if they want=
ed to.</p>
<p dir=3D"ltr">Spencer</p>
</div></blockquote></body></html>=

--Apple-Mail-131EC800-0DE7-4D34-B88F-6C9506008312--


From nobody Sun Apr 10 09:43:20 2016
Return-Path: <spencerdawkins.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 7D92C12D51A for <ietf@ietfa.amsl.com>; Sun, 10 Apr 2016 09:43:18 -0700 (PDT)
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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 V_9hLXFW4Bhf for <ietf@ietfa.amsl.com>; Sun, 10 Apr 2016 09:43:16 -0700 (PDT)
Received: from mail-yw0-x231.google.com (mail-yw0-x231.google.com [IPv6:2607:f8b0:4002: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 3EDF212B035 for <ietf@ietf.org>; Sun, 10 Apr 2016 09:43:16 -0700 (PDT)
Received: by mail-yw0-x231.google.com with SMTP id t10so184253689ywa.0 for <ietf@ietf.org>; Sun, 10 Apr 2016 09:43:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=3StXW43i848qq4hvj6l72CYuNdWEpkh+ZWwic5hDG/Y=; b=naYjldRdZWpO0nwJTHuxnuBDkACn2jKoSYsS/hOO2KG0bRhBW+rec+upmLWXtk4/T3 Xwlvr7/05tKmKc8ltK4KRZ5hOYuy28tdTLLpLFtQ7/ws4HRWQfGNwkEYBmLM0nfy7UUr /9ptwXFLTh3P7q5/WwbyUSgYNgm0qqB7G4Qg2CSmde7VIbywb91ycqVcsGNilVzjx7fv A6ROyOBKJDg7khBhDcHHgUpAapwsVsXomnRg8ww85gXpIGrg2RFXN4WiBxkEoE/ZYtYu Jif3w/mAdsIVmwDdvysaAmDtMBUUQ86vq/Q90419z2GzYE8ORLmMVSSAT354Fhwjx3iJ 7w7g==
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:date :message-id:subject:from:to:cc; bh=3StXW43i848qq4hvj6l72CYuNdWEpkh+ZWwic5hDG/Y=; b=B4HYl31MZdqpvXXELUOoIxNw6uNVvS1uPkS+mEwlETHH8DBFJBTrGhVECYJXOg/Udn ZYLOMmJ4OVlDvWItwzcYVY8C+wGUrycr2vr6HVQWDwRd30Ht0nhrDCPk7Kv9tU5dJmOw TikNPUfriRgcj7Sa88GtljwSv8f/um05DuJ4berni4wCc5JPu4VJrFqp8gvGG6d1X/7j MCd6km/1jTlNgk6feIgxSFdWFXRGiYk4IlK5uHF87eujNpf8Sqizgj4V9YhtKhDr4znr RUxpDL7hiw/VgAFlMSF29MFSsuDFQ124szX4tRtWNjx99M6Yc8mw0JzDtYZwdgu89kc7 k8vQ==
X-Gm-Message-State: AD7BkJLI1oPQQwsYcNN2cCcdi4z6alTcPYe9pGFoPUbQwatzPsReNW3/NmxzWqJJnL2b/lf9By5e2COTxst5Lg==
MIME-Version: 1.0
X-Received: by 10.129.94.9 with SMTP id s9mr9177919ywb.307.1460306595398; Sun, 10 Apr 2016 09:43:15 -0700 (PDT)
Received: by 10.37.207.211 with HTTP; Sun, 10 Apr 2016 09:43:15 -0700 (PDT)
Received: by 10.37.207.211 with HTTP; Sun, 10 Apr 2016 09:43:15 -0700 (PDT)
In-Reply-To: <BE6114E3-5CFA-4416-8C36-DB05B0239F18@me.com>
References: <0D914666-C3D4-4CCE-AD5E-4E5B34EA1A73@piuha.net> <20160407182936.GA21340@pfrc.org> <CAB75xn780nNDjGa_Cc222J20-+1CCHt09Xp8KHzaK=n0xx51pg@mail.gmail.com> <5706B100.9040509@mnt.se> <CAB75xn6fmj84ROUtG5eUB3GerHx83hrEr3w5vSADY_g=BRg5FA@mail.gmail.com> <9B723FB0-6B93-4C85-ADD9-D423F873CF08@virtualized.org> <20160409155300.6283348.41255.10529@blackberry.com> <ADC8666A-436C-4AD4-BD48-9277601069F8@gmail.com> <20160410063603.6283348.44889.10575@blackberry.com> <CAKKJt-cjYe-FgRW9n-Ve7KWPq2ALYUDwQb=nuAHONQFpbGb8Fw@mail.gmail.com> <BE6114E3-5CFA-4416-8C36-DB05B0239F18@me.com>
Date: Sun, 10 Apr 2016 13:43:15 -0300
Message-ID: <CAKKJt-fT_A8Nz_=cg=1F6W74qP+96zV4+3GABEU80Pi_CiS7aA@mail.gmail.com>
Subject: Re: Concerns about Singapore
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
To: Ole Jacobsen <olejacobsen@me.com>
Content-Type: multipart/alternative; boundary=001a11491bbae1cfc20530241fcd
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/0zDtO_JSRhDJmNGkpMhK7vlbzmI>
Cc: 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: Sun, 10 Apr 2016 16:43:18 -0000

--001a11491bbae1cfc20530241fcd
Content-Type: text/plain; charset=UTF-8

Hi, Ole,

On Apr 10, 2016 10:08, "Ole Jacobsen" <olejacobsen@me.com> wrote:
>
> Please rest assured that we are gathering information on precisely these
issues!

Oh, I am. I absolutely am.

And happy birthday, I believe?

Spencer

> Ole J. Jacobsen
> Editor & Publisher
> The Internet Protocol Journal
> Cell: +1 415 370-4628
> docomo: (090) 3337 9311
> http://protocoljournal.org
>
> Sent from my iPhone
>
> On Apr 10, 2016, at 12:01, Spencer Dawkins at IETF <
spencerdawkins.ietf@gmail.com> wrote:
>
>> This has been a wide-ranging conversation that I've been content to
watch quietly, but Andrew just stepped on the land mine ...
>>
>> On Apr 10, 2016 01:36, "Andrew Allen" <aallen@blackberry.com> wrote:
>> >
>> >
>> > That's why I proposed that IETF check with the hotels that this isn't
going to be an issue. The other potential issue I foresee which needs
checking with the authorities is if there will be a problem with customs
and immigration forms with questions regarding marital status and number of
family members traveling with you.
>>
>> Bingo.
>>
>> I've been coming to the IETF since 1996, and I know a fair number of
GLBTQ IETF participants, but I knew most of them for years, and in a few
cases for more than a decade, before realizing that.
>>
>> For my GLBTQ friends from the US, it has been relatively recent for most
of them to live their lives openly.
>>
>> The gay man who automatically came to IETF meetings even ten years ago
with no "paper trail" ten years ago is now much more likely to show up with
a paper train now.
>>
>> If he shows up with another man with the same last name, the same
address on IDs, each other as emergency contacts on every form that asks
for that, and (for extra credit) one or more kids with the same last name
in tow, it's a lot harder to miss in 2016 than it was in 2006, and at least
some of that is still visible even if he leaves the family at home.
>>
>> Our friends who were forced to suffer in silence until recently would
have a much more difficult time doing that today, even if they wanted to.
>>
>> Spencer

--001a11491bbae1cfc20530241fcd
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<p dir=3D"ltr">Hi, Ole,</p>
<p dir=3D"ltr">On Apr 10, 2016 10:08, &quot;Ole Jacobsen&quot; &lt;<a href=
=3D"mailto:olejacobsen@me.com">olejacobsen@me.com</a>&gt; wrote:<br>
&gt;<br>
&gt; Please rest assured that we are gathering information on precisely the=
se issues!</p>
<p dir=3D"ltr">Oh, I am. I absolutely am.</p>
<p dir=3D"ltr">And happy birthday, I believe?</p>
<p dir=3D"ltr">Spencer</p>
<p dir=3D"ltr">&gt; Ole J. Jacobsen<br>
&gt; Editor &amp; Publisher<br>
&gt; The Internet Protocol Journal<br>
&gt; Cell: +1 415 370-4628<br>
&gt; docomo: (090) 3337 9311<br>
&gt; <a href=3D"http://protocoljournal.org">http://protocoljournal.org</a><=
br>
&gt;<br>
&gt; Sent from my iPhone<br>
&gt;<br>
&gt; On Apr 10, 2016, at 12:01, Spencer Dawkins at IETF &lt;<a href=3D"mail=
to:spencerdawkins.ietf@gmail.com">spencerdawkins.ietf@gmail.com</a>&gt; wro=
te:<br>
&gt;<br>
&gt;&gt; This has been a wide-ranging conversation that I&#39;ve been conte=
nt to watch quietly, but Andrew just stepped on the land mine ...<br>
&gt;&gt;<br>
&gt;&gt; On Apr 10, 2016 01:36, &quot;Andrew Allen&quot; &lt;<a href=3D"mai=
lto:aallen@blackberry.com">aallen@blackberry.com</a>&gt; wrote:<br>
&gt;&gt; &gt;<br>
&gt;&gt; &gt;<br>
&gt;&gt; &gt; That&#39;s why I proposed that IETF check with the hotels tha=
t this isn&#39;t going to be an issue. The other potential issue I foresee =
which needs checking with the authorities is if there will be a problem wit=
h customs and immigration forms with questions regarding marital status and=
 number of family members traveling with you.<br>
&gt;&gt;<br>
&gt;&gt; Bingo.<br>
&gt;&gt;<br>
&gt;&gt; I&#39;ve been coming to the IETF since 1996, and I know a fair num=
ber of GLBTQ IETF participants, but I knew most of them for years, and in a=
 few cases for more than a decade, before realizing that.<br>
&gt;&gt;<br>
&gt;&gt; For my GLBTQ friends from the US, it has been relatively recent fo=
r most of them to live their lives openly.<br>
&gt;&gt;<br>
&gt;&gt; The gay man who automatically came to IETF meetings even ten years=
 ago with no &quot;paper trail&quot; ten years ago is now much more likely =
to show up with a paper train now.<br>
&gt;&gt;<br>
&gt;&gt; If he shows up with another man with the same last name, the same =
address on IDs, each other as emergency contacts on every form that asks fo=
r that, and (for extra credit) one or more kids with the same last name in =
tow, it&#39;s a lot harder to miss in 2016 than it was in 2006, and at leas=
t some of that is still visible even if he leaves the family at home.<br>
&gt;&gt;<br>
&gt;&gt; Our friends who were forced to suffer in silence until recently wo=
uld have a much more difficult time doing that today, even if they wanted t=
o.<br>
&gt;&gt;<br>
&gt;&gt; Spencer</p>

--001a11491bbae1cfc20530241fcd--


From nobody Sun Apr 10 09:43:36 2016
Return-Path: <john-ietf@jck.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 E20E412D601 for <ietf@ietfa.amsl.com>; Sun, 10 Apr 2016 09:43:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.896
X-Spam-Level: 
X-Spam-Status: No, score=-2.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.996] 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 EMw6VdcFfLpd for <ietf@ietfa.amsl.com>; Sun, 10 Apr 2016 09:43:33 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 780E012D5FB for <ietf@ietf.org>; Sun, 10 Apr 2016 09:43:32 -0700 (PDT)
Received: from [198.252.137.10] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1apISO-000F02-UH; Sun, 10 Apr 2016 12:43:28 -0400
Date: Sun, 10 Apr 2016 12:43:23 -0400
From: John C Klensin <john-ietf@jck.com>
To: "Murray S. Kucherawy" <superuser@gmail.com>, Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: I-D Action: draft-kucherawy-nomcom-procexp-00.txt
Message-ID: <47541D4081FC9856A5390378@JcK-HP8200.jck.com>
In-Reply-To: <CAL0qLwbROnW8pKKtd=7hkHHyP=xA-_eNoBuoKqPpaGjjpgUH+Q@mail.gmail.com>
References: <20160408185636.23101.86017.idtracker@ietfa.amsl.com> <570882CE.9010501@gmail.com> <13214.1460236486@obiwan.sandelman.ca> <CAL0qLwYKbB3_PQcUAUDqJwnddc4oywffVD+sVusOK2xiBYu4PA@mail.gmail.com> <5709CE36.3040605@gmail.com> <CAL0qLwbROnW8pKKtd=7hkHHyP=xA-_eNoBuoKqPpaGjjpgUH+Q@mail.gmail.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/dPcKLsx1F_dlUKoGU-EOIiVq23I>
Cc: Michael Richardson <mcr+ietf@sandelman.ca>, IETF discussion list <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: Sun, 10 Apr 2016 16:43:35 -0000

--On Saturday, April 09, 2016 21:46 -0700 "Murray S. Kucherawy"
<superuser@gmail.com> wrote:

> On Sat, Apr 9, 2016 at 8:53 PM, Brian E Carpenter <
> brian.e.carpenter@gmail.com> wrote:
> 
>> 
>> Regardless, I would think we would want challenges that said
>> things like "Brian Carpenter really hasn't been active enough
>> in the last couple of years to be able to evaluate the
>> candidates" rather than vaguely suggest that he is isn't
>> suitable.

> Does bullet 3 in Section 2 need to say more than it does now
> on that topic?

Murray, I don't know if my concern aligns with Brian's or not,
but I would think that there needs to be some impediment to
secret challenges that are based on innuendo, especially so
because there has traditionally been no appeal model for
challenges (and you don't add one).  On the other hand,
encouraging public slander is not a good idea either.  Perhaps
the text in Section 2 might be improved by: (i) Making it a bit
more clear that, while less that the historical attendance level
is grounds for a challenge, the assumption is that anyone who
applies is qualified and that any challenge has to contain
sufficient information of substance to overcome that
assumptions.  I think that is your intent, but the text is a
little bit less clear and more discretionary.  (ii) Adding a
rule that, if someone is challenged and the Nomcom chair upholds
the challenge and disqualifies the Nomcom applicant, the
challenge and associated correspondence may be made public at
the request of the applicant.  Perhaps the risk of public
disclosure would be sufficient to reduce concerns about possible
abuses

    john


From nobody Sun Apr 10 09:59:40 2016
Return-Path: <john-ietf@jck.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 BD3CE12D60B for <ietf@ietfa.amsl.com>; Sun, 10 Apr 2016 09:59:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.896
X-Spam-Level: 
X-Spam-Status: No, score=-2.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.996] 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 m9Ohg2t8PZ8U for <ietf@ietfa.amsl.com>; Sun, 10 Apr 2016 09:59:37 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CE7A412D558 for <ietf@ietf.org>; Sun, 10 Apr 2016 09:59:37 -0700 (PDT)
Received: from [198.252.137.10] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1apIi0-000F1h-IY; Sun, 10 Apr 2016 12:59:36 -0400
Date: Sun, 10 Apr 2016 12:59:31 -0400
From: John C Klensin <john-ietf@jck.com>
To: "Murray S. Kucherawy" <superuser@gmail.com>
Subject: Re: I-D Action: draft-kucherawy-nomcom-procexp-00.txt
Message-ID: <7FBF15BB56B5908D0A908194@JcK-HP8200.jck.com>
In-Reply-To: <47541D4081FC9856A5390378@JcK-HP8200.jck.com>
References: <20160408185636.23101.86017.idtracker@ietfa.amsl.com> <570882CE.9010501@gmail.com> <13214.1460236486@obiwan.sandelman.ca> <CAL0qLwYKbB3_PQcUAUDqJwnddc4oywffVD+sVusOK2xiBYu4PA@mail.gmail.com> <5709CE36.3040605@gmail.com> <CAL0qLwbROnW8pKKtd=7hkHHyP=xA-_eNoBuoKqPpaGjjpgUH+Q@mail.gmail.com> <47541D4081FC9856A5390378@JcK-HP8200.jck.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/0qsfQx8wGqZh4_orwKDsErng0k8>
Cc: IETF discussion list <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: Sun, 10 Apr 2016 16:59:38 -0000

Murray,

One more thought about the challenge process.  Without
performing the experiment, we can only guess at how many
challenges there would be and that might make a difference.
However, I wonder whether, instead of adding "didn't attend
enough meetings and isn't appropriate" on to the challenge
criteria for post-selection challenges, it might be better to
create a different category and allow challenges on that basis
to people entering the selection pool.

In other words, 

(1) The pool is announced (as today) with the "fewer meetings"
people identified (as you now suggest).

(2) There is a brief period for community challenges to those
who have not attended three of five meetings, paralleling the
period in which the Secretariat checks to be sure those who have
claimed three of five meetings really did attend.

(3) Once we get past step 2, the pool is the pool and, while any
one selected can be challenged under the rules of RFC 7437,
challenges based on meeting attendance are no longer allowed.

I'm not sure, and I'm a tad concerned about DoS attacks (see
above), but it seems to me that might be a little bit cleaner.
It would also have the property that potentially-controversial
challenges based on unsuitability would occur much earlier in
the process, before the random draw is made, and that might be
an advantage.

     john



From nobody Sun Apr 10 10:53:35 2016
Return-Path: <jared@puck.nether.net>
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 5F76412B066 for <ietf@ietfa.amsl.com>; Sun, 10 Apr 2016 10:53:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.198
X-Spam-Level: 
X-Spam-Status: No, score=-5.198 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.996, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] 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 ruXcX5EkXYoA for <ietf@ietfa.amsl.com>; Sun, 10 Apr 2016 10:53:32 -0700 (PDT)
Received: from puck.nether.net (puck.nether.net [IPv6:2001:418:3f4::5]) by ietfa.amsl.com (Postfix) with ESMTP id 22C3212B05D for <ietf@ietf.org>; Sun, 10 Apr 2016 10:53:32 -0700 (PDT)
Received: from [IPv6:2601:401:4:3000:14b4:8919:5865:bf3a] (unknown [IPv6:2601:401:4:3000:14b4:8919:5865:bf3a]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by puck.nether.net (Postfix) with ESMTPSA id 9D7F55406A1; Sun, 10 Apr 2016 13:53:29 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (1.0)
Subject: Re: Concerns about Singapore
From: Jared Mauch <jared@puck.nether.net>
X-Mailer: iPhone Mail (13E238)
In-Reply-To: <570A67B4.3010206@comcast.net>
Date: Sun, 10 Apr 2016 13:53:29 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <7060475F-E348-4BF0-B515-BB47143A2C24@puck.nether.net>
References: <0D914666-C3D4-4CCE-AD5E-4E5B34EA1A73@piuha.net> <20160407182936.GA21340@pfrc.org> <CAB75xn780nNDjGa_Cc222J20-+1CCHt09Xp8KHzaK=n0xx51pg@mail.gmail.com> <5706B100.9040509@mnt.se> <CAB75xn6fmj84ROUtG5eUB3GerHx83hrEr3w5vSADY_g=BRg5FA@mail.gmail.com> <5706BA40.3060005@mnt.se> <alpine.DEB.2.02.1604072157240.31096@uplift.swm.pp.se> <A9B63A6D-3102-482F-8FFC-2E57A5FD8336@nic.cz> <16925.1460122349@obiwan.sandelman.ca> <m27fg77zst.wl%randy@psg.com> <57097077.7040703@comcast.net> <m2fuuu75ls.wl%randy@psg.com> <87wpo5a8im.fsf@tops.chopps.org> <m260vp7eke.wl%randy@psg.com> <570A6458.3050206@comcast.net> <m21t6d7c9t.wl%randy@psg.com> <570A67B4.3010206@comcast.net>
To: Michael StJohns <mstjohns@comcast.net>
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/demkHJZ3MzKVAS7sb45gX7l95Rg>
Cc: IETF Disgust List <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: Sun, 10 Apr 2016 17:53:33 -0000

I would suggest European networks have quite different content than elsewher=
e as a result of local censorship laws and other rights afforded to people i=
n the region.=20

Jared Mauch

> On Apr 10, 2016, at 10:48 AM, Michael StJohns <mstjohns@comcast.net> wrote=
:
>=20
> On 4/10/2016 10:45 AM, Randy Bush wrote:
>>>> it was clean unfettered Internet.  some local folk stuck their necks ou=
t
>>>> very far to accomplish this.  it was definitely different than one got
>>>> outside of the ietf meeting network.  this has been a condition placed
>>>> on hosts and beijing was no exception.
>>> This surprises me - "this has been a condition placed on hosts...".
>> it was even in the hour of embarrassing babble fred used to prevent
>> people from talking about real problems at the bof
>>=20
>>> Could you enlighten us as to which [and I'll try to be precise here]
>>> other IETFs had a condition where the content accessible by the IETF
>>> network was markedly different from the content of say the network at
>>> a local Starbuck's equivalent wifi hot spot just down the street from
>>> the IETF and where that was mandated by the hosts and/or local laws?
>>> I mean besides Beijing?  Key words "markedly different" and "content
>>> accessible".
>> we don't specify it's 'different'.  among other silly distractions, it
>> would require a 'different from precisely what and in what ways?'
>>=20
>> we simply specifiy open and unfettered
>=20
> I repeat - "where" have the local hosts/laws specified conditions that res=
ulted in the IETF network content access being markedly different than that a=
ccessible to the random local citizen?
>=20
>=20
>>=20
>> rndy


From nobody Sun Apr 10 11:20:24 2016
Return-Path: <johnl@taugh.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 DFDF812B069 for <ietf@ietfa.amsl.com>; Sun, 10 Apr 2016 11:20:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.002
X-Spam-Level: 
X-Spam-Status: No, score=-0.002 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] 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 dxuFKZbTI-MD for <ietf@ietfa.amsl.com>; Sun, 10 Apr 2016 11:20:21 -0700 (PDT)
Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9AC3812B032 for <ietf@ietf.org>; Sun, 10 Apr 2016 11:20:21 -0700 (PDT)
Received: (qmail 89128 invoked from network); 10 Apr 2016 18:20:20 -0000
Received: from unknown (64.57.183.18) by mail1.iecc.com with QMQP; 10 Apr 2016 18:20:20 -0000
Date: 10 Apr 2016 18:19:58 -0000
Message-ID: <20160410181958.58762.qmail@ary.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: Concerns about Singapore and other places
In-Reply-To: <alpine.OSX.2.01.1604100736080.45987@rabdullah.local>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/82P-o9DtoS4zk8W4e5GQBDUNPas>
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: Sun, 10 Apr 2016 18:20:24 -0000

>The IETF has a meeting network requirements document that specifies a 
>number of parameters which includes no blocking.

In London in 2014, do you know whether we were behind the national
child porn filters?

R's,
John


From nobody Sun Apr 10 13:12:41 2016
Return-Path: <brian.e.carpenter@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 BDA4B12D12A for <ietf@ietfa.amsl.com>; Sun, 10 Apr 2016 13:12:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 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, RCVD_IN_DNSWL_LOW=-0.7, 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 UguM0f6CEkck for <ietf@ietfa.amsl.com>; Sun, 10 Apr 2016 13:12:38 -0700 (PDT)
Received: from mail-pa0-x22a.google.com (mail-pa0-x22a.google.com [IPv6:2607:f8b0:400e:c03::22a]) (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 3DCAA12D628 for <ietf@ietf.org>; Sun, 10 Apr 2016 13:12:36 -0700 (PDT)
Received: by mail-pa0-x22a.google.com with SMTP id ot11so24211915pab.1 for <ietf@ietf.org>; Sun, 10 Apr 2016 13:12:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=subject:to:references:cc:from:organization:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=dnwa3OZImRmHPuck5B0tRoXHpxBYSx+6olIbqkqQAk4=; b=satyRV4BHBmyUOaLTRTiuiVdVYgkMcIJBls+b+sOtUp/boAHMaPvusT0UXboRfoNR2 bi4p7p1qpcgae8UhwND3QLQZkWeZstvYT9LCCalTgwgWU2nsZC6oNFjvUEPmSx7O4Z+n 39ZMh/q64Ee+pX2kb5HZOU8GvO7qd3BWrNhJ6WiV/pw/52XrZ94fAIwbzCi9c6uNcfDC nQsnm4/waTYiJNHmWC4gaSQgZJ5IZt6sf29n/DY/pxbK+o1lE8dcvCUVYoesGkjpa5C9 qk5SjybzcMD4nxMjdKtw+RKamXhx6fpPWkEDxwfc/U/eL5FsT6vsUPqhKKEnFUDcRIpH KmAw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:cc:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=dnwa3OZImRmHPuck5B0tRoXHpxBYSx+6olIbqkqQAk4=; b=I0DJ/de2t6Ip+wxic4sGFArfsuAqMln0ldn1ilntSYAAJ+vuVrrqk2qRg8kNBSYeeB vXvOY8Plo0NnYTC9qByO4gNTHy+kFl5k2PtqGtGZAw+GZDvd2JAchaihUyf6TGVufln8 +m8UqORUBb2dobIFvrs5gFFddgZWYzuXdbCzepoS2ix58Ak9dzKmJgpPklN0XddNSFwT kpj0XlLofJ0thP/0EfSzuwceQxqNlowYk/6X0ETEVMAj2d22f18OzJv5qWWjqrcmgHMn BmT2pDW+2BKBExrC91WB09XQAIoW8cF0tgWyKz88Tb2IzHOVeO9FzUJkRhMaqMXWSiIk 2ZYQ==
X-Gm-Message-State: AD7BkJJsWJDYA07fScTor+8xlOZ5JcJdQMFLQg8enkKjVHpcGREYWTL6BkRk/Hnia1GwyA==
X-Received: by 10.66.164.165 with SMTP id yr5mr27792006pab.133.1460319155852;  Sun, 10 Apr 2016 13:12:35 -0700 (PDT)
Received: from ?IPv6:2406:e007:4e39:1:28cc:dc4c:9703:6781? ([2406:e007:4e39:1:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id x64sm31117657pfa.72.2016.04.10.13.12.33 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 10 Apr 2016 13:12:34 -0700 (PDT)
Subject: Re: Concerns about Singapore
To: Michael StJohns <mstjohns@comcast.net>, Randy Bush <randy@psg.com>
References: <0D914666-C3D4-4CCE-AD5E-4E5B34EA1A73@piuha.net> <20160407182936.GA21340@pfrc.org> <CAB75xn780nNDjGa_Cc222J20-+1CCHt09Xp8KHzaK=n0xx51pg@mail.gmail.com> <5706B100.9040509@mnt.se> <CAB75xn6fmj84ROUtG5eUB3GerHx83hrEr3w5vSADY_g=BRg5FA@mail.gmail.com> <5706BA40.3060005@mnt.se> <alpine.DEB.2.02.1604072157240.31096@uplift.swm.pp.se> <A9B63A6D-3102-482F-8FFC-2E57A5FD8336@nic.cz> <16925.1460122349@obiwan.sandelman.ca> <m27fg77zst.wl%randy@psg.com> <57097077.7040703@comcast.net> <m2fuuu75ls.wl%randy@psg.com> <87wpo5a8im.fsf@tops.chopps.org> <m260vp7eke.wl%randy@psg.com> <570A6458.3050206@comcast.net> <m21t6d7c9t.wl%randy@psg.com> <570A67B4.3010206@comcast.net>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <570AB3AF.2050401@gmail.com>
Date: Mon, 11 Apr 2016 08:12:31 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2
MIME-Version: 1.0
In-Reply-To: <570A67B4.3010206@comcast.net>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/o1NrfBYYx58Y_Q3RXsb1nO4jVjE>
Cc: IETF discussion list <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: Sun, 10 Apr 2016 20:12:40 -0000

On 11/04/2016 02:48, Michael StJohns wrote:
> On 4/10/2016 10:45 AM, Randy Bush wrote:
>>>> it was clean unfettered Internet.  some local folk stuck their necks out
>>>> very far to accomplish this.  it was definitely different than one got
>>>> outside of the ietf meeting network.  this has been a condition placed
>>>> on hosts and beijing was no exception.
>>> This surprises me - "this has been a condition placed on hosts...".

In the case of Beijing it was very clear from the earliest discussions,
going back to 2005 and before, to my personal knowledge.

...
> 
> I repeat - "where" have the local hosts/laws specified conditions that resulted in the IETF network content access being
> markedly different than that accessible to the random local citizen?

Why is that relevant? The criterion is: can the IETF do its work properly?
Of which a sub-criterion is: will there be clean unfettered Internet at
the meeting site?

How RFC 4084 applies in the local coffee shops is another matter.

   Brian


From nobody Sun Apr 10 13:21:49 2016
Return-Path: <dhc@dcrocker.net>
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 F02F512D10C for <ietf@ietfa.amsl.com>; Sun, 10 Apr 2016 13:21:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] 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 GDF_iZqXydZs for <ietf@ietfa.amsl.com>; Sun, 10 Apr 2016 13:21:48 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1153212D105 for <ietf@ietf.org>; Sun, 10 Apr 2016 13:21:48 -0700 (PDT)
Received: from [192.168.1.168] (76-218-10-206.lightspeed.sntcca.sbcglobal.net [76.218.10.206]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id u3AKLgHC004787 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Sun, 10 Apr 2016 13:21:42 -0700
Subject: Re: Concerns about Singapore
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, Michael StJohns <mstjohns@comcast.net>, Randy Bush <randy@psg.com>
References: <0D914666-C3D4-4CCE-AD5E-4E5B34EA1A73@piuha.net> <20160407182936.GA21340@pfrc.org> <CAB75xn780nNDjGa_Cc222J20-+1CCHt09Xp8KHzaK=n0xx51pg@mail.gmail.com> <5706B100.9040509@mnt.se> <CAB75xn6fmj84ROUtG5eUB3GerHx83hrEr3w5vSADY_g=BRg5FA@mail.gmail.com> <5706BA40.3060005@mnt.se> <alpine.DEB.2.02.1604072157240.31096@uplift.swm.pp.se> <A9B63A6D-3102-482F-8FFC-2E57A5FD8336@nic.cz> <16925.1460122349@obiwan.sandelman.ca> <m27fg77zst.wl%randy@psg.com> <57097077.7040703@comcast.net> <m2fuuu75ls.wl%randy@psg.com> <87wpo5a8im.fsf@tops.chopps.org> <m260vp7eke.wl%randy@psg.com> <570A6458.3050206@comcast.net> <m21t6d7c9t.wl%randy@psg.com> <570A67B4.3010206@comcast.net> <570AB3AF.2050401@gmail.com>
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
Message-ID: <570AB5D0.5060004@dcrocker.net>
Date: Sun, 10 Apr 2016 13:21:36 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2
MIME-Version: 1.0
In-Reply-To: <570AB3AF.2050401@gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Sun, 10 Apr 2016 13:21:43 -0700 (PDT)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/woMjzMXlpc14rxSxTE_hoc_RJ7E>
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: dcrocker@bbiw.net
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: Sun, 10 Apr 2016 20:21:49 -0000

On 4/10/2016 1:12 PM, Brian E Carpenter wrote:
>> I repeat - "where" have the local hosts/laws specified conditions that resulted in the IETF network content access being
>> >markedly different than that accessible to the random local citizen?
> Why is that relevant? The criterion is: can the IETF do its work properly?
> Of which a sub-criterion is: will there be clean unfettered Internet at
> the meeting site?


A great deal of IETF work gets done away from the meeting site.  Having 
state-imposed restrictions away from the meeting site invites basic 
productivity limitations.

It also is oddly dissonant with the IETF's general call for open and 
unfettered access.  We risk sounding a tad elitist if it means something 
like "open and unfettered for us, but we're not concerned about you 
other folk"...

To offer an intentionally extreme comparison, imagine having a desire 
that children not be recruited to be soldiers.  (Yes, I know, that's a 
controversial point of view and many reasonable people think it's ok to 
have children be slaughtered and do slaughtering in war...)  But then 
imagine choosing to go to a country that uses children that way, 
formally.  Is it reasonable to go there with the view that it's ok, as 
long as they don't recruit any of /our/ children to be solders?

d/

-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net


From nobody Sun Apr 10 13:29:56 2016
Return-Path: <brian.e.carpenter@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 6F7CD12D0F3 for <ietf@ietfa.amsl.com>; Sun, 10 Apr 2016 13:29:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 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, RCVD_IN_DNSWL_LOW=-0.7, 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 EnfV5iPBtyrl for <ietf@ietfa.amsl.com>; Sun, 10 Apr 2016 13:29:54 -0700 (PDT)
Received: from mail-pf0-x233.google.com (mail-pf0-x233.google.com [IPv6:2607:f8b0:400e:c00::233]) (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 17ABF12B00C for <ietf@ietf.org>; Sun, 10 Apr 2016 13:29:54 -0700 (PDT)
Received: by mail-pf0-x233.google.com with SMTP id 184so110251437pff.0 for <ietf@ietf.org>; Sun, 10 Apr 2016 13:29:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=subject:to:references:cc:from:organization:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=Q+b7Q9hDJcX0btRzP0UZ0BSY+0c91EjXFZYqJ95b3vQ=; b=FYnf5sBEJQa+32UbH5XNGXBfbcGj7k0c+ecq48IVJzkQzbr+/FOTJmd1MaG1sy6aQa UkGEYtrzQaAGzpcjH1yYiXQglcZHNFro68MnmvA6zSV8RdSgsbw8elWF7luZII6P+Rvq PbWhFw9dcUUyN7LqGflTIpPuseqDpK4huSfjKLSuVZ2Ki3CUZqR9AXQgRjRwZ8wP4nC6 sHmMRG8eCKL/ptLuzQSbrcLz9V6lPTfCAfBt6dDLLLtwMEuh6N9N04hzuIwpGQmn5CRe vOE5ypbEkZVgqp8x2hUSndqIpBG14L8ct/8+SkLDs1BqBEobAZHsBdMdd2nslXmt07oA zBVw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:cc:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=Q+b7Q9hDJcX0btRzP0UZ0BSY+0c91EjXFZYqJ95b3vQ=; b=dQUU/DO9lr0L940Iy7L12BUY3IMuspJB3Eu1mzaur1CVJ4PS6ON5ahBoTUDdYeZhSz d+pUBq+G8bUCStUuafBf6MF5i8AuLQzuwF0rA+mpIjAbWRVTHKF0LkyNUfGSE5W/MkEA kdwXeVCjy0SH4LIX9pJ64dT+T1syYpisFyp3gZk7BJWrdDCCIk9oSx8z4YjxhoSPzgff jLTEanppvreJksU7oL+KQ2FuToNf9aFbgsAOv/K1KjUH2l9broFpXay8afvet6DVwNtO FdrzHQroedNSONYntBg0MwVa+FbuQODJajiz0XhuVmYgS9N4X+eijvzeuJMO39NvWbuF Ms6g==
X-Gm-Message-State: AD7BkJKUEgja2f6f01qKM3EYAOML4sB+NcjNkgCLj/FymwLIjbiGUvgxzFAcnsEJlxxY0w==
X-Received: by 10.98.18.212 with SMTP id 81mr28261983pfs.104.1460320193734; Sun, 10 Apr 2016 13:29:53 -0700 (PDT)
Received: from ?IPv6:2406:e007:4e39:1:28cc:dc4c:9703:6781? ([2406:e007:4e39:1:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id y3sm9677287par.2.2016.04.10.13.29.50 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 10 Apr 2016 13:29:52 -0700 (PDT)
Subject: Re: I-D Action: draft-kucherawy-nomcom-procexp-00.txt
To: John C Klensin <john-ietf@jck.com>, "Murray S. Kucherawy" <superuser@gmail.com>
References: <20160408185636.23101.86017.idtracker@ietfa.amsl.com> <570882CE.9010501@gmail.com> <13214.1460236486@obiwan.sandelman.ca> <CAL0qLwYKbB3_PQcUAUDqJwnddc4oywffVD+sVusOK2xiBYu4PA@mail.gmail.com> <5709CE36.3040605@gmail.com> <CAL0qLwbROnW8pKKtd=7hkHHyP=xA-_eNoBuoKqPpaGjjpgUH+Q@mail.gmail.com> <47541D4081FC9856A5390378@JcK-HP8200.jck.com> <7FBF15BB56B5908D0A908194@JcK-HP8200.jck.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <570AB7BC.8040605@gmail.com>
Date: Mon, 11 Apr 2016 08:29:48 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2
MIME-Version: 1.0
In-Reply-To: <7FBF15BB56B5908D0A908194@JcK-HP8200.jck.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/xQPffW-GCnZZxHKOD4aLi1QtT6U>
Cc: IETF discussion list <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: Sun, 10 Apr 2016 20:29:55 -0000

1) Murray asked:

> Does bullet 3 in Section 2 need to say more than it does now on that topic?

No. "Such a challenge must be
accompanied by an explanation of why that particular member is
not suitable." allows any kind of challenge, including libel.
I'm saying that the only allowable challenge here should be
on the grounds of insufficient recent IETF experience.

2) Therefore, with respect to what John writes below, +1.

   Brian
On 11/04/2016 04:59, John C Klensin wrote:
> Murray,
> 
> One more thought about the challenge process.  Without
> performing the experiment, we can only guess at how many
> challenges there would be and that might make a difference.
> However, I wonder whether, instead of adding "didn't attend
> enough meetings and isn't appropriate" on to the challenge
> criteria for post-selection challenges, it might be better to
> create a different category and allow challenges on that basis
> to people entering the selection pool.
> 
> In other words, 
> 
> (1) The pool is announced (as today) with the "fewer meetings"
> people identified (as you now suggest).
> 
> (2) There is a brief period for community challenges to those
> who have not attended three of five meetings, paralleling the
> period in which the Secretariat checks to be sure those who have
> claimed three of five meetings really did attend.
> 
> (3) Once we get past step 2, the pool is the pool and, while any
> one selected can be challenged under the rules of RFC 7437,
> challenges based on meeting attendance are no longer allowed.
> 
> I'm not sure, and I'm a tad concerned about DoS attacks (see
> above), but it seems to me that might be a little bit cleaner.
> It would also have the property that potentially-controversial
> challenges based on unsuitability would occur much earlier in
> the process, before the random draw is made, and that might be
> an advantage.
> 
>      john
> 
> 
> 


From nobody Sun Apr 10 13:59:33 2016
Return-Path: <mstjohns@comcast.net>
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 78F8212D12A for <ietf@ietfa.amsl.com>; Sun, 10 Apr 2016 13:59:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.696
X-Spam-Level: 
X-Spam-Status: No, score=-3.696 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, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.996, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=comcast.net
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 UybjhcPNvV2A for <ietf@ietfa.amsl.com>; Sun, 10 Apr 2016 13:59:30 -0700 (PDT)
Received: from resqmta-ch2-04v.sys.comcast.net (resqmta-ch2-04v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:36]) (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 4BC0512D121 for <ietf@ietf.org>; Sun, 10 Apr 2016 13:59:30 -0700 (PDT)
Received: from resomta-ch2-17v.sys.comcast.net ([69.252.207.113]) by comcast with SMTP id pMS9aU8jonIc7pMS9aXQsB; Sun, 10 Apr 2016 20:59:29 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1460321969; bh=8vPZSYcRpLkV3HRu4F9tr8sfgjaxDqS8dLrEIkylS+Y=; h=Received:Received:Subject:To:From:Message-ID:Date:MIME-Version: Content-Type; b=lACpT6pCO3gebfvStWDKU9lGerjKUYp1pocHJaaywq/z34kmCE+XaDotVp2rc+QO5 UHEEhMWriAm6aoZq2cOvQwSGe0oautwtJgh0/+vof22TpCuJtnP+eJJrBa17qvxpW4 T81vJdH0xlAGuDjJmcg3fF9g6Ziz9UPoTM9cyjRBSFI3UawqkZgODRMuaq4Z1esTcU LFCcZTHUhFu8mgabK85i81FR79bLMefOAOK4hWv8qX38+xA3tPq3Fg6JEey6W8zFom U2IdcThNYZ3IGjzA8UHBLD4tk625VnaKBAFiTHhKe2OziK8SnSk0olx9GqqRlu3TEK iz2pTJ9KkD5LA==
Received: from [192.168.1.113] ([69.255.115.150]) by resomta-ch2-17v.sys.comcast.net with comcast id gkzU1s00P3Em2Kp01kzVFU; Sun, 10 Apr 2016 20:59:29 +0000
Subject: Re: Concerns about Singapore
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, Randy Bush <randy@psg.com>
References: <0D914666-C3D4-4CCE-AD5E-4E5B34EA1A73@piuha.net> <20160407182936.GA21340@pfrc.org> <CAB75xn780nNDjGa_Cc222J20-+1CCHt09Xp8KHzaK=n0xx51pg@mail.gmail.com> <5706B100.9040509@mnt.se> <CAB75xn6fmj84ROUtG5eUB3GerHx83hrEr3w5vSADY_g=BRg5FA@mail.gmail.com> <5706BA40.3060005@mnt.se> <alpine.DEB.2.02.1604072157240.31096@uplift.swm.pp.se> <A9B63A6D-3102-482F-8FFC-2E57A5FD8336@nic.cz> <16925.1460122349@obiwan.sandelman.ca> <m27fg77zst.wl%randy@psg.com> <57097077.7040703@comcast.net> <m2fuuu75ls.wl%randy@psg.com> <87wpo5a8im.fsf@tops.chopps.org> <m260vp7eke.wl%randy@psg.com> <570A6458.3050206@comcast.net> <m21t6d7c9t.wl%randy@psg.com> <570A67B4.3010206@comcast.net> <570AB3AF.2050401@gmail.com>
From: Michael StJohns <mstjohns@comcast.net>
Message-ID: <570ABEA2.6090701@comcast.net>
Date: Sun, 10 Apr 2016 16:59:14 -0400
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2
MIME-Version: 1.0
In-Reply-To: <570AB3AF.2050401@gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/_NpTeAlnXNKN0UD2nYdy3z6hiIE>
Cc: IETF discussion list <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: Sun, 10 Apr 2016 20:59:31 -0000

On 4/10/2016 4:12 PM, Brian E Carpenter wrote:
> On 11/04/2016 02:48, Michael StJohns wrote:
>> On 4/10/2016 10:45 AM, Randy Bush wrote:
>>>>> it was clean unfettered Internet.  some local folk stuck their necks out
>>>>> very far to accomplish this.  it was definitely different than one got
>>>>> outside of the ietf meeting network.  this has been a condition placed
>>>>> on hosts and beijing was no exception.
>>>> This surprises me - "this has been a condition placed on hosts...".
> In the case of Beijing it was very clear from the earliest discussions,
> going back to 2005 and before, to my personal knowledge.
>
> ...

This is where close reading of the chain is useful - specifically the 
meaning of "this".  What I was referring to was the "condition placed on 
the hosts" (apparently by the government) that the IETF regulate access 
to its network by implementing a per user login system, rather than 
"condition placed on the hosts" by the IETF that we get to see the real 
Internet as a requirement for going there. The former is unique in 
AFAICT.  The latter is basically business as usual for us.
>> I repeat - "where" have the local hosts/laws specified conditions that resulted in the IETF network content access being
>> markedly different than that accessible to the random local citizen?
> Why is that relevant? The criterion is: can the IETF do its work properly?
> Of which a sub-criterion is: will there be clean unfettered Internet at
> the meeting site?

It's not relevant to that question exactly - this goes all the way back 
to the beginning of this chain with respect to the meaning of "open" vs 
"closed" network and from who's viewpoint you're considering the 
question.   The original poster said Beijing was a closed network, Randy 
said it was an open network.  From any one sitting inside the IETF 
looking out, it certainly was as open as what we normally get.  For 
anyone sitting outside, in country,  and unable to come in, it certainly 
was as closed as any corporate or VPN or government network as I've ever 
seen.

 From MCR's original comment, I believe he was viewing the network as 
closed using the above criteria.

Later, Mike

>
> How RFC 4084 applies in the local coffee shops is another matter.
>
>     Brian


From nobody Sun Apr 10 16:15:20 2016
Return-Path: <robert.w.withers@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 D50E712D195 for <ietf@ietfa.amsl.com>; Sun, 10 Apr 2016 16:15:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 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, RCVD_IN_DNSWL_LOW=-0.7, 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 A-IMb98-x5QY for <ietf@ietfa.amsl.com>; Sun, 10 Apr 2016 16:15:17 -0700 (PDT)
Received: from mail-qg0-x22c.google.com (mail-qg0-x22c.google.com [IPv6:2607:f8b0:400d:c04::22c]) (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 47B3E12D185 for <ietf@ietf.org>; Sun, 10 Apr 2016 16:15:17 -0700 (PDT)
Received: by mail-qg0-x22c.google.com with SMTP id c6so131518641qga.1 for <ietf@ietf.org>; Sun, 10 Apr 2016 16:15:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=subject:mime-version:from:in-reply-to:date :content-transfer-encoding:message-id:references:to; bh=8046h3ihm6q1i+q1hHrKk7e0AIPRmu57kb75zFru/qU=; b=J4of56Cz010pCxQOIe5VZodsObfedUyPYKqYzTLcU22jvIEqC1NLIhM1cp6AYKdF7F lV6rGTfITKo1IH0VCPh7fxzJxwUA1Ef970LlB7yFH+ltzyLfmS/iGLhL36WeMi8P8EOk vXVS962bTBRVyksEi/YQ2zgROBJ22dMdr3UkuI7I+EmL3YPTXagtdRseg6AGKi/JLE/a HynMtV/MMISOJ52HCGI7OyCEcEAt/JSsZUNzKKqyU3XtbfDSB0AvtQ8ekowCXzHOmsW8 ihvEIurl8BjE/N/kAfyZCM1NjF1Xl2yJQAxDgZVLVqcI39RcMxx+iSOebfrG1fzSOEfQ 0dag==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:mime-version:from:in-reply-to:date :content-transfer-encoding:message-id:references:to; bh=8046h3ihm6q1i+q1hHrKk7e0AIPRmu57kb75zFru/qU=; b=cMwILgqIxVHUMau63Rv8EQxYMtADSkdvPObW4S9IaYom48fIdw0h3Rvqt705zi5mk8 5EZyO140Os0AcOnFbLvdM03vruWXAWGHmOI06dpFTY9WmyL9A9g8R1DuNwCvphHlr3Xx hlpCZ6y3Z+AJXYz38j5vW7Y6brE0MS6Yv1Cs2a/H3iBLfwMbgv26l3QYg9TckRiyN0s8 /YJSXCS2QN1nLuO55Ya5NHu5mMjw8yaSl5UjFPr4tR5dlB5OYmM+plBvnbqB0ByepjP7 qkDVDh8Ook/fjdpXDHS44MJlVRRkRbYHqr6+sDjnOqjPs9GDeZV7OnncCIrxUqrmYqIV NHtA==
X-Gm-Message-State: AD7BkJJBtvpC9x3BB+RumriTm9xy0JseVOPQ5YKl9X03eO+PDLX83HZqRfX16TaU7DqdwA==
X-Received: by 10.140.194.67 with SMTP id p64mr27162607qha.19.1460330116439; Sun, 10 Apr 2016 16:15:16 -0700 (PDT)
Received: from [192.168.2.3] (cpe-107-15-45-203.nc.res.rr.com. [107.15.45.203]) by smtp.gmail.com with ESMTPSA id j185sm2079291qke.40.2016.04.10.16.15.14 for <ietf@ietf.org> (version=TLSv1/SSLv3 cipher=OTHER); Sun, 10 Apr 2016 16:15:14 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Subject: Re: Concerns about Singapore
Mime-Version: 1.0 (1.0)
X-Mailer: iPhone Mail (13E238)
From: Robert Withers <robert.w.withers@gmail.com>
In-Reply-To: <8295F54A-0A2B-4D89-9433-519F14F63C65@puck.nether.net>
Date: Sun, 10 Apr 2016 19:15:13 -0400
Content-Transfer-Encoding: quoted-printable
Received: from [192.168.2.3] (cpe-107-15-45-203.nc.res.rr.com. [107.15.45.203]) by smtp.gmail.com with ESMTPSA id m188sm13200240ywe.46.2016.04.10.13.45.01 for <jared@puck.nether.net> (version=TLSv1/SSLv3 cipher=OTHER); Sun, 10 Apr 2016 13:45:01 -0700 (PDT)
Message-Id: <FFA9507A-A1A6-42D9-8047-ADE81B6044EC@gmail.com>
References: <0D914666-C3D4-4CCE-AD5E-4E5B34EA1A73@piuha.net> <20160407182936.GA21340@pfrc.org> <CAB75xn780nNDjGa_Cc222J20-+1CCHt09Xp8KHzaK=n0xx51pg@mail.gmail.com> <5706B100.9040509@mnt.se> <CAB75xn6fmj84ROUtG5eUB3GerHx83hrEr3w5vSADY_g=BRg5FA@mail.gmail.com> <5706BA40.3060005@mnt.se> <alpine.DEB.2.02.1604072157240.31096@uplift.swm.pp.se> <A9B63A6D-3102-482F-8FFC-2E57A5FD8336@nic.cz> <16925.1460122349@obiwan.sandelman.ca> <m27fg77zst.wl%randy@psg.com> <57097077.7040703@comcast.net> <m2fuuu75ls.wl%randy@psg.com> <87wpo5a8im.fsf@tops.chopps.org> <m260vp7eke.wl%randy@psg.com> <570A6458.3050206@comcast.net> <m21t6d7c9t.wl%randy@psg.com> <570A67B4.3010206@comcast.net> <7060475F-E348-4BF0-B515-BB47143A2C24@puck.nether.net> <570A9A5F.6020906@gmail.com> <8295F54A-0A2B-4D89-9433-519F14F63C65@puck.nether.net>
To: ietf@ietf.org
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/iCjfEvU8cjR658i0ciMlxqE_JnU>
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: Sun, 10 Apr 2016 23:15:19 -0000

Resending to the list...and an extra thought...

If censorship rights are managed in more granularity than nationally, perhap=
s the neighborhood or subdivision level, it allows variance and differentiat=
ion, including mixed access within an urban setting. The nation must be the u=
nion and membership in associations may carry censorship requirements limiti=
ng one's access by agreement. This sort of approach may be welcomed by those=
 regimes with real concerns regarding 'westernization' of their media. Count=
ries may well allow international conference attendees free access while sim=
ultaneously protecting their children from wanting to serve the local warlor=
d rather than sticking to the local Civil Defense Unit. I believe the idea h=
as merit, perhaps reducing slaughter.

=46rom the perspective of those exercising active decision, it would be term=
ed the right to forget, another right to be sure. It's a form of BDS, yes? Q=
uite effective.

Well I think it would be wonderful if network protocols supported filtering i=
n both senses: filter reception from certain senders & filter transmission t=
o certain recipients. I'm thinking of some sort of intersection of sender/re=
ceiver permission volumes specified with N dimensional Voronoi tessellations=
 in negotiated session state at the routers, managed with multicast hashes i=
n the traffic headers. One will literally never be in contact with said trou=
blesome traffic and both foreign and domestic users would have that censorin=
g/forgetting guarantee.=20

best,
robert

> On Apr 10, 2016, at 16:28, Jared Mauch <jared@puck.nether.net> wrote:
>=20
> Countries do their own censorship, or have rights for their citizens eg: r=
egional/ national right to be forgotten.=20
>=20
> If you need some articles on these topics, let me know.=20
>=20
> Jared Mauch
>=20
>> On Apr 10, 2016, at 2:24 PM, Robert Withers <robert.w.withers@gmail.com> w=
rote:
>>=20
>> Pardon me, do I understanding you to say that it is a basic right for a l=
ocal region to censor content? As you put it: "local censorship laws and oth=
er rights", So to establish specific censorships in local areas, this is a f=
undamental right of that neighborhood?  That is a very shiny idea, very Mill=
enarianly said.
>>=20
>> Robert
>>=20
>>> On 04/10/2016 01:53 PM, Jared Mauch wrote:
>>> I would suggest European networks have quite different content than else=
where as a result of local censorship laws and other rights afforded to peop=
le in the region.
>>>=20
>>> Jared Mauch
>>>=20
>>>> On Apr 10, 2016, at 10:48 AM, Michael StJohns <mstjohns@comcast.net> wr=
ote:
>>>>=20
>>>> On 4/10/2016 10:45 AM, Randy Bush wrote:
>>>>>>> it was clean unfettered Internet.  some local folk stuck their necks=
 out
>>>>>>> very far to accomplish this.  it was definitely different than one g=
ot
>>>>>>> outside of the ietf meeting network.  this has been a condition plac=
ed
>>>>>>> on hosts and beijing was no exception.
>>>>>> This surprises me - "this has been a condition placed on hosts...".
>>>>> it was even in the hour of embarrassing babble fred used to prevent
>>>>> people from talking about real problems at the bof
>>>>>=20
>>>>>> Could you enlighten us as to which [and I'll try to be precise here]
>>>>>> other IETFs had a condition where the content accessible by the IETF
>>>>>> network was markedly different from the content of say the network at=

>>>>>> a local Starbuck's equivalent wifi hot spot just down the street from=

>>>>>> the IETF and where that was mandated by the hosts and/or local laws?
>>>>>> I mean besides Beijing?  Key words "markedly different" and "content
>>>>>> accessible".
>>>>> we don't specify it's 'different'.  among other silly distractions, it=

>>>>> would require a 'different from precisely what and in what ways?'
>>>>>=20
>>>>> we simply specifiy open and unfettered
>>>> I repeat - "where" have the local hosts/laws specified conditions that r=
esulted in the IETF network content access being markedly different than tha=
t accessible to the random local citizen?
>>>>=20
>>>>=20
>>>>> rndy
>>=20
>> --=20
>> Robert
>> .  ..   ...    ^,^
>=20


From nobody Sun Apr 10 18:17:00 2016
Return-Path: <chopps@chopps.org>
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 8C1D012DC94 for <ietf@ietfa.amsl.com>; Sun, 10 Apr 2016 18:16:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.896
X-Spam-Level: 
X-Spam-Status: No, score=-2.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.996] 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 5T11dzHE0keN for <ietf@ietfa.amsl.com>; Sun, 10 Apr 2016 18:16:57 -0700 (PDT)
Received: from smtp.chopps.org (smtp.chopps.org [54.88.81.56]) by ietfa.amsl.com (Postfix) with ESMTP id 81C3F12DC64 for <ietf@ietf.org>; Sun, 10 Apr 2016 18:16:57 -0700 (PDT)
Received: from tops.chopps.org (24-247-68-31.dhcp.trcy.mi.charter.com [24.247.68.31]) (using TLSv1.2 with cipher AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by smtp.chopps.org (Postfix) with ESMTPSA id 7811061176; Mon, 11 Apr 2016 01:16:56 +0000 (UTC)
References: <0D914666-C3D4-4CCE-AD5E-4E5B34EA1A73@piuha.net> <20160407182936.GA21340@pfrc.org> <CAB75xn780nNDjGa_Cc222J20-+1CCHt09Xp8KHzaK=n0xx51pg@mail.gmail.com> <5706B100.9040509@mnt.se> <CAB75xn6fmj84ROUtG5eUB3GerHx83hrEr3w5vSADY_g=BRg5FA@mail.gmail.com> <5706BA40.3060005@mnt.se> <alpine.DEB.2.02.1604072157240.31096@uplift.swm.pp.se> <A9B63A6D-3102-482F-8FFC-2E57A5FD8336@nic.cz> <16925.1460122349@obiwan.sandelman.ca> <m27fg77zst.wl%randy@psg.com> <57097077.7040703@comcast.net> <m2fuuu75ls.wl%randy@psg.com> <87wpo5a8im.fsf@tops.chopps.org> <m260vp7eke.wl%randy@psg.com> <570A6458.3050206@comcast.net> <m21t6d7c9t.wl%randy@psg.com> <570A67B4.3010206@comcast.net> <570AB3AF.2050401@gmail.com>
User-agent: mu4e 0.9.16; emacs 24.5.1
From: <chopps@chopps.org>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: Concerns about Singapore
In-reply-to: <570AB3AF.2050401@gmail.com>
Date: Sun, 10 Apr 2016 21:16:55 -0400
Message-ID: <87twj99c6w.fsf@tops.chopps.org>
MIME-Version: 1.0
Content-Type: text/plain
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/wN1HXfVWmPNk32XbEU34hjdZB8I>
Cc: IETF discussion list <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: Mon, 11 Apr 2016 01:16:58 -0000

Brian E Carpenter <brian.e.carpenter@gmail.com> writes:

> On 11/04/2016 02:48, Michael StJohns wrote:
>> On 4/10/2016 10:45 AM, Randy Bush wrote:
>>>>> it was clean unfettered Internet.  some local folk stuck their necks out
>>>>> very far to accomplish this.  it was definitely different than one got
>>>>> outside of the ietf meeting network.  this has been a condition placed
>>>>> on hosts and beijing was no exception.
>>>> This surprises me - "this has been a condition placed on hosts...".
>
> In the case of Beijing it was very clear from the earliest discussions,
> going back to 2005 and before, to my personal knowledge.
>
> ...
>>
>> I repeat - "where" have the local hosts/laws specified conditions that resulted in the IETF network content access being
>> markedly different than that accessible to the random local citizen?
>
> Why is that relevant? The criterion is: can the IETF do its work properly?
> Of which a sub-criterion is: will there be clean unfettered Internet at
> the meeting site?

It's certainly relevant to me, b/c I don't personally think that IETF
meetings should be held in oppressive and censoring countries. I don't
know how to articulate this well -- others are better at it -- but I
certainly would like to skip any meetings that I feel violate IETFs
value of openness so that I can at least vote with my feet and my
dollars.

Thanks,
Chris.

>
> How RFC 4084 applies in the local coffee shops is another matter.
>
>    Brian


From nobody Sun Apr 10 19:24:29 2016
Return-Path: <vinayakh@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 9389612DFD4 for <ietf@ietfa.amsl.com>; Sun, 10 Apr 2016 19:24:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 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, RCVD_IN_DNSWL_LOW=-0.7, 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 KMMJF-af91Yx for <ietf@ietfa.amsl.com>; Sun, 10 Apr 2016 19:24:27 -0700 (PDT)
Received: from mail-wm0-x231.google.com (mail-wm0-x231.google.com [IPv6:2a00:1450:400c:c09::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 AD5B612DFD3 for <ietf@ietf.org>; Sun, 10 Apr 2016 19:24:26 -0700 (PDT)
Received: by mail-wm0-x231.google.com with SMTP id 191so69095864wmq.0 for <ietf@ietf.org>; Sun, 10 Apr 2016 19:24:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=cXhTDCFiGqQJunm567EO3NCmL5ZAxEpYPPpCLZL6FMY=; b=CCQmhCqy3aiAoB5N2yFp08eY5wCkUUkXtKV6a+UWE/cqffANcIsNvQA83ih++anyRl V4x+ryMGfULdahMottnUgUWyXICU1JzioFtzTelAT7y5LbY7FC7v6u4Ws7aEH7g6QwBZ PjpRJwDzso2QqfE5c3lz0uf2nEH9zON3jEjswSeXRHlxmfOWuuyBwpyoAYI27Wy52cZK s2S8g2ySpkRMWVd/zWZntpDB8gYgE8qeZ2tC9+P8Xe651jcL4T3edcU/UuQVxjJ8hJcq Db9QAAwEgW8hfdxCtLhkVyw1A0uXWutoTS1bQS/igWqjDkTxFxq81/5KMoeof6Z2CXG3 Im6g==
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:date :message-id:subject:from:to:cc; bh=cXhTDCFiGqQJunm567EO3NCmL5ZAxEpYPPpCLZL6FMY=; b=IzDMLM6S3UO2xr3nC8tdrnqjcizkNQ6w9rgngt7oIbkhqIa+MpnqvwK4IQi+NZ6AQr YGM8lRxWL3nlOh6Q3TIaiHugLlefzG7VFpyDxRVeXgHefvD6lUv9G9F38QaM6oQDXXNb uNrB2JKZ6iGC7Muz5xhe1Ly9t5flqGML0UhsbA1CEoiEDez0puc0EjDVhZ0MplmX57LN 2Ks+EU34tibozqJcWeLFzS6PMZvAaDu3KX7T/Wgb68O6uVpDct+F0W5FaDqWs9xvruUr W3VtRUEXml54yV/Gk9Gi8Y6LbrsIADu8wPFaPceiRCMO/GRCJMhh3PhXVxhfR6H/tHwh wRWA==
X-Gm-Message-State: AD7BkJIGaDphS2CEK/c59SFNNLhDUU1s46ZFBuJUDACPtbKgx8UUCa+e95bWC0hER0oZ3GWFNA4yc/0K1Ob9FA==
MIME-Version: 1.0
X-Received: by 10.28.29.84 with SMTP id d81mr14677181wmd.59.1460341465298; Sun, 10 Apr 2016 19:24:25 -0700 (PDT)
Received: by 10.194.133.99 with HTTP; Sun, 10 Apr 2016 19:24:25 -0700 (PDT)
In-Reply-To: <87twj99c6w.fsf@tops.chopps.org>
References: <0D914666-C3D4-4CCE-AD5E-4E5B34EA1A73@piuha.net> <20160407182936.GA21340@pfrc.org> <CAB75xn780nNDjGa_Cc222J20-+1CCHt09Xp8KHzaK=n0xx51pg@mail.gmail.com> <5706B100.9040509@mnt.se> <CAB75xn6fmj84ROUtG5eUB3GerHx83hrEr3w5vSADY_g=BRg5FA@mail.gmail.com> <5706BA40.3060005@mnt.se> <alpine.DEB.2.02.1604072157240.31096@uplift.swm.pp.se> <A9B63A6D-3102-482F-8FFC-2E57A5FD8336@nic.cz> <16925.1460122349@obiwan.sandelman.ca> <m27fg77zst.wl%randy@psg.com> <57097077.7040703@comcast.net> <m2fuuu75ls.wl%randy@psg.com> <87wpo5a8im.fsf@tops.chopps.org> <m260vp7eke.wl%randy@psg.com> <570A6458.3050206@comcast.net> <m21t6d7c9t.wl%randy@psg.com> <570A67B4.3010206@comcast.net> <570AB3AF.2050401@gmail.com> <87twj99c6w.fsf@tops.chopps.org>
Date: Mon, 11 Apr 2016 07:54:25 +0530
Message-ID: <CAKe6YvMyp-DyeDwpPY6KYmbDbnpgnvVk_cUStnA32wmgDWcz3w@mail.gmail.com>
Subject: Re: Concerns about Singapore
From: Vinayak Hegde <vinayakh@gmail.com>
To: chopps@chopps.org
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/6aRd69-UM2M1uG07wZHvOoph_l4>
Cc: IETF discussion list <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: Mon, 11 Apr 2016 02:24:28 -0000

On Mon, Apr 11, 2016 at 6:46 AM,  <chopps@chopps.org> wrote:
> It's certainly relevant to me, b/c I don't personally think that IETF
> meetings should be held in oppressive and censoring countries. I don't
> know how to articulate this well -- others are better at it -- but I
> certainly would like to skip any meetings that I feel violate IETFs
> value of openness so that I can at least vote with my feet and my
> dollars.

Well how does this work with Internet's (and IETF's) mission of
inclusiveness. Applying the same scale of "oppressiveness", I am
sure large parts of the world think the same about the US/UK which
has waged wars in Iraq, Afghanistan, Vietnam, Syria, Argentina
(our latest venue) and elsewhere.

The IETF doesn't seem to have a problem having meetings in
these countries. I hope the majority of participants on this list
realise that they are viewing the world through a western prism.

The notion of punishing the general populace for the mistakes of
their elected and unelected govt. seems wrong to me. Many times,
the general populace of the country is fighting their govt. through
the Internet. eg. Turkey.

-- Vinayak


From nobody Mon Apr 11 00:12:37 2016
Return-Path: <john-ietf@jck.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 108B512E7B6 for <ietf@ietfa.amsl.com>; Mon, 11 Apr 2016 00:12:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.896
X-Spam-Level: 
X-Spam-Status: No, score=-2.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.996] 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 UGHyMWNRFJJm for <ietf@ietfa.amsl.com>; Mon, 11 Apr 2016 00:12:34 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A667112E7A6 for <ietf@ietf.org>; Mon, 11 Apr 2016 00:12:34 -0700 (PDT)
Received: from [198.252.137.10] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1apW1R-000GZO-0u; Mon, 11 Apr 2016 03:12:33 -0400
Date: Mon, 11 Apr 2016 03:12:28 -0400
From: John C Klensin <john-ietf@jck.com>
To: Robert Withers <robert.w.withers@gmail.com>, ietf@ietf.org
Subject: Re: Concerns about Singapore
Message-ID: <9AA9661DC0C3747E2B467F44@JcK-HP8200.jck.com>
In-Reply-To: <FFA9507A-A1A6-42D9-8047-ADE81B6044EC@gmail.com>
References: <0D914666-C3D4-4CCE-AD5E-4E5B34EA1A73@piuha.net> <20160407182936.GA21340@pfrc.org> <CAB75xn780nNDjGa_Cc222J20-+1CCHt09Xp8KHzaK=n0xx51pg@mail.gmail.com> <5706B100.9040509@mnt.se> <CAB75xn6fmj84ROUtG5eUB3GerHx83hrEr3w5vSADY_g=BRg5FA@mail.gmail.com> <5706BA40.3060005@mnt.se> <alpine.DEB.2.02.1604072157240.31096@uplift.swm.pp.se> <A9B63A6D-3102-482F-8FFC-2E57A5FD8336@nic.cz> <16925.1460122349@obiwan.sandelman.ca> <m27fg77zst.wl%randy@psg.com> <57097077.7040703@comcast.net> <m2fuuu75ls.wl%randy@psg.com> <87wpo5a8im.fsf@tops.chopps.org> <m260vp7eke.wl%randy@psg.com> <570A6458.3050206@comcast.net> <m21t6d7c9t.wl%randy@psg.com> <570A67B4.3010206@comcast.net> <7060475F-E348-4BF0-B515-BB47143A2C24@puck.nether.net> <570A9A5F.6020906@gmail.com> <8295F54A-0A2B-4D89-9433-519F14F63C65@puck.nether.net> <FFA9507A-A1A6-42D9-8047-ADE81B6044EC@gmail.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/JRGgmwmIrspnTfssBk7dWOCJ6vc>
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: Mon, 11 Apr 2016 07:12:36 -0000

--On Sunday, April 10, 2016 19:15 -0400 Robert Withers
<robert.w.withers@gmail.com> wrote:

> Resending to the list...and an extra thought...
> 
> If censorship rights are managed in more granularity than
> nationally, perhaps the neighborhood or subdivision level, it
> allows variance and differentiation, including mixed access
> within an urban setting. The nation must be the union and
> membership in associations may carry censorship requirements
> limiting one's access by agreement. This sort of approach may
> be welcomed by those regimes with real concerns regarding
> 'westernization' of their media. Countries may well allow
> international conference attendees free access while
> simultaneously protecting their children from wanting to serve
> the local warlord rather than sticking to the local Civil
> Defense Unit. I believe the idea has merit, perhaps reducing
> slaughter.
>...

On the other hand, that same kind of granularity can be used
(and often has been) to allow unrestricted access to media and
content by members of elites (or those trusted to support the
parties in power) while restricting access by those less
favored, less trusted, or with different views.  Acceptance of
it does reduce slaughter too, but does so primarily by virtue of
the principle that those who avoid expressing dissent are much
less likely to be punished for dissenting than those who do
express it.

YMMD, but I'm not very happy about the direction in which the
argument above takes us.

    john






From nobody Mon Apr 11 01:05:26 2016
Return-Path: <aallen@blackberry.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 8F27B12D0C9 for <ietf@ietfa.amsl.com>; Mon, 11 Apr 2016 01:05:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.617
X-Spam-Level: 
X-Spam-Status: No, score=-3.617 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.996, SPF_PASS=-0.001] 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 jPPfOLufSPgt for <ietf@ietfa.amsl.com>; Mon, 11 Apr 2016 01:05:24 -0700 (PDT)
Received: from smtp-p02.blackberry.com (smtp-p02.blackberry.com [208.65.78.89]) by ietfa.amsl.com (Postfix) with ESMTP id A3C5612E6AB for <ietf@ietf.org>; Mon, 11 Apr 2016 01:05:20 -0700 (PDT)
Received: from smtp-pop.rim.net (HELO XCT104CNC.rim.net) ([10.65.161.204]) by mhs215cnc.rim.net with ESMTP/TLS/AES256-SHA; 11 Apr 2016 05:38:47 -0400
Received: from XMB122CNC.rim.net ([fe80::28c6:fa1c:91c6:2e23]) by XCT104CNC.rim.net ([::1]) with mapi id 14.03.0210.002; Mon, 11 Apr 2016 04:05:20 -0400
From: Andrew Allen <aallen@blackberry.com>
To: Vinayak Hegde <vinayakh@gmail.com>, "chopps@chopps.org" <chopps@chopps.org>
Subject: RE: Concerns about Singapore
Thread-Topic: Concerns about Singapore
Thread-Index: AQHRkOMNjufwcA4TvkK+5mik25hZRp9/GCcAgAAATwCAAAuKAIAACE6AgAACuQCAAAKSAIAAAg8AgAEj0YCAAXn+AIAAmSKAgAAdGICAAPYtgIAABOuAgAAKigCAAANOAIAAALMAgABak4CAAFUMgIAAEtyAgAAODvA=
Date: Mon, 11 Apr 2016 08:05:19 +0000
Message-ID: <BBF5DDFE515C3946BC18D733B20DAD233A62AA18@XMB122CNC.rim.net>
References: <0D914666-C3D4-4CCE-AD5E-4E5B34EA1A73@piuha.net> <20160407182936.GA21340@pfrc.org> <CAB75xn780nNDjGa_Cc222J20-+1CCHt09Xp8KHzaK=n0xx51pg@mail.gmail.com> <5706B100.9040509@mnt.se> <CAB75xn6fmj84ROUtG5eUB3GerHx83hrEr3w5vSADY_g=BRg5FA@mail.gmail.com> <5706BA40.3060005@mnt.se> <alpine.DEB.2.02.1604072157240.31096@uplift.swm.pp.se> <A9B63A6D-3102-482F-8FFC-2E57A5FD8336@nic.cz> <16925.1460122349@obiwan.sandelman.ca> <m27fg77zst.wl%randy@psg.com> <57097077.7040703@comcast.net> <m2fuuu75ls.wl%randy@psg.com> <87wpo5a8im.fsf@tops.chopps.org> <m260vp7eke.wl%randy@psg.com> <570A6458.3050206@comcast.net> <m21t6d7c9t.wl%randy@psg.com> <570A67B4.3010206@comcast.net> <570AB3AF.2050401@gmail.com> <87twj99c6w.fsf@tops.chopps.org> <CAKe6YvMyp-DyeDwpPY6KYmbDbnpgnvVk_cUStnA32wmgDWcz3w@mail.gmail.com>
In-Reply-To: <CAKe6YvMyp-DyeDwpPY6KYmbDbnpgnvVk_cUStnA32wmgDWcz3w@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.65.160.247]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/SQb8s6aTq6j0s4xpQZURgMcfy84>
Cc: IETF discussion list <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: Mon, 11 Apr 2016 08:05:25 -0000

VGhpcyBpcyB3aGF0IEkgbWVhbiBieSBzbGlwcGVyeSBzbG9wZSAtIG9uY2Ugd2UgZ28gZG93biB0
aGlzIHBhdGggaXQgbmV2ZXIgZW5kcyAtIGluIGEgZ2xvYmFsIGNvbW11bml0eSBvZiB3ZWxsIG92
ZXIgMTAwMCBhY3RpdmUgcGVvcGxlIGF0IGxlYXN0IG9uZSBwZXJzb24gaXMgbGlrZWx5IHRvIGhh
dmUgYSBwcm9ibGVtIHdpdGggc29tZSBhc3BlY3Qgb2YgbW9zdCBvZiB0aGUgY291bnRyaWVzIGdv
dmVybm1lbnRzLCBwb2xpY2llcywgY3VsdHVyZXMgb3IgYWN0aW9ucywgZXRjLg0KDQpXZSBjb3Vs
ZCBiZSBsZWZ0IHdpdGggdGhlIG9ubHkgcG9zc2libGUgdmVudWUgYmVpbmcgYSBjcnVpc2Ugc2hp
cCBzYWlsaW5nIGluIGludGVybmF0aW9uYWwgd2F0ZXJzIC0gYnV0IHRoZW4gc29tZW9uZSB3aWxs
IHByb2JhYmx5IG9iamVjdCBiZWNhdXNlIHRoZSBzaGlwIGlzIHJlZ2lzdGVyZWQgaW4gUGFuYW1h
IG9yIExpYmVyaWEhDQoNClRoZSBmb2N1cyBzaG91bGQgYmUgb24gY2hvb3NpbmcgYSBsb2NhdGlv
biBmb3IgdGhlIG1lZXRpbmcgdGhhdCBpcyBvcGVuIGZvciBhbGwgdG8gYXR0ZW5kIGFuZCB3aGVy
ZSBpdCBpcyByZWFzb25hYmx5IHNhZmUgdG8gYXR0ZW5kIGFuZCBtZWV0cyB0aGUgbmVlZHMgb2Yg
YSBtZWV0aW5nIGZvciBhIGxhcmdlIG51bWJlciBvZiBwZW9wbGUgYW5kIHJlcHJlc2VudHMgdGhl
IHJlZ2lvbmFsIGJhbGFuY2Ugb2YgdGhlIG1lbWJlcnNoaXAuIA0KDQpUaGUgbWlzc2lvbiBvZiB0
aGUgSUVURiBpcyB0byBtYWtlIHRoZSBJbnRlcm5ldCB3b3JrIGJldHRlciBieSBwcm9kdWNpbmcg
aGlnaCBxdWFsaXR5LCByZWxldmFudCB0ZWNobmljYWwgZG9jdW1lbnRzIHRoYXQgaW5mbHVlbmNl
IHRoZSB3YXkgcGVvcGxlIGRlc2lnbiwgdXNlLCBhbmQgbWFuYWdlIHRoZSBJbnRlcm5ldC4NCg0K
VGhlIElFVEYgaXMgbm90IGFuIG9yZ2FuaXphdGlvbiB0aGF0J3MgbWlzc2lvbiBpcyB0byBiZSBh
biBhZHZvY2F0ZSBmb3IgZ2xvYmFsIHNvY2lhbCwgZW52aXJvbm1lbnRhbCBvciBwb2xpdGljYWwg
Y2hhbmdlLiBUaGUgc2VsZWN0aW9uIG9mIGEgbWVldGluZyBsb2NhdGlvbiBzaG91bGQgYmUgZm9y
IHRoZSBwdXJwb3NlcyBvZiBhZHZhbmNpbmcgdGhlIElFVEYncyBtaXNzaW9uLiBJIHRoaW5rIHNv
bWUgb2YgdGhlIGNvbmNlcm5zIHJhaXNlZCBhYm91dCBTaW5nYXBvcmUgbmVlZCB0byBiZSBhZGRy
ZXNzZWQgaW4gdGVybXMgb2YgdGhlIHByYWN0aWNhbCBpbXBhY3QgYW5kIHJpc2sgdG8gdGhlIGF0
dGVuZGFuY2Ugb2Ygc29tZSBpbiB0aGUgSUVURiBjb21tdW5pdHkgYnV0IHdlIHNob3VsZG7igJl0
IHN0YXJ0IGRvd24gdGhlIHJvYWQgb2YgY2hvb3Npbmcgb3Igbm90IGNob29zaW5nIG1lZXRpbmcg
bG9jYXRpb25zIGJhc2VkIG9uIGFuIGV2YWx1YXRpb24gb2YgYSBjb3VudHJpZXMgbGF3cywgY3Vs
dHVyZSBhbmQgcG9saWNpZXMgYW5kIHdoZXRoZXIgdGhvc2UgYXJlIGFjY2VwdGFibGUgdG8gYWxs
IG9yIG1vc3Qgb2YgdGhlIGNvbW11bml0eS4NCg0KRGViYXRlcyBvdmVyIHdoZXRoZXIgYSBsb2Nh
dGlvbiBpcyBwb2xpdGljYWxseSBvciBtb3JhbGx5IGFjY2VwdGFibGUgd2lsbCBvbmx5IGRpc3Ry
YWN0IGZyb20gdGhlIG1pc3Npb24gb2YgdGhlIElFVEYgYW5kIGxpa2VseSBkaXZpZGUgdGhlIGNv
bW11bml0eSByYXRoZXIgdGhhbiBoZWxwIGluIG1ha2luZyBwcm9ncmVzcyB0b3dhcmRzIGZvcm1p
bmcgY29uc2Vuc3VzIG9uIHRoZSBmdXR1cmUgZGV2ZWxvcG1lbnQgb2YgdGhlIGludGVybmV0Lg0K
DQpBbmRyZXcNCg0KLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCkZyb206IGlldGYgW21haWx0
bzppZXRmLWJvdW5jZXNAaWV0Zi5vcmddIE9uIEJlaGFsZiBPZiBWaW5heWFrIEhlZ2RlDQpTZW50
OiBTdW5kYXksIEFwcmlsIDEwLCAyMDE2IDEwOjI0IFBNDQpUbzogY2hvcHBzQGNob3Bwcy5vcmcN
CkNjOiBJRVRGIGRpc2N1c3Npb24gbGlzdCA8aWV0ZkBpZXRmLm9yZz4NClN1YmplY3Q6IFJlOiBD
b25jZXJucyBhYm91dCBTaW5nYXBvcmUNCg0KT24gTW9uLCBBcHIgMTEsIDIwMTYgYXQgNjo0NiBB
TSwgIDxjaG9wcHNAY2hvcHBzLm9yZz4gd3JvdGU6DQo+IEl0J3MgY2VydGFpbmx5IHJlbGV2YW50
IHRvIG1lLCBiL2MgSSBkb24ndCBwZXJzb25hbGx5IHRoaW5rIHRoYXQgSUVURiANCj4gbWVldGlu
Z3Mgc2hvdWxkIGJlIGhlbGQgaW4gb3BwcmVzc2l2ZSBhbmQgY2Vuc29yaW5nIGNvdW50cmllcy4g
SSBkb24ndCANCj4ga25vdyBob3cgdG8gYXJ0aWN1bGF0ZSB0aGlzIHdlbGwgLS0gb3RoZXJzIGFy
ZSBiZXR0ZXIgYXQgaXQgLS0gYnV0IEkgDQo+IGNlcnRhaW5seSB3b3VsZCBsaWtlIHRvIHNraXAg
YW55IG1lZXRpbmdzIHRoYXQgSSBmZWVsIHZpb2xhdGUgSUVURnMgDQo+IHZhbHVlIG9mIG9wZW5u
ZXNzIHNvIHRoYXQgSSBjYW4gYXQgbGVhc3Qgdm90ZSB3aXRoIG15IGZlZXQgYW5kIG15IA0KPiBk
b2xsYXJzLg0KDQpXZWxsIGhvdyBkb2VzIHRoaXMgd29yayB3aXRoIEludGVybmV0J3MgKGFuZCBJ
RVRGJ3MpIG1pc3Npb24gb2YgaW5jbHVzaXZlbmVzcy4gQXBwbHlpbmcgdGhlIHNhbWUgc2NhbGUg
b2YgIm9wcHJlc3NpdmVuZXNzIiwgSSBhbSBzdXJlIGxhcmdlIHBhcnRzIG9mIHRoZSB3b3JsZCB0
aGluayB0aGUgc2FtZSBhYm91dCB0aGUgVVMvVUsgd2hpY2ggaGFzIHdhZ2VkIHdhcnMgaW4gSXJh
cSwgQWZnaGFuaXN0YW4sIFZpZXRuYW0sIFN5cmlhLCBBcmdlbnRpbmEgKG91ciBsYXRlc3QgdmVu
dWUpIGFuZCBlbHNld2hlcmUuDQoNClRoZSBJRVRGIGRvZXNuJ3Qgc2VlbSB0byBoYXZlIGEgcHJv
YmxlbSBoYXZpbmcgbWVldGluZ3MgaW4gdGhlc2UgY291bnRyaWVzLiBJIGhvcGUgdGhlIG1ham9y
aXR5IG9mIHBhcnRpY2lwYW50cyBvbiB0aGlzIGxpc3QgcmVhbGlzZSB0aGF0IHRoZXkgYXJlIHZp
ZXdpbmcgdGhlIHdvcmxkIHRocm91Z2ggYSB3ZXN0ZXJuIHByaXNtLg0KDQpUaGUgbm90aW9uIG9m
IHB1bmlzaGluZyB0aGUgZ2VuZXJhbCBwb3B1bGFjZSBmb3IgdGhlIG1pc3Rha2VzIG9mIHRoZWly
IGVsZWN0ZWQgYW5kIHVuZWxlY3RlZCBnb3Z0LiBzZWVtcyB3cm9uZyB0byBtZS4gTWFueSB0aW1l
cywgdGhlIGdlbmVyYWwgcG9wdWxhY2Ugb2YgdGhlIGNvdW50cnkgaXMgZmlnaHRpbmcgdGhlaXIg
Z292dC4gdGhyb3VnaCB0aGUgSW50ZXJuZXQuIGVnLiBUdXJrZXkuDQoNCi0tIFZpbmF5YWsNCg0K


From nobody Mon Apr 11 02:34:56 2016
Return-Path: <andrew.hutton@unify.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 A08A212EA62 for <ietf@ietfa.amsl.com>; Mon, 11 Apr 2016 02:34:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.216
X-Spam-Level: 
X-Spam-Status: No, score=-1.216 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.996, URIBL_BLACK=1.7] autolearn=no 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 pggv23lOekWy for <ietf@ietfa.amsl.com>; Mon, 11 Apr 2016 02:34:52 -0700 (PDT)
Received: from mx12.unify.com (mx12.unify.com [62.134.46.10]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7A7EC12EA63 for <ietf@ietf.org>; Mon, 11 Apr 2016 02:34:52 -0700 (PDT)
Received: from MCHP02HTC.global-ad.net (unknown [172.29.42.235]) by mx12.unify.com (Server) with ESMTP id AF80B23F0460; Mon, 11 Apr 2016 11:34:50 +0200 (CEST)
Received: from MCHP04MSX.global-ad.net ([169.254.37.243]) by MCHP02HTC.global-ad.net ([172.29.42.235]) with mapi id 14.03.0279.002; Mon, 11 Apr 2016 11:34:50 +0200
From: "Hutton, Andrew" <andrew.hutton@unify.com>
To: Andrew Allen <aallen@blackberry.com>
Subject: Re: Concerns about Singapore
Thread-Topic: Concerns about Singapore
Thread-Index: AQHRklgXVOzdo7TotESuyZpJrFoKvJ9/GCcAgAAATwCAAAuKAIAACE6AgAACuQCAAAKSAIAAAg8AgAEj0YCAAXn+AIAAmSKAgAAdGICAAPYtgIAABOuAgAAKigCAAANOAIAAALMAgABak4CAAFUMgIAAEtyAgAAODvCAACQ7QQ==
Date: Mon, 11 Apr 2016 09:34:49 +0000
Message-ID: <7AD254D8-730E-413D-ADDC-A42DAD873976@unify.com>
References: <0D914666-C3D4-4CCE-AD5E-4E5B34EA1A73@piuha.net> <20160407182936.GA21340@pfrc.org> <CAB75xn780nNDjGa_Cc222J20-+1CCHt09Xp8KHzaK=n0xx51pg@mail.gmail.com> <5706B100.9040509@mnt.se> <CAB75xn6fmj84ROUtG5eUB3GerHx83hrEr3w5vSADY_g=BRg5FA@mail.gmail.com> <5706BA40.3060005@mnt.se> <alpine.DEB.2.02.1604072157240.31096@uplift.swm.pp.se> <A9B63A6D-3102-482F-8FFC-2E57A5FD8336@nic.cz> <16925.1460122349@obiwan.sandelman.ca> <m27fg77zst.wl%randy@psg.com> <57097077.7040703@comcast.net> <m2fuuu75ls.wl%randy@psg.com> <87wpo5a8im.fsf@tops.chopps.org> <m260vp7eke.wl%randy@psg.com> <570A6458.3050206@comcast.net> <m21t6d7c9t.wl%randy@psg.com> <570A67B4.3010206@comcast.net> <570AB3AF.2050401@gmail.com> <87twj99c6w.fsf@tops.chopps.org> <CAKe6YvMyp-DyeDwpPY6KYmbDbnpgnvVk_cUStnA32wmgDWcz3w@mail.gmail.com>, <BBF5DDFE515C3946BC18D733B20DAD233A62AA18@XMB122CNC.rim.net>
In-Reply-To: <BBF5DDFE515C3946BC18D733B20DAD233A62AA18@XMB122CNC.rim.net>
Accept-Language: en-US
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/Tyin4Wg9I9Ja9Xclr-3OIihVzjM>
Cc: IETF discussion list <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: Mon, 11 Apr 2016 09:34:54 -0000

I agree 100% with Andrew's view.

Regards
Andy

> On 11 Apr 2016, at 09:05, Andrew Allen <aallen@blackberry.com> wrote:
>=20
> This is what I mean by slippery slope - once we go down this path it neve=
r ends - in a global community of well over 1000 active people at least one=
 person is likely to have a problem with some aspect of most of the countri=
es governments, policies, cultures or actions, etc.
>=20
> We could be left with the only possible venue being a cruise ship sailing=
 in international waters - but then someone will probably object because th=
e ship is registered in Panama or Liberia!
>=20
> The focus should be on choosing a location for the meeting that is open f=
or all to attend and where it is reasonably safe to attend and meets the ne=
eds of a meeting for a large number of people and represents the regional b=
alance of the membership.=20
>=20
> The mission of the IETF is to make the Internet work better by producing =
high quality, relevant technical documents that influence the way people de=
sign, use, and manage the Internet.
>=20
> The IETF is not an organization that's mission is to be an advocate for g=
lobal social, environmental or political change. The selection of a meeting=
 location should be for the purposes of advancing the IETF's mission. I thi=
nk some of the concerns raised about Singapore need to be addressed in term=
s of the practical impact and risk to the attendance of some in the IETF co=
mmunity but we shouldn=92t start down the road of choosing or not choosing =
meeting locations based on an evaluation of a countries laws, culture and p=
olicies and whether those are acceptable to all or most of the community.
>=20
> Debates over whether a location is politically or morally acceptable will=
 only distract from the mission of the IETF and likely divide the community=
 rather than help in making progress towards forming consensus on the futur=
e development of the internet.
>=20
> Andrew
>=20
> -----Original Message-----
> From: ietf [mailto:ietf-bounces@ietf.org] On Behalf Of Vinayak Hegde
> Sent: Sunday, April 10, 2016 10:24 PM
> To: chopps@chopps.org
> Cc: IETF discussion list <ietf@ietf.org>
> Subject: Re: Concerns about Singapore
>=20
>> On Mon, Apr 11, 2016 at 6:46 AM,  <chopps@chopps.org> wrote:
>> It's certainly relevant to me, b/c I don't personally think that IETF=20
>> meetings should be held in oppressive and censoring countries. I don't=20
>> know how to articulate this well -- others are better at it -- but I=20
>> certainly would like to skip any meetings that I feel violate IETFs=20
>> value of openness so that I can at least vote with my feet and my=20
>> dollars.
>=20
> Well how does this work with Internet's (and IETF's) mission of inclusive=
ness. Applying the same scale of "oppressiveness", I am sure large parts of=
 the world think the same about the US/UK which has waged wars in Iraq, Afg=
hanistan, Vietnam, Syria, Argentina (our latest venue) and elsewhere.
>=20
> The IETF doesn't seem to have a problem having meetings in these countrie=
s. I hope the majority of participants on this list realise that they are v=
iewing the world through a western prism.
>=20
> The notion of punishing the general populace for the mistakes of their el=
ected and unelected govt. seems wrong to me. Many times, the general popula=
ce of the country is fighting their govt. through the Internet. eg. Turkey.
>=20
> -- Vinayak
>=20


From nobody Mon Apr 11 03:23:47 2016
Return-Path: <stephen.farrell@cs.tcd.ie>
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 1A6F212EB8B for <ietf@ietfa.amsl.com>; Mon, 11 Apr 2016 03:23:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.297
X-Spam-Level: 
X-Spam-Status: No, score=-5.297 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.996, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cs.tcd.ie
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 olT83NkdKOva for <ietf@ietfa.amsl.com>; Mon, 11 Apr 2016 03:23:44 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1E3DA12EB88 for <ietf@ietf.org>; Mon, 11 Apr 2016 03:23:42 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 50AFEBE2F; Mon, 11 Apr 2016 11:23:34 +0100 (IST)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vvuNmJB6qSVF; Mon, 11 Apr 2016 11:23:33 +0100 (IST)
Received: from [10.87.49.100] (unknown [86.46.23.241]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 2C49CBDF9; Mon, 11 Apr 2016 11:23:31 +0100 (IST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; s=mail; t=1460370211; bh=PDBGIDrK/2p0VPhfI/c1u87XYLjQ0SfAoiAo1CKjcQs=; h=Subject:To:References:Cc:From:Date:In-Reply-To:From; b=xoSqGn3S60xt46Z8UztGl00Ag/r2rbYLhLpWyX4a+vgHat3jO/mTf1fYbWBplnC7Z T1lGfPCwQ1JqaASMYNf49GJC7SC8zKYwNELdnfAXcrOLaZuteniYbBJCZyRhiMj2Y1 bebZ/VH1rJdJJ1fvDVUireWr2dC/bmvUOqkmpK1E=
Subject: Re: Concerns about Singapore
To: Andrew Allen <aallen@blackberry.com>, Vinayak Hegde <vinayakh@gmail.com>,  "chopps@chopps.org" <chopps@chopps.org>
References: <0D914666-C3D4-4CCE-AD5E-4E5B34EA1A73@piuha.net> <20160407182936.GA21340@pfrc.org> <CAB75xn780nNDjGa_Cc222J20-+1CCHt09Xp8KHzaK=n0xx51pg@mail.gmail.com> <5706B100.9040509@mnt.se> <CAB75xn6fmj84ROUtG5eUB3GerHx83hrEr3w5vSADY_g=BRg5FA@mail.gmail.com> <5706BA40.3060005@mnt.se> <alpine.DEB.2.02.1604072157240.31096@uplift.swm.pp.se> <A9B63A6D-3102-482F-8FFC-2E57A5FD8336@nic.cz> <16925.1460122349@obiwan.sandelman.ca> <m27fg77zst.wl%randy@psg.com> <57097077.7040703@comcast.net> <m2fuuu75ls.wl%randy@psg.com> <87wpo5a8im.fsf@tops.chopps.org> <m260vp7eke.wl%randy@psg.com> <570A6458.3050206@comcast.net> <m21t6d7c9t.wl%randy@psg.com> <570A67B4.3010206@comcast.net> <570AB3AF.2050401@gmail.com> <87twj99c6w.fsf@tops.chopps.org> <CAKe6YvMyp-DyeDwpPY6KYmbDbnpgnvVk_cUStnA32wmgDWcz3w@mail.gmail.com> <BBF5DDFE515C3946BC18D733B20DAD233A62AA18@XMB122CNC.rim.net>
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Openpgp: id=D66EA7906F0B897FB2E97D582F3C8736805F8DA2; url=
Message-ID: <570B7B22.90801@cs.tcd.ie>
Date: Mon, 11 Apr 2016 11:23:30 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0
MIME-Version: 1.0
In-Reply-To: <BBF5DDFE515C3946BC18D733B20DAD233A62AA18@XMB122CNC.rim.net>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha-256; boundary="------------ms030107030602040609070504"
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/7ra5iDRaARwGEVm0UbwWUhGqV2k>
Cc: IETF discussion list <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: Mon, 11 Apr 2016 10:23:46 -0000

This is a cryptographically signed message in MIME format.

--------------ms030107030602040609070504
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable



On 11/04/16 09:05, Andrew Allen wrote:
> Debates over whether a location is politically or morally acceptable
> will only distract from the mission of the IETF and likely divide the
> community rather than help in making progress towards forming
> consensus on the future development of the internet.

I almost but don't agree with the above. The danger of such debates
dividing folks and being a barrier to progress is real. OTOH, there
are also dangers in the lack of such debate, or if the debate is post
facto, as happened in this case.

I think the lesson the IAOC ought learn here is to switch to a
default-open mode of operation where only those things that really
need to be kept confidential are kept confidential. (Note that I
don't only mean for f2f meeting arrangements but for all of what the
IAOC do.) That will require them (or someone) to go figure out (with
the community) which kinds of things really do need to be kept
confidential, and which can be done openly, in the normal IETF way.

I'd be fine if the IAOC announced that they will be doing the above
but also said we weren't going to work out the details until after
they have figured out whatever it is they end up doing about IETF-100.

Cheers,
S.



--------------ms030107030602040609070504
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIAGCSqGSIb3DQEHAqCAMIACAQExDzANBglghkgBZQMEAgEFADCABgkqhkiG9w0BBwEAAKCC
CvIwggUIMIID8KADAgECAhBPzaE7pzYviUJyhmHTFBdnMA0GCSqGSIb3DQEBCwUAMHUxCzAJ
BgNVBAYTAklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSkwJwYDVQQLEyBTdGFydENvbSBD
ZXJ0aWZpY2F0aW9uIEF1dGhvcml0eTEjMCEGA1UEAxMaU3RhcnRDb20gQ2xhc3MgMSBDbGll
bnQgQ0EwHhcNMTYwMjA5MDkyODE1WhcNMTcwMjA5MDkyODE1WjBOMSIwIAYDVQQDDBlzdGVw
aGVuLmZhcnJlbGxAY3MudGNkLmllMSgwJgYJKoZIhvcNAQkBFhlzdGVwaGVuLmZhcnJlbGxA
Y3MudGNkLmllMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAtuC0rYze/2JinSra
C9F2RjGdQZjNALLcW9C3WKTwYII3wBslobmHuPEYE5JaGItmzuKnAW619R1rD/kfoNWC19N3
rBZ6UX9Cmb9D9exCwYIwVuSwjrCQWGxgCtNQTrwKzCCpI790GRiMTvxvO7UmzmBrCaBLiZW5
R0fBjK5Yn6hUhAzGBkNbkIEL28cLJqH0yVz7Kl92OlzrQqTPEts5m6cDnNdY/ADfeAX18c1r
dxZqcAxhLotrCqgsVA4ilbQDMMXGTLlB5TP35HeWZuGBU7xu003rLcFLdOkD8xvpJoYZy9Kt
3oABXPS5yqtMK+XCNdqmMn+4mOtLwQSMmPCSiQIDAQABo4IBuTCCAbUwCwYDVR0PBAQDAgSw
MB0GA1UdJQQWMBQGCCsGAQUFBwMCBggrBgEFBQcDBDAJBgNVHRMEAjAAMB0GA1UdDgQWBBQJ
QhvwQ5Fl372Z6xqo6fdn8XejTTAfBgNVHSMEGDAWgBQkgWw5Yb5JD4+3G0YrySi1J0htaDBv
BggrBgEFBQcBAQRjMGEwJAYIKwYBBQUHMAGGGGh0dHA6Ly9vY3NwLnN0YXJ0c3NsLmNvbTA5
BggrBgEFBQcwAoYtaHR0cDovL2FpYS5zdGFydHNzbC5jb20vY2VydHMvc2NhLmNsaWVudDEu
Y3J0MDgGA1UdHwQxMC8wLaAroCmGJ2h0dHA6Ly9jcmwuc3RhcnRzc2wuY29tL3NjYS1jbGll
bnQxLmNybDAkBgNVHREEHTAbgRlzdGVwaGVuLmZhcnJlbGxAY3MudGNkLmllMCMGA1UdEgQc
MBqGGGh0dHA6Ly93d3cuc3RhcnRzc2wuY29tLzBGBgNVHSAEPzA9MDsGCysGAQQBgbU3AQIE
MCwwKgYIKwYBBQUHAgEWHmh0dHA6Ly93d3cuc3RhcnRzc2wuY29tL3BvbGljeTANBgkqhkiG
9w0BAQsFAAOCAQEArzrSv2C8PlBBmGuiGrzm2Wma46/KHtXmZYS0bsd43pM66Pc/MsqPE0HD
C1GzMFfwB6BfkJn8ijNSIhlgj898WzjvnpM/SO8KStjlB8719ig/xKISrOl5mX55XbFlQtX9
U6MrqRgbDIATxhD9IDr+ryvovDzChqgQj7mt2jYr4mdlRjsjod3H1VY6XglRmaaNGZfsCARM
aE/TU5SXIiqauwt5KxNGYAY67QkOBs7O1FkSXpTk7+1MmzJMF4nP8QQ5n8vhVNseF+/Wm7ai
9mtnrkLbaznMsy/ULo/C2yuLUWTbZZbf4EKNmVdme6tUDgYkFjAFOblfA7W1fSPiQGagYzCC
BeIwggPKoAMCAQICEGunin0K14jWUQr5WeTntOEwDQYJKoZIhvcNAQELBQAwfTELMAkGA1UE
BhMCSUwxFjAUBgNVBAoTDVN0YXJ0Q29tIEx0ZC4xKzApBgNVBAsTIlNlY3VyZSBEaWdpdGFs
IENlcnRpZmljYXRlIFNpZ25pbmcxKTAnBgNVBAMTIFN0YXJ0Q29tIENlcnRpZmljYXRpb24g
QXV0aG9yaXR5MB4XDTE1MTIxNjAxMDAwNVoXDTMwMTIxNjAxMDAwNVowdTELMAkGA1UEBhMC
SUwxFjAUBgNVBAoTDVN0YXJ0Q29tIEx0ZC4xKTAnBgNVBAsTIFN0YXJ0Q29tIENlcnRpZmlj
YXRpb24gQXV0aG9yaXR5MSMwIQYDVQQDExpTdGFydENvbSBDbGFzcyAxIENsaWVudCBDQTCC
ASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAL192vfDon2D9luC/dtbX64eG3XAtRmv
mCSsu1d52DXsCR58zJQbCtB2/A5uFqNxWacpXGGtTCRk9dEDBlmixEd8QiLkUfvHpJX/xKnm
VkS6Iye8wUbYzMsDzgnpazlPg19dnSqfhM+Cevdfa89VLnUztRr2cgmCfyO9Otrh7LJDPG+4
D8ZnAqDtVB8MKYJL6QgKyVhhaBc4y3bGWxKyXEtx7QIZZGxPwSkzK3WIN+VKNdkiwTubW5PI
dopmykwvIjLPqbJK7yPwFZYekKE015OsW6FV+s4DIM8UlVS8pkIsoGGJtMuWjLL4tq2hYQuu
N0jhrxK1ljz50hH23gA9cbMCAwEAAaOCAWQwggFgMA4GA1UdDwEB/wQEAwIBBjAdBgNVHSUE
FjAUBggrBgEFBQcDAgYIKwYBBQUHAwQwEgYDVR0TAQH/BAgwBgEB/wIBADAyBgNVHR8EKzAp
MCegJaAjhiFodHRwOi8vY3JsLnN0YXJ0c3NsLmNvbS9zZnNjYS5jcmwwZgYIKwYBBQUHAQEE
WjBYMCQGCCsGAQUFBzABhhhodHRwOi8vb2NzcC5zdGFydHNzbC5jb20wMAYIKwYBBQUHMAKG
JGh0dHA6Ly9haWEuc3RhcnRzc2wuY29tL2NlcnRzL2NhLmNydDAdBgNVHQ4EFgQUJIFsOWG+
SQ+PtxtGK8kotSdIbWgwHwYDVR0jBBgwFoAUTgvvGqRAW6UXaYcwyjRoQ9BBrvIwPwYDVR0g
BDgwNjA0BgRVHSAAMCwwKgYIKwYBBQUHAgEWHmh0dHA6Ly93d3cuc3RhcnRzc2wuY29tL3Bv
bGljeTANBgkqhkiG9w0BAQsFAAOCAgEAi+P3h+wBi4StDwECW5zhIycjBL008HACblIf26HY
0JdOruKbrWDsXUsiI0j/7Crft9S5oxvPiDtVqspBOB/y5uzSns1lZwh7sG96bYBZpcGzGxpF
NjDmQbcM3yl3WFIRS4WhNrsOY14V7y2IrUGsvetsD+bjyOngCIVeC/GmsmtbuLOzJ606tEc9
uRbhjTu/b0x2Fo+/e7UkQvKzNeo7OMhijixaULyINBfCBJb+e29bLafgu6JqjOUJ9eXXj20p
6q/CW+uVrZiSW57+q5an2P2i7hP85jQJcy5j4HzA0rSiF3YPhKGAWUxKPMAVGgcYoXzWydOv
Z3UDsTDTagXpRDIKQLZo02wrlxY6iMFqvlzsemVf1odhQJmi7Eh5TbxI40kDGcBOBHhwnaOu
mZhLP+SWJQnjpLpSlUOj95uf1zo9oz9e0NgIJoz/tdfrBzez76xtDsK0KfUDHt1/q59BvDI7
RX6gVr0fQoCyMczNzCTcRXYHY0tq2J0oT+bsb6sH2b4WVWAiJKnSYaWDjdA70qHX4mq9MIjO
/ZskmSY8wtAk24orAc0vwXgYanqNsBX5Yv4sN4Z9VyrwMdLcusP7HJgRdAGKpkR2I9U4zEsN
JQJewM7S4Jalo1DyPrLpL2nTET8ZrSl5Utp1UeGp/2deoprGevfnxWB+vHNQiu85o6MxggPM
MIIDyAIBATCBiTB1MQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRDb20gTHRkLjEpMCcG
A1UECxMgU3RhcnRDb20gQ2VydGlmaWNhdGlvbiBBdXRob3JpdHkxIzAhBgNVBAMTGlN0YXJ0
Q29tIENsYXNzIDEgQ2xpZW50IENBAhBPzaE7pzYviUJyhmHTFBdnMA0GCWCGSAFlAwQCAQUA
oIICEzAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0xNjA0MTEx
MDIzMzBaMC8GCSqGSIb3DQEJBDEiBCByKyoQk3vdT2LoexGcABeu+MI4QSBldjFOA+v958+t
DDBsBgkqhkiG9w0BCQ8xXzBdMAsGCWCGSAFlAwQBKjALBglghkgBZQMEAQIwCgYIKoZIhvcN
AwcwDgYIKoZIhvcNAwICAgCAMA0GCCqGSIb3DQMCAgFAMAcGBSsOAwIHMA0GCCqGSIb3DQMC
AgEoMIGaBgkrBgEEAYI3EAQxgYwwgYkwdTELMAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0
Q29tIEx0ZC4xKTAnBgNVBAsTIFN0YXJ0Q29tIENlcnRpZmljYXRpb24gQXV0aG9yaXR5MSMw
IQYDVQQDExpTdGFydENvbSBDbGFzcyAxIENsaWVudCBDQQIQT82hO6c2L4lCcoZh0xQXZzCB
nAYLKoZIhvcNAQkQAgsxgYyggYkwdTELMAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0Q29t
IEx0ZC4xKTAnBgNVBAsTIFN0YXJ0Q29tIENlcnRpZmljYXRpb24gQXV0aG9yaXR5MSMwIQYD
VQQDExpTdGFydENvbSBDbGFzcyAxIENsaWVudCBDQQIQT82hO6c2L4lCcoZh0xQXZzANBgkq
hkiG9w0BAQEFAASCAQCyzGteZuloXKGqhZnIyUJwSYUl5i9a5qw5UQb3t1QYDYhCPLnwo5gp
wV0I2NUgCFkvAtqahq841NAOEXK1Q8BrBSdysMPyqku2NdxuyRqHqh5I8xTIn3Ez/ZBnQ7KD
KcEmmKDYH/t+rrMZXYPRIDjedyE7lritlhYt3KOiOuVSiiyiB7OMHMd2BF83rfOH9ZhCpwpd
INTESOFsc4hj5AgKJTUt4Ks5NjGvD1q374b0LtX0mlvJOH4tPZchj1S9N+hs3qdwJiJjfV9i
tuGQDUv7tmo5VTSGJvP7nrspXcSY9mIrthI8V67G0cKnt9ujFDLSpph8kNshW4tjgGwGrGCD
AAAAAAAA
--------------ms030107030602040609070504--


From nobody Mon Apr 11 03:45:29 2016
Return-Path: <rsk@gsp.org>
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 3BE2812D1AD for <ietf@ietfa.amsl.com>; Mon, 11 Apr 2016 03:45:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] 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 A8zHUudxwV8o for <ietf@ietfa.amsl.com>; Mon, 11 Apr 2016 03:45:22 -0700 (PDT)
Received: from taos.firemountain.net (taos.firemountain.net [207.114.3.54]) (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 0FAB612D1E1 for <ietf@ietf.org>; Mon, 11 Apr 2016 03:45:21 -0700 (PDT)
Received: from gsp.org (localhost [127.0.0.1]) by taos.firemountain.net (8.15.1/8.14.9) with SMTP id u3BAjKaT008598 for <ietf@ietf.org>; Mon, 11 Apr 2016 06:45:20 -0400 (EDT)
Date: Mon, 11 Apr 2016 06:45:19 -0400
From: Rich Kulawiec <rsk@gsp.org>
To: ietf@ietf.org
Subject: Re: Concerns about Singapore
Message-ID: <20160411104519.GA19092@gsp.org>
References: <m2fuuu75ls.wl%randy@psg.com> <87wpo5a8im.fsf@tops.chopps.org> <m260vp7eke.wl%randy@psg.com> <570A6458.3050206@comcast.net> <m21t6d7c9t.wl%randy@psg.com> <570A67B4.3010206@comcast.net> <570AB3AF.2050401@gmail.com> <87twj99c6w.fsf@tops.chopps.org> <CAKe6YvMyp-DyeDwpPY6KYmbDbnpgnvVk_cUStnA32wmgDWcz3w@mail.gmail.com> <BBF5DDFE515C3946BC18D733B20DAD233A62AA18@XMB122CNC.rim.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <BBF5DDFE515C3946BC18D733B20DAD233A62AA18@XMB122CNC.rim.net>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/3XmnEfnyZVWGPdMguN6sx9t_l1o>
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: Mon, 11 Apr 2016 10:45:28 -0000

On Mon, Apr 11, 2016 at 08:05:19AM +0000, Andrew Allen wrote:
> We could be left with the only possible venue being a cruise ship
> sailing in international waters - [snip]

There is another alternative -- one I've raised repeatedly.

Don't have physical meetings.  Then this entire problem space simply
vanishes, along with the need for a discusion thread that's now over a
hundred messages.  (And it's not the first one.)  YES, it's replaced by a
different problem space, which roughly works out to "how can everything
be done virtually?"  but given that this is the *Internet* engineering
task force I have no doubt that the collective expertise is more than
capable of dealing with that.  Particularly if all the discussion, effort,
and expense going into the logistics of physical meetings is redirected
into virtual ones instead.

I really can't take any of the platitudes about "inclusion" seriously
until that happens -- because as long as the IETF persists with physical
meetings, most people *will* be excluded due to cost, distance, time,
legal climate, personal safety, etc.  The IETF is, even if accidentally,
selecting for the elite few who are fortunate enough to be attend.

---rsk


From nobody Mon Apr 11 05:17:48 2016
Return-Path: <ynir.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 A9B8C12ED56 for <ietf@ietfa.amsl.com>; Mon, 11 Apr 2016 05:17:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 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, RCVD_IN_DNSWL_LOW=-0.7, 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 xwgFsDHASvqC for <ietf@ietfa.amsl.com>; Mon, 11 Apr 2016 05:17:43 -0700 (PDT)
Received: from mail-wm0-x22d.google.com (mail-wm0-x22d.google.com [IPv6:2a00:1450:400c:c09::22d]) (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 7524B12EA84 for <ietf@ietf.org>; Mon, 11 Apr 2016 05:17:43 -0700 (PDT)
Received: by mail-wm0-x22d.google.com with SMTP id v188so83811774wme.1 for <ietf@ietf.org>; Mon, 11 Apr 2016 05:17:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=SLTJ+dxY2BajFqbsjBKq94nFV65Xq0WiL0giAAEW/r0=; b=vovA8Ci/8Izsr0vkAAM/eY9uNQTlZgtbZ+ocucITMqJkKmFFgxSVKlQ0IliFT3DJhF Dqaff0sqlpxHCTD4ggEOdxQW/BGRu4xVn7ENe/AwlGMbio4RWMWPZ9BS2wui2H2dHRLF kraGgHkzA2tF3dIZxJ9FkK7xXTP/+LSrMW++eOq2Ce5S2ttb+EvZ1t8lJI1g0ijQiEyC PLQ4mubR1Xo2mm4/dcVKgtFURRaYtiYJ4mydjaen9+0MXBA+INYfMICXAb6+eYSR0NHU 1GBnH3t/+oH1VNbS+oWQk1Mz6HA8PVx0o/cFOIlR3A5wcqz3k8TpnAiGawSCYuwZ1Oco RgcA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=SLTJ+dxY2BajFqbsjBKq94nFV65Xq0WiL0giAAEW/r0=; b=Sa6ditIClSV2hscwdCfo2OKp0P2X4sJ8nXtxn3iR1JPjaHNwkHXV/nGYPgBanfWg1d 7l+YaybrsfVkzaX5lItEkZGV33ELQI7oLNvpaVFQoQY3jSRaa0sC1X8Zd7zvYb9wE5+8 GV9WTtYmwpckrhWIi4/uBSDdoeKuQGdG6dcmW8iaQG4GN5Onu63li9aJjY0PxpzdOehq R2RJaFGFkX6bz9Do58R3OlxhYzGu/eOdgvWP1a8bpf94ZIFXpDabM/c1RBlE9Z1uim6r 3yJeJFrJFpi8NFo2c4HjxX3QbkEooBaVTTfs+vPpdFxPRqH2VjrqlP8HUZXEYA51k+km coQw==
X-Gm-Message-State: AD7BkJI3xJiimPIKYNQT9lvU+ilXEdlQCJ5U0IrLfV4bkxfKVM4ICIjBHFzYy4Wu3Lg4rg==
X-Received: by 10.194.111.229 with SMTP id il5mr26032979wjb.82.1460377061567;  Mon, 11 Apr 2016 05:17:41 -0700 (PDT)
Received: from [172.24.251.43] (dyn32-131.checkpoint.com. [194.29.32.131]) by smtp.gmail.com with ESMTPSA id k133sm4565856wmg.7.2016.04.11.05.17.40 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Mon, 11 Apr 2016 05:17:40 -0700 (PDT)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Subject: Re: Concerns about Singapore
From: Yoav Nir <ynir.ietf@gmail.com>
In-Reply-To: <20160411104519.GA19092@gsp.org>
Date: Mon, 11 Apr 2016 15:17:39 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <3F48466D-390C-4C18-B958-732AE3E46FF1@gmail.com>
References: <m2fuuu75ls.wl%randy@psg.com> <87wpo5a8im.fsf@tops.chopps.org> <m260vp7eke.wl%randy@psg.com> <570A6458.3050206@comcast.net> <m21t6d7c9t.wl%randy@psg.com> <570A67B4.3010206@comcast.net> <570AB3AF.2050401@gmail.com> <87twj99c6w.fsf@tops.chopps.org> <CAKe6YvMyp-DyeDwpPY6KYmbDbnpgnvVk_cUStnA32wmgDWcz3w@mail.gmail.com> <BBF5DDFE515C3946BC18D733B20DAD233A62AA18@XMB122CNC.rim.net> <20160411104519.GA19092@gsp.org>
To: Rich Kulawiec <rsk@gsp.org>
X-Mailer: Apple Mail (2.3124)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/-ZY4k9krDdXawJSgRXB9EHg9Igg>
Cc: 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: Mon, 11 Apr 2016 12:17:46 -0000

> On 11 Apr 2016, at 1:45 PM, Rich Kulawiec <rsk@gsp.org> wrote:
>=20
> On Mon, Apr 11, 2016 at 08:05:19AM +0000, Andrew Allen wrote:
>> We could be left with the only possible venue being a cruise ship
>> sailing in international waters - [snip]
>=20
> There is another alternative -- one I've raised repeatedly.
>=20
> Don't have physical meetings.  Then this entire problem space simply
> vanishes, along with the need for a discusion thread that's now over a
> hundred messages.  (And it's not the first one.)  YES, it's replaced =
by a
> different problem space, which roughly works out to "how can =
everything
> be done virtually?"  but given that this is the *Internet* engineering
> task force I have no doubt that the collective expertise is more than
> capable of dealing with that. =20

I don=E2=80=99t believe that this technology exists. People have been =
singing the praise of Meetecho in IETF 95, and yet remote participation =
is nothing like being in the room. And the =E2=80=9Cvirtual interim=E2=80=9D=
 meetings are nothing like physical meetings. There is a reason why =
airlines make great money from business travel and don=E2=80=99t shut =
down for the winter.

> Particularly if all the discussion, effort,
> and expense going into the logistics of physical meetings is =
redirected
> into virtual ones instead.

Yeah, perhaps, some day when we=E2=80=99re all wearing virtual reality =
headsets and our avatars are hanging out in a virtual venue, and we all =
have sufficient equipment and bandwidth to handle all that. We=E2=80=99re =
not there yet.

> I really can't take any of the platitudes about "inclusion" seriously
> until that happens -- because as long as the IETF persists with =
physical
> meetings, most people *will* be excluded due to cost, distance, time,
> legal climate, personal safety, etc.  The IETF is, even if =
accidentally,
> selecting for the elite few who are fortunate enough to be attend.

Virtual meetings with the technology we have today makes it very hard =
for people with mediocre English to follow the discussion. The =E2=80=9CI =
don=E2=80=99t quite follow what you=E2=80=99re saying=E2=80=9D look does =
not translate well to the kind of video we can use today. That extends =
even to people with relatively good English (for non-native speakers) =
like me.=20

Yoav=


From nobody Mon Apr 11 06:02:41 2016
Return-Path: <mellon@fugue.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 0FE6512ED66 for <ietf@ietfa.amsl.com>; Mon, 11 Apr 2016 06:02:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.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 VNAquDUhudX5 for <ietf@ietfa.amsl.com>; Mon, 11 Apr 2016 06:02:36 -0700 (PDT)
Received: from mail-lf0-x22e.google.com (mail-lf0-x22e.google.com [IPv6:2a00:1450:4010:c07::22e]) (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 D0A3912D0DF for <ietf@ietf.org>; Mon, 11 Apr 2016 06:02:35 -0700 (PDT)
Received: by mail-lf0-x22e.google.com with SMTP id e190so153898077lfe.0 for <ietf@ietf.org>; Mon, 11 Apr 2016 06:02:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=We51j/dp2gBWPcivmpqbzG0oRMgfjLX6gtmjI/hLFEM=; b=yg1fo2IeruDcjTqtzjmNYedup3u9BZzahDgmwln1gdswvZQ/1yQzzNcpCkqgyeAgGb caiVm39pTNgmet37vGwlWYbwemANeFAXPdKMyWDd+iAIfEK2Z/z+CXjaTNf5tTZLxZh3 eWJEa4N/VqXVHVUsCU0KgzJ26bs270cE3tzWP7BgGSmk8uRDGaDpmfHy13BfI8oVARvA GITdDmzD5Y2WXtkBSwC4f+TbTxQIBKKXu5+hdMpT8MZ5j7C+3nSxPjK7LSqb8+k/ea9d sgdYoIJbzsENwbMynHtyPW9vNcVu2tcaspR8VQi1GuO2xco7wcUSNi5mPG/v+f0s3uB2 ZKqw==
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=We51j/dp2gBWPcivmpqbzG0oRMgfjLX6gtmjI/hLFEM=; b=HwNTvIwQiMY/DFmkgMiOea023hG2l9CJu/in4xshihSzoJqtQxS8tPc0y8LPp9/RwJ 4tVXh9H7Dl+P1QbYivIgwhP2Y4v/MfbliyBksmEWyph0QPTUqEOJftpVsp6GIPTb0jea purueZI2NvNNovvX5EmscI6OJ0TlDKa3dtyv2+re0hBYRPSoxpkjYD9yVT9Z1IrbNnsS UrU1NyTEydKiDoqtw7hb679bZIcx74fTLF5X0BMpqKzEXPeOjwKMvaYBM4e/XbdxV1UV fiPdarb0oZvD6Vl605IIIPsyTikEhYypfQbHZuyolmq0ueO16TrLlTHvFQoEy8ovvnY6 Ww7w==
X-Gm-Message-State: AOPr4FUZU4AhlE6CnPuru9BMtvl5ANNDGTXAtig4c3IRQskES5MxEQm+HC6DEUA++8GJcZeuUewivoGmw2+HoQ==
X-Received: by 10.25.73.212 with SMTP id w203mr1540346lfa.22.1460379753783; Mon, 11 Apr 2016 06:02:33 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.25.40.136 with HTTP; Mon, 11 Apr 2016 06:01:53 -0700 (PDT)
X-Originating-IP: [71.233.41.235]
In-Reply-To: <3F48466D-390C-4C18-B958-732AE3E46FF1@gmail.com>
References: <m2fuuu75ls.wl%randy@psg.com> <87wpo5a8im.fsf@tops.chopps.org> <m260vp7eke.wl%randy@psg.com> <570A6458.3050206@comcast.net> <m21t6d7c9t.wl%randy@psg.com> <570A67B4.3010206@comcast.net> <570AB3AF.2050401@gmail.com> <87twj99c6w.fsf@tops.chopps.org> <CAKe6YvMyp-DyeDwpPY6KYmbDbnpgnvVk_cUStnA32wmgDWcz3w@mail.gmail.com> <BBF5DDFE515C3946BC18D733B20DAD233A62AA18@XMB122CNC.rim.net> <20160411104519.GA19092@gsp.org> <3F48466D-390C-4C18-B958-732AE3E46FF1@gmail.com>
From: Ted Lemon <mellon@fugue.com>
Date: Mon, 11 Apr 2016 09:01:53 -0400
Message-ID: <CAPt1N1kej35TSzDGH1QzNgJ9LvK2DMH-PFxDVUgvv_n_LPkvVw@mail.gmail.com>
Subject: Re: Concerns about Singapore
To: Yoav Nir <ynir.ietf@gmail.com>
Content-Type: multipart/alternative; boundary=001a114b1592763859053035283a
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/UxKDB056GcfjUM0cpRF3Uz38wag>
Cc: Rich Kulawiec <rsk@gsp.org>, ietf <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: Mon, 11 Apr 2016 13:02:40 -0000

--001a114b1592763859053035283a
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Also, if you live in a country with censorship, or with low bandwidth, it's
possible that the only way to attend an IETF meeting will be in person.
It would be nice if there were a bright line to draw on one side of which
is total inclusiveness, but there is not.   We need to make both kinds of
meeting work.

What Stephen said is right--the IAOC needs to systematically, rather than
informally, analyze what it is that needs to be done in confidence, and
expose the rest to public view.   I know this is non-trivial, and I do not
say this in the spirit of bashing the IAOC, who work very hard for us with
little reward other than our complaining.

If I were on the IAOC right now, I would be thinking about how to get off
of it.   I've been in the situation of having what seemed like a big chunk
of the IETF upset at me, and it's pretty soul-crushing.   Nevertheless, I
think what Stephen proposes is the thing the IAOC can do that is most
likely to prevent future woe of this kind.

On Mon, Apr 11, 2016 at 8:17 AM, Yoav Nir <ynir.ietf@gmail.com> wrote:

>
> > On 11 Apr 2016, at 1:45 PM, Rich Kulawiec <rsk@gsp.org> wrote:
> >
> > On Mon, Apr 11, 2016 at 08:05:19AM +0000, Andrew Allen wrote:
> >> We could be left with the only possible venue being a cruise ship
> >> sailing in international waters - [snip]
> >
> > There is another alternative -- one I've raised repeatedly.
> >
> > Don't have physical meetings.  Then this entire problem space simply
> > vanishes, along with the need for a discusion thread that's now over a
> > hundred messages.  (And it's not the first one.)  YES, it's replaced by=
 a
> > different problem space, which roughly works out to "how can everything
> > be done virtually?"  but given that this is the *Internet* engineering
> > task force I have no doubt that the collective expertise is more than
> > capable of dealing with that.
>
> I don=E2=80=99t believe that this technology exists. People have been sin=
ging the
> praise of Meetecho in IETF 95, and yet remote participation is nothing li=
ke
> being in the room. And the =E2=80=9Cvirtual interim=E2=80=9D meetings are=
 nothing like
> physical meetings. There is a reason why airlines make great money from
> business travel and don=E2=80=99t shut down for the winter.
>
> > Particularly if all the discussion, effort,
> > and expense going into the logistics of physical meetings is redirected
> > into virtual ones instead.
>
> Yeah, perhaps, some day when we=E2=80=99re all wearing virtual reality he=
adsets
> and our avatars are hanging out in a virtual venue, and we all have
> sufficient equipment and bandwidth to handle all that. We=E2=80=99re not =
there yet.
>
> > I really can't take any of the platitudes about "inclusion" seriously
> > until that happens -- because as long as the IETF persists with physica=
l
> > meetings, most people *will* be excluded due to cost, distance, time,
> > legal climate, personal safety, etc.  The IETF is, even if accidentally=
,
> > selecting for the elite few who are fortunate enough to be attend.
>
> Virtual meetings with the technology we have today makes it very hard for
> people with mediocre English to follow the discussion. The =E2=80=9CI don=
=E2=80=99t quite
> follow what you=E2=80=99re saying=E2=80=9D look does not translate well t=
o the kind of
> video we can use today. That extends even to people with relatively good
> English (for non-native speakers) like me.
>
> Yoav
>

--001a114b1592763859053035283a
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Also, if you live in a country with censorship, or with lo=
w bandwidth, it&#39;s possible that the only way to attend an IETF meeting =
will be in person. =C2=A0 It would be nice if there were a bright line to d=
raw on one side of which is total inclusiveness, but there is not. =C2=A0 W=
e need to make both kinds of meeting work.<div><br></div><div>What Stephen =
said is right--the IAOC needs to systematically, rather than informally, an=
alyze what it is that needs to be done in confidence, and expose the rest t=
o public view. =C2=A0 I know this is non-trivial, and I do not say this in =
the spirit of bashing the IAOC, who work very hard for us with little rewar=
d other than our complaining.</div><div><br></div><div>If I were on the IAO=
C right now, I would be thinking about how to get off of it. =C2=A0 I&#39;v=
e been in the situation of having what seemed like a big chunk of the IETF =
upset at me, and it&#39;s pretty soul-crushing. =C2=A0 Nevertheless, I thin=
k what Stephen proposes is the thing the IAOC can do that is most likely to=
 prevent future woe of this kind.</div></div><div class=3D"gmail_extra"><br=
><div class=3D"gmail_quote">On Mon, Apr 11, 2016 at 8:17 AM, Yoav Nir <span=
 dir=3D"ltr">&lt;<a href=3D"mailto:ynir.ietf@gmail.com" target=3D"_blank">y=
nir.ietf@gmail.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quot=
e" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">=
<span class=3D""><br>
&gt; On 11 Apr 2016, at 1:45 PM, Rich Kulawiec &lt;<a href=3D"mailto:rsk@gs=
p.org">rsk@gsp.org</a>&gt; wrote:<br>
&gt;<br>
&gt; On Mon, Apr 11, 2016 at 08:05:19AM +0000, Andrew Allen wrote:<br>
&gt;&gt; We could be left with the only possible venue being a cruise ship<=
br>
&gt;&gt; sailing in international waters - [snip]<br>
&gt;<br>
&gt; There is another alternative -- one I&#39;ve raised repeatedly.<br>
&gt;<br>
&gt; Don&#39;t have physical meetings.=C2=A0 Then this entire problem space=
 simply<br>
&gt; vanishes, along with the need for a discusion thread that&#39;s now ov=
er a<br>
&gt; hundred messages.=C2=A0 (And it&#39;s not the first one.)=C2=A0 YES, i=
t&#39;s replaced by a<br>
&gt; different problem space, which roughly works out to &quot;how can ever=
ything<br>
&gt; be done virtually?&quot;=C2=A0 but given that this is the *Internet* e=
ngineering<br>
&gt; task force I have no doubt that the collective expertise is more than<=
br>
&gt; capable of dealing with that.<br>
<br>
</span>I don=E2=80=99t believe that this technology exists. People have bee=
n singing the praise of Meetecho in IETF 95, and yet remote participation i=
s nothing like being in the room. And the =E2=80=9Cvirtual interim=E2=80=9D=
 meetings are nothing like physical meetings. There is a reason why airline=
s make great money from business travel and don=E2=80=99t shut down for the=
 winter.<br>
<span class=3D""><br>
&gt; Particularly if all the discussion, effort,<br>
&gt; and expense going into the logistics of physical meetings is redirecte=
d<br>
&gt; into virtual ones instead.<br>
<br>
</span>Yeah, perhaps, some day when we=E2=80=99re all wearing virtual reali=
ty headsets and our avatars are hanging out in a virtual venue, and we all =
have sufficient equipment and bandwidth to handle all that. We=E2=80=99re n=
ot there yet.<br>
<span class=3D""><br>
&gt; I really can&#39;t take any of the platitudes about &quot;inclusion&qu=
ot; seriously<br>
&gt; until that happens -- because as long as the IETF persists with physic=
al<br>
&gt; meetings, most people *will* be excluded due to cost, distance, time,<=
br>
&gt; legal climate, personal safety, etc.=C2=A0 The IETF is, even if accide=
ntally,<br>
&gt; selecting for the elite few who are fortunate enough to be attend.<br>
<br>
</span>Virtual meetings with the technology we have today makes it very har=
d for people with mediocre English to follow the discussion. The =E2=80=9CI=
 don=E2=80=99t quite follow what you=E2=80=99re saying=E2=80=9D look does n=
ot translate well to the kind of video we can use today. That extends even =
to people with relatively good English (for non-native speakers) like me.<b=
r>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
Yoav<br>
</font></span></blockquote></div><br></div>

--001a114b1592763859053035283a--


From nobody Mon Apr 11 06:38:42 2016
Return-Path: <Lee@asgard.org>
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 8870312E979 for <ietf@ietfa.amsl.com>; Mon, 11 Apr 2016 06:38:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.552
X-Spam-Level: 
X-Spam-Status: No, score=-1.552 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DATE_IN_PAST_12_24=1.049, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001] autolearn=no 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 4o1ApWPBjHvj for <ietf@ietfa.amsl.com>; Mon, 11 Apr 2016 06:38:39 -0700 (PDT)
Received: from atl4mhob11.myregisteredsite.com (atl4mhob11.myregisteredsite.com [209.17.115.49]) by ietfa.amsl.com (Postfix) with ESMTP id 56E9812E840 for <ietf@ietf.org>; Mon, 11 Apr 2016 06:38:39 -0700 (PDT)
Received: from mailpod.hostingplatform.com ([10.30.71.211]) by atl4mhob11.myregisteredsite.com (8.14.4/8.14.4) with ESMTP id u3BDcaZS032225 for <ietf@ietf.org>; Mon, 11 Apr 2016 09:38:36 -0400
Received: (qmail 5607 invoked by uid 0); 11 Apr 2016 13:38:36 -0000
X-TCPREMOTEIP: 204.235.115.162
X-Authenticated-UID: lee@asgard.org
Received: from unknown (HELO ?10.71.147.26?) (lee@asgard.org@204.235.115.162) by 0 with ESMTPA; 11 Apr 2016 13:38:35 -0000
User-Agent: Microsoft-MacOutlook/14.6.1.160122
Date: Sun, 10 Apr 2016 11:19:34 -0300
Subject: Re: "We did not know" is not a good excuse
From: Lee Howard <Lee@asgard.org>
To: <dcrocker@bbiw.net>, <adrian@olddog.co.uk>
Message-ID: <D32FE504.DD257%Lee@asgard.org>
Thread-Topic: "We did not know" is not a good excuse
References: <09ff01d1905c$f15d4e70$d417eb50$@olddog.co.uk> <5705C39E.30807@dcrocker.net> <0a5801d19086$79f40e30$6ddc2a90$@olddog.co.uk> <570677BC.9000900@dcrocker.net>
In-Reply-To: <570677BC.9000900@dcrocker.net>
Mime-version: 1.0
Content-type: text/plain; charset="ISO-8859-1"
Content-transfer-encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/Vbzk_plue99jL1XvsLtyB6XQR88>
Cc: 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: Mon, 11 Apr 2016 13:38:40 -0000

On 4/7/16, 12:07 PM, "ietf on behalf of Dave Crocker"
<ietf-bounces@ietf.org on behalf of dhc@dcrocker.net> wrote:

>On 4/6/2016 9:32 PM, Adrian Farrel wrote:
>> It may be true that the community could provide a list of vetoed and
>>approved
>> locations for the Meetings Committee to work with. That is a possible
>>approach.
>> Another approach might be for the Meetings Committee to suggest some
>>venues and
>> see what the community feels (this has happened before with a poll on
>>some
>> venues that Ray sent to the community).
>
>
>A practical issue is that announcing a venue before there is a contract
>in place for the meeting site impairs our ability to negotiate the
>contract.  And I'll suggest that this is not an issue that one should
>try to 'game', such as by trying to obscure the choice by floating
>various venue possibilities or otherwise hoping that we haven't signaled
>the choice to a specific city/hotel.

I=B9m still unsure about the proposal, but in the case of Asia, and when
we=B9re negotiating contracts for multiple meetings often well in advance,
you could practically list all countries that have cities large enough to
host.
We=B9re considering meetings in
Seoul
Singapore
Hong Kong
Beijing
Nanjing
Xi=B9an
Shanghai
Tokyo
Yokohama
Kyoto
Fukushima
Jakarta
Bangkok
Mumbai
(and so on and so on)

Build a matrix of mandatory and desired features and evaluate each
potential destination=B9s qualifications. Some are too specific (one roof)
to list before hotel negotiations begin, but others (accessibility by
disability, two-flight rule, other political climate, safety, multiple
hotels, etc.) can be evaluated very early in the process. In doing so,
that information remains on the record, and can be updated later.



>
>Rather, the way to deal with the choice of acceptable/unacceptable
>countries or cities is for the IETF community to develop lists
>reflecting the range of choices.
>
>The IETF's established set of regions is Eastern/Southeastern Asia,
>North America, Europe.  For each of these, the total list of countries
>is relatively small, so that a priori consideration and assessment by
>the IETF community ought to be feasible.

Right, although I=B9d like to include cities because some countries are
acceptable (Japan) but some cities within them may not be (Fukushima).

>
>(Other regions fall into the asterisk realm of 1:1:1:* and are already
>subject to prior discussion with the IETF community.)
>
>d/
>--=20
>
>   Dave Crocker

Lee




From nobody Mon Apr 11 06:53:31 2016
Return-Path: <john-ietf@jck.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 EDB9F12DF08 for <ietf@ietfa.amsl.com>; Mon, 11 Apr 2016 06:53:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.896
X-Spam-Level: 
X-Spam-Status: No, score=-2.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.996] 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 VWGWluWef7YB for <ietf@ietfa.amsl.com>; Mon, 11 Apr 2016 06:53:27 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BEDCA12DB41 for <ietf@ietf.org>; Mon, 11 Apr 2016 06:53:27 -0700 (PDT)
Received: from [198.252.137.10] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1apcHG-000H2A-O9; Mon, 11 Apr 2016 09:53:18 -0400
Date: Mon, 11 Apr 2016 09:53:13 -0400
From: John C Klensin <john-ietf@jck.com>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Subject: Re: Concerns about Singapore
Message-ID: <85DF4272E16A9292143D4AB5@JcK-HP8200.jck.com>
In-Reply-To: <570B7B22.90801@cs.tcd.ie>
References: <0D914666-C3D4-4CCE-AD5E-4E5B34EA1A73@piuha.net> <20160407182936.GA21340@pfrc.org> <CAB75xn780nNDjGa_Cc222J20-+1CCHt09Xp8KHzaK=n0xx51pg@mail.gmail.com> <5706B100.9040509@mnt.se> <CAB75xn6fmj84ROUtG5eUB3GerHx83hrEr3w5vSADY_g=BRg5FA@mail.gmail.com> <5706BA40.3060005@mnt.se> <alpine.DEB.2.02.1604072157240.31096@uplift.swm.pp.se> <A9B63A6D-3102-482F-8FFC-2E57A5FD8336@nic.cz> <16925.1460122349@obiwan.sandelman.ca> <m27fg77zst.wl%randy@psg.com> <57097077.7040703@comcast.net> <m2fuuu75ls.wl%randy@psg.com> <87wpo5a8im.fsf@tops.chopps.org> <m260vp7eke.wl%randy@psg.com> <570A6458.3050206@comcast.net> <m21t6d7c9t.wl%randy@psg.com> <570A67B4.3010206@comcast.net> <570AB3AF.2050401@gmail.com> <87twj99c6w.fsf@tops.chopps.org> <CAKe6YvMyp-DyeDwpPY6KYmbDbnpgnvVk_cUStnA32wmgDWcz3w@mail.gmail.com> <BBF5DDFE515C3946BC18D733B20DAD233A62AA18@XMB122CNC.rim.net> <570B7B22.90801@cs.tcd.ie>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/rExuWSwrLqlJ9cMRvbgw626jeKg>
Cc: IETF discussion list <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: Mon, 11 Apr 2016 13:53:30 -0000

--On Monday, April 11, 2016 11:23 +0100 Stephen Farrell
<stephen.farrell@cs.tcd.ie> wrote:

>...
> I think the lesson the IAOC ought learn here is to switch to a
> default-open mode of operation where only those things that
> really need to be kept confidential are kept confidential.
> (Note that I don't only mean for f2f meeting arrangements but
> for all of what the IAOC do.) That will require them (or
> someone) to go figure out (with the community) which kinds of
> things really do need to be kept confidential, and which can
> be done openly, in the normal IETF way.

I agree that the above is key.  Particular meeting choices,
registration decisions, etc., aside, I see the real problem as
that the IAOC has, perhaps by accident, gotten into habits
equivalent to working in secret and then catching the community
-- including members of the community who could have pointed out
additional issues to be considered -- by surprise with "this is
done and it is too late to undo it" announcements.   Moving to
"by default open" and "need to get explicit community buy-in for
categories of things that are treated as confidential" would, I
think, make a world of difference... especially if those
categories were made as narrow as possible.

IMO, much of the hostility the IAOC periodically encounters
(including my suggestion a few weeks ago that the "surprise!
remote participants now need to register" announcement should
cause some people to consider resigning) is directly connected
to the surprise announcements with no transparency about the
decision process, much less an opportunity for community review.
Fewer surprises about possibly-problematic actions, less
hostility.

That does nothing about the sense that some requirements are
absolute (e.g., "no-go for meetings and no associated discussion
about 'balance'"), but we ought to be able to have an open
discussion about what falls into that category (and keep it as
narrow as possible), not a situation in which the IAOC or its
committees say things equivalent to "there are a lot of factors,
we can't make everyone happy, and therefore we get to decide, in
secret, how to balance things and make announcements only after
contracts (or other irreversible actions are in place".

    john


From nobody Mon Apr 11 06:59:30 2016
Return-Path: <john@jlc.net>
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 2427F12E6C7 for <ietf@ietfa.amsl.com>; Mon, 11 Apr 2016 06:59:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.486
X-Spam-Level: 
X-Spam-Status: No, score=-1.486 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_SBL_CSS=3.335, RCVD_IN_XBL=0.375, RP_MATCHES_RCVD=-0.996] autolearn=no 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 JVdnV4aVoYWO for <ietf@ietfa.amsl.com>; Mon, 11 Apr 2016 06:59:28 -0700 (PDT)
Received: from mailhost.jlc.net (mailhost.jlc.net [199.201.159.4]) by ietfa.amsl.com (Postfix) with ESMTP id B94CA12E62B for <ietf@ietf.org>; Mon, 11 Apr 2016 06:59:27 -0700 (PDT)
Received: by mailhost.jlc.net (Postfix, from userid 104) id 7D3B6C94BD; Mon, 11 Apr 2016 09:59:22 -0400 (EDT)
Date: Mon, 11 Apr 2016 09:59:22 -0400
From: John Leslie <john@jlc.net>
To: Yoav Nir <ynir.ietf@gmail.com>
Subject: Virtual Meetings
Message-ID: <20160411135922.GB3997@verdi>
References: <m260vp7eke.wl%randy@psg.com> <570A6458.3050206@comcast.net> <m21t6d7c9t.wl%randy@psg.com> <570A67B4.3010206@comcast.net> <570AB3AF.2050401@gmail.com> <87twj99c6w.fsf@tops.chopps.org> <CAKe6YvMyp-DyeDwpPY6KYmbDbnpgnvVk_cUStnA32wmgDWcz3w@mail.gmail.com> <BBF5DDFE515C3946BC18D733B20DAD233A62AA18@XMB122CNC.rim.net> <20160411104519.GA19092@gsp.org> <3F48466D-390C-4C18-B958-732AE3E46FF1@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3F48466D-390C-4C18-B958-732AE3E46FF1@gmail.com>
User-Agent: Mutt/1.4.1i
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/ZhxH9A5be0aF2BbJ2Oi9C_f_1io>
Cc: Rich Kulawiec <rsk@gsp.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: Mon, 11 Apr 2016 13:59:29 -0000

Yoav Nir <ynir.ietf@gmail.com> wrote:
>> On 11 Apr 2016, at 1:45 PM, Rich Kulawiec <rsk@gsp.org> wrote:
>> 
>> Don't have physical meetings.  Then this entire problem space simply
>> vanishes...

... to be replaced by other "unsolvable" problems: but ones where progress
might be easier...

>> YES, it's replaced by a different problem space, which roughly works out
>> to "how can everything be done virtually?"

   ++

>> but given that this is the *Internet* engineering task force I have no
>> doubt that the collective expertise is more than capable of dealing
>> with that.  

   I don't 100% share that enthusiam; but I do believe we'd see visible
progress within a year or two.

> I don't believe that this technology exists.

   That makes three of us agreeing!

> People have been singing the praise of Meetecho in IETF 95, and yet
> remote participation is nothing like being in the room.

   True... I can be attending to my email, or even pouring through a
deskful of background papers, and nobody will chide me for not listening!

> And the "virtual interim" meetings are nothing like physical meetings...

   Less true... I have participated in some very effective virtual meetings.
It's a matter of how the Chair runs things. (And that _is_ variable!)

>> Particularly if all the discussion, effort, and expense going into the
>> logistics of physical meetings is redirected into virtual ones instead.
> 
> Yeah, perhaps, some day when we're all wearing virtual reality headsets
> and our avatars are hanging out in a virtual venue, and we all have
> sufficient equipment and bandwidth to handle all that.

   It really has nothing to do with such gimmicks!

   For IETF-95 I used a $500 large-screen for the first time. It certainly
didn't give me $500 of benefit over the multiple 20-inch screens I usually
use, but large-screens don't cost $500 anymore. ;^)

   I wouldn't use a V-R headset if it were a gift. Avatars would get in
the way of expressing differing attitudes. The whole field of how to show
non-local participants needs work!

> We're not there yet.

   We're not even agreed where "there" should be.

>> I really can't take any of the platitudes about "inclusion" seriously
>> until that happens -- because as long as the IETF persists with physical
>> meetings, most people *will* be excluded due to cost, distance, time,
>> legal climate, personal safety, etc.

   Guilty as charged.

>> The IETF is, even if accidentally, selecting for the elite few who are
>> fortunate enough to be [able to] attend.

   Guilty as charged, again.

   I've had quite a number of high-school students working here who could
have become valuable participants at IETF. Exactly _one_ of them agreed to
attend an IETF week; and that one would never consent to attend another.
We are selecting mostly those whose employers send them in hopes of getting
a return-on-investment.

   I long for the days when we attracted lots of graduate students!

> Virtual meetings with the technology we have today makes it very hard for
> people with mediocre English to follow the discussion.

   It's hard for them in-person on-site, too. Why aren't we discussing
tools to help them?

> The "I don't quite follow what you're saying" look does not translate
> well to the kind of video we can use today.

   False! It merely doesn't translate to the kind of video we _do_ use
today.

> That extends even to people with relatively good English (for non-native
> speakers) like me. 

   So, to fall back to my standard question: "What are you going to do
about it?"

--
John Leslie <john@jlc.net>


From nobody Mon Apr 11 07:07:13 2016
Return-Path: <ynir.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 3102C12EEC5 for <ietf@ietfa.amsl.com>; Mon, 11 Apr 2016 07:07:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 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, RCVD_IN_DNSWL_LOW=-0.7, 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 u5lbL-EJ8RJN for <ietf@ietfa.amsl.com>; Mon, 11 Apr 2016 07:07:07 -0700 (PDT)
Received: from mail-wm0-x22e.google.com (mail-wm0-x22e.google.com [IPv6:2a00:1450:400c:c09::22e]) (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 E496B12EEBA for <ietf@ietf.org>; Mon, 11 Apr 2016 07:07:06 -0700 (PDT)
Received: by mail-wm0-x22e.google.com with SMTP id n3so106277861wmn.0 for <ietf@ietf.org>; Mon, 11 Apr 2016 07:07:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=1OA1tPH815bTL8KIU1EcKs/CHG1OQS0Qh0OSIET4PiI=; b=TJQt/JCBnwjm0HldAYEdfFWofmUhwYzW7WEBKppJsc5oe8dz6HmdM48IB1RXVyYp5l REv8XfFoyj0hOIrSHoVGBFetAq3az7S/NN0ghae3MgpXhTXXdNma3zZxmZlqGbNp4sD9 Cdbca0Sl0r+NAdyPeF31bSDM/oAnV0TkTLuBMuKTwOho/kg9VPn68zehUrFG9c6TvM3R mV0bg+7FW+TxKShx+vFPehTVdzmvNNXqWpMfCStMdhIjDqklHSUYjYh69s+Latx6gINU IQOlfM4SC6l3bpOVA1pi4nxq11txaZZTFFgKHkpvvufbBOrBsTJMGhOcR1icRFBbACLM BAyw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=1OA1tPH815bTL8KIU1EcKs/CHG1OQS0Qh0OSIET4PiI=; b=DHA0LbR2tkOt6M9/TOPe4Nu4Peqjddt8J/G6j7SlQ55yuOrrHWHeyG/C4PDjN83n3v WR/4ashtqYJWHiqyPWq9RxqqomiRLcaSWqZO6bC+f0WMA565Xn/EHxVDWOGjuUW72G3g 0kyiuBYtiQOY/dGQdUus5dp8sRMDMq/YYe6tkQsuR3DCm4bHH4Xeuf4RYIRcTer18mbW +pGMooCO69u6dYphxCMyM/RqcPJ32eFLq7u3DSitLi0OSXhB/MoyeFtONWbZyGq4vMwm ddPQFU2066DdOpp7v7WOS7oQswxBZBksku4A1pkhhPoEyeNRFYX/7q6Bd5Hss8B3v+VC A9zQ==
X-Gm-Message-State: AD7BkJKY6SJMWtJVM385BTs1a/geYFSPbhnuQZVRfmRy0wsHYCT4C26UmSv+Gzzj5c7hKw==
X-Received: by 10.194.111.199 with SMTP id ik7mr26796861wjb.150.1460383625462;  Mon, 11 Apr 2016 07:07:05 -0700 (PDT)
Received: from [192.168.4.111] ([199.203.248.154]) by smtp.gmail.com with ESMTPSA id xx3sm28111858wjc.32.2016.04.11.07.07.03 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Mon, 11 Apr 2016 07:07:04 -0700 (PDT)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Subject: Re: Concerns about Singapore
From: Yoav Nir <ynir.ietf@gmail.com>
In-Reply-To: <CAPt1N1kej35TSzDGH1QzNgJ9LvK2DMH-PFxDVUgvv_n_LPkvVw@mail.gmail.com>
Date: Mon, 11 Apr 2016 17:07:03 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <BC981CAF-5B3D-4C0A-8ECA-DE93F38912EC@gmail.com>
References: <m2fuuu75ls.wl%randy@psg.com> <87wpo5a8im.fsf@tops.chopps.org> <m260vp7eke.wl%randy@psg.com> <570A6458.3050206@comcast.net> <m21t6d7c9t.wl%randy@psg.com> <570A67B4.3010206@comcast.net> <570AB3AF.2050401@gmail.com> <87twj99c6w.fsf@tops.chopps.org> <CAKe6YvMyp-DyeDwpPY6KYmbDbnpgnvVk_cUStnA32wmgDWcz3w@mail.gmail.com> <BBF5DDFE515C3946BC18D733B20DAD233A62AA18@XMB122CNC.rim.net> <20160411104519.GA19092@gsp.org> <3F48466D-390C-4C18-B958-732AE3E46FF1@gmail.com> <CAPt1N1kej35TSzDGH1QzNgJ9LvK2DMH-PFxDVUgvv_n_LPkvVw@mail.gmail.com>
To: Ted Lemon <mellon@fugue.com>
X-Mailer: Apple Mail (2.3124)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/OnON44uQyJNpiRAgDFcA6IDNvnI>
Cc: Rich Kulawiec <rsk@gsp.org>, ietf <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: Mon, 11 Apr 2016 14:07:11 -0000

> On 11 Apr 2016, at 4:01 PM, Ted Lemon <mellon@fugue.com> wrote:
>=20
> Also, if you live in a country with censorship, or with low bandwidth, =
it's possible that the only way to attend an IETF meeting will be in =
person.   It would be nice if there were a bright line to draw on one =
side of which is total inclusiveness, but there is not.   We need to =
make both kinds of meeting work.
>=20
> What Stephen said is right--the IAOC needs to systematically, rather =
than informally, analyze what it is that needs to be done in confidence, =
and expose the rest to public view.   I know this is non-trivial, and I =
do not say this in the spirit of bashing the IAOC, who work very hard =
for us with little reward other than our complaining.
>=20
> If I were on the IAOC right now, I would be thinking about how to get =
off of it.   I've been in the situation of having what seemed like a big =
chunk of the IETF upset at me, and it's pretty soul-crushing.   =
Nevertheless, I think what Stephen proposes is the thing the IAOC can do =
that is most likely to prevent future woe of this kind.

I think Dave Crocker=E2=80=99s suggestion that the IAOC advertise the =
countries / cities it is considering might go a long way to help. If we =
had heard two years ago that the IAOC was considering Singapore, the =
objection we heard at the plenary would have been voiced then. In that =
case, the IAOC might go elsewhere or it might get assurances from =
Singaporean authorities or it might even decide to go for it anyway. But =
they would not be caught off-guard as they were last Wednesday.

Similarly for other countries or locations. This is not enough to solve =
all inclusiveness issues and there are deeper issues that need =
addressing, but this is low-hanging fruit IMO.

Yoav


From nobody Mon Apr 11 07:07:53 2016
Return-Path: <ynir.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 D033D12EEE1 for <ietf@ietfa.amsl.com>; Mon, 11 Apr 2016 07:07:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1
X-Spam-Level: 
X-Spam-Status: No, score=-1 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, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLACK=1.7] autolearn=no 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 6J6CtcuUE00o for <ietf@ietfa.amsl.com>; Mon, 11 Apr 2016 07:07:49 -0700 (PDT)
Received: from mail-wm0-x22f.google.com (mail-wm0-x22f.google.com [IPv6:2a00:1450:400c:c09::22f]) (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 85FB812EEDA for <ietf@ietf.org>; Mon, 11 Apr 2016 07:07:48 -0700 (PDT)
Received: by mail-wm0-x22f.google.com with SMTP id l6so147582138wml.1 for <ietf@ietf.org>; Mon, 11 Apr 2016 07:07:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=7T0G44+ppLPKEHdSRG60vnWxCpW2RvTV6ueQhroSk38=; b=b1aFe6E58T2b6REgDJyPVzmJo3lyJZQz4cQd/ZoyYkC1BnFwVJQYgS6rxI+dvxNcwk HNAdBkONtpK7gTj7rneYnLanDn4mdiDKy+yGE3FB9lUgOsQYHVdIlxCofJ9o7vl0WU28 RpXyMPznS1AiMAcU6bMdVcttmXjLU6+cy7cx2Fl4/ZZeNw5ZFyDJ2uWsuP9ScPe7rkVF MxHbQMAs4kUSs1U3UdED//6NWroCjD+QTXeVeOzJfhLkMapoSeoApL/T0htHsrPe5Y2L Hyb4vcWnRJZJ76GwANRqS6KgmO6iMnvbNv6AzLEU4hzZp/HbxhJfvP2dbNb4IOOdXTV/ miTg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=7T0G44+ppLPKEHdSRG60vnWxCpW2RvTV6ueQhroSk38=; b=MpVwNr8tSBcLgkcBopYC5zHQLGMmGk+Gc7f2kt042MwnAeYydwu/C+BvneKgFb4sOC LgoV3Wv7rMNrnRX/qMC6XtXeXtk3XGE6nYXzVquU4dMX7naMOHHqN83B0vgOVufgVNvA 4u4uj0x+ZsJar1+XYGra91kaVj1bLa+MbSGBRoL6YvKd3GM5ab/VRzmAej73s9nh0xp7 u5xPvk9GsDXZLF2/XMWJnvGa1SJ6b9VgjCcbGSwG+Z1iCR31KzwgzVwXqr0viizjj9BT cpgKqlCm8C+JSAbxot2W2a9KuNgWYsmL+Fs9razv4cLm9wJyOaxFCVC8juJjG0SSDVTZ gtMw==
X-Gm-Message-State: AOPr4FV1BoJ4K8rvL0T3Fzao78bP4izVHfx2gxDPw69XSbwR2DJVdLWFKLFq5OLulRqYmg==
X-Received: by 10.28.17.144 with SMTP id 138mr11802733wmr.5.1460383667033; Mon, 11 Apr 2016 07:07:47 -0700 (PDT)
Received: from [192.168.4.111] ([199.203.248.154]) by smtp.gmail.com with ESMTPSA id xx3sm28111858wjc.32.2016.04.11.07.07.45 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Mon, 11 Apr 2016 07:07:46 -0700 (PDT)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Subject: Re: Concerns about Singapore
From: Yoav Nir <ynir.ietf@gmail.com>
In-Reply-To: <7AD254D8-730E-413D-ADDC-A42DAD873976@unify.com>
Date: Mon, 11 Apr 2016 17:07:45 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <71A00847-8231-477A-BAC9-3A2D39C99523@gmail.com>
References: <0D914666-C3D4-4CCE-AD5E-4E5B34EA1A73@piuha.net> <20160407182936.GA21340@pfrc.org> <CAB75xn780nNDjGa_Cc222J20-+1CCHt09Xp8KHzaK=n0xx51pg@mail.gmail.com> <5706B100.9040509@mnt.se> <CAB75xn6fmj84ROUtG5eUB3GerHx83hrEr3w5vSADY_g=BRg5FA@mail.gmail.com> <5706BA40.3060005@mnt.se> <alpine.DEB.2.02.1604072157240.31096@uplift.swm.pp.se> <A9B63A6D-3102-482F-8FFC-2E57A5FD8336@nic.cz> <16925.1460122349@obiwan.sandelman.ca> <m27fg77zst.wl%randy@psg.com> <57097077.7040703@comcast.net> <m2fuuu75ls.wl%randy@psg.com> <87wpo5a8im.fsf@tops.chopps.org> <m260vp7eke.wl%randy@psg.com> <570A6458.3050206@comcast.net> <m21t6d7c9t.wl%randy@psg.com> <570A67B4.3010206@comcast.net> <570AB3AF.2050401@gmail.com> <87twj99c6w.fsf@tops.chopps.org> <CAKe6YvMyp-DyeDwpPY6KYmbDbnpgnvVk_cUStnA32wmgDWcz3w@mail.gmail.com> <BBF5DDFE515C3946BC18D733B20DAD233A62AA18@XMB122CNC.rim.net> <7AD254D8-730E-413D-ADDC-A42DAD873976@unify.com>
To: "Hutton, Andrew" <andrew.hutton@unify.com>
X-Mailer: Apple Mail (2.3124)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/YW1pqTVIAPSvBajrUaKo6rZ-YcA>
Cc: IETF discussion list <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: Mon, 11 Apr 2016 14:07:53 -0000

+1=20

> On 11 Apr 2016, at 12:34 PM, Hutton, Andrew <andrew.hutton@unify.com> =
wrote:
>=20
> I agree 100% with Andrew's view.
>=20
> Regards
> Andy
>=20
>> On 11 Apr 2016, at 09:05, Andrew Allen <aallen@blackberry.com> wrote:
>>=20
>> This is what I mean by slippery slope - once we go down this path it =
never ends - in a global community of well over 1000 active people at =
least one person is likely to have a problem with some aspect of most of =
the countries governments, policies, cultures or actions, etc.
>>=20
>> We could be left with the only possible venue being a cruise ship =
sailing in international waters - but then someone will probably object =
because the ship is registered in Panama or Liberia!
>>=20
>> The focus should be on choosing a location for the meeting that is =
open for all to attend and where it is reasonably safe to attend and =
meets the needs of a meeting for a large number of people and represents =
the regional balance of the membership.=20
>>=20
>> The mission of the IETF is to make the Internet work better by =
producing high quality, relevant technical documents that influence the =
way people design, use, and manage the Internet.
>>=20
>> The IETF is not an organization that's mission is to be an advocate =
for global social, environmental or political change. The selection of a =
meeting location should be for the purposes of advancing the IETF's =
mission. I think some of the concerns raised about Singapore need to be =
addressed in terms of the practical impact and risk to the attendance of =
some in the IETF community but we shouldn=92t start down the road of =
choosing or not choosing meeting locations based on an evaluation of a =
countries laws, culture and policies and whether those are acceptable to =
all or most of the community.
>>=20
>> Debates over whether a location is politically or morally acceptable =
will only distract from the mission of the IETF and likely divide the =
community rather than help in making progress towards forming consensus =
on the future development of the internet.
>>=20
>> Andrew
>>=20
>> -----Original Message-----
>> From: ietf [mailto:ietf-bounces@ietf.org] On Behalf Of Vinayak Hegde
>> Sent: Sunday, April 10, 2016 10:24 PM
>> To: chopps@chopps.org
>> Cc: IETF discussion list <ietf@ietf.org>
>> Subject: Re: Concerns about Singapore
>>=20
>>> On Mon, Apr 11, 2016 at 6:46 AM,  <chopps@chopps.org> wrote:
>>> It's certainly relevant to me, b/c I don't personally think that =
IETF=20
>>> meetings should be held in oppressive and censoring countries. I =
don't=20
>>> know how to articulate this well -- others are better at it -- but I=20=

>>> certainly would like to skip any meetings that I feel violate IETFs=20=

>>> value of openness so that I can at least vote with my feet and my=20
>>> dollars.
>>=20
>> Well how does this work with Internet's (and IETF's) mission of =
inclusiveness. Applying the same scale of "oppressiveness", I am sure =
large parts of the world think the same about the US/UK which has waged =
wars in Iraq, Afghanistan, Vietnam, Syria, Argentina (our latest venue) =
and elsewhere.
>>=20
>> The IETF doesn't seem to have a problem having meetings in these =
countries. I hope the majority of participants on this list realise that =
they are viewing the world through a western prism.
>>=20
>> The notion of punishing the general populace for the mistakes of =
their elected and unelected govt. seems wrong to me. Many times, the =
general populace of the country is fighting their govt. through the =
Internet. eg. Turkey.
>>=20
>> -- Vinayak
>>=20
>=20


From nobody Mon Apr 11 07:16:14 2016
Return-Path: <mellon@fugue.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 0C2FC12EF1B for <ietf@ietfa.amsl.com>; Mon, 11 Apr 2016 07:16:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.2
X-Spam-Level: 
X-Spam-Status: No, score=-0.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_PASS=-0.001, URIBL_BLACK=1.7] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.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 Ew5mPSr2y8ak for <ietf@ietfa.amsl.com>; Mon, 11 Apr 2016 07:16:10 -0700 (PDT)
Received: from mail-lf0-x229.google.com (mail-lf0-x229.google.com [IPv6:2a00:1450:4010:c07::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 AC8C312EF19 for <ietf@ietf.org>; Mon, 11 Apr 2016 07:16:09 -0700 (PDT)
Received: by mail-lf0-x229.google.com with SMTP id c126so158973513lfb.2 for <ietf@ietf.org>; Mon, 11 Apr 2016 07:16:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=n+dJyuHa3hAS/taPA5n/ZpiAWU5GbEugg51gqCc2ZoQ=; b=R0X4msYW+odNKsurpsALWCymrKFc0enz0GRlYebLQ4iwL/W0Ql7KI3peF+Y0zHBgeD +Ri/Ns3kBEPqgtsXB7pDq5tr6Lh3OEbq1LllIFcBydtOaK3yVzRPuwwDe64vY8FqxTy8 01jrRwVbVUYK7sZv9pVXeT30GvS9IPNxTUPPPJuS1qn0+hoQeh8RcwqHYT39cW9OBSxw im8SPN2rAz2t341IgHAvDkBaloutHTDsuhw5EdG2FWlP4tcMnFy2VPqwOXBr9w43gLi0 +EhqUwv6e/9AAdbaFQdfuEFsNODU/CX+s4XHPN34jfeLjAtiYtvWYvA69Nz+QA4G+Vtj 1BQw==
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; bh=n+dJyuHa3hAS/taPA5n/ZpiAWU5GbEugg51gqCc2ZoQ=; b=ATUHm3jMAPx4XE/dt0I161HwyN6m9EyLxqjzOWHq4+ieU3JlUgESm9GwcIw2yZu392 zNGqVtkYh7kv6mGAv2cPDRvCOKbMkYzVZ+OQl7iyuXh9xjAOLLK1yv/DqDrWucGtGot8 lb0FIoVqzpbbIqMZcWDVKGLH1r6kbFeYEI9kh2q38NcDikeA4fjSt8i9gHJhZqXzhyLW crT6Mr8TMutX74dweT0UG+NqMYkBCMS6rsbDDUteEyKFnl5ztFHidKMijrAOI1LANxRf 7S656FfBApMK4nxQYW+gTXrh+LURpWpkWcpYXEIuPS3xhQgdxQmKMbn+zAncsg3mWoC5 612Q==
X-Gm-Message-State: AD7BkJJHJhzBVlS0AF6y1FZ5jZpRY33eesggX/VcCABw8esvZiVb1TUuzWeIbS3Htnx3fbqHqWH1iu6113C/bQ==
X-Received: by 10.112.227.71 with SMTP id ry7mr8249511lbc.78.1460384167784; Mon, 11 Apr 2016 07:16:07 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.25.40.136 with HTTP; Mon, 11 Apr 2016 07:15:28 -0700 (PDT)
X-Originating-IP: [71.233.41.235]
In-Reply-To: <71A00847-8231-477A-BAC9-3A2D39C99523@gmail.com>
References: <0D914666-C3D4-4CCE-AD5E-4E5B34EA1A73@piuha.net> <20160407182936.GA21340@pfrc.org> <CAB75xn780nNDjGa_Cc222J20-+1CCHt09Xp8KHzaK=n0xx51pg@mail.gmail.com> <5706B100.9040509@mnt.se> <CAB75xn6fmj84ROUtG5eUB3GerHx83hrEr3w5vSADY_g=BRg5FA@mail.gmail.com> <5706BA40.3060005@mnt.se> <alpine.DEB.2.02.1604072157240.31096@uplift.swm.pp.se> <A9B63A6D-3102-482F-8FFC-2E57A5FD8336@nic.cz> <16925.1460122349@obiwan.sandelman.ca> <m27fg77zst.wl%randy@psg.com> <57097077.7040703@comcast.net> <m2fuuu75ls.wl%randy@psg.com> <87wpo5a8im.fsf@tops.chopps.org> <m260vp7eke.wl%randy@psg.com> <570A6458.3050206@comcast.net> <m21t6d7c9t.wl%randy@psg.com> <570A67B4.3010206@comcast.net> <570AB3AF.2050401@gmail.com> <87twj99c6w.fsf@tops.chopps.org> <CAKe6YvMyp-DyeDwpPY6KYmbDbnpgnvVk_cUStnA32wmgDWcz3w@mail.gmail.com> <BBF5DDFE515C3946BC18D733B20DAD233A62AA18@XMB122CNC.rim.net> <7AD254D8-730E-413D-ADDC-A42DAD873976@unify.com> <71A00847-8231-477A-BAC9-3A2D39C99523@gmail.com>
From: Ted Lemon <mellon@fugue.com>
Date: Mon, 11 Apr 2016 10:15:28 -0400
Message-ID: <CAPt1N1nsGbcE5gAE3wbXYDM8YGbv5BHqhhwzbbTtL-D5vyMBDw@mail.gmail.com>
Subject: Re: Concerns about Singapore
To: IETF discussion list <ietf@ietf.org>
Content-Type: multipart/alternative; boundary=001a11347e8e8e89ef0530362f16
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/obfA61SiDxdC9cs88ClhffnvM5M>
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: Mon, 11 Apr 2016 14:16:13 -0000

--001a11347e8e8e89ef0530362f16
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

FWIW, last week was not the first time I heard Singapore mentioned,
although I don't remember the context in which it had previously been
mentioned.   We need to have both more transparency about which locations
are being considered, and also a process for registering feedback on these
locations.   E.g., feedback on the IETF mailing list probably isn't
sufficient, because it's hard to keep track of the entirety of that mailing
list even if you subscribe to it, so a comment there could very easily get
lost.

On Mon, Apr 11, 2016 at 10:07 AM, Yoav Nir <ynir.ietf@gmail.com> wrote:

> +1
>
> > On 11 Apr 2016, at 12:34 PM, Hutton, Andrew <andrew.hutton@unify.com>
> wrote:
> >
> > I agree 100% with Andrew's view.
> >
> > Regards
> > Andy
> >
> >> On 11 Apr 2016, at 09:05, Andrew Allen <aallen@blackberry.com> wrote:
> >>
> >> This is what I mean by slippery slope - once we go down this path it
> never ends - in a global community of well over 1000 active people at lea=
st
> one person is likely to have a problem with some aspect of most of the
> countries governments, policies, cultures or actions, etc.
> >>
> >> We could be left with the only possible venue being a cruise ship
> sailing in international waters - but then someone will probably object
> because the ship is registered in Panama or Liberia!
> >>
> >> The focus should be on choosing a location for the meeting that is ope=
n
> for all to attend and where it is reasonably safe to attend and meets the
> needs of a meeting for a large number of people and represents the region=
al
> balance of the membership.
> >>
> >> The mission of the IETF is to make the Internet work better by
> producing high quality, relevant technical documents that influence the w=
ay
> people design, use, and manage the Internet.
> >>
> >> The IETF is not an organization that's mission is to be an advocate fo=
r
> global social, environmental or political change. The selection of a
> meeting location should be for the purposes of advancing the IETF's
> mission. I think some of the concerns raised about Singapore need to be
> addressed in terms of the practical impact and risk to the attendance of
> some in the IETF community but we shouldn=E2=80=99t start down the road o=
f choosing
> or not choosing meeting locations based on an evaluation of a countries
> laws, culture and policies and whether those are acceptable to all or mos=
t
> of the community.
> >>
> >> Debates over whether a location is politically or morally acceptable
> will only distract from the mission of the IETF and likely divide the
> community rather than help in making progress towards forming consensus o=
n
> the future development of the internet.
> >>
> >> Andrew
> >>
> >> -----Original Message-----
> >> From: ietf [mailto:ietf-bounces@ietf.org] On Behalf Of Vinayak Hegde
> >> Sent: Sunday, April 10, 2016 10:24 PM
> >> To: chopps@chopps.org
> >> Cc: IETF discussion list <ietf@ietf.org>
> >> Subject: Re: Concerns about Singapore
> >>
> >>> On Mon, Apr 11, 2016 at 6:46 AM,  <chopps@chopps.org> wrote:
> >>> It's certainly relevant to me, b/c I don't personally think that IETF
> >>> meetings should be held in oppressive and censoring countries. I don'=
t
> >>> know how to articulate this well -- others are better at it -- but I
> >>> certainly would like to skip any meetings that I feel violate IETFs
> >>> value of openness so that I can at least vote with my feet and my
> >>> dollars.
> >>
> >> Well how does this work with Internet's (and IETF's) mission of
> inclusiveness. Applying the same scale of "oppressiveness", I am sure lar=
ge
> parts of the world think the same about the US/UK which has waged wars in
> Iraq, Afghanistan, Vietnam, Syria, Argentina (our latest venue) and
> elsewhere.
> >>
> >> The IETF doesn't seem to have a problem having meetings in these
> countries. I hope the majority of participants on this list realise that
> they are viewing the world through a western prism.
> >>
> >> The notion of punishing the general populace for the mistakes of their
> elected and unelected govt. seems wrong to me. Many times, the general
> populace of the country is fighting their govt. through the Internet. eg.
> Turkey.
> >>
> >> -- Vinayak
> >>
> >
>
>

--001a11347e8e8e89ef0530362f16
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">FWIW, last week was not the first time I heard Singapore m=
entioned, although I don&#39;t remember the context in which it had previou=
sly been mentioned. =C2=A0 We need to have both more transparency about whi=
ch locations are being considered, and also a process for registering feedb=
ack on these locations. =C2=A0 E.g., feedback on the IETF mailing list prob=
ably isn&#39;t sufficient, because it&#39;s hard to keep track of the entir=
ety of that mailing list even if you subscribe to it, so a comment there co=
uld very easily get lost.</div><div class=3D"gmail_extra"><br><div class=3D=
"gmail_quote">On Mon, Apr 11, 2016 at 10:07 AM, Yoav Nir <span dir=3D"ltr">=
&lt;<a href=3D"mailto:ynir.ietf@gmail.com" target=3D"_blank">ynir.ietf@gmai=
l.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"m=
argin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">+1<br>
<br>
&gt; On 11 Apr 2016, at 12:34 PM, Hutton, Andrew &lt;<a href=3D"mailto:andr=
ew.hutton@unify.com">andrew.hutton@unify.com</a>&gt; wrote:<br>
&gt;<br>
&gt; I agree 100% with Andrew&#39;s view.<br>
&gt;<br>
&gt; Regards<br>
&gt; Andy<br>
&gt;<br>
&gt;&gt; On 11 Apr 2016, at 09:05, Andrew Allen &lt;<a href=3D"mailto:aalle=
n@blackberry.com">aallen@blackberry.com</a>&gt; wrote:<br>
&gt;&gt;<br>
&gt;&gt; This is what I mean by slippery slope - once we go down this path =
it never ends - in a global community of well over 1000 active people at le=
ast one person is likely to have a problem with some aspect of most of the =
countries governments, policies, cultures or actions, etc.<br>
&gt;&gt;<br>
&gt;&gt; We could be left with the only possible venue being a cruise ship =
sailing in international waters - but then someone will probably object bec=
ause the ship is registered in Panama or Liberia!<br>
&gt;&gt;<br>
&gt;&gt; The focus should be on choosing a location for the meeting that is=
 open for all to attend and where it is reasonably safe to attend and meets=
 the needs of a meeting for a large number of people and represents the reg=
ional balance of the membership.<br>
&gt;&gt;<br>
&gt;&gt; The mission of the IETF is to make the Internet work better by pro=
ducing high quality, relevant technical documents that influence the way pe=
ople design, use, and manage the Internet.<br>
&gt;&gt;<br>
&gt;&gt; The IETF is not an organization that&#39;s mission is to be an adv=
ocate for global social, environmental or political change. The selection o=
f a meeting location should be for the purposes of advancing the IETF&#39;s=
 mission. I think some of the concerns raised about Singapore need to be ad=
dressed in terms of the practical impact and risk to the attendance of some=
 in the IETF community but we shouldn=E2=80=99t start down the road of choo=
sing or not choosing meeting locations based on an evaluation of a countrie=
s laws, culture and policies and whether those are acceptable to all or mos=
t of the community.<br>
<span class=3D"">&gt;&gt;<br>
&gt;&gt; Debates over whether a location is politically or morally acceptab=
le will only distract from the mission of the IETF and likely divide the co=
mmunity rather than help in making progress towards forming consensus on th=
e future development of the internet.<br>
&gt;&gt;<br>
</span>&gt;&gt; Andrew<br>
&gt;&gt;<br>
&gt;&gt; -----Original Message-----<br>
&gt;&gt; From: ietf [mailto:<a href=3D"mailto:ietf-bounces@ietf.org">ietf-b=
ounces@ietf.org</a>] On Behalf Of Vinayak Hegde<br>
&gt;&gt; Sent: Sunday, April 10, 2016 10:24 PM<br>
&gt;&gt; To: <a href=3D"mailto:chopps@chopps.org">chopps@chopps.org</a><br>
&gt;&gt; Cc: IETF discussion list &lt;<a href=3D"mailto:ietf@ietf.org">ietf=
@ietf.org</a>&gt;<br>
&gt;&gt; Subject: Re: Concerns about Singapore<br>
&gt;&gt;<br>
&gt;&gt;&gt; On Mon, Apr 11, 2016 at 6:46 AM,=C2=A0 &lt;<a href=3D"mailto:c=
hopps@chopps.org">chopps@chopps.org</a>&gt; wrote:<br>
&gt;&gt;&gt; It&#39;s certainly relevant to me, b/c I don&#39;t personally =
think that IETF<br>
&gt;&gt;&gt; meetings should be held in oppressive and censoring countries.=
 I don&#39;t<br>
&gt;&gt;&gt; know how to articulate this well -- others are better at it --=
 but I<br>
&gt;&gt;&gt; certainly would like to skip any meetings that I feel violate =
IETFs<br>
&gt;&gt;&gt; value of openness so that I can at least vote with my feet and=
 my<br>
&gt;&gt;&gt; dollars.<br>
&gt;&gt;<br>
&gt;&gt; Well how does this work with Internet&#39;s (and IETF&#39;s) missi=
on of inclusiveness. Applying the same scale of &quot;oppressiveness&quot;,=
 I am sure large parts of the world think the same about the US/UK which ha=
s waged wars in Iraq, Afghanistan, Vietnam, Syria, Argentina (our latest ve=
nue) and elsewhere.<br>
&gt;&gt;<br>
&gt;&gt; The IETF doesn&#39;t seem to have a problem having meetings in the=
se countries. I hope the majority of participants on this list realise that=
 they are viewing the world through a western prism.<br>
&gt;&gt;<br>
&gt;&gt; The notion of punishing the general populace for the mistakes of t=
heir elected and unelected govt. seems wrong to me. Many times, the general=
 populace of the country is fighting their govt. through the Internet. eg. =
Turkey.<br>
&gt;&gt;<br>
&gt;&gt; -- Vinayak<br>
&gt;&gt;<br>
&gt;<br>
<br>
</blockquote></div><br></div>

--001a11347e8e8e89ef0530362f16--


From nobody Mon Apr 11 07:24:59 2016
Return-Path: <mcr+ietf@sandelman.ca>
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 3895F12EF73 for <ietf@ietfa.amsl.com>; Mon, 11 Apr 2016 07:24:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.897
X-Spam-Level: 
X-Spam-Status: No, score=-2.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.996, SPF_PASS=-0.001] 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 0Mr6BYlzQuyx for <ietf@ietfa.amsl.com>; Mon, 11 Apr 2016 07:24:50 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1283612EF72 for <ietf@ietf.org>; Mon, 11 Apr 2016 07:24:49 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id 8EB2A2009E for <ietf@ietf.org>; Mon, 11 Apr 2016 10:28:38 -0400 (EDT)
Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 0795363755 for <ietf@ietf.org>; Mon, 11 Apr 2016 10:24:49 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: IETF discussion list <ietf@ietf.org>
Subject: Re: I-D Action: draft-kucherawy-nomcom-procexp-00.txt
In-Reply-To: <7FBF15BB56B5908D0A908194@JcK-HP8200.jck.com>
References: <20160408185636.23101.86017.idtracker@ietfa.amsl.com> <570882CE.9010501@gmail.com> <13214.1460236486@obiwan.sandelman.ca> <CAL0qLwYKbB3_PQcUAUDqJwnddc4oywffVD+sVusOK2xiBYu4PA@mail.gmail.com> <5709CE36.3040605@gmail.com> <CAL0qLwbROnW8pKKtd=7hkHHyP=xA-_eNoBuoKqPpaGjjpgUH+Q@mail.gmail.com> <47541D4081FC9856A5390378@JcK-HP8200.jck.com> <7FBF15BB56B5908D0A908194@JcK-HP8200.jck.com>
X-Mailer: MH-E 8.6; nmh 1.6+dev; GNU Emacs 24.4.2
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Mon, 11 Apr 2016 10:24:48 -0400
Message-ID: <20280.1460384688@obiwan.sandelman.ca>
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/TclnoHXyJZ-wMO3HtzSsge3wcOQ>
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: Mon, 11 Apr 2016 14:24:57 -0000

--=-=-=
Content-Type: text/plain


John C Klensin <john-ietf@jck.com> wrote:
    > (2) There is a brief period for community challenges to those who have
    > not attended three of five meetings, paralleling the period in which
    > the Secretariat checks to be sure those who have claimed three of five
    > meetings really did attend.

That's not how it works now, btw.
The nomcom chair vets the people as they volunteer.
(I wrote poor ruby to scrape the secretariat provided interface to do it in
bulk.  We might get JSON replies soon...)

This may involve communicating with them to determine if they perhaps changed
employers, or emails, etc.

But, we still have a challenge period in the schedule.

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-




--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQEVAwUBVwuzroCLcPvd0N1lAQJwsAf/Q7bm+d2/bCqTAJ8xxRn5UL0aiPJlytLX
xPeUUcSqHQvQhu/Bl08aBxgB0GPJ0mKSAzVLVZBywzGAiczIzsAK26MpPeK1tVGS
fHdXKeWoJ92FVqT130kiTVZMBRidAA8u389VuXYgTWmcfwvfqSxOzFSWrCFcHO21
m8ZhgVCrIaG3fcnr7uDURKenepXyEQLDpvlq/tBlYe/M7P57cQ/xYHNpvUevOqpe
pQ+dsrlnVEB4tFRUx+SS1YcXguJaEI//k6PNYr9GP/n7vsdC34DWUZfdL9F2ECAP
1Y8XPhvd5fjj5KVZy5KB2RlV7aH+bGGEtLogEHAd92are0F9hpL51w==
=XuAA
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Mon Apr 11 07:29:08 2016
Return-Path: <stewart.bryant@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 07C8E12EF7B for <ietf@ietfa.amsl.com>; Mon, 11 Apr 2016 07:29:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 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, RCVD_IN_DNSWL_LOW=-0.7, 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 9U8mJ5LZjAM5 for <ietf@ietfa.amsl.com>; Mon, 11 Apr 2016 07:29:04 -0700 (PDT)
Received: from mail-wm0-x22a.google.com (mail-wm0-x22a.google.com [IPv6:2a00:1450:400c:c09::22a]) (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 E5B0012EF6E for <ietf@ietf.org>; Mon, 11 Apr 2016 07:29:03 -0700 (PDT)
Received: by mail-wm0-x22a.google.com with SMTP id f198so148179024wme.0 for <ietf@ietf.org>; Mon, 11 Apr 2016 07:29:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=subject:references:to:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding; bh=ekVQe4oR78jejk5MU2ipJVY55NliDFwTBSIBbSYrslg=; b=VrRxoRQ3Z8cKomfVRFK6nT1mYQQn8LHhdyYEANCDAA39X85+4Vd2QJF/VmjzQOERPZ Gb+Mf5UtwrVtrNyHVXvu1bBjOcLDrk3lCxH9me4qTW8SegAiCE4FVAcKH3KnMUp7vXsU qihG5qoIUzTqIQos/zY0k2d8Q+W6s39Wq125zXz1PbnaLJgPPooJgMV9VFcizJA9F94c 6WnUmgum2dZhiOvV3TAiMX+2PMj7trFzv2oDoFQpnQPpJi2uSuPRPoG5DtM0hTN/9DFb yj0j47ByutiMjWO0m1LYovZ+viHv6KJ57lyyoPu/06K49/Gi8KqBt766TMfg0wjhRjU3 0EXw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:references:to:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=ekVQe4oR78jejk5MU2ipJVY55NliDFwTBSIBbSYrslg=; b=eAMB3Gk1LqbfkJLohjKYjg0euaab4nA/rFFb3NrtaXbgJ2qAmwhS3BH5DAbGBAUwZR vcDpN6ZTP3QteO5QxnGrblwP560ZgpvGAziYUtZe//Cuu3BvSZWBB83oQo8lIB/Q0nGY Ts5oxt2oeDh7TPQziubvJvpvdrTnGpES/cvxqg+Jh4Cf6YxAuljix8Id1tLLmApzopfa oUMgHAHwYqBcEn0BG8lT2zHVyicCCgrigiZI5LXBfneVozObt+K7JZtbTqHlF1Lh8QaA C9gpp+MhbuAkGJ6Nyx8u4P6IBlfltyXh0FvjUTquU4XCoShPuJIjt9MeigYblGiKsaEZ E4ow==
X-Gm-Message-State: AD7BkJJeQzETGGyIQNUwtqMG69KkHPenJPQJnU/l9CRusFnTnA05UaRx9mvEMYI1izlzPg==
X-Received: by 10.28.73.70 with SMTP id w67mr19292409wma.28.1460384942463; Mon, 11 Apr 2016 07:29:02 -0700 (PDT)
Received: from [192.168.2.126] (host213-123-124-182.in-addr.btopenworld.com. [213.123.124.182]) by smtp.gmail.com with ESMTPSA id gk4sm28083849wjd.7.2016.04.11.07.29.00 for <ietf@ietf.org> (version=TLSv1/SSLv3 cipher=OTHER); Mon, 11 Apr 2016 07:29:00 -0700 (PDT)
Subject: Re: Concerns about Singapore
References: <0D914666-C3D4-4CCE-AD5E-4E5B34EA1A73@piuha.net> <20160407182936.GA21340@pfrc.org> <CAB75xn780nNDjGa_Cc222J20-+1CCHt09Xp8KHzaK=n0xx51pg@mail.gmail.com> <5706B100.9040509@mnt.se> <CAB75xn6fmj84ROUtG5eUB3GerHx83hrEr3w5vSADY_g=BRg5FA@mail.gmail.com> <5706BA40.3060005@mnt.se> <alpine.DEB.2.02.1604072157240.31096@uplift.swm.pp.se> <A9B63A6D-3102-482F-8FFC-2E57A5FD8336@nic.cz> <16925.1460122349@obiwan.sandelman.ca> <m27fg77zst.wl%randy@psg.com> <57097077.7040703@comcast.net> <m2fuuu75ls.wl%randy@psg.com> <87wpo5a8im.fsf@tops.chopps.org> <m260vp7eke.wl%randy@psg.com> <570A6458.3050206@comcast.net> <m21t6d7c9t.wl%randy@psg.com> <570A67B4.3010206@comcast.net> <570AB3AF.2050401@gmail.com> <87twj99c6w.fsf@tops.chopps.org> <CAKe6YvMyp-DyeDwpPY6KYmbDbnpgnvVk_cUStnA32wmgDWcz3w@mail.gmail.com> <BBF5DDFE515C3946BC18D733B20DAD233A62AA18@XMB122CNC.rim.net> <570B7B22.90801@cs.tcd.ie> <85DF4272E16A9292143D4AB5@JcK-HP8200.jck.com>
To: IETF discussion list <ietf@ietf.org>
From: Stewart Bryant <stewart.bryant@gmail.com>
Message-ID: <570BB4AA.5020307@gmail.com>
Date: Mon, 11 Apr 2016 15:28:58 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.7.0
MIME-Version: 1.0
In-Reply-To: <85DF4272E16A9292143D4AB5@JcK-HP8200.jck.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/FGccpbACoE939IcUK4qZ3iojUfw>
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: Mon, 11 Apr 2016 14:29:07 -0000

I would be happy if we took a boring utilitarian
attitude to meeting venues:

Find three places that more or less work and
just keep using them.

Stewart


From nobody Mon Apr 11 07:34:47 2016
Return-Path: <jmh@joelhalpern.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 2079C12EFA4 for <ietf@ietfa.amsl.com>; Mon, 11 Apr 2016 07:34:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.702
X-Spam-Level: 
X-Spam-Status: No, score=-2.702 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=joelhalpern.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 rvj-Gi5DrnlH for <ietf@ietfa.amsl.com>; Mon, 11 Apr 2016 07:34:45 -0700 (PDT)
Received: from maila2.tigertech.net (maila2.tigertech.net [208.80.4.152]) (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 B2F4D12EFA3 for <ietf@ietf.org>; Mon, 11 Apr 2016 07:34:37 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by maila2.tigertech.net (Postfix) with ESMTP id 7FDB4253617; Mon, 11 Apr 2016 07:34:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=1.tigertech; t=1460385277; bh=Q0UP21uvbuaxl6Wzq3gBoxBb41LzeOBivNow6lAvY2k=; h=Subject:To:References:From:Date:In-Reply-To:From; b=Vkb3fOsWI+Jf2A/23HZV89BaeOpUE4K8DLrJpWUXSKrcn2nUn4aoAiTVdiYNkeiuR Xh/k2hCkbx5gsGDrjAQJPJPT3nFG87vITZRyN6I42t8Te3NIfa3j65oqKLg31eQYD0 4VeUUcUnAzqbJ6SXv+CwJakA3oprPJgYOAELAQoQ=
X-Virus-Scanned: Debian amavisd-new at maila2.tigertech.net
Received: from Joels-MacBook-Pro.local (209-255-163-147.ip.mcleodusa.net [209.255.163.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by maila2.tigertech.net (Postfix) with ESMTPSA id 09FD724EB32; Mon, 11 Apr 2016 07:34:36 -0700 (PDT)
Subject: Re: Concerns about Singapore
To: Stewart Bryant <stewart.bryant@gmail.com>, IETF discussion list <ietf@ietf.org>
References: <0D914666-C3D4-4CCE-AD5E-4E5B34EA1A73@piuha.net> <20160407182936.GA21340@pfrc.org> <CAB75xn780nNDjGa_Cc222J20-+1CCHt09Xp8KHzaK=n0xx51pg@mail.gmail.com> <5706B100.9040509@mnt.se> <CAB75xn6fmj84ROUtG5eUB3GerHx83hrEr3w5vSADY_g=BRg5FA@mail.gmail.com> <5706BA40.3060005@mnt.se> <alpine.DEB.2.02.1604072157240.31096@uplift.swm.pp.se> <A9B63A6D-3102-482F-8FFC-2E57A5FD8336@nic.cz> <16925.1460122349@obiwan.sandelman.ca> <m27fg77zst.wl%randy@psg.com> <57097077.7040703@comcast.net> <m2fuuu75ls.wl%randy@psg.com> <87wpo5a8im.fsf@tops.chopps.org> <m260vp7eke.wl%randy@psg.com> <570A6458.3050206@comcast.net> <m21t6d7c9t.wl%randy@psg.com> <570A67B4.3010206@comcast.net> <570AB3AF.2050401@gmail.com> <87twj99c6w.fsf@tops.chopps.org> <CAKe6YvMyp-DyeDwpPY6KYmbDbnpgnvVk_cUStnA32wmgDWcz3w@mail.gmail.com> <BBF5DDFE515C3946BC18D733B20DAD233A62AA18@XMB122CNC.rim.net> <570B7B22.90801@cs.tcd.ie> <85DF4272E16A9292143D4AB5@JcK-HP8200.jck.com> <570BB4AA.5020307@gmail.com>
From: "Joel M. Halpern" <jmh@joelhalpern.com>
Message-ID: <570BB5FC.6010405@joelhalpern.com>
Date: Mon, 11 Apr 2016 10:34:36 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:38.0) Gecko/20100101 Thunderbird/38.7.2
MIME-Version: 1.0
In-Reply-To: <570BB4AA.5020307@gmail.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/utwf0Jmb2vb9ZHFcuDzYNpXAgm8>
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: Mon, 11 Apr 2016 14:34:46 -0000

Surprisingly to some, it turns out that it is a real help if the host 
has local people on the ground in the meeting city.  This creates a 
noticeable drawback to trying to just use 3 cities over and over.

Yours,
Joel

On 4/11/16 10:28 AM, Stewart Bryant wrote:
> I would be happy if we took a boring utilitarian
> attitude to meeting venues:
>
> Find three places that more or less work and
> just keep using them.
>
> Stewart
>
>


From nobody Mon Apr 11 07:36:49 2016
Return-Path: <dhc@dcrocker.net>
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 5F45112EFB7 for <ietf@ietfa.amsl.com>; Mon, 11 Apr 2016 07:36:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] 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 AFjIGjTXKJpA for <ietf@ietfa.amsl.com>; Mon, 11 Apr 2016 07:36:47 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3832212EFB6 for <ietf@ietf.org>; Mon, 11 Apr 2016 07:36:47 -0700 (PDT)
Received: from [192.168.1.168] (76-218-10-206.lightspeed.sntcca.sbcglobal.net [76.218.10.206]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id u3BEakW6028980 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Mon, 11 Apr 2016 07:36:46 -0700
Subject: Re: Concerns about Singapore
References: <0D914666-C3D4-4CCE-AD5E-4E5B34EA1A73@piuha.net> <CAB75xn780nNDjGa_Cc222J20-+1CCHt09Xp8KHzaK=n0xx51pg@mail.gmail.com> <5706B100.9040509@mnt.se> <CAB75xn6fmj84ROUtG5eUB3GerHx83hrEr3w5vSADY_g=BRg5FA@mail.gmail.com> <5706BA40.3060005@mnt.se> <alpine.DEB.2.02.1604072157240.31096@uplift.swm.pp.se> <A9B63A6D-3102-482F-8FFC-2E57A5FD8336@nic.cz> <16925.1460122349@obiwan.sandelman.ca> <m27fg77zst.wl%randy@psg.com> <57097077.7040703@comcast.net> <m2fuuu75ls.wl%randy@psg.com> <87wpo5a8im.fsf@tops.chopps.org> <m260vp7eke.wl%randy@psg.com> <570A6458.3050206@comcast.net> <m21t6d7c9t.wl%randy@psg.com> <570A67B4.3010206@comcast.net> <570AB3AF.2050401@gmail.com> <87twj99c6w.fsf@tops.chopps.org> <CAKe6YvMyp-DyeDwpPY6KYmbDbnpgnvVk_cUStnA32wmgDWcz3w@mail.gmail.com> <BBF5DDFE515C3946BC18D733B20DAD233A62AA18@XMB122CNC.rim.net> <570B7B22.90801@cs.tcd.ie> <85DF4272E16A9292143D4AB5@JcK-HP8200.jck.com> <570BB4AA.5020307@gmail.com> <570BB5FC.6010405@joelhalpern.com>
To: "Joel M. Halpern" <jmh@joelhalpern.com>
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
Message-ID: <570BB678.9030306@dcrocker.net>
Date: Mon, 11 Apr 2016 07:36:40 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2
MIME-Version: 1.0
In-Reply-To: <570BB5FC.6010405@joelhalpern.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Mon, 11 Apr 2016 07:36:46 -0700 (PDT)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/kn2WMoampKzLjR4NSmBZIL0P1SY>
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: dcrocker@bbiw.net
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: Mon, 11 Apr 2016 14:36:48 -0000

On 4/11/2016 7:34 AM, Joel M. Halpern wrote:
> Surprisingly to some, it turns out that it is a real help if the host
> has local people on the ground in the meeting city.  This creates a
> noticeable drawback to trying to just use 3 cities over and over.


That makes a big difference -- at the level of being essential -- for 
new cities in challenging regions -- mostly Asia for the IETF.

It's /much/ less of an issue for places having repeat visits.

d/

-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net


From nobody Mon Apr 11 07:52:05 2016
Return-Path: <chopps@chopps.org>
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 9563712D6CC for <ietf@ietfa.amsl.com>; Mon, 11 Apr 2016 07:52:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.196
X-Spam-Level: 
X-Spam-Status: No, score=-1.196 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.996, URIBL_BLACK=1.7] autolearn=no 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 otCO3I1HV98n for <ietf@ietfa.amsl.com>; Mon, 11 Apr 2016 07:52:02 -0700 (PDT)
Received: from smtp.chopps.org (smtp.chopps.org [54.88.81.56]) by ietfa.amsl.com (Postfix) with ESMTP id 4372312D5D4 for <ietf@ietf.org>; Mon, 11 Apr 2016 07:52:02 -0700 (PDT)
Received: from tops.chopps.org (24-247-68-31.dhcp.trcy.mi.charter.com [24.247.68.31]) (using TLSv1.2 with cipher AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by smtp.chopps.org (Postfix) with ESMTPSA id 80EF361176; Mon, 11 Apr 2016 14:52:01 +0000 (UTC)
References: <0D914666-C3D4-4CCE-AD5E-4E5B34EA1A73@piuha.net> <20160407182936.GA21340@pfrc.org> <CAB75xn780nNDjGa_Cc222J20-+1CCHt09Xp8KHzaK=n0xx51pg@mail.gmail.com> <5706B100.9040509@mnt.se> <CAB75xn6fmj84ROUtG5eUB3GerHx83hrEr3w5vSADY_g=BRg5FA@mail.gmail.com> <5706BA40.3060005@mnt.se> <alpine.DEB.2.02.1604072157240.31096@uplift.swm.pp.se> <A9B63A6D-3102-482F-8FFC-2E57A5FD8336@nic.cz> <16925.1460122349@obiwan.sandelman.ca> <m27fg77zst.wl%randy@psg.com> <57097077.7040703@comcast.net> <m2fuuu75ls.wl%randy@psg.com> <87wpo5a8im.fsf@tops.chopps.org> <m260vp7eke.wl%randy@psg.com> <570A6458.3050206@comcast.net> <m21t6d7c9t.wl%randy@psg.com> <570A67B4.3010206@comcast.net> <570AB3AF.2050401@gmail.com> <87twj99c6w.fsf@tops.chopps.org> <CAKe6YvMyp-DyeDwpPY6KYmbDbnpgnvVk_cUStnA32wmgDWcz3w@mail.gmail.com> <BBF5DDFE515C3946BC18D733B20DAD233A62AA18@XMB122CNC.rim.net>
User-agent: mu4e 0.9.16; emacs 24.5.1
From: <chopps@chopps.org>
To: Andrew Allen <aallen@blackberry.com>
Subject: Re: Concerns about Singapore
In-reply-to: <BBF5DDFE515C3946BC18D733B20DAD233A62AA18@XMB122CNC.rim.net>
Date: Mon, 11 Apr 2016 10:52:00 -0400
Message-ID: <87fuusjizz.fsf@tops.chopps.org>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature"
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/aAkZqQzvZgiXlic5DDVKynWMEZE>
Cc: IETF discussion list <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: Mon, 11 Apr 2016 14:52:03 -0000

--=-=-=
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


Andrew Allen <aallen@blackberry.com> writes:

> This is what I mean by slippery slope - once we go down this path it neve=
r ends - in a global community of well over 1000 active people at least one=
 person is likely to have a problem with some aspect of most of the countri=
es governments, policies, cultures or actions, etc.

FWIW, I believe an earlier mail I sent led in part to this thread. I was
saying it was important for me to understand how and when the IETF is
being treated "specially". I wish to have this information so that I can
make informed decision on whether I will attend the meeting (i.e.,
voting with my presence and dollars).

I'm wasn't asking for anything more, and I don't think there's a
slippery slope in being transparent on this issue.

I've refrained from getting involved in debates with people trying to
convince me that my views are wrong. That's another discussion, it's not
one I wish to have on the IETF discussion list, and not relevant to the
question of transparency that I was addressing.

Thanks,
Chris.

> We could be left with the only possible venue being a cruise ship sailing=
 in international waters - but then someone will probably object because th=
e ship is registered in Panama or Liberia!
>
> The focus should be on choosing a location for the meeting that is open f=
or all to attend and where it is reasonably safe to attend and meets the ne=
eds of a meeting for a large number of people and represents the regional b=
alance of the membership.
>
> The mission of the IETF is to make the Internet work better by producing =
high quality, relevant technical documents that influence the way people de=
sign, use, and manage the Internet.
>
> The IETF is not an organization that's mission is to be an advocate for g=
lobal social, environmental or political change. The selection of a meeting=
 location should be for the purposes of advancing the IETF's mission. I thi=
nk some of the concerns raised about Singapore need to be addressed in term=
s of the practical impact and risk to the attendance of some in the IETF co=
mmunity but we shouldn=E2=80=99t start down the road of choosing or not cho=
osing meeting locations based on an evaluation of a countries laws, culture=
 and policies and whether those are acceptable to all or most of the commun=
ity.
>
> Debates over whether a location is politically or morally acceptable will=
 only distract from the mission of the IETF and likely divide the community=
 rather than help in making progress towards forming consensus on the futur=
e development of the internet.
>
> Andrew
>
> -----Original Message-----
> From: ietf [mailto:ietf-bounces@ietf.org] On Behalf Of Vinayak Hegde
> Sent: Sunday, April 10, 2016 10:24 PM
> To: chopps@chopps.org
> Cc: IETF discussion list <ietf@ietf.org>
> Subject: Re: Concerns about Singapore
>
> On Mon, Apr 11, 2016 at 6:46 AM,  <chopps@chopps.org> wrote:
>> It's certainly relevant to me, b/c I don't personally think that IETF
>> meetings should be held in oppressive and censoring countries. I don't
>> know how to articulate this well -- others are better at it -- but I
>> certainly would like to skip any meetings that I feel violate IETFs
>> value of openness so that I can at least vote with my feet and my
>> dollars.
>
> Well how does this work with Internet's (and IETF's) mission of inclusive=
ness. Applying the same scale of "oppressiveness", I am sure large parts of=
 the world think the same about the US/UK which has waged wars in Iraq, Afg=
hanistan, Vietnam, Syria, Argentina (our latest venue) and elsewhere.
>
> The IETF doesn't seem to have a problem having meetings in these countrie=
s. I hope the majority of participants on this list realise that they are v=
iewing the world through a western prism.
>
> The notion of punishing the general populace for the mistakes of their el=
ected and unelected govt. seems wrong to me. Many times, the general popula=
ce of the country is fighting their govt. through the Internet. eg. Turkey.
>
> -- Vinayak


--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQIcBAEBCgAGBQJXC7oQAAoJEC4dgw7XuDAlmQEP/14upTfLIekG1bLmVmvGwPBp
QVKxL082pobqBXCzcd/wGs+lHG7HzBiQZroCSClLwsIzGYndqAWDsOwQvcF+3/CM
53yisa+IlmGhfXk7xkdiFzf48447/CWVx78k+cN2JnPN5f+O7fz9JX2ZpG7A1iIe
Kbvg32pCumGxf8D5/6avkYFYH4tsWsMeTgvd9az43CgKWcPUolMeuxe8e43Ymk8P
v0cdYUyRqgxbn0a+tp4eWMg4+YlkqM8lbVDeJYwj3eNaVm9eOVBQ+fsC0Gj4ZBSX
PH9DLav7bCI2iYblNMg358MOdPr+Y2ofHLRZWlBJ8GQ4RZQxGD3U1IGCDivhOrv8
duoYHkCGM/HJi4FipZ+T7KMc6xT5hBv7Y2YQIkL+2IMusT904EgYExetNLhH4tGp
+WEmfoRmZLlYzSNOYQfJ9qc6D2HRT1yZ6myl70l5zJyyu0N0C+2pz2zSaFM0l7c/
IYCh23igU8D6ToWU7NGoDmi818psIdt0cGe9Jp6X1YdClnJXRPPBmJovOUCU/2rZ
yYovxq8YUax6fZMSx23HP0otH29Eqd9i3ISG/lYeI8/ixJ1tlBoRl0MXutiZjyHX
y8KBaOzdHj97Gm9IJfn3SpPo+syGNqvpA0KlvMWkwtYuBRr7hQzbJVlIBKB7PT5e
5Fq0zUHMd4l+ru/bmOrX
=cZm+
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Mon Apr 11 09:36:55 2016
Return-Path: <paul.hoffman@vpnc.org>
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 02C4A12F16C for <ietf@ietfa.amsl.com>; Mon, 11 Apr 2016 09:36:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 t5enKv2iNxQ3 for <ietf@ietfa.amsl.com>; Mon, 11 Apr 2016 09:36:52 -0700 (PDT)
Received: from mail.proper.com (Opus1.Proper.COM [207.182.41.91]) (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 E85C412F166 for <ietf@ietf.org>; Mon, 11 Apr 2016 09:36:51 -0700 (PDT)
Received: from [10.32.60.122] (50-1-98-216.dsl.dynamic.fusionbroadband.com [50.1.98.216]) (authenticated bits=0) by mail.proper.com (8.15.2/8.14.9) with ESMTPSA id u3BGaoRW001177 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Mon, 11 Apr 2016 09:36:51 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
X-Authentication-Warning: mail.proper.com: Host 50-1-98-216.dsl.dynamic.fusionbroadband.com [50.1.98.216] claimed to be [10.32.60.122]
From: "Paul Hoffman" <paul.hoffman@vpnc.org>
To: ietf@ietf.org
Subject: Hackathon results?
Date: Mon, 11 Apr 2016 09:36:50 -0700
Message-ID: <E2698DD7-3A06-48CB-9359-D28286BF0656@vpnc.org>
MIME-Version: 1.0
Content-Type: text/plain; format=flowed
X-Mailer: MailMate (1.9.4r5234)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/4KSWyVHsntYd0fOdu_o_m7J3IK0>
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: Mon, 11 Apr 2016 16:36:54 -0000

Greetings again. If I want to show people what happened at the recent 
IETF Hackathons, where can I find information? There aren't slides in 
the Proceedings, at least for IETF 94.

--Paul Hoffman


From nobody Mon Apr 11 10:17:31 2016
Return-Path: <presnick@qti.qualcomm.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 7333812F1D3 for <ietf@ietfa.amsl.com>; Mon, 11 Apr 2016 10:17:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.017
X-Spam-Level: 
X-Spam-Status: No, score=-8.017 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.996, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=qti.qualcomm.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 LKSlQr1Yd_Fs for <ietf@ietfa.amsl.com>; Mon, 11 Apr 2016 10:17:27 -0700 (PDT)
Received: from wolverine02.qualcomm.com (wolverine02.qualcomm.com [199.106.114.251]) (using TLSv1.2 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9511812F1DA for <ietf@ietf.org>; Mon, 11 Apr 2016 10:17:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1460395047; x=1491931047; h=from:to:subject:date:message-id:in-reply-to:references: mime-version; bh=2ar7WMPqksOvD2NIK9g3YzSiQG71bRS8n1wNXKhmXM8=; b=ABHWRPcEvDaHLfRMN0v2z4UfohtpDZtpbjpaGnPha5xc3n/S50AMqyi7 cVlzEQWs5WJgGXDFjKyXyyUwDihwHgugdNJhKXoAO9vh07eqa3QahGkAG H/AmnVMYiEIT0D3ruEjCTz+cULKlKmTxSV3Qm6HtX2lfOoDBIelj1ZShn A=;
X-IronPort-AV: E=Sophos;i="5.24,462,1455004800"; d="scan'208";a="279174864"
Received: from ironmsg03-r-new.qualcomm.com (HELO Ironmsg03-R.qualcomm.com) ([10.53.140.107]) by wolverine02.qualcomm.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 11 Apr 2016 10:17:23 -0700
X-IronPort-AV: E=McAfee;i="5700,7163,8132"; a="1119815764"
Received: from nasanexm01f.na.qualcomm.com ([10.85.0.32]) by Ironmsg03-R.qualcomm.com with ESMTP/TLS/RC4-SHA; 11 Apr 2016 10:17:23 -0700
Received: from [10.64.163.124] (10.80.80.8) by NASANEXM01F.na.qualcomm.com (10.85.0.32) with Microsoft SMTP Server (TLS) id 15.0.1130.7; Mon, 11 Apr 2016 10:17:22 -0700
From: Pete Resnick <presnick@qti.qualcomm.com>
To: IETF <ietf@ietf.org>
Subject: Re: Last Call on draft-bradner-rfc3979bis-08.txt ("Intellectual Property Rights in IETF Technology")
Date: Mon, 11 Apr 2016 12:17:21 -0500
Message-ID: <E7E31E22-1C86-40C4-BC5B-F65132015EF5@qti.qualcomm.com>
In-Reply-To: <0000431F-F977-4A24-BA4D-064F740977A0@piuha.net>
References: <0000431F-F977-4A24-BA4D-064F740977A0@piuha.net>
MIME-Version: 1.0
Content-Type: text/plain; format=flowed
X-Mailer: MailMate (1.9.4r5239)
X-Originating-IP: [10.80.80.8]
X-ClientProxiedBy: nasanexm01a.na.qualcomm.com (10.85.0.81) To NASANEXM01F.na.qualcomm.com (10.85.0.32)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/-eWKxFmGug1so4Hy5YkiGP81tUs>
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: Mon, 11 Apr 2016 17:17:29 -0000

Some questions and comments, much of them editorial, though nonetheless 
important:

- Section 2:

The third paragraph of 3979 section 2 (with the 2026 "principles") was 
deleted. I kinda liked it. Can we put it back in? So basically I'm 
suggesting:

OLD
     Section 1 defines...
NEW
     RFC 2026, Section 10 established three basic principles regarding
     the IETF dealing with claims of Intellectual Property Rights:

     (a) the IETF will make no determination about the validity of any
         particular IPR claim
     (b) the IETF following normal processes can decide to use 
technology
         for which IPR disclosures have been made if it decides that 
such
         a use is warranted
     (c) in order for the working group and the rest of the IETF to have
         the information needed to make an informed decision about the
         use of a particular technology, all those contributing to the
         working group's discussions must disclose the existence of any
         IPR the Contributor or other IETF participant believes Covers 
or
         may ultimately Cover the technology under discussion.  This
         applies to both Contributors and other participants, and 
applies
         whether they contribute in person, via email or by other means.
         The requirement applies to all IPR of the participant, the
         participant's employer, sponsor, or others represented by the
         participants, that is reasonably and personally known to the
         participant.  No patent search is required.

     Section 1 defines...
END

- Section 4:

A bunch of (D) (what was section 4.1 from 3979) was deleted. It seemed 
like sensible stuff. Why was it removed? Was it just the 2026 reference? 
Couldn't we just update that to refer to 6410?

- Section 5.2.1 (A): The stuff after the first sentence is more 
completely described in 5.4.2. How about a forward reference here 
instead:

OLD
                                                                   For
        example, if the Contribution is an update to a Contribution for
        which an IPR disclosure has already been made and the
        applicability of the disclosure is not changed by the new
        Contribution, then no new disclosure is required.  But if the
        Contribution is a new one, or is one that changes an existing
        Contribution such that the revised Contribution is no longer
        Covered by the disclosed IPR or would be Covered by new or
        different IPR, then a new disclosure must be made.
NEW
        See section 5.4.2 for a discussion of when updates need to be
        made for an existing disclosure.
END

- Section 5.4.2(A):

A couple of cleanups items in this section, and one concern. First, the 
cleanup: Clause (2) could use the same "unless" clause that (1) and (3) 
have; if you've got enough info regarding the patent application in the 
disclosure to find that it's been abandoned, there shouldn't be a hard 
requirement to update the disclosure. Also, clause (4) says "causes the 
Disclosure to be covered" when it should say "causes the Contribution to 
be covered". But even leaving that aside, clause (4) is a really a noop: 
If there is a material change to the document, that is in and of itself 
a new contribution, and is therefore addressed by section 5.1 or the 
"inherited by revisions" sentence at the bottom of 5.4.2(A). So, for the 
first part of 5.4.2(A), I suggest the following:

OLD
     A. An IPR disclosure must be updated or a new disclosure made
        promptly after any of the following has occurred: (1) the
        publication of a previously unpublished patent application,
        (unless sufficient information to identify the published
        application was disclosed when the unpublished application was
        disclosed), (2) the abandonment of a patent application (3) the
        issuance of a patent on a previously disclosed patent 
application
        (unless sufficient information to identify the issued patent was
        disclosed when the patent application was disclosed), (4) a
        material change to the IETF Document covered by the Disclosure
        that causes the Disclosure to be covered by additional IPR.
NEW
     A. An IPR disclosure must be updated or a new disclosure made
        promptly after any of the following has occurred unless
        sufficient information was provided when the original disclosure
        was made to discover the status of the patent or patent
        application: (1) the publication of a previously unpublished
        patent application, (2) the abandonment of a patent application,
        or (3) the issuance of a patent on a previously disclosed patent
        application.
END

As far as the concern, the second part of the next sentence in 5.4.2(A) 
is worrisome:

                                                                     If 
a
        patent has issued, then the new IPR disclosure must include the
        patent number and, if the claims of the granted patent differ
        from those of the application in manner material to the relevant
        Contribution, the IPR disclosure must describe any differences 
in
        applicability to the Contribution.

The first part is fine, though it repeats what's in 5.4.1 already, so I 
think it can be dropped. But the second part is what I'm concerned 
about. We've never before required disclosures to determine and discuss 
the applicability of the disclosure to the Contribution, and nowhere 
else in this document is that mentioned. Indeed, we go to great lengths 
to say that the leadership of the IETF doesn't try to figure out 
applicability, and that even WGs or the IESG can only take into account 
their opinions of what the applicability is. As a general rule, I don't 
think we can ask people who disclose to do the analysis to determine 
what parts of the patent do or do not apply to a particular 
contribution. As we say elsewhere, that's really up to a court. So I 
think the above should just be dropped.

A few editorial ones suggested by some lawyer friends. They all seem 
eminently sensible to me:

- Section 5.5(A): s/i.e./e.g.

- Section 5.5(B): s/royalty rates/royalties. I'm told that there are 
royalties that might not have "rates" associated with them.

- Section 5.5(C): Two things:

OLD
       and will attach to the associated IPR
NEW
       and will attach, to the extent permissible by law, to the 
associated IPR
END

I'm told that there are some jurisdictions where you may not be able to 
do that.

OLD
       must ensure that such
       commitments are binding on any subsequent transferee of the
       relevant IPR.
NEW
       must ensure that such commitments are binding on a transferee of
       the relevant IPR, and that such transferee will use reasonable
       efforts to ensure that such commitments are binding on a
       subsequent transferee of the relevant IPR, and so on.
END

The object of the "subsequent" wasn't clear, so this just spells it out. 
Wordy, but more precise.

- Section 7, paragraph 6:

The only change in this paragraph from 3979 was to add the word "all" in 
the second-to-last sentence. My lawyer friends tell me that this little 
change is opening a can of worms, having to do with licensing to makers 
of parts instead of implementers of the whole specification. I don't 
think we meant to change the meaning from the 3979 meaning, and I 
certainly don't think that we meant to change some implication about 
whether folks in general needed to license to people that make parts 
where they wouldn't have before. Was there something unclear about that 
sentence that needed the word "all" added to it? We aren't making a 
substantive change, are we? Can we just strike it? It seemed pretty 
clear to me before.

pr
-- 
Pete Resnick <http://www.qualcomm.com/~presnick/>
Qualcomm Technologies, Inc. - +1 (858)651-4478


From nobody Mon Apr 11 14:04:28 2016
Return-Path: <richard@shockey.us>
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 49D6C12F46E for <ietf@ietfa.amsl.com>; Mon, 11 Apr 2016 14:04:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (768-bit key) header.d=shockey.us
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 UDyYmxZLVRXf for <ietf@ietfa.amsl.com>; Mon, 11 Apr 2016 14:04:25 -0700 (PDT)
Received: from gproxy5-pub.mail.unifiedlayer.com (gproxy5-pub.mail.unifiedlayer.com [67.222.38.55]) by ietfa.amsl.com (Postfix) with SMTP id 7001312F46A for <ietf@ietf.org>; Mon, 11 Apr 2016 14:04:25 -0700 (PDT)
Received: (qmail 19481 invoked by uid 0); 11 Apr 2016 21:04:23 -0000
Received: from unknown (HELO CMOut01) (10.0.90.82) by gproxy5.mail.unifiedlayer.com with SMTP; 11 Apr 2016 21:04:23 -0000
Received: from box462.bluehost.com ([74.220.219.62]) by CMOut01 with  id h94H1s00h1MNPNq0194LWK; Mon, 11 Apr 2016 15:04:22 -0600
X-Authority-Analysis: v=2.1 cv=G/WPTbU5 c=1 sm=1 tr=0 a=jTEj1adHphCQ5SwrTAOQMg==:117 a=jTEj1adHphCQ5SwrTAOQMg==:17 a=L9H7d07YOLsA:10 a=9cW_t1CCXrUA:10 a=s5jvgZ67dGcA:10 a=IkcTkHD0fZMA:10 a=8WrITzYgnNwA:10 a=p-_XEfp0GhYA:10 a=kziv93cY1bsA:10 a=ll-iCDY8AAAA:8 a=M0OflfRGAAAA:8 a=48vgC7mUAAAA:8 a=pGLkceISAAAA:8 a=h9BFz859YBSEKFmMsmAA:9 a=iaBm1-PoNESJO3ow:21 a=8wGcYLj1Wf-qRW84:21 a=QEXdDO2ut3YA:10 a=ivbTfD_dPm4A:10
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=shockey.us;  s=default; h=Content-transfer-encoding:Content-type:Mime-version:In-Reply-To :References:Message-ID:To:From:Subject:Date; bh=C9Y9RPyiyFsZkG9dktcdPjADfK/W43uv3rY4aGxxqxQ=; b=XUb0kpg+9g9rJuj1LTDsTob0EZ Hzbnopst8nSqTeRMPVvp+cSXnzSMEFIa/vB2i59nrPP4XSLqpKaC3RE745QB8AvV5sY1fZG4CVC7L iDLNn5k+PnhASHwAr6U0QwzYs;
Received: from [100.36.35.60] (port=59610 helo=[192.168.1.9]) by box462.bluehost.com with esmtpa (Exim 4.86_2) (envelope-from <richard@shockey.us>) id 1apj0M-00067s-GN; Mon, 11 Apr 2016 15:04:18 -0600
User-Agent: Microsoft-MacOutlook/0.0.0.160212
Date: Mon, 11 Apr 2016 17:04:11 -0400
Subject: Re: Concerns about Singapore
From: Richard Shockey <richard@shockey.us>
To: Stewart Bryant <stewart.bryant@gmail.com>, IETF discussion list <ietf@ietf.org>
Message-ID: <10C9F20A-F248-41CD-8131-79C5A7F9BD1D@shockey.us>
Thread-Topic: Concerns about Singapore
References: <0D914666-C3D4-4CCE-AD5E-4E5B34EA1A73@piuha.net> <20160407182936.GA21340@pfrc.org> <CAB75xn780nNDjGa_Cc222J20-+1CCHt09Xp8KHzaK=n0xx51pg@mail.gmail.com> <5706B100.9040509@mnt.se> <CAB75xn6fmj84ROUtG5eUB3GerHx83hrEr3w5vSADY_g=BRg5FA@mail.gmail.com> <5706BA40.3060005@mnt.se> <alpine.DEB.2.02.1604072157240.31096@uplift.swm.pp.se> <A9B63A6D-3102-482F-8FFC-2E57A5FD8336@nic.cz> <16925.1460122349@obiwan.sandelman.ca> <m27fg77zst.wl%randy@psg.com> <57097077.7040703@comcast.net> <m2fuuu75ls.wl%randy@psg.com> <87wpo5a8im.fsf@tops.chopps.org> <m260vp7eke.wl%randy@psg.com> <570A6458.3050206@comcast.net> <m21t6d7c9t.wl%randy@psg.com> <570A67B4.3010206@comcast.net> <570AB3AF.2050401@gmail.com> <87twj99c6w.fsf@tops.chopps.org> <CAKe6YvMyp-DyeDwpPY6KYmbDbnpgnvVk_cUStnA32wmgDWcz3w@mail.gmail.com> <BBF5DDFE515C3946BC18D733B20DAD233A62AA18@XMB122CNC.rim.net> <570B7B22.90801@cs.tcd.ie> <85DF4272E16A9292143D4AB5@JcK-HP8200.jck.com> <570BB4AA.5020307@gmail.com>
In-Reply-To: <570BB4AA.5020307@gmail.com>
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: quoted-printable
X-Identified-User: {3286:box462.bluehost.com:shockeyu:shockey.us} {sentby:smtp auth 100.36.35.60 authed with richard+shockey.us}
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/nTqNYLgCLgQrxHSGawrZ6FLWkVo>
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: Mon, 11 Apr 2016 21:04:27 -0000

You can=E2=80=99t do that! =20

Didn=E2=80=99t you get the memo. This is the Internet Engineering Travel Forum.=20


=E2=80=94=20
Richard Shockey
Shockey Consulting LLC
Chairman of the Board SIP Forum
www.shockey.us
www.sipforum.org
richard<at>shockey.us
Skype-Linkedin-Facebook rshockey101
PSTN +1 703-593-2683








On 4/11/16, 10:28 AM, "ietf on behalf of Stewart Bryant" <ietf-bounces@ietf=
.org on behalf of stewart.bryant@gmail.com> wrote:

>I would be happy if we took a boring utilitarian
>attitude to meeting venues:
>
>Find three places that more or less work and
>just keep using them.
>
>Stewart
>


From nobody Mon Apr 11 14:09:42 2016
Return-Path: <jared@puck.nether.net>
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 B743F12EB8D for <ietf@ietfa.amsl.com>; Mon, 11 Apr 2016 14:09:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.198
X-Spam-Level: 
X-Spam-Status: No, score=-5.198 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.996, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] 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 ZLR-L-OTBqFT for <ietf@ietfa.amsl.com>; Mon, 11 Apr 2016 14:09:39 -0700 (PDT)
Received: from puck.nether.net (puck.nether.net [204.42.254.5]) by ietfa.amsl.com (Postfix) with ESMTP id 9CEFD12E550 for <ietf@ietf.org>; Mon, 11 Apr 2016 14:09:39 -0700 (PDT)
Received: from [IPv6:2601:401:4:3000:1d88:ad36:3fc4:763] (unknown [IPv6:2601:401:4:3000:1d88:ad36:3fc4:763]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by puck.nether.net (Postfix) with ESMTPSA id E9EDF540623; Mon, 11 Apr 2016 17:09:37 -0400 (EDT)
Subject: Re: Concerns about Singapore
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Content-Type: text/plain; charset=utf-8
From: Jared Mauch <jared@puck.nether.net>
In-Reply-To: <10C9F20A-F248-41CD-8131-79C5A7F9BD1D@shockey.us>
Date: Mon, 11 Apr 2016 17:09:37 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <94B861A7-4192-4F28-8359-09F2320A4A29@puck.nether.net>
References: <0D914666-C3D4-4CCE-AD5E-4E5B34EA1A73@piuha.net> <20160407182936.GA21340@pfrc.org> <CAB75xn780nNDjGa_Cc222J20-+1CCHt09Xp8KHzaK=n0xx51pg@mail.gmail.com> <5706B100.9040509@mnt.se> <CAB75xn6fmj84ROUtG5eUB3GerHx83hrEr3w5vSADY_g=BRg5FA@mail.gmail.com> <5706BA40.3060005@mnt.se> <alpine.DEB.2.02.1604072157240.31096@uplift.swm.pp.se> <A9B63A6D-3102-482F-8FFC-2E57A5FD8336@nic.cz> <16925.1460122349@obiwan.sandelman.ca> <m27fg77zst.wl%randy@psg.com> <57097077.7040703@comcast.net> <m2fuuu75ls.wl%randy@psg.com> <87wpo5a8im.fsf@tops.chopps.org> <m260vp7eke.wl%randy@psg.com> <570A6458.3050206@comcast.net> <m21t6d7c9t.wl%randy@psg.com> <570A67B4.3010206@comcast.net> <570AB3AF.2050401@gmail.com> <87twj99c6w.fsf@tops.chopps.org> <CAKe6YvMyp-DyeDwpPY6KYmbDbnpgnvVk_cUStnA32wmgDWcz3w@mail.gmail.com> <BBF5DDFE515C3946BC18D733B20DAD233A62AA18@XMB122CNC.rim.net> <570B7B22.90801@cs.tcd.ie> <85DF4272E16A9292143D4AB5@JcK-HP8200.jck.com> <570BB4AA.5020307@gmail.com> <10C9F20A-F248-41CD-8131-79C5A7F9 BD1D@shockey.us>
To: Richard Shockey <richard@shockey.us>
X-Mailer: Apple Mail (2.3124)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/_5xY0yhz5nIpp12zeBQj2qqmyZs>
Cc: IETF discussion list <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: Mon, 11 Apr 2016 21:09:41 -0000

> On Apr 11, 2016, at 5:04 PM, Richard Shockey <richard@shockey.us> =
wrote:
>=20
>=20
>=20
> You can=E2=80=99t do that! =20
>=20
> Didn=E2=80=99t you get the memo. This is the Internet Engineering =
Travel Forum.=20

It=E2=80=99s also the Internet Engineering Temperature Forum

https://www.youtube.com/watch?v=3DeTdn9-fqgtQ


From nobody Mon Apr 11 14:47:26 2016
Return-Path: <randy@psg.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 BB79912DE1F for <ietf@ietfa.amsl.com>; Mon, 11 Apr 2016 14:47:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.896
X-Spam-Level: 
X-Spam-Status: No, score=-7.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.996] 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 MrC7SNeOAcG1 for <ietf@ietfa.amsl.com>; Mon, 11 Apr 2016 14:47:22 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D685F12DBF9 for <ietf@ietf.org>; Mon, 11 Apr 2016 14:47:22 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com) by ran.psg.com with esmtp (Exim 4.82) (envelope-from <randy@psg.com>) id 1apjg1-0000jm-C0 for ietf@ietf.org; Mon, 11 Apr 2016 21:47:21 +0000
Date: Tue, 12 Apr 2016 06:47:19 +0900
Message-ID: <m24mb76cns.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: IETF Disgust List <ietf@ietf.org>
Subject: thank you
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/vhZ8uuOf9A_f3ILNo_b5HPffhA0>
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: Mon, 11 Apr 2016 21:47:25 -0000

buenos aires is a beautiful latin american city, hospitable, and with
great folk.  kudos for such a great meeting go to many people and
organizations that i will not enumerate for fear of missing one.  thank
you.

randy


From nobody Mon Apr 11 15:10:15 2016
Return-Path: <gjshep@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 A2E3712F515 for <ietf@ietfa.amsl.com>; Mon, 11 Apr 2016 15:10:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 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, RCVD_IN_DNSWL_LOW=-0.7, 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 bT9YE1mOEN-2 for <ietf@ietfa.amsl.com>; Mon, 11 Apr 2016 15:10:12 -0700 (PDT)
Received: from mail-pa0-x22c.google.com (mail-pa0-x22c.google.com [IPv6:2607:f8b0:400e:c03::22c]) (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 5BDE212F513 for <ietf@ietf.org>; Mon, 11 Apr 2016 15:10:12 -0700 (PDT)
Received: by mail-pa0-x22c.google.com with SMTP id zm5so16905pac.0 for <ietf@ietf.org>; Mon, 11 Apr 2016 15:10:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=TNUiGGy3cMdWZfTcz86knN/7A5PmuNJEHuANA0SGoaI=; b=g04s++JOlN1C/Jvcul3F8lZWOGudlQ5l+4s5DaXe2vtNs3uJ157SOvl9pfLJ3Et6sq gEGYwc97WXoHpngju427SYJI2KNtrLyExoQveT+gsA9IPTp01XYWAzw0GGJwJb0YJgTs IVTzfnKOXPmQq8GP5n7rNS7jgsbo3jmL24NtGoKva8Xk/o7sB9WWUmSv2yEho5e8GFHe 9XWbfAm4NwOgVEh9FbH39vTOpXDjdTvKaCifDrGvV1k+iWoS9d3b6RIHAyHsKMjh03A/ 0E+kd3oO5gum646PI1meh7OQf/Ej890EducUO7TiIKAPwU1AF+VTO4dk5I9UoHK8K0lv O3cQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=TNUiGGy3cMdWZfTcz86knN/7A5PmuNJEHuANA0SGoaI=; b=k9JxYAnpXzpI4CwkVarqDiK2eDYDKJV2WEKpcuAXVFofv+0FH6IzCDlwK+cQ2fZAkd dAULr4qEWSsygwUUBsupPL2mZpqropfDDrfCCRn7La/xh0xLRtYFAekWwWxkq3CK5FeG bXuU5eTdCzdk4d6OU7wTHL1Q1rQps0gRY3P/H8tJBphfEeq7tdXNFCBveJ0IaDyDVvOF JBLInyjLF/VK2qRh1qogTcCADIXyiD6nFEg5DZ8EekADmKoZTJ959c2QRhigBRcy7xgP nBY1REhEhwfK6wWv23K8XmLl07gCquiAUngvysHonO99dCHe6G7OHqvK3cTJy61Ymsn+ RVbA==
X-Gm-Message-State: AD7BkJICa2cxQf569XMoNe9g1aLReMfF62EdihYEO35ffc0HDkDlYGRe7yfFQbdxElC38g==
X-Received: by 10.66.251.132 with SMTP id zk4mr36039328pac.50.1460412612027; Mon, 11 Apr 2016 15:10:12 -0700 (PDT)
Received: from [10.198.40.131] (mobile-166-176-185-188.mycingular.net. [166.176.185.188]) by smtp.gmail.com with ESMTPSA id uu7sm20552714pac.40.2016.04.11.15.10.10 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 11 Apr 2016 15:10:11 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (1.0)
Subject: Re: thank you
From: Greg Shepherd <gjshep@gmail.com>
X-Mailer: iPhone Mail (13E238)
In-Reply-To: <m24mb76cns.wl%randy@psg.com>
Date: Mon, 11 Apr 2016 15:10:09 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <0773370A-98DF-421D-B286-20764AD8F724@gmail.com>
References: <m24mb76cns.wl%randy@psg.com>
To: Randy Bush <randy@psg.com>
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/7F6FG4X0RBsy14ZKd4YJtzs3FXk>
Cc: IETF Disgust List <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: Mon, 11 Apr 2016 22:10:13 -0000

I couldn't agree more. Few times I leave IETF wishing I had time to stay lon=
ger. Thanks to everyone who had a hand putting this all together.

Greg

Sent from my iPhone

> On Apr 11, 2016, at 14:47, Randy Bush <randy@psg.com> wrote:
>=20
> buenos aires is a beautiful latin american city, hospitable, and with
> great folk.  kudos for such a great meeting go to many people and
> organizations that i will not enumerate for fear of missing one.  thank
> you.
>=20
> randy
>=20


From nobody Mon Apr 11 15:33:44 2016
Return-Path: <alissa@cooperw.in>
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 62D6912F283 for <ietf@ietfa.amsl.com>; Mon, 11 Apr 2016 15:33:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.721
X-Spam-Level: 
X-Spam-Status: No, score=-2.721 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cooperw.in header.b=ZJlshZCj; dkim=pass (1024-bit key) header.d=messagingengine.com header.b=EY3z5ydO
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 e37C7RemiwVE for <ietf@ietfa.amsl.com>; Mon, 11 Apr 2016 15:33:41 -0700 (PDT)
Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9CC3512F307 for <ietf@ietf.org>; Mon, 11 Apr 2016 15:33:41 -0700 (PDT)
Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id CC40921BE3 for <ietf@ietf.org>; Mon, 11 Apr 2016 18:33:39 -0400 (EDT)
Received: from frontend1 ([10.202.2.160]) by compute4.internal (MEProxy); Mon, 11 Apr 2016 18:33:39 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=cooperw.in; h=cc :content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-sasl-enc :x-sasl-enc; s=mesmtp; bh=gvGcEovVWsj243ne/mWppbh//CA=; b=ZJlshZ CjhOkAqK6zA/qv+oB/Oxg9SD0Nbyt+Qi7BCLLfaRBr3gVhKQKRFVjEOUdgh8Dc0q zOv/U2kWAc17UEQY/ikyQEay4QvSoVknNfLiUKW5UlQKb6HMbldZCMbPoXpnKyVP TDVt+qwwRy5przyFBnD9/w3PeNludmWlNg/kQ=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-sasl-enc:x-sasl-enc; s=smtpout; bh=gvGcEovVWsj243n e/mWppbh//CA=; b=EY3z5ydOtEt1iqlxZhHa5Vd1yjS7zJcgBxJ2R+YOKM8XkPN T+dNvEnP3CjVVef8jZRwp4lhJ7sVW9V/JJQm1Wv3T9xaSizyvmqAA5UBSLVXCP78 oq6ulGhipm//5ElDX+UDfR10LsbtzLO6E7VAHoiZrVfEpx3Bk7NqJ1U87Ck4=
X-Sasl-enc: vhy73sjcQ+H+/DlSMIR24QX2r0WAnO3gGdbCZ+Voy/ac 1460414019
Received: from dhcp-171-68-20-149.cisco.com (dhcp-171-68-20-149.cisco.com [171.68.20.149]) by mail.messagingengine.com (Postfix) with ESMTPA id 363B9C00014; Mon, 11 Apr 2016 18:33:39 -0400 (EDT)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 9.2 \(3112\))
Subject: Re: Last Call on draft-bradner-rfc3979bis-08.txt ("Intellectual Property Rights in IETF Technology")
From: Alissa Cooper <alissa@cooperw.in>
In-Reply-To: <19FD9771-D4A1-4D1A-87BF-A11F2BEC3E6A@piuha.net>
Date: Mon, 11 Apr 2016 15:33:38 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <D674EE47-9E29-4E03-9BC5-7BCA0AFD880F@cooperw.in>
References: <0000431F-F977-4A24-BA4D-064F740977A0@piuha.net> <56FBF599.9080605@ericsson.com> <F99F459688AAAFCDCD5D9CC1@JcK-HP8200.jck.com> <5702CBA2.2060802@gmail.com> <19FD9771-D4A1-4D1A-87BF-A11F2BEC3E6A@piuha.net>
To: Jari Arkko <jari.arkko@piuha.net>
X-Mailer: Apple Mail (2.3112)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/CH47eJ3CFJMXdwDc8vMX09PNL5U>
Cc: John C Klensin <john-ietf@jck.com>, IETF <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: Mon, 11 Apr 2016 22:33:43 -0000

> On Apr 4, 2016, at 1:28 PM, Jari Arkko <jari.arkko@piuha.net> wrote:
>=20
>=20
>> Well, *exactly*. That's why I don't think that ADs or WGCs need to
>> be called out in any particular way: they participate and therefore
>> if they are reasonably and personally aware of IPR, they must =
disclose
>> (and if they can't disclose, they need to stop participating in
>> that particular case).
>=20
> Right, and I think we all are actually in agreement over this.
>=20
> Personally, I=92d love to see the draft talk about AD participation =
just like it talks about other people's participation. If I really =
haven=92t participated in WG X, well, I haven=92t, even if my co-AD owns =
the group :-) And if I did participate, well, I should declare the IPR =
that I know of :-)

+1
This is what did not make sense to me about the draft.=20

Alissa

>=20
> Jari
>=20


From nobody Mon Apr 11 15:34:14 2016
Return-Path: <rsk@gsp.org>
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 A72AB12F4C9 for <ietf@ietfa.amsl.com>; Mon, 11 Apr 2016 15:34:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] 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 y5oCUzGyU6iu for <ietf@ietfa.amsl.com>; Mon, 11 Apr 2016 15:34:11 -0700 (PDT)
Received: from taos.firemountain.net (taos.firemountain.net [207.114.3.54]) (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 87E0D12F4B5 for <ietf@ietf.org>; Mon, 11 Apr 2016 15:34:11 -0700 (PDT)
Received: from gsp.org (localhost [127.0.0.1]) by taos.firemountain.net (8.15.1/8.14.9) with SMTP id u3BMY5Lw027409 for <ietf@ietf.org>; Mon, 11 Apr 2016 18:34:09 -0400 (EDT)
Date: Mon, 11 Apr 2016 18:34:04 -0400
From: Rich Kulawiec <rsk@gsp.org>
To: ietf@ietf.org
Subject: Re: Concerns about Singapore
Message-ID: <20160411223403.GA6743@gsp.org>
References: <m260vp7eke.wl%randy@psg.com> <570A6458.3050206@comcast.net> <m21t6d7c9t.wl%randy@psg.com> <570A67B4.3010206@comcast.net> <570AB3AF.2050401@gmail.com> <87twj99c6w.fsf@tops.chopps.org> <CAKe6YvMyp-DyeDwpPY6KYmbDbnpgnvVk_cUStnA32wmgDWcz3w@mail.gmail.com> <BBF5DDFE515C3946BC18D733B20DAD233A62AA18@XMB122CNC.rim.net> <20160411104519.GA19092@gsp.org> <3F48466D-390C-4C18-B958-732AE3E46FF1@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3F48466D-390C-4C18-B958-732AE3E46FF1@gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/o9WMq7LeVbWKz5prR4qa16j7H9o>
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: Mon, 11 Apr 2016 22:34:13 -0000

On Mon, Apr 11, 2016 at 03:17:39PM +0300, Yoav Nir wrote:
> I don???t believe that this technology exists. 

People have remote meetings all day, every day.   Lots of technology
exists, more is being invented all the time.  Perhaps (to follow
on your mention of Meetecho in 1995) if 20 years had been invested
in making it work for the IETF then it would be working by now.

> Yeah, perhaps, some day when we???re all wearing virtual reality
> headsets and our avatars are hanging out in a virtual venue, and we all
> have sufficient equipment and bandwidth to handle all that. We???re not
> there yet.

Nor is there any need to go there.  Meetings do not require VR.

> Virtual meetings with the technology we have today makes it very hard
> for people with mediocre English to follow the discussion.

That's (a) not a very big problem and (b) a solvable problem.  


What I'm hearing is a lot of we've-always-done-it-this-way.  Well,
that's not working very well except for the privileged elite few
(most of whom are backed by corporations).  And I understand
that those with plenty of money and time and freedom have gotten
comfortable with how-things-are-done.  It's an easy thing to do,
I've done it myself.   But it doesn't serve the long-term interests
of the IETF or the Internet well.

---rsk


From nobody Mon Apr 11 15:47:42 2016
Return-Path: <stephen.farrell@cs.tcd.ie>
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 6D81F12E93A for <ietf@ietfa.amsl.com>; Mon, 11 Apr 2016 15:47:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.297
X-Spam-Level: 
X-Spam-Status: No, score=-5.297 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.996, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cs.tcd.ie
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 zHad3_QF3M2p for <ietf@ietfa.amsl.com>; Mon, 11 Apr 2016 15:47:38 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 50EEC12DBB3 for <ietf@ietf.org>; Mon, 11 Apr 2016 15:47:38 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 7B09EBE2D; Mon, 11 Apr 2016 23:47:36 +0100 (IST)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jgcgvFwpulGL; Mon, 11 Apr 2016 23:47:35 +0100 (IST)
Received: from [10.87.49.100] (unknown [86.46.23.241]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 9C6C7BE25; Mon, 11 Apr 2016 23:47:34 +0100 (IST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; s=mail; t=1460414855; bh=geYKxzaut4DHZy+H0t1jTZRPVC0YpiNmenKkN1WzTII=; h=Subject:To:References:From:Date:In-Reply-To:From; b=j2jn78JAlxjcPsaH1eVae9HTrSAjDg+ATapK+T7PWuBIfIAuJRLtQrOFoddF2vv1I 6CLJmCyV4//zk/8KDAFqma02zVH2WWzaVNfSwEZBHjIaMhILE7Gh4BrByhYD1aAmhx zL3/6xaGIWjwF196o8/ejAE/sCn7Jkw9fJmA+wD8=
Subject: 1000 person virtual meeting (Was: Re: Concerns about Singapore)
To: Rich Kulawiec <rsk@gsp.org>, ietf@ietf.org
References: <m260vp7eke.wl%randy@psg.com> <570A6458.3050206@comcast.net> <m21t6d7c9t.wl%randy@psg.com> <570A67B4.3010206@comcast.net> <570AB3AF.2050401@gmail.com> <87twj99c6w.fsf@tops.chopps.org> <CAKe6YvMyp-DyeDwpPY6KYmbDbnpgnvVk_cUStnA32wmgDWcz3w@mail.gmail.com> <BBF5DDFE515C3946BC18D733B20DAD233A62AA18@XMB122CNC.rim.net> <20160411104519.GA19092@gsp.org> <3F48466D-390C-4C18-B958-732AE3E46FF1@gmail.com> <20160411223403.GA6743@gsp.org>
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Openpgp: id=D66EA7906F0B897FB2E97D582F3C8736805F8DA2; url=
Message-ID: <570C2985.9030701@cs.tcd.ie>
Date: Mon, 11 Apr 2016 23:47:33 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0
MIME-Version: 1.0
In-Reply-To: <20160411223403.GA6743@gsp.org>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha-256; boundary="------------ms000304060308080808060609"
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/_YkqpNcsT9byupTfn8s4ymI7gNE>
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: Mon, 11 Apr 2016 22:47:40 -0000

This is a cryptographically signed message in MIME format.

--------------ms000304060308080808060609
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


Hiya,

On 11/04/16 23:34, Rich Kulawiec wrote:
>=20
> What I'm hearing is a lot of we've-always-done-it-this-way.  Well,
> that's not working very well except for the privileged elite few
> (most of whom are backed by corporations).  And I understand
> that those with plenty of money and time and freedom have gotten
> comfortable with how-things-are-done.  It's an easy thing to do,
> I've done it myself.   But it doesn't serve the long-term interests
> of the IETF or the Internet well.

FWIW, I think you're getting a few years ahead of reality
there, but eventually reality will catch up with you. I'm
not sure when I'd predict may happen, maybe in the next
5-10 years would be my current guess.

But maybe I'm wrong - can you send details of how an approx.
1000 person virtual meeting where everyone could provide real
input has been held by anyone? I'm unaware of such but I'd
be very interested if that had happened already.

Even if we're only in the realms of speculation, that could
still be useful speculation, so I'd encourage you to write
down your ideas as to how that could work, in an I-D. (Or
however you prefer to document stuff.)

And of course, that "that" that has to work need not involve
simultaneous participation by 1000 people from all over the
world within any one or a few hours. However, it does need
to involve that large a set with some practical method for
cross-pollination and for people to establish working
personal relationships with one another.

In summary, I do think we'll get figure out ways to cut out
most of the travel in future, but I figure we're just not
there yet, and I don't see how we establish the interpersonal
relationships if we do end up with a purist non-travel scenario.
But that said, I do agree that our current expensive-travel
approach definitely does favour the well financially endowed,
which currently includes me (surprisingly, to me;-)

Cheers,
S.


--------------ms000304060308080808060609
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIAGCSqGSIb3DQEHAqCAMIACAQExDzANBglghkgBZQMEAgEFADCABgkqhkiG9w0BBwEAAKCC
CvIwggUIMIID8KADAgECAhBPzaE7pzYviUJyhmHTFBdnMA0GCSqGSIb3DQEBCwUAMHUxCzAJ
BgNVBAYTAklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSkwJwYDVQQLEyBTdGFydENvbSBD
ZXJ0aWZpY2F0aW9uIEF1dGhvcml0eTEjMCEGA1UEAxMaU3RhcnRDb20gQ2xhc3MgMSBDbGll
bnQgQ0EwHhcNMTYwMjA5MDkyODE1WhcNMTcwMjA5MDkyODE1WjBOMSIwIAYDVQQDDBlzdGVw
aGVuLmZhcnJlbGxAY3MudGNkLmllMSgwJgYJKoZIhvcNAQkBFhlzdGVwaGVuLmZhcnJlbGxA
Y3MudGNkLmllMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAtuC0rYze/2JinSra
C9F2RjGdQZjNALLcW9C3WKTwYII3wBslobmHuPEYE5JaGItmzuKnAW619R1rD/kfoNWC19N3
rBZ6UX9Cmb9D9exCwYIwVuSwjrCQWGxgCtNQTrwKzCCpI790GRiMTvxvO7UmzmBrCaBLiZW5
R0fBjK5Yn6hUhAzGBkNbkIEL28cLJqH0yVz7Kl92OlzrQqTPEts5m6cDnNdY/ADfeAX18c1r
dxZqcAxhLotrCqgsVA4ilbQDMMXGTLlB5TP35HeWZuGBU7xu003rLcFLdOkD8xvpJoYZy9Kt
3oABXPS5yqtMK+XCNdqmMn+4mOtLwQSMmPCSiQIDAQABo4IBuTCCAbUwCwYDVR0PBAQDAgSw
MB0GA1UdJQQWMBQGCCsGAQUFBwMCBggrBgEFBQcDBDAJBgNVHRMEAjAAMB0GA1UdDgQWBBQJ
QhvwQ5Fl372Z6xqo6fdn8XejTTAfBgNVHSMEGDAWgBQkgWw5Yb5JD4+3G0YrySi1J0htaDBv
BggrBgEFBQcBAQRjMGEwJAYIKwYBBQUHMAGGGGh0dHA6Ly9vY3NwLnN0YXJ0c3NsLmNvbTA5
BggrBgEFBQcwAoYtaHR0cDovL2FpYS5zdGFydHNzbC5jb20vY2VydHMvc2NhLmNsaWVudDEu
Y3J0MDgGA1UdHwQxMC8wLaAroCmGJ2h0dHA6Ly9jcmwuc3RhcnRzc2wuY29tL3NjYS1jbGll
bnQxLmNybDAkBgNVHREEHTAbgRlzdGVwaGVuLmZhcnJlbGxAY3MudGNkLmllMCMGA1UdEgQc
MBqGGGh0dHA6Ly93d3cuc3RhcnRzc2wuY29tLzBGBgNVHSAEPzA9MDsGCysGAQQBgbU3AQIE
MCwwKgYIKwYBBQUHAgEWHmh0dHA6Ly93d3cuc3RhcnRzc2wuY29tL3BvbGljeTANBgkqhkiG
9w0BAQsFAAOCAQEArzrSv2C8PlBBmGuiGrzm2Wma46/KHtXmZYS0bsd43pM66Pc/MsqPE0HD
C1GzMFfwB6BfkJn8ijNSIhlgj898WzjvnpM/SO8KStjlB8719ig/xKISrOl5mX55XbFlQtX9
U6MrqRgbDIATxhD9IDr+ryvovDzChqgQj7mt2jYr4mdlRjsjod3H1VY6XglRmaaNGZfsCARM
aE/TU5SXIiqauwt5KxNGYAY67QkOBs7O1FkSXpTk7+1MmzJMF4nP8QQ5n8vhVNseF+/Wm7ai
9mtnrkLbaznMsy/ULo/C2yuLUWTbZZbf4EKNmVdme6tUDgYkFjAFOblfA7W1fSPiQGagYzCC
BeIwggPKoAMCAQICEGunin0K14jWUQr5WeTntOEwDQYJKoZIhvcNAQELBQAwfTELMAkGA1UE
BhMCSUwxFjAUBgNVBAoTDVN0YXJ0Q29tIEx0ZC4xKzApBgNVBAsTIlNlY3VyZSBEaWdpdGFs
IENlcnRpZmljYXRlIFNpZ25pbmcxKTAnBgNVBAMTIFN0YXJ0Q29tIENlcnRpZmljYXRpb24g
QXV0aG9yaXR5MB4XDTE1MTIxNjAxMDAwNVoXDTMwMTIxNjAxMDAwNVowdTELMAkGA1UEBhMC
SUwxFjAUBgNVBAoTDVN0YXJ0Q29tIEx0ZC4xKTAnBgNVBAsTIFN0YXJ0Q29tIENlcnRpZmlj
YXRpb24gQXV0aG9yaXR5MSMwIQYDVQQDExpTdGFydENvbSBDbGFzcyAxIENsaWVudCBDQTCC
ASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAL192vfDon2D9luC/dtbX64eG3XAtRmv
mCSsu1d52DXsCR58zJQbCtB2/A5uFqNxWacpXGGtTCRk9dEDBlmixEd8QiLkUfvHpJX/xKnm
VkS6Iye8wUbYzMsDzgnpazlPg19dnSqfhM+Cevdfa89VLnUztRr2cgmCfyO9Otrh7LJDPG+4
D8ZnAqDtVB8MKYJL6QgKyVhhaBc4y3bGWxKyXEtx7QIZZGxPwSkzK3WIN+VKNdkiwTubW5PI
dopmykwvIjLPqbJK7yPwFZYekKE015OsW6FV+s4DIM8UlVS8pkIsoGGJtMuWjLL4tq2hYQuu
N0jhrxK1ljz50hH23gA9cbMCAwEAAaOCAWQwggFgMA4GA1UdDwEB/wQEAwIBBjAdBgNVHSUE
FjAUBggrBgEFBQcDAgYIKwYBBQUHAwQwEgYDVR0TAQH/BAgwBgEB/wIBADAyBgNVHR8EKzAp
MCegJaAjhiFodHRwOi8vY3JsLnN0YXJ0c3NsLmNvbS9zZnNjYS5jcmwwZgYIKwYBBQUHAQEE
WjBYMCQGCCsGAQUFBzABhhhodHRwOi8vb2NzcC5zdGFydHNzbC5jb20wMAYIKwYBBQUHMAKG
JGh0dHA6Ly9haWEuc3RhcnRzc2wuY29tL2NlcnRzL2NhLmNydDAdBgNVHQ4EFgQUJIFsOWG+
SQ+PtxtGK8kotSdIbWgwHwYDVR0jBBgwFoAUTgvvGqRAW6UXaYcwyjRoQ9BBrvIwPwYDVR0g
BDgwNjA0BgRVHSAAMCwwKgYIKwYBBQUHAgEWHmh0dHA6Ly93d3cuc3RhcnRzc2wuY29tL3Bv
bGljeTANBgkqhkiG9w0BAQsFAAOCAgEAi+P3h+wBi4StDwECW5zhIycjBL008HACblIf26HY
0JdOruKbrWDsXUsiI0j/7Crft9S5oxvPiDtVqspBOB/y5uzSns1lZwh7sG96bYBZpcGzGxpF
NjDmQbcM3yl3WFIRS4WhNrsOY14V7y2IrUGsvetsD+bjyOngCIVeC/GmsmtbuLOzJ606tEc9
uRbhjTu/b0x2Fo+/e7UkQvKzNeo7OMhijixaULyINBfCBJb+e29bLafgu6JqjOUJ9eXXj20p
6q/CW+uVrZiSW57+q5an2P2i7hP85jQJcy5j4HzA0rSiF3YPhKGAWUxKPMAVGgcYoXzWydOv
Z3UDsTDTagXpRDIKQLZo02wrlxY6iMFqvlzsemVf1odhQJmi7Eh5TbxI40kDGcBOBHhwnaOu
mZhLP+SWJQnjpLpSlUOj95uf1zo9oz9e0NgIJoz/tdfrBzez76xtDsK0KfUDHt1/q59BvDI7
RX6gVr0fQoCyMczNzCTcRXYHY0tq2J0oT+bsb6sH2b4WVWAiJKnSYaWDjdA70qHX4mq9MIjO
/ZskmSY8wtAk24orAc0vwXgYanqNsBX5Yv4sN4Z9VyrwMdLcusP7HJgRdAGKpkR2I9U4zEsN
JQJewM7S4Jalo1DyPrLpL2nTET8ZrSl5Utp1UeGp/2deoprGevfnxWB+vHNQiu85o6MxggPM
MIIDyAIBATCBiTB1MQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRDb20gTHRkLjEpMCcG
A1UECxMgU3RhcnRDb20gQ2VydGlmaWNhdGlvbiBBdXRob3JpdHkxIzAhBgNVBAMTGlN0YXJ0
Q29tIENsYXNzIDEgQ2xpZW50IENBAhBPzaE7pzYviUJyhmHTFBdnMA0GCWCGSAFlAwQCAQUA
oIICEzAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0xNjA0MTEy
MjQ3MzNaMC8GCSqGSIb3DQEJBDEiBCDcmPuL75Qo9gQm1RlnAkdTSoa2PwYa9tiH0okt03d/
rTBsBgkqhkiG9w0BCQ8xXzBdMAsGCWCGSAFlAwQBKjALBglghkgBZQMEAQIwCgYIKoZIhvcN
AwcwDgYIKoZIhvcNAwICAgCAMA0GCCqGSIb3DQMCAgFAMAcGBSsOAwIHMA0GCCqGSIb3DQMC
AgEoMIGaBgkrBgEEAYI3EAQxgYwwgYkwdTELMAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0
Q29tIEx0ZC4xKTAnBgNVBAsTIFN0YXJ0Q29tIENlcnRpZmljYXRpb24gQXV0aG9yaXR5MSMw
IQYDVQQDExpTdGFydENvbSBDbGFzcyAxIENsaWVudCBDQQIQT82hO6c2L4lCcoZh0xQXZzCB
nAYLKoZIhvcNAQkQAgsxgYyggYkwdTELMAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0Q29t
IEx0ZC4xKTAnBgNVBAsTIFN0YXJ0Q29tIENlcnRpZmljYXRpb24gQXV0aG9yaXR5MSMwIQYD
VQQDExpTdGFydENvbSBDbGFzcyAxIENsaWVudCBDQQIQT82hO6c2L4lCcoZh0xQXZzANBgkq
hkiG9w0BAQEFAASCAQBWvmWeFGCnN3/HjFZJbFM2P4r+BBySB9p2OU9Q6uk6zSqZldKxq+oj
e8hkZf2X4YtYGlbEDexDE3Ly/wFyuaoY/6GByIOqPl4A8bVV+nBEZzF9hMfrTiiiWiS7mBnH
QhEqPnUqKRNO/d9Ui9C3UlB3D7SGOQclGorD8D1YYJkvNwAM/NptxykxahKDYh6PnluJQA7+
DAdcKJu7dGxuasrb+fjZC2C1hxfdZbIE24yqHOjFxQPoGirlv2USbBYqXmsxCz7zmaw3v+ax
erJpB7dED4J9QmisoM+TtG9auwgK4V4hbzbIiSuZwm6VIcHux/fnFXd9GkzPAANUsBYxdf7F
AAAAAAAA
--------------ms000304060308080808060609--


From nobody Mon Apr 11 16:01:34 2016
Return-Path: <chopps@chopps.org>
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 5A6EB12DABF for <ietf@ietfa.amsl.com>; Mon, 11 Apr 2016 16:01:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.896
X-Spam-Level: 
X-Spam-Status: No, score=-2.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.996] 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 PaiMJ4kUYqsW for <ietf@ietfa.amsl.com>; Mon, 11 Apr 2016 16:01:32 -0700 (PDT)
Received: from smtp.chopps.org (smtp.chopps.org [54.88.81.56]) by ietfa.amsl.com (Postfix) with ESMTP id 4AACB12DABD for <ietf@ietf.org>; Mon, 11 Apr 2016 16:01:31 -0700 (PDT)
Received: from tops.chopps.org (24-247-68-31.dhcp.trcy.mi.charter.com [24.247.68.31]) (using TLSv1.2 with cipher AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by smtp.chopps.org (Postfix) with ESMTPSA id B8FA961166; Mon, 11 Apr 2016 23:01:30 +0000 (UTC)
References: <m260vp7eke.wl%randy@psg.com> <570A6458.3050206@comcast.net> <m21t6d7c9t.wl%randy@psg.com> <570A67B4.3010206@comcast.net> <570AB3AF.2050401@gmail.com> <87twj99c6w.fsf@tops.chopps.org> <CAKe6YvMyp-DyeDwpPY6KYmbDbnpgnvVk_cUStnA32wmgDWcz3w@mail.gmail.com> <BBF5DDFE515C3946BC18D733B20DAD233A62AA18@XMB122CNC.rim.net> <20160411104519.GA19092@gsp.org> <3F48466D-390C-4C18-B958-732AE3E46FF1@gmail.com> <20160411223403.GA6743@gsp.org>
User-agent: mu4e 0.9.16; emacs 24.5.1
From: <chopps@chopps.org>
To: Rich Kulawiec <rsk@gsp.org>
Subject: Remote only meetings? [Re: Concerns about Singapore]
In-reply-to: <20160411223403.GA6743@gsp.org>
Date: Mon, 11 Apr 2016 19:01:16 -0400
Message-ID: <87twj7eon7.fsf@tops.chopps.org>
MIME-Version: 1.0
Content-Type: text/plain
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/kYuODzcZ34Dst4EijuElE6aXw2w>
Cc: 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: Mon, 11 Apr 2016 23:01:33 -0000

Having just participated remotely for this IETF 95, and having thought
about what I was missing while doing so, I feel that nothing can really
replace the actual IETF face-to-face meeting experience. We can strive
to do as much as possible to make remote be equal as possible
participant, but remote participation can never be a 100% substitute for
100s of colleagues spending an intense week together in the same
location focused morning, noon, and night; while eating, drinking,
meeting, relaxing, on the engineering of the Internet.

Why would we want to get rid of such a rich source of inspiration and
invention?

I don't see that meetings aren't working well, instead I think we're
trying to make them work even better through enhanced remote
participation (e.g., meetecho, remote hubs, etc).

Thanks,
Chris.


Rich Kulawiec <rsk@gsp.org> writes:

> On Mon, Apr 11, 2016 at 03:17:39PM +0300, Yoav Nir wrote:
>> I don???t believe that this technology exists.
>
> People have remote meetings all day, every day.   Lots of technology
> exists, more is being invented all the time.  Perhaps (to follow
> on your mention of Meetecho in 1995) if 20 years had been invested
> in making it work for the IETF then it would be working by now.
>
>> Yeah, perhaps, some day when we???re all wearing virtual reality
>> headsets and our avatars are hanging out in a virtual venue, and we all
>> have sufficient equipment and bandwidth to handle all that. We???re not
>> there yet.
>
> Nor is there any need to go there.  Meetings do not require VR.
>
>> Virtual meetings with the technology we have today makes it very hard
>> for people with mediocre English to follow the discussion.
>
> That's (a) not a very big problem and (b) a solvable problem.
>
>
> What I'm hearing is a lot of we've-always-done-it-this-way.  Well,
> that's not working very well except for the privileged elite few
> (most of whom are backed by corporations).  And I understand
> that those with plenty of money and time and freedom have gotten
> comfortable with how-things-are-done.  It's an easy thing to do,
> I've done it myself.   But it doesn't serve the long-term interests
> of the IETF or the Internet well.
>
> ---rsk


From nobody Mon Apr 11 16:55:13 2016
Return-Path: <mellon@fugue.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 602B412D1C1 for <ietf@ietfa.amsl.com>; Mon, 11 Apr 2016 16:55:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.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 OXyBxxe0ZGwK for <ietf@ietfa.amsl.com>; Mon, 11 Apr 2016 16:55:08 -0700 (PDT)
Received: from mail-lf0-x22b.google.com (mail-lf0-x22b.google.com [IPv6:2a00:1450:4010:c07::22b]) (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 8FC9312E627 for <ietf@ietf.org>; Mon, 11 Apr 2016 16:55:07 -0700 (PDT)
Received: by mail-lf0-x22b.google.com with SMTP id e190so2493773lfe.0 for <ietf@ietf.org>; Mon, 11 Apr 2016 16:55:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=ivJfiShQS6wJvcO1BeP2XK5wlnqEJb36d5H3pcwnkvI=; b=chmnaH3K+WHo4jPqxO4875/DyyoQSE3Q+zuQem618Yz0hqYeUeq6AOl3YKNvlRq54t EQ+pd4cW7dZ3qjFgv4zElBB/0vBE6jP9MdvPTq6TyXySqFsnJkl/RmThxaw6Uqdu6vCU NQxrtph3hMefXktUjO+yvVYeP5nOQTjjo+Kn0xRP9VNJ7js/+fVh6WtIfQ+bHw9wM96r FKxZnzP1JYODpm4Pp3zCCnd41YuXlHq0L1lbpvX2ncZ4EsBVix3JPVmWZSpTJhHAS7f9 4gVAKBmwCYB5+RWkZeLL0m/QtDr7SKznKoeL7+tKA0ApvjYLgXHIF1Q6PbCeJ6sYFbkC PdIw==
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=ivJfiShQS6wJvcO1BeP2XK5wlnqEJb36d5H3pcwnkvI=; b=Pi/xZNkTxQo3SvTla7bWF9LwVcNK3iI1CO52dMtaGwMrbMNoQfknUoNLtKJYD1PwL8 5MtFiTuTRvZolhtNcBMiQH+1CbZDSzuLcwFsHsAhL3PcIKO+I+esRt8buet4HbERlb4U ifH7Pyzm13tLfBX8zRNg06JsT4CtMjBNtbfuoEY+MqjdMPi498Xifyo/8YWljC6zOxX1 3Le2z2WbveV0xZMoZHokGNuCN4Io/iNo0TdWzdKNdcHBuwulYDhqJbLXsr/evdooneDX 8QvaOQppWcDxpYNJCCJ4xt4A948sUlf6r5Tg7stfI+XZ+I7jCmmPHq0kMENmQM2allRy XrXA==
X-Gm-Message-State: AOPr4FUrBqlmArbruBoa8TzevbvB2aJnrDGYoGL+oQAQTLtdgzLzW7HnYlTQJOby+5laGUkPeXsXT/N45yFbjA==
X-Received: by 10.112.13.8 with SMTP id d8mr78821lbc.110.1460418905323; Mon, 11 Apr 2016 16:55:05 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.25.40.136 with HTTP; Mon, 11 Apr 2016 16:54:25 -0700 (PDT)
X-Originating-IP: [71.233.41.235]
In-Reply-To: <20160411223403.GA6743@gsp.org>
References: <m260vp7eke.wl%randy@psg.com> <570A6458.3050206@comcast.net> <m21t6d7c9t.wl%randy@psg.com> <570A67B4.3010206@comcast.net> <570AB3AF.2050401@gmail.com> <87twj99c6w.fsf@tops.chopps.org> <CAKe6YvMyp-DyeDwpPY6KYmbDbnpgnvVk_cUStnA32wmgDWcz3w@mail.gmail.com> <BBF5DDFE515C3946BC18D733B20DAD233A62AA18@XMB122CNC.rim.net> <20160411104519.GA19092@gsp.org> <3F48466D-390C-4C18-B958-732AE3E46FF1@gmail.com> <20160411223403.GA6743@gsp.org>
From: Ted Lemon <mellon@fugue.com>
Date: Mon, 11 Apr 2016 19:54:25 -0400
Message-ID: <CAPt1N1nNo0=JSptQdWRZCFy1v-m6Q8NQy4WVGHtnRJuFZFmMig@mail.gmail.com>
Subject: Re: Concerns about Singapore
To: Rich Kulawiec <rsk@gsp.org>
Content-Type: multipart/alternative; boundary=001a11c3b44e1351c205303e462a
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/6lvKJ5NHrKby2VzZgQ0cqP7z2JI>
Cc: ietf <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: Mon, 11 Apr 2016 23:55:11 -0000

--001a11c3b44e1351c205303e462a
Content-Type: text/plain; charset=UTF-8

While I do not think it's true that we can entirely get away without doing
in-person meetings, I do agree with you that we can do better at doing
remote meetings.   Perhaps we should let this unfortunate event drive us to
make the attempt.

If we were to attempt such a thing, how do you think it would work?

On Mon, Apr 11, 2016 at 6:34 PM, Rich Kulawiec <rsk@gsp.org> wrote:

> On Mon, Apr 11, 2016 at 03:17:39PM +0300, Yoav Nir wrote:
> > I don???t believe that this technology exists.
>
> People have remote meetings all day, every day.   Lots of technology
> exists, more is being invented all the time.  Perhaps (to follow
> on your mention of Meetecho in 1995) if 20 years had been invested
> in making it work for the IETF then it would be working by now.
>
> > Yeah, perhaps, some day when we???re all wearing virtual reality
> > headsets and our avatars are hanging out in a virtual venue, and we all
> > have sufficient equipment and bandwidth to handle all that. We???re not
> > there yet.
>
> Nor is there any need to go there.  Meetings do not require VR.
>
> > Virtual meetings with the technology we have today makes it very hard
> > for people with mediocre English to follow the discussion.
>
> That's (a) not a very big problem and (b) a solvable problem.
>
>
> What I'm hearing is a lot of we've-always-done-it-this-way.  Well,
> that's not working very well except for the privileged elite few
> (most of whom are backed by corporations).  And I understand
> that those with plenty of money and time and freedom have gotten
> comfortable with how-things-are-done.  It's an easy thing to do,
> I've done it myself.   But it doesn't serve the long-term interests
> of the IETF or the Internet well.
>
> ---rsk
>
>

--001a11c3b44e1351c205303e462a
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">While I do not think it&#39;s true that we can entirely ge=
t away without doing in-person meetings, I do agree with you that we can do=
 better at doing remote meetings. =C2=A0 Perhaps we should let this unfortu=
nate event drive us to make the attempt.<div><br></div><div>If we were to a=
ttempt such a thing, how do you think it would work?</div></div><div class=
=3D"gmail_extra"><br><div class=3D"gmail_quote">On Mon, Apr 11, 2016 at 6:3=
4 PM, Rich Kulawiec <span dir=3D"ltr">&lt;<a href=3D"mailto:rsk@gsp.org" ta=
rget=3D"_blank">rsk@gsp.org</a>&gt;</span> wrote:<br><blockquote class=3D"g=
mail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-l=
eft:1ex">On Mon, Apr 11, 2016 at 03:17:39PM +0300, Yoav Nir wrote:<br>
&gt; I don???t believe that this technology exists.<br>
<br>
People have remote meetings all day, every day.=C2=A0 =C2=A0Lots of technol=
ogy<br>
exists, more is being invented all the time.=C2=A0 Perhaps (to follow<br>
on your mention of Meetecho in 1995) if 20 years had been invested<br>
in making it work for the IETF then it would be working by now.<br>
<br>
&gt; Yeah, perhaps, some day when we???re all wearing virtual reality<br>
<span class=3D"">&gt; headsets and our avatars are hanging out in a virtual=
 venue, and we all<br>
</span>&gt; have sufficient equipment and bandwidth to handle all that. We?=
??re not<br>
&gt; there yet.<br>
<br>
Nor is there any need to go there.=C2=A0 Meetings do not require VR.<br>
<span class=3D""><br>
&gt; Virtual meetings with the technology we have today makes it very hard<=
br>
&gt; for people with mediocre English to follow the discussion.<br>
<br>
</span>That&#39;s (a) not a very big problem and (b) a solvable problem.<br=
>
<br>
<br>
What I&#39;m hearing is a lot of we&#39;ve-always-done-it-this-way.=C2=A0 W=
ell,<br>
that&#39;s not working very well except for the privileged elite few<br>
(most of whom are backed by corporations).=C2=A0 And I understand<br>
that those with plenty of money and time and freedom have gotten<br>
comfortable with how-things-are-done.=C2=A0 It&#39;s an easy thing to do,<b=
r>
I&#39;ve done it myself.=C2=A0 =C2=A0But it doesn&#39;t serve the long-term=
 interests<br>
of the IETF or the Internet well.<br>
<br>
---rsk<br>
<br>
</blockquote></div><br></div>

--001a11c3b44e1351c205303e462a--


From nobody Mon Apr 11 17:07:37 2016
Return-Path: <farmer@umn.edu>
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 28F2012D65E for <ietf@ietfa.amsl.com>; Mon, 11 Apr 2016 17:07:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.995
X-Spam-Level: 
X-Spam-Status: No, score=-2.995 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_NONE=-0.0001, RP_MATCHES_RCVD=-0.996] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=umn.edu
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 r48JA-0VaOcG for <ietf@ietfa.amsl.com>; Mon, 11 Apr 2016 17:07:33 -0700 (PDT)
Received: from mta-p8.oit.umn.edu (mta-p8.oit.umn.edu [134.84.196.208]) (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 E17D612D0E4 for <ietf@ietf.org>; Mon, 11 Apr 2016 17:07:32 -0700 (PDT)
Received: from localhost (unknown [127.0.0.1]) by mta-p8.oit.umn.edu (Postfix) with ESMTP id 4D0AD9A6 for <ietf@ietf.org>; Tue, 12 Apr 2016 00:07:32 +0000 (UTC)
X-Virus-Scanned: amavisd-new at umn.edu
Received: from mta-p8.oit.umn.edu ([127.0.0.1]) by localhost (mta-p8.oit.umn.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AaUZDBjyl75k for <ietf@ietf.org>; Mon, 11 Apr 2016 19:07:32 -0500 (CDT)
Received: from mail-lf0-f52.google.com (mail-lf0-f52.google.com [209.85.215.52]) (using TLSv1.2 with cipher AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mta-p8.oit.umn.edu (Postfix) with ESMTPS id C2C43973 for <ietf@ietf.org>; Mon, 11 Apr 2016 19:07:31 -0500 (CDT)
Received: by mail-lf0-f52.google.com with SMTP id j11so2719778lfb.1 for <ietf@ietf.org>; Mon, 11 Apr 2016 17:07:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=umn.edu; s=google; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=inau+gG/H5YKBj6BljgiXzwGUVTtshDFSCr6nfi+udA=; b=K9mZwYVRaJaVLFclWMKliTkqE1KgH2+6TFNsR1jNBO7DFOCSHAX30O5DX4u5TH/OiL 0ESOt+ZzOI+fTOy4mXze8r07+oYrPMTYMgx0wdmN/l0PuFCsHYO7jiRR6+TjLPUZyqsf LcSDc3gCgAx5+50TNvgGQvlEUCB1zu2XdAD1A=
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:date :message-id:subject:from:to:cc; bh=inau+gG/H5YKBj6BljgiXzwGUVTtshDFSCr6nfi+udA=; b=MdNz6qiQuYrtxT5BOCgiKC4Ge2/OmUX525klJPDTutaMLgsFZXeYUOJcGYl56a4yS5 phTtd3rmZ5I+dKgri71pmLuiHlzQ+URMEbM5YjSFkMmlbbbctdz8GKy8qVa49O7Ugvbr LiNfJrUQa2iwkoHDHpF/h1LPoIPcLno9uiwDH2UFbEmWePIEDzDi2kPlGY+isyXYnOXF SA/3nWT9mY+5HhfIQP04e2VogyDrrJsRy1rDDWC+x+g+NUPNRmQUEWqoJOaCH5ensR6D kBFTl5HXo9vObad3Y/lS2njtMkxQFXHeQIUDjeoibV6edgPqZSASsn8yIIq6mXxf6q60 joPw==
X-Gm-Message-State: AOPr4FWQra6V8pyYSVQNDTUZcuQglELANO+JjvIXURcLm8/VPOCUth9YnCMlPSIB9ttSt7zdeJZE9lSa3prg3VPMalYfARhOT9p1vmKnvwVMe179apYdcmBrL7/h772q0wxPxWdjUDQlb80kFfs=
X-Received: by 10.25.153.5 with SMTP id b5mr79189lfe.122.1460419650464; Mon, 11 Apr 2016 17:07:30 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.25.153.5 with SMTP id b5mr79183lfe.122.1460419650319; Mon, 11 Apr 2016 17:07:30 -0700 (PDT)
Received: by 10.25.78.148 with HTTP; Mon, 11 Apr 2016 17:07:30 -0700 (PDT)
In-Reply-To: <570C2985.9030701@cs.tcd.ie>
References: <m260vp7eke.wl%randy@psg.com> <570A6458.3050206@comcast.net> <m21t6d7c9t.wl%randy@psg.com> <570A67B4.3010206@comcast.net> <570AB3AF.2050401@gmail.com> <87twj99c6w.fsf@tops.chopps.org> <CAKe6YvMyp-DyeDwpPY6KYmbDbnpgnvVk_cUStnA32wmgDWcz3w@mail.gmail.com> <BBF5DDFE515C3946BC18D733B20DAD233A62AA18@XMB122CNC.rim.net> <20160411104519.GA19092@gsp.org> <3F48466D-390C-4C18-B958-732AE3E46FF1@gmail.com> <20160411223403.GA6743@gsp.org> <570C2985.9030701@cs.tcd.ie>
Date: Mon, 11 Apr 2016 19:07:30 -0500
Message-ID: <CAN-Dau0JzMNrUFU6baX1=M4FtfF85oEkyr7PmSbt5TBNPMHumQ@mail.gmail.com>
Subject: Re: 1000 person virtual meeting (Was: Re: Concerns about Singapore)
From: David Farmer <farmer@umn.edu>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Content-Type: multipart/alternative; boundary=001a114034ec7b09a905303e728f
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/44-cPXL0UwMZuTMHcTdPGgxYfWM>
Cc: Rich Kulawiec <rsk@gsp.org>, IETF-Discussion 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: Tue, 12 Apr 2016 00:07:36 -0000

--001a114034ec7b09a905303e728f
Content-Type: text/plain; charset=UTF-8

On Mon, Apr 11, 2016 at 5:47 PM, Stephen Farrell <stephen.farrell@cs.tcd.ie>
wrote:
>
>
> But maybe I'm wrong - can you send details of how an approx.
> 1000 person virtual meeting where everyone could provide real
> input has been held by anyone? I'm unaware of such but I'd
> be very interested if that had happened already.
>

It is definitely a challenge, but it has been done, just like a real
meeting with 1000 people in the room frequently ends up being mostly one
person or small group talking and then questions being asked by the
audience, this can be accomplished virtually too.

There was a recurring annual event;

http://www.megaconference.org/past.html

And in Fall of 2001 because of the events of 911, Internet2 canceled its
Member Meeting in San Antonio and held a Virtual Member Meeting in early
October 2001.  I can't find much online regarding it any longer, but it is
listed on the list of past meetings.

http://www.internet2.edu/news-events/events/past-events/past-annual-member-meetings/

These are a few examples I know of, I'm sure there are others.

-- 
===============================================
David Farmer               Email:farmer@umn.edu
Networking & Telecommunication Services
Office of Information Technology
University of Minnesota
2218 University Ave SE        Phone: 612-626-0815
Minneapolis, MN 55414-3029   Cell: 612-812-9952
===============================================

--001a114034ec7b09a905303e728f
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><div class=3D"gmail_quo=
te">On Mon, Apr 11, 2016 at 5:47 PM, Stephen Farrell <span dir=3D"ltr">&lt;=
<a href=3D"mailto:stephen.farrell@cs.tcd.ie" target=3D"_blank">stephen.farr=
ell@cs.tcd.ie</a>&gt;</span> wrote:<blockquote class=3D"gmail_quote" style=
=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(20=
4,204,204);border-left-style:solid;padding-left:1ex">
<br>
But maybe I&#39;m wrong - can you send details of how an approx.<br>
1000 person virtual meeting where everyone could provide real<br>
input has been held by anyone? I&#39;m unaware of such but I&#39;d<br>
be very interested if that had happened already.<br></blockquote><div><br><=
/div><div>It is definitely a challenge, but it has been done, just like a r=
eal meeting with 1000 people in the room frequently ends up being mostly on=
e person or small group talking and then questions being asked by the audie=
nce, this can be accomplished virtually too.=C2=A0<br></div><div><br></div>=
<div>There was a recurring annual event;</div><div><br></div><div><a href=
=3D"http://www.megaconference.org/past.html">http://www.megaconference.org/=
past.html</a>=C2=A0</div></div><br>And in Fall of 2001 because of the event=
s of 911, Internet2 canceled its Member Meeting in San Antonio and held a V=
irtual=C2=A0Member Meeting=C2=A0in early October 2001.=C2=A0 I can&#39;t fi=
nd much online regarding it any longer, but it is listed on the list of pas=
t meetings.</div><div class=3D"gmail_extra"><br></div><div class=3D"gmail_e=
xtra"><a href=3D"http://www.internet2.edu/news-events/events/past-events/pa=
st-annual-member-meetings/">http://www.internet2.edu/news-events/events/pas=
t-events/past-annual-member-meetings/</a><br></div><div class=3D"gmail_extr=
a"><br></div><div class=3D"gmail_extra">These are a few examples I know of,=
 I&#39;m sure there are others.</div><div class=3D"gmail_extra"><div><br></=
div>-- <br><div class=3D"gmail_signature">=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br>David Farmer=C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0=C2=A0 <a href=3D"mailto:Email%3Afarmer@umn.edu" ta=
rget=3D"_blank">Email:farmer@umn.edu</a><br>Networking &amp; Telecommunicat=
ion Services<br>Office of Information Technology<br>University of Minnesota=
=C2=A0=C2=A0 <br>2218 University Ave SE=C2=A0 =C2=A0 =C2=A0 =C2=A0 Phone: 6=
12-626-0815<br>Minneapolis, MN 55414-3029=C2=A0=C2=A0 Cell: 612-812-9952<br=
>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D </div=
>
</div></div>

--001a114034ec7b09a905303e728f--


From nobody Mon Apr 11 17:08:51 2016
Return-Path: <lloyd.wood@yahoo.co.uk>
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 3D3C612F1F7 for <ietf@ietfa.amsl.com>; Mon, 11 Apr 2016 17:08:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level: 
X-Spam-Status: No, score=-2.701 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, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-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=yahoo.co.uk
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 Sjk4R6m1dvYk for <ietf@ietfa.amsl.com>; Mon, 11 Apr 2016 17:08:49 -0700 (PDT)
Received: from nm27-vm8.bullet.mail.ir2.yahoo.com (nm27-vm8.bullet.mail.ir2.yahoo.com [212.82.97.59]) (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 9B5AB12F1AB for <ietf@ietf.org>; Mon, 11 Apr 2016 17:08:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.co.uk; s=s2048;  t=1460419727; bh=1IJf2Zfua/2OjKavBFDj8OSbkSeePJxRxE/9nW73GZc=;  h=Date:From:Reply-To:To:In-Reply-To:References:Subject:From:Subject;  b=DzhZeTV19XENLLKmbwO5mrcvwM9A5bFh0toDZzF8N+bP+H6B6ya+Gh9QrOABcnErZUtz+XsWXkBNMqum/lTjt50ocbVmk0p5OCI9Ia8fNehd9DoPsmubUvc2NrHXfVGbm4K3jwtcV8Z+dgEX4AwEIX60SGeJswkngvjBd7Q8HvEGHQtZJ+njl9T1Fl2rdV5po/vVODqlI0yfHLBWZ4ep7xY0mWI11D3csMVvTvjxZZAbKYOiWjyXli/pagWJky139/CRRqqIBuE1PaIhqjJMi9IQRz7tonEa3GURm94NrP9ZmD2FtTdIDnyOEpIC7sTE+zdRpAhm2o5T5zBESpZM6w==
Received: from [212.82.98.63] by nm27.bullet.mail.ir2.yahoo.com with NNFMP; 12 Apr 2016 00:08:47 -0000
Received: from [212.82.98.73] by tm16.bullet.mail.ir2.yahoo.com with NNFMP; 12 Apr 2016 00:08:47 -0000
Received: from [127.0.0.1] by omp1010.mail.ir2.yahoo.com with NNFMP; 12 Apr 2016 00:08:47 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 46431.20316.bm@omp1010.mail.ir2.yahoo.com
X-YMail-OSG: Uy3gi1YVM1mthuKKhGqSqJigx.PTVi8txXTE64f7JsEas6hiOptGTriNHZyPfoZ GP3_CBNLWIokJssbXVgrO2Wu0tR24SMdsBXIMv1pCx3PpE6SGCaxV7DN4Nygg_BXKmiloUkAnhDO feArKsUL4QDAymU6VAE0LHajp.3omPPvgRNwDEjbc8PQlIi8oRvK.jl1MtRxkQo0j_Ktz_CB5FgR RkysLNKczFiclz9mliXi8b.Q8w_tmQvC07UL1y0w84367T.TWVCKOjR_uo9xwes5yyvZTajOw2Qu fuLA1P98BN0qfs_PHXoS3jCBUghl_tINxG01es1FlBk7xRRvevhWcTZf4u5k0qZlXV9dz0TBl.Pw rUe7UjrSPo3L0a_RmTz2qZYR7bFlqYwtxK6Omdxfbl16VFMh7XaZZc3XJFGbDTyJYHRe.wS8wvfo lq_KO5FrmjivETqjnstmuNRXkXvPxOpByNyG7AfCOwU6Q8JZXoezA6kc5ePEuc6jG4xSAtvXkIoA L31eFNihgT77wT.kskw--
Received: by 212.82.98.123; Tue, 12 Apr 2016 00:08:46 +0000 
Date: Tue, 12 Apr 2016 00:08:34 +0000 (UTC)
From: <lloyd.wood@yahoo.co.uk>
To: Rich Kulawiec <rsk@gsp.org>, "ietf@ietf.org" <ietf@ietf.org>
Message-ID: <860206232.1954211.1460419714948.JavaMail.yahoo@mail.yahoo.com>
In-Reply-To: <20160411223403.GA6743@gsp.org>
References: <20160411223403.GA6743@gsp.org>
Subject: Meetecho was Re: Concerns about Singapore
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/ns79kuHFWdAaCE8Z-5HSy2U5FsM>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: lloyd.wood@yahoo.co.uk
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: Tue, 12 Apr 2016 00:08:50 -0000

> People have remote meetings all day, every day.   Lots of technology
> exists, more is being invented all the time.  Perhaps (to follow
> on your mention of Meetecho in 1995) if 20 years had been invested
> in making it work for the IETF then it would be working by now.


http://recs.conf.meetecho.com/Playout/watch.jsp?recording=IETF95_DTN&chapter=chapter_1

try listening to the first twenty minutes of this.
then tell me if IETF WG meetings with remote presentation
via Meetecho are anything other than a complete waste
of time.

L.

it's not the mediocre English. It's the mediocracy.


Lloyd Wood lloyd.wood@yahoo.co.uk http://about.me/lloydwood 

________________________________
From: Rich Kulawiec <rsk@gsp.org>
To: ietf@ietf.org 
Sent: Tuesday, 12 April 2016, 8:34
Subject: Re: Concerns about Singapore


On Mon, Apr 11, 2016 at 03:17:39PM +0300, Yoav Nir wrote:
> I don???t believe that this technology exists. 

People have remote meetings all day, every day.   Lots of technology
exists, more is being invented all the time.  Perhaps (to follow
on your mention of Meetecho in 1995) if 20 years had been invested
in making it work for the IETF then it would be working by now.

> Yeah, perhaps, some day when we???re all wearing virtual reality
> headsets and our avatars are hanging out in a virtual venue, and we all
> have sufficient equipment and bandwidth to handle all that. We???re not
> there yet.

Nor is there any need to go there.  Meetings do not require VR.

> Virtual meetings with the technology we have today makes it very hard
> for people with mediocre English to follow the discussion.

That's (a) not a very big problem and (b) a solvable problem.  


What I'm hearing is a lot of we've-always-done-it-this-way.  Well,
that's not working very well except for the privileged elite few
(most of whom are backed by corporations).  And I understand
that those with plenty of money and time and freedom have gotten
comfortable with how-things-are-done.  It's an easy thing to do,
I've done it myself.   But it doesn't serve the long-term interests
of the IETF or the Internet well.


---rsk


From nobody Mon Apr 11 17:13:53 2016
Return-Path: <mellon@fugue.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 0B3B012D716 for <ietf@ietfa.amsl.com>; Mon, 11 Apr 2016 17:13:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.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 V7eraJ_oZvJt for <ietf@ietfa.amsl.com>; Mon, 11 Apr 2016 17:13:51 -0700 (PDT)
Received: from mail-lf0-x22a.google.com (mail-lf0-x22a.google.com [IPv6:2a00:1450:4010:c07::22a]) (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 0E4DB12E68E for <ietf@ietf.org>; Mon, 11 Apr 2016 17:13:49 -0700 (PDT)
Received: by mail-lf0-x22a.google.com with SMTP id c126so2824976lfb.2 for <ietf@ietf.org>; Mon, 11 Apr 2016 17:13:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=64j/FwruaYDr0FAf65r8/LRti8jJBUph366qWjs+TkI=; b=Y8fNtYi9hQhV0+jA2NjwyBmhbT6wIVwt1h+mK292sVOOJ89tV0uSoULinFvLTwmgf7 Idlf7ofaCotPlT0+HH63TXMV3ZrSQK0jESUjI2PDMLC8CKy92bhZ4yFJaoRDkDzyLJt0 D2B5yQltCkuYxosY+6nmp4bcYygVyFfDSYhNKZXeO42bKcVUuCYNrEZn4OYwDBKxozEG k1VTZKlrmSnADzL0Pdj/i/zhZg1aT/Rj2sP6NTpOFUwF7YqpJhNU6sehes/4Qc4XPaEw RfKm2L3zGLmnPXL7JzWa8eUvfo2BuuNcVQ4k6hgt76NWMbpJGMqWEJI1J11M4IMfIL2R tUkw==
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; bh=64j/FwruaYDr0FAf65r8/LRti8jJBUph366qWjs+TkI=; b=QR7AMfM+Xm4ip5FVeEMO4zEoGxg6gnsEbrxT1g2qkCtyDf+Qyy/0Z3zXkMZF3c9CyE R+F/gF2o/ZSkfsKWax+CqFC0Ylq3WW9VcKErG8CzFQylV3qbCmYi/e8fJsr2Z6wWuTV9 euxtKEOPQDOstN+FPuZT/o/YPmdwIZxNcEvi9p6odgLgoDMFHfQ/A0/ZdAJSu7tA0qHx E0K3a9IT2tz3Cwh+mLogtKn/AdjMsfEZ8cZRiL1Q+amnD3KA7rXMW5UHFPnWWjSjXx4f jhuz7+LHNw3Jjb2yue+nk+E1xhy4LrudrLaB5cciwFXoGu7rbt74dWVgsraXF4KASAi+ DOSg==
X-Gm-Message-State: AOPr4FUNXF/0v4R/K3sJOKDFmTmFiKJtuF+xNePAvlGgCC6gt2oFQv6Mg+wT4kj3j0dPKVUV7hVlz9/GCPK85g==
X-Received: by 10.112.169.105 with SMTP id ad9mr85847lbc.135.1460420027129; Mon, 11 Apr 2016 17:13:47 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.25.40.136 with HTTP; Mon, 11 Apr 2016 17:13:07 -0700 (PDT)
X-Originating-IP: [71.233.41.235]
In-Reply-To: <CAN-Dau0JzMNrUFU6baX1=M4FtfF85oEkyr7PmSbt5TBNPMHumQ@mail.gmail.com>
References: <m260vp7eke.wl%randy@psg.com> <570A6458.3050206@comcast.net> <m21t6d7c9t.wl%randy@psg.com> <570A67B4.3010206@comcast.net> <570AB3AF.2050401@gmail.com> <87twj99c6w.fsf@tops.chopps.org> <CAKe6YvMyp-DyeDwpPY6KYmbDbnpgnvVk_cUStnA32wmgDWcz3w@mail.gmail.com> <BBF5DDFE515C3946BC18D733B20DAD233A62AA18@XMB122CNC.rim.net> <20160411104519.GA19092@gsp.org> <3F48466D-390C-4C18-B958-732AE3E46FF1@gmail.com> <20160411223403.GA6743@gsp.org> <570C2985.9030701@cs.tcd.ie> <CAN-Dau0JzMNrUFU6baX1=M4FtfF85oEkyr7PmSbt5TBNPMHumQ@mail.gmail.com>
From: Ted Lemon <mellon@fugue.com>
Date: Mon, 11 Apr 2016 20:13:07 -0400
Message-ID: <CAPt1N1kKMDvZt6K_QxRt4SVbzw6FOjkXH2fFbntxWn28i=NLfA@mail.gmail.com>
Subject: Re: 1000 person virtual meeting (Was: Re: Concerns about Singapore)
To: IETF-Discussion Discussion <ietf@ietf.org>
Content-Type: multipart/alternative; boundary=001a11c38c08f0b7b605303e8810
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/4Dh5YkPGxjO6PXMCnJUIedkjx-4>
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: Tue, 12 Apr 2016 00:13:53 -0000

--001a11c38c08f0b7b605303e8810
Content-Type: text/plain; charset=UTF-8

The challenge here is not so much that doing a 1000-person remote meeting
is impossible to do, but that doing a 1000-person remote meeting that winds
up being as effective as a 1000-person in-person meeting is hard to do.
If we decided to make it a priority, I'd be willing to bet that we could
come up with something fairly cromulent.   Of course it would not be
exactly the same as an in-person meeting; it would have things that went
better, and things that went worse.   But if we decided to do it, we could
definitely do it, and it would be worth doing.

On Mon, Apr 11, 2016 at 8:07 PM, David Farmer <farmer@umn.edu> wrote:

>
>
> On Mon, Apr 11, 2016 at 5:47 PM, Stephen Farrell <
> stephen.farrell@cs.tcd.ie> wrote:
>>
>>
>> But maybe I'm wrong - can you send details of how an approx.
>> 1000 person virtual meeting where everyone could provide real
>> input has been held by anyone? I'm unaware of such but I'd
>> be very interested if that had happened already.
>>
>
> It is definitely a challenge, but it has been done, just like a real
> meeting with 1000 people in the room frequently ends up being mostly one
> person or small group talking and then questions being asked by the
> audience, this can be accomplished virtually too.
>
> There was a recurring annual event;
>
> http://www.megaconference.org/past.html
>
> And in Fall of 2001 because of the events of 911, Internet2 canceled its
> Member Meeting in San Antonio and held a Virtual Member Meeting in early
> October 2001.  I can't find much online regarding it any longer, but it is
> listed on the list of past meetings.
>
>
> http://www.internet2.edu/news-events/events/past-events/past-annual-member-meetings/
>
> These are a few examples I know of, I'm sure there are others.
>
> --
> ===============================================
> David Farmer               Email:farmer@umn.edu
> Networking & Telecommunication Services
> Office of Information Technology
> University of Minnesota
> 2218 University Ave SE        Phone: 612-626-0815
> Minneapolis, MN 55414-3029   Cell: 612-812-9952
> ===============================================
>

--001a11c38c08f0b7b605303e8810
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">The challenge here is not so much that doing a 1000-person=
 remote meeting is impossible to do, but that doing a 1000-person remote me=
eting that winds up being as effective as a 1000-person in-person meeting i=
s hard to do. =C2=A0 If we decided to make it a priority, I&#39;d be willin=
g to bet that we could come up with something fairly cromulent. =C2=A0 Of c=
ourse it would not be exactly the same as an in-person meeting; it would ha=
ve things that went better, and things that went worse. =C2=A0 But if we de=
cided to do it, we could definitely do it, and it would be worth doing.</di=
v><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Mon, Apr 11,=
 2016 at 8:07 PM, David Farmer <span dir=3D"ltr">&lt;<a href=3D"mailto:farm=
er@umn.edu" target=3D"_blank">farmer@umn.edu</a>&gt;</span> wrote:<br><bloc=
kquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #cc=
c solid;padding-left:1ex"><div dir=3D"ltr"><br><div class=3D"gmail_extra"><=
br><div class=3D"gmail_quote"><span class=3D"">On Mon, Apr 11, 2016 at 5:47=
 PM, Stephen Farrell <span dir=3D"ltr">&lt;<a href=3D"mailto:stephen.farrel=
l@cs.tcd.ie" target=3D"_blank">stephen.farrell@cs.tcd.ie</a>&gt;</span> wro=
te:<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;bord=
er-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:soli=
d;padding-left:1ex">
<br>
But maybe I&#39;m wrong - can you send details of how an approx.<br>
1000 person virtual meeting where everyone could provide real<br>
input has been held by anyone? I&#39;m unaware of such but I&#39;d<br>
be very interested if that had happened already.<br></blockquote><div><br><=
/div></span><div>It is definitely a challenge, but it has been done, just l=
ike a real meeting with 1000 people in the room frequently ends up being mo=
stly one person or small group talking and then questions being asked by th=
e audience, this can be accomplished virtually too.=C2=A0<br></div><div><br=
></div><div>There was a recurring annual event;</div><div><br></div><div><a=
 href=3D"http://www.megaconference.org/past.html" target=3D"_blank">http://=
www.megaconference.org/past.html</a>=C2=A0</div></div><br>And in Fall of 20=
01 because of the events of 911, Internet2 canceled its Member Meeting in S=
an Antonio and held a Virtual=C2=A0Member Meeting=C2=A0in early October 200=
1.=C2=A0 I can&#39;t find much online regarding it any longer, but it is li=
sted on the list of past meetings.</div><div class=3D"gmail_extra"><br></di=
v><div class=3D"gmail_extra"><a href=3D"http://www.internet2.edu/news-event=
s/events/past-events/past-annual-member-meetings/" target=3D"_blank">http:/=
/www.internet2.edu/news-events/events/past-events/past-annual-member-meetin=
gs/</a><br></div><div class=3D"gmail_extra"><br></div><div class=3D"gmail_e=
xtra">These are a few examples I know of, I&#39;m sure there are others.</d=
iv><span class=3D"HOEnZb"><font color=3D"#888888"><div class=3D"gmail_extra=
"><div><br></div>-- <br><div>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D<br>David Farmer=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0=C2=A0 <a href=3D"mailto:Email%3Afarmer@umn.edu" target=3D"_blank=
">Email:farmer@umn.edu</a><br>Networking &amp; Telecommunication Services<b=
r>Office of Information Technology<br>University of Minnesota=C2=A0=C2=A0 <=
br>2218 University Ave SE=C2=A0 =C2=A0 =C2=A0 =C2=A0 Phone: <a href=3D"tel:=
612-626-0815" value=3D"+16126260815" target=3D"_blank">612-626-0815</a><br>=
Minneapolis, MN 55414-3029=C2=A0=C2=A0 Cell: <a href=3D"tel:612-812-9952" v=
alue=3D"+16128129952" target=3D"_blank">612-812-9952</a><br>=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D </div>
</div></font></span></div>
</blockquote></div><br></div>

--001a11c38c08f0b7b605303e8810--


From nobody Mon Apr 11 17:17:06 2016
Return-Path: <samita.chakrabarti@ericsson.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 6FFCB12D8AD for <ietf@ietfa.amsl.com>; Mon, 11 Apr 2016 17:17:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] 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 yMs18w3EwGFo for <ietf@ietfa.amsl.com>; Mon, 11 Apr 2016 17:17:04 -0700 (PDT)
Received: from usplmg20.ericsson.net (usplmg20.ericsson.net [198.24.6.45]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3E43C12D70E for <ietf@ietf.org>; Mon, 11 Apr 2016 17:17:04 -0700 (PDT)
X-AuditID: c618062d-f79216d00000767f-4c-570c380781c2
Received: from EUSAAHC007.ericsson.se (Unknown_Domain [147.117.188.93]) by usplmg20.ericsson.net (Symantec Mail Security) with SMTP id EF.4B.30335.7083C075; Tue, 12 Apr 2016 01:49:27 +0200 (CEST)
Received: from EUSAAMB103.ericsson.se ([147.117.188.120]) by EUSAAHC007.ericsson.se ([147.117.188.93]) with mapi id 14.03.0248.002; Mon, 11 Apr 2016 20:17:02 -0400
From: Samita Chakrabarti <samita.chakrabarti@ericsson.com>
To: Greg Shepherd <gjshep@gmail.com>, Randy Bush <randy@psg.com>
Subject: RE: thank you
Thread-Topic: thank you
Thread-Index: AQHRlDvEYmtFfQLRMEKZJXn2jazV/p+FmGiA///enxA=
Date: Tue, 12 Apr 2016 00:17:02 +0000
Message-ID: <ECA43DA70480A3498E43C3471FB2E1F02237A98C@eusaamb103.ericsson.se>
References: <m24mb76cns.wl%randy@psg.com> <0773370A-98DF-421D-B286-20764AD8F724@gmail.com>
In-Reply-To: <0773370A-98DF-421D-B286-20764AD8F724@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [147.117.188.10]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFmpmkeLIzCtJLcpLzFFi42KZXLonVpfdgifcYN49K4stc/Isnm2cz2Lx rPUlkwOzx85Zd9k9liz5yeQxdeZsxgDmKC6blNSczLLUIn27BK6M7kML2Qo2cFQcu+7TwHiJ rYuRk0NCwERieu8eFghbTOLCvfVAcS4OIYGjjBJzvn9lhnCWM0q8fTGNFaSKTcBKoqN3DzuI LSLgIDHj83tGEJtZQFWi69kaJhBbGGjS09krgGo4gGrEJaZ1ckOUW0lMPvCZGcRmASp/eusk WDmvgK/E3dt3wcYICcRITLjRBnYQp4CtxON1O8FqGIFGfj8FMZ4ZaOStJ/OZII4WkFiy5zwz hC0q8fLxP1YIW0li0tJzrBD1OhILdn9ig7C1JZYtfM0MsVdQ4uTMJywTGMVmIRk7C0nLLCQt s5C0LGBkWcXIUVpckJObbmSwiREYNcck2HR3MN6f7nmIUYCDUYmHV4GVO1yINbGsuDL3EKME B7OSCO8+G55wId6UxMqq1KL8+KLSnNTiQ4zSHCxK4ryNwf/ChATSE0tSs1NTC1KLYLJMHJxS DYwba7pn8D+fpupx83Pu4os9KQLeU6xOHjku+cfb+tKlyvsMyy++vvO8wOuDq71GolT92Vcv a1gO/NcJv/RoxvQHyvFhR/k/GpgENy7SOXsiO4TH+pL04aod4jMf7xJzdODrmjv3mnDyUwdp jRaZyiVnLBaum/Txo1VAZnVU8Ymbqb4C+084bzuqxFKckWioxVxUnAgADAM4cJYCAAA=
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/_zBxkUtVIcLMK7NzJ3FE_u3R84g>
Cc: IETF Disgust List <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: Tue, 12 Apr 2016 00:17:05 -0000

It was indeed a great  IETF experience in Buenos Aires- friendly local peop=
le, great food and excellent network connectivity all through the week!
It speaks for  itself as to how important is a f2f meeting for human intera=
ction and giving experiences of IETF first hand to the region.
Thanks to the organizers for this wonderful experience.

-Samita


-----Original Message-----
From: ietf [mailto:ietf-bounces@ietf.org] On Behalf Of Greg Shepherd
Sent: Monday, April 11, 2016 3:10 PM
To: Randy Bush
Cc: IETF Disgust List
Subject: Re: thank you

I couldn't agree more. Few times I leave IETF wishing I had time to stay lo=
nger. Thanks to everyone who had a hand putting this all together.

Greg

Sent from my iPhone

> On Apr 11, 2016, at 14:47, Randy Bush <randy@psg.com> wrote:
>=20
> buenos aires is a beautiful latin american city, hospitable, and with=20
> great folk.  kudos for such a great meeting go to many people and=20
> organizations that i will not enumerate for fear of missing one. =20
> thank you.
>=20
> randy
>=20


From nobody Mon Apr 11 17:18:59 2016
Return-Path: <ggm@algebras.org>
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 0B21B12EFDB for <ietf@ietfa.amsl.com>; Mon, 11 Apr 2016 17:18:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=algebras-org.20150623.gappssmtp.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 mkPesImSCCjx for <ietf@ietfa.amsl.com>; Mon, 11 Apr 2016 17:18:55 -0700 (PDT)
Received: from mail-oi0-x22e.google.com (mail-oi0-x22e.google.com [IPv6:2607:f8b0:4003:c06::22e]) (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 254A812EFE8 for <ietf@ietf.org>; Mon, 11 Apr 2016 17:18:55 -0700 (PDT)
Received: by mail-oi0-x22e.google.com with SMTP id y204so3086936oie.3 for <ietf@ietf.org>; Mon, 11 Apr 2016 17:18:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=algebras-org.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=4R/32mUYD7WaF6kByjdxVfn04LTMxEmNd7YF4vH7Km8=; b=FNq21PkygrU0cLfPAPrXygiKiv/MRFcA/sTrES/iobBKkq5VITqAxRLSHfEqS5V/UJ aH2PowiyCXt28GeylHFEWf/ODsk+vsOw9Q6I5jpXYVaq7hxDBNUKqNAH9xwuITnuKhF6 OTwju+BlosglIir7AXz1pW6R6PlZ6YsbXmRdYrUvdMWgE5v8bPL7OMckHy6hm86RFj+M wVEoI/1XwftKz/NQc6BoJID7cPA9Z8ErkxHV6QqiymeBKBQ7KhxwIguW8CivVJ8vWyj+ jJzZYKQcUU/YAe4qlDfBqsb4WRdXYZYUpRcany94oMa5QueRHM1S7y0ZwclXjH+7pkvs sPIg==
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:date :message-id:subject:from:to:cc; bh=4R/32mUYD7WaF6kByjdxVfn04LTMxEmNd7YF4vH7Km8=; b=aDy+UHY9utxmsg+p+5M/LE7TeAjbTe5idWdqjanSo39Dj5WXF9TF3wB9iPzxK6iDQ6 hqk9ufQ5WTH+jc9tjHneWK5YuCQrFVWUYkSTg5+qkpwInW31hycScsZOrQKkP2DUCwk6 cRdyGWq5f6+czJRvUhcZZYtX9tr+DQogCtAaLjWFI6/QcaHZLEHCSSy6G7xiWgtkQdIf eTwnLmE0If5e1YPkxYuZz7sxzRdPrJ3DtISLhtWra5JeF5BTjaTyyPQmKtRUjN1Bfrtb Io3SWqDmXqXi76WizVNzdEkPeypnKb2hcWavCswsuHmfeME5S5xIDqlkpua031JguXFP 5AVw==
X-Gm-Message-State: AOPr4FXwyMFFXPI8RbKHj9q80NqIp77sdCa+LpxMNGDOUmBIf47aFdr8GQwb5HbXFpY5UEE/NIB8M3qhfO1Oww==
MIME-Version: 1.0
X-Received: by 10.202.105.205 with SMTP id e196mr96353oic.113.1460420334485; Mon, 11 Apr 2016 17:18:54 -0700 (PDT)
Received: by 10.182.19.225 with HTTP; Mon, 11 Apr 2016 17:18:54 -0700 (PDT)
X-Originating-IP: [2001:dc0:a000:4:b038:4565:ffb1:47d1]
In-Reply-To: <CAPt1N1nNo0=JSptQdWRZCFy1v-m6Q8NQy4WVGHtnRJuFZFmMig@mail.gmail.com>
References: <m260vp7eke.wl%randy@psg.com> <570A6458.3050206@comcast.net> <m21t6d7c9t.wl%randy@psg.com> <570A67B4.3010206@comcast.net> <570AB3AF.2050401@gmail.com> <87twj99c6w.fsf@tops.chopps.org> <CAKe6YvMyp-DyeDwpPY6KYmbDbnpgnvVk_cUStnA32wmgDWcz3w@mail.gmail.com> <BBF5DDFE515C3946BC18D733B20DAD233A62AA18@XMB122CNC.rim.net> <20160411104519.GA19092@gsp.org> <3F48466D-390C-4C18-B958-732AE3E46FF1@gmail.com> <20160411223403.GA6743@gsp.org> <CAPt1N1nNo0=JSptQdWRZCFy1v-m6Q8NQy4WVGHtnRJuFZFmMig@mail.gmail.com>
Date: Tue, 12 Apr 2016 10:18:54 +1000
Message-ID: <CAKr6gn1KmNcgNwbPHZWB2aJQAuchz4eB7gxJhV2Dsbc1Z50kDw@mail.gmail.com>
Subject: Re: Concerns about Singapore
From: George Michaelson <ggm@algebras.org>
To: Ted Lemon <mellon@fugue.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/O-O1OO1wuodvELWD_rs9IK_W1SI>
Cc: Rich Kulawiec <rsk@gsp.org>, ietf <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: Tue, 12 Apr 2016 00:18:58 -0000

On Tue, Apr 12, 2016 at 9:54 AM, Ted Lemon <mellon@fugue.com> wrote:
> While I do not think it's true that we can entirely get away without doing
> in-person meetings, I do agree with you that we can do better at doing
> remote meetings.   Perhaps we should let this unfortunate event drive us to
> make the attempt.
>
> If we were to attempt such a thing, how do you think it would work?
>

We'd need tighter chairing. We'd need microphone floor control, and
queues and reservations and we'd adopt meeting formalisms to get the
poll of the room.

Consensus hums would be next to impossible. We'd find pressure to head
to votes. Which of course is a huge no-go for a lot of people.

Van Jacobsen talked to me 15+ years ago about the ways you might have
to police the MBONE and it was interesting to think he was looking
forward then to large attendee, widely distributed, delay-bound
interactions online which is where we're kind-of heading.

The RIR have been doing break-out meetings for a while, and training
the chairs to respect a 30 second lag for feedback from the room is
very hard. Chairs like to judge consensus with eyes in the room, not
on the screen.

-G


From nobody Mon Apr 11 17:25:46 2016
Return-Path: <richard@shockey.us>
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 2BE6112F28D for <ietf@ietfa.amsl.com>; Mon, 11 Apr 2016 17:25:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.002
X-Spam-Level: 
X-Spam-Status: No, score=-2.002 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (768-bit key) header.d=shockey.us
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 uKVSkrkE9Vni for <ietf@ietfa.amsl.com>; Mon, 11 Apr 2016 17:25:43 -0700 (PDT)
Received: from gproxy10-pub.mail.unifiedlayer.com (gproxy10-pub.mail.unifiedlayer.com [69.89.20.226]) by ietfa.amsl.com (Postfix) with SMTP id 432EB12D788 for <ietf@ietf.org>; Mon, 11 Apr 2016 17:25:43 -0700 (PDT)
Received: (qmail 4310 invoked by uid 0); 12 Apr 2016 00:25:42 -0000
Received: from unknown (HELO cmgw3) (10.0.90.84) by gproxy10.mail.unifiedlayer.com with SMTP; 12 Apr 2016 00:25:42 -0000
Received: from box462.bluehost.com ([74.220.219.62]) by cmgw3 with  id hKRb1s0041MNPNq01KRegd; Tue, 12 Apr 2016 01:25:38 -0600
X-Authority-Analysis: v=2.1 cv=Maz/5fPf c=1 sm=1 tr=0 a=jTEj1adHphCQ5SwrTAOQMg==:117 a=jTEj1adHphCQ5SwrTAOQMg==:17 a=L9H7d07YOLsA:10 a=9cW_t1CCXrUA:10 a=s5jvgZ67dGcA:10 a=IkcTkHD0fZMA:10 a=8WrITzYgnNwA:10 a=p-_XEfp0GhYA:10 a=kziv93cY1bsA:10 a=48vgC7mUAAAA:8 a=No5EcEP4AAAA:8 a=jcWNZqZlpGq5pb4eyFUA:9 a=VgDl-esgAnS3UZNp:21 a=YAtlPzYoj1WGeW9U:21 a=QEXdDO2ut3YA:10
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=shockey.us;  s=default; h=Content-transfer-encoding:Content-type:Mime-version:In-Reply-To :References:Message-ID:To:From:Subject:Date; bh=sDazwBdr+BGLvq6cePQIDr+YtRQSydcXEqdiiN25ILA=; b=GEMKrhzLZc0iTSwmQ0v4AKLeA+ z/PrT45IxUG+lZwBU31vR5hwdH7p5kiGhSEt/bwiIyiTVaYDDS1qxmbo0EsBYAdUgW9qvtvWXNr5I dzxb116Dm78WixQtM2mp+qO+0;
Received: from [100.36.35.60] (port=60766 helo=[192.168.1.9]) by box462.bluehost.com with esmtpa (Exim 4.86_2) (envelope-from <richard@shockey.us>) id 1apm9C-0004BI-07; Mon, 11 Apr 2016 18:25:38 -0600
User-Agent: Microsoft-MacOutlook/0.0.0.160212
Date: Mon, 11 Apr 2016 20:25:37 -0400
Subject: Re: thank you
From: Richard Shockey <richard@shockey.us>
To: Randy Bush <randy@psg.com>, IETF Disgust List <ietf@ietf.org>
Message-ID: <9EA38D1A-E7C9-429D-874E-D1072D79F1F4@shockey.us>
Thread-Topic: thank you
References: <m24mb76cns.wl%randy@psg.com>
In-Reply-To: <m24mb76cns.wl%randy@psg.com>
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: quoted-printable
X-Identified-User: {3286:box462.bluehost.com:shockeyu:shockey.us} {sentby:smtp auth 100.36.35.60 authed with richard+shockey.us}
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/em07psB7yaZLAIaumhi3noOmVEQ>
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: Tue, 12 Apr 2016 00:25:45 -0000

Outstanding.. So can we get a Internet Draft on all the best restaurants (S=
TEAK) best wines Malbec etc for those of couldn=E2=80=99t make it? =20


On 4/11/16, 5:47 PM, "ietf on behalf of Randy Bush" <ietf-bounces@ietf.org =
on behalf of randy@psg.com> wrote:

>buenos aires is a beautiful latin american city, hospitable, and with
>great folk.  kudos for such a great meeting go to many people and
>organizations that i will not enumerate for fear of missing one.  thank
>you.
>
>randy
>


From nobody Mon Apr 11 17:27:20 2016
Return-Path: <stephen.farrell@cs.tcd.ie>
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 F2B9112D782 for <ietf@ietfa.amsl.com>; Mon, 11 Apr 2016 17:27:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.297
X-Spam-Level: 
X-Spam-Status: No, score=-5.297 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.996, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cs.tcd.ie
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 QDVV5jd-5Iaz for <ietf@ietfa.amsl.com>; Mon, 11 Apr 2016 17:27:18 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9908312D0BB for <ietf@ietf.org>; Mon, 11 Apr 2016 17:27:17 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id D40B6BE2D; Tue, 12 Apr 2016 01:27:15 +0100 (IST)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IP0ZQkVIrSgO; Tue, 12 Apr 2016 01:27:12 +0100 (IST)
Received: from [10.87.49.100] (unknown [86.46.23.241]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 88DE2BE25; Tue, 12 Apr 2016 01:27:07 +0100 (IST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; s=mail; t=1460420832; bh=3WuJy4ejmRmYsuAxJ3j9lN4VsHtBVsAA/f31Kp8AjBE=; h=Subject:To:References:Cc:From:Date:In-Reply-To:From; b=S6lHYGh2jRxv9uxT3vn1v9nwmdk5EGdgGoTSnrzMPFtcM25hkxs6eJA9s+F0vm5ip Ol2GADFuUfkviMAfsyb85IHK2u2SgtT5YVQ/4XmWbzF4EQeW4gCagnB6EE575fxBOQ F+XRLUjKqoiuWqqs2jPZDeq25zlW0UHWEoPDOr/c=
Subject: Re: 1000 person virtual meeting (Was: Re: Concerns about Singapore)
To: David Farmer <farmer@umn.edu>
References: <m260vp7eke.wl%randy@psg.com> <570A6458.3050206@comcast.net> <m21t6d7c9t.wl%randy@psg.com> <570A67B4.3010206@comcast.net> <570AB3AF.2050401@gmail.com> <87twj99c6w.fsf@tops.chopps.org> <CAKe6YvMyp-DyeDwpPY6KYmbDbnpgnvVk_cUStnA32wmgDWcz3w@mail.gmail.com> <BBF5DDFE515C3946BC18D733B20DAD233A62AA18@XMB122CNC.rim.net> <20160411104519.GA19092@gsp.org> <3F48466D-390C-4C18-B958-732AE3E46FF1@gmail.com> <20160411223403.GA6743@gsp.org> <570C2985.9030701@cs.tcd.ie> <CAN-Dau0JzMNrUFU6baX1=M4FtfF85oEkyr7PmSbt5TBNPMHumQ@mail.gmail.com>
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Openpgp: id=D66EA7906F0B897FB2E97D582F3C8736805F8DA2; url=
Message-ID: <570C40D4.6000001@cs.tcd.ie>
Date: Tue, 12 Apr 2016 01:27:00 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0
MIME-Version: 1.0
In-Reply-To: <CAN-Dau0JzMNrUFU6baX1=M4FtfF85oEkyr7PmSbt5TBNPMHumQ@mail.gmail.com>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha-256; boundary="------------ms030806030304000001040500"
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/jRKGMbK_7KHoM2s33V-iFYIscNM>
Cc: Rich Kulawiec <rsk@gsp.org>, IETF-Discussion 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: Tue, 12 Apr 2016 00:27:20 -0000

This is a cryptographically signed message in MIME format.

--------------ms030806030304000001040500
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable



On 12/04/16 01:07, David Farmer wrote:
> On Mon, Apr 11, 2016 at 5:47 PM, Stephen Farrell <stephen.farrell@cs.tc=
d.ie>
> wrote:
>>
>>
>> But maybe I'm wrong - can you send details of how an approx.
>> 1000 person virtual meeting where everyone could provide real
>> input has been held by anyone? I'm unaware of such but I'd
>> be very interested if that had happened already.
>>
>=20
> It is definitely a challenge, but it has been done, just like a real
> meeting with 1000 people in the room frequently ends up being mostly on=
e
> person or small group talking and then questions being asked by the
> audience, this can be accomplished virtually too.
>=20
> There was a recurring annual event;
>=20
> http://www.megaconference.org/past.html

Interesting! Thanks. Any idea if anyone has posted a summary
of how that went?

Ta,
S.

>=20
> And in Fall of 2001 because of the events of 911, Internet2 canceled it=
s
> Member Meeting in San Antonio and held a Virtual Member Meeting in earl=
y
> October 2001.  I can't find much online regarding it any longer, but it=
 is
> listed on the list of past meetings.
>=20
> http://www.internet2.edu/news-events/events/past-events/past-annual-mem=
ber-meetings/
>=20
> These are a few examples I know of, I'm sure there are others.
>=20


--------------ms030806030304000001040500
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIAGCSqGSIb3DQEHAqCAMIACAQExDzANBglghkgBZQMEAgEFADCABgkqhkiG9w0BBwEAAKCC
CvIwggUIMIID8KADAgECAhBPzaE7pzYviUJyhmHTFBdnMA0GCSqGSIb3DQEBCwUAMHUxCzAJ
BgNVBAYTAklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSkwJwYDVQQLEyBTdGFydENvbSBD
ZXJ0aWZpY2F0aW9uIEF1dGhvcml0eTEjMCEGA1UEAxMaU3RhcnRDb20gQ2xhc3MgMSBDbGll
bnQgQ0EwHhcNMTYwMjA5MDkyODE1WhcNMTcwMjA5MDkyODE1WjBOMSIwIAYDVQQDDBlzdGVw
aGVuLmZhcnJlbGxAY3MudGNkLmllMSgwJgYJKoZIhvcNAQkBFhlzdGVwaGVuLmZhcnJlbGxA
Y3MudGNkLmllMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAtuC0rYze/2JinSra
C9F2RjGdQZjNALLcW9C3WKTwYII3wBslobmHuPEYE5JaGItmzuKnAW619R1rD/kfoNWC19N3
rBZ6UX9Cmb9D9exCwYIwVuSwjrCQWGxgCtNQTrwKzCCpI790GRiMTvxvO7UmzmBrCaBLiZW5
R0fBjK5Yn6hUhAzGBkNbkIEL28cLJqH0yVz7Kl92OlzrQqTPEts5m6cDnNdY/ADfeAX18c1r
dxZqcAxhLotrCqgsVA4ilbQDMMXGTLlB5TP35HeWZuGBU7xu003rLcFLdOkD8xvpJoYZy9Kt
3oABXPS5yqtMK+XCNdqmMn+4mOtLwQSMmPCSiQIDAQABo4IBuTCCAbUwCwYDVR0PBAQDAgSw
MB0GA1UdJQQWMBQGCCsGAQUFBwMCBggrBgEFBQcDBDAJBgNVHRMEAjAAMB0GA1UdDgQWBBQJ
QhvwQ5Fl372Z6xqo6fdn8XejTTAfBgNVHSMEGDAWgBQkgWw5Yb5JD4+3G0YrySi1J0htaDBv
BggrBgEFBQcBAQRjMGEwJAYIKwYBBQUHMAGGGGh0dHA6Ly9vY3NwLnN0YXJ0c3NsLmNvbTA5
BggrBgEFBQcwAoYtaHR0cDovL2FpYS5zdGFydHNzbC5jb20vY2VydHMvc2NhLmNsaWVudDEu
Y3J0MDgGA1UdHwQxMC8wLaAroCmGJ2h0dHA6Ly9jcmwuc3RhcnRzc2wuY29tL3NjYS1jbGll
bnQxLmNybDAkBgNVHREEHTAbgRlzdGVwaGVuLmZhcnJlbGxAY3MudGNkLmllMCMGA1UdEgQc
MBqGGGh0dHA6Ly93d3cuc3RhcnRzc2wuY29tLzBGBgNVHSAEPzA9MDsGCysGAQQBgbU3AQIE
MCwwKgYIKwYBBQUHAgEWHmh0dHA6Ly93d3cuc3RhcnRzc2wuY29tL3BvbGljeTANBgkqhkiG
9w0BAQsFAAOCAQEArzrSv2C8PlBBmGuiGrzm2Wma46/KHtXmZYS0bsd43pM66Pc/MsqPE0HD
C1GzMFfwB6BfkJn8ijNSIhlgj898WzjvnpM/SO8KStjlB8719ig/xKISrOl5mX55XbFlQtX9
U6MrqRgbDIATxhD9IDr+ryvovDzChqgQj7mt2jYr4mdlRjsjod3H1VY6XglRmaaNGZfsCARM
aE/TU5SXIiqauwt5KxNGYAY67QkOBs7O1FkSXpTk7+1MmzJMF4nP8QQ5n8vhVNseF+/Wm7ai
9mtnrkLbaznMsy/ULo/C2yuLUWTbZZbf4EKNmVdme6tUDgYkFjAFOblfA7W1fSPiQGagYzCC
BeIwggPKoAMCAQICEGunin0K14jWUQr5WeTntOEwDQYJKoZIhvcNAQELBQAwfTELMAkGA1UE
BhMCSUwxFjAUBgNVBAoTDVN0YXJ0Q29tIEx0ZC4xKzApBgNVBAsTIlNlY3VyZSBEaWdpdGFs
IENlcnRpZmljYXRlIFNpZ25pbmcxKTAnBgNVBAMTIFN0YXJ0Q29tIENlcnRpZmljYXRpb24g
QXV0aG9yaXR5MB4XDTE1MTIxNjAxMDAwNVoXDTMwMTIxNjAxMDAwNVowdTELMAkGA1UEBhMC
SUwxFjAUBgNVBAoTDVN0YXJ0Q29tIEx0ZC4xKTAnBgNVBAsTIFN0YXJ0Q29tIENlcnRpZmlj
YXRpb24gQXV0aG9yaXR5MSMwIQYDVQQDExpTdGFydENvbSBDbGFzcyAxIENsaWVudCBDQTCC
ASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAL192vfDon2D9luC/dtbX64eG3XAtRmv
mCSsu1d52DXsCR58zJQbCtB2/A5uFqNxWacpXGGtTCRk9dEDBlmixEd8QiLkUfvHpJX/xKnm
VkS6Iye8wUbYzMsDzgnpazlPg19dnSqfhM+Cevdfa89VLnUztRr2cgmCfyO9Otrh7LJDPG+4
D8ZnAqDtVB8MKYJL6QgKyVhhaBc4y3bGWxKyXEtx7QIZZGxPwSkzK3WIN+VKNdkiwTubW5PI
dopmykwvIjLPqbJK7yPwFZYekKE015OsW6FV+s4DIM8UlVS8pkIsoGGJtMuWjLL4tq2hYQuu
N0jhrxK1ljz50hH23gA9cbMCAwEAAaOCAWQwggFgMA4GA1UdDwEB/wQEAwIBBjAdBgNVHSUE
FjAUBggrBgEFBQcDAgYIKwYBBQUHAwQwEgYDVR0TAQH/BAgwBgEB/wIBADAyBgNVHR8EKzAp
MCegJaAjhiFodHRwOi8vY3JsLnN0YXJ0c3NsLmNvbS9zZnNjYS5jcmwwZgYIKwYBBQUHAQEE
WjBYMCQGCCsGAQUFBzABhhhodHRwOi8vb2NzcC5zdGFydHNzbC5jb20wMAYIKwYBBQUHMAKG
JGh0dHA6Ly9haWEuc3RhcnRzc2wuY29tL2NlcnRzL2NhLmNydDAdBgNVHQ4EFgQUJIFsOWG+
SQ+PtxtGK8kotSdIbWgwHwYDVR0jBBgwFoAUTgvvGqRAW6UXaYcwyjRoQ9BBrvIwPwYDVR0g
BDgwNjA0BgRVHSAAMCwwKgYIKwYBBQUHAgEWHmh0dHA6Ly93d3cuc3RhcnRzc2wuY29tL3Bv
bGljeTANBgkqhkiG9w0BAQsFAAOCAgEAi+P3h+wBi4StDwECW5zhIycjBL008HACblIf26HY
0JdOruKbrWDsXUsiI0j/7Crft9S5oxvPiDtVqspBOB/y5uzSns1lZwh7sG96bYBZpcGzGxpF
NjDmQbcM3yl3WFIRS4WhNrsOY14V7y2IrUGsvetsD+bjyOngCIVeC/GmsmtbuLOzJ606tEc9
uRbhjTu/b0x2Fo+/e7UkQvKzNeo7OMhijixaULyINBfCBJb+e29bLafgu6JqjOUJ9eXXj20p
6q/CW+uVrZiSW57+q5an2P2i7hP85jQJcy5j4HzA0rSiF3YPhKGAWUxKPMAVGgcYoXzWydOv
Z3UDsTDTagXpRDIKQLZo02wrlxY6iMFqvlzsemVf1odhQJmi7Eh5TbxI40kDGcBOBHhwnaOu
mZhLP+SWJQnjpLpSlUOj95uf1zo9oz9e0NgIJoz/tdfrBzez76xtDsK0KfUDHt1/q59BvDI7
RX6gVr0fQoCyMczNzCTcRXYHY0tq2J0oT+bsb6sH2b4WVWAiJKnSYaWDjdA70qHX4mq9MIjO
/ZskmSY8wtAk24orAc0vwXgYanqNsBX5Yv4sN4Z9VyrwMdLcusP7HJgRdAGKpkR2I9U4zEsN
JQJewM7S4Jalo1DyPrLpL2nTET8ZrSl5Utp1UeGp/2deoprGevfnxWB+vHNQiu85o6MxggPM
MIIDyAIBATCBiTB1MQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRDb20gTHRkLjEpMCcG
A1UECxMgU3RhcnRDb20gQ2VydGlmaWNhdGlvbiBBdXRob3JpdHkxIzAhBgNVBAMTGlN0YXJ0
Q29tIENsYXNzIDEgQ2xpZW50IENBAhBPzaE7pzYviUJyhmHTFBdnMA0GCWCGSAFlAwQCAQUA
oIICEzAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0xNjA0MTIw
MDI3MDBaMC8GCSqGSIb3DQEJBDEiBCD+74vNsYpNnr5xzpw4F9CBhXiqWnA9rRBqmCt0+Obg
CjBsBgkqhkiG9w0BCQ8xXzBdMAsGCWCGSAFlAwQBKjALBglghkgBZQMEAQIwCgYIKoZIhvcN
AwcwDgYIKoZIhvcNAwICAgCAMA0GCCqGSIb3DQMCAgFAMAcGBSsOAwIHMA0GCCqGSIb3DQMC
AgEoMIGaBgkrBgEEAYI3EAQxgYwwgYkwdTELMAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0
Q29tIEx0ZC4xKTAnBgNVBAsTIFN0YXJ0Q29tIENlcnRpZmljYXRpb24gQXV0aG9yaXR5MSMw
IQYDVQQDExpTdGFydENvbSBDbGFzcyAxIENsaWVudCBDQQIQT82hO6c2L4lCcoZh0xQXZzCB
nAYLKoZIhvcNAQkQAgsxgYyggYkwdTELMAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0Q29t
IEx0ZC4xKTAnBgNVBAsTIFN0YXJ0Q29tIENlcnRpZmljYXRpb24gQXV0aG9yaXR5MSMwIQYD
VQQDExpTdGFydENvbSBDbGFzcyAxIENsaWVudCBDQQIQT82hO6c2L4lCcoZh0xQXZzANBgkq
hkiG9w0BAQEFAASCAQA8rjSYIkrMGEMm+RFmknDlX2w4IywCaK48wzxYHzEozl1diHnnSjvh
qppfFcuz67/rFPQGsnDaYI/jmHiyE7Gva4tdevC2Hark71LOEgwW+1viHSdLLdHf5oieCi/2
U0F7uw8qEm5aXhP0+aUWDudH9FN/kXytvnQY0/R7RpQbzs17Bzxg3pDxFPNmHzEu3O6xmbUo
FqEBfTd9qkmDYKfuCZUOwhgt0XkGwVY5Zd3eCftgFAHz2aJXyB2yzWGSoQuVJm4oKVWIPYxF
MmO0ET6dqL7k/ItkQzVB8sbAN2+idPwFwkEK3a1SLNb2Gs17VzYpE8Sp06uuTb7P/3HKCq3I
AAAAAAAA
--------------ms030806030304000001040500--


From nobody Mon Apr 11 17:30:33 2016
Return-Path: <marka@isc.org>
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 DD45D12F60E for <ietf@ietfa.amsl.com>; Mon, 11 Apr 2016 17:30:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.897
X-Spam-Level: 
X-Spam-Status: No, score=-7.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.996, SPF_PASS=-0.001] 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 ydXYHlRlSQv4 for <ietf@ietfa.amsl.com>; Mon, 11 Apr 2016 17:30:31 -0700 (PDT)
Received: from mx.ams1.isc.org (mx.ams1.isc.org [IPv6:2001:500:60::65]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C1C4612D7C1 for <ietf@ietf.org>; Mon, 11 Apr 2016 17:30:31 -0700 (PDT)
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx.ams1.isc.org (Postfix) with ESMTPS id 1F19C1FCAE5; Tue, 12 Apr 2016 00:30:29 +0000 (UTC)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTPS id E8AEA160073; Tue, 12 Apr 2016 00:30:27 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id D4248160072; Tue, 12 Apr 2016 00:30:27 +0000 (UTC)
Received: from zmx1.isc.org ([127.0.0.1]) by localhost (zmx1.isc.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id Ai1WpLlXmhn3; Tue, 12 Apr 2016 00:30:27 +0000 (UTC)
Received: from rock.dv.isc.org (c122-106-161-187.carlnfd1.nsw.optusnet.com.au [122.106.161.187]) by zmx1.isc.org (Postfix) with ESMTPSA id 92043160053; Tue, 12 Apr 2016 00:30:27 +0000 (UTC)
Received: from rock.dv.isc.org (localhost [IPv6:::1]) by rock.dv.isc.org (Postfix) with ESMTP id 1739C461BB18; Tue, 12 Apr 2016 10:30:25 +1000 (EST)
To: Ted Lemon <mellon@fugue.com>
From: Mark Andrews <marka@isc.org>
References: <m260vp7eke.wl%randy@psg.com> <570A6458.3050206@comcast.net> <m21t6d7c9t.wl%randy@psg.com> <570A67B4.3010206@comcast.net> <570AB3AF.2050401@gmail.com> <87twj99c6w.fsf@tops.chopps.org> <CAKe6YvMyp-DyeDwpPY6KYmbDbnpgnvVk_cUStnA32wmgDWcz3w@mail.gmail.com> <BBF5DDFE515C3946BC18D733B20DAD233A62AA18@XMB122CNC.rim.net> <20160411104519.GA19092@gsp.org> <3F48466D-390C-4C18-B958-732AE3E46FF1@gmail.com> <20160411223403.GA6743@gsp.org> <570C2985.9030701@cs.tcd.ie> <CAN-Dau0JzMNrUFU6baX1=M4FtfF85oEkyr7PmSbt5TBNPMHumQ@mail.gmail.com> <CAPt1N1kKMDvZt6K_QxRt4SVbzw6FOjkXH2fFbntxWn28i=NLfA@mail.gmail.com>
Subject: Re: 1000 person virtual meeting (Was: Re: Concerns about Singapore)
In-reply-to: Your message of "Mon, 11 Apr 2016 20:13:07 -0400." <CAPt1N1kKMDvZt6K_QxRt4SVbzw6FOjkXH2fFbntxWn28i=NLfA@mail.gmail.com>
Date: Tue, 12 Apr 2016 10:30:25 +1000
Message-Id: <20160412003025.1739C461BB18@rock.dv.isc.org>
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/Xoiu7ZoCemEdewUoY27S-oJmhyE>
Cc: IETF-Discussion 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: Tue, 12 Apr 2016 00:30:33 -0000

I also have no doubt one could do a 1000 person remote meeting.

That being said, I've tried to do remote attendence at meetings
both where there is a small timezone offset and a large timezone
offset.  The small timezone offset "works" but in no way replaces
face to face meetings.  The large timezone offset only works if you
have 1 or 2 working groups to want to attend.

Face to face forces attendees to be mostly in sync with respect to
the timezone.  BA was a 10 hour shift for me but it was do able.

-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org


From nobody Mon Apr 11 17:34:36 2016
Return-Path: <mfidelman@meetinghouse.net>
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 767ED12D973 for <ietf@ietfa.amsl.com>; Mon, 11 Apr 2016 17:34:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] 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 McA-aO6ls2L9 for <ietf@ietfa.amsl.com>; Mon, 11 Apr 2016 17:34:34 -0700 (PDT)
Received: from server1.neighborhoods.net (server1.neighborhoods.net [207.154.13.48]) by ietfa.amsl.com (Postfix) with ESMTP id 3DC1712D926 for <ietf@ietf.org>; Mon, 11 Apr 2016 17:34:34 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by server1.neighborhoods.net (Postfix) with ESMTP id B5C55CC065 for <ietf@ietf.org>; Mon, 11 Apr 2016 20:34:33 -0400 (EDT)
X-Virus-Scanned: by amavisd-new-2.6.2 (20081215) (Debian) at neighborhoods.net
Received: from server1.neighborhoods.net ([127.0.0.1]) by localhost (server1.neighborhoods.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id FODAGgr7vp3o for <ietf@ietf.org>; Mon, 11 Apr 2016 20:34:31 -0400 (EDT)
Received: from Miless-MBP.fios-router.home (pool-108-26-191-201.bstnma.fios.verizon.net [108.26.191.201]) by server1.neighborhoods.net (Postfix) with ESMTPSA id CF283CC04B for <ietf@ietf.org>; Mon, 11 Apr 2016 20:34:31 -0400 (EDT)
Subject: Re: 1000 person virtual meeting (Was: Re: Concerns about Singapore)
To: ietf@ietf.org
References: <m260vp7eke.wl%randy@psg.com> <570A6458.3050206@comcast.net> <m21t6d7c9t.wl%randy@psg.com> <570A67B4.3010206@comcast.net> <570AB3AF.2050401@gmail.com> <87twj99c6w.fsf@tops.chopps.org> <CAKe6YvMyp-DyeDwpPY6KYmbDbnpgnvVk_cUStnA32wmgDWcz3w@mail.gmail.com> <BBF5DDFE515C3946BC18D733B20DAD233A62AA18@XMB122CNC.rim.net> <20160411104519.GA19092@gsp.org> <3F48466D-390C-4C18-B958-732AE3E46FF1@gmail.com> <20160411223403.GA6743@gsp.org> <570C2985.9030701@cs.tcd.ie> <CAN-Dau0JzMNrUFU6baX1=M4FtfF85oEkyr7PmSbt5TBNPMHumQ@mail.gmail.com> <CAPt1N1kKMDvZt6K_QxRt4SVbzw6FOjkXH2fFbntxWn28i=NLfA@mail.gmail.com> <20160412003025.1739C461BB18@rock.dv.isc.org>
From: Miles Fidelman <mfidelman@meetinghouse.net>
Message-ID: <570C4296.5010302@meetinghouse.net>
Date: Mon, 11 Apr 2016 20:34:30 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:38.0) Gecko/20100101 Thunderbird/38.7.2
MIME-Version: 1.0
In-Reply-To: <20160412003025.1739C461BB18@rock.dv.isc.org>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/B_dWcj0QTIWobSK8dsdTxnXQjv8>
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: Tue, 12 Apr 2016 00:34:35 -0000

On 4/11/16 8:30 PM, Mark Andrews wrote:
> I also have no doubt one could do a 1000 person remote meeting.
>
> That being said, I've tried to do remote attendence at meetings
> both where there is a small timezone offset and a large timezone
> offset.  The small timezone offset "works" but in no way replaces
> face to face meetings.  The large timezone offset only works if you
> have 1 or 2 working groups to want to attend.
>
> Face to face forces attendees to be mostly in sync with respect to
> the timezone.  BA was a 10 hour shift for me but it was do able.
>

Well, keep in mind that a 1000-person in-person meeting is pretty hard 
as well.  Sure, it works as a plenary session, but in-person working 
meetings also break down at pretty low numbers.

Now, if one thinks about multiple, simultaneous, remote meetings - of 
10-50 people each - things start to sound a more feasible.

Just a thought,

Miles Fidelman



-- 
In theory, there is no difference between theory and practice.
In practice, there is.  .... Yogi Berra


From nobody Mon Apr 11 17:44:09 2016
Return-Path: <jared@puck.nether.net>
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 BF19F12D803 for <ietf@ietfa.amsl.com>; Mon, 11 Apr 2016 17:44:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.198
X-Spam-Level: 
X-Spam-Status: No, score=-5.198 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.996, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] 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 6cXnSD6dkbNh for <ietf@ietfa.amsl.com>; Mon, 11 Apr 2016 17:44:06 -0700 (PDT)
Received: from puck.nether.net (puck.nether.net [204.42.254.5]) by ietfa.amsl.com (Postfix) with ESMTP id 6102912D76A for <ietf@ietf.org>; Mon, 11 Apr 2016 17:44:06 -0700 (PDT)
Received: from [IPv6:2601:401:4:3000:1d88:ad36:3fc4:763] (unknown [IPv6:2601:401:4:3000:1d88:ad36:3fc4:763]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by puck.nether.net (Postfix) with ESMTPSA id 18F365406A7; Mon, 11 Apr 2016 20:44:04 -0400 (EDT)
Subject: Re: Meetecho was Re: Concerns about Singapore
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Content-Type: text/plain; charset=us-ascii
From: Jared Mauch <jared@puck.nether.net>
In-Reply-To: <860206232.1954211.1460419714948.JavaMail.yahoo@mail.yahoo.com>
Date: Mon, 11 Apr 2016 20:44:03 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <F2FE2CAF-A8E5-4956-8A9F-2BBD704154A8@puck.nether.net>
References: <20160411223403.GA6743@gsp.org> <860206232.1954211.1460419714948.JavaMail.yahoo@mail.yahoo.com>
To: lloyd.wood@yahoo.co.uk
X-Mailer: Apple Mail (2.3124)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/fttHYDNM5z1tcv-Jd9Z-J1CpXS4>
Cc: Rich Kulawiec <rsk@gsp.org>, "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: Tue, 12 Apr 2016 00:44:07 -0000

> On Apr 11, 2016, at 8:08 PM, <lloyd.wood@yahoo.co.uk> =
<lloyd.wood@yahoo.co.uk> wrote:
>=20
> try listening to the first twenty minutes of this.
> then tell me if IETF WG meetings with remote presentation
> via Meetecho are anything other than a complete waste
> of time.
>=20

The NTPWG had a very successful experience, including remote presenters, =
and remote people going back and forth with their interaction. =20

I would say your experience is atypical, and certainly not the desired =
outcome.

- Jared=


From nobody Mon Apr 11 17:45:22 2016
Return-Path: <stephen.farrell@cs.tcd.ie>
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 F2F1F12D824 for <ietf@ietfa.amsl.com>; Mon, 11 Apr 2016 17:45:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.297
X-Spam-Level: 
X-Spam-Status: No, score=-5.297 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.996, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cs.tcd.ie
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 pDZ3ql6Rc4T8 for <ietf@ietfa.amsl.com>; Mon, 11 Apr 2016 17:45:18 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 786E812D81D for <ietf@ietf.org>; Mon, 11 Apr 2016 17:45:18 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 282E3BE2D; Tue, 12 Apr 2016 01:45:17 +0100 (IST)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id V92tTVl4NwuE; Tue, 12 Apr 2016 01:45:15 +0100 (IST)
Received: from [10.87.49.100] (unknown [86.46.23.241]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 32B73BE25; Tue, 12 Apr 2016 01:45:15 +0100 (IST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; s=mail; t=1460421915; bh=/i9bosQiPZFinGzCM2ncNju7Co3b8pfqN00tIBZFXu4=; h=Subject:To:References:From:Date:In-Reply-To:From; b=i5eKC7NuoOUuv3v2LDDlUFyhdswpxR+b5zExLkv2mTXsZlVr6GuBmTkcHOMM3ESO5 SClLOqqOyTlnlvBkbStBAPVqZrVtC3vQpleoT/eiGRtLjIUq9l9yi5+i3fW4/Qamoy PoUPUAWoGVpnsLiO3PuH8/VqGrK2V7KsZJfrv0Tc=
Subject: Re: 1000 person virtual meeting (Was: Re: Concerns about Singapore)
To: Miles Fidelman <mfidelman@meetinghouse.net>, ietf@ietf.org
References: <m260vp7eke.wl%randy@psg.com> <570A6458.3050206@comcast.net> <m21t6d7c9t.wl%randy@psg.com> <570A67B4.3010206@comcast.net> <570AB3AF.2050401@gmail.com> <87twj99c6w.fsf@tops.chopps.org> <CAKe6YvMyp-DyeDwpPY6KYmbDbnpgnvVk_cUStnA32wmgDWcz3w@mail.gmail.com> <BBF5DDFE515C3946BC18D733B20DAD233A62AA18@XMB122CNC.rim.net> <20160411104519.GA19092@gsp.org> <3F48466D-390C-4C18-B958-732AE3E46FF1@gmail.com> <20160411223403.GA6743@gsp.org> <570C2985.9030701@cs.tcd.ie> <CAN-Dau0JzMNrUFU6baX1=M4FtfF85oEkyr7PmSbt5TBNPMHumQ@mail.gmail.com> <CAPt1N1kKMDvZt6K_QxRt4SVbzw6FOjkXH2fFbntxWn28i=NLfA@mail.gmail.com> <20160412003025.1739C461BB18@rock.dv.isc.org> <570C4296.5010302@meetinghouse.net>
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Openpgp: id=D66EA7906F0B897FB2E97D582F3C8736805F8DA2; url=
Message-ID: <570C451A.6050600@cs.tcd.ie>
Date: Tue, 12 Apr 2016 01:45:14 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0
MIME-Version: 1.0
In-Reply-To: <570C4296.5010302@meetinghouse.net>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha-256; boundary="------------ms070401050009020800010800"
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/8nhQLBYNzoiTfNf1H883wcGKMi4>
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: Tue, 12 Apr 2016 00:45:20 -0000

This is a cryptographically signed message in MIME format.

--------------ms070401050009020800010800
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable



On 12/04/16 01:34, Miles Fidelman wrote:
>=20
> On 4/11/16 8:30 PM, Mark Andrews wrote:
>> I also have no doubt one could do a 1000 person remote meeting.
>>
>> That being said, I've tried to do remote attendence at meetings
>> both where there is a small timezone offset and a large timezone
>> offset.  The small timezone offset "works" but in no way replaces
>> face to face meetings.  The large timezone offset only works if you
>> have 1 or 2 working groups to want to attend.
>>
>> Face to face forces attendees to be mostly in sync with respect to
>> the timezone.  BA was a 10 hour shift for me but it was do able.
>>
>=20
> Well, keep in mind that a 1000-person in-person meeting is pretty hard
> as well.  Sure, it works as a plenary session, but in-person working
> meetings also break down at pretty low numbers.
>=20
> Now, if one thinks about multiple, simultaneous, remote meetings - of
> 10-50 people each - things start to sound a more feasible.

"Sound more feasible"? Perhaps. Add TZ's and remote input issues
that we face with today's technology and that may no longer be
convincing.

I've been a bit involved in the session planning for the last dozen
or so IETF meetings - I reckon adding a TZ constraint for each/many
participants would have broken all of those. There are also typically
8 sessions in parallel at IETF meetings, the largest of which often
involves between one and two hundred folks in one session so things
do not in fact break down into 10-50 people sub things, at least today.

Add all that up and I think we're "sounding" utterly impractical.
(That said, I do still need to check out the David Farmer's response
in this thread.)


S.



>=20
> Just a thought,
>=20
> Miles Fidelman
>=20
>=20
>=20


--------------ms070401050009020800010800
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIAGCSqGSIb3DQEHAqCAMIACAQExDzANBglghkgBZQMEAgEFADCABgkqhkiG9w0BBwEAAKCC
CvIwggUIMIID8KADAgECAhBPzaE7pzYviUJyhmHTFBdnMA0GCSqGSIb3DQEBCwUAMHUxCzAJ
BgNVBAYTAklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSkwJwYDVQQLEyBTdGFydENvbSBD
ZXJ0aWZpY2F0aW9uIEF1dGhvcml0eTEjMCEGA1UEAxMaU3RhcnRDb20gQ2xhc3MgMSBDbGll
bnQgQ0EwHhcNMTYwMjA5MDkyODE1WhcNMTcwMjA5MDkyODE1WjBOMSIwIAYDVQQDDBlzdGVw
aGVuLmZhcnJlbGxAY3MudGNkLmllMSgwJgYJKoZIhvcNAQkBFhlzdGVwaGVuLmZhcnJlbGxA
Y3MudGNkLmllMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAtuC0rYze/2JinSra
C9F2RjGdQZjNALLcW9C3WKTwYII3wBslobmHuPEYE5JaGItmzuKnAW619R1rD/kfoNWC19N3
rBZ6UX9Cmb9D9exCwYIwVuSwjrCQWGxgCtNQTrwKzCCpI790GRiMTvxvO7UmzmBrCaBLiZW5
R0fBjK5Yn6hUhAzGBkNbkIEL28cLJqH0yVz7Kl92OlzrQqTPEts5m6cDnNdY/ADfeAX18c1r
dxZqcAxhLotrCqgsVA4ilbQDMMXGTLlB5TP35HeWZuGBU7xu003rLcFLdOkD8xvpJoYZy9Kt
3oABXPS5yqtMK+XCNdqmMn+4mOtLwQSMmPCSiQIDAQABo4IBuTCCAbUwCwYDVR0PBAQDAgSw
MB0GA1UdJQQWMBQGCCsGAQUFBwMCBggrBgEFBQcDBDAJBgNVHRMEAjAAMB0GA1UdDgQWBBQJ
QhvwQ5Fl372Z6xqo6fdn8XejTTAfBgNVHSMEGDAWgBQkgWw5Yb5JD4+3G0YrySi1J0htaDBv
BggrBgEFBQcBAQRjMGEwJAYIKwYBBQUHMAGGGGh0dHA6Ly9vY3NwLnN0YXJ0c3NsLmNvbTA5
BggrBgEFBQcwAoYtaHR0cDovL2FpYS5zdGFydHNzbC5jb20vY2VydHMvc2NhLmNsaWVudDEu
Y3J0MDgGA1UdHwQxMC8wLaAroCmGJ2h0dHA6Ly9jcmwuc3RhcnRzc2wuY29tL3NjYS1jbGll
bnQxLmNybDAkBgNVHREEHTAbgRlzdGVwaGVuLmZhcnJlbGxAY3MudGNkLmllMCMGA1UdEgQc
MBqGGGh0dHA6Ly93d3cuc3RhcnRzc2wuY29tLzBGBgNVHSAEPzA9MDsGCysGAQQBgbU3AQIE
MCwwKgYIKwYBBQUHAgEWHmh0dHA6Ly93d3cuc3RhcnRzc2wuY29tL3BvbGljeTANBgkqhkiG
9w0BAQsFAAOCAQEArzrSv2C8PlBBmGuiGrzm2Wma46/KHtXmZYS0bsd43pM66Pc/MsqPE0HD
C1GzMFfwB6BfkJn8ijNSIhlgj898WzjvnpM/SO8KStjlB8719ig/xKISrOl5mX55XbFlQtX9
U6MrqRgbDIATxhD9IDr+ryvovDzChqgQj7mt2jYr4mdlRjsjod3H1VY6XglRmaaNGZfsCARM
aE/TU5SXIiqauwt5KxNGYAY67QkOBs7O1FkSXpTk7+1MmzJMF4nP8QQ5n8vhVNseF+/Wm7ai
9mtnrkLbaznMsy/ULo/C2yuLUWTbZZbf4EKNmVdme6tUDgYkFjAFOblfA7W1fSPiQGagYzCC
BeIwggPKoAMCAQICEGunin0K14jWUQr5WeTntOEwDQYJKoZIhvcNAQELBQAwfTELMAkGA1UE
BhMCSUwxFjAUBgNVBAoTDVN0YXJ0Q29tIEx0ZC4xKzApBgNVBAsTIlNlY3VyZSBEaWdpdGFs
IENlcnRpZmljYXRlIFNpZ25pbmcxKTAnBgNVBAMTIFN0YXJ0Q29tIENlcnRpZmljYXRpb24g
QXV0aG9yaXR5MB4XDTE1MTIxNjAxMDAwNVoXDTMwMTIxNjAxMDAwNVowdTELMAkGA1UEBhMC
SUwxFjAUBgNVBAoTDVN0YXJ0Q29tIEx0ZC4xKTAnBgNVBAsTIFN0YXJ0Q29tIENlcnRpZmlj
YXRpb24gQXV0aG9yaXR5MSMwIQYDVQQDExpTdGFydENvbSBDbGFzcyAxIENsaWVudCBDQTCC
ASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAL192vfDon2D9luC/dtbX64eG3XAtRmv
mCSsu1d52DXsCR58zJQbCtB2/A5uFqNxWacpXGGtTCRk9dEDBlmixEd8QiLkUfvHpJX/xKnm
VkS6Iye8wUbYzMsDzgnpazlPg19dnSqfhM+Cevdfa89VLnUztRr2cgmCfyO9Otrh7LJDPG+4
D8ZnAqDtVB8MKYJL6QgKyVhhaBc4y3bGWxKyXEtx7QIZZGxPwSkzK3WIN+VKNdkiwTubW5PI
dopmykwvIjLPqbJK7yPwFZYekKE015OsW6FV+s4DIM8UlVS8pkIsoGGJtMuWjLL4tq2hYQuu
N0jhrxK1ljz50hH23gA9cbMCAwEAAaOCAWQwggFgMA4GA1UdDwEB/wQEAwIBBjAdBgNVHSUE
FjAUBggrBgEFBQcDAgYIKwYBBQUHAwQwEgYDVR0TAQH/BAgwBgEB/wIBADAyBgNVHR8EKzAp
MCegJaAjhiFodHRwOi8vY3JsLnN0YXJ0c3NsLmNvbS9zZnNjYS5jcmwwZgYIKwYBBQUHAQEE
WjBYMCQGCCsGAQUFBzABhhhodHRwOi8vb2NzcC5zdGFydHNzbC5jb20wMAYIKwYBBQUHMAKG
JGh0dHA6Ly9haWEuc3RhcnRzc2wuY29tL2NlcnRzL2NhLmNydDAdBgNVHQ4EFgQUJIFsOWG+
SQ+PtxtGK8kotSdIbWgwHwYDVR0jBBgwFoAUTgvvGqRAW6UXaYcwyjRoQ9BBrvIwPwYDVR0g
BDgwNjA0BgRVHSAAMCwwKgYIKwYBBQUHAgEWHmh0dHA6Ly93d3cuc3RhcnRzc2wuY29tL3Bv
bGljeTANBgkqhkiG9w0BAQsFAAOCAgEAi+P3h+wBi4StDwECW5zhIycjBL008HACblIf26HY
0JdOruKbrWDsXUsiI0j/7Crft9S5oxvPiDtVqspBOB/y5uzSns1lZwh7sG96bYBZpcGzGxpF
NjDmQbcM3yl3WFIRS4WhNrsOY14V7y2IrUGsvetsD+bjyOngCIVeC/GmsmtbuLOzJ606tEc9
uRbhjTu/b0x2Fo+/e7UkQvKzNeo7OMhijixaULyINBfCBJb+e29bLafgu6JqjOUJ9eXXj20p
6q/CW+uVrZiSW57+q5an2P2i7hP85jQJcy5j4HzA0rSiF3YPhKGAWUxKPMAVGgcYoXzWydOv
Z3UDsTDTagXpRDIKQLZo02wrlxY6iMFqvlzsemVf1odhQJmi7Eh5TbxI40kDGcBOBHhwnaOu
mZhLP+SWJQnjpLpSlUOj95uf1zo9oz9e0NgIJoz/tdfrBzez76xtDsK0KfUDHt1/q59BvDI7
RX6gVr0fQoCyMczNzCTcRXYHY0tq2J0oT+bsb6sH2b4WVWAiJKnSYaWDjdA70qHX4mq9MIjO
/ZskmSY8wtAk24orAc0vwXgYanqNsBX5Yv4sN4Z9VyrwMdLcusP7HJgRdAGKpkR2I9U4zEsN
JQJewM7S4Jalo1DyPrLpL2nTET8ZrSl5Utp1UeGp/2deoprGevfnxWB+vHNQiu85o6MxggPM
MIIDyAIBATCBiTB1MQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRDb20gTHRkLjEpMCcG
A1UECxMgU3RhcnRDb20gQ2VydGlmaWNhdGlvbiBBdXRob3JpdHkxIzAhBgNVBAMTGlN0YXJ0
Q29tIENsYXNzIDEgQ2xpZW50IENBAhBPzaE7pzYviUJyhmHTFBdnMA0GCWCGSAFlAwQCAQUA
oIICEzAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0xNjA0MTIw
MDQ1MTRaMC8GCSqGSIb3DQEJBDEiBCBYASxXcXj7FOlkHOhoYaeZbmlecQD/sJrVpNJb2HoJ
JTBsBgkqhkiG9w0BCQ8xXzBdMAsGCWCGSAFlAwQBKjALBglghkgBZQMEAQIwCgYIKoZIhvcN
AwcwDgYIKoZIhvcNAwICAgCAMA0GCCqGSIb3DQMCAgFAMAcGBSsOAwIHMA0GCCqGSIb3DQMC
AgEoMIGaBgkrBgEEAYI3EAQxgYwwgYkwdTELMAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0
Q29tIEx0ZC4xKTAnBgNVBAsTIFN0YXJ0Q29tIENlcnRpZmljYXRpb24gQXV0aG9yaXR5MSMw
IQYDVQQDExpTdGFydENvbSBDbGFzcyAxIENsaWVudCBDQQIQT82hO6c2L4lCcoZh0xQXZzCB
nAYLKoZIhvcNAQkQAgsxgYyggYkwdTELMAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0Q29t
IEx0ZC4xKTAnBgNVBAsTIFN0YXJ0Q29tIENlcnRpZmljYXRpb24gQXV0aG9yaXR5MSMwIQYD
VQQDExpTdGFydENvbSBDbGFzcyAxIENsaWVudCBDQQIQT82hO6c2L4lCcoZh0xQXZzANBgkq
hkiG9w0BAQEFAASCAQBdzRPmO0Utny3DWHXiLFnvO/wE9M17TDj40dtuPi8yoCvcBwButnaJ
UAYN8yGv9rrF7wARkC2eAQzqQOgBO+6wG13GDmkrDMX8lYdQR1wOzJ5PfKecMVysI0l5wiGA
jrGSZmI0L30KfgmpcNloBLlFpBZ4BtKunMvSnWZcG4JWdt6h4wnzof+gliMJcCxx4DtPm11J
840gZyh99vk3dFuPY1hQeQGJfSARtAK1w/Bw0/SMI6p8YiRZ4dVwDL1EePbjHJxrFUL5sYxK
IdpSv+kDKh8BBxQQH4RBxbqfbkEsdZPxk1VOLCBUJITK5BpToJ+luF/VoTKGGNSzFagudoWj
AAAAAAAA
--------------ms070401050009020800010800--


From nobody Mon Apr 11 17:51:01 2016
Return-Path: <mellon@fugue.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 3D5BE12D899 for <ietf@ietfa.amsl.com>; Mon, 11 Apr 2016 17:51:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.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 F6tful1yy12S for <ietf@ietfa.amsl.com>; Mon, 11 Apr 2016 17:50:58 -0700 (PDT)
Received: from mail-lf0-x22f.google.com (mail-lf0-x22f.google.com [IPv6:2a00:1450:4010:c07::22f]) (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 394AA12D895 for <ietf@ietf.org>; Mon, 11 Apr 2016 17:50:58 -0700 (PDT)
Received: by mail-lf0-x22f.google.com with SMTP id c126so3639352lfb.2 for <ietf@ietf.org>; Mon, 11 Apr 2016 17:50:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=H5U4f6akbU8dnvmP3nG/wj4NkUqmnxbozz+tnZ8p5uY=; b=VJRY71erDw67sACnGqn2nOKMmZ2fyos0NUqpah1s3GsYkqRdB7AHUgkrCaPouLYKbf ikXVN+SOGpWc46alG8jOb1UuE3+Zge7Hyl3/Jg3tz3ScqkyrxDsypaRHzOsRLtDPmN70 kYRbMpgKrYSAzGhvcgiZGEnWjF6siI2tfPL8e4fRMnNs+BoT+iIkwert1+xMowfvCDB/ IwxZPM2Jlp0MfRqHovZtElR74f5H2Wbp1xD21Yi2zbuhsQ8ID2PSAIZ1xyS7CetAU97b VTOFeQWlBeEuyU+RRXydd+mTiomlgCVS96Qa4Pb99vIcMFtjZvcneCv4afxp4vjXx/L4 HUBg==
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=H5U4f6akbU8dnvmP3nG/wj4NkUqmnxbozz+tnZ8p5uY=; b=LGguJ9STr9ArlrBo3azul9vvvcCw90tVZecQoOUI9E6r2jjDqByJQLe5/uu4RxEUxj fRFsVg7xg9W+QrHAmOcgP6tAWJ7/v5Ui1q1+7i3UwfKDUQe1uT7budZW4fjVCAUTJTVj sVl15lWjc7l+iv8zpMRe98jazqH51jiqiyK2kvbG88oLkvrwMtE2BUX7SvH9y8fHYVA4 sHvGOMFW4w25s49mnmfKXYc0+bH1cQsQA1OBqPVntTOTXWsA9VEYBo+9cyTlXTdWckeF OoIkVi1zqrOS8QB1hwHgLc/+0E2fTo2rig+ekS5ZC1S/qFcsGfr5BnrbLXVzen46uGxZ KlTg==
X-Gm-Message-State: AOPr4FXFl/QRDdA7HkTlHr/o8OIh+daHR9ghbR/CZ/l+He6MRiOZeoaV7epLH28GjTGnioUKi5lcFQU8ltA8qw==
X-Received: by 10.25.148.208 with SMTP id w199mr161358lfd.124.1460422256421; Mon, 11 Apr 2016 17:50:56 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.25.40.136 with HTTP; Mon, 11 Apr 2016 17:50:16 -0700 (PDT)
X-Originating-IP: [71.233.41.235]
In-Reply-To: <CAKr6gn1KmNcgNwbPHZWB2aJQAuchz4eB7gxJhV2Dsbc1Z50kDw@mail.gmail.com>
References: <m260vp7eke.wl%randy@psg.com> <570A6458.3050206@comcast.net> <m21t6d7c9t.wl%randy@psg.com> <570A67B4.3010206@comcast.net> <570AB3AF.2050401@gmail.com> <87twj99c6w.fsf@tops.chopps.org> <CAKe6YvMyp-DyeDwpPY6KYmbDbnpgnvVk_cUStnA32wmgDWcz3w@mail.gmail.com> <BBF5DDFE515C3946BC18D733B20DAD233A62AA18@XMB122CNC.rim.net> <20160411104519.GA19092@gsp.org> <3F48466D-390C-4C18-B958-732AE3E46FF1@gmail.com> <20160411223403.GA6743@gsp.org> <CAPt1N1nNo0=JSptQdWRZCFy1v-m6Q8NQy4WVGHtnRJuFZFmMig@mail.gmail.com> <CAKr6gn1KmNcgNwbPHZWB2aJQAuchz4eB7gxJhV2Dsbc1Z50kDw@mail.gmail.com>
From: Ted Lemon <mellon@fugue.com>
Date: Mon, 11 Apr 2016 20:50:16 -0400
Message-ID: <CAPt1N1mWjg_-525avYJ4PnSECYQrtpVFJCXPfH=PryJ8q0vy4Q@mail.gmail.com>
Subject: Re: Concerns about Singapore
To: George Michaelson <ggm@algebras.org>
Content-Type: multipart/alternative; boundary=001a1140234cd1049305303f0d24
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/Ui35FBJFm7kD5VvSV7Z6L0kLa9E>
Cc: Rich Kulawiec <rsk@gsp.org>, ietf <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: Tue, 12 Apr 2016 00:51:00 -0000

--001a1140234cd1049305303f0d24
Content-Type: text/plain; charset=UTF-8

The only thing you mentioned that can't be done with existing conferencing
software is hums, and I'm sure we could figure out a way to make that
work.  It's not rocket science.   Chairs who judge consensus by looking at
the room aren't following IETF process--consensus is judged on the mailing
list.  Hums are useful for figuring out why we _don't_ have consensus, and
for _getting_ to consensus, but if you were to judge consensus by hums or a
show of hands, then you'd be taking a vote, wouldn't you?

On Mon, Apr 11, 2016 at 8:18 PM, George Michaelson <ggm@algebras.org> wrote:

> On Tue, Apr 12, 2016 at 9:54 AM, Ted Lemon <mellon@fugue.com> wrote:
> > While I do not think it's true that we can entirely get away without
> doing
> > in-person meetings, I do agree with you that we can do better at doing
> > remote meetings.   Perhaps we should let this unfortunate event drive us
> to
> > make the attempt.
> >
> > If we were to attempt such a thing, how do you think it would work?
> >
>
> We'd need tighter chairing. We'd need microphone floor control, and
> queues and reservations and we'd adopt meeting formalisms to get the
> poll of the room.
>
> Consensus hums would be next to impossible. We'd find pressure to head
> to votes. Which of course is a huge no-go for a lot of people.
>
> Van Jacobsen talked to me 15+ years ago about the ways you might have
> to police the MBONE and it was interesting to think he was looking
> forward then to large attendee, widely distributed, delay-bound
> interactions online which is where we're kind-of heading.
>
> The RIR have been doing break-out meetings for a while, and training
> the chairs to respect a 30 second lag for feedback from the room is
> very hard. Chairs like to judge consensus with eyes in the room, not
> on the screen.
>
> -G
>

--001a1140234cd1049305303f0d24
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">The only thing you mentioned that can&#39;t be done with e=
xisting conferencing software is hums, and I&#39;m sure we could figure out=
 a way to make that work.=C2=A0 It&#39;s not rocket science. =C2=A0 Chairs =
who judge consensus by looking at the room aren&#39;t following IETF proces=
s--consensus is judged on the mailing list.=C2=A0 Hums are useful for figur=
ing out why we _don&#39;t_ have consensus, and for _getting_ to consensus, =
but if you were to judge consensus by hums or a show of hands, then you&#39=
;d be taking a vote, wouldn&#39;t you?</div><div class=3D"gmail_extra"><br>=
<div class=3D"gmail_quote">On Mon, Apr 11, 2016 at 8:18 PM, George Michaels=
on <span dir=3D"ltr">&lt;<a href=3D"mailto:ggm@algebras.org" target=3D"_bla=
nk">ggm@algebras.org</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_qu=
ote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex=
"><span class=3D"">On Tue, Apr 12, 2016 at 9:54 AM, Ted Lemon &lt;<a href=
=3D"mailto:mellon@fugue.com">mellon@fugue.com</a>&gt; wrote:<br>
&gt; While I do not think it&#39;s true that we can entirely get away witho=
ut doing<br>
&gt; in-person meetings, I do agree with you that we can do better at doing=
<br>
&gt; remote meetings.=C2=A0 =C2=A0Perhaps we should let this unfortunate ev=
ent drive us to<br>
&gt; make the attempt.<br>
&gt;<br>
&gt; If we were to attempt such a thing, how do you think it would work?<br=
>
&gt;<br>
<br>
</span>We&#39;d need tighter chairing. We&#39;d need microphone floor contr=
ol, and<br>
queues and reservations and we&#39;d adopt meeting formalisms to get the<br=
>
poll of the room.<br>
<br>
Consensus hums would be next to impossible. We&#39;d find pressure to head<=
br>
to votes. Which of course is a huge no-go for a lot of people.<br>
<br>
Van Jacobsen talked to me 15+ years ago about the ways you might have<br>
to police the MBONE and it was interesting to think he was looking<br>
forward then to large attendee, widely distributed, delay-bound<br>
interactions online which is where we&#39;re kind-of heading.<br>
<br>
The RIR have been doing break-out meetings for a while, and training<br>
the chairs to respect a 30 second lag for feedback from the room is<br>
very hard. Chairs like to judge consensus with eyes in the room, not<br>
on the screen.<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
-G<br>
</font></span></blockquote></div><br></div>

--001a1140234cd1049305303f0d24--


From nobody Mon Apr 11 19:28:52 2016
Return-Path: <fgont@si6networks.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 65BCF12DE56 for <ietf@ietfa.amsl.com>; Mon, 11 Apr 2016 19:28:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] 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 N6klW5SE3S4K for <ietf@ietfa.amsl.com>; Mon, 11 Apr 2016 19:28:49 -0700 (PDT)
Received: from fgont.go6lab.si (fgont.go6lab.si [91.239.96.14]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 726E412DE4E for <ietf@ietf.org>; Mon, 11 Apr 2016 19:28:49 -0700 (PDT)
Received: from [192.168.3.107] (192-174-17-190.fibertel.com.ar [190.17.174.192]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id 5898E80645; Tue, 12 Apr 2016 04:28:43 +0200 (CEST)
Subject: Re: thank you
To: Randy Bush <randy@psg.com>, IETF Disgust List <ietf@ietf.org>
References: <m24mb76cns.wl%randy@psg.com>
From: Fernando Gont <fgont@si6networks.com>
X-Enigmail-Draft-Status: N1110
Message-ID: <570C5CDB.1020102@si6networks.com>
Date: Mon, 11 Apr 2016 23:26:35 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0
MIME-Version: 1.0
In-Reply-To: <m24mb76cns.wl%randy@psg.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/Fy4FggIEJdNDjDNr2FEtIQSGKEI>
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: Tue, 12 Apr 2016 02:28:51 -0000

I'm no one to assign credit, nor do I know all the people involved. But
simply wanted to ack one that I'm aware was running here and there to
make it happen: Christian O'Flaherty.

Cheers,
Fernando




On 04/11/2016 06:47 PM, Randy Bush wrote:
> buenos aires is a beautiful latin american city, hospitable, and with
> great folk.  kudos for such a great meeting go to many people and
> organizations that i will not enumerate for fear of missing one.  thank
> you.
> 
> randy
> 
> 


-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492





From nobody Mon Apr 11 21:28:24 2016
Return-Path: <harald@alvestrand.no>
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 D53E612E1E9 for <ietf@ietfa.amsl.com>; Mon, 11 Apr 2016 21:28:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.896
X-Spam-Level: 
X-Spam-Status: No, score=-2.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.996] 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 OZK5UtpNbksw for <ietf@ietfa.amsl.com>; Mon, 11 Apr 2016 21:28:20 -0700 (PDT)
Received: from mork.alvestrand.no (mork.alvestrand.no [IPv6:2001:700:1:2::117]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0C9AF12E1E4 for <ietf@ietf.org>; Mon, 11 Apr 2016 21:28:20 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mork.alvestrand.no (Postfix) with ESMTP id 1ABDE7C7CCF for <ietf@ietf.org>; Tue, 12 Apr 2016 06:28:18 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at alvestrand.no
Received: from mork.alvestrand.no ([127.0.0.1]) by localhost (mork.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TFtr2W1aOVZs for <ietf@ietf.org>; Tue, 12 Apr 2016 06:28:16 +0200 (CEST)
Received: from [IPv6:2001:470:de0a:1:34fd:aec1:692d:e316] (unknown [IPv6:2001:470:de0a:1:34fd:aec1:692d:e316]) by mork.alvestrand.no (Postfix) with ESMTPSA id 905B67C7CCE for <ietf@ietf.org>; Tue, 12 Apr 2016 06:28:16 +0200 (CEST)
Subject: Re: Concerns about Singapore
To: ietf@ietf.org
References: <0D914666-C3D4-4CCE-AD5E-4E5B34EA1A73@piuha.net> <20160407182936.GA21340@pfrc.org> <CAB75xn780nNDjGa_Cc222J20-+1CCHt09Xp8KHzaK=n0xx51pg@mail.gmail.com> <5706B100.9040509@mnt.se> <CAB75xn6fmj84ROUtG5eUB3GerHx83hrEr3w5vSADY_g=BRg5FA@mail.gmail.com> <5706BA40.3060005@mnt.se> <alpine.DEB.2.02.1604072157240.31096@uplift.swm.pp.se> <A9B63A6D-3102-482F-8FFC-2E57A5FD8336@nic.cz> <16925.1460122349@obiwan.sandelman.ca> <m27fg77zst.wl%randy@psg.com> <57097077.7040703@comcast.net> <m2fuuu75ls.wl%randy@psg.com> <87wpo5a8im.fsf@tops.chopps.org> <m260vp7eke.wl%randy@psg.com> <570A6458.3050206@comcast.net> <m21t6d7c9t.wl%randy@psg.com> <570A67B4.3010206@comcast.net> <570AB3AF.2050401@gmail.com> <87twj99c6w.fsf@tops.chopps.org> <CAKe6YvMyp-DyeDwpPY6KYmbDbnpgnvVk_cUStnA32wmgDWcz3w@mail.gmail.com> <BBF5DDFE515C3946BC18D733B20DAD233A62AA18@XMB122CNC.rim.net>
From: Harald Alvestrand <harald@alvestrand.no>
X-Enigmail-Draft-Status: N1110
Message-ID: <570C7960.50803@alvestrand.no>
Date: Tue, 12 Apr 2016 06:28:16 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0
MIME-Version: 1.0
In-Reply-To: <BBF5DDFE515C3946BC18D733B20DAD233A62AA18@XMB122CNC.rim.net>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/2gXBlYEUp_m5H0HVxtFr8RdOGh4>
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: Tue, 12 Apr 2016 04:28:23 -0000

The IETF is not a value-neutral organization.

Since we're citing the Mission Statement RFC here, it also contains:

>    The Internet isn't value-neutral, and neither is the IETF.  We want
>    the Internet to be useful for communities that share our commitment
>    to openness and fairness.  We embrace technical concepts such as
>    decentralized control, edge-user empowerment and sharing of
>    resources, because those concepts resonate with the core values of
>    the IETF community.  These concepts have little to do with the
>    technology that's possible, and much to do with the technology that
>    we choose to create.

That said - after doing my amateur research on the whole Singapore
thing, I'm willing to live with whatever resolution of the issue the
IAOC comes up with. It's not an open-and-shut "stay away" thing; I
regard the first IETF to be held inside the Great Firewall as a more
clearly problematic decision - but, in retrospect, agree with it.

My unhappiness with the IAOC's handling (pre-plenary) is mainly that
they were surprised that this concern needs considering.




Den 11. april 2016 10:05, skrev Andrew Allen:
> This is what I mean by slippery slope - once we go down this path it never ends - in a global community of well over 1000 active people at least one person is likely to have a problem with some aspect of most of the countries governments, policies, cultures or actions, etc.
> 
> We could be left with the only possible venue being a cruise ship sailing in international waters - but then someone will probably object because the ship is registered in Panama or Liberia!
> 
> The focus should be on choosing a location for the meeting that is open for all to attend and where it is reasonably safe to attend and meets the needs of a meeting for a large number of people and represents the regional balance of the membership. 
> 
> The mission of the IETF is to make the Internet work better by producing high quality, relevant technical documents that influence the way people design, use, and manage the Internet.
> 
> The IETF is not an organization that's mission is to be an advocate for global social, environmental or political change. The selection of a meeting location should be for the purposes of advancing the IETF's mission. I think some of the concerns raised about Singapore need to be addressed in terms of the practical impact and risk to the attendance of some in the IETF community but we shouldnâ€™t start down the road of choosing or not choosing meeting locations based on an evaluation of a countries laws, culture and policies and whether those are acceptable to all or most of the community.
> 
> Debates over whether a location is politically or morally acceptable will only distract from the mission of the IETF and likely divide the community rather than help in making progress towards forming consensus on the future development of the internet.
> 
> Andrew
> 
> -----Original Message-----
> From: ietf [mailto:ietf-bounces@ietf.org] On Behalf Of Vinayak Hegde
> Sent: Sunday, April 10, 2016 10:24 PM
> To: chopps@chopps.org
> Cc: IETF discussion list <ietf@ietf.org>
> Subject: Re: Concerns about Singapore
> 
> On Mon, Apr 11, 2016 at 6:46 AM,  <chopps@chopps.org> wrote:
>> It's certainly relevant to me, b/c I don't personally think that IETF 
>> meetings should be held in oppressive and censoring countries. I don't 
>> know how to articulate this well -- others are better at it -- but I 
>> certainly would like to skip any meetings that I feel violate IETFs 
>> value of openness so that I can at least vote with my feet and my 
>> dollars.
> 
> Well how does this work with Internet's (and IETF's) mission of inclusiveness. Applying the same scale of "oppressiveness", I am sure large parts of the world think the same about the US/UK which has waged wars in Iraq, Afghanistan, Vietnam, Syria, Argentina (our latest venue) and elsewhere.
> 
> The IETF doesn't seem to have a problem having meetings in these countries. I hope the majority of participants on this list realise that they are viewing the world through a western prism.
> 
> The notion of punishing the general populace for the mistakes of their elected and unelected govt. seems wrong to me. Many times, the general populace of the country is fighting their govt. through the Internet. eg. Turkey.
> 
> -- Vinayak
> 


From nobody Tue Apr 12 01:04:12 2016
Return-Path: <leifj@mnt.se>
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 8146D12E89A for <ietf@ietfa.amsl.com>; Tue, 12 Apr 2016 01:04:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mnt-se.20150623.gappssmtp.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 gz_oHYF1NQMP for <ietf@ietfa.amsl.com>; Tue, 12 Apr 2016 01:04:09 -0700 (PDT)
Received: from mail-lf0-x236.google.com (mail-lf0-x236.google.com [IPv6:2a00:1450:4010:c07::236]) (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 DC91E12E89E for <ietf@ietf.org>; Tue, 12 Apr 2016 01:04:08 -0700 (PDT)
Received: by mail-lf0-x236.google.com with SMTP id g184so13871457lfb.3 for <ietf@ietf.org>; Tue, 12 Apr 2016 01:04:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mnt-se.20150623.gappssmtp.com; s=20150623; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding; bh=4NHYU2MKiLHYNaQGODQtU9OT89tI8DhH3OBHhuAbqsM=; b=CLWg4Etx3MrTJ4HoBaI6oq6EX7x0Y71+ttuVex+PGTe0ksnPUhYRMjFQx0cWcoiAPS Pfqpyx4ast7O2G4mNv1eUGRzXebCtSWHyMSfRhWfsmqmxB6NedjYmiCJjkohJneFJ824 1LgWtSEt0LnpWxkhLFeF2j9VpVEUy5NdlIT2w+ARGLwryIeToYtnnEG+su2LYZakK8y0 ThxB516+q/q0BEdqD9JauufLYG9ofx1F6lCpe3j0gDYAtWdb3QFy9RRYPZxgCORrRJ1L hbXR7Ck324zLnDzaOtdJK5lsuW9L/gTU2XPhRb5Pj3fCQxl/UDOlawCeapdo/Buaz1lo YsOA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=4NHYU2MKiLHYNaQGODQtU9OT89tI8DhH3OBHhuAbqsM=; b=PAsfWb0i9TSW22SOfEgHjk7/3oBm/XJ1RcRY9tLduo3sxKrdyI6zCCen2Y+9JqO566 y3yx1ZPiF0zt2UdepDksxV+lie8VqQHEwlTihy/fjcKhbY0Nb08LKASbygxtWAVdVcR9 TIlmsnfh/BQ/c1b7ENB3QVm7IFkbyXz9piK51FEvnekiroeqhnpZk/qIgOY+XSjOqZ6Q CJAxsnwh36PiwQ35DUMIZ7fIiyRF4TzFPuvK2hTqm7TGurMe81Wa9yiIVnwGfiMzcwfG MrbrotaAzH8Bgt4T9qvR7I72qZDmbixptqr/Se1gj7XbXZ5UgxCEh6cOJI5kHq7F5XxD L7ng==
X-Gm-Message-State: AOPr4FUUk9MqDUnZsfIPERCPfOqUNy1+55SbzMIpOL974hdWzXbmixb4dcdgIiIyQOLCiA==
X-Received: by 10.25.85.138 with SMTP id j132mr665716lfb.123.1460448246889; Tue, 12 Apr 2016 01:04:06 -0700 (PDT)
Received: from [194.47.40.185] ([194.47.40.185]) by smtp.googlemail.com with ESMTPSA id c5sm5055490lfc.44.2016.04.12.01.04.05 for <ietf@ietf.org> (version=TLSv1/SSLv3 cipher=OTHER); Tue, 12 Apr 2016 01:04:05 -0700 (PDT)
Subject: Re: thank you
To: ietf@ietf.org
References: <m24mb76cns.wl%randy@psg.com>
From: Leif Johansson <leifj@mnt.se>
Message-ID: <570CABF4.6090906@mnt.se>
Date: Tue, 12 Apr 2016 10:04:04 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0
MIME-Version: 1.0
In-Reply-To: <m24mb76cns.wl%randy@psg.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/FZSH9olqndc9JIyDQw7DsdCF7OE>
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: Tue, 12 Apr 2016 08:04:10 -0000

On 2016-04-11 23:47, Randy Bush wrote:
> buenos aires is a beautiful latin american city, hospitable, and with
> great folk.  kudos for such a great meeting go to many people and
> organizations that i will not enumerate for fear of missing one.  thank
> you.
>
> randy
>

+= great steaks


From nobody Tue Apr 12 02:29:27 2016
Return-Path: <john-ietf@jck.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 DDCF212EB9C for <ietf@ietfa.amsl.com>; Tue, 12 Apr 2016 02:29:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.896
X-Spam-Level: 
X-Spam-Status: No, score=-2.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.996] 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 eyQKctFTh1Zc for <ietf@ietfa.amsl.com>; Tue, 12 Apr 2016 02:29:23 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 292AB12EB83 for <ietf@ietf.org>; Tue, 12 Apr 2016 02:29:23 -0700 (PDT)
Received: from [198.252.137.10] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1apudF-000Imo-60; Tue, 12 Apr 2016 05:29:13 -0400
Date: Tue, 12 Apr 2016 05:29:08 -0400
From: John C Klensin <john-ietf@jck.com>
To: Alissa Cooper <alissa@cooperw.in>, Jari Arkko <jari.arkko@piuha.net>
Subject: Re: Last Call on draft-bradner-rfc3979bis-08.txt ("Intellectual Property Rights in IETF Technology")
Message-ID: <65AD4D713F340D761513414F@JcK-HP8200.jck.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/wqavH5BulZTa_uEng04lSzVRsHo>
Cc: IETF <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: Tue, 12 Apr 2016 09:29:25 -0000

--On Monday, April 11, 2016 15:33 -0700 Alissa Cooper
<alissa@cooperw.in> wrote:

>> Personally, I'd love to see the draft talk about AD
>> participation just like it talks about other people's
>> participation. If I really haven't participated in WG X,
>> well, I haven't, even if my co-AD owns the group :-) And if
>> I did participate, well, I should declare the IPR that I know
>> of :-)
> 
> +1
> This is what did not make sense to me about the draft. 

Alissa,

I'm fine with the above, but I think there is a delicate line
involved.  Let me try to explain it this way.  As a random
member of the community, whether I'm participating in a WG, or
even actively monitoring it, is fairly clear.  If, for example,
I'm attending its meetings (f2f or remotely) or signed up for
its mailing list, the community should be able to assume that
I'm watching the work in that WG and should be required to make
relevant IPR disclosures even if I don't actually say anything
or otherwise generate Contributions.    If I do none of those
things but occasionally check on mailing list archives, read
Last Call announcements, I think the community needs to take my
word for it if I claim to be "not participating".

I think things are a little different (but only a little) if
there is management involvement.  If you are the AD responsible
for a WG, then I think the community gets to assume that you
know what its work items are, have approved document editors,
and have at least read the abstracts of the various drafts,
i.e., that you are participating.  If you are some other AD in
the same area, well, areas differ a lot and over time.  In some
cases, ADs shadow each other as a mutual backup arrangements and
I'd expect to be able to treat all ADs in the same area as
"participating" in all WGs.  In others, WGs get divided up among
ADs, after which the area might as well be as many separate ones
as there are ADs.  At IETF evaluation time, any ADs who record a
position other that "abstain" on a spec, or to engage in any
IESG discussion about it, has presumably studied that spec
closely enough to incur disclosure obligations if IPR is known
to them because making a decision to adopt (or not) is clearly
"participation".  The same issue might exist with Co-chairs of a
WG with many tasks.  I'd normally assume that each one is
familiar with and participating in every work item, but it isn't
hard to imagine situations in which work might be split up along
clear boundaries with one co-chair getting involved in the work
of the other only at around the time of Last Call if then.

All of that said, I think that trying to create a collection of
very specific rules or definitions to cover each case and
variations on it is almost certain to cause more harm than good.
I think the intent of the rules -- that anyone who has
contributed to a spec or put themselves in a position in which
they influence an IETF decision to adopt (or not) or publish (or
not) has disclosure obligations (whether direct or third-party
as discussed in the I-D). My expectation is that WG Chairs and,
to even a greater extent, ADs, will be sensitive to the intent
of the rules.  To do otherwise would be a breach of the trust
the community placed in them and that would be at least as
serious, perhaps more, than breaching the letter of the IPR
rules.   

If we need rule changes in that area, they probably lie in
making recalls more feasible rather than more case analysis in
the IPR document(s).   If the latter documents need anything
extra, perhaps it is an explicit statement to the effect of
"Because of the trust the community places in them and the
consensus-determination and decision authority associated with
their positions, IETF Leadership including WG Chairs and Nomcom
appointees are expected to be especially diligent in observing
the intent of these rules".  

best.
     john




From nobody Tue Apr 12 04:03:05 2016
Return-Path: <rsk@gsp.org>
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 984DC12EACA for <ietf@ietfa.amsl.com>; Tue, 12 Apr 2016 04:03:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] 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 18ejyKbt3otJ for <ietf@ietfa.amsl.com>; Tue, 12 Apr 2016 04:03:02 -0700 (PDT)
Received: from taos.firemountain.net (taos.firemountain.net [207.114.3.54]) (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 3D45D12EB2B for <ietf@ietf.org>; Tue, 12 Apr 2016 04:03:01 -0700 (PDT)
Received: from gsp.org (localhost [127.0.0.1]) by taos.firemountain.net (8.15.1/8.14.9) with SMTP id u3CB2xGS015168 for <ietf@ietf.org>; Tue, 12 Apr 2016 07:03:00 -0400 (EDT)
Date: Tue, 12 Apr 2016 07:02:59 -0400
From: Rich Kulawiec <rsk@gsp.org>
To: ietf <ietf@ietf.org>
Subject: Re: Concerns about Singapore
Message-ID: <20160412110259.GA7267@gsp.org>
References: <m21t6d7c9t.wl%randy@psg.com> <570A67B4.3010206@comcast.net> <570AB3AF.2050401@gmail.com> <87twj99c6w.fsf@tops.chopps.org> <CAKe6YvMyp-DyeDwpPY6KYmbDbnpgnvVk_cUStnA32wmgDWcz3w@mail.gmail.com> <BBF5DDFE515C3946BC18D733B20DAD233A62AA18@XMB122CNC.rim.net> <20160411104519.GA19092@gsp.org> <3F48466D-390C-4C18-B958-732AE3E46FF1@gmail.com> <20160411223403.GA6743@gsp.org> <CAPt1N1nNo0=JSptQdWRZCFy1v-m6Q8NQy4WVGHtnRJuFZFmMig@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAPt1N1nNo0=JSptQdWRZCFy1v-m6Q8NQy4WVGHtnRJuFZFmMig@mail.gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/yPGnsVLuTYeePpvvaZpqPnUzoSE>
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: Tue, 12 Apr 2016 11:03:03 -0000

On Mon, Apr 11, 2016 at 07:54:25PM -0400, Ted Lemon wrote:
> If we were to attempt such a thing, how do you think it would work?

Let me preface this by saying that I think attempts to completely
mimic the current in-person meeting experience as it exists probably
won't work.  They might: but they probably won't.  But then again,
I don't think that's entirely necessary: processes and procedures
change (compare boarding a steamship in 1930 with an aircraft in 2005)
and evolve in order to work with technology.

So if I were to envision this, things I'd want to experiment with
would include:

- passive view-only, listen-only read-only access to anyone, anonymously.
(That is: no registration required.)

- levels of read-write access, perhaps (roughly speaking) distinguished
as text, audio, and video.  Participants could select based on their
available bandwidth and on the level they're comfortable with.  I think
it's reasonable to require registration for write access.

- a channel for presentation content only. Again, this is an option for
those with limited bandwidth or limited time.

- ability to delay/time-shift.

- perhaps restructuring long sessions into smaller time slots.  If people
have all travelled to the same place, then it makes sense to get a lot
done in a short time, and so a four hour session (for example) makes
sense.  But if people are in disparate locations, then maybe four one-hour
sessions make more sense.  This also better accomodate people who have
trouble carving out four hours in the middle of their day.  Or night.

- integrated storage of sessions, so that someone can watch, listen,
read, and absorb the entire experience.  Useful for someone half a
planet away who won't be (or can't be) awake for real-time participation.

- translations and/or text captioning and/or some kind of assistance
for non-native speakers and the hearing impaired.

- emphasis on the inclusion of participants who can't make it to meetings
today, either because of time, money, politics, distance, family, job, etc.

Over and above all of this: a willingness to experiment and to have
some of those expirements fail -- which they will.

---rsk


From nobody Tue Apr 12 04:08:43 2016
Return-Path: <rsk@gsp.org>
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 6708B12D15E for <ietf@ietfa.amsl.com>; Tue, 12 Apr 2016 04:08:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.5
X-Spam-Level: 
X-Spam-Status: No, score=-2.5 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, URIBL_BLACK=1.7] 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 aw0GMUat0Ewp for <ietf@ietfa.amsl.com>; Tue, 12 Apr 2016 04:08:41 -0700 (PDT)
Received: from taos.firemountain.net (taos.firemountain.net [207.114.3.54]) (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 8D42712DD28 for <ietf@ietf.org>; Tue, 12 Apr 2016 04:08:41 -0700 (PDT)
Received: from gsp.org (localhost [127.0.0.1]) by taos.firemountain.net (8.15.1/8.14.9) with SMTP id u3CB8dYo004830 for <ietf@ietf.org>; Tue, 12 Apr 2016 07:08:40 -0400 (EDT)
Date: Tue, 12 Apr 2016 07:08:39 -0400
From: Rich Kulawiec <rsk@gsp.org>
To: ietf@ietf.org
Subject: Re: Remote only meetings? [Re: Concerns about Singapore]
Message-ID: <20160412110839.GA20488@gsp.org>
References: <m21t6d7c9t.wl%randy@psg.com> <570A67B4.3010206@comcast.net> <570AB3AF.2050401@gmail.com> <87twj99c6w.fsf@tops.chopps.org> <CAKe6YvMyp-DyeDwpPY6KYmbDbnpgnvVk_cUStnA32wmgDWcz3w@mail.gmail.com> <BBF5DDFE515C3946BC18D733B20DAD233A62AA18@XMB122CNC.rim.net> <20160411104519.GA19092@gsp.org> <3F48466D-390C-4C18-B958-732AE3E46FF1@gmail.com> <20160411223403.GA6743@gsp.org> <87twj7eon7.fsf@tops.chopps.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <87twj7eon7.fsf@tops.chopps.org>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/VmtDBr7hxJB-cUuf0cEvkI4piWk>
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: Tue, 12 Apr 2016 11:08:42 -0000

On Mon, Apr 11, 2016 at 07:01:16PM -0400, chopps@chopps.org wrote:
> Why would we want to get rid of such a rich source of inspiration and
> invention?

Because it works exclusively for the elite, privileged few.  (And no
doubt: it works quite well.)  But it's the antithesis of inclusion
and diversity -- and I think those qualities are increasingly necessary.

---rsk


From nobody Tue Apr 12 04:16:12 2016
Return-Path: <tjc@ecs.soton.ac.uk>
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 B28D912E428 for <ietf@ietfa.amsl.com>; Tue, 12 Apr 2016 04:16:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.517
X-Spam-Level: 
X-Spam-Status: No, score=-4.517 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.996, SPF_NEUTRAL=0.779] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ecs.soton.ac.uk
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 kPO0DQ5zMFB5 for <ietf@ietfa.amsl.com>; Tue, 12 Apr 2016 04:16:09 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [IPv6:2001:630:d0:f102::25e]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 77CE412E042 for <ietf@ietf.org>; Tue, 12 Apr 2016 04:16:09 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (localhost [127.0.0.1]) by falcon.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id u3CBG41F008281 for <ietf@ietf.org>; Tue, 12 Apr 2016 12:16:04 +0100
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk u3CBG41F008281
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=201304; t=1460459764; bh=oAR8/SIIkRkT48sOneSAFfc9k/Q=; h=Mime-Version:Subject:From:In-Reply-To:Date:References:To; b=WSn+YsAIiB7g35KLIn6sYkOk2UdT4kRwiwr7QfcBL0vb7RNEc+UZ52yFaNTxiZa5a 1Mh66ihHafv/uBsZBKv349kKY3SOTNjTp8AUxsf/aCLPKjtEZAZeCWAgj2+7OTh3a7 8Ej/pK8MJU/zivu736YV6vI3SqLmkdcl0MurIDl8=
Received: from gander.ecs.soton.ac.uk (gander.ecs.soton.ac.uk [2001:630:d0:f102::25d]) by falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [2001:630:d0:f102::25e]) envelope-from <tjc@ecs.soton.ac.uk> with ESMTP (valid=N/A) id s3BCG432192060108D ret-id none; Tue, 12 Apr 2016 12:16:04 +0100
Received: from 20010a88d51011.ipv6.customer.clara.net (20010a88d51011.ipv6.customer.clara.net [IPv6:2001:a88:d510:1101:a93e:5914:9e35:ffe3] (may be forged)) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id u3CBG0XJ020672 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Tue, 12 Apr 2016 12:16:01 +0100
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 9.2 \(3112\))
Subject: Re: Concerns about Singapore
From: Tim Chown <tjc@ecs.soton.ac.uk>
In-Reply-To: <CAPt1N1mWjg_-525avYJ4PnSECYQrtpVFJCXPfH=PryJ8q0vy4Q@mail.gmail.com>
Date: Tue, 12 Apr 2016 12:15:59 +0100
Content-Transfer-Encoding: quoted-printable
Message-ID: <EMEW3|d5cb2cb80712b3716e1ab4e2a54c9430s3BCG403tjc|ecs.soton.ac.uk|A684A3C4-7161-49F5-919E-A5F948A3F316@ecs.soton.ac.uk>
References: <m260vp7eke.wl%randy@psg.com> <570A6458.3050206@comcast.net> <m21t6d7c9t.wl%randy@psg.com> <570A67B4.3010206@comcast.net> <570AB3AF.2050401@gmail.com> <87twj99c6w.fsf@tops.chopps.org> <CAKe6YvMyp-DyeDwpPY6KYmbDbnpgnvVk_cUStnA32wmgDWcz3w@mail.gmail.com> <BBF5DDFE515C3946BC18D733B20DAD233A62AA18@XMB122CNC.rim.net> <20160411104519.GA19092@gsp.org> <3F48466D-390C-4C18-B958-732AE3E46FF1@gmail.com> <20160411223403.GA6743@gsp.org> <CAPt1N1nNo0=JSptQdWRZCFy1v-m6Q8NQy4WVGHtnRJuFZFmMig@mail.gmail.com> <CAKr6gn1KmNcgNwbPHZWB2aJQAuchz4eB7gxJhV2Dsbc1Z50kDw@mail.gmail.com> <CAPt1N1mWjg_-525avYJ4PnSECYQrtpVFJCXPfH=PryJ8q0vy4Q@mail.gmail.com> <A684A3C4-7161-49F5-919E-A5F948A3F316@ecs.soton.ac.uk>
To: ietf <ietf@ietf.org>
X-Mailer: Apple Mail (2.3112)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=s3BCG4321920601000; tid=s3BCG432192060108D; client=relay,ipv6; mail=; rcpt=; nrcpt=1:0; fails=0
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: u3CBG41F008281
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/Wt261RB6DfsMHG-l1Pd7nMWCOL8>
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: Tue, 12 Apr 2016 11:16:10 -0000

> On 12 Apr 2016, at 01:50, Ted Lemon <mellon@fugue.com> wrote:
>=20
> The only thing you mentioned that can't be done with existing =
conferencing software is hums, and I'm sure we could figure out a way to =
make that work.  It's not rocket science.   Chairs who judge consensus =
by looking at the room aren't following IETF process--consensus is =
judged on the mailing list.  Hums are useful for figuring out why we =
_don't_ have consensus, and for _getting_ to consensus, but if you were =
to judge consensus by hums or a show of hands, then you'd be taking a =
vote, wouldn't you?

Meetecho has a =E2=80=98hum=E2=80=99 button, which throws =E2=80=98hmmmmmm=
=E2=80=99 into the jabber room for the WG. I did see it used, once.=20

Tim=


From nobody Tue Apr 12 04:20:55 2016
Return-Path: <bertietf@bwijnen.net>
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 1278E12D80A for <ietf@ietfa.amsl.com>; Tue, 12 Apr 2016 04:20:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.62
X-Spam-Level: 
X-Spam-Status: No, score=-2.62 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01] 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 v1YAx6Zh_5fG for <ietf@ietfa.amsl.com>; Tue, 12 Apr 2016 04:20:51 -0700 (PDT)
Received: from lb2-smtp-cloud6.xs4all.net (lb2-smtp-cloud6.xs4all.net [194.109.24.28]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3DE0912DF90 for <ietf@ietf.org>; Tue, 12 Apr 2016 04:20:51 -0700 (PDT)
Received: from Macintosh-2.fritz.box ([83.163.239.181]) by smtp-cloud6.xs4all.net with ESMTP id hPLn1s0063vXPcr01PLozo; Tue, 12 Apr 2016 13:20:49 +0200
Subject: Re: thank you
To: ietf@ietf.org
References: <m24mb76cns.wl%randy@psg.com> <570CABF4.6090906@mnt.se>
From: "Bert Wijnen (IETF)" <bertietf@bwijnen.net>
Message-ID: <570CDA10.4010407@bwijnen.net>
Date: Tue, 12 Apr 2016 13:20:48 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:38.0) Gecko/20100101 Thunderbird/38.7.1
MIME-Version: 1.0
In-Reply-To: <570CABF4.6090906@mnt.se>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/AaAjqK_DPlqSiX8FHxW7nG29AH4>
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: Tue, 12 Apr 2016 11:20:54 -0000

Well said Randy

Bert

On 12/04/16 10:04, Leif Johansson wrote:
> On 2016-04-11 23:47, Randy Bush wrote:
>> buenos aires is a beautiful latin american city, hospitable, and with
>> great folk.  kudos for such a great meeting go to many people and
>> organizations that i will not enumerate for fear of missing one.  thank
>> you.
>>
>> randy
>>
>
> += great steaks
>
>


From nobody Tue Apr 12 04:43:32 2016
Return-Path: <tjc@ecs.soton.ac.uk>
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 60ACF12EB69 for <ietf@ietfa.amsl.com>; Tue, 12 Apr 2016 04:43:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.517
X-Spam-Level: 
X-Spam-Status: No, score=-4.517 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.996, SPF_NEUTRAL=0.779] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ecs.soton.ac.uk
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 AfkeRi48hAKp for <ietf@ietfa.amsl.com>; Tue, 12 Apr 2016 04:43:29 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [IPv6:2001:630:d0:f102::25e]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C53C012EB2D for <ietf@ietf.org>; Tue, 12 Apr 2016 04:43:28 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (localhost [127.0.0.1]) by falcon.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id u3CBhQSg014369 for <ietf@ietf.org>; Tue, 12 Apr 2016 12:43:26 +0100
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk u3CBhQSg014369
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=201304; t=1460461406; bh=VUay0I+sy3Hwyr4HYqwJQSv+6sE=; h=Mime-Version:Subject:From:In-Reply-To:Date:References:To; b=zhjjid5Yp8ymEBcM6UVuTxC6AmAL0jmPBRxjp5LqdbeADWC30dxzdrGj3syxZIh2f O1m20+wIduU2qAk8eg5VbUz2J9VnQ9g4LtvBIMWbvRCVuU0KL8VslH+rxQY2ToO+se SZqyB4hhdNTUA99Fo9/G3fBkbrMqh+aZ6+1o1wDw=
Received: from gander.ecs.soton.ac.uk (gander.ecs.soton.ac.uk [2001:630:d0:f102::25d]) by falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [2001:630:d0:f102::25e]) envelope-from <tjc@ecs.soton.ac.uk> with ESMTP (valid=N/A) id s3BChQ3219206321GJ ret-id none; Tue, 12 Apr 2016 12:43:26 +0100
Received: from 20010a88d51011.ipv6.customer.clara.net (20010a88d51011.ipv6.customer.clara.net [IPv6:2001:a88:d510:1101:a93e:5914:9e35:ffe3] (may be forged)) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id u3CBhNA9029840 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Tue, 12 Apr 2016 12:43:23 +0100
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 9.2 \(3112\))
Subject: Re: Concerns about Singapore
From: Tim Chown <tjc@ecs.soton.ac.uk>
In-Reply-To: <CAPt1N1nNo0=JSptQdWRZCFy1v-m6Q8NQy4WVGHtnRJuFZFmMig@mail.gmail.com>
Date: Tue, 12 Apr 2016 12:43:22 +0100
Content-Transfer-Encoding: quoted-printable
Message-ID: <EMEW3|9aaa87920b361e2e71efe9c7005e927cs3BChQ03tjc|ecs.soton.ac.uk|DDFE7AA1-4C07-4944-AECA-EA361A3A0B71@ecs.soton.ac.uk>
References: <m260vp7eke.wl%randy@psg.com> <570A6458.3050206@comcast.net> <m21t6d7c9t.wl%randy@psg.com> <570A67B4.3010206@comcast.net> <570AB3AF.2050401@gmail.com> <87twj99c6w.fsf@tops.chopps.org> <CAKe6YvMyp-DyeDwpPY6KYmbDbnpgnvVk_cUStnA32wmgDWcz3w@mail.gmail.com> <BBF5DDFE515C3946BC18D733B20DAD233A62AA18@XMB122CNC.rim.net> <20160411104519.GA19092@gsp.org> <3F48466D-390C-4C18-B958-732AE3E46FF1@gmail.com> <20160411223403.GA6743@gsp.org> <CAPt1N1nNo0=JSptQdWRZCFy1v-m6Q8NQy4WVGHtnRJuFZFmMig@mail.gmail.com> <DDFE7AA1-4C07-4944-AECA-EA361A3A0B71@ecs.soton.ac.uk>
To: ietf <ietf@ietf.org>
X-Mailer: Apple Mail (2.3112)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=s3BChQ321920632100; tid=s3BChQ3219206321GJ; client=relay,ipv6; mail=; rcpt=; nrcpt=1:0; fails=0
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: u3CBhQSg014369
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/q9LMYCxfy3SQUl4D86WB2y0WFmw>
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: Tue, 12 Apr 2016 11:43:30 -0000

Hi,

To minimise the chances of a =E2=80=98Singapore=E2=80=99 happening again =
it would seem prudent to

a) re-use previous successful meeting venues for the bulk of our =
meetings (say, every 5 in 6 meetings); this is one criteria for meeting =
selection as it stands anyway; that list might include venues like =
Prague, Berlin, Vancouver, etc.; we=E2=80=99d need to be clear in what =
=E2=80=98successful=E2=80=99 means - the meeting feedback forms provide =
one such mechanism;

b) be transparent at an early stage about where new venues might be, =
whether by country or city, so there is a fair chance for people to give =
feedback; of course, how such feedback is weighed is an open question, =
but at least it would be there, and the IAOC can then make a decision =
=E2=80=98eyes wide open=E2=80=99.

In such a system, Buenos Aires would have been a =E2=80=981 in 6=E2=80=99 =
venue. In that light, I=E2=80=99d note that many people have said how =
much they enjoyed Buenos Aires as a meeting place. And while the IAOC =
probably feel rather down over the comments about Singapore, they should =
be praised for going out on something of a limb in making the Buenos =
Aires selection. (And I=E2=80=99d add that the enthusiasm and =
helpfulness of the LACNIC hosts was also fantastic.)

In terms of virtual meetings, I=E2=80=99d suggest we try to hold more =
interim WG meetings, some completely virtually, and learn how to make =
those better. If we can regularly hold good quality wholly virtual =
interim meetings, then we can consider whether the same technology might =
be used for a larger meeting.

Tim

> On 12 Apr 2016, at 00:54, Ted Lemon <mellon@fugue.com> wrote:
>=20
> While I do not think it's true that we can entirely get away without =
doing in-person meetings, I do agree with you that we can do better at =
doing remote meetings.   Perhaps we should let this unfortunate event =
drive us to make the attempt.
>=20
> If we were to attempt such a thing, how do you think it would work?


From nobody Tue Apr 12 04:49:48 2016
Return-Path: <mellon@fugue.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 9324912E480 for <ietf@ietfa.amsl.com>; Tue, 12 Apr 2016 04:49:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.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 wTP-cA1g_dR7 for <ietf@ietfa.amsl.com>; Tue, 12 Apr 2016 04:49:44 -0700 (PDT)
Received: from mail-lf0-x22a.google.com (mail-lf0-x22a.google.com [IPv6:2a00:1450:4010:c07::22a]) (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 2D49912E720 for <ietf@ietf.org>; Tue, 12 Apr 2016 04:49:44 -0700 (PDT)
Received: by mail-lf0-x22a.google.com with SMTP id g184so21256830lfb.3 for <ietf@ietf.org>; Tue, 12 Apr 2016 04:49:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=GEEzAlouvS+5GBjrrloVob2gbGzMSZ98jOvMJdcknu8=; b=SdMBxzwc3G975t18im8a1PFfQpiNxKgRIWmmgJH5i3wsbTbXdweK7aoEIKqGoIks+T xs0JDMtLTWINOJ+Z+iim9w/tnJvmSbn6mPOYnwlkLkJpsiJUZmtfF3Y4nVznhh9XT6H6 M3gRsmeBv+H/5a2DWW0+h8tqctxjZiwXXUUQdXrDZmWPBf5X/sCgb7CkNbRXQBcRXGVk i0LgPmF1qT1RwTHH6ZxGvVeOVd9sH1Ut3qvgd9gkLawtj7V0g618j/F5cOGOEGPVs2fY spHx5obly8UKHV/q1JVtrqmGN0IcsJPy9ajcwthPeace2ODQZN2On5PWinPAoEtWOZ9E bFew==
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=GEEzAlouvS+5GBjrrloVob2gbGzMSZ98jOvMJdcknu8=; b=VnRaVlwr/P+cHZ1icOBheMte3ebnwYt+9uI7GnBo8xB/z2p0xJPGSqd+vMpJSrarlz Jm9Jrk+m6NtSaT4qoUpNd9mXAvi0S9cAYoMrE+SYiYF9hVdzqqeiwM85CAIpP/J3/93u gPYd0RIQ5OPZ36j8F4QRt7HW6ZIz+gS+r1lH1hb+YJCWGM3Y9KElXMMMzFYs109Bd/zl zVK6m1lan0VHAxYUbQqbM0ot2wFvzYZEqcFT2rTlfB9qLMsTWWxblRBRqON6bul0SGBP EZaxwaXmhM7Riae5TsNL9L5O+PbFi5EqyYgbW5oE/+5K8nuj2FXzoiEcYO8ewfOTACar VUgA==
X-Gm-Message-State: AOPr4FWq77QMIMEXLBUQLd9rfyQY3AGLLgOLFZ3hlB7cFUpSYmIjbi4OxQvp96sZI+B/Wr9aoZa/nCWMy/+7nQ==
X-Received: by 10.25.73.212 with SMTP id w203mr1024402lfa.22.1460461782372; Tue, 12 Apr 2016 04:49:42 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.25.40.136 with HTTP; Tue, 12 Apr 2016 04:49:02 -0700 (PDT)
X-Originating-IP: [71.233.41.235]
In-Reply-To: <EMEW3|9aaa87920b361e2e71efe9c7005e927cs3BChQ03tjc|ecs.soton.ac.uk|DDFE7AA1-4C07-4944-AECA-EA361A3A0B71@ecs.soton.ac.uk>
References: <m260vp7eke.wl%randy@psg.com> <570A6458.3050206@comcast.net> <m21t6d7c9t.wl%randy@psg.com> <570A67B4.3010206@comcast.net> <570AB3AF.2050401@gmail.com> <87twj99c6w.fsf@tops.chopps.org> <CAKe6YvMyp-DyeDwpPY6KYmbDbnpgnvVk_cUStnA32wmgDWcz3w@mail.gmail.com> <BBF5DDFE515C3946BC18D733B20DAD233A62AA18@XMB122CNC.rim.net> <20160411104519.GA19092@gsp.org> <3F48466D-390C-4C18-B958-732AE3E46FF1@gmail.com> <20160411223403.GA6743@gsp.org> <DDFE7AA1-4C07-4944-AECA-EA361A3A0B71@ecs.soton.ac.uk> <CAPt1N1nNo0=JSptQdWRZCFy1v-m6Q8NQy4WVGHtnRJuFZFmMig@mail.gmail.com> <EMEW3|9aaa87920b361e2e71efe9c7005e927cs3BChQ03tjc|ecs.soton.ac.uk|DDFE7AA1-4C07-4944-AECA-EA361A3A0B71@ecs.soton.ac.uk>
From: Ted Lemon <mellon@fugue.com>
Date: Tue, 12 Apr 2016 07:49:02 -0400
Message-ID: <CAPt1N1nucCAg99gVDWOHVE2up=2xK0Qm2Ud81hUhp4ryHRmwPA@mail.gmail.com>
Subject: Re: Concerns about Singapore
To: Tim Chown <tjc@ecs.soton.ac.uk>
Content-Type: multipart/alternative; boundary=001a114b1592bf261505304841f9
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/BxtoYN12kbzh6tlRvpROqhRxadg>
Cc: ietf <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: Tue, 12 Apr 2016 11:49:47 -0000

--001a114b1592bf261505304841f9
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Agree about Buenos Aires.   We already do excellent virtual interims--I
think if your standard for whether we can do a virtual IETF is that virtual
interims work, we are already there.

I think that if we want to test this idea, what we need to do is designate
some future IETF virtual _now_, and then start preparing, rather than say
"oh, we should do a virtual" and then dither about when we might be ready.
  We will never be so ready that a virtual IETF feels identical to an
in-person IETF, so let's just abandon that idea and get started on making a
virtual IETF that, while different, is still a success.

On Tue, Apr 12, 2016 at 7:43 AM, Tim Chown <tjc@ecs.soton.ac.uk> wrote:

> Hi,
>
> To minimise the chances of a =E2=80=98Singapore=E2=80=99 happening again =
it would seem
> prudent to
>
> a) re-use previous successful meeting venues for the bulk of our meetings
> (say, every 5 in 6 meetings); this is one criteria for meeting selection =
as
> it stands anyway; that list might include venues like Prague, Berlin,
> Vancouver, etc.; we=E2=80=99d need to be clear in what =E2=80=98successfu=
l=E2=80=99 means - the
> meeting feedback forms provide one such mechanism;
>
> b) be transparent at an early stage about where new venues might be,
> whether by country or city, so there is a fair chance for people to give
> feedback; of course, how such feedback is weighed is an open question, bu=
t
> at least it would be there, and the IAOC can then make a decision =E2=80=
=98eyes
> wide open=E2=80=99.
>
> In such a system, Buenos Aires would have been a =E2=80=981 in 6=E2=80=99=
 venue. In that
> light, I=E2=80=99d note that many people have said how much they enjoyed =
Buenos
> Aires as a meeting place. And while the IAOC probably feel rather down ov=
er
> the comments about Singapore, they should be praised for going out on
> something of a limb in making the Buenos Aires selection. (And I=E2=80=99=
d add that
> the enthusiasm and helpfulness of the LACNIC hosts was also fantastic.)
>
> In terms of virtual meetings, I=E2=80=99d suggest we try to hold more int=
erim WG
> meetings, some completely virtually, and learn how to make those better. =
If
> we can regularly hold good quality wholly virtual interim meetings, then =
we
> can consider whether the same technology might be used for a larger meeti=
ng.
>
> Tim
>
> > On 12 Apr 2016, at 00:54, Ted Lemon <mellon@fugue.com> wrote:
> >
> > While I do not think it's true that we can entirely get away without
> doing in-person meetings, I do agree with you that we can do better at
> doing remote meetings.   Perhaps we should let this unfortunate event dri=
ve
> us to make the attempt.
> >
> > If we were to attempt such a thing, how do you think it would work?
>
>

--001a114b1592bf261505304841f9
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Agree about Buenos Aires. =C2=A0 We already do excellent v=
irtual interims--I think if your standard for whether we can do a virtual I=
ETF is that virtual interims work, we are already there.<div><br></div><div=
>I think that if we want to test this idea, what we need to do is designate=
 some future IETF virtual _now_, and then start preparing, rather than say =
&quot;oh, we should do a virtual&quot; and then dither about when we might =
be ready. =C2=A0 We will never be so ready that a virtual IETF feels identi=
cal to an in-person IETF, so let&#39;s just abandon that idea and get start=
ed on making a virtual IETF that, while different, is still a success.</div=
></div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Tue, Ap=
r 12, 2016 at 7:43 AM, Tim Chown <span dir=3D"ltr">&lt;<a href=3D"mailto:tj=
c@ecs.soton.ac.uk" target=3D"_blank">tjc@ecs.soton.ac.uk</a>&gt;</span> wro=
te:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-=
left:1px #ccc solid;padding-left:1ex">Hi,<br>
<br>
To minimise the chances of a =E2=80=98Singapore=E2=80=99 happening again it=
 would seem prudent to<br>
<br>
a) re-use previous successful meeting venues for the bulk of our meetings (=
say, every 5 in 6 meetings); this is one criteria for meeting selection as =
it stands anyway; that list might include venues like Prague, Berlin, Vanco=
uver, etc.; we=E2=80=99d need to be clear in what =E2=80=98successful=E2=80=
=99 means - the meeting feedback forms provide one such mechanism;<br>
<br>
b) be transparent at an early stage about where new venues might be, whethe=
r by country or city, so there is a fair chance for people to give feedback=
; of course, how such feedback is weighed is an open question, but at least=
 it would be there, and the IAOC can then make a decision =E2=80=98eyes wid=
e open=E2=80=99.<br>
<br>
In such a system, Buenos Aires would have been a =E2=80=981 in 6=E2=80=99 v=
enue. In that light, I=E2=80=99d note that many people have said how much t=
hey enjoyed Buenos Aires as a meeting place. And while the IAOC probably fe=
el rather down over the comments about Singapore, they should be praised fo=
r going out on something of a limb in making the Buenos Aires selection. (A=
nd I=E2=80=99d add that the enthusiasm and helpfulness of the LACNIC hosts =
was also fantastic.)<br>
<br>
In terms of virtual meetings, I=E2=80=99d suggest we try to hold more inter=
im WG meetings, some completely virtually, and learn how to make those bett=
er. If we can regularly hold good quality wholly virtual interim meetings, =
then we can consider whether the same technology might be used for a larger=
 meeting.<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
Tim<br>
</font></span><div class=3D"HOEnZb"><div class=3D"h5"><br>
&gt; On 12 Apr 2016, at 00:54, Ted Lemon &lt;<a href=3D"mailto:mellon@fugue=
.com">mellon@fugue.com</a>&gt; wrote:<br>
&gt;<br>
&gt; While I do not think it&#39;s true that we can entirely get away witho=
ut doing in-person meetings, I do agree with you that we can do better at d=
oing remote meetings.=C2=A0 =C2=A0Perhaps we should let this unfortunate ev=
ent drive us to make the attempt.<br>
&gt;<br>
&gt; If we were to attempt such a thing, how do you think it would work?<br=
>
<br>
</div></div></blockquote></div><br></div>

--001a114b1592bf261505304841f9--


From nobody Tue Apr 12 04:57:58 2016
Return-Path: <chopps@chopps.org>
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 793BB12DE63 for <ietf@ietfa.amsl.com>; Tue, 12 Apr 2016 04:57:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.896
X-Spam-Level: 
X-Spam-Status: No, score=-2.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.996] 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 xJWHMZygpi90 for <ietf@ietfa.amsl.com>; Tue, 12 Apr 2016 04:57:55 -0700 (PDT)
Received: from smtp.chopps.org (smtp.chopps.org [54.88.81.56]) by ietfa.amsl.com (Postfix) with ESMTP id 2AB9412DE54 for <ietf@ietf.org>; Tue, 12 Apr 2016 04:57:55 -0700 (PDT)
Received: from tops.chopps.org (24-247-68-31.dhcp.trcy.mi.charter.com [24.247.68.31]) (using TLSv1.2 with cipher AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by smtp.chopps.org (Postfix) with ESMTPSA id 9DB3E6117B; Tue, 12 Apr 2016 11:57:54 +0000 (UTC)
References: <m21t6d7c9t.wl%randy@psg.com> <570A67B4.3010206@comcast.net> <570AB3AF.2050401@gmail.com> <87twj99c6w.fsf@tops.chopps.org> <CAKe6YvMyp-DyeDwpPY6KYmbDbnpgnvVk_cUStnA32wmgDWcz3w@mail.gmail.com> <BBF5DDFE515C3946BC18D733B20DAD233A62AA18@XMB122CNC.rim.net> <20160411104519.GA19092@gsp.org> <3F48466D-390C-4C18-B958-732AE3E46FF1@gmail.com> <20160411223403.GA6743@gsp.org> <87twj7eon7.fsf@tops.chopps.org> <20160412110839.GA20488@gsp.org>
User-agent: mu4e 0.9.16; emacs 24.5.1
From: <chopps@chopps.org>
To: Rich Kulawiec <rsk@gsp.org>
Subject: Re: Remote only meetings? [Re: Concerns about Singapore]
In-reply-to: <20160412110839.GA20488@gsp.org>
Date: Tue, 12 Apr 2016 07:57:53 -0400
Message-ID: <8760vn82f2.fsf@tops.chopps.org>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature"
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/8YHUu3ZTeyp3KV4rNyNGB2cgZKo>
Cc: 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: Tue, 12 Apr 2016 11:57:56 -0000

--=-=-=
Content-Type: text/plain


Rich Kulawiec <rsk@gsp.org> writes:

> On Mon, Apr 11, 2016 at 07:01:16PM -0400, chopps@chopps.org wrote:
>> Why would we want to get rid of such a rich source of inspiration and
>> invention?
>
> Because it works exclusively for the elite, privileged few.  (And no
> doubt: it works quite well.)  But it's the antithesis of inclusion
> and diversity -- and I think those qualities are increasingly necessary.

But this is not how the IETF operates. In fact we mandate that the use
of mailing lists to make sure this isn't the case. The meetings are in
addition to the mailing list, and more recently the virtual interim
meetings (which I have found to be very useful as well), and we strive
to make them as accessible as possible remotely as well.

The face to face meetings add real value to the process, and b/c they
are not mandatory they should not subtract value from the process. Your
suggestion of not having them would subtract value from the process
though. I don't see the win.

It would be great if everyone who wished to could attend the meetings to
take part in that added value though. The fact that some people cannot
is not reason abandon the meetings, but rather a reason to try and make
them as easy to attend as possible. The 1+1+1 format helps here, but so
does picking affordable sites to travel to and stay in. The conference
fee could be quite high for an individual contributor I think, we should
perhaps explore a reduced fee for individuals when this would make the
difference between attending and not. In any case I think we can and
should continue to work on this front for sure.

Thanks,
Chris.

> ---rsk


--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQIcBAEBCgAGBQJXDOLBAAoJEC4dgw7XuDAlNDcP/22SJlQqeJTXbtMgm+VXjzLp
uQ5Kt64jUjAA3nEI58eQMboJwWgMDf+8or1zY6XcW7ESvdElR8s4oBjsBgXTyAne
rQVRSt/k2GGxwzh/6dSu4NXZLgjaEu/49KZv2dPnTifQi8kuBuB82HCEet5jtAcJ
Dm6HjtGSE18UjD7of/b1tl/ZST5AePyM8rwbdOLn3ln/o/tdwQ1V+SP5pGuntl+F
BD4suyUrETHndSa8R76z/n12jx7yGvI64Wsx9r2Y0ziI3CLPsyU7Z1NyMQaQWsyr
SxIO1CNSiZ9TIDeH/8geqnftoFFI5ks5Ir1PAHuSKakk5gE3uzPHwy4Ms4KHcH60
E0EMZJj3euAD67+hfWdHZdEyH9lQL/Rwrab3flP25LVNs3qw78R+PV+tmW/IFG56
71vKQ5e3twAqUixoUNxShOpdoTIVy8jD11xq86FmLeabJtS1h9ox+e79n/gVrcLs
Zxo17z9IgW37W14GLKixmmHjBB3LNUxvGc8CHIBsPrgERa2fxg9eJu1zNsykxSRr
gD+6UWrOSYRZP5FsqmFoh+em5WcMfWPg/vpFoQ9FykkrX3KS5CsHBZL3MuwO++Td
WE1lqGT+k0qfljZs0RqKAaOFhWd5ob6vCowdEJksukmVMnVB3aGJfbC/YIk8sG3/
+X27C6bEOBSw2wiylsE9
=uzd8
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Tue Apr 12 05:07:11 2016
Return-Path: <sm@resistor.net>
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 74BA112EBAD; Tue, 12 Apr 2016 05:07:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=opendkim.org header.b=zLX1OJHY; dkim=pass (1024-bit key) header.d=resistor.net header.b=SN27blcN
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 Xhnem2_KVrcp; Tue, 12 Apr 2016 05:07:07 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 9685112D8BC; Tue, 12 Apr 2016 05:07:07 -0700 (PDT)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id u3CC710t014347 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 12 Apr 2016 05:07:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1460462827; x=1460549227; bh=wp/vl/rn1jneu2i6FCKT4tdULNlBBoiM337rmSaRuKU=; h=Date:To:From:Subject:Cc; b=zLX1OJHYeRJ2rT+j2vQ2+PAz06qOQFW8IVMa1vLnH7KE4gmp8dZ9CgLZdKw6R4mv3 jiehps5baXLdEBt+K0ynpKH6PFCAfRmHK8PcQXl4LhEk8VO0Aap1UpVzN9DqVRZny1 kvDZ0hwW7CtvKwpn6LmSRD28HfGtWhYYoILRAlko=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1460462827; x=1460549227; i=@resistor.net; bh=wp/vl/rn1jneu2i6FCKT4tdULNlBBoiM337rmSaRuKU=; h=Date:To:From:Subject:Cc; b=SN27blcNuNgEUH54AEAHxcOb25lHmS2Zgg9nFfJZv8paT/x9g8y+Sas0RavI+Hr1a RX2W1EYoMcR24pSTy8Anc0Cjky7KwS2CCurVlR0r7Vwl87fA6KChruJYC51Y5eKdfa H8xVwuTfk7YIthGjp5WhUA1AMjOw71UzML8eGKWc=
Message-Id: <6.2.5.6.2.20160412031201.0da034e8@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Tue, 12 Apr 2016 05:01:04 -0700
To: iesg@ietf.org
From: SM <sm@resistor.net>
Subject: Transparency of IAOC
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/PR0C60WCm3d6opi8a8Ezq0akRis>
Cc: 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: Tue, 12 Apr 2016 12:07:08 -0000

Dear Members of the IESG,

Section 3 of RFC 4071 states that the "IASA structure is designed to 
ensure accountability and transparency of the IETF administrative and 
fiscal activities to the IETF community".  There are other 
occurrences of the word "transparency" in that RFC.

Transparency can be discussed from several perspectives.  If I am, 
for example, someone you dislike and/or you believe that my 
motivation is only to make your life difficult, you could ask me to 
prove that there is a transparency problem.  Another perspective is 
when you believe that the burden of proof is on your side, i.e. it is 
up to you to show that when you use the word "transparency", that is 
what you mean.

Regards,
-sm


From nobody Tue Apr 12 05:19:53 2016
Return-Path: <swmike@swm.pp.se>
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 3047712EC2E for <ietf@ietfa.amsl.com>; Tue, 12 Apr 2016 05:19:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.297
X-Spam-Level: 
X-Spam-Status: No, score=-5.297 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.996, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=swm.pp.se
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 2UkM3EWr2oJu for <ietf@ietfa.amsl.com>; Tue, 12 Apr 2016 05:19:48 -0700 (PDT)
Received: from uplift.swm.pp.se (ipv6.swm.pp.se [IPv6:2a00:801::f]) (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 6A99212E182 for <ietf@ietf.org>; Tue, 12 Apr 2016 05:19:45 -0700 (PDT)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id 48DD0A2; Tue, 12 Apr 2016 14:19:43 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1460463583; bh=BG5qUpRFnBsM005sJcMNarS2ny3XHRlLEj1Ufz5/pQI=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=1AsQFGKPbE/JYFQFqoIE7egZCeWT+E7VcG6DWHmslbp3u/+XmoO5VQ7gNyppOHtn/ FkQ70RNMR3BvTPZVV+nqUhSwo6/bZi0w1PrdhK45uKCEkvhFwOvsJATRaklgUOoV3D TF2ET6sdvHggXpC3OrIP4mjA33rR7gLM00mYYQxY=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 22A71A1; Tue, 12 Apr 2016 14:19:43 +0200 (CEST)
Date: Tue, 12 Apr 2016 14:19:43 +0200 (CEST)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Jared Mauch <jared@puck.nether.net>
Subject: Re: Meetecho was Re: Concerns about Singapore
In-Reply-To: <F2FE2CAF-A8E5-4956-8A9F-2BBD704154A8@puck.nether.net>
Message-ID: <alpine.DEB.2.02.1604121412350.16013@uplift.swm.pp.se>
References: <20160411223403.GA6743@gsp.org> <860206232.1954211.1460419714948.JavaMail.yahoo@mail.yahoo.com> <F2FE2CAF-A8E5-4956-8A9F-2BBD704154A8@puck.nether.net>
User-Agent: Alpine 2.02 (DEB 1266 2009-07-14)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/YKb3Q9EDKb0WeOcORLmB0u21AAM>
Cc: "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: Tue, 12 Apr 2016 12:19:51 -0000

On Mon, 11 Apr 2016, Jared Mauch wrote:

>
>> On Apr 11, 2016, at 8:08 PM, <lloyd.wood@yahoo.co.uk> <lloyd.wood@yahoo.co.uk> wrote:
>>
>> try listening to the first twenty minutes of this.
>> then tell me if IETF WG meetings with remote presentation
>> via Meetecho are anything other than a complete waste
>> of time.
>>
>
> The NTPWG had a very successful experience, including remote presenters, and remote people going back and forth with their interaction.
>
> I would say your experience is atypical, and certainly not the desired outcome.

+1 on this.

I have spent the past meetings doing frequent jabber scribe work. I use 
Meetecho to do this, and I place myself next to the front participant mic 
(so I can see the name tag of the person speaking), and then I type on 
jabber the name of who the person speaking in the mic. There is (I've been 
told) now a suggestion to the IETF secritariat to reserve the seat next to 
the front mic (at table) for Jabber scribe, and this would be great. Now 
we just need to teach everybody to flash their badge to the jabber scribe 
as well.

I have long offered to call out the slides (which is typically needed for 
people who are on audio+jabber only) if someone wanted it, but the past 
few meetings nobody has requested that. My guess is that most people use 
Meetecho because it gives the complete view of what's going on, you get 
chat+presentation+video+sound, and you can also ask questions (which was 
used numerous times in the sessions I participated in).

Generally, I'm very happy with Meetecho (wonders of HTML5+WEBRTC to be 
able to run this in just a browser). There were some initial sound 
problems on monday morning, but that was quickly rectified.

I also really appreciate the fact that I can call out "meetecho" in the 
jabber room to notify them of potential problems, and they immediately 
dispatch someone to fix the problem (including alerting the A/V crew if 
it's a local issue).

So while there were a few hiccups, I'd say most of the time Meetecho and 
the local A/V works great.

-- 
Mikael Abrahamsson    email: swmike@swm.pp.se


From nobody Tue Apr 12 05:30:49 2016
Return-Path: <tjc@ecs.soton.ac.uk>
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 EE18812EC31 for <ietf@ietfa.amsl.com>; Tue, 12 Apr 2016 05:30:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.516
X-Spam-Level: 
X-Spam-Status: No, score=-4.516 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_MED=-2.3, RP_MATCHES_RCVD=-0.996, SPF_NEUTRAL=0.779] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ecs.soton.ac.uk
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 lcpBjAFKQWJR for <ietf@ietfa.amsl.com>; Tue, 12 Apr 2016 05:30:45 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [IPv6:2001:630:d0:f102::25e]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6F11412D1E0 for <ietf@ietf.org>; Tue, 12 Apr 2016 05:30:45 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (localhost [127.0.0.1]) by falcon.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id u3CCUhoJ025596; Tue, 12 Apr 2016 13:30:43 +0100
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk u3CCUhoJ025596
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=201304; t=1460464243; bh=6T2VawsHlIqXJiVBJFpKS5Ojlis=; h=Mime-Version:Subject:From:In-Reply-To:Date:Cc:References:To; b=WgYYsdZ5JHaAQyqdGVyKFJ2NOn+1XAA6iWO4t23ZCHvA1g7lVO1HTjy1t9ZX5Wzwb /EvyAQG9nCZclwS6jaEHb9vAQ2lTX9whMqN2vYfTROqfEaSM4ictnt6C0RjcDnL5dw a5aGSe/sN+sEWjkuYVLOsbZd3ARl3ybYFCt31WXQ=
Received: from gander.ecs.soton.ac.uk ([2001:630:d0:f102:250:56ff:fea0:401]) by falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [2001:630:d0:f102:250:56ff:fea0:68da]) envelope-from <tjc@ecs.soton.ac.uk> with ESMTP (valid=N/A) id s3BDUh3219206748Xe ret-id none; Tue, 12 Apr 2016 13:30:43 +0100
Received: from [192.168.0.16] (tchowndsl.claranet.co.uk [212.188.254.49]) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id u3CCUbf2013207 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 12 Apr 2016 13:30:38 +0100
Content-Type: multipart/alternative; boundary="Apple-Mail=_565F6DB7-8EEF-44A1-8594-BFED5BBA8953"
Mime-Version: 1.0 (Mac OS X Mail 9.2 \(3112\))
Subject: Virtual IETFs (was: Re: Concerns about Singapore)
From: Tim Chown <tjc@ecs.soton.ac.uk>
In-Reply-To: <CAPt1N1nucCAg99gVDWOHVE2up=2xK0Qm2Ud81hUhp4ryHRmwPA@mail.gmail.com>
Date: Tue, 12 Apr 2016 13:30:37 +0100
Message-ID: <EMEW3|bbf82c39a7afc0305d21ff1c5582540bs3BDUh03tjc|ecs.soton.ac.uk|22CF4C02-B728-4148-A86A-B42080728FE6@ecs.soton.ac.uk>
References: <m260vp7eke.wl%randy@psg.com> <570A6458.3050206@comcast.net> <m21t6d7c9t.wl%randy@psg.com> <570A67B4.3010206@comcast.net> <570AB3AF.2050401@gmail.com> <87twj99c6w.fsf@tops.chopps.org> <CAKe6YvMyp-DyeDwpPY6KYmbDbnpgnvVk_cUStnA32wmgDWcz3w@mail.gmail.com> <BBF5DDFE515C3946BC18D733B20DAD233A62AA18@XMB122CNC.rim.net> <20160411104519.GA19092@gsp.org> <3F48466D-390C-4C18-B958-732AE3E46FF1@gmail.com> <20160411223403.GA6743@gsp.org> <DDFE7AA1-4C07-4944-AECA-EA361A3A0B71@ecs.soton.ac.uk> <CAPt1N1nNo0=JSptQdWRZCFy1v-m6Q8NQy4WVGHtnRJuFZFmMig@mail.gmail.com> <EMEW3|9aaa87920b361e2e71efe9c7005e927cs3BChQ03tjc|ecs.soton.ac.uk|DDFE7AA1-4C07-4944-AECA-EA361A3A0B71@ecs.soton.ac.uk> <CAPt1N1nucCAg99gVDWOHVE2up=2xK0Qm2Ud81hUhp4ryHRmwPA@mail.gmail.com> <22CF4C02-B728-4148-A86A-B42080728FE6@ecs.soton.ac.uk>
To: Ted Lemon <mellon@fugue.com>
X-Mailer: Apple Mail (2.3112)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=s3BDUh321920674800; tid=s3BDUh3219206748Xe; client=relay,forged,no_ptr,ipv6; mail=; rcpt=; nrcpt=2:0; fails=0
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: u3CCUhoJ025596
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/_fVFTbDddjPhprfS8Ognh9Yiezk>
Cc: ietf <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: Tue, 12 Apr 2016 12:30:48 -0000

--Apple-Mail=_565F6DB7-8EEF-44A1-8594-BFED5BBA8953
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

> On 12 Apr 2016, at 12:49, Ted Lemon <mellon@fugue.com> wrote:
>=20
> Agree about Buenos Aires.   We already do excellent virtual =
interims--I think if your standard for whether we can do a virtual IETF =
is that virtual interims work, we are already there.
>=20
> I think that if we want to test this idea, what we need to do is =
designate some future IETF virtual _now_, and then start preparing, =
rather than say "oh, we should do a virtual" and then dither about when =
we might be ready.   We will never be so ready that a virtual IETF feels =
identical to an in-person IETF, so let's just abandon that idea and get =
started on making a virtual IETF that, while different, is still a =
success.

Sounds interesting, if something of a big leap to attempt. Is a larger =
wholly virtual, multiple WG interim meeting a next step then?

Btw where do we get the virtual T-shirt? ;)

Tim

>=20
> On Tue, Apr 12, 2016 at 7:43 AM, Tim Chown <tjc@ecs.soton.ac.uk =
<mailto:tjc@ecs.soton.ac.uk>> wrote:
> Hi,
>=20
> To minimise the chances of a =E2=80=98Singapore=E2=80=99 happening =
again it would seem prudent to
>=20
> a) re-use previous successful meeting venues for the bulk of our =
meetings (say, every 5 in 6 meetings); this is one criteria for meeting =
selection as it stands anyway; that list might include venues like =
Prague, Berlin, Vancouver, etc.; we=E2=80=99d need to be clear in what =
=E2=80=98successful=E2=80=99 means - the meeting feedback forms provide =
one such mechanism;
>=20
> b) be transparent at an early stage about where new venues might be, =
whether by country or city, so there is a fair chance for people to give =
feedback; of course, how such feedback is weighed is an open question, =
but at least it would be there, and the IAOC can then make a decision =
=E2=80=98eyes wide open=E2=80=99.
>=20
> In such a system, Buenos Aires would have been a =E2=80=981 in 6=E2=80=99=
 venue. In that light, I=E2=80=99d note that many people have said how =
much they enjoyed Buenos Aires as a meeting place. And while the IAOC =
probably feel rather down over the comments about Singapore, they should =
be praised for going out on something of a limb in making the Buenos =
Aires selection. (And I=E2=80=99d add that the enthusiasm and =
helpfulness of the LACNIC hosts was also fantastic.)
>=20
> In terms of virtual meetings, I=E2=80=99d suggest we try to hold more =
interim WG meetings, some completely virtually, and learn how to make =
those better. If we can regularly hold good quality wholly virtual =
interim meetings, then we can consider whether the same technology might =
be used for a larger meeting.
>=20
> Tim
>=20
> > On 12 Apr 2016, at 00:54, Ted Lemon <mellon@fugue.com =
<mailto:mellon@fugue.com>> wrote:
> >
> > While I do not think it's true that we can entirely get away without =
doing in-person meetings, I do agree with you that we can do better at =
doing remote meetings.   Perhaps we should let this unfortunate event =
drive us to make the attempt.
> >
> > If we were to attempt such a thing, how do you think it would work?
>=20
>=20


--Apple-Mail=_565F6DB7-8EEF-44A1-8594-BFED5BBA8953
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D""><div><blockquote type=3D"cite" class=3D""><div class=3D"">On =
12 Apr 2016, at 12:49, Ted Lemon &lt;<a href=3D"mailto:mellon@fugue.com" =
class=3D"">mellon@fugue.com</a>&gt; wrote:</div><br =
class=3D"Apple-interchange-newline"><div class=3D""><div dir=3D"ltr" =
class=3D"">Agree about Buenos Aires. &nbsp; We already do excellent =
virtual interims--I think if your standard for whether we can do a =
virtual IETF is that virtual interims work, we are already there.<div =
class=3D""><br class=3D""></div><div class=3D"">I think that if we want =
to test this idea, what we need to do is designate some future IETF =
virtual _now_, and then start preparing, rather than say "oh, we should =
do a virtual" and then dither about when we might be ready. &nbsp; We =
will never be so ready that a virtual IETF feels identical to an =
in-person IETF, so let's just abandon that idea and get started on =
making a virtual IETF that, while different, is still a =
success.</div></div></div></blockquote><div><br =
class=3D""></div><div>Sounds interesting, if something of a big leap to =
attempt. Is a larger wholly virtual, multiple WG interim meeting a next =
step then?</div><div><br class=3D""></div><div>Btw where do we get the =
virtual T-shirt? ;)</div><div><br class=3D""></div>Tim</div><div><br =
class=3D""><blockquote type=3D"cite" class=3D""><div class=3D""><div =
class=3D"gmail_extra"><br class=3D""><div class=3D"gmail_quote">On Tue, =
Apr 12, 2016 at 7:43 AM, Tim Chown <span dir=3D"ltr" class=3D"">&lt;<a =
href=3D"mailto:tjc@ecs.soton.ac.uk" target=3D"_blank" =
class=3D"">tjc@ecs.soton.ac.uk</a>&gt;</span> wrote:<br =
class=3D""><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 =
.8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br class=3D"">
<br class=3D"">
To minimise the chances of a =E2=80=98Singapore=E2=80=99 happening again =
it would seem prudent to<br class=3D"">
<br class=3D"">
a) re-use previous successful meeting venues for the bulk of our =
meetings (say, every 5 in 6 meetings); this is one criteria for meeting =
selection as it stands anyway; that list might include venues like =
Prague, Berlin, Vancouver, etc.; we=E2=80=99d need to be clear in what =
=E2=80=98successful=E2=80=99 means - the meeting feedback forms provide =
one such mechanism;<br class=3D"">
<br class=3D"">
b) be transparent at an early stage about where new venues might be, =
whether by country or city, so there is a fair chance for people to give =
feedback; of course, how such feedback is weighed is an open question, =
but at least it would be there, and the IAOC can then make a decision =
=E2=80=98eyes wide open=E2=80=99.<br class=3D"">
<br class=3D"">
In such a system, Buenos Aires would have been a =E2=80=981 in 6=E2=80=99 =
venue. In that light, I=E2=80=99d note that many people have said how =
much they enjoyed Buenos Aires as a meeting place. And while the IAOC =
probably feel rather down over the comments about Singapore, they should =
be praised for going out on something of a limb in making the Buenos =
Aires selection. (And I=E2=80=99d add that the enthusiasm and =
helpfulness of the LACNIC hosts was also fantastic.)<br class=3D"">
<br class=3D"">
In terms of virtual meetings, I=E2=80=99d suggest we try to hold more =
interim WG meetings, some completely virtually, and learn how to make =
those better. If we can regularly hold good quality wholly virtual =
interim meetings, then we can consider whether the same technology might =
be used for a larger meeting.<br class=3D"">
<span class=3D"HOEnZb"><font color=3D"#888888" class=3D""><br class=3D"">
Tim<br class=3D"">
</font></span><div class=3D"HOEnZb"><div class=3D"h5"><br class=3D"">
&gt; On 12 Apr 2016, at 00:54, Ted Lemon &lt;<a =
href=3D"mailto:mellon@fugue.com" class=3D"">mellon@fugue.com</a>&gt; =
wrote:<br class=3D"">
&gt;<br class=3D"">
&gt; While I do not think it's true that we can entirely get away =
without doing in-person meetings, I do agree with you that we can do =
better at doing remote meetings.&nbsp; &nbsp;Perhaps we should let this =
unfortunate event drive us to make the attempt.<br class=3D"">
&gt;<br class=3D"">
&gt; If we were to attempt such a thing, how do you think it would =
work?<br class=3D"">
<br class=3D"">
</div></div></blockquote></div><br class=3D""></div>
</div></blockquote></div><br class=3D""></body></html>=

--Apple-Mail=_565F6DB7-8EEF-44A1-8594-BFED5BBA8953--


From nobody Tue Apr 12 05:35:53 2016
Return-Path: <tjc@ecs.soton.ac.uk>
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 D96BD12EC53 for <ietf@ietfa.amsl.com>; Tue, 12 Apr 2016 05:35:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.517
X-Spam-Level: 
X-Spam-Status: No, score=-4.517 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.996, SPF_NEUTRAL=0.779] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ecs.soton.ac.uk
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 rwxYkdtSwAzB for <ietf@ietfa.amsl.com>; Tue, 12 Apr 2016 05:35:51 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [IPv6:2001:630:d0:f102::25e]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7BD3812DFF4 for <ietf@ietf.org>; Tue, 12 Apr 2016 05:35:51 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (localhost [127.0.0.1]) by falcon.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id u3CCZlPS026515; Tue, 12 Apr 2016 13:35:47 +0100
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk u3CCZlPS026515
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=201304; t=1460464547; bh=5uFHgPQDiAIHLbkHd6i1Hs8v5WA=; h=Mime-Version:Subject:From:In-Reply-To:Date:Cc:References:To; b=e9xNVLzZOt5aH1GXui3zhagOOP/k8pJkd1viu6lBVisGIE9SUi1SXMJt2Jqlhwapm ZD1Xeh/HsvRKZQbkh9iC/AsmH8WDdJbefl13c0Qin9rXzcH3zZVPf6jqgt4snlwvkA wW5b9zxgpMSkYEpmPuTzCECjIXH3Mi9tbQDGndME=
Received: from gander.ecs.soton.ac.uk ([2001:630:d0:f102:250:56ff:fea0:401]) by falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [2001:630:d0:f102:250:56ff:fea0:68da]) envelope-from <tjc@ecs.soton.ac.uk> with ESMTP (valid=N/A) id s3BDZl32192067906d ret-id none; Tue, 12 Apr 2016 13:35:47 +0100
Received: from 20010a88d51011.ipv6.customer.clara.net (20010a88d51011.ipv6.customer.clara.net [IPv6:2001:a88:d510:1101:a93e:5914:9e35:ffe3] (may be forged)) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id u3CCZeAl014471 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 12 Apr 2016 13:35:40 +0100
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 9.2 \(3112\))
Subject: Re: Meetecho was Re: Concerns about Singapore
From: Tim Chown <tjc@ecs.soton.ac.uk>
In-Reply-To: <alpine.DEB.2.02.1604121412350.16013@uplift.swm.pp.se>
Date: Tue, 12 Apr 2016 13:35:40 +0100
Content-Transfer-Encoding: quoted-printable
Message-ID: <EMEW3|6105314ca86919853e4a12a21c94d38as3BDZl03tjc|ecs.soton.ac.uk|2ED8F5F5-126E-44C1-A4E4-54E9C7881CDD@ecs.soton.ac.uk>
References: <20160411223403.GA6743@gsp.org> <860206232.1954211.1460419714948.JavaMail.yahoo@mail.yahoo.com> <F2FE2CAF-A8E5-4956-8A9F-2BBD704154A8@puck.nether.net> <alpine.DEB.2.02.1604121412350.16013@uplift.swm.pp.se> <2ED8F5F5-126E-44C1-A4E4-54E9C7881CDD@ecs.soton.ac.uk>
To: Mikael Abrahamsson <swmike@swm.pp.se>
X-Mailer: Apple Mail (2.3112)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=s3BDZl321920679000; tid=s3BDZl32192067906d; client=relay,forged,no_ptr,ipv6; mail=; rcpt=; nrcpt=3:0; fails=0
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: u3CCZlPS026515
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/zOPbZ_Ord8DR7gQtPPpyf5cv6_0>
Cc: "ietf@ietf.org" <ietf@ietf.org>, Jared Mauch <jared@puck.nether.net>
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: Tue, 12 Apr 2016 12:35:53 -0000

> On 12 Apr 2016, at 13:19, Mikael Abrahamsson <swmike@swm.pp.se> wrote:
>=20
> I have spent the past meetings doing frequent jabber scribe work. I =
use Meetecho to do this, and I place myself next to the front =
participant mic (so I can see the name tag of the person speaking), and =
then I type on jabber the name of who the person speaking in the mic. =
There is (I've been told) now a suggestion to the IETF secritariat to =
reserve the seat next to the front mic (at table) for Jabber scribe, and =
this would be great. Now we just need to teach everybody to flash their =
badge to the jabber scribe as well.

I also do this, and agree it=E2=80=99s a good idea.

> I have long offered to call out the slides (which is typically needed =
for people who are on audio+jabber only) if someone wanted it, but the =
past few meetings nobody has requested that. My guess is that most =
people use Meetecho because it gives the complete view of what's going =
on, you get chat+presentation+video+sound, and you can also ask =
questions (which was used numerous times in the sessions I participated =
in).

I also noticed that remote people don=E2=80=99t seem to want slide =
numbers called out now. Might be interesting to see if we have stats on =
numbers of people listening to the old school audio-only streams, or on =
non-Meetecho participants in Jabber (the login IDs of Meetecho people is =
distinctive there=E2=80=A6), just to get some data points on current =
trends.

> Generally, I'm very happy with Meetecho (wonders of HTML5+WEBRTC to be =
able to run this in just a browser). There were some initial sound =
problems on monday morning, but that was quickly rectified.
>=20
> I also really appreciate the fact that I can call out "meetecho" in =
the jabber room to notify them of potential problems, and they =
immediately dispatch someone to fix the problem (including alerting the =
A/V crew if it's a local issue).

Just like Beetlejuice :)

> So while there were a few hiccups, I'd say most of the time Meetecho =
and the local A/V works great.

Agreed.

Tim

>=20
> --=20
> Mikael Abrahamsson    email: swmike@swm.pp.se
>=20


From nobody Tue Apr 12 05:46:55 2016
Return-Path: <rsk@gsp.org>
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 53A9012EC49 for <ietf@ietfa.amsl.com>; Tue, 12 Apr 2016 05:46:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] 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 B9Ri-S9AS9Gz for <ietf@ietfa.amsl.com>; Tue, 12 Apr 2016 05:46:42 -0700 (PDT)
Received: from taos.firemountain.net (taos.firemountain.net [207.114.3.54]) (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 18B0E12EB25 for <ietf@ietf.org>; Tue, 12 Apr 2016 05:46:42 -0700 (PDT)
Received: from gsp.org (localhost [127.0.0.1]) by taos.firemountain.net (8.15.1/8.14.9) with SMTP id u3CCkdEA025983 for <ietf@ietf.org>; Tue, 12 Apr 2016 08:46:40 -0400 (EDT)
Date: Tue, 12 Apr 2016 08:46:39 -0400
From: Rich Kulawiec <rsk@gsp.org>
To: ietf@ietf.org
Subject: Re: Remote only meetings? [Re: Concerns about Singapore]
Message-ID: <20160412124639.GA27223@gsp.org>
References: <570AB3AF.2050401@gmail.com> <87twj99c6w.fsf@tops.chopps.org> <CAKe6YvMyp-DyeDwpPY6KYmbDbnpgnvVk_cUStnA32wmgDWcz3w@mail.gmail.com> <BBF5DDFE515C3946BC18D733B20DAD233A62AA18@XMB122CNC.rim.net> <20160411104519.GA19092@gsp.org> <3F48466D-390C-4C18-B958-732AE3E46FF1@gmail.com> <20160411223403.GA6743@gsp.org> <87twj7eon7.fsf@tops.chopps.org> <20160412110839.GA20488@gsp.org> <8760vn82f2.fsf@tops.chopps.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <8760vn82f2.fsf@tops.chopps.org>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/sZTEknKLU4ZzmKHm0c7PaRLxIm8>
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: Tue, 12 Apr 2016 12:46:43 -0000

On Tue, Apr 12, 2016 at 07:57:53AM -0400, chopps@chopps.org wrote:
> Your suggestion of not having them would subtract value from the process
> though. I don't see the win.

The win is that all of the time and effort and expense (all of which
are finite resources) that go into those could be directed elsewhere.

> The conference
> fee could be quite high for an individual contributor I think, we should
> perhaps explore a reduced fee for individuals when this would make the
> difference between attending and not.

It's not just the money, as I've said several times.  It's the time:
not everyone has the incredible luxury of being able to be away from their
job or their family.  It's the travel expense and the travel hassle/risk,
both of which are increasing.  It's the political/legal climate that
attendees are exposed to.  It's the problem of unrestricted Internet
access.  It's the increasingly-intrusive border crossings.  It's all
the factors that go into being there in person for several days.

These meetings select for a highly limited (by circumstance, by necessity,
and by choice) subset.  And once upon a time, when the 'net was much
younger and more limited in terms of geography and scope, that might
have been alright, because the subset mapped fairly well onto the larger
set of people involved in networking.  But that's no longer true.
And the difficulties/expense of travel are only going to get worse
for the forseeable future: they're not going to get better.

---rsk


From nobody Tue Apr 12 05:49:48 2016
Return-Path: <loa@pi.nu>
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 4C65312ECF0 for <ietf@ietfa.amsl.com>; Tue, 12 Apr 2016 05:49:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.896
X-Spam-Level: 
X-Spam-Status: No, score=-2.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.996] 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 3Nw7yapDaO6U for <ietf@ietfa.amsl.com>; Tue, 12 Apr 2016 05:49:45 -0700 (PDT)
Received: from pipi.pi.nu (pipi.pi.nu [83.168.239.141]) (using TLSv1.1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7299C12E59B for <ietf@ietf.org>; Tue, 12 Apr 2016 05:49:45 -0700 (PDT)
Received: from [192.168.1.2] (unknown [122.53.41.246]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: loa@pi.nu) by pipi.pi.nu (Postfix) with ESMTPSA id 674D31802C3A for <ietf@ietf.org>; Tue, 12 Apr 2016 14:49:41 +0200 (CEST)
Subject: Re: Remote only meetings? [Re: Concerns about Singapore]
To: ietf@ietf.org
References: <m21t6d7c9t.wl%randy@psg.com> <570A67B4.3010206@comcast.net> <570AB3AF.2050401@gmail.com> <87twj99c6w.fsf@tops.chopps.org> <CAKe6YvMyp-DyeDwpPY6KYmbDbnpgnvVk_cUStnA32wmgDWcz3w@mail.gmail.com> <BBF5DDFE515C3946BC18D733B20DAD233A62AA18@XMB122CNC.rim.net> <20160411104519.GA19092@gsp.org> <3F48466D-390C-4C18-B958-732AE3E46FF1@gmail.com> <20160411223403.GA6743@gsp.org> <87twj7eon7.fsf@tops.chopps.org> <20160412110839.GA20488@gsp.org>
From: Loa Andersson <loa@pi.nu>
Message-ID: <570CEED7.1030202@pi.nu>
Date: Tue, 12 Apr 2016 20:49:27 +0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2
MIME-Version: 1.0
In-Reply-To: <20160412110839.GA20488@gsp.org>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/ggsEJlfTduSsIQFBgbTD_EINay0>
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: Tue, 12 Apr 2016 12:49:47 -0000

All,

On 2016-04-12 19:08, Rich Kulawiec wrote:
> On Mon, Apr 11, 2016 at 07:01:16PM -0400, chopps@chopps.org wrote:
>> Why would we want to get rid of such a rich source of inspiration and
>> invention?
>
> Because it works exclusively for the elite, privileged few.  (And no
> doubt: it works quite well.)  But it's the antithesis of inclusion
> and diversity -- and I think those qualities are increasingly necessary.

I don't think we should entertain ideas about *replace* f-2-f meetings.

I think we could entertain ideas about IETF wide remote meetings, but
don't think that such meetings should be modeled after the f-2-f
meetings.

For example we should take the opportunity to get rid of all colliding
meetings, i.e. run just meeting (wg or other) at the time.

Let us say that we set aside enough time about half way between two IETF
meetings and schedule all the meetings, as requested by wg chairs or
people in charge of other meetings, as a long series.

Let us assume that the wg meetings is on average 1.5 hours, scheduling
100 wg meetings would require 150 hours.

/Loa

>
> ---rsk
>


From nobody Tue Apr 12 06:18:46 2016
Return-Path: <loa@pi.nu>
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 5967A12EDF2 for <ietf@ietfa.amsl.com>; Tue, 12 Apr 2016 06:18:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.896
X-Spam-Level: 
X-Spam-Status: No, score=-2.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.996] 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 F61tQ22pfc5u for <ietf@ietfa.amsl.com>; Tue, 12 Apr 2016 06:18:23 -0700 (PDT)
Received: from pipi.pi.nu (pipi.pi.nu [83.168.239.141]) (using TLSv1.1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AD66C12EDE9 for <ietf@ietf.org>; Tue, 12 Apr 2016 06:18:23 -0700 (PDT)
Received: from [192.168.1.2] (unknown [122.53.41.246]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: loa@pi.nu) by pipi.pi.nu (Postfix) with ESMTPSA id C766C1802C38 for <ietf@ietf.org>; Tue, 12 Apr 2016 15:18:21 +0200 (CEST)
Subject: Re: Concerns about Singapore
To: ietf@ietf.org
References: <m260vp7eke.wl%randy@psg.com> <570A6458.3050206@comcast.net> <m21t6d7c9t.wl%randy@psg.com> <570A67B4.3010206@comcast.net> <570AB3AF.2050401@gmail.com> <87twj99c6w.fsf@tops.chopps.org> <CAKe6YvMyp-DyeDwpPY6KYmbDbnpgnvVk_cUStnA32wmgDWcz3w@mail.gmail.com> <BBF5DDFE515C3946BC18D733B20DAD233A62AA18@XMB122CNC.rim.net> <20160411104519.GA19092@gsp.org> <3F48466D-390C-4C18-B958-732AE3E46FF1@gmail.com> <20160411223403.GA6743@gsp.org> <CAPt1N1nNo0=JSptQdWRZCFy1v-m6Q8NQy4WVGHtnRJuFZFmMig@mail.gmail.com> <CAKr6gn1KmNcgNwbPHZWB2aJQAuchz4eB7gxJhV2Dsbc1Z50kDw@mail.gmail.com> <CAPt1N1mWjg_-525avYJ4PnSECYQrtpVFJCXPfH=PryJ8q0vy4Q@mail.gmail.com> <A684A3C4-7161-49F5-919E-A5F948A3F316@ecs.soton.ac.uk> <EMEW3|d5cb2cb80712b3716e1ab4e2a54c9430s3BCG403tjc|ecs.soton.ac.uk|A684A3C4-7161-49F5-919E-A5F948A3F316@ecs.soton.ac.uk>
From: Loa Andersson <loa@pi.nu>
Message-ID: <570CF594.5070509@pi.nu>
Date: Tue, 12 Apr 2016 21:18:12 +0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2
MIME-Version: 1.0
In-Reply-To: <EMEW3|d5cb2cb80712b3716e1ab4e2a54c9430s3BCG403tjc|ecs.soton.ac.uk|A684A3C4-7161-49F5-919E-A5F948A3F316@ecs.soton.ac.uk>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/f29nNeeGtxAzCBFt1pbhFHLgbRQ>
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: Tue, 12 Apr 2016 13:18:40 -0000

Folks,

On 2016-04-12 19:15, Tim Chown wrote:
>> On 12 Apr 2016, at 01:50, Ted Lemon <mellon@fugue.com> wrote:
>>
>> The only thing you mentioned that can't be done with existing conferencing software is hums, and I'm sure we could figure out a way to make that work.  It's not rocket science.   Chairs who judge consensus by looking at the room aren't following IETF process--consensus is judged on the mailing list.  Hums are useful for figuring out why we _don't_ have consensus, and for _getting_ to consensus, but if you were to judge consensus by hums or a show of hands, then you'd be taking a vote, wouldn't you?
>
> Meetecho has a â€�humâ€™ button, which throws â€�hmmmmmmâ€™ into the jabber room for the WG. I did see it used, once.

Let me return to the start of this discussion.

It seems to me that the LGBTQ peoples concern about a meeting in
Singapore is real, at least it is perceived to be real.

I don't think anything that is within our power to do can change this
perception.

Thus we need to take this seriously, the concerns is about our upcoming
meeting in Singapore. That should be our focus.

/Loa

>
> Tim
>


From nobody Tue Apr 12 06:23:41 2016
Return-Path: <mellon@fugue.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 2794D12EE63 for <ietf@ietfa.amsl.com>; Tue, 12 Apr 2016 06:23:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.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 OytqKrPmh79t for <ietf@ietfa.amsl.com>; Tue, 12 Apr 2016 06:23:37 -0700 (PDT)
Received: from mail-lf0-x229.google.com (mail-lf0-x229.google.com [IPv6:2a00:1450:4010:c07::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 AF28612EE54 for <ietf@ietf.org>; Tue, 12 Apr 2016 06:23:36 -0700 (PDT)
Received: by mail-lf0-x229.google.com with SMTP id g184so24876048lfb.3 for <ietf@ietf.org>; Tue, 12 Apr 2016 06:23:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=bqnmIO6t1xbAy5LbfSq9EU8RFye/r+Ba3YF5d5AVDUc=; b=dOBJqx2UNosGhkUTK1huNE8GVDZMBXzPtsS/29SVr3Uc/VSB3zuUKzovopAtpZeiTM V5YkYO9guWe1/BmiTuwLDrCgkd717ve5t+hocT2NbWIBFbd6jnweMnM45NjmWfWHvhXb UvXysMWYiuqc0Czps/41gE2c1FGhhWV/yXQQimHEWZ+95P/WEjC6VE9yQpkXhccz3Ek5 xZqrGd4Xtg32iMLMcbS+9UgXpCUDw7/ZDFm9uSDaqVoIkTf2TQK8rE0Z4xsdYuLpPcwN 8NET7y+DPn5PrU9PtlW9Hi3kSbZgFeui+Pjc3wgxehJF1iKIPyy1etGDWmAbvBYRCaBj EFzA==
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=bqnmIO6t1xbAy5LbfSq9EU8RFye/r+Ba3YF5d5AVDUc=; b=DWYx2MHS6rQhhcXzHVJ/LQgijJkpJRWTk8K9QVTDOagSe+qvPY5cxxrpYMSROGPIaa uIs8yN5Q9fS7W8ZaVsUh3y+Su53+qHiK9uEDTOiyV0kEKOVDDajyPHD9m0JRJaqTAKzj kwc6RBmZ0TRYX0GtwIL2aaDb3huAgXeHJgL3VXmE92ciQnEJGpfilUMLfbd/KoUFuZob m17LoK6ACYUMORdWF5OKrBd4WnKN15qMFYXiBlY0bn3YKLfDQIwxukX1+kJJH4i0j4Yc F8xWCKW8v4HVyJHwWLrXJtYFw2V+EnhPC5F6eocFjcZ8n4EBVB6gnDs9nArF7G9x1CEz 3epw==
X-Gm-Message-State: AOPr4FUVDAg1C9MJJlAzRaiGjD5dm6GiT0M3kDtToZzDcZZBKqEYX/2Q6s11shT3/iice5JMtOFaLNt39bFV9A==
X-Received: by 10.112.143.40 with SMTP id sb8mr1352376lbb.83.1460467414773; Tue, 12 Apr 2016 06:23:34 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.25.40.136 with HTTP; Tue, 12 Apr 2016 06:22:54 -0700 (PDT)
X-Originating-IP: [71.233.41.235]
In-Reply-To: <EMEW3|bbf82c39a7afc0305d21ff1c5582540bs3BDUh03tjc|ecs.soton.ac.uk|22CF4C02-B728-4148-A86A-B42080728FE6@ecs.soton.ac.uk>
References: <m260vp7eke.wl%randy@psg.com> <570A6458.3050206@comcast.net> <m21t6d7c9t.wl%randy@psg.com> <570A67B4.3010206@comcast.net> <570AB3AF.2050401@gmail.com> <87twj99c6w.fsf@tops.chopps.org> <CAKe6YvMyp-DyeDwpPY6KYmbDbnpgnvVk_cUStnA32wmgDWcz3w@mail.gmail.com> <BBF5DDFE515C3946BC18D733B20DAD233A62AA18@XMB122CNC.rim.net> <20160411104519.GA19092@gsp.org> <3F48466D-390C-4C18-B958-732AE3E46FF1@gmail.com> <20160411223403.GA6743@gsp.org> <DDFE7AA1-4C07-4944-AECA-EA361A3A0B71@ecs.soton.ac.uk> <CAPt1N1nNo0=JSptQdWRZCFy1v-m6Q8NQy4WVGHtnRJuFZFmMig@mail.gmail.com> <EMEW3|9aaa87920b361e2e71efe9c7005e927cs3BChQ03tjc|ecs.soton.ac.uk|DDFE7AA1-4C07-4944-AECA-EA361A3A0B71@ecs.soton.ac.uk> <22CF4C02-B728-4148-A86A-B42080728FE6@ecs.soton.ac.uk> <CAPt1N1nucCAg99gVDWOHVE2up=2xK0Qm2Ud81hUhp4ryHRmwPA@mail.gmail.com> <EMEW3|bbf82c39a7afc0305d21ff1c5582540bs3BDUh03tjc|ecs.soton.ac.uk|22CF4C02-B728-4148-A86A-B42080728FE6@ecs.soton.ac.uk>
From: Ted Lemon <mellon@fugue.com>
Date: Tue, 12 Apr 2016 09:22:54 -0400
Message-ID: <CAPt1N1ncty=agWKaNnYFNBXnLQnxCzZMKe8S1zTUq7hQ3SLA1w@mail.gmail.com>
Subject: Re: Virtual IETFs (was: Re: Concerns about Singapore)
To: Tim Chown <tjc@ecs.soton.ac.uk>
Content-Type: multipart/alternative; boundary=089e011832ba76c4d80530499151
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/fTnhDf9CV0J9KubzC__V376vYH8>
Cc: ietf <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: Tue, 12 Apr 2016 13:23:39 -0000

--089e011832ba76c4d80530499151
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

The problem with a larger virtual interim is that it doesn't replace an
IETF, and so you're adding workload but not subtracting any workload.   I
don't see the point in that.

On Tue, Apr 12, 2016 at 8:30 AM, Tim Chown <tjc@ecs.soton.ac.uk> wrote:

> On 12 Apr 2016, at 12:49, Ted Lemon <mellon@fugue.com> wrote:
>
> Agree about Buenos Aires.   We already do excellent virtual interims--I
> think if your standard for whether we can do a virtual IETF is that virtu=
al
> interims work, we are already there.
>
> I think that if we want to test this idea, what we need to do is designat=
e
> some future IETF virtual _now_, and then start preparing, rather than say
> "oh, we should do a virtual" and then dither about when we might be ready=
.
>   We will never be so ready that a virtual IETF feels identical to an
> in-person IETF, so let's just abandon that idea and get started on making=
 a
> virtual IETF that, while different, is still a success.
>
>
> Sounds interesting, if something of a big leap to attempt. Is a larger
> wholly virtual, multiple WG interim meeting a next step then?
>
> Btw where do we get the virtual T-shirt? ;)
>
> Tim
>
>
> On Tue, Apr 12, 2016 at 7:43 AM, Tim Chown <tjc@ecs.soton.ac.uk> wrote:
>
>> Hi,
>>
>> To minimise the chances of a =E2=80=98Singapore=E2=80=99 happening again=
 it would seem
>> prudent to
>>
>> a) re-use previous successful meeting venues for the bulk of our meeting=
s
>> (say, every 5 in 6 meetings); this is one criteria for meeting selection=
 as
>> it stands anyway; that list might include venues like Prague, Berlin,
>> Vancouver, etc.; we=E2=80=99d need to be clear in what =E2=80=98successf=
ul=E2=80=99 means - the
>> meeting feedback forms provide one such mechanism;
>>
>> b) be transparent at an early stage about where new venues might be,
>> whether by country or city, so there is a fair chance for people to give
>> feedback; of course, how such feedback is weighed is an open question, b=
ut
>> at least it would be there, and the IAOC can then make a decision =E2=80=
=98eyes
>> wide open=E2=80=99.
>>
>> In such a system, Buenos Aires would have been a =E2=80=981 in 6=E2=80=
=99 venue. In that
>> light, I=E2=80=99d note that many people have said how much they enjoyed=
 Buenos
>> Aires as a meeting place. And while the IAOC probably feel rather down o=
ver
>> the comments about Singapore, they should be praised for going out on
>> something of a limb in making the Buenos Aires selection. (And I=E2=80=
=99d add that
>> the enthusiasm and helpfulness of the LACNIC hosts was also fantastic.)
>>
>> In terms of virtual meetings, I=E2=80=99d suggest we try to hold more in=
terim WG
>> meetings, some completely virtually, and learn how to make those better.=
 If
>> we can regularly hold good quality wholly virtual interim meetings, then=
 we
>> can consider whether the same technology might be used for a larger meet=
ing.
>>
>> Tim
>>
>> > On 12 Apr 2016, at 00:54, Ted Lemon <mellon@fugue.com> wrote:
>> >
>> > While I do not think it's true that we can entirely get away without
>> doing in-person meetings, I do agree with you that we can do better at
>> doing remote meetings.   Perhaps we should let this unfortunate event dr=
ive
>> us to make the attempt.
>> >
>> > If we were to attempt such a thing, how do you think it would work?
>>
>>
>
>

--089e011832ba76c4d80530499151
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">The problem with a larger virtual interim is that it doesn=
&#39;t replace an IETF, and so you&#39;re adding workload but not subtracti=
ng any workload. =C2=A0 I don&#39;t see the point in that.</div><div class=
=3D"gmail_extra"><br><div class=3D"gmail_quote">On Tue, Apr 12, 2016 at 8:3=
0 AM, Tim Chown <span dir=3D"ltr">&lt;<a href=3D"mailto:tjc@ecs.soton.ac.uk=
" target=3D"_blank">tjc@ecs.soton.ac.uk</a>&gt;</span> wrote:<br><blockquot=
e class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc sol=
id;padding-left:1ex"><div style=3D"word-wrap:break-word"><div><blockquote t=
ype=3D"cite"><div>On 12 Apr 2016, at 12:49, Ted Lemon &lt;<a href=3D"mailto=
:mellon@fugue.com" target=3D"_blank">mellon@fugue.com</a>&gt; wrote:</div><=
br><div><div dir=3D"ltr">Agree about Buenos Aires. =C2=A0 We already do exc=
ellent virtual interims--I think if your standard for whether we can do a v=
irtual IETF is that virtual interims work, we are already there.<div><br></=
div><div>I think that if we want to test this idea, what we need to do is d=
esignate some future IETF virtual _now_, and then start preparing, rather t=
han say &quot;oh, we should do a virtual&quot; and then dither about when w=
e might be ready. =C2=A0 We will never be so ready that a virtual IETF feel=
s identical to an in-person IETF, so let&#39;s just abandon that idea and g=
et started on making a virtual IETF that, while different, is still a succe=
ss.</div></div></div></blockquote><div><br></div><div>Sounds interesting, i=
f something of a big leap to attempt. Is a larger wholly virtual, multiple =
WG interim meeting a next step then?</div><div><br></div><div>Btw where do =
we get the virtual T-shirt? ;)</div><div><br></div>Tim</div><div><br><block=
quote type=3D"cite"><div><div class=3D"gmail_extra"><br><div class=3D"gmail=
_quote">On Tue, Apr 12, 2016 at 7:43 AM, Tim Chown <span dir=3D"ltr">&lt;<a=
 href=3D"mailto:tjc@ecs.soton.ac.uk" target=3D"_blank">tjc@ecs.soton.ac.uk<=
/a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:=
0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br>
<br>
To minimise the chances of a =E2=80=98Singapore=E2=80=99 happening again it=
 would seem prudent to<br>
<br>
a) re-use previous successful meeting venues for the bulk of our meetings (=
say, every 5 in 6 meetings); this is one criteria for meeting selection as =
it stands anyway; that list might include venues like Prague, Berlin, Vanco=
uver, etc.; we=E2=80=99d need to be clear in what =E2=80=98successful=E2=80=
=99 means - the meeting feedback forms provide one such mechanism;<br>
<br>
b) be transparent at an early stage about where new venues might be, whethe=
r by country or city, so there is a fair chance for people to give feedback=
; of course, how such feedback is weighed is an open question, but at least=
 it would be there, and the IAOC can then make a decision =E2=80=98eyes wid=
e open=E2=80=99.<br>
<br>
In such a system, Buenos Aires would have been a =E2=80=981 in 6=E2=80=99 v=
enue. In that light, I=E2=80=99d note that many people have said how much t=
hey enjoyed Buenos Aires as a meeting place. And while the IAOC probably fe=
el rather down over the comments about Singapore, they should be praised fo=
r going out on something of a limb in making the Buenos Aires selection. (A=
nd I=E2=80=99d add that the enthusiasm and helpfulness of the LACNIC hosts =
was also fantastic.)<br>
<br>
In terms of virtual meetings, I=E2=80=99d suggest we try to hold more inter=
im WG meetings, some completely virtually, and learn how to make those bett=
er. If we can regularly hold good quality wholly virtual interim meetings, =
then we can consider whether the same technology might be used for a larger=
 meeting.<br>
<span><font color=3D"#888888"><br>
Tim<br>
</font></span><div><div><br>
&gt; On 12 Apr 2016, at 00:54, Ted Lemon &lt;<a href=3D"mailto:mellon@fugue=
.com" target=3D"_blank">mellon@fugue.com</a>&gt; wrote:<br>
&gt;<br>
&gt; While I do not think it&#39;s true that we can entirely get away witho=
ut doing in-person meetings, I do agree with you that we can do better at d=
oing remote meetings.=C2=A0 =C2=A0Perhaps we should let this unfortunate ev=
ent drive us to make the attempt.<br>
&gt;<br>
&gt; If we were to attempt such a thing, how do you think it would work?<br=
>
<br>
</div></div></blockquote></div><br></div>
</div></blockquote></div><br></div></blockquote></div><br></div>

--089e011832ba76c4d80530499151--


From nobody Tue Apr 12 06:33:16 2016
Return-Path: <akatlas@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 4F29712DC24 for <ietf@ietfa.amsl.com>; Tue, 12 Apr 2016 06:33:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.699
X-Spam-Level: 
X-Spam-Status: No, score=-102.699 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, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] 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 DLxqOettMs4g for <ietf@ietfa.amsl.com>; Tue, 12 Apr 2016 06:33:13 -0700 (PDT)
Received: from mail-ob0-x22e.google.com (mail-ob0-x22e.google.com [IPv6:2607:f8b0:4003:c01::22e]) (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 203E612E06D for <ietf@ietf.org>; Tue, 12 Apr 2016 06:33:13 -0700 (PDT)
Received: by mail-ob0-x22e.google.com with SMTP id bg3so11379690obb.1 for <ietf@ietf.org>; Tue, 12 Apr 2016 06:33:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=BiorpVctUVyI1dQwbG3Z2CluqLhSBhVyBUkPBB0BXQc=; b=mqgJeA7yWg8i2FZb3mbvXpzB993lNOEdRHM/YbBw/5sNRzGZQzsQpr3xztET6WowoA 2kS9ncvjIzyqZhKJF0x6MEa1g8+V5i7AoPPX03H0W/20BnSmPZqTMOeajAM0FXRJx7KO lIYa27tlGtIlCUMaXHeMp22jGYAGbo2+grPmwT69xXBOTjy76wXWeo3PIbmN9dKi+9nC LXUk440C3+UkFeLTjVSvYdQ+UvmPQn59La+Uecb2zi2uMR50T1wzaT2wFdrp4p5YP900 3gYGBMtFx9NHLwrFJABrYlKiVYzSETmZ4PmJsWyTSOIsOF66ICRWklD9rUmRMgK3qjLg F2Xw==
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:date :message-id:subject:from:to:cc; bh=BiorpVctUVyI1dQwbG3Z2CluqLhSBhVyBUkPBB0BXQc=; b=heWdUItLDb5KhWpagZV8NHrLtN+wtwZMyUz4bzZLXx7yr7bNX7hPVRqVU4F3B8W5Pz APYnk6vAtwBhhmEIaFe20p5RgtY6HP4EAw1470ZapmhBBhOtqzKDtQ2lkIpJ7i7lHB3j d22EGCEjMozJ2F612w/8lpoSWFSt1Q2v/N1q1A6nOD8Uga63BqcsY7mE26/qapxWq1MC COpDkiM+x9dLVCkc9zetTEFkW2cHEyGERKO2dqHhZ3GEkGND4sNFdDtxuNIJw5IMIay3 HZj9qFRALU4/2efKMJxaU6uLLZZAIVuqQL+wWoQCuR/WB80Rz+CGcpMgrpU0gq0J/Lh6 vGiA==
X-Gm-Message-State: AOPr4FVWSfBofg7uQRT8fJlpKUT6N/dO0rEyuIxpes9kEFnkpS+C0vImQj0bdhxHMtCPRGzaNXFHeiSSZOF7RQ==
MIME-Version: 1.0
X-Received: by 10.60.56.170 with SMTP id b10mr378480oeq.27.1460467992517; Tue, 12 Apr 2016 06:33:12 -0700 (PDT)
Received: by 10.60.115.168 with HTTP; Tue, 12 Apr 2016 06:33:12 -0700 (PDT)
In-Reply-To: <CAPt1N1ncty=agWKaNnYFNBXnLQnxCzZMKe8S1zTUq7hQ3SLA1w@mail.gmail.com>
References: <m260vp7eke.wl%randy@psg.com> <570A6458.3050206@comcast.net> <m21t6d7c9t.wl%randy@psg.com> <570A67B4.3010206@comcast.net> <570AB3AF.2050401@gmail.com> <87twj99c6w.fsf@tops.chopps.org> <CAKe6YvMyp-DyeDwpPY6KYmbDbnpgnvVk_cUStnA32wmgDWcz3w@mail.gmail.com> <BBF5DDFE515C3946BC18D733B20DAD233A62AA18@XMB122CNC.rim.net> <20160411104519.GA19092@gsp.org> <3F48466D-390C-4C18-B958-732AE3E46FF1@gmail.com> <20160411223403.GA6743@gsp.org> <DDFE7AA1-4C07-4944-AECA-EA361A3A0B71@ecs.soton.ac.uk> <CAPt1N1nNo0=JSptQdWRZCFy1v-m6Q8NQy4WVGHtnRJuFZFmMig@mail.gmail.com> <EMEW3|9aaa87920b361e2e71efe9c7005e927cs3BChQ03tjc|ecs.soton.ac.uk|DDFE7AA1-4C07-4944-AECA-EA361A3A0B71@ecs.soton.ac.uk> <22CF4C02-B728-4148-A86A-B42080728FE6@ecs.soton.ac.uk> <CAPt1N1nucCAg99gVDWOHVE2up=2xK0Qm2Ud81hUhp4ryHRmwPA@mail.gmail.com> <EMEW3|bbf82c39a7afc0305d21ff1c5582540bs3BDUh03tjc|ecs.soton.ac.uk|22CF4C02-B728-4148-A86A-B42080728FE6@ecs.soton.ac.uk> <CAPt1N1ncty=agWKaNnYFNBXnLQnxCzZMKe8S1zTUq7hQ3SLA1w@mail.gmail.com>
Date: Tue, 12 Apr 2016 09:33:12 -0400
Message-ID: <CAG4d1rd1x=gbj3OS2t_N8njOPxnbbCeS9T+tKcFuTgShetPFZA@mail.gmail.com>
Subject: Re: Virtual IETFs (was: Re: Concerns about Singapore)
From: Alia Atlas <akatlas@gmail.com>
To: Ted Lemon <mellon@fugue.com>
Content-Type: multipart/alternative; boundary=089e013a0ec2e668e0053049b370
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/VK_HUJh72ujbxxuo_frliu7ejiY>
Cc: Tim Chown <tjc@ecs.soton.ac.uk>, ietf <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: Tue, 12 Apr 2016 13:33:15 -0000

--089e013a0ec2e668e0053049b370
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Tue, Apr 12, 2016 at 9:22 AM, Ted Lemon <mellon@fugue.com> wrote:

> The problem with a larger virtual interim is that it doesn't replace an
> IETF, and so you're adding workload but not subtracting any workload.   I
> don't see the point in that.
>

It clocks those working groups at a higher rate.  Many people find it
easier to prioritize IETF work when there are specific deadlines or a loss
of face if work isn't done.

While the IETF determines consensus on mailing lists, there has been a
strong tendency in the last decade to focus on the physical meetings for
the next deadline, to have necessary talks, and so on.   I personally feel
that it is important to push back on this.

Discussing an issue on the mailing list suffers from people losing state on
the issue being talked about - for instance:
     Day 1: Alice reviews a draft and posts her review with a technical
point to consider.  Bob, an author, sees the email but is
                in the midst of a day-job priority.
     Day 4: Bob reads the email, rereads the draft section, and suggests a
fix.  Alice sees email, but is focused on day-job.
     Day 8: Alice refreshes her memory and responds with a point that
wasn't handled.
etc.

A benefit of virtual interims is that folks try to be up to speed and that
conversational back and forth can happen.
We do the same thing - aspirationally - on WGLCs on the mailing lists where
a two-week period is set aside to focus on a
particular draft.

Regards,
Alia



> On Tue, Apr 12, 2016 at 8:30 AM, Tim Chown <tjc@ecs.soton.ac.uk> wrote:
>
>> On 12 Apr 2016, at 12:49, Ted Lemon <mellon@fugue.com> wrote:
>>
>> Agree about Buenos Aires.   We already do excellent virtual interims--I
>> think if your standard for whether we can do a virtual IETF is that virt=
ual
>> interims work, we are already there.
>>
>> I think that if we want to test this idea, what we need to do is
>> designate some future IETF virtual _now_, and then start preparing, rath=
er
>> than say "oh, we should do a virtual" and then dither about when we migh=
t
>> be ready.   We will never be so ready that a virtual IETF feels identica=
l
>> to an in-person IETF, so let's just abandon that idea and get started on
>> making a virtual IETF that, while different, is still a success.
>>
>>
>> Sounds interesting, if something of a big leap to attempt. Is a larger
>> wholly virtual, multiple WG interim meeting a next step then?
>>
>> Btw where do we get the virtual T-shirt? ;)
>>
>> Tim
>>
>>
>> On Tue, Apr 12, 2016 at 7:43 AM, Tim Chown <tjc@ecs.soton.ac.uk> wrote:
>>
>>> Hi,
>>>
>>> To minimise the chances of a =E2=80=98Singapore=E2=80=99 happening agai=
n it would seem
>>> prudent to
>>>
>>> a) re-use previous successful meeting venues for the bulk of our
>>> meetings (say, every 5 in 6 meetings); this is one criteria for meeting
>>> selection as it stands anyway; that list might include venues like Prag=
ue,
>>> Berlin, Vancouver, etc.; we=E2=80=99d need to be clear in what =E2=80=
=98successful=E2=80=99 means -
>>> the meeting feedback forms provide one such mechanism;
>>>
>>> b) be transparent at an early stage about where new venues might be,
>>> whether by country or city, so there is a fair chance for people to giv=
e
>>> feedback; of course, how such feedback is weighed is an open question, =
but
>>> at least it would be there, and the IAOC can then make a decision =E2=
=80=98eyes
>>> wide open=E2=80=99.
>>>
>>> In such a system, Buenos Aires would have been a =E2=80=981 in 6=E2=80=
=99 venue. In that
>>> light, I=E2=80=99d note that many people have said how much they enjoye=
d Buenos
>>> Aires as a meeting place. And while the IAOC probably feel rather down =
over
>>> the comments about Singapore, they should be praised for going out on
>>> something of a limb in making the Buenos Aires selection. (And I=E2=80=
=99d add that
>>> the enthusiasm and helpfulness of the LACNIC hosts was also fantastic.)
>>>
>>> In terms of virtual meetings, I=E2=80=99d suggest we try to hold more i=
nterim WG
>>> meetings, some completely virtually, and learn how to make those better=
. If
>>> we can regularly hold good quality wholly virtual interim meetings, the=
n we
>>> can consider whether the same technology might be used for a larger mee=
ting.
>>>
>>> Tim
>>>
>>> > On 12 Apr 2016, at 00:54, Ted Lemon <mellon@fugue.com> wrote:
>>> >
>>> > While I do not think it's true that we can entirely get away without
>>> doing in-person meetings, I do agree with you that we can do better at
>>> doing remote meetings.   Perhaps we should let this unfortunate event d=
rive
>>> us to make the attempt.
>>> >
>>> > If we were to attempt such a thing, how do you think it would work?
>>>
>>>
>>
>>
>

--089e013a0ec2e668e0053049b370
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On T=
ue, Apr 12, 2016 at 9:22 AM, Ted Lemon <span dir=3D"ltr">&lt;<a href=3D"mai=
lto:mellon@fugue.com" target=3D"_blank">mellon@fugue.com</a>&gt;</span> wro=
te:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-=
left:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr">The problem with a l=
arger virtual interim is that it doesn&#39;t replace an IETF, and so you&#3=
9;re adding workload but not subtracting any workload. =C2=A0 I don&#39;t s=
ee the point in that.</div></blockquote><div><br></div><div>It clocks those=
 working groups at a higher rate.=C2=A0 Many people find it easier to prior=
itize IETF work when there are specific deadlines or a loss of face if work=
 isn&#39;t done.</div><div><br></div><div>While the IETF determines consens=
us on mailing lists, there has been a strong tendency in the last decade to=
 focus on the physical meetings for the next deadline, to have necessary ta=
lks, and so on. =C2=A0 I personally feel that it is important to push back =
on this.</div><div><br></div><div>Discussing an issue on the mailing list s=
uffers from people losing state on the issue being talked about - for insta=
nce:</div><div>=C2=A0 =C2=A0 =C2=A0Day 1: Alice reviews a draft and posts h=
er review with a technical point to consider.=C2=A0 Bob, an author, sees th=
e email but is=C2=A0</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 in the midst of a day-job priority.</div><div>=C2=A0 =C2=A0 =
=C2=A0Day 4: Bob reads the email, rereads the draft section, and suggests a=
 fix.=C2=A0 Alice sees email, but is focused on day-job.</div><div>=C2=A0 =
=C2=A0 =C2=A0Day 8: Alice refreshes her memory and responds with a point th=
at wasn&#39;t handled.</div><div>etc.</div><div><br></div><div>A benefit of=
 virtual interims is that folks try to be up to speed and that conversation=
al back and forth can happen.</div><div>We do the same thing - aspirational=
ly - on WGLCs on the mailing lists where a two-week period is set aside to =
focus on a=C2=A0</div><div>particular draft.</div><div><br></div><div>Regar=
ds,</div><div>Alia</div><div><br></div><div>=C2=A0</div><blockquote class=
=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padd=
ing-left:1ex"><div class=3D"HOEnZb"><div class=3D"h5"><div class=3D"gmail_e=
xtra"><div class=3D"gmail_quote">On Tue, Apr 12, 2016 at 8:30 AM, Tim Chown=
 <span dir=3D"ltr">&lt;<a href=3D"mailto:tjc@ecs.soton.ac.uk" target=3D"_bl=
ank">tjc@ecs.soton.ac.uk</a>&gt;</span> wrote:<br><blockquote class=3D"gmai=
l_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left=
:1ex"><div style=3D"word-wrap:break-word"><div><blockquote type=3D"cite"><d=
iv>On 12 Apr 2016, at 12:49, Ted Lemon &lt;<a href=3D"mailto:mellon@fugue.c=
om" target=3D"_blank">mellon@fugue.com</a>&gt; wrote:</div><br><div><div di=
r=3D"ltr">Agree about Buenos Aires. =C2=A0 We already do excellent virtual =
interims--I think if your standard for whether we can do a virtual IETF is =
that virtual interims work, we are already there.<div><br></div><div>I thin=
k that if we want to test this idea, what we need to do is designate some f=
uture IETF virtual _now_, and then start preparing, rather than say &quot;o=
h, we should do a virtual&quot; and then dither about when we might be read=
y. =C2=A0 We will never be so ready that a virtual IETF feels identical to =
an in-person IETF, so let&#39;s just abandon that idea and get started on m=
aking a virtual IETF that, while different, is still a success.</div></div>=
</div></blockquote><div><br></div><div>Sounds interesting, if something of =
a big leap to attempt. Is a larger wholly virtual, multiple WG interim meet=
ing a next step then?</div><div><br></div><div>Btw where do we get the virt=
ual T-shirt? ;)</div><div><br></div>Tim</div><div><br><blockquote type=3D"c=
ite"><div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Tue,=
 Apr 12, 2016 at 7:43 AM, Tim Chown <span dir=3D"ltr">&lt;<a href=3D"mailto=
:tjc@ecs.soton.ac.uk" target=3D"_blank">tjc@ecs.soton.ac.uk</a>&gt;</span> =
wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bord=
er-left:1px #ccc solid;padding-left:1ex">Hi,<br>
<br>
To minimise the chances of a =E2=80=98Singapore=E2=80=99 happening again it=
 would seem prudent to<br>
<br>
a) re-use previous successful meeting venues for the bulk of our meetings (=
say, every 5 in 6 meetings); this is one criteria for meeting selection as =
it stands anyway; that list might include venues like Prague, Berlin, Vanco=
uver, etc.; we=E2=80=99d need to be clear in what =E2=80=98successful=E2=80=
=99 means - the meeting feedback forms provide one such mechanism;<br>
<br>
b) be transparent at an early stage about where new venues might be, whethe=
r by country or city, so there is a fair chance for people to give feedback=
; of course, how such feedback is weighed is an open question, but at least=
 it would be there, and the IAOC can then make a decision =E2=80=98eyes wid=
e open=E2=80=99.<br>
<br>
In such a system, Buenos Aires would have been a =E2=80=981 in 6=E2=80=99 v=
enue. In that light, I=E2=80=99d note that many people have said how much t=
hey enjoyed Buenos Aires as a meeting place. And while the IAOC probably fe=
el rather down over the comments about Singapore, they should be praised fo=
r going out on something of a limb in making the Buenos Aires selection. (A=
nd I=E2=80=99d add that the enthusiasm and helpfulness of the LACNIC hosts =
was also fantastic.)<br>
<br>
In terms of virtual meetings, I=E2=80=99d suggest we try to hold more inter=
im WG meetings, some completely virtually, and learn how to make those bett=
er. If we can regularly hold good quality wholly virtual interim meetings, =
then we can consider whether the same technology might be used for a larger=
 meeting.<br>
<span><font color=3D"#888888"><br>
Tim<br>
</font></span><div><div><br>
&gt; On 12 Apr 2016, at 00:54, Ted Lemon &lt;<a href=3D"mailto:mellon@fugue=
.com" target=3D"_blank">mellon@fugue.com</a>&gt; wrote:<br>
&gt;<br>
&gt; While I do not think it&#39;s true that we can entirely get away witho=
ut doing in-person meetings, I do agree with you that we can do better at d=
oing remote meetings.=C2=A0 =C2=A0Perhaps we should let this unfortunate ev=
ent drive us to make the attempt.<br>
&gt;<br>
&gt; If we were to attempt such a thing, how do you think it would work?<br=
>
<br>
</div></div></blockquote></div><br></div>
</div></blockquote></div><br></div></blockquote></div><br></div>
</div></div></blockquote></div><br></div></div>

--089e013a0ec2e668e0053049b370--


From nobody Tue Apr 12 06:35:21 2016
Return-Path: <mellon@fugue.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 CD60B12DECD for <ietf@ietfa.amsl.com>; Tue, 12 Apr 2016 06:35:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.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 XHzTLlbGMbFb for <ietf@ietfa.amsl.com>; Tue, 12 Apr 2016 06:35:19 -0700 (PDT)
Received: from mail-lf0-x22b.google.com (mail-lf0-x22b.google.com [IPv6:2a00:1450:4010:c07::22b]) (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 DD38A12D56F for <ietf@ietf.org>; Tue, 12 Apr 2016 06:35:18 -0700 (PDT)
Received: by mail-lf0-x22b.google.com with SMTP id g184so25385205lfb.3 for <ietf@ietf.org>; Tue, 12 Apr 2016 06:35:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=ouxyCbDMpx1opAhLgI+5Q4Tn30Vu0X0vNlC8qmh+or0=; b=tcca6q7Tr1gZayblwHPXUOq4Bg3iIBnm/xxN1k2hXy+HkWuOaPn+yKIh+xv79PnjGV PUCk6ys2x2bxo/13W6m1H3aSrA5jHZqQYhLhucBgJQHYjqisTxdN7xmGwkFpF+X6v02i R6wXjSGfcaYSeC86Otm8LGDnkETYTN7Oi7p7Mdjq12jEAby/DyQAJsQ8B+/+m9d7tTfT /nkuMkAiua07wdqSWFqsrMSDkFJ/aaa63lHc5/XcUTl/CaBmSy6+H4/szWowIWb1iuc1 bb6kKaN+URkxMgi8lZyrz2StpxTJr14BCshGiuQkvGSIjI/e79VmLFYpxC6w06rLIamF aDEw==
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=ouxyCbDMpx1opAhLgI+5Q4Tn30Vu0X0vNlC8qmh+or0=; b=dRskYrg3yfYTsTxHXNSGLSvRzb66YJpXAcn6TBzRvieCfb+TNxhQTBxX62aPIL2MGP FMuBYW5HsPw5FUCnNYr5V2RZGYh0OYk8SWuuUiOIWbhUenzFv6e0+6plxqbzZa8A2Drc ajo2gnUBYUzvIdCYNQ1rEPuEletWMThloafcVMJK0d8s1KoBgazMZ+R1mFfnL4Xs+gXg iDu4nn7pYSCq8laWZA58TIlV3WousTdXPQxbtD6WNsTWnum9LDCpvvOlu5EID6bufdXH B9SotPTDi8BKwc4HOIc9RdGexf/W6DK5OyRNkzu9Pa/ilCWcvGa57wBtIcFmhDrcum45 3ypA==
X-Gm-Message-State: AOPr4FWvEPZJixfm/06YB9Gw7YSTBfS6y3VDcVjr/qeSz577qRQG1Qj2zTn5TBpOsenBRIIZMcLq7Uc9OCpE9g==
X-Received: by 10.25.143.212 with SMTP id r203mr1428797lfd.119.1460468117070;  Tue, 12 Apr 2016 06:35:17 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.25.40.136 with HTTP; Tue, 12 Apr 2016 06:34:37 -0700 (PDT)
X-Originating-IP: [71.233.41.235]
In-Reply-To: <570CF594.5070509@pi.nu>
References: <m260vp7eke.wl%randy@psg.com> <570A6458.3050206@comcast.net> <m21t6d7c9t.wl%randy@psg.com> <570A67B4.3010206@comcast.net> <570AB3AF.2050401@gmail.com> <87twj99c6w.fsf@tops.chopps.org> <CAKe6YvMyp-DyeDwpPY6KYmbDbnpgnvVk_cUStnA32wmgDWcz3w@mail.gmail.com> <BBF5DDFE515C3946BC18D733B20DAD233A62AA18@XMB122CNC.rim.net> <20160411104519.GA19092@gsp.org> <3F48466D-390C-4C18-B958-732AE3E46FF1@gmail.com> <20160411223403.GA6743@gsp.org> <CAPt1N1nNo0=JSptQdWRZCFy1v-m6Q8NQy4WVGHtnRJuFZFmMig@mail.gmail.com> <CAKr6gn1KmNcgNwbPHZWB2aJQAuchz4eB7gxJhV2Dsbc1Z50kDw@mail.gmail.com> <CAPt1N1mWjg_-525avYJ4PnSECYQrtpVFJCXPfH=PryJ8q0vy4Q@mail.gmail.com> <A684A3C4-7161-49F5-919E-A5F948A3F316@ecs.soton.ac.uk> <EMEW3|d5cb2cb80712b3716e1ab4e2a54c9430s3BCG403tjc|ecs.soton.ac.uk|A684A3C4-7161-49F5-919E-A5F948A3F316@ecs.soton.ac.uk> <570CF594.5070509@pi.nu>
From: Ted Lemon <mellon@fugue.com>
Date: Tue, 12 Apr 2016 09:34:37 -0400
Message-ID: <CAPt1N1m_gbTMdxUfqgUDdKfw56E7Exfo6QU2GuxxueN_gPFCwQ@mail.gmail.com>
Subject: Re: Concerns about Singapore
To: Loa Andersson <loa@pi.nu>
Content-Type: multipart/alternative; boundary=001a1140225452ff67053049bb45
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/H67gTvRmPbhaXY-AkqD1GcHlNUs>
Cc: ietf <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: Tue, 12 Apr 2016 13:35:21 -0000

--001a1140225452ff67053049bb45
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

I think that at this point the question of what we can do to address the
Singapore problem is in the hands of the IAOC, which has indicated a
willingness to explore going even further than Ted asked them to in
addressing the problem.   Ted asked them to not bring their families to
Singapore in solidarity with him, since he doesn't feel safe bringing his
family.   The IAOC has said they are looking into how difficult it would be
to actually move IETF 100 to a different country.   So I don't think
there's anything for us to discuss here, unless you are a member of the
LGBTQ+ community and have something to add about how you think Singapore
should be handled.

Your point about derailment makes sense, though--this is definitely a
separate issue from the "virtual IETF" issue.

On Tue, Apr 12, 2016 at 9:18 AM, Loa Andersson <loa@pi.nu> wrote:

> Folks,
>
> On 2016-04-12 19:15, Tim Chown wrote:
>
>> On 12 Apr 2016, at 01:50, Ted Lemon <mellon@fugue.com> wrote:
>>>
>>> The only thing you mentioned that can't be done with existing
>>> conferencing software is hums, and I'm sure we could figure out a way t=
o
>>> make that work.  It's not rocket science.   Chairs who judge consensus =
by
>>> looking at the room aren't following IETF process--consensus is judged =
on
>>> the mailing list.  Hums are useful for figuring out why we _don't_ have
>>> consensus, and for _getting_ to consensus, but if you were to judge
>>> consensus by hums or a show of hands, then you'd be taking a vote, woul=
dn't
>>> you?
>>>
>>
>> Meetecho has a =E2=80=98hum=E2=80=99 button, which throws =E2=80=98hmmmm=
mm=E2=80=99 into the jabber room
>> for the WG. I did see it used, once.
>>
>
> Let me return to the start of this discussion.
>
> It seems to me that the LGBTQ peoples concern about a meeting in
> Singapore is real, at least it is perceived to be real.
>
> I don't think anything that is within our power to do can change this
> perception.
>
> Thus we need to take this seriously, the concerns is about our upcoming
> meeting in Singapore. That should be our focus.
>
> /Loa
>
>
>> Tim
>>
>>
>

--001a1140225452ff67053049bb45
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>I think that at this point the question of what we ca=
n do to address the Singapore problem is in the hands of the IAOC, which ha=
s indicated a willingness to explore going even further than Ted asked them=
 to in addressing the problem. =C2=A0 Ted asked them to not bring their fam=
ilies to Singapore in solidarity with him, since he doesn&#39;t feel safe b=
ringing his family. =C2=A0 The IAOC has said they are looking into how diff=
icult it would be to actually move IETF 100 to a different country. =C2=A0 =
So I don&#39;t think there&#39;s anything for us to discuss here, unless yo=
u are a member of the LGBTQ+ community and have something to add about how =
you think Singapore should be handled.</div><div><br>Your point about derai=
lment makes sense, though--this is definitely a separate issue from the &qu=
ot;virtual IETF&quot; issue.</div></div><div class=3D"gmail_extra"><br><div=
 class=3D"gmail_quote">On Tue, Apr 12, 2016 at 9:18 AM, Loa Andersson <span=
 dir=3D"ltr">&lt;<a href=3D"mailto:loa@pi.nu" target=3D"_blank">loa@pi.nu</=
a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0=
 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Folks,<span class=3D=
""><br>
<br>
On 2016-04-12 19:15, Tim Chown wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><blockquote class=3D"gmail_quote" style=3D"m=
argin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On 12 Apr 2016, at 01:50, Ted Lemon &lt;<a href=3D"mailto:mellon@fugue.com"=
 target=3D"_blank">mellon@fugue.com</a>&gt; wrote:<br>
<br>
The only thing you mentioned that can&#39;t be done with existing conferenc=
ing software is hums, and I&#39;m sure we could figure out a way to make th=
at work.=C2=A0 It&#39;s not rocket science.=C2=A0 =C2=A0Chairs who judge co=
nsensus by looking at the room aren&#39;t following IETF process--consensus=
 is judged on the mailing list.=C2=A0 Hums are useful for figuring out why =
we _don&#39;t_ have consensus, and for _getting_ to consensus, but if you w=
ere to judge consensus by hums or a show of hands, then you&#39;d be taking=
 a vote, wouldn&#39;t you?<br>
</blockquote>
<br>
Meetecho has a =E2=80=98hum=E2=80=99 button, which throws =E2=80=98hmmmmmm=
=E2=80=99 into the jabber room for the WG. I did see it used, once.<br>
</blockquote>
<br></span>
Let me return to the start of this discussion.<br>
<br>
It seems to me that the LGBTQ peoples concern about a meeting in<br>
Singapore is real, at least it is perceived to be real.<br>
<br>
I don&#39;t think anything that is within our power to do can change this<b=
r>
perception.<br>
<br>
Thus we need to take this seriously, the concerns is about our upcoming<br>
meeting in Singapore. That should be our focus.<br>
<br>
/Loa<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<br>
Tim<br>
<br>
</blockquote>
<br>
</blockquote></div><br></div>

--001a1140225452ff67053049bb45--


From nobody Tue Apr 12 06:37:09 2016
Return-Path: <chopps@chopps.org>
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 0DC9712DF41 for <ietf@ietfa.amsl.com>; Tue, 12 Apr 2016 06:37:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.896
X-Spam-Level: 
X-Spam-Status: No, score=-2.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.996] 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 yZ8By85NECHW for <ietf@ietfa.amsl.com>; Tue, 12 Apr 2016 06:37:06 -0700 (PDT)
Received: from smtp.chopps.org (smtp.chopps.org [54.88.81.56]) by ietfa.amsl.com (Postfix) with ESMTP id AA84312DDA2 for <ietf@ietf.org>; Tue, 12 Apr 2016 06:37:06 -0700 (PDT)
Received: from tops.chopps.org (24-247-68-31.dhcp.trcy.mi.charter.com [24.247.68.31]) (using TLSv1.2 with cipher AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by smtp.chopps.org (Postfix) with ESMTPSA id 20FDA6117B; Tue, 12 Apr 2016 13:37:06 +0000 (UTC)
References: <570AB3AF.2050401@gmail.com> <87twj99c6w.fsf@tops.chopps.org> <CAKe6YvMyp-DyeDwpPY6KYmbDbnpgnvVk_cUStnA32wmgDWcz3w@mail.gmail.com> <BBF5DDFE515C3946BC18D733B20DAD233A62AA18@XMB122CNC.rim.net> <20160411104519.GA19092@gsp.org> <3F48466D-390C-4C18-B958-732AE3E46FF1@gmail.com> <20160411223403.GA6743@gsp.org> <87twj7eon7.fsf@tops.chopps.org> <20160412110839.GA20488@gsp.org> <8760vn82f2.fsf@tops.chopps.org> <20160412124639.GA27223@gsp.org>
User-agent: mu4e 0.9.16; emacs 24.5.1
From: <chopps@chopps.org>
To: Rich Kulawiec <rsk@gsp.org>
Subject: Re: Remote only meetings? [Re: Concerns about Singapore]
In-reply-to: <20160412124639.GA27223@gsp.org>
Date: Tue, 12 Apr 2016 09:37:04 -0400
Message-ID: <87fuurgd8f.fsf@tops.chopps.org>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature"
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/MC9qx96UvjVDL7usDL2V2HBrPxs>
Cc: 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: Tue, 12 Apr 2016 13:37:08 -0000

--=-=-=
Content-Type: text/plain


Rich Kulawiec <rsk@gsp.org> writes:

> On Tue, Apr 12, 2016 at 07:57:53AM -0400, chopps@chopps.org wrote:
>> Your suggestion of not having them would subtract value from the process
>> though. I don't see the win.
>
> The win is that all of the time and effort and expense (all of which
> are finite resources) that go into those could be directed elsewhere.

The meetings and their fees are income positive, they aren't a drain on
resource, the opposite in fact.

> These meetings select for a highly limited (by circumstance, by necessity,
> and by choice) subset.  And once upon a time, when the 'net was much
> younger and more limited in terms of geography and scope, that might
> have been alright, because the subset mapped fairly well onto the larger
> set of people involved in networking.  But that's no longer true.
> And the difficulties/expense of travel are only going to get worse
> for the forseeable future: they're not going to get better.

I think it would be useful to get some real data to measure exactly how
highly limited that subset of people are. Perhaps as a simple first
shot we could take email sent to IETF working group mailing lists over
the last year, and cross reference that against the registrations lists
of the last 3 IETFs and see what percentage of people doing IETF work
cannot or choose not to attend the on-site meetings?

Thanks,
Chris.


>
> ---rsk


--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQIcBAEBCgAGBQJXDPoAAAoJEC4dgw7XuDAlAzwP/0c4rGROJJKR2sGxLdjE6eeB
/iKVoSopbm1Vz02V0hq+APsbpU2BMjnjSGeFimdk/PabvlHtk15YkOKrxk3Yboqh
OxJ3HRH2rLJQoyAajcV75qv0yLC1KkdYEeG65RK2Kf3JOxk1JxsOQSuUTLNfeJV5
z7Jw7UN4we/KElXMxjWfHM2zXoqNw5iHHnt3Nta9qFCMdbq+MhqvE6oABNxIaNfU
27YIitHNr3EWHdo7yyG1+Tph2ytFPTUNHEAZJ773ooqvKwiG2gQmrdAHTO0RTt9J
BIH/F9zUlXSqMyyjoJsFmTNBTC7vSOkc+ANI70AYt9zrHeC70P13mVlwPyHtomII
3+BPQn+Ry8AECM1AYEAk895f22Z3QxXw2bgXryGg+7wa785Eo9WP0ioT2vgPPedk
DLGrtpVNG/bLdUAyoJfv4lDNO2Ee3kacAB/i23kaeA2ssRUP8aHseL9XDmgnRMvG
nojuC0FF/mivtPwtDVpCZrQ8wXnYRjgoKK2uZ2j7zbU5Ld8GOExg0QpHHBAZVKTQ
6aoK2wfTsTIjy9hB70s8y9SSi4j6EXU5VflhngIdvW9sIob9cqYE9+8vBIRbXE55
AbtbBvNwuCXB9bGLIRP64Nerk8SrMERY0DeSzm6iQCuca6miUQCzOBn2pq8AySZD
S8Os869mct78RRKYnjwa
=vF1O
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Tue Apr 12 06:42:36 2016
Return-Path: <tjc@ecs.soton.ac.uk>
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 D88B112E1ED for <ietf@ietfa.amsl.com>; Tue, 12 Apr 2016 06:42:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.306
X-Spam-Level: 
X-Spam-Status: No, score=-4.306 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.996, SPF_NEUTRAL=0.779, T_DKIM_INVALID=0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=ecs.soton.ac.uk
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 ZBhcC0Wi81x7 for <ietf@ietfa.amsl.com>; Tue, 12 Apr 2016 06:42:30 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [IPv6:2001:630:d0:f102::25e]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 51AC712DBD1 for <ietf@ietf.org>; Tue, 12 Apr 2016 06:42:30 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (localhost [127.0.0.1]) by falcon.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id u3CDgQw9009832; Tue, 12 Apr 2016 14:42:26 +0100
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk u3CDgQw9009832
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=201304; t=1460468547; bh=Km7XyDgtM98+dEwNDRFS3feLmZ0=; h=Mime-Version:Subject:From:In-Reply-To:Date:Cc:References:To; b=SGch46TjukrouBAaaQFR5yndOPhPN2UqdK3gUoez9jUITo1CQzBO1Qoga0DmXWyjv ExekNDEChoiIfs75iEBhAt4/puMqFgatHJFz5r7V1ged1lV3KrRYffaxE7tzgAyvSR JHjlAAwk+ZZTiZaHDWb/YKysu/2jxOat5qcXqlS8=
Received: from gander.ecs.soton.ac.uk (gander.ecs.soton.ac.uk [2001:630:d0:f102::25d]) by falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [2001:630:d0:f102::25e]) envelope-from <tjc@ecs.soton.ac.uk> with ESMTP (valid=N/A) id s3BEgQ3219207736ur ret-id none; Tue, 12 Apr 2016 14:42:26 +0100
Received: from 20010a88d51011.ipv6.customer.clara.net (20010a88d51011.ipv6.customer.clara.net [IPv6:2001:a88:d510:1101:a93e:5914:9e35:ffe3] (may be forged)) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id u3CDgLp7032678 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 12 Apr 2016 14:42:22 +0100
Content-Type: multipart/alternative; boundary="Apple-Mail=_C5E359DE-2DE2-4010-BCA2-ADED1410451E"
Mime-Version: 1.0 (Mac OS X Mail 9.2 \(3112\))
Subject: Re: Virtual IETFs (was: Re: Concerns about Singapore)
From: Tim Chown <tjc@ecs.soton.ac.uk>
In-Reply-To: <CAPt1N1ncty=agWKaNnYFNBXnLQnxCzZMKe8S1zTUq7hQ3SLA1w@mail.gmail.com>
Date: Tue, 12 Apr 2016 14:42:20 +0100
Message-ID: <EMEW3|97bceb9b22356ec71621ead633105fcfs3BEgQ03tjc|ecs.soton.ac.uk|DDC5F6F9-5ECA-455C-B435-E8B6784D6695@ecs.soton.ac.uk>
References: <m260vp7eke.wl%randy@psg.com> <570A6458.3050206@comcast.net> <m21t6d7c9t.wl%randy@psg.com> <570A67B4.3010206@comcast.net> <570AB3AF.2050401@gmail.com> <87twj99c6w.fsf@tops.chopps.org> <CAKe6YvMyp-DyeDwpPY6KYmbDbnpgnvVk_cUStnA32wmgDWcz3w@mail.gmail.com> <BBF5DDFE515C3946BC18D733B20DAD233A62AA18@XMB122CNC.rim.net> <20160411104519.GA19092@gsp.org> <3F48466D-390C-4C18-B958-732AE3E46FF1@gmail.com> <20160411223403.GA6743@gsp.org> <DDFE7AA1-4C07-4944-AECA-EA361A3A0B71@ecs.soton.ac.uk> <CAPt1N1nNo0=JSptQdWRZCFy1v-m6Q8NQy4WVGHtnRJuFZFmMig@mail.gmail.com> <EMEW3|9aaa87920b361e2e71efe9c7005e927cs3BChQ03tjc|ecs.soton.ac.uk|DDFE7AA1-4C07-4944-AECA-EA361A3A0B71@ecs.soton.ac.uk> <22CF4C02-B728-4148-A86A-B42080728FE6@ecs.soton.ac.uk> <CAPt1N1nucCAg99gVDWOHVE2up=2xK0Qm2Ud81hUhp4ryHRmwPA@mail.gmail.com> <EMEW3|bbf82c39a7afc0305d21ff1c5582540bs3BDUh03tjc|ecs.soton.ac.uk|22CF4C02-B728-4148-A86A-B42080728FE6@ecs.soton.ac.uk> <CAPt1N1ncty=agWKaNnYFNBXnLQnxCzZMKe8S1zTUq7hQ3SLA1w@mail.g! mail.com> <DDC5F6F9-5ECA-455C-B435-E8B6784D6695@ecs.soton.ac.uk>
To: Ted Lemon <mellon@fugue.com>
X-Mailer: Apple Mail (2.3112)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-ECS-MailScanner-SpamScore: ss
X-smtpf-Report: sid=s3BEgQ321920773600; tid=s3BEgQ3219207736ur; client=relay,ipv6; mail=; rcpt=; nrcpt=2:0; fails=0
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: u3CDgQw9009832
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/6gT3czu-nlNlYxIlrmsn3CoJQ-I>
Cc: ietf <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: Tue, 12 Apr 2016 13:42:35 -0000

--Apple-Mail=_C5E359DE-2DE2-4010-BCA2-ADED1410451E
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

> On 12 Apr 2016, at 14:22, Ted Lemon <mellon@fugue.com> wrote:
>=20
> The problem with a larger virtual interim is that it doesn't replace =
an IETF, and so you're adding workload but not subtracting any workload. =
  I don't see the point in that.

Well, there may be a number of WGs that wish to progress their work a =
bit more briskly, or have one or more specific topics that need prompt =
discussion, and use an interim meeting to achieve that. So I=E2=80=99m =
not sure it=E2=80=99s adding to workload, rather it may allow us to be =
more efficient.  But the main issue with any virtual meeting is =
timezones. There=E2=80=99s really no way to deal with that problem =
satisfactorily.=20

Tim

>=20
> On Tue, Apr 12, 2016 at 8:30 AM, Tim Chown <tjc@ecs.soton.ac.uk =
<mailto:tjc@ecs.soton.ac.uk>> wrote:
>> On 12 Apr 2016, at 12:49, Ted Lemon <mellon@fugue.com =
<mailto:mellon@fugue.com>> wrote:
>>=20
>> Agree about Buenos Aires.   We already do excellent virtual =
interims--I think if your standard for whether we can do a virtual IETF =
is that virtual interims work, we are already there.
>>=20
>> I think that if we want to test this idea, what we need to do is =
designate some future IETF virtual _now_, and then start preparing, =
rather than say "oh, we should do a virtual" and then dither about when =
we might be ready.   We will never be so ready that a virtual IETF feels =
identical to an in-person IETF, so let's just abandon that idea and get =
started on making a virtual IETF that, while different, is still a =
success.
>=20
> Sounds interesting, if something of a big leap to attempt. Is a larger =
wholly virtual, multiple WG interim meeting a next step then?
>=20
> Btw where do we get the virtual T-shirt? ;)
>=20
> Tim
>=20
>>=20
>> On Tue, Apr 12, 2016 at 7:43 AM, Tim Chown <tjc@ecs.soton.ac.uk =
<mailto:tjc@ecs.soton.ac.uk>> wrote:
>> Hi,
>>=20
>> To minimise the chances of a =E2=80=98Singapore=E2=80=99 happening =
again it would seem prudent to
>>=20
>> a) re-use previous successful meeting venues for the bulk of our =
meetings (say, every 5 in 6 meetings); this is one criteria for meeting =
selection as it stands anyway; that list might include venues like =
Prague, Berlin, Vancouver, etc.; we=E2=80=99d need to be clear in what =
=E2=80=98successful=E2=80=99 means - the meeting feedback forms provide =
one such mechanism;
>>=20
>> b) be transparent at an early stage about where new venues might be, =
whether by country or city, so there is a fair chance for people to give =
feedback; of course, how such feedback is weighed is an open question, =
but at least it would be there, and the IAOC can then make a decision =
=E2=80=98eyes wide open=E2=80=99.
>>=20
>> In such a system, Buenos Aires would have been a =E2=80=981 in 6=E2=80=99=
 venue. In that light, I=E2=80=99d note that many people have said how =
much they enjoyed Buenos Aires as a meeting place. And while the IAOC =
probably feel rather down over the comments about Singapore, they should =
be praised for going out on something of a limb in making the Buenos =
Aires selection. (And I=E2=80=99d add that the enthusiasm and =
helpfulness of the LACNIC hosts was also fantastic.)
>>=20
>> In terms of virtual meetings, I=E2=80=99d suggest we try to hold more =
interim WG meetings, some completely virtually, and learn how to make =
those better. If we can regularly hold good quality wholly virtual =
interim meetings, then we can consider whether the same technology might =
be used for a larger meeting.
>>=20
>> Tim
>>=20
>> > On 12 Apr 2016, at 00:54, Ted Lemon <mellon@fugue.com =
<mailto:mellon@fugue.com>> wrote:
>> >
>> > While I do not think it's true that we can entirely get away =
without doing in-person meetings, I do agree with you that we can do =
better at doing remote meetings.   Perhaps we should let this =
unfortunate event drive us to make the attempt.
>> >
>> > If we were to attempt such a thing, how do you think it would work?
>>=20
>>=20
>=20
>=20


--Apple-Mail=_C5E359DE-2DE2-4010-BCA2-ADED1410451E
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D""><div><blockquote type=3D"cite" class=3D""><div class=3D"">On =
12 Apr 2016, at 14:22, Ted Lemon &lt;<a href=3D"mailto:mellon@fugue.com" =
class=3D"">mellon@fugue.com</a>&gt; wrote:</div><br =
class=3D"Apple-interchange-newline"><div class=3D""><div dir=3D"ltr" =
class=3D"">The problem with a larger virtual interim is that it doesn't =
replace an IETF, and so you're adding workload but not subtracting any =
workload. &nbsp; I don't see the point in =
that.</div></div></blockquote><div><br class=3D""></div><div>Well, there =
may be a number of WGs that wish to progress their work a bit more =
briskly, or have one or more specific topics that need prompt =
discussion, and use an interim meeting to achieve that. So I=E2=80=99m =
not sure it=E2=80=99s adding to workload, rather it may allow us to be =
more efficient. &nbsp;But the main issue with any virtual meeting is =
timezones. There=E2=80=99s really no way to deal with that problem =
satisfactorily.&nbsp;</div><div><br class=3D""></div>Tim</div><div><br =
class=3D""><blockquote type=3D"cite" class=3D""><div class=3D""><div =
class=3D"gmail_extra"><br class=3D""><div class=3D"gmail_quote">On Tue, =
Apr 12, 2016 at 8:30 AM, Tim Chown <span dir=3D"ltr" class=3D"">&lt;<a =
href=3D"mailto:tjc@ecs.soton.ac.uk" target=3D"_blank" =
class=3D"">tjc@ecs.soton.ac.uk</a>&gt;</span> wrote:<br =
class=3D""><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 =
.8ex;border-left:1px #ccc solid;padding-left:1ex"><div =
style=3D"word-wrap:break-word" class=3D""><div class=3D""><blockquote =
type=3D"cite" class=3D""><div class=3D"">On 12 Apr 2016, at 12:49, Ted =
Lemon &lt;<a href=3D"mailto:mellon@fugue.com" target=3D"_blank" =
class=3D"">mellon@fugue.com</a>&gt; wrote:</div><br class=3D""><div =
class=3D""><div dir=3D"ltr" class=3D"">Agree about Buenos Aires. &nbsp; =
We already do excellent virtual interims--I think if your standard for =
whether we can do a virtual IETF is that virtual interims work, we are =
already there.<div class=3D""><br class=3D""></div><div class=3D"">I =
think that if we want to test this idea, what we need to do is designate =
some future IETF virtual _now_, and then start preparing, rather than =
say "oh, we should do a virtual" and then dither about when we might be =
ready. &nbsp; We will never be so ready that a virtual IETF feels =
identical to an in-person IETF, so let's just abandon that idea and get =
started on making a virtual IETF that, while different, is still a =
success.</div></div></div></blockquote><div class=3D""><br =
class=3D""></div><div class=3D"">Sounds interesting, if something of a =
big leap to attempt. Is a larger wholly virtual, multiple WG interim =
meeting a next step then?</div><div class=3D""><br class=3D""></div><div =
class=3D"">Btw where do we get the virtual T-shirt? ;)</div><div =
class=3D""><br class=3D""></div>Tim</div><div class=3D""><br =
class=3D""><blockquote type=3D"cite" class=3D""><div class=3D""><div =
class=3D"gmail_extra"><br class=3D""><div class=3D"gmail_quote">On Tue, =
Apr 12, 2016 at 7:43 AM, Tim Chown <span dir=3D"ltr" class=3D"">&lt;<a =
href=3D"mailto:tjc@ecs.soton.ac.uk" target=3D"_blank" =
class=3D"">tjc@ecs.soton.ac.uk</a>&gt;</span> wrote:<br =
class=3D""><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 =
.8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br class=3D"">
<br class=3D"">
To minimise the chances of a =E2=80=98Singapore=E2=80=99 happening again =
it would seem prudent to<br class=3D"">
<br class=3D"">
a) re-use previous successful meeting venues for the bulk of our =
meetings (say, every 5 in 6 meetings); this is one criteria for meeting =
selection as it stands anyway; that list might include venues like =
Prague, Berlin, Vancouver, etc.; we=E2=80=99d need to be clear in what =
=E2=80=98successful=E2=80=99 means - the meeting feedback forms provide =
one such mechanism;<br class=3D"">
<br class=3D"">
b) be transparent at an early stage about where new venues might be, =
whether by country or city, so there is a fair chance for people to give =
feedback; of course, how such feedback is weighed is an open question, =
but at least it would be there, and the IAOC can then make a decision =
=E2=80=98eyes wide open=E2=80=99.<br class=3D"">
<br class=3D"">
In such a system, Buenos Aires would have been a =E2=80=981 in 6=E2=80=99 =
venue. In that light, I=E2=80=99d note that many people have said how =
much they enjoyed Buenos Aires as a meeting place. And while the IAOC =
probably feel rather down over the comments about Singapore, they should =
be praised for going out on something of a limb in making the Buenos =
Aires selection. (And I=E2=80=99d add that the enthusiasm and =
helpfulness of the LACNIC hosts was also fantastic.)<br class=3D"">
<br class=3D"">
In terms of virtual meetings, I=E2=80=99d suggest we try to hold more =
interim WG meetings, some completely virtually, and learn how to make =
those better. If we can regularly hold good quality wholly virtual =
interim meetings, then we can consider whether the same technology might =
be used for a larger meeting.<br class=3D"">
<span class=3D""><font color=3D"#888888" class=3D""><br class=3D"">
Tim<br class=3D"">
</font></span><div class=3D""><div class=3D""><br class=3D"">
&gt; On 12 Apr 2016, at 00:54, Ted Lemon &lt;<a =
href=3D"mailto:mellon@fugue.com" target=3D"_blank" =
class=3D"">mellon@fugue.com</a>&gt; wrote:<br class=3D"">
&gt;<br class=3D"">
&gt; While I do not think it's true that we can entirely get away =
without doing in-person meetings, I do agree with you that we can do =
better at doing remote meetings.&nbsp; &nbsp;Perhaps we should let this =
unfortunate event drive us to make the attempt.<br class=3D"">
&gt;<br class=3D"">
&gt; If we were to attempt such a thing, how do you think it would =
work?<br class=3D"">
<br class=3D"">
</div></div></blockquote></div><br class=3D""></div>
</div></blockquote></div><br class=3D""></div></blockquote></div><br =
class=3D""></div>
</div></blockquote></div><br class=3D""></body></html>=

--Apple-Mail=_C5E359DE-2DE2-4010-BCA2-ADED1410451E--


From nobody Tue Apr 12 06:48:38 2016
Return-Path: <mellon@fugue.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 20FE512DDC4 for <ietf@ietfa.amsl.com>; Tue, 12 Apr 2016 06:48:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.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 hX4dqSRoz66C for <ietf@ietfa.amsl.com>; Tue, 12 Apr 2016 06:48:34 -0700 (PDT)
Received: from mail-lf0-x22d.google.com (mail-lf0-x22d.google.com [IPv6:2a00:1450:4010:c07::22d]) (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 B5EE112DB90 for <ietf@ietf.org>; Tue, 12 Apr 2016 06:48:33 -0700 (PDT)
Received: by mail-lf0-x22d.google.com with SMTP id c126so26015308lfb.2 for <ietf@ietf.org>; Tue, 12 Apr 2016 06:48:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=ZQSWCOO5zd97hfcnLjo0Pfz3xopE78kLjwFyXmYLmJw=; b=ct6uZegwjxODaK3qogAR3ayJOTvHarr5QVnQEm/r6lqoPINE/o/r0fD+UU/MuXzIXc 4tLuhM0hmhtbM0/k9GRU40zAm6HzWedD+VqPZ3Dz1mQlNmleehADdJ/dXrTjkswnAIMV 052/MghNZkGoM87/eWhsMcbX1lFUHyLYaym85/ltMsQqUvE1khWd/OmKYNrcOC/Jhc8p e2NKz46o4tS6VnuEp/cFrwbJVJqBBbDMVbxSakIhsJP2NbheKgWuzBubkWNVMTgsmvKT xh4nOz0d+uCMkZiKS+NNUKK+KA/FNiFEaqlMPlxviEQqZMmytMvz7wqomppsalOfeKqG ORyw==
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=ZQSWCOO5zd97hfcnLjo0Pfz3xopE78kLjwFyXmYLmJw=; b=nDCJM0YWdULR+zj0Asp5yqcEUDgJawM8lufj+o/z/UqfqAIu47Xud0acV4bRfg+gRc WxbYoWQDvaIalU5uCMur1Bq3Jkf6YQz7rdBXrLRurh7CUFxovrhtvtS1JfYS2m9pN6di W1hG/GeVdfMvSLnI1VYvWDlMxmmgGWwJBv+FDysAI2V9WD0c8RPDFmKHo/NqEiIsvGbY 6dIIPdrwRYWEdulOUFcMs6t7OmJRDPA/N0nlW5lKSHfwV3qaBgSD459hOMXxahmLLZnN CISWB4oSuvZWLhbAWWNtFD+aZooKpEHP58l7T6LLqf9ZmskVcWlrYvq3X2UZ8NjiZaMC lIXQ==
X-Gm-Message-State: AOPr4FUKW8qxAw1GQOhKY1ojuivZE7z6UKm9iURkJJrevlXVzuM7fPTGveyl78HDgU4l67y8HWD0CQeqV/ELSQ==
X-Received: by 10.112.161.41 with SMTP id xp9mr1410599lbb.133.1460468911892; Tue, 12 Apr 2016 06:48:31 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.25.40.136 with HTTP; Tue, 12 Apr 2016 06:47:52 -0700 (PDT)
X-Originating-IP: [71.233.41.235]
In-Reply-To: <EMEW3|97bceb9b22356ec71621ead633105fcfs3BEgQ03tjc|ecs.soton.ac.uk|DDC5F6F9-5ECA-455C-B435-E8B6784D6695@ecs.soton.ac.uk>
References: <m260vp7eke.wl%randy@psg.com> <570A6458.3050206@comcast.net> <m21t6d7c9t.wl%randy@psg.com> <570A67B4.3010206@comcast.net> <570AB3AF.2050401@gmail.com> <87twj99c6w.fsf@tops.chopps.org> <CAKe6YvMyp-DyeDwpPY6KYmbDbnpgnvVk_cUStnA32wmgDWcz3w@mail.gmail.com> <BBF5DDFE515C3946BC18D733B20DAD233A62AA18@XMB122CNC.rim.net> <20160411104519.GA19092@gsp.org> <3F48466D-390C-4C18-B958-732AE3E46FF1@gmail.com> <20160411223403.GA6743@gsp.org> <DDFE7AA1-4C07-4944-AECA-EA361A3A0B71@ecs.soton.ac.uk> <CAPt1N1nNo0=JSptQdWRZCFy1v-m6Q8NQy4WVGHtnRJuFZFmMig@mail.gmail.com> <EMEW3|9aaa87920b361e2e71efe9c7005e927cs3BChQ03tjc|ecs.soton.ac.uk|DDFE7AA1-4C07-4944-AECA-EA361A3A0B71@ecs.soton.ac.uk> <22CF4C02-B728-4148-A86A-B42080728FE6@ecs.soton.ac.uk> <CAPt1N1nucCAg99gVDWOHVE2up=2xK0Qm2Ud81hUhp4ryHRmwPA@mail.gmail.com> <EMEW3|bbf82c39a7afc0305d21ff1c5582540bs3BDUh03tjc|ecs.soton.ac.uk|22CF4C02-B728-4148-A86A-B42080728FE6@ecs.soton.ac.uk> <DDC5F6F9-5ECA-455C-B435-E8B6784D6695@ecs.soton.ac.uk> <CAPt1N1ncty=agWKaNnYFNBXnLQnxCzZMKe8S1zTUq7hQ3SLA1w@mail.gmail.com> <EMEW3|97bceb9b22356ec71621ead633105fcfs3BEgQ03tjc|ecs.soton.ac.uk|DDC5F6F9-5ECA-455C-B435-E8B6784D6695@ecs.soton.ac.uk>
From: Ted Lemon <mellon@fugue.com>
Date: Tue, 12 Apr 2016 09:47:52 -0400
Message-ID: <CAPt1N1nLVZ5Be4jKCWrPAxrsaUFnyTb2pTeZZRg69yBBovqqTg@mail.gmail.com>
Subject: Re: Virtual IETFs (was: Re: Concerns about Singapore)
To: Tim Chown <tjc@ecs.soton.ac.uk>
Content-Type: multipart/alternative; boundary=001a11c26b2ab3034e053049ea04
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/zvIUwmir7-o7Yi7r7l52K5Um2gk>
Cc: ietf <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: Tue, 12 Apr 2016 13:48:36 -0000

--001a11c26b2ab3034e053049ea04
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

When I had to miss Prague, I just time-shifted for the week.   Wouldn't
work for everyone, but it seemed fine to me.

On Tue, Apr 12, 2016 at 9:42 AM, Tim Chown <tjc@ecs.soton.ac.uk> wrote:

> On 12 Apr 2016, at 14:22, Ted Lemon <mellon@fugue.com> wrote:
>
> The problem with a larger virtual interim is that it doesn't replace an
> IETF, and so you're adding workload but not subtracting any workload.   I
> don't see the point in that.
>
>
> Well, there may be a number of WGs that wish to progress their work a bit
> more briskly, or have one or more specific topics that need prompt
> discussion, and use an interim meeting to achieve that. So I=E2=80=99m no=
t sure
> it=E2=80=99s adding to workload, rather it may allow us to be more effici=
ent.  But
> the main issue with any virtual meeting is timezones. There=E2=80=99s rea=
lly no way
> to deal with that problem satisfactorily.
>
> Tim
>
>
> On Tue, Apr 12, 2016 at 8:30 AM, Tim Chown <tjc@ecs.soton.ac.uk> wrote:
>
>> On 12 Apr 2016, at 12:49, Ted Lemon <mellon@fugue.com> wrote:
>>
>> Agree about Buenos Aires.   We already do excellent virtual interims--I
>> think if your standard for whether we can do a virtual IETF is that virt=
ual
>> interims work, we are already there.
>>
>> I think that if we want to test this idea, what we need to do is
>> designate some future IETF virtual _now_, and then start preparing, rath=
er
>> than say "oh, we should do a virtual" and then dither about when we migh=
t
>> be ready.   We will never be so ready that a virtual IETF feels identica=
l
>> to an in-person IETF, so let's just abandon that idea and get started on
>> making a virtual IETF that, while different, is still a success.
>>
>>
>> Sounds interesting, if something of a big leap to attempt. Is a larger
>> wholly virtual, multiple WG interim meeting a next step then?
>>
>> Btw where do we get the virtual T-shirt? ;)
>>
>> Tim
>>
>>
>> On Tue, Apr 12, 2016 at 7:43 AM, Tim Chown <tjc@ecs.soton.ac.uk> wrote:
>>
>>> Hi,
>>>
>>> To minimise the chances of a =E2=80=98Singapore=E2=80=99 happening agai=
n it would seem
>>> prudent to
>>>
>>> a) re-use previous successful meeting venues for the bulk of our
>>> meetings (say, every 5 in 6 meetings); this is one criteria for meeting
>>> selection as it stands anyway; that list might include venues like Prag=
ue,
>>> Berlin, Vancouver, etc.; we=E2=80=99d need to be clear in what =E2=80=
=98successful=E2=80=99 means -
>>> the meeting feedback forms provide one such mechanism;
>>>
>>> b) be transparent at an early stage about where new venues might be,
>>> whether by country or city, so there is a fair chance for people to giv=
e
>>> feedback; of course, how such feedback is weighed is an open question, =
but
>>> at least it would be there, and the IAOC can then make a decision =E2=
=80=98eyes
>>> wide open=E2=80=99.
>>>
>>> In such a system, Buenos Aires would have been a =E2=80=981 in 6=E2=80=
=99 venue. In that
>>> light, I=E2=80=99d note that many people have said how much they enjoye=
d Buenos
>>> Aires as a meeting place. And while the IAOC probably feel rather down =
over
>>> the comments about Singapore, they should be praised for going out on
>>> something of a limb in making the Buenos Aires selection. (And I=E2=80=
=99d add that
>>> the enthusiasm and helpfulness of the LACNIC hosts was also fantastic.)
>>>
>>> In terms of virtual meetings, I=E2=80=99d suggest we try to hold more i=
nterim WG
>>> meetings, some completely virtually, and learn how to make those better=
. If
>>> we can regularly hold good quality wholly virtual interim meetings, the=
n we
>>> can consider whether the same technology might be used for a larger mee=
ting.
>>>
>>> Tim
>>>
>>> > On 12 Apr 2016, at 00:54, Ted Lemon <mellon@fugue.com> wrote:
>>> >
>>> > While I do not think it's true that we can entirely get away without
>>> doing in-person meetings, I do agree with you that we can do better at
>>> doing remote meetings.   Perhaps we should let this unfortunate event d=
rive
>>> us to make the attempt.
>>> >
>>> > If we were to attempt such a thing, how do you think it would work?
>>>
>>>
>>
>>
>
>

--001a11c26b2ab3034e053049ea04
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">When I had to miss Prague, I just time-shifted for the wee=
k. =C2=A0 Wouldn&#39;t work for everyone, but it seemed fine to me.</div><d=
iv class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Tue, Apr 12, 201=
6 at 9:42 AM, Tim Chown <span dir=3D"ltr">&lt;<a href=3D"mailto:tjc@ecs.sot=
on.ac.uk" target=3D"_blank">tjc@ecs.soton.ac.uk</a>&gt;</span> wrote:<br><b=
lockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px =
#ccc solid;padding-left:1ex"><div style=3D"word-wrap:break-word"><div><span=
 class=3D""><blockquote type=3D"cite"><div>On 12 Apr 2016, at 14:22, Ted Le=
mon &lt;<a href=3D"mailto:mellon@fugue.com" target=3D"_blank">mellon@fugue.=
com</a>&gt; wrote:</div><br><div><div dir=3D"ltr">The problem with a larger=
 virtual interim is that it doesn&#39;t replace an IETF, and so you&#39;re =
adding workload but not subtracting any workload. =C2=A0 I don&#39;t see th=
e point in that.</div></div></blockquote><div><br></div></span><div>Well, t=
here may be a number of WGs that wish to progress their work a bit more bri=
skly, or have one or more specific topics that need prompt discussion, and =
use an interim meeting to achieve that. So I=E2=80=99m not sure it=E2=80=99=
s adding to workload, rather it may allow us to be more efficient.=C2=A0 Bu=
t the main issue with any virtual meeting is timezones. There=E2=80=99s rea=
lly no way to deal with that problem satisfactorily.=C2=A0</div><span class=
=3D"HOEnZb"><font color=3D"#888888"><div><br></div>Tim</font></span></div><=
span class=3D""><div><br><blockquote type=3D"cite"><div><div class=3D"gmail=
_extra"><br><div class=3D"gmail_quote">On Tue, Apr 12, 2016 at 8:30 AM, Tim=
 Chown <span dir=3D"ltr">&lt;<a href=3D"mailto:tjc@ecs.soton.ac.uk" target=
=3D"_blank">tjc@ecs.soton.ac.uk</a>&gt;</span> wrote:<br><blockquote class=
=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padd=
ing-left:1ex"><div style=3D"word-wrap:break-word"><div><blockquote type=3D"=
cite"><div>On 12 Apr 2016, at 12:49, Ted Lemon &lt;<a href=3D"mailto:mellon=
@fugue.com" target=3D"_blank">mellon@fugue.com</a>&gt; wrote:</div><br><div=
><div dir=3D"ltr">Agree about Buenos Aires. =C2=A0 We already do excellent =
virtual interims--I think if your standard for whether we can do a virtual =
IETF is that virtual interims work, we are already there.<div><br></div><di=
v>I think that if we want to test this idea, what we need to do is designat=
e some future IETF virtual _now_, and then start preparing, rather than say=
 &quot;oh, we should do a virtual&quot; and then dither about when we might=
 be ready. =C2=A0 We will never be so ready that a virtual IETF feels ident=
ical to an in-person IETF, so let&#39;s just abandon that idea and get star=
ted on making a virtual IETF that, while different, is still a success.</di=
v></div></div></blockquote><div><br></div><div>Sounds interesting, if somet=
hing of a big leap to attempt. Is a larger wholly virtual, multiple WG inte=
rim meeting a next step then?</div><div><br></div><div>Btw where do we get =
the virtual T-shirt? ;)</div><div><br></div>Tim</div><div><br><blockquote t=
ype=3D"cite"><div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote"=
>On Tue, Apr 12, 2016 at 7:43 AM, Tim Chown <span dir=3D"ltr">&lt;<a href=
=3D"mailto:tjc@ecs.soton.ac.uk" target=3D"_blank">tjc@ecs.soton.ac.uk</a>&g=
t;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0=
 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br>
<br>
To minimise the chances of a =E2=80=98Singapore=E2=80=99 happening again it=
 would seem prudent to<br>
<br>
a) re-use previous successful meeting venues for the bulk of our meetings (=
say, every 5 in 6 meetings); this is one criteria for meeting selection as =
it stands anyway; that list might include venues like Prague, Berlin, Vanco=
uver, etc.; we=E2=80=99d need to be clear in what =E2=80=98successful=E2=80=
=99 means - the meeting feedback forms provide one such mechanism;<br>
<br>
b) be transparent at an early stage about where new venues might be, whethe=
r by country or city, so there is a fair chance for people to give feedback=
; of course, how such feedback is weighed is an open question, but at least=
 it would be there, and the IAOC can then make a decision =E2=80=98eyes wid=
e open=E2=80=99.<br>
<br>
In such a system, Buenos Aires would have been a =E2=80=981 in 6=E2=80=99 v=
enue. In that light, I=E2=80=99d note that many people have said how much t=
hey enjoyed Buenos Aires as a meeting place. And while the IAOC probably fe=
el rather down over the comments about Singapore, they should be praised fo=
r going out on something of a limb in making the Buenos Aires selection. (A=
nd I=E2=80=99d add that the enthusiasm and helpfulness of the LACNIC hosts =
was also fantastic.)<br>
<br>
In terms of virtual meetings, I=E2=80=99d suggest we try to hold more inter=
im WG meetings, some completely virtually, and learn how to make those bett=
er. If we can regularly hold good quality wholly virtual interim meetings, =
then we can consider whether the same technology might be used for a larger=
 meeting.<br>
<span><font color=3D"#888888"><br>
Tim<br>
</font></span><div><div><br>
&gt; On 12 Apr 2016, at 00:54, Ted Lemon &lt;<a href=3D"mailto:mellon@fugue=
.com" target=3D"_blank">mellon@fugue.com</a>&gt; wrote:<br>
&gt;<br>
&gt; While I do not think it&#39;s true that we can entirely get away witho=
ut doing in-person meetings, I do agree with you that we can do better at d=
oing remote meetings.=C2=A0 =C2=A0Perhaps we should let this unfortunate ev=
ent drive us to make the attempt.<br>
&gt;<br>
&gt; If we were to attempt such a thing, how do you think it would work?<br=
>
<br>
</div></div></blockquote></div><br></div>
</div></blockquote></div><br></div></blockquote></div><br></div>
</div></blockquote></div><br></span></div></blockquote></div><br></div>

--001a11c26b2ab3034e053049ea04--


From nobody Tue Apr 12 07:09:40 2016
Return-Path: <mary.h.barnes@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 ABA3112E933 for <ietf@ietfa.amsl.com>; Tue, 12 Apr 2016 07:09:39 -0700 (PDT)
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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 FiByDUdoQIVo for <ietf@ietfa.amsl.com>; Tue, 12 Apr 2016 07:09:37 -0700 (PDT)
Received: from mail-yw0-x235.google.com (mail-yw0-x235.google.com [IPv6:2607:f8b0:4002:c05::235]) (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 1792512E7F5 for <ietf@ietf.org>; Tue, 12 Apr 2016 07:09:37 -0700 (PDT)
Received: by mail-yw0-x235.google.com with SMTP id i84so25200991ywc.2 for <ietf@ietf.org>; Tue, 12 Apr 2016 07:09:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=r5gj7GqMFhnbTm1ETfDMXAI7jwidjhV6Cytbwm73UI4=; b=AOBokvAjGCzbyODnDePj3XEvktYRGuODyV7KdZIsmSfx7ND2KkaO7NqRL2Y4dnCWkR JUDZnLI3WY4OR1UKoD9AlFiApKEaWJU+u5WckpQdPIy2pryfo2rdgknHcVJoOdbnHU1Q 6R6G8MadtI9yX3xhvE7xa8aQSn01hwJVc6W8myS2eI2f8i/Go2dranDncGxFuE25A6RR K9t6LrpAOShxEfX5PJH7IwvGWFol57/DCdkTNrTLr7m5hvAc+AoADvDBUoWeWQ/nAl2P 8/mT4G9wgX+D+og8hdxcxrgvPwDYt3TE9Yap7V3lPrYmij7eKatC3AcisdceSYYvZ8/q 0MCQ==
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:date :message-id:subject:from:to:cc; bh=r5gj7GqMFhnbTm1ETfDMXAI7jwidjhV6Cytbwm73UI4=; b=A3CkePRo4rEDSkmsiDiW3jhtu/IGp8MWoyCXrQCsB71y7DkGOnFVgYjByXMWQA9puu eBhTZvcm8faS86DKi8WaJeWp09dIlNoyQ+1eB+jVj74DUzN6V3HsFUmE8c+7/4bTTgGf WADkGF0mR9tx+0iqi15W97Qw9UrME5mJiiqh+xYbL0FjCK9RXMIMEgq0aK8dIKb/g0Sv lMIbCrWQlivlCUQBmESKPW9iKY0uH7n0hKjtAfrRCSHnSSLK1XkP4zz88HSski+llSVg 5NSlP1JbRCKz+/BBjQfo1gicUXwncPywrfbWLV2BNd/qYB/hQe5Y3xeoEJab8Zs7O8r/ Hi/g==
X-Gm-Message-State: AOPr4FVQ10Xz82iPGAK4iwV8Vtqdpzb/RPoQhFzw12gkR0HjuspTdTHNF0w3mZwqf28Z5EuN0PZ2ialBqiscvg==
MIME-Version: 1.0
X-Received: by 10.13.205.198 with SMTP id p189mr1736248ywd.180.1460470176274;  Tue, 12 Apr 2016 07:09:36 -0700 (PDT)
Received: by 10.37.63.197 with HTTP; Tue, 12 Apr 2016 07:09:36 -0700 (PDT)
In-Reply-To: <87fuurgd8f.fsf@tops.chopps.org>
References: <570AB3AF.2050401@gmail.com> <87twj99c6w.fsf@tops.chopps.org> <CAKe6YvMyp-DyeDwpPY6KYmbDbnpgnvVk_cUStnA32wmgDWcz3w@mail.gmail.com> <BBF5DDFE515C3946BC18D733B20DAD233A62AA18@XMB122CNC.rim.net> <20160411104519.GA19092@gsp.org> <3F48466D-390C-4C18-B958-732AE3E46FF1@gmail.com> <20160411223403.GA6743@gsp.org> <87twj7eon7.fsf@tops.chopps.org> <20160412110839.GA20488@gsp.org> <8760vn82f2.fsf@tops.chopps.org> <20160412124639.GA27223@gsp.org> <87fuurgd8f.fsf@tops.chopps.org>
Date: Tue, 12 Apr 2016 09:09:36 -0500
Message-ID: <CABmDk8kCfTB_AKyqV4X+AghL2G7i+XcKR=tzV0jybM05k+UU4Q@mail.gmail.com>
Subject: Re: Remote only meetings? [Re: Concerns about Singapore]
From: Mary Barnes <mary.h.barnes@gmail.com>
To: chopps@chopps.org
Content-Type: multipart/alternative; boundary=001a114da6561009dc05304a3621
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/vQn62u4Dy-ycYaI4xTLRd3iBnFM>
Cc: Rich Kulawiec <rsk@gsp.org>, "<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: Tue, 12 Apr 2016 14:09:39 -0000

--001a114da6561009dc05304a3621
Content-Type: text/plain; charset=UTF-8

On Tue, Apr 12, 2016 at 8:37 AM, <chopps@chopps.org> wrote:

>
> Rich Kulawiec <rsk@gsp.org> writes:
>
> > On Tue, Apr 12, 2016 at 07:57:53AM -0400, chopps@chopps.org wrote:
> >> Your suggestion of not having them would subtract value from the process
> >> though. I don't see the win.
> >
> > The win is that all of the time and effort and expense (all of which
> > are finite resources) that go into those could be directed elsewhere.
>
> The meetings and their fees are income positive, they aren't a drain on
> resource, the opposite in fact.
>
[MB] I would agree when it comes to dollars, but people (i.e., the effort
to which Rich is referring) are also a resource and volunteers do the
work.  If the only volunteers you get are from large companies, I think the
IETF does lose.  With improved remote participation, individuals that
aren't sponsored by large companies can continue to contribute.  Without
it, we become ineffective.  [/MB]

>
> > These meetings select for a highly limited (by circumstance, by
> necessity,
> > and by choice) subset.  And once upon a time, when the 'net was much
> > younger and more limited in terms of geography and scope, that might
> > have been alright, because the subset mapped fairly well onto the larger
> > set of people involved in networking.  But that's no longer true.
> > And the difficulties/expense of travel are only going to get worse
> > for the forseeable future: they're not going to get better.
>
> I think it would be useful to get some real data to measure exactly how
> highly limited that subset of people are. Perhaps as a simple first
> shot we could take email sent to IETF working group mailing lists over
> the last year, and cross reference that against the registrations lists
> of the last 3 IETFs and see what percentage of people doing IETF work
> cannot or choose not to attend the on-site meetings?
>
> [MB] There was a separate list of registered remote attendees for this
recent meeting. You can take a look there and see a number of long time
contributors and some WG chairs (myself included) that have participated
remotely.  The very reason I did not go was due to lack of funding.  There
are a number of us that have contributed significantly over the past 15-30
years that would like to continue to do so but as independent consultants,
some of these trips are just not fiscally possible.  I went to Yokohama so
couldn't even entertain the idea of attending the meeting in BA without a
sponsor.    And, I seriously doubt I can continue as a WG chair if I can't
get funding in the future.  So, in the end, the current model self selects
and benefits the larger companies over individuals that really do want to
do work for the "good of the Internet" but just can't justify the expense.
  [/MB]


> Thanks,
> Chris.
>
>
> >
> > ---rsk
>
>

--001a114da6561009dc05304a3621
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><div class=3D"gmail_quo=
te">On Tue, Apr 12, 2016 at 8:37 AM,  <span dir=3D"ltr">&lt;<a href=3D"mail=
to:chopps@chopps.org" target=3D"_blank">chopps@chopps.org</a>&gt;</span> wr=
ote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border=
-left:1px #ccc solid;padding-left:1ex"><span class=3D""><br>
Rich Kulawiec &lt;<a href=3D"mailto:rsk@gsp.org">rsk@gsp.org</a>&gt; writes=
:<br>
<br>
&gt; On Tue, Apr 12, 2016 at 07:57:53AM -0400, <a href=3D"mailto:chopps@cho=
pps.org">chopps@chopps.org</a> wrote:<br>
&gt;&gt; Your suggestion of not having them would subtract value from the p=
rocess<br>
&gt;&gt; though. I don&#39;t see the win.<br>
&gt;<br>
&gt; The win is that all of the time and effort and expense (all of which<b=
r>
&gt; are finite resources) that go into those could be directed elsewhere.<=
br>
<br>
</span>The meetings and their fees are income positive, they aren&#39;t a d=
rain on<br>
resource, the opposite in fact.<br></blockquote><div>[MB] I would agree whe=
n it comes to dollars, but people (i.e., the effort to which Rich is referr=
ing) are also a resource and volunteers do the work.=C2=A0 If the only volu=
nteers you get are from large companies, I think the IETF does lose.=C2=A0 =
With improved remote participation, individuals that aren&#39;t sponsored b=
y large companies can continue to contribute.=C2=A0 Without it, we become i=
neffective. =C2=A0[/MB]=C2=A0</div><blockquote class=3D"gmail_quote" style=
=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<span class=3D""><br>
&gt; These meetings select for a highly limited (by circumstance, by necess=
ity,<br>
&gt; and by choice) subset.=C2=A0 And once upon a time, when the &#39;net w=
as much<br>
&gt; younger and more limited in terms of geography and scope, that might<b=
r>
&gt; have been alright, because the subset mapped fairly well onto the larg=
er<br>
&gt; set of people involved in networking.=C2=A0 But that&#39;s no longer t=
rue.<br>
&gt; And the difficulties/expense of travel are only going to get worse<br>
&gt; for the forseeable future: they&#39;re not going to get better.<br>
<br>
</span>I think it would be useful to get some real data to measure exactly =
how<br>
highly limited that subset of people are. Perhaps as a simple first<br>
shot we could take email sent to IETF working group mailing lists over<br>
the last year, and cross reference that against the registrations lists<br>
of the last 3 IETFs and see what percentage of people doing IETF work<br>
cannot or choose not to attend the on-site meetings?<br><br></blockquote><d=
iv>[MB] There was a separate list of registered remote attendees for this r=
ecent meeting. You can take a look there and see a number of long time cont=
ributors and some WG chairs (myself included) that have participated remote=
ly.=C2=A0 The very reason I did not go was due to lack of funding.=C2=A0 Th=
ere are a number of us that have contributed significantly over the past 15=
-30 years that would like to continue to do so but as independent consultan=
ts, some of these trips are just not fiscally possible.=C2=A0 I went to Yok=
ohama so couldn&#39;t even entertain the idea of attending the meeting in B=
A without a sponsor. =C2=A0 =C2=A0And, I seriously doubt I can continue as =
a WG chair if I can&#39;t get funding in the future.=C2=A0 So, in the end, =
the current model self selects and benefits the larger companies over indiv=
iduals that really do want to do work for the &quot;good of the Internet&qu=
ot; but just can&#39;t justify the expense. =C2=A0 [/MB]</div><div>=C2=A0</=
div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-lef=
t:1px #ccc solid;padding-left:1ex">
Thanks,<br>
Chris.<br>
<br>
<br>
&gt;<br>
&gt; ---rsk<br>
<br>
</blockquote></div><br></div></div>

--001a114da6561009dc05304a3621--


From nobody Tue Apr 12 07:21:03 2016
Return-Path: <chopps@chopps.org>
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 86C1A12EE14 for <ietf@ietfa.amsl.com>; Tue, 12 Apr 2016 07:21:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.895
X-Spam-Level: 
X-Spam-Status: No, score=-2.895 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.996] 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 ZRMkNqIEp4eS for <ietf@ietfa.amsl.com>; Tue, 12 Apr 2016 07:21:00 -0700 (PDT)
Received: from smtp.chopps.org (smtp.chopps.org [54.88.81.56]) by ietfa.amsl.com (Postfix) with ESMTP id AB7F312DC5C for <ietf@ietf.org>; Tue, 12 Apr 2016 07:21:00 -0700 (PDT)
Received: from [192.168.1.5] (24-247-68-31.dhcp.trcy.mi.charter.com [24.247.68.31]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by smtp.chopps.org (Postfix) with ESMTPSA id D2F0B6117B; Tue, 12 Apr 2016 14:20:59 +0000 (UTC)
Subject: Re: Remote only meetings? [Re: Concerns about Singapore]
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Content-Type: multipart/signed; boundary="Apple-Mail=_674C82CF-227B-44CF-B08E-C47F0E82C731"; protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail 2.6b2
From: Christian Hopps <chopps@chopps.org>
In-Reply-To: <CABmDk8kCfTB_AKyqV4X+AghL2G7i+XcKR=tzV0jybM05k+UU4Q@mail.gmail.com>
Date: Tue, 12 Apr 2016 10:20:58 -0400
Message-Id: <65989154-BD08-45F0-B6F0-2AE3E435409C@chopps.org>
References: <570AB3AF.2050401@gmail.com> <87twj99c6w.fsf@tops.chopps.org> <CAKe6YvMyp-DyeDwpPY6KYmbDbnpgnvVk_cUStnA32wmgDWcz3w@mail.gmail.com> <BBF5DDFE515C3946BC18D733B20DAD233A62AA18@XMB122CNC.rim.net> <20160411104519.GA19092@gsp.org> <3F48466D-390C-4C18-B958-732AE3E46FF1@gmail.com> <20160411223403.GA6743@gsp.org> <87twj7eon7.fsf@tops.chopps.org> <20160412110839.GA20488@gsp.org> <8760vn82f2.fsf@tops.chopps.org> <20160412124639.GA27223@gsp.org> <87fuurgd8f.fsf@tops.chopps.org> <CABmDk8kCfTB_AKyqV4X+AghL2G7i+XcKR=tzV0jybM05k+UU4Q@mail.gmail.com>
To: Mary Barnes <mary.h.barnes@gmail.com>
X-Mailer: Apple Mail (2.3124)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/wfSaNu4V98IhRC_8e7J-IzflUC0>
Cc: Rich Kulawiec <rsk@gsp.org>, "<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: Tue, 12 Apr 2016 14:21:02 -0000

--Apple-Mail=_674C82CF-227B-44CF-B08E-C47F0E82C731
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_D4478259-0B09-43A7-A021-7514F3FF37A7"


--Apple-Mail=_D4478259-0B09-43A7-A021-7514F3FF37A7
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


> On Apr 12, 2016, at 10:09 AM, Mary Barnes <mary.h.barnes@gmail.com> =
wrote:
>=20
>=20
>=20
> On Tue, Apr 12, 2016 at 8:37 AM,  <chopps@chopps.org =
<mailto:chopps@chopps.org>> wrote:
>=20
> Rich Kulawiec <rsk@gsp.org <mailto:rsk@gsp.org>> writes:
>=20
> > On Tue, Apr 12, 2016 at 07:57:53AM -0400, chopps@chopps.org =
<mailto:chopps@chopps.org> wrote:
> >> Your suggestion of not having them would subtract value from the =
process
> >> though. I don't see the win.
> >
> > The win is that all of the time and effort and expense (all of which
> > are finite resources) that go into those could be directed =
elsewhere.
>=20
> The meetings and their fees are income positive, they aren't a drain =
on
> resource, the opposite in fact.
> [MB] I would agree when it comes to dollars, but people (i.e., the =
effort to which Rich is referring) are also a resource and volunteers do =
the work.  If the only volunteers you get are from large companies, I =
think the IETF does lose.  With improved remote participation, =
individuals that aren't sponsored by large companies can continue to =
contribute.  Without it, we become ineffective.  [/MB]
>=20
> > These meetings select for a highly limited (by circumstance, by =
necessity,
> > and by choice) subset.  And once upon a time, when the 'net was much
> > younger and more limited in terms of geography and scope, that might
> > have been alright, because the subset mapped fairly well onto the =
larger
> > set of people involved in networking.  But that's no longer true.
> > And the difficulties/expense of travel are only going to get worse
> > for the forseeable future: they're not going to get better.
>=20
> I think it would be useful to get some real data to measure exactly =
how
> highly limited that subset of people are. Perhaps as a simple first
> shot we could take email sent to IETF working group mailing lists over
> the last year, and cross reference that against the registrations =
lists
> of the last 3 IETFs and see what percentage of people doing IETF work
> cannot or choose not to attend the on-site meetings?
>=20
> [MB] There was a separate list of registered remote attendees for this =
recent meeting. You can take a look there and see a number of long time =
contributors and some WG chairs (myself included) that have participated =
remotely.  The very reason I did not go was due to lack of funding.  =
There are a number of us that have contributed significantly over the =
past 15-30 years that would like to continue to do so but as independent =
consultants, some of these trips are just not fiscally possible.  I went =
to Yokohama so couldn't even entertain the idea of attending the meeting =
in BA without a sponsor.    And, I seriously doubt I can continue as a =
WG chair if I can't get funding in the future.  So, in the end, the =
current model self selects and benefits the larger companies over =
individuals that really do want to do work for the "good of the =
Internet" but just can't justify the expense.   [/MB]

I myself am on that remote list. I've heard the B.A. meeting was hard =
for many people (although this is anecdotal), and is a separate issue of =
contention for some. This is why I suggested the last 3 meetings, and a =
year of email so that the sample was large enough to not run in to =
particulars for each attendee who may not have been able to attend all, =
but rather some meetings.

I also think we have ways to make meetings more affordable, but Rich =
indicated this was only one of many concerns.

I think we need to look at a good sampling of the data at this point.

Thanks,
Chris.

>=20
> Thanks,
> Chris.
>=20
>=20
> >
> > ---rsk


--Apple-Mail=_D4478259-0B09-43A7-A021-7514F3FF37A7
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dus-ascii"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D""><br class=3D""><div><blockquote type=3D"cite" class=3D""><div =
class=3D"">On Apr 12, 2016, at 10:09 AM, Mary Barnes &lt;<a =
href=3D"mailto:mary.h.barnes@gmail.com" =
class=3D"">mary.h.barnes@gmail.com</a>&gt; wrote:</div><br =
class=3D"Apple-interchange-newline"><div class=3D""><br =
class=3D"Apple-interchange-newline"><br style=3D"font-family: Helvetica; =
font-size: 16px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; orphans: auto; text-align: =
start; text-indent: 0px; text-transform: none; white-space: normal; =
widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" =
class=3D""><div class=3D"gmail_quote" style=3D"font-family: Helvetica; =
font-size: 16px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; orphans: auto; text-align: =
start; text-indent: 0px; text-transform: none; white-space: normal; =
widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;">On =
Tue, Apr 12, 2016 at 8:37 AM,<span =
class=3D"Apple-converted-space">&nbsp;</span><span =
class=3D"Apple-converted-space">&nbsp;</span><span dir=3D"ltr" =
class=3D"">&lt;<a href=3D"mailto:chopps@chopps.org" target=3D"_blank" =
class=3D"">chopps@chopps.org</a>&gt;</span><span =
class=3D"Apple-converted-space">&nbsp;</span>wrote:<br =
class=3D""><blockquote class=3D"gmail_quote" style=3D"margin: 0px 0px =
0px 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, =
204); border-left-style: solid; padding-left: 1ex;"><span class=3D""><br =
class=3D"">Rich Kulawiec &lt;<a href=3D"mailto:rsk@gsp.org" =
class=3D"">rsk@gsp.org</a>&gt; writes:<br class=3D""><br class=3D"">&gt; =
On Tue, Apr 12, 2016 at 07:57:53AM -0400,<span =
class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"mailto:chopps@chopps.org" class=3D"">chopps@chopps.org</a><span =
class=3D"Apple-converted-space">&nbsp;</span>wrote:<br class=3D"">&gt;&gt;=
 Your suggestion of not having them would subtract value from the =
process<br class=3D"">&gt;&gt; though. I don't see the win.<br =
class=3D"">&gt;<br class=3D"">&gt; The win is that all of the time and =
effort and expense (all of which<br class=3D"">&gt; are finite =
resources) that go into those could be directed elsewhere.<br =
class=3D""><br class=3D""></span>The meetings and their fees are income =
positive, they aren't a drain on<br class=3D"">resource, the opposite in =
fact.<br class=3D""></blockquote><div class=3D"">[MB] I would agree when =
it comes to dollars, but people (i.e., the effort to which Rich is =
referring) are also a resource and volunteers do the work.&nbsp; If the =
only volunteers you get are from large companies, I think the IETF does =
lose.&nbsp; With improved remote participation, individuals that aren't =
sponsored by large companies can continue to contribute.&nbsp; Without =
it, we become ineffective. &nbsp;[/MB]&nbsp;</div><blockquote =
class=3D"gmail_quote" style=3D"margin: 0px 0px 0px 0.8ex; =
border-left-width: 1px; border-left-color: rgb(204, 204, 204); =
border-left-style: solid; padding-left: 1ex;"><span class=3D""><br =
class=3D"">&gt; These meetings select for a highly limited (by =
circumstance, by necessity,<br class=3D"">&gt; and by choice) =
subset.&nbsp; And once upon a time, when the 'net was much<br =
class=3D"">&gt; younger and more limited in terms of geography and =
scope, that might<br class=3D"">&gt; have been alright, because the =
subset mapped fairly well onto the larger<br class=3D"">&gt; set of =
people involved in networking.&nbsp; But that's no longer true.<br =
class=3D"">&gt; And the difficulties/expense of travel are only going to =
get worse<br class=3D"">&gt; for the forseeable future: they're not =
going to get better.<br class=3D""><br class=3D""></span>I think it =
would be useful to get some real data to measure exactly how<br =
class=3D"">highly limited that subset of people are. Perhaps as a simple =
first<br class=3D"">shot we could take email sent to IETF working group =
mailing lists over<br class=3D"">the last year, and cross reference that =
against the registrations lists<br class=3D"">of the last 3 IETFs and =
see what percentage of people doing IETF work<br class=3D"">cannot or =
choose not to attend the on-site meetings?<br class=3D""><br =
class=3D""></blockquote><div class=3D"">[MB] There was a separate list =
of registered remote attendees for this recent meeting. You can take a =
look there and see a number of long time contributors and some WG chairs =
(myself included) that have participated remotely.&nbsp; The very reason =
I did not go was due to lack of funding.&nbsp; There are a number of us =
that have contributed significantly over the past 15-30 years that would =
like to continue to do so but as independent consultants, some of these =
trips are just not fiscally possible.&nbsp; I went to Yokohama so =
couldn't even entertain the idea of attending the meeting in BA without =
a sponsor. &nbsp; &nbsp;And, I seriously doubt I can continue as a WG =
chair if I can't get funding in the future.&nbsp; So, in the end, the =
current model self selects and benefits the larger companies over =
individuals that really do want to do work for the "good of the =
Internet" but just can't justify the expense. &nbsp; =
[/MB]</div></div></div></blockquote><div><br class=3D""></div><div>I =
myself am on that remote list. I've heard the B.A. meeting was hard for =
many people (although this is anecdotal), and is a separate issue of =
contention for some. This is why I suggested the last 3 meetings, and a =
year of email so that the sample was large enough to not run in to =
particulars for each attendee who may not have been able to attend all, =
but rather some meetings.</div><div><br class=3D""></div><div>I also =
think we have ways to make meetings more affordable, but Rich indicated =
this was only one of many concerns.</div><div><br class=3D""></div><div>I =
think we need to look at a good sampling of the data at this =
point.</div><div><br =
class=3D""></div><div>Thanks,</div><div>Chris.</div><br =
class=3D""><blockquote type=3D"cite" class=3D""><div class=3D""><div =
class=3D"gmail_quote" style=3D"font-family: Helvetica; font-size: 16px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; orphans: auto; text-align: start; text-indent: =
0px; text-transform: none; white-space: normal; widows: auto; =
word-spacing: 0px; -webkit-text-stroke-width: 0px;"><div =
class=3D"">&nbsp;</div><blockquote class=3D"gmail_quote" style=3D"margin: =
0px 0px 0px 0.8ex; border-left-width: 1px; border-left-color: rgb(204, =
204, 204); border-left-style: solid; padding-left: 1ex;">Thanks,<br =
class=3D"">Chris.<br class=3D""><br class=3D""><br class=3D"">&gt;<br =
class=3D"">&gt; ---rsk</blockquote></div></div></blockquote></div><br =
class=3D""></body></html>=

--Apple-Mail=_D4478259-0B09-43A7-A021-7514F3FF37A7--

--Apple-Mail=_674C82CF-227B-44CF-B08E-C47F0E82C731
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQIcBAEBCgAGBQJXDQRKAAoJEC4dgw7XuDAlRlUQAIMZnN9Sdn957otnzQ/HmhO1
LTZCUQyDMs/tw4cGGcLzFSytvgB2FMRYllx6K00pR4jGrkUpxEOW7gtx+wnCUWkx
8SiPXe+YJgeYFPdDCooTvA1ED8IFgE8JzQMR+hq/msZbtzGCI/HzVaYcpMZ6Mm+7
ixouHVUPHxQWaFAhYJOYurZqp7qxiMAUWvSkOWzUvpTI5CXkzj02L/GOiF73p5Cx
9EIxVlGbUENOOnGqsJ3KkgIWLbXttVR5R1FBLZKpwck8ttqE5GpUkabXqxKaXUQa
oAmtGTcT2I8B3Hjs+deJ7+LW5r2L1T/EbRjTpK3YNeQVK+X4Po7LR+DkFeFUPWv7
WCjbuTJapasi1FX5xLjPNIkMEv2HsLqVT5gFvaVJ9GAiEmHtb6dQaXcrj7s4MjhO
AIzrA3szgOsq8Aqlc/oyVurVKI6tqL2l8FLNya/Xl662dRcGSXRtTYrDnxgMzrHy
oB6z4T/m2obGX+C90xajOL8pY7NHF8pnRk5PxMBE9puWkDG46aaQZ4y/HfkDgRYt
D5IoptJJQxAQi1aP/g9j69IoSCNeReJKok5A71Elf+Xq+42qxmKpnDABlnFGrshy
jUqN/0r/UrIvDNshJA09HuEfflirQOak6AKLfbzXILHFJ6CWNMJ+PdF1UjmXauyS
OHPjjwvEx6jCMZy8NqFQ
=BsK/
-----END PGP SIGNATURE-----

--Apple-Mail=_674C82CF-227B-44CF-B08E-C47F0E82C731--


From nobody Tue Apr 12 07:47:32 2016
Return-Path: <olejacobsen@me.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 E19AA12DDAB for <ietf@ietfa.amsl.com>; Tue, 12 Apr 2016 07:47:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.617
X-Spam-Level: 
X-Spam-Status: No, score=-3.617 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.996, SPF_PASS=-0.001] 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 Kip_drewCZl0 for <ietf@ietfa.amsl.com>; Tue, 12 Apr 2016 07:47:28 -0700 (PDT)
Received: from mr11p00im-asmtp003.me.com (mr11p00im-asmtp003.me.com [17.110.69.254]) (using TLSv1.2 with cipher DHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A177912E0EB for <ietf@ietf.org>; Tue, 12 Apr 2016 07:47:26 -0700 (PDT)
Received: from [10.1.10.8] (173-11-110-134-SFBA.hfc.comcastbusiness.net [173.11.110.134]) by mr11p00im-asmtp003.me.com (Oracle Communications Messaging Server 7.0.5.36.0 64bit (built Sep 8 2015)) with ESMTPSA id <0O5I00K1FZR1XO10@mr11p00im-asmtp003.me.com> for ietf@ietf.org; Tue, 12 Apr 2016 14:47:26 +0000 (GMT)
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, definitions=2016-04-12_07:,, signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 clxscore=1015 suspectscore=0 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1510270003 definitions=main-1604120209
Date: Tue, 12 Apr 2016 07:47:25 -0700 (PDT)
From: Ole Jacobsen <olejacobsen@me.com>
To: Loa Andersson <loa@pi.nu>
Subject: Re: Concerns about Singapore
In-reply-to: <570CF594.5070509@pi.nu>
Message-id: <alpine.OSX.2.01.1604120745250.52880@rabdullah.local>
References: <m260vp7eke.wl%randy@psg.com> <570A6458.3050206@comcast.net> <m21t6d7c9t.wl%randy@psg.com> <570A67B4.3010206@comcast.net> <570AB3AF.2050401@gmail.com> <87twj99c6w.fsf@tops.chopps.org> <CAKe6YvMyp-DyeDwpPY6KYmbDbnpgnvVk_cUStnA32wmgDWcz3w@mail.gmail.com> <BBF5DDFE515C3946BC18D733B20DAD233A62AA18@XMB122CNC.rim.net> <20160411104519.GA19092@gsp.org> <3F48466D-390C-4C18-B958-732AE3E46FF1@gmail.com> <20160411223403.GA6743@gsp.org> <CAPt1N1nNo0=JSptQdWRZCFy1v-m6Q8NQy4WVGHtnRJuFZFmMig@mail.gmail.com> <CAKr6gn1KmNcgNwbPHZWB2aJQAuchz4eB7gxJhV2Dsbc1Z50kDw@mail.gmail.com> <CAPt1N1mWjg_-525avYJ4PnSECYQrtpVFJCXPfH=PryJ8q0vy4Q@mail.gmail.com> <A684A3C4-7161-49F5-919E-A5F948A3F316@ecs.soton.ac.uk> <EMEW3|d5cb2cb80712b3716e1ab4e2a54c9430s3BCG403tjc|ecs.soton.ac.uk|A684A3C4-7161-49F5-919E-A5F948A3F316@ecs.soton.ac.uk> <570CF594.5070509@pi.nu>
User-Agent: Alpine 2.01 (OSX 1266 2009-07-14)
MIME-version: 1.0
Content-type: TEXT/PLAIN; charset=US-ASCII
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/vGRHuL0hEakGos-nViwvIbn6WEQ>
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: Ole Jacobsen <olejacobsen@me.com>
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: Tue, 12 Apr 2016 14:47:31 -0000

You said:

"I don't think anything that is within our power to do can change this
perception."

Perhaps some information from "the ground" and from frequent visitors
to Singapore who would have concerns about these issue *might* help.

Let's gather the data before we throw the baby out with the bath water
so to speak.

Ole


Ole J. Jacobsen
Editor and Publisher
The Internet Protocol Journal
Office:  +1 415-550-9433
Cell:    +1 415-370-4628
docomo: (090) 3337-9311
Web: protocoljournal.org
E-mail: olejacobsen@me.com





From nobody Tue Apr 12 08:03:12 2016
Return-Path: <prvs=90323f149=theodore.v.faber@aero.org>
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 33E7B12EEE2 for <ietf@ietfa.amsl.com>; Tue, 12 Apr 2016 08:03:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.896
X-Spam-Level: 
X-Spam-Status: No, score=-2.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RP_MATCHES_RCVD=-0.996] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=neutral reason="invalid (public key: not available)" header.d=aero.org header.b=fmuyx3XE; dkim=pass (1024-bit key) header.d=aerospacecloud.onmicrosoft.com header.b=JCHsPw6r
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 q37gP_v3rofp for <ietf@ietfa.amsl.com>; Tue, 12 Apr 2016 08:03:08 -0700 (PDT)
Received: from email3-east.aero.org (email3-east.aero.org [130.221.184.167]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 152F912E590 for <ietf@ietf.org>; Tue, 12 Apr 2016 08:03:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=aero.org; i=@aero.org; q=dns/txt; s=mailhub; t=1460473388; x=1492009388; h=from:to:cc:subject:date:message-id:references: content-transfer-encoding:mime-version; bh=HTSW+nxCq0n8cyQPCQ+tbh1lCleSKFOyYC7BttByCg4=; b=fmuyx3XEkvWSYQyGqEGrOZcoz5c2r8a34Jr11gD9NMfkrBAKddbyX7Hq ObVYaFG2U7B1PD7iyw9/YUUNw25PYcfKqu+wFdHjXnGPn9hzOwFDKnRd6 YrhOFrfefGGLmyQlefchtI19mwKYIjoISJ8EV7j/fi/iFZsmmejnxNBoy 0=;
x-SBRS: None
x-SenderGroup: Inbound_Office365
X-IronPort-AV: E=McAfee;i="5700,7163,8133"; a="2567281"
X-IronPort-AV: E=Sophos;i="5.24,474,1454994000";  d="scan'208";a="2567281"
X-IPAS-Result: A2HjAQDEDQ1X/xbGZxdbAw4LAQEBAYNtfQa6YAENgXQZhXQCgWsUAQEBAQEBAQNiJ4I3ODwBAQEBAQEjAg0nOAEBAQMSAScGAQE3AQ8CAQgOCh4QMiUCBAENBQgSCIdxAxKhCQGBJwEcYQUoAopohSgBBIgvGIUCAQEBAQEBAQEBAQEBAQEBAQEBAQEBDwIEimyEPQIhJoJkgiuYDYV3lyaPJx4BAUKBdwwagQ87bAGJBgF9AQEB
Received: from mail-cy1gcc01lp0022.outbound.protection.outlook.com (HELO gcc01-CY1-obe.outbound.protection.outlook.com) ([23.103.198.22]) by email3-east.aero.org with ESMTP/TLS/AES256-SHA; 12 Apr 2016 11:03:05 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aerospacecloud.onmicrosoft.com; s=selector1-aero-org; h=From:To:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=oxT/lLSubOxKq9qIjTkSint+dkwSjo2ncwtgCh2agpY=; b=JCHsPw6rTlzK9fa5sSlnTqKh7DzmK7/QyJXjw8rJUSoDVZsl1JwF0LcMBP0XUv4Z35fNMg+vEzzhsSbmVmhrqcFEz6TM0CSL2EF/68xFjombxzZW7KNuF5U64YwyXxb35YhdFanmkOAQN3PA++dju6+jC6uf5yV7BagZsl5bOgc=
Received: from DM2PR09MB0336.namprd09.prod.outlook.com (10.160.247.153) by DM2PR09MB0336.namprd09.prod.outlook.com (10.160.247.153) with Microsoft SMTP Server (TLS) id 15.1.453.26; Tue, 12 Apr 2016 15:02:45 +0000
Received: from DM2PR09MB0336.namprd09.prod.outlook.com ([10.160.247.153]) by DM2PR09MB0336.namprd09.prod.outlook.com ([10.160.247.153]) with mapi id 15.01.0453.029; Tue, 12 Apr 2016 15:02:45 +0000
From: Theodore V Faber <theodore.v.faber@aero.org>
To: Ted Lemon <mellon@fugue.com>, Tim Chown <tjc@ecs.soton.ac.uk>
Subject: Re: Concerns about Singapore
Thread-Topic: Concerns about Singapore
Thread-Index: AQHRkOMTs3DHSqtWXUaKt2vKlrce+A==
Date: Tue, 12 Apr 2016 15:02:45 +0000
Message-ID: <DM2PR09MB033626C01645A605418ED967B9950@DM2PR09MB0336.namprd09.prod.outlook.com>
References: <m260vp7eke.wl%randy@psg.com> <570A6458.3050206@comcast.net> <m21t6d7c9t.wl%randy@psg.com> <570A67B4.3010206@comcast.net> <570AB3AF.2050401@gmail.com> <87twj99c6w.fsf@tops.chopps.org> <CAKe6YvMyp-DyeDwpPY6KYmbDbnpgnvVk_cUStnA32wmgDWcz3w@mail.gmail.com> <BBF5DDFE515C3946BC18D733B20DAD233A62AA18@XMB122CNC.rim.net> <20160411104519.GA19092@gsp.org> <3F48466D-390C-4C18-B958-732AE3E46FF1@gmail.com> <20160411223403.GA6743@gsp.org> <DDFE7AA1-4C07-4944-AECA-EA361A3A0B71@ecs.soton.ac.uk> <CAPt1N1nNo0=JSptQdWRZCFy1v-m6Q8NQy4WVGHtnRJuFZFmMig@mail.gmail.com> <EMEW3|9aaa87920b361e2e71efe9c7005e927cs3BChQ03tjc|ecs.soton.ac.uk|DDFE7AA1-4C07-4944-AECA-EA361A3A0B71@ecs.soton.ac.uk> <CAPt1N1nucCAg99gVDWOHVE2up=2xK0Qm2Ud81hUhp4ryHRmwPA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: fugue.com; dkim=none (message not signed) header.d=none;fugue.com; dmarc=none action=none header.from=aero.org;
x-originating-ip: [130.221.224.7]
x-ms-office365-filtering-correlation-id: a259bce0-3336-4541-ca1c-08d362e3816a
x-microsoft-exchange-diagnostics: 1; DM2PR09MB0336; 5:VBv5R0WdWOVrBbyVkcdvJCQ2kbnSVdLQ1GSOWvRZbaHuyIo6UjHXPHR3GRlBNyYJDXpNCOq68LMmESI/pwFIWVv2CLaWimli9205lC/llWQXmye0cWp7obiIuNjtQYIac6oEK1Vqa0TmE5UgLrqMcg==; 24:bErMzGnQN1dm+xRewQwHZ7slo2I7cxQGBLUdmHfsrBaH+cRKUfyE+KEjEln9QCKITm5B9+AYkajmaBVTjbuEXF+RINt93YsHXpWU/HPwgII=
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:DM2PR09MB0336;
x-microsoft-antispam-prvs: <DM2PR09MB0336CA8E327F8EEB0BCAB1C2B9950@DM2PR09MB0336.namprd09.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(601004)(2401047)(5005006)(8121501046)(3002001)(10201501046); SRVR:DM2PR09MB0336; BCL:0; PCL:0; RULEID:; SRVR:DM2PR09MB0336; 
x-forefront-prvs: 0910AAF391
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(6009001)(54524002)(51444003)(24454002)(3480700003)(3846002)(3660700001)(4326007)(6116002)(102836003)(1220700001)(586003)(1096002)(77096005)(2900100001)(5004730100002)(15975445007)(10400500002)(9686002)(5003600100002)(5001770100001)(92566002)(5002640100001)(3280700002)(81166005)(11100500001)(575784001)(50986999)(99286002)(76176999)(54356999)(2906002)(189998001)(19580395003)(122556002)(66066001)(76576001)(33656002)(19580405001)(5008740100001)(106116001)(86362001)(87936001)(74316001)(93886004); DIR:OUT; SFP:1101; SCL:1; SRVR:DM2PR09MB0336; H:DM2PR09MB0336.namprd09.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en; 
spamdiagnosticoutput: 1:23
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: aero.org
X-MS-Exchange-CrossTenant-originalarrivaltime: 12 Apr 2016 15:02:45.4604 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: c8294700-c5a4-4ca1-a876-1457d39899fd
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM2PR09MB0336
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/C5JsNmbmH0SPlt8dM0U-V0cP7mA>
Cc: ietf <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: Tue, 12 Apr 2016 15:03:10 -0000

-----BEGIN PGP SIGNED MESSAGE-----=0A=
Hash: SHA512=0A=
=0A=
On 4/12/16 04:50, Ted Lemon wrote:=0A=
> Agree about Buenos Aires.   We already do excellent virtual=0A=
> interims--I think if your standard for whether we can do a virtual=0A=
> IETF is that virtual interims work, we are already there.=0A=
> =0A=
> I think that if we want to test this idea, what we need to do is =0A=
> designate some future IETF virtual _now_, and then start=0A=
> preparing, rather than say "oh, we should do a virtual" and then=0A=
> dither about when we might be ready.   We will never be so ready=0A=
> that a virtual IETF feels identical to an in-person IETF, so let's=0A=
> just abandon that idea and get started on making a virtual IETF=0A=
> that, while different, is still a success.=0A=
=0A=
+1 on the approach.  I'm not a huge proponent of virtual meetings, but=0A=
setting deadlines motivates us.  This should not be news to anyone.=0A=
=0A=
- -- =0A=
Ted Faber <theodore.v.faber@aero.org>=0A=
Engineering Specialist=0A=
Computer Systems Research Department=0A=
310-336-7373=0A=
-----BEGIN PGP SIGNATURE-----=0A=
Comment: GPGTools - https://gpgtools.org=0A=
=0A=
iQIcBAEBCgAGBQJXDQ4UAAoJEFNjQnOBW8uOb8wP/jE8U9OcbcRzjTRphDMJ2svI=0A=
5TP/DFtwy/IvJhoOiE75YDtFOTr9I4hVC7FjX/cCrCWuG+nna7xAFWIPjU3JE5MU=0A=
8C+O39eb6kAsR1huFksG1EHR5SHa3hzzNuHG+gRgW9KwRGyv0TvT5D69Kh0T0L+Y=0A=
cl0clJ9qceRSnWuNYUeRBRMC6dJi0JIlHnROSCC1EEfc3rBIN5pquhNQy7qrlCsG=0A=
ecrjlKhtbpOc8FKOEC9Ao003hwnT/2N30FpOOYaXgDubmhdkiY50jIwa7p3AhJYu=0A=
bFFLYgft1DuHnmBreuRVYYmM2wa5peGbDPZhLjYPoWxtnMGU9cvju9e0Lozg7cJZ=0A=
GKiHtPzJ9O+pgcobN11fi6b9BXB0KM1Qd/ZpiBSmqcuS+7q+aLorja9gWo5kb9Ar=0A=
10WAPAWzcRxUQBbS9fCp3kLdyxuI0JBAZkn/vQpgm2DTOlF42kIqPxKfMPhs7MJt=0A=
s1jeEImmBi3mhayey/fgO6u2QO8sNUKj8NztaAWw02PH2eZPO52q3bt6NCHo61at=0A=
ZZLkcH5k4k3gOEm9W5K/0c1XQwONEXMZla7NzVcuVI8ujlyArk4Igu2PEHrtYK/d=0A=
I2dDvVE1KNgWexd0fQksdSTF28hiDHzJP9vwljAUmx+MrIDD1UwtFOnoYGT+7+Pj=0A=
gUnFPIcRE+95ID6+WF8L=0A=
=3DfPsz=0A=
-----END PGP SIGNATURE-----=0A=


From nobody Tue Apr 12 08:42:25 2016
Return-Path: <jmh@joelhalpern.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 BF3A612F00E for <ietf@ietfa.amsl.com>; Tue, 12 Apr 2016 08:42:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.702
X-Spam-Level: 
X-Spam-Status: No, score=-2.702 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=joelhalpern.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 Dtv6Yrr3xqSj for <ietf@ietfa.amsl.com>; Tue, 12 Apr 2016 08:42:23 -0700 (PDT)
Received: from mailb2.tigertech.net (mailb2.tigertech.net [208.80.4.154]) (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 772DC12F012 for <ietf@ietf.org>; Tue, 12 Apr 2016 08:42:23 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id 473821C0663; Tue, 12 Apr 2016 08:42:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=1.tigertech; t=1460475743; bh=4KPFSC3+bw7cxE4jAp1x+gNVqOpBWdKjgftUIGaNp7w=; h=Subject:To:References:Cc:From:Date:In-Reply-To:From; b=HJ4SFuXIwG98rJ7FneeTUwaLm3+BlZ7f4qt2WipItaGxAi8Ir146LlnU86R+/Ec4j pMmCKnmUTHmGK5dtZdiKH/LUSndPQ1o/cAWO7dyBKS73yXZtRaUPdkJJ0MixQP5KGQ TaGcGoWHxuefKJtV+LDZ4GrW3sVd4L34oxd4Ani8=
X-Virus-Scanned: Debian amavisd-new at b2.tigertech.net
Received: from Joels-MacBook-Pro.local (209-255-163-147.ip.mcleodusa.net [209.255.163.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mailb2.tigertech.net (Postfix) with ESMTPSA id 6E60B540060; Tue, 12 Apr 2016 08:42:22 -0700 (PDT)
Subject: Re: Remote only meetings? [Re: Concerns about Singapore]
To: Mary Barnes <mary.h.barnes@gmail.com>, chopps@chopps.org
References: <570AB3AF.2050401@gmail.com> <87twj99c6w.fsf@tops.chopps.org> <CAKe6YvMyp-DyeDwpPY6KYmbDbnpgnvVk_cUStnA32wmgDWcz3w@mail.gmail.com> <BBF5DDFE515C3946BC18D733B20DAD233A62AA18@XMB122CNC.rim.net> <20160411104519.GA19092@gsp.org> <3F48466D-390C-4C18-B958-732AE3E46FF1@gmail.com> <20160411223403.GA6743@gsp.org> <87twj7eon7.fsf@tops.chopps.org> <20160412110839.GA20488@gsp.org> <8760vn82f2.fsf@tops.chopps.org> <20160412124639.GA27223@gsp.org> <87fuurgd8f.fsf@tops.chopps.org> <CABmDk8kCfTB_AKyqV4X+AghL2G7i+XcKR=tzV0jybM05k+UU4Q@mail.gmail.com>
From: "Joel M. Halpern" <jmh@joelhalpern.com>
Message-ID: <570D175A.1040001@joelhalpern.com>
Date: Tue, 12 Apr 2016 11:42:18 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:38.0) Gecko/20100101 Thunderbird/38.7.2
MIME-Version: 1.0
In-Reply-To: <CABmDk8kCfTB_AKyqV4X+AghL2G7i+XcKR=tzV0jybM05k+UU4Q@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/Bay0tP6kfj4A2mQtkMOvkp9AYGY>
Cc: Rich Kulawiec <rsk@gsp.org>, "<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: Tue, 12 Apr 2016 15:42:25 -0000

I believe that there would be a real cost in moving to remote-only 
meetings.  Even putting aside the time zone difficulties, and the 
reduced effectiveness of in-meeting interaction, there are aspects of 
face-to-face interaction taht current remote technologies simply do not 
capture.
It was very helpful in BA (and at many previous IETF meetings) to be 
able to find time to talk with a small number of people concerned about 
an aspect of one working group.  I did that over meals, breaks, etc.  It 
sorted out issues far more effectively than email conversations (in 
several cases, we had tried to sort it out via email.  10 minutes 
face-to-face clarified what was being missed, and found a good path 
forward.)

Even in-meeting, when the meeting works well it takes advantage of the 
nature of face-to-face interactions.  Admittedly, many sessions do not 
need this, but many do.

Yours,
Joel

On 4/12/16 10:09 AM, Mary Barnes wrote:
>
>
> On Tue, Apr 12, 2016 at 8:37 AM, <chopps@chopps.org
> <mailto:chopps@chopps.org>> wrote:
>
>
>     Rich Kulawiec <rsk@gsp.org <mailto:rsk@gsp.org>> writes:
>
>     > On Tue, Apr 12, 2016 at 07:57:53AM -0400,chopps@chopps.org <mailto:chopps@chopps.org> wrote:
>     >> Your suggestion of not having them would subtract value from the process
>     >> though. I don't see the win.
>     >
>     > The win is that all of the time and effort and expense (all of which
>     > are finite resources) that go into those could be directed elsewhere.
>
>     The meetings and their fees are income positive, they aren't a drain on
>     resource, the opposite in fact.
>
> [MB] I would agree when it comes to dollars, but people (i.e., the
> effort to which Rich is referring) are also a resource and volunteers do
> the work.  If the only volunteers you get are from large companies, I
> think the IETF does lose.  With improved remote participation,
> individuals that aren't sponsored by large companies can continue to
> contribute.  Without it, we become ineffective.  [/MB]
>
>
>     > These meetings select for a highly limited (by circumstance, by necessity,
>     > and by choice) subset.  And once upon a time, when the 'net was much
>     > younger and more limited in terms of geography and scope, that might
>     > have been alright, because the subset mapped fairly well onto the larger
>     > set of people involved in networking.  But that's no longer true.
>     > And the difficulties/expense of travel are only going to get worse
>     > for the forseeable future: they're not going to get better.
>
>     I think it would be useful to get some real data to measure exactly how
>     highly limited that subset of people are. Perhaps as a simple first
>     shot we could take email sent to IETF working group mailing lists over
>     the last year, and cross reference that against the registrations lists
>     of the last 3 IETFs and see what percentage of people doing IETF work
>     cannot or choose not to attend the on-site meetings?
>
> [MB] There was a separate list of registered remote attendees for this
> recent meeting. You can take a look there and see a number of long time
> contributors and some WG chairs (myself included) that have participated
> remotely.  The very reason I did not go was due to lack of funding.
> There are a number of us that have contributed significantly over the
> past 15-30 years that would like to continue to do so but as independent
> consultants, some of these trips are just not fiscally possible.  I went
> to Yokohama so couldn't even entertain the idea of attending the meeting
> in BA without a sponsor.    And, I seriously doubt I can continue as a
> WG chair if I can't get funding in the future.  So, in the end, the
> current model self selects and benefits the larger companies over
> individuals that really do want to do work for the "good of the
> Internet" but just can't justify the expense.   [/MB]
>
>     Thanks,
>     Chris.
>
>
>      >
>      > ---rsk
>
>


From nobody Tue Apr 12 09:01:49 2016
Return-Path: <mellon@fugue.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 D273F12D61C for <ietf@ietfa.amsl.com>; Tue, 12 Apr 2016 09:01:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.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 c0AHr5aX1XVd for <ietf@ietfa.amsl.com>; Tue, 12 Apr 2016 09:01:42 -0700 (PDT)
Received: from mail-lf0-x22a.google.com (mail-lf0-x22a.google.com [IPv6:2a00:1450:4010:c07::22a]) (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 7788612D932 for <ietf@ietf.org>; Tue, 12 Apr 2016 09:01:41 -0700 (PDT)
Received: by mail-lf0-x22a.google.com with SMTP id e190so31996369lfe.0 for <ietf@ietf.org>; Tue, 12 Apr 2016 09:01:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=wQjd4wNmVRWElM+FJCvogbvJhkEV4r5v1uYfEayR0RQ=; b=r/nsBprEjubY57EnRmMIVONiPH5duFnzmP0JUxaGGzgpiHcakUceYDEHO4FZVpwBjm e7xf5dPDBqA0Yn7gw68z7GNsm/DPiVIFrgLTX6hQ6jshXkoDnu0Wey4nlsWBcZSQd/cY 40Kh2VLLLs2Es+iKKFP/qntIGe1J/MHqWnZHVIh08ScviT+3ZY6El3apz/zin1W09zC0 1ttgZx2BstZnr0OcgK19HBWYpma3XVaGpEoQ5mC6PU+7RUQL3yZ0D9AtT/34zyRGoTcJ 35geIF0F5NyH2t2scV5MJgO5n7vHsPgQk64wil0xe2VfejHfZEusZm/Fh6RrDnBNF06O 5LyA==
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=wQjd4wNmVRWElM+FJCvogbvJhkEV4r5v1uYfEayR0RQ=; b=E40k0bbfuvBVVPhuvdIbzSNeYf7h7ui7vV2ZjvcBFUYdWepls9Lm7y+KshOsYw9f9R eqmknU8OBPiiZ4Odz1DRbwJYxdvMOTdqfl3jgd7tlkMhWIjxT4U/5HKpT0ZKce3T/h1R 4vB1tSB1u/FHKdpOtfoQnRdxOu5V02r+PND8C5ZEE8fiHh7+q2bp+MZpVo4JboXLRbQb /Gyn12e8AHaBv8PaHPqH3jrY8/ny3dItY725JAeaxfe8PgAZqqLP8emvPNTQ9grHfmvv k66bXKliIYGQ7hI1fSv63ISHqUwVsz/8Bl9bCmpLp5uw0Q74J4JPdztuthx1Czvdnuf4 hckw==
X-Gm-Message-State: AOPr4FWs7MWZxL3E8ZddHCm2fMG1WNB5T0VWz1utK0lLZfec8UHo/YOTnj4w/ULnWrq9XaRRUw9QzycJvjDNYg==
X-Received: by 10.25.148.208 with SMTP id w199mr1806884lfd.124.1460476899650;  Tue, 12 Apr 2016 09:01:39 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.25.40.136 with HTTP; Tue, 12 Apr 2016 09:00:59 -0700 (PDT)
X-Originating-IP: [71.233.41.235]
In-Reply-To: <570D175A.1040001@joelhalpern.com>
References: <570AB3AF.2050401@gmail.com> <87twj99c6w.fsf@tops.chopps.org> <CAKe6YvMyp-DyeDwpPY6KYmbDbnpgnvVk_cUStnA32wmgDWcz3w@mail.gmail.com> <BBF5DDFE515C3946BC18D733B20DAD233A62AA18@XMB122CNC.rim.net> <20160411104519.GA19092@gsp.org> <3F48466D-390C-4C18-B958-732AE3E46FF1@gmail.com> <20160411223403.GA6743@gsp.org> <87twj7eon7.fsf@tops.chopps.org> <20160412110839.GA20488@gsp.org> <8760vn82f2.fsf@tops.chopps.org> <20160412124639.GA27223@gsp.org> <87fuurgd8f.fsf@tops.chopps.org> <CABmDk8kCfTB_AKyqV4X+AghL2G7i+XcKR=tzV0jybM05k+UU4Q@mail.gmail.com> <570D175A.1040001@joelhalpern.com>
From: Ted Lemon <mellon@fugue.com>
Date: Tue, 12 Apr 2016 12:00:59 -0400
Message-ID: <CAPt1N1n0_UJ5AVzO=dyvzeLtYi0b8g5894wyhctwPwqTzme-PQ@mail.gmail.com>
Subject: Re: Remote only meetings? [Re: Concerns about Singapore]
To: "Joel M. Halpern" <jmh@joelhalpern.com>
Content-Type: multipart/alternative; boundary=001a1140234cce878905304bc6f2
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/vuhcr5GPExfN4Z6_jKJBEnz0two>
Cc: Rich Kulawiec <rsk@gsp.org>, "<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: Tue, 12 Apr 2016 16:01:46 -0000

--001a1140234cce878905304bc6f2
Content-Type: text/plain; charset=UTF-8

This is all true, but the idea that it can't be replicated online is silly.
  How did you arrange to have lunch with these people?   You went looking
for them, rounded them up, and sat down to lunch.   You can do that online
as well.

It is certainly true that random conversation in the halls can also happen
and lead to useful consequences, but having taken heavy advantage of
"running into people" in BA, I can tell you that a lot of it was
deliberate, and the parts that weren't probably would have been triggered
by WG meetings even if they hadn't been triggered by just running into
someone familiar in the lobby of the Hilton.


On Tue, Apr 12, 2016 at 11:42 AM, Joel M. Halpern <jmh@joelhalpern.com>
wrote:

> I believe that there would be a real cost in moving to remote-only
> meetings.  Even putting aside the time zone difficulties, and the reduced
> effectiveness of in-meeting interaction, there are aspects of face-to-face
> interaction taht current remote technologies simply do not capture.
> It was very helpful in BA (and at many previous IETF meetings) to be able
> to find time to talk with a small number of people concerned about an
> aspect of one working group.  I did that over meals, breaks, etc.  It
> sorted out issues far more effectively than email conversations (in several
> cases, we had tried to sort it out via email.  10 minutes face-to-face
> clarified what was being missed, and found a good path forward.)
>
> Even in-meeting, when the meeting works well it takes advantage of the
> nature of face-to-face interactions.  Admittedly, many sessions do not need
> this, but many do.
>
> Yours,
> Joel
>
> On 4/12/16 10:09 AM, Mary Barnes wrote:
>
>>
>>
>> On Tue, Apr 12, 2016 at 8:37 AM, <chopps@chopps.org
>> <mailto:chopps@chopps.org>> wrote:
>>
>>
>>     Rich Kulawiec <rsk@gsp.org <mailto:rsk@gsp.org>> writes:
>>
>>
>>     > On Tue, Apr 12, 2016 at 07:57:53AM -0400,chopps@chopps.org <mailto:
>> chopps@chopps.org> wrote:
>>     >> Your suggestion of not having them would subtract value from the
>> process
>>     >> though. I don't see the win.
>>     >
>>     > The win is that all of the time and effort and expense (all of which
>>     > are finite resources) that go into those could be directed
>> elsewhere.
>>
>>     The meetings and their fees are income positive, they aren't a drain
>> on
>>     resource, the opposite in fact.
>>
>> [MB] I would agree when it comes to dollars, but people (i.e., the
>> effort to which Rich is referring) are also a resource and volunteers do
>> the work.  If the only volunteers you get are from large companies, I
>> think the IETF does lose.  With improved remote participation,
>> individuals that aren't sponsored by large companies can continue to
>> contribute.  Without it, we become ineffective.  [/MB]
>>
>>
>>     > These meetings select for a highly limited (by circumstance, by
>> necessity,
>>     > and by choice) subset.  And once upon a time, when the 'net was much
>>     > younger and more limited in terms of geography and scope, that might
>>     > have been alright, because the subset mapped fairly well onto the
>> larger
>>     > set of people involved in networking.  But that's no longer true.
>>     > And the difficulties/expense of travel are only going to get worse
>>     > for the forseeable future: they're not going to get better.
>>
>>     I think it would be useful to get some real data to measure exactly
>> how
>>     highly limited that subset of people are. Perhaps as a simple first
>>     shot we could take email sent to IETF working group mailing lists over
>>     the last year, and cross reference that against the registrations
>> lists
>>     of the last 3 IETFs and see what percentage of people doing IETF work
>>     cannot or choose not to attend the on-site meetings?
>>
>> [MB] There was a separate list of registered remote attendees for this
>> recent meeting. You can take a look there and see a number of long time
>> contributors and some WG chairs (myself included) that have participated
>> remotely.  The very reason I did not go was due to lack of funding.
>> There are a number of us that have contributed significantly over the
>> past 15-30 years that would like to continue to do so but as independent
>> consultants, some of these trips are just not fiscally possible.  I went
>> to Yokohama so couldn't even entertain the idea of attending the meeting
>> in BA without a sponsor.    And, I seriously doubt I can continue as a
>> WG chair if I can't get funding in the future.  So, in the end, the
>> current model self selects and benefits the larger companies over
>> individuals that really do want to do work for the "good of the
>> Internet" but just can't justify the expense.   [/MB]
>>
>>     Thanks,
>>     Chris.
>>
>>
>>      >
>>      > ---rsk
>>
>>
>>
>

--001a1140234cce878905304bc6f2
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">This is all true, but the idea that it can&#39;t be replic=
ated online is silly. =C2=A0 How did you arrange to have lunch with these p=
eople? =C2=A0 You went looking for them, rounded them up, and sat down to l=
unch. =C2=A0 You can do that online as well.<div><br></div><div>It is certa=
inly true that random conversation in the halls can also happen and lead to=
 useful consequences, but having taken heavy advantage of &quot;running int=
o people&quot; in BA, I can tell you that a lot of it was deliberate, and t=
he parts that weren&#39;t probably would have been triggered by WG meetings=
 even if they hadn&#39;t been triggered by just running into someone famili=
ar in the lobby of the Hilton.</div><div><br></div></div><div class=3D"gmai=
l_extra"><br><div class=3D"gmail_quote">On Tue, Apr 12, 2016 at 11:42 AM, J=
oel M. Halpern <span dir=3D"ltr">&lt;<a href=3D"mailto:jmh@joelhalpern.com"=
 target=3D"_blank">jmh@joelhalpern.com</a>&gt;</span> wrote:<br><blockquote=
 class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc soli=
d;padding-left:1ex">I believe that there would be a real cost in moving to =
remote-only meetings.=C2=A0 Even putting aside the time zone difficulties, =
and the reduced effectiveness of in-meeting interaction, there are aspects =
of face-to-face interaction taht current remote technologies simply do not =
capture.<br>
It was very helpful in BA (and at many previous IETF meetings) to be able t=
o find time to talk with a small number of people concerned about an aspect=
 of one working group.=C2=A0 I did that over meals, breaks, etc.=C2=A0 It s=
orted out issues far more effectively than email conversations (in several =
cases, we had tried to sort it out via email.=C2=A0 10 minutes face-to-face=
 clarified what was being missed, and found a good path forward.)<br>
<br>
Even in-meeting, when the meeting works well it takes advantage of the natu=
re of face-to-face interactions.=C2=A0 Admittedly, many sessions do not nee=
d this, but many do.<br>
<br>
Yours,<br>
Joel<span class=3D""><br>
<br>
On 4/12/16 10:09 AM, Mary Barnes wrote:<br>
</span><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-=
left:1px #ccc solid;padding-left:1ex"><span class=3D"">
<br>
<br>
On Tue, Apr 12, 2016 at 8:37 AM, &lt;<a href=3D"mailto:chopps@chopps.org" t=
arget=3D"_blank">chopps@chopps.org</a><br></span>
&lt;mailto:<a href=3D"mailto:chopps@chopps.org" target=3D"_blank">chopps@ch=
opps.org</a>&gt;&gt; wrote:<br>
<br>
<br>
=C2=A0 =C2=A0 Rich Kulawiec &lt;<a href=3D"mailto:rsk@gsp.org" target=3D"_b=
lank">rsk@gsp.org</a> &lt;mailto:<a href=3D"mailto:rsk@gsp.org" target=3D"_=
blank">rsk@gsp.org</a>&gt;&gt; writes:<div><div class=3D"h5"><br>
<br>
=C2=A0 =C2=A0 &gt; On Tue, Apr 12, 2016 at 07:57:53AM -0400,<a href=3D"mail=
to:chopps@chopps.org" target=3D"_blank">chopps@chopps.org</a> &lt;mailto:<a=
 href=3D"mailto:chopps@chopps.org" target=3D"_blank">chopps@chopps.org</a>&=
gt; wrote:<br>
=C2=A0 =C2=A0 &gt;&gt; Your suggestion of not having them would subtract va=
lue from the process<br>
=C2=A0 =C2=A0 &gt;&gt; though. I don&#39;t see the win.<br>
=C2=A0 =C2=A0 &gt;<br>
=C2=A0 =C2=A0 &gt; The win is that all of the time and effort and expense (=
all of which<br>
=C2=A0 =C2=A0 &gt; are finite resources) that go into those could be direct=
ed elsewhere.<br>
<br>
=C2=A0 =C2=A0 The meetings and their fees are income positive, they aren&#3=
9;t a drain on<br>
=C2=A0 =C2=A0 resource, the opposite in fact.<br>
<br>
[MB] I would agree when it comes to dollars, but people (i.e., the<br>
effort to which Rich is referring) are also a resource and volunteers do<br=
>
the work.=C2=A0 If the only volunteers you get are from large companies, I<=
br>
think the IETF does lose.=C2=A0 With improved remote participation,<br>
individuals that aren&#39;t sponsored by large companies can continue to<br=
>
contribute.=C2=A0 Without it, we become ineffective.=C2=A0 [/MB]<br>
<br>
<br>
=C2=A0 =C2=A0 &gt; These meetings select for a highly limited (by circumsta=
nce, by necessity,<br>
=C2=A0 =C2=A0 &gt; and by choice) subset.=C2=A0 And once upon a time, when =
the &#39;net was much<br>
=C2=A0 =C2=A0 &gt; younger and more limited in terms of geography and scope=
, that might<br>
=C2=A0 =C2=A0 &gt; have been alright, because the subset mapped fairly well=
 onto the larger<br>
=C2=A0 =C2=A0 &gt; set of people involved in networking.=C2=A0 But that&#39=
;s no longer true.<br>
=C2=A0 =C2=A0 &gt; And the difficulties/expense of travel are only going to=
 get worse<br>
=C2=A0 =C2=A0 &gt; for the forseeable future: they&#39;re not going to get =
better.<br>
<br>
=C2=A0 =C2=A0 I think it would be useful to get some real data to measure e=
xactly how<br>
=C2=A0 =C2=A0 highly limited that subset of people are. Perhaps as a simple=
 first<br>
=C2=A0 =C2=A0 shot we could take email sent to IETF working group mailing l=
ists over<br>
=C2=A0 =C2=A0 the last year, and cross reference that against the registrat=
ions lists<br>
=C2=A0 =C2=A0 of the last 3 IETFs and see what percentage of people doing I=
ETF work<br>
=C2=A0 =C2=A0 cannot or choose not to attend the on-site meetings?<br>
<br>
[MB] There was a separate list of registered remote attendees for this<br>
recent meeting. You can take a look there and see a number of long time<br>
contributors and some WG chairs (myself included) that have participated<br=
>
remotely.=C2=A0 The very reason I did not go was due to lack of funding.<br=
>
There are a number of us that have contributed significantly over the<br>
past 15-30 years that would like to continue to do so but as independent<br=
>
consultants, some of these trips are just not fiscally possible.=C2=A0 I we=
nt<br>
to Yokohama so couldn&#39;t even entertain the idea of attending the meetin=
g<br>
in BA without a sponsor.=C2=A0 =C2=A0 And, I seriously doubt I can continue=
 as a<br>
WG chair if I can&#39;t get funding in the future.=C2=A0 So, in the end, th=
e<br>
current model self selects and benefits the larger companies over<br>
individuals that really do want to do work for the &quot;good of the<br>
Internet&quot; but just can&#39;t justify the expense.=C2=A0 =C2=A0[/MB]<br=
>
<br>
=C2=A0 =C2=A0 Thanks,<br>
=C2=A0 =C2=A0 Chris.<br>
<br>
<br>
=C2=A0 =C2=A0 =C2=A0&gt;<br>
=C2=A0 =C2=A0 =C2=A0&gt; ---rsk<br>
<br>
<br>
</div></div></blockquote>
<br>
</blockquote></div><br></div>

--001a1140234cce878905304bc6f2--


From nobody Tue Apr 12 09:15:09 2016
Return-Path: <jmh@joelhalpern.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 F361A12E3BB for <ietf@ietfa.amsl.com>; Tue, 12 Apr 2016 09:15:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.702
X-Spam-Level: 
X-Spam-Status: No, score=-2.702 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=joelhalpern.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 ViGi3NiQpNiz for <ietf@ietfa.amsl.com>; Tue, 12 Apr 2016 09:15:06 -0700 (PDT)
Received: from mailb2.tigertech.net (mailb2.tigertech.net [208.80.4.154]) (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 3050112E1F1 for <ietf@ietf.org>; Tue, 12 Apr 2016 09:15:05 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id 037511C024F; Tue, 12 Apr 2016 09:15:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=1.tigertech; t=1460477705; bh=w/tgptt8f82FWUyyiz71Dutp9PuCJH7SFALiJHuOZWw=; h=Subject:To:References:Cc:From:Date:In-Reply-To:From; b=rHgt4G9oz+jrsMyzO6+MrSPe6Xs6q84zsUJGIQ2SlDP/ineuz9sM0Wur93efsC3di 9VFEmU3u/W4PEps0OVmUkgUvhTYZnzyCyCYPOpDLqPIWhqDwiSCje80eDAbmwvYLJI KgeQ82850SKAdQGIwkL1jalKRV788H9L6MDfB8Zg=
X-Virus-Scanned: Debian amavisd-new at b2.tigertech.net
Received: from Joels-MacBook-Pro.local (209-255-163-147.ip.mcleodusa.net [209.255.163.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mailb2.tigertech.net (Postfix) with ESMTPSA id 27B9B1C04A6; Tue, 12 Apr 2016 09:15:04 -0700 (PDT)
Subject: Re: Remote only meetings? [Re: Concerns about Singapore]
To: Ted Lemon <mellon@fugue.com>
References: <570AB3AF.2050401@gmail.com> <87twj99c6w.fsf@tops.chopps.org> <CAKe6YvMyp-DyeDwpPY6KYmbDbnpgnvVk_cUStnA32wmgDWcz3w@mail.gmail.com> <BBF5DDFE515C3946BC18D733B20DAD233A62AA18@XMB122CNC.rim.net> <20160411104519.GA19092@gsp.org> <3F48466D-390C-4C18-B958-732AE3E46FF1@gmail.com> <20160411223403.GA6743@gsp.org> <87twj7eon7.fsf@tops.chopps.org> <20160412110839.GA20488@gsp.org> <8760vn82f2.fsf@tops.chopps.org> <20160412124639.GA27223@gsp.org> <87fuurgd8f.fsf@tops.chopps.org> <CABmDk8kCfTB_AKyqV4X+AghL2G7i+XcKR=tzV0jybM05k+UU4Q@mail.gmail.com> <570D175A.1040001@joelhalpern.com> <CAPt1N1n0_UJ5AVzO=dyvzeLtYi0b8g5894wyhctwPwqTzme-PQ@mail.gmail.com>
From: "Joel M. Halpern" <jmh@joelhalpern.com>
Message-ID: <570D1F04.8050701@joelhalpern.com>
Date: Tue, 12 Apr 2016 12:15:00 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:38.0) Gecko/20100101 Thunderbird/38.7.2
MIME-Version: 1.0
In-Reply-To: <CAPt1N1n0_UJ5AVzO=dyvzeLtYi0b8g5894wyhctwPwqTzme-PQ@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/dXEDlT3p0mw-Eqcc_YPw0Bx1J-I>
Cc: Rich Kulawiec <rsk@gsp.org>, "<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: Tue, 12 Apr 2016 16:15:08 -0000

Ted, you missed my point.  Yes, I can arrange a call with the relevant 
people.  And I frequently do.
It is harder, but that would be acceptable.

The important part is that such calls are MUCH less effective than 
face-to-face discussions.  There are lots of well-known reasons for this.

And no, inc ase it was not obvious, without the face-to-face meeting, 
there is no way to arrange such face-to-face meetings.

Yes, we should work to make remote participation more effective.  Doing 
away with the face-to-face meetings reminds me of the old SF story of 
the ballet dancers who were forced to dance wearing extra weights, to be 
"fair" to the less talented dancers.

Yours,
Joel

On 4/12/16 12:00 PM, Ted Lemon wrote:
> This is all true, but the idea that it can't be replicated online is
> silly.   How did you arrange to have lunch with these people?   You went
> looking for them, rounded them up, and sat down to lunch.   You can do
> that online as well.
>
> It is certainly true that random conversation in the halls can also
> happen and lead to useful consequences, but having taken heavy advantage
> of "running into people" in BA, I can tell you that a lot of it was
> deliberate, and the parts that weren't probably would have been
> triggered by WG meetings even if they hadn't been triggered by just
> running into someone familiar in the lobby of the Hilton.
>
>
> On Tue, Apr 12, 2016 at 11:42 AM, Joel M. Halpern <jmh@joelhalpern.com
> <mailto:jmh@joelhalpern.com>> wrote:
>
>     I believe that there would be a real cost in moving to remote-only
>     meetings.  Even putting aside the time zone difficulties, and the
>     reduced effectiveness of in-meeting interaction, there are aspects
>     of face-to-face interaction taht current remote technologies simply
>     do not capture.
>     It was very helpful in BA (and at many previous IETF meetings) to be
>     able to find time to talk with a small number of people concerned
>     about an aspect of one working group.  I did that over meals,
>     breaks, etc.  It sorted out issues far more effectively than email
>     conversations (in several cases, we had tried to sort it out via
>     email.  10 minutes face-to-face clarified what was being missed, and
>     found a good path forward.)
>
>     Even in-meeting, when the meeting works well it takes advantage of
>     the nature of face-to-face interactions.  Admittedly, many sessions
>     do not need this, but many do.
>
>     Yours,
>     Joel
>
>     On 4/12/16 10:09 AM, Mary Barnes wrote:
>
>
>
>         On Tue, Apr 12, 2016 at 8:37 AM, <chopps@chopps.org
>         <mailto:chopps@chopps.org>
>         <mailto:chopps@chopps.org <mailto:chopps@chopps.org>>> wrote:
>
>
>              Rich Kulawiec <rsk@gsp.org <mailto:rsk@gsp.org>
>         <mailto:rsk@gsp.org <mailto:rsk@gsp.org>>> writes:
>
>
>              > On Tue, Apr 12, 2016 at 07:57:53AM
>         -0400,chopps@chopps.org <mailto:chopps@chopps.org>
>         <mailto:chopps@chopps.org <mailto:chopps@chopps.org>> wrote:
>              >> Your suggestion of not having them would subtract value
>         from the process
>              >> though. I don't see the win.
>              >
>              > The win is that all of the time and effort and expense
>         (all of which
>              > are finite resources) that go into those could be
>         directed elsewhere.
>
>              The meetings and their fees are income positive, they
>         aren't a drain on
>              resource, the opposite in fact.
>
>         [MB] I would agree when it comes to dollars, but people (i.e., the
>         effort to which Rich is referring) are also a resource and
>         volunteers do
>         the work.  If the only volunteers you get are from large
>         companies, I
>         think the IETF does lose.  With improved remote participation,
>         individuals that aren't sponsored by large companies can continue to
>         contribute.  Without it, we become ineffective.  [/MB]
>
>
>              > These meetings select for a highly limited (by
>         circumstance, by necessity,
>              > and by choice) subset.  And once upon a time, when the
>         'net was much
>              > younger and more limited in terms of geography and scope,
>         that might
>              > have been alright, because the subset mapped fairly well
>         onto the larger
>              > set of people involved in networking.  But that's no
>         longer true.
>              > And the difficulties/expense of travel are only going to
>         get worse
>              > for the forseeable future: they're not going to get better.
>
>              I think it would be useful to get some real data to measure
>         exactly how
>              highly limited that subset of people are. Perhaps as a
>         simple first
>              shot we could take email sent to IETF working group mailing
>         lists over
>              the last year, and cross reference that against the
>         registrations lists
>              of the last 3 IETFs and see what percentage of people doing
>         IETF work
>              cannot or choose not to attend the on-site meetings?
>
>         [MB] There was a separate list of registered remote attendees
>         for this
>         recent meeting. You can take a look there and see a number of
>         long time
>         contributors and some WG chairs (myself included) that have
>         participated
>         remotely.  The very reason I did not go was due to lack of funding.
>         There are a number of us that have contributed significantly
>         over the
>         past 15-30 years that would like to continue to do so but as
>         independent
>         consultants, some of these trips are just not fiscally
>         possible.  I went
>         to Yokohama so couldn't even entertain the idea of attending the
>         meeting
>         in BA without a sponsor.    And, I seriously doubt I can
>         continue as a
>         WG chair if I can't get funding in the future.  So, in the end, the
>         current model self selects and benefits the larger companies over
>         individuals that really do want to do work for the "good of the
>         Internet" but just can't justify the expense.   [/MB]
>
>              Thanks,
>              Chris.
>
>
>               >
>               > ---rsk
>
>
>
>


From nobody Tue Apr 12 09:24:36 2016
Return-Path: <hallam@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 1FA6C12D11C for <ietf@ietfa.amsl.com>; Tue, 12 Apr 2016 09:24:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.4
X-Spam-Level: 
X-Spam-Status: No, score=-2.4 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.199, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 6K8Tfkwovl_8 for <ietf@ietfa.amsl.com>; Tue, 12 Apr 2016 09:24:29 -0700 (PDT)
Received: from mail-lf0-x230.google.com (mail-lf0-x230.google.com [IPv6:2a00:1450:4010:c07::230]) (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 82E3F12D7A0 for <ietf@ietf.org>; Tue, 12 Apr 2016 09:24:28 -0700 (PDT)
Received: by mail-lf0-x230.google.com with SMTP id g184so32773588lfb.3 for <ietf@ietf.org>; Tue, 12 Apr 2016 09:24:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc; bh=WkhSNMNX5AghpZ1EplPI2sMAgcklx5hBILV9dsWLvyk=; b=K52DfCIo8ApL4vuES4Dj3KeHOAPBQqm3oOk+RFSPt8Jxcoee3binH5016BWNd7pxuK eJzy4WR6ZLY8hMeDnfPIxIf4SUl3HptX5zymBGdM3tkleAyHX6mLeuM8yNqyg+vyDhut kCOAovYZ6CMVUZA7mde/Nr9+9nVJ4wUkPxrACINtaph7B9m6Ugxq0j7famb1NVizEtMY Sb3mP+VnMb33zsjXbUHIK0Gu6bckG9L1W7bmM5d6uilTX0/OF8Phq0Ek+Qin2oQVgluL htams7xg/5pOI2pNZ9rvnNybMtzqumRqqWTDwFnIaFgV4ozt8slZJcMI6jCPgYYG0PiD ES0A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:date :message-id:subject:from:to:cc; bh=WkhSNMNX5AghpZ1EplPI2sMAgcklx5hBILV9dsWLvyk=; b=LmE690B1N/PjQQmR2FT5EYLiMliegvO4D1H/MmW3oqEbFolttjlDofutTm4XZU8Yrr JWJgv6OGDdiEwjmmcSzOQGFDCIcirwie7Q6Ks/9PY8VlRmcFIbkX5lS6LRK2tGfQSRNk NXHqVfx4GcvwdHEV3rmekXqDrXDjXbqrdGhWZsDGZQORZhEt94Q1XwPiriE7ESpnZMUA EJjQ8oGuJFgco4l087S2gsBX/sw/KeGhjGVHKqBXuWQkbQ7gqRUFCPfvE1YBf5znACVB vcZ0VJDXfcbcnt1IjDv3BY41pZJcxY4dZcdvEdp/ktTF6ODjZVGrrB5IJhHjq0XMLTWf Pdpw==
X-Gm-Message-State: AOPr4FWJiAXzPk5+j9zoDWqlltu3y0w0tJ9h12/lgp1KOqwdWxvQvshW0dT3qHyyqr/RpD3Aa5kX+WG+A6VKHQ==
MIME-Version: 1.0
X-Received: by 10.112.10.109 with SMTP id h13mr1793163lbb.58.1460478266682; Tue, 12 Apr 2016 09:24:26 -0700 (PDT)
Sender: hallam@gmail.com
Received: by 10.112.151.67 with HTTP; Tue, 12 Apr 2016 09:24:26 -0700 (PDT)
In-Reply-To: <20160410181958.58762.qmail@ary.lan>
References: <alpine.OSX.2.01.1604100736080.45987@rabdullah.local> <20160410181958.58762.qmail@ary.lan>
Date: Tue, 12 Apr 2016 13:24:26 -0300
X-Google-Sender-Auth: 3Qj_X5n7gh0fKw-jIOMdv81lE5g
Message-ID: <CAMm+LwgE_oOJSCjgsMGTSMDV2-LsUzw1zW3-+N_VCtE14m26BA@mail.gmail.com>
Subject: Re: Concerns about Singapore and other places
From: Phillip Hallam-Baker <phill@hallambaker.com>
To: John Levine <johnl@taugh.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/ATrwnb0jjlgg7741c-zOyijAWu0>
Cc: IETF Discussion Mailing List <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: Tue, 12 Apr 2016 16:24:35 -0000

On Sun, Apr 10, 2016 at 3:19 PM, John Levine <johnl@taugh.com> wrote:
>>The IETF has a meeting network requirements document that specifies a
>>number of parameters which includes no blocking.
>
> In London in 2014, do you know whether we were behind the national
> child porn filters?
>
> R's,
> John

I am not sure that they actually filter.

I think it rather more likely that if you were to surf to
kiddieporn.com from the Hilton Metropole, that you would find Mr Plod
knocking on your hotel room door 15 minutes later. That being the
driving time from New Scotland Yard.


From nobody Tue Apr 12 09:25:21 2016
Return-Path: <mellon@fugue.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 A413012D9A3 for <ietf@ietfa.amsl.com>; Tue, 12 Apr 2016 09:25:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.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 vVTWAhPtLS0c for <ietf@ietfa.amsl.com>; Tue, 12 Apr 2016 09:25:05 -0700 (PDT)
Received: from mail-lf0-x229.google.com (mail-lf0-x229.google.com [IPv6:2a00:1450:4010:c07::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 D010312E28D for <ietf@ietf.org>; Tue, 12 Apr 2016 09:25:02 -0700 (PDT)
Received: by mail-lf0-x229.google.com with SMTP id j11so32736130lfb.1 for <ietf@ietf.org>; Tue, 12 Apr 2016 09:25:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=XpzB4d+GqDfxukzoQQw48I6TYMOBEs6iydfPG8qXM5k=; b=LkY1nyNoccAW+0Hyd03QQIr4En7wrNuIHtEix3CFRzh8En/n5Ku76jljYc9kFQycWM nxyGQCon7JrLOnBWHbEEzhtTfOTpKUXz7mh8u0hO4HHQjmHFILZG8mDObr4rQnoRhs09 xhxmlKHz4TrR/3wFainBtfKWC3/RAh8Vk0SXnwnofogjZjSEYYQmZY+wj4d9+7M1P43u sxG6AqNCZtInn9e2mRdwTN+qU0nnOmobQe0cBPHgGQk6kOPtERT9BREG3NdZwGF3sZ60 BYgFwahegqqZSqIm3obPgZkJ0mccwBe2geqAhSX23J02Z54Al7bYAw13x7K4zT8fuZ/1 snYw==
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=XpzB4d+GqDfxukzoQQw48I6TYMOBEs6iydfPG8qXM5k=; b=X0r5UU3QNTQchUnKaxeTEe4tHb7fevSXY0CPHfnZsn9TMlos1MlFCmhQCg/qG12xc4 wuNDhjgdDkyihBlXugWU+v7b+0N10nMjUQsPhQmqX4vupHTKQm1uk67zzV6e6cpAHR/C JC1KTj4MzCVO+mIIeUffDfJy9Xrqh//zJ3/rl2LN65bbR64GO7RNryWGzKGq9OQxZVQG HgvOYmMS06tzQGo7rfLv+0GnYRA1LK+uVWpZODzsyC69KHfo6VimNZTZlt3spXBVVk/0 ivT4amsMVtKjEauChOGUYQZU4IGKScO+0kz6CEkI0m7JEjx5Ha5jgJUX9xXE6zOeqXrU XV5w==
X-Gm-Message-State: AOPr4FUNQYYtTGSocD2rLmrrVr1RCOvkep6t9RVUZGo3LfDT+hwp4jzTrD8OJyzMU9qNCIlWceU12G7oY46WwQ==
X-Received: by 10.112.169.105 with SMTP id ad9mr1740232lbc.135.1460478300966;  Tue, 12 Apr 2016 09:25:00 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.25.40.136 with HTTP; Tue, 12 Apr 2016 09:24:21 -0700 (PDT)
X-Originating-IP: [71.233.41.235]
In-Reply-To: <570D1F04.8050701@joelhalpern.com>
References: <570AB3AF.2050401@gmail.com> <87twj99c6w.fsf@tops.chopps.org> <CAKe6YvMyp-DyeDwpPY6KYmbDbnpgnvVk_cUStnA32wmgDWcz3w@mail.gmail.com> <BBF5DDFE515C3946BC18D733B20DAD233A62AA18@XMB122CNC.rim.net> <20160411104519.GA19092@gsp.org> <3F48466D-390C-4C18-B958-732AE3E46FF1@gmail.com> <20160411223403.GA6743@gsp.org> <87twj7eon7.fsf@tops.chopps.org> <20160412110839.GA20488@gsp.org> <8760vn82f2.fsf@tops.chopps.org> <20160412124639.GA27223@gsp.org> <87fuurgd8f.fsf@tops.chopps.org> <CABmDk8kCfTB_AKyqV4X+AghL2G7i+XcKR=tzV0jybM05k+UU4Q@mail.gmail.com> <570D175A.1040001@joelhalpern.com> <CAPt1N1n0_UJ5AVzO=dyvzeLtYi0b8g5894wyhctwPwqTzme-PQ@mail.gmail.com> <570D1F04.8050701@joelhalpern.com>
From: Ted Lemon <mellon@fugue.com>
Date: Tue, 12 Apr 2016 12:24:21 -0400
Message-ID: <CAPt1N1=-wxMj+k=8Kx9yXSnWnSR-hXX9AWp90Mgz8eZOueGoFA@mail.gmail.com>
Subject: Re: Remote only meetings? [Re: Concerns about Singapore]
To: "Joel M. Halpern" <jmh@joelhalpern.com>
Content-Type: multipart/alternative; boundary=001a11c38c0854e74a05304c1a7e
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/F6wWy9Kz7J_qjwasX130i0hFnSA>
Cc: Rich Kulawiec <rsk@gsp.org>, "<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: Tue, 12 Apr 2016 16:25:19 -0000

--001a11c38c0854e74a05304c1a7e
Content-Type: text/plain; charset=UTF-8

I think there was a story like that about football players too.   However,
I have not had the same experience you have.   I think that zero f2f
meetings is bad, and Iim not advocating that.   But it is quite possible to
be effective in a voice chat, and even more so in a video chat.   The idea
of a virtual meeting would be to try to set things up so that peoples
schedules are cleared and we can have informal meetings as well as formal
ones.

On Tue, Apr 12, 2016 at 12:15 PM, Joel M. Halpern <jmh@joelhalpern.com>
wrote:

> Ted, you missed my point.  Yes, I can arrange a call with the relevant
> people.  And I frequently do.
> It is harder, but that would be acceptable.
>
> The important part is that such calls are MUCH less effective than
> face-to-face discussions.  There are lots of well-known reasons for this.
>
> And no, inc ase it was not obvious, without the face-to-face meeting,
> there is no way to arrange such face-to-face meetings.
>
> Yes, we should work to make remote participation more effective.  Doing
> away with the face-to-face meetings reminds me of the old SF story of the
> ballet dancers who were forced to dance wearing extra weights, to be "fair"
> to the less talented dancers.
>
> Yours,
> Joel
>
> On 4/12/16 12:00 PM, Ted Lemon wrote:
>
>> This is all true, but the idea that it can't be replicated online is
>> silly.   How did you arrange to have lunch with these people?   You went
>> looking for them, rounded them up, and sat down to lunch.   You can do
>> that online as well.
>>
>> It is certainly true that random conversation in the halls can also
>> happen and lead to useful consequences, but having taken heavy advantage
>> of "running into people" in BA, I can tell you that a lot of it was
>> deliberate, and the parts that weren't probably would have been
>> triggered by WG meetings even if they hadn't been triggered by just
>> running into someone familiar in the lobby of the Hilton.
>>
>>
>> On Tue, Apr 12, 2016 at 11:42 AM, Joel M. Halpern <jmh@joelhalpern.com
>> <mailto:jmh@joelhalpern.com>> wrote:
>>
>>     I believe that there would be a real cost in moving to remote-only
>>     meetings.  Even putting aside the time zone difficulties, and the
>>     reduced effectiveness of in-meeting interaction, there are aspects
>>     of face-to-face interaction taht current remote technologies simply
>>     do not capture.
>>     It was very helpful in BA (and at many previous IETF meetings) to be
>>     able to find time to talk with a small number of people concerned
>>     about an aspect of one working group.  I did that over meals,
>>     breaks, etc.  It sorted out issues far more effectively than email
>>     conversations (in several cases, we had tried to sort it out via
>>     email.  10 minutes face-to-face clarified what was being missed, and
>>     found a good path forward.)
>>
>>     Even in-meeting, when the meeting works well it takes advantage of
>>     the nature of face-to-face interactions.  Admittedly, many sessions
>>     do not need this, but many do.
>>
>>     Yours,
>>     Joel
>>
>>     On 4/12/16 10:09 AM, Mary Barnes wrote:
>>
>>
>>
>>         On Tue, Apr 12, 2016 at 8:37 AM, <chopps@chopps.org
>>         <mailto:chopps@chopps.org>
>>         <mailto:chopps@chopps.org <mailto:chopps@chopps.org>>> wrote:
>>
>>
>>              Rich Kulawiec <rsk@gsp.org <mailto:rsk@gsp.org>
>>         <mailto:rsk@gsp.org <mailto:rsk@gsp.org>>> writes:
>>
>>
>>              > On Tue, Apr 12, 2016 at 07:57:53AM
>>         -0400,chopps@chopps.org <mailto:chopps@chopps.org>
>>         <mailto:chopps@chopps.org <mailto:chopps@chopps.org>> wrote:
>>              >> Your suggestion of not having them would subtract value
>>         from the process
>>              >> though. I don't see the win.
>>              >
>>              > The win is that all of the time and effort and expense
>>         (all of which
>>              > are finite resources) that go into those could be
>>         directed elsewhere.
>>
>>              The meetings and their fees are income positive, they
>>         aren't a drain on
>>              resource, the opposite in fact.
>>
>>         [MB] I would agree when it comes to dollars, but people (i.e., the
>>         effort to which Rich is referring) are also a resource and
>>         volunteers do
>>         the work.  If the only volunteers you get are from large
>>         companies, I
>>         think the IETF does lose.  With improved remote participation,
>>         individuals that aren't sponsored by large companies can continue
>> to
>>         contribute.  Without it, we become ineffective.  [/MB]
>>
>>
>>              > These meetings select for a highly limited (by
>>         circumstance, by necessity,
>>              > and by choice) subset.  And once upon a time, when the
>>         'net was much
>>              > younger and more limited in terms of geography and scope,
>>         that might
>>              > have been alright, because the subset mapped fairly well
>>         onto the larger
>>              > set of people involved in networking.  But that's no
>>         longer true.
>>              > And the difficulties/expense of travel are only going to
>>         get worse
>>              > for the forseeable future: they're not going to get better.
>>
>>              I think it would be useful to get some real data to measure
>>         exactly how
>>              highly limited that subset of people are. Perhaps as a
>>         simple first
>>              shot we could take email sent to IETF working group mailing
>>         lists over
>>              the last year, and cross reference that against the
>>         registrations lists
>>              of the last 3 IETFs and see what percentage of people doing
>>         IETF work
>>              cannot or choose not to attend the on-site meetings?
>>
>>         [MB] There was a separate list of registered remote attendees
>>         for this
>>         recent meeting. You can take a look there and see a number of
>>         long time
>>         contributors and some WG chairs (myself included) that have
>>         participated
>>         remotely.  The very reason I did not go was due to lack of
>> funding.
>>         There are a number of us that have contributed significantly
>>         over the
>>         past 15-30 years that would like to continue to do so but as
>>         independent
>>         consultants, some of these trips are just not fiscally
>>         possible.  I went
>>         to Yokohama so couldn't even entertain the idea of attending the
>>         meeting
>>         in BA without a sponsor.    And, I seriously doubt I can
>>         continue as a
>>         WG chair if I can't get funding in the future.  So, in the end,
>> the
>>         current model self selects and benefits the larger companies over
>>         individuals that really do want to do work for the "good of the
>>         Internet" but just can't justify the expense.   [/MB]
>>
>>              Thanks,
>>              Chris.
>>
>>
>>               >
>>               > ---rsk
>>
>>
>>
>>
>>

--001a11c38c0854e74a05304c1a7e
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">I think there was a story like that about football players=
 too. =C2=A0 However, I have not had the same experience you have. =C2=A0 I=
 think that zero f2f meetings is bad, and Iim not advocating that. =C2=A0 B=
ut it is quite possible to be effective in a voice chat, and even more so i=
n a video chat. =C2=A0 The idea of a virtual meeting would be to try to set=
 things up so that peoples schedules are cleared and we can have informal m=
eetings as well as formal ones.</div><div class=3D"gmail_extra"><br><div cl=
ass=3D"gmail_quote">On Tue, Apr 12, 2016 at 12:15 PM, Joel M. Halpern <span=
 dir=3D"ltr">&lt;<a href=3D"mailto:jmh@joelhalpern.com" target=3D"_blank">j=
mh@joelhalpern.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quot=
e" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">=
Ted, you missed my point.=C2=A0 Yes, I can arrange a call with the relevant=
 people.=C2=A0 And I frequently do.<br>
It is harder, but that would be acceptable.<br>
<br>
The important part is that such calls are MUCH less effective than face-to-=
face discussions.=C2=A0 There are lots of well-known reasons for this.<br>
<br>
And no, inc ase it was not obvious, without the face-to-face meeting, there=
 is no way to arrange such face-to-face meetings.<br>
<br>
Yes, we should work to make remote participation more effective.=C2=A0 Doin=
g away with the face-to-face meetings reminds me of the old SF story of the=
 ballet dancers who were forced to dance wearing extra weights, to be &quot=
;fair&quot; to the less talented dancers.<br>
<br>
Yours,<br>
Joel<span class=3D""><br>
<br>
On 4/12/16 12:00 PM, Ted Lemon wrote:<br>
</span><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-=
left:1px #ccc solid;padding-left:1ex"><span class=3D"">
This is all true, but the idea that it can&#39;t be replicated online is<br=
>
silly.=C2=A0 =C2=A0How did you arrange to have lunch with these people?=C2=
=A0 =C2=A0You went<br>
looking for them, rounded them up, and sat down to lunch.=C2=A0 =C2=A0You c=
an do<br>
that online as well.<br>
<br>
It is certainly true that random conversation in the halls can also<br>
happen and lead to useful consequences, but having taken heavy advantage<br=
>
of &quot;running into people&quot; in BA, I can tell you that a lot of it w=
as<br>
deliberate, and the parts that weren&#39;t probably would have been<br>
triggered by WG meetings even if they hadn&#39;t been triggered by just<br>
running into someone familiar in the lobby of the Hilton.<br>
<br>
<br>
On Tue, Apr 12, 2016 at 11:42 AM, Joel M. Halpern &lt;<a href=3D"mailto:jmh=
@joelhalpern.com" target=3D"_blank">jmh@joelhalpern.com</a><br></span><span=
 class=3D"">
&lt;mailto:<a href=3D"mailto:jmh@joelhalpern.com" target=3D"_blank">jmh@joe=
lhalpern.com</a>&gt;&gt; wrote:<br>
<br>
=C2=A0 =C2=A0 I believe that there would be a real cost in moving to remote=
-only<br>
=C2=A0 =C2=A0 meetings.=C2=A0 Even putting aside the time zone difficulties=
, and the<br>
=C2=A0 =C2=A0 reduced effectiveness of in-meeting interaction, there are as=
pects<br>
=C2=A0 =C2=A0 of face-to-face interaction taht current remote technologies =
simply<br>
=C2=A0 =C2=A0 do not capture.<br>
=C2=A0 =C2=A0 It was very helpful in BA (and at many previous IETF meetings=
) to be<br>
=C2=A0 =C2=A0 able to find time to talk with a small number of people conce=
rned<br>
=C2=A0 =C2=A0 about an aspect of one working group.=C2=A0 I did that over m=
eals,<br>
=C2=A0 =C2=A0 breaks, etc.=C2=A0 It sorted out issues far more effectively =
than email<br>
=C2=A0 =C2=A0 conversations (in several cases, we had tried to sort it out =
via<br>
=C2=A0 =C2=A0 email.=C2=A0 10 minutes face-to-face clarified what was being=
 missed, and<br>
=C2=A0 =C2=A0 found a good path forward.)<br>
<br>
=C2=A0 =C2=A0 Even in-meeting, when the meeting works well it takes advanta=
ge of<br>
=C2=A0 =C2=A0 the nature of face-to-face interactions.=C2=A0 Admittedly, ma=
ny sessions<br>
=C2=A0 =C2=A0 do not need this, but many do.<br>
<br>
=C2=A0 =C2=A0 Yours,<br>
=C2=A0 =C2=A0 Joel<br>
<br>
=C2=A0 =C2=A0 On 4/12/16 10:09 AM, Mary Barnes wrote:<br>
<br>
<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 On Tue, Apr 12, 2016 at 8:37 AM, &lt;<a href=3D=
"mailto:chopps@chopps.org" target=3D"_blank">chopps@chopps.org</a><br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 &lt;mailto:<a href=3D"mailto:chopps@chopps.org"=
 target=3D"_blank">chopps@chopps.org</a>&gt;<br></span><span class=3D"">
=C2=A0 =C2=A0 =C2=A0 =C2=A0 &lt;mailto:<a href=3D"mailto:chopps@chopps.org"=
 target=3D"_blank">chopps@chopps.org</a> &lt;mailto:<a href=3D"mailto:chopp=
s@chopps.org" target=3D"_blank">chopps@chopps.org</a>&gt;&gt;&gt; wrote:<br=
>
<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Rich Kulawiec &lt;<a href=
=3D"mailto:rsk@gsp.org" target=3D"_blank">rsk@gsp.org</a> &lt;mailto:<a hre=
f=3D"mailto:rsk@gsp.org" target=3D"_blank">rsk@gsp.org</a>&gt;<br></span><s=
pan class=3D"">
=C2=A0 =C2=A0 =C2=A0 =C2=A0 &lt;mailto:<a href=3D"mailto:rsk@gsp.org" targe=
t=3D"_blank">rsk@gsp.org</a> &lt;mailto:<a href=3D"mailto:rsk@gsp.org" targ=
et=3D"_blank">rsk@gsp.org</a>&gt;&gt;&gt; writes:<br>
<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&gt; On Tue, Apr 12, 2016 a=
t 07:57:53AM<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 -0400,<a href=3D"mailto:chopps@chopps.org" targ=
et=3D"_blank">chopps@chopps.org</a> &lt;mailto:<a href=3D"mailto:chopps@cho=
pps.org" target=3D"_blank">chopps@chopps.org</a>&gt;<br></span><div><div cl=
ass=3D"h5">
=C2=A0 =C2=A0 =C2=A0 =C2=A0 &lt;mailto:<a href=3D"mailto:chopps@chopps.org"=
 target=3D"_blank">chopps@chopps.org</a> &lt;mailto:<a href=3D"mailto:chopp=
s@chopps.org" target=3D"_blank">chopps@chopps.org</a>&gt;&gt; wrote:<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&gt;&gt; Your suggestion of=
 not having them would subtract value<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 from the process<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&gt;&gt; though. I don&#39;=
t see the win.<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&gt;<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&gt; The win is that all of=
 the time and effort and expense<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 (all of which<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&gt; are finite resources) =
that go into those could be<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 directed elsewhere.<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0The meetings and their fees=
 are income positive, they<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 aren&#39;t a drain on<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0resource, the opposite in f=
act.<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 [MB] I would agree when it comes to dollars, bu=
t people (i.e., the<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 effort to which Rich is referring) are also a r=
esource and<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 volunteers do<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 the work.=C2=A0 If the only volunteers you get =
are from large<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 companies, I<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 think the IETF does lose.=C2=A0 With improved r=
emote participation,<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 individuals that aren&#39;t sponsored by large =
companies can continue to<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 contribute.=C2=A0 Without it, we become ineffec=
tive.=C2=A0 [/MB]<br>
<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&gt; These meetings select =
for a highly limited (by<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 circumstance, by necessity,<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&gt; and by choice) subset.=
=C2=A0 And once upon a time, when the<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 &#39;net was much<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&gt; younger and more limit=
ed in terms of geography and scope,<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 that might<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&gt; have been alright, bec=
ause the subset mapped fairly well<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 onto the larger<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&gt; set of people involved=
 in networking.=C2=A0 But that&#39;s no<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 longer true.<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&gt; And the difficulties/e=
xpense of travel are only going to<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 get worse<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&gt; for the forseeable fut=
ure: they&#39;re not going to get better.<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0I think it would be useful =
to get some real data to measure<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 exactly how<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0highly limited that subset =
of people are. Perhaps as a<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 simple first<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0shot we could take email se=
nt to IETF working group mailing<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 lists over<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0the last year, and cross re=
ference that against the<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 registrations lists<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0of the last 3 IETFs and see=
 what percentage of people doing<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 IETF work<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0cannot or choose not to att=
end the on-site meetings?<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 [MB] There was a separate list of registered re=
mote attendees<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 for this<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 recent meeting. You can take a look there and s=
ee a number of<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 long time<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 contributors and some WG chairs (myself include=
d) that have<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 participated<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 remotely.=C2=A0 The very reason I did not go wa=
s due to lack of funding.<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 There are a number of us that have contributed =
significantly<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 over the<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 past 15-30 years that would like to continue to=
 do so but as<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 independent<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 consultants, some of these trips are just not f=
iscally<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 possible.=C2=A0 I went<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 to Yokohama so couldn&#39;t even entertain the =
idea of attending the<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 meeting<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 in BA without a sponsor.=C2=A0 =C2=A0 And, I se=
riously doubt I can<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 continue as a<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 WG chair if I can&#39;t get funding in the futu=
re.=C2=A0 So, in the end, the<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 current model self selects and benefits the lar=
ger companies over<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 individuals that really do want to do work for =
the &quot;good of the<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Internet&quot; but just can&#39;t justify the e=
xpense.=C2=A0 =C2=A0[/MB]<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Thanks,<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Chris.<br>
<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 &gt;<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 &gt; ---rsk<br>
<br>
<br>
<br>
<br>
</div></div></blockquote>
</blockquote></div><br></div>

--001a11c38c0854e74a05304c1a7e--


From nobody Tue Apr 12 09:50:43 2016
Return-Path: <alissa@cooperw.in>
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 98D2512E663 for <ietf@ietfa.amsl.com>; Tue, 12 Apr 2016 09:50:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.721
X-Spam-Level: 
X-Spam-Status: No, score=-2.721 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cooperw.in header.b=q4MMsott; dkim=pass (1024-bit key) header.d=messagingengine.com header.b=HxGp8k0I
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 0Lv5W4okUB1G for <ietf@ietfa.amsl.com>; Tue, 12 Apr 2016 09:50:40 -0700 (PDT)
Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3193812E0F1 for <ietf@ietf.org>; Tue, 12 Apr 2016 09:50:40 -0700 (PDT)
Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.nyi.internal (Postfix) with ESMTP id 9A11A217CF for <ietf@ietf.org>; Tue, 12 Apr 2016 12:50:39 -0400 (EDT)
Received: from frontend1 ([10.202.2.160]) by compute2.internal (MEProxy); Tue, 12 Apr 2016 12:50:39 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=cooperw.in; h=cc :content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-sasl-enc :x-sasl-enc; s=mesmtp; bh=zsHqj43/DDe/pIHYndhDNbATJAE=; b=q4MMso ttACLI3xY4/F/WfsNqVy4sjC5oYXPpqN9g0cBw9YNpctigS9WJ0XZW71iJ5uZpEN 7DiBFhKvZpK4NOVfhYHu5SKUwSSN0Ox3bmbyzpirxDFb5HUScJz3Zs6zKaqR1VYs YUPdaPsosuWF0ONQYIkbNYoi/vq92dVuch1vA=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-sasl-enc:x-sasl-enc; s=smtpout; bh=zsHqj43/DDe/pIH YndhDNbATJAE=; b=HxGp8k0I7eyqPvs7zeD2FynCWSJ5RXX2nn2F/OSzCnVSBTn d1OP9RQxaMfrr7bHgtEqbDgQv4LoCNON7EBUymXUqnHvh43ZZ9OrhB94ek12EXvC mB9HyFK4uI2x8u3j+ljCJk3J1YyAnCq/BCvlkbuUHktIKYsvVBtUMWo+V2kA=
X-Sasl-enc: mfPFxhCyDiD191XOMJty1/zKfXossdXj/7r8CIS1lp0W 1460479839
Received: from dhcp-171-68-20-116.cisco.com (dhcp-171-68-20-116.cisco.com [171.68.20.116]) by mail.messagingengine.com (Postfix) with ESMTPA id DC48BC0001E; Tue, 12 Apr 2016 12:50:38 -0400 (EDT)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 9.2 \(3112\))
Subject: Re: Last Call on draft-bradner-rfc3979bis-08.txt ("Intellectual Property Rights in IETF Technology")
From: Alissa Cooper <alissa@cooperw.in>
In-Reply-To: <65AD4D713F340D761513414F@JcK-HP8200.jck.com>
Date: Tue, 12 Apr 2016 09:50:38 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <F79025B0-EC2E-44CB-840A-55736DBE8318@cooperw.in>
References: <65AD4D713F340D761513414F@JcK-HP8200.jck.com>
To: John C Klensin <john-ietf@jck.com>
X-Mailer: Apple Mail (2.3112)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/JFWhwIZjt467_ksyVPHp8EKipFs>
Cc: IETF <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: Tue, 12 Apr 2016 16:50:41 -0000

> On Apr 12, 2016, at 2:29 AM, John C Klensin <john-ietf@jck.com> wrote:
>=20
>=20
>=20
> --On Monday, April 11, 2016 15:33 -0700 Alissa Cooper
> <alissa@cooperw.in> wrote:
>=20
>>> Personally, I'd love to see the draft talk about AD
>>> participation just like it talks about other people's
>>> participation. If I really haven't participated in WG X,
>>> well, I haven't, even if my co-AD owns the group :-) And if
>>> I did participate, well, I should declare the IPR that I know
>>> of :-)
>>=20
>> +1
>> This is what did not make sense to me about the draft.=20
>=20
> Alissa,
>=20
> I'm fine with the above, but I think there is a delicate line
> involved.  Let me try to explain it this way.  As a random
> member of the community, whether I'm participating in a WG, or
> even actively monitoring it, is fairly clear.  If, for example,
> I'm attending its meetings (f2f or remotely) or signed up for
> its mailing list, the community should be able to assume that
> I'm watching the work in that WG and should be required to make
> relevant IPR disclosures even if I don't actually say anything
> or otherwise generate Contributions.    If I do none of those
> things but occasionally check on mailing list archives, read
> Last Call announcements, I think the community needs to take my
> word for it if I claim to be "not participating".
>=20
> I think things are a little different (but only a little) if
> there is management involvement.  If you are the AD responsible
> for a WG, then I think the community gets to assume that you
> know what its work items are, have approved document editors,
> and have at least read the abstracts of the various drafts,
> i.e., that you are participating.  If you are some other AD in
> the same area, well, areas differ a lot and over time.  In some
> cases, ADs shadow each other as a mutual backup arrangements and
> I'd expect to be able to treat all ADs in the same area as
> "participating" in all WGs.  In others, WGs get divided up among
> ADs, after which the area might as well be as many separate ones
> as there are ADs.  At IETF evaluation time, any ADs who record a
> position other that "abstain" on a spec, or to engage in any
> IESG discussion about it, has presumably studied that spec
> closely enough to incur disclosure obligations if IPR is known
> to them because making a decision to adopt (or not) is clearly
> "participation".  The same issue might exist with Co-chairs of a
> WG with many tasks.  I'd normally assume that each one is
> familiar with and participating in every work item, but it isn't
> hard to imagine situations in which work might be split up along
> clear boundaries with one co-chair getting involved in the work
> of the other only at around the time of Last Call if then.
>=20
> All of that said, I think that trying to create a collection of
> very specific rules or definitions to cover each case and
> variations on it is almost certain to cause more harm than good.
> I think the intent of the rules -- that anyone who has
> contributed to a spec or put themselves in a position in which
> they influence an IETF decision to adopt (or not) or publish (or
> not) has disclosure obligations (whether direct or third-party
> as discussed in the I-D). My expectation is that WG Chairs and,
> to even a greater extent, ADs, will be sensitive to the intent
> of the rules.  To do otherwise would be a breach of the trust
> the community placed in them and that would be at least as
> serious, perhaps more, than breaching the letter of the IPR
> rules.  =20
>=20
> If we need rule changes in that area, they probably lie in
> making recalls more feasible rather than more case analysis in
> the IPR document(s).   If the latter documents need anything
> extra, perhaps it is an explicit statement to the effect of
> "Because of the trust the community places in them and the
> consensus-determination and decision authority associated with
> their positions, IETF Leadership including WG Chairs and Nomcom
> appointees are expected to be especially diligent in observing
> the intent of these rules=E2=80=9D. =20

WFM
Alissa

>=20
> best.
>     john
>=20
>=20
>=20


From nobody Tue Apr 12 09:53:27 2016
Return-Path: <mellon@fugue.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 9DCE212E935 for <ietf@ietfa.amsl.com>; Tue, 12 Apr 2016 09:53:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.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 gyRhahHyKdeG for <ietf@ietfa.amsl.com>; Tue, 12 Apr 2016 09:53:22 -0700 (PDT)
Received: from mail-lf0-x229.google.com (mail-lf0-x229.google.com [IPv6:2a00:1450:4010:c07::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 C153112E987 for <ietf@ietf.org>; Tue, 12 Apr 2016 09:53:21 -0700 (PDT)
Received: by mail-lf0-x229.google.com with SMTP id j11so33821950lfb.1 for <ietf@ietf.org>; Tue, 12 Apr 2016 09:53:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=cEu3nYZBWA1glCaDTzgOogkbBd0fBYB0w0U52ZeQDOo=; b=cUl9BGThW4akNaJ8jkrCRrWVHxUVjOx9B+pcrmaJf4c5z+cGi6PzQDodfdf9eqCnEj 0aV3XW/7tRdbu0OfF28JNms3x0GO+TIrD2pV18Cy44h6bAth49uye5CYqfUiuQHthSUO u7b5QPjlzci04s4Y5ux/DUB0F/OjZtkiP7tS+AVOEDNrbGOlhuctFpulCYmt8RZEeDYZ m5B504a0pt8SeuUyTgYQqnr3lyzIUBbZZ/0dVH9u3d0Jp8K70vvqSjBFeNGXv94euWU3 kuux+1vOukd1i3b3kY/1a6ERkUBlYguRfU7UOoIm4SzOGaOWt4pQQeNjXoiCMVwiaGA9 H9bg==
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=cEu3nYZBWA1glCaDTzgOogkbBd0fBYB0w0U52ZeQDOo=; b=KivxKb6wXhD6TV70jXSfG36istcNMKe/9NbIUBDvdU4EIZ1+F7Dah/61hg/0RMb3JO VJTym8JTesWBi225umIyPqiBGzJsw24Q3DaWPcWfxKY58Dll1yW9Ax6tc79GhaJO+cOQ IuxvsAQzXwegySFMnf7CaSkkqtMoIknH6PpIgeHKrhdW+YmDT7rR5XgyEF3kEC7CfASK kNarZ2QD1H2ZR375RoLpiQDVvGcO+ynltN5O+637iMa2Yba155+UhV4ydqL900dzHjI4 ADI1g51/SPNfHvowXrnFi7LcZ0jKAemvGsUEUao0wZ9cPj/Iay6ptPddw5Wt22T1Ed4f Zylg==
X-Gm-Message-State: AOPr4FWcneUs4b8nqfUYMIprsBG/3jVrKheYmFUe4ssbnsPgEY4bo6vlRd258y20OBwN5TAKOOeeLy62qSAAZg==
X-Received: by 10.112.13.8 with SMTP id d8mr1812986lbc.110.1460479999968; Tue, 12 Apr 2016 09:53:19 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.25.40.136 with HTTP; Tue, 12 Apr 2016 09:52:40 -0700 (PDT)
X-Originating-IP: [71.233.41.235]
In-Reply-To: <CAMm+LwgE_oOJSCjgsMGTSMDV2-LsUzw1zW3-+N_VCtE14m26BA@mail.gmail.com>
References: <alpine.OSX.2.01.1604100736080.45987@rabdullah.local> <20160410181958.58762.qmail@ary.lan> <CAMm+LwgE_oOJSCjgsMGTSMDV2-LsUzw1zW3-+N_VCtE14m26BA@mail.gmail.com>
From: Ted Lemon <mellon@fugue.com>
Date: Tue, 12 Apr 2016 12:52:40 -0400
Message-ID: <CAPt1N1nLWrVqGpPh+h=Ano6PJyw2ZRaroiAMgG4RDKTFV7rkpA@mail.gmail.com>
Subject: Re: Concerns about Singapore and other places
To: Phillip Hallam-Baker <phill@hallambaker.com>
Content-Type: multipart/alternative; boundary=001a11c3b44e9996f405304c7f13
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/P-efZ4Ur2-MYBcGOS0batwBw7wA>
Cc: John Levine <johnl@taugh.com>, IETF Discussion Mailing List <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: Tue, 12 Apr 2016 16:53:26 -0000

--001a11c3b44e9996f405304c7f13
Content-Type: text/plain; charset=UTF-8

The UK filter is an "opt out" filter, and I assume that we (the IETF) opted
out.   Even the "opt out" blocking is voluntary at present--an ISP is not
required by law to have a filter, but in practice the big ones do.

On Tue, Apr 12, 2016 at 12:24 PM, Phillip Hallam-Baker <
phill@hallambaker.com> wrote:

> On Sun, Apr 10, 2016 at 3:19 PM, John Levine <johnl@taugh.com> wrote:
> >>The IETF has a meeting network requirements document that specifies a
> >>number of parameters which includes no blocking.
> >
> > In London in 2014, do you know whether we were behind the national
> > child porn filters?
> >
> > R's,
> > John
>
> I am not sure that they actually filter.
>
> I think it rather more likely that if you were to surf to
> kiddieporn.com from the Hilton Metropole, that you would find Mr Plod
> knocking on your hotel room door 15 minutes later. That being the
> driving time from New Scotland Yard.
>
>

--001a11c3b44e9996f405304c7f13
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">The UK filter is an &quot;opt out&quot; filter, and I assu=
me that we (the IETF) opted out. =C2=A0 Even the &quot;opt out&quot; blocki=
ng is voluntary at present--an ISP is not required by law to have a filter,=
 but in practice the big ones do.</div><div class=3D"gmail_extra"><br><div =
class=3D"gmail_quote">On Tue, Apr 12, 2016 at 12:24 PM, Phillip Hallam-Bake=
r <span dir=3D"ltr">&lt;<a href=3D"mailto:phill@hallambaker.com" target=3D"=
_blank">phill@hallambaker.com</a>&gt;</span> wrote:<br><blockquote class=3D=
"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding=
-left:1ex"><div class=3D"HOEnZb"><div class=3D"h5">On Sun, Apr 10, 2016 at =
3:19 PM, John Levine &lt;<a href=3D"mailto:johnl@taugh.com">johnl@taugh.com=
</a>&gt; wrote:<br>
&gt;&gt;The IETF has a meeting network requirements document that specifies=
 a<br>
&gt;&gt;number of parameters which includes no blocking.<br>
&gt;<br>
&gt; In London in 2014, do you know whether we were behind the national<br>
&gt; child porn filters?<br>
&gt;<br>
&gt; R&#39;s,<br>
&gt; John<br>
<br>
</div></div>I am not sure that they actually filter.<br>
<br>
I think it rather more likely that if you were to surf to<br>
<a href=3D"http://kiddieporn.com" rel=3D"noreferrer" target=3D"_blank">kidd=
ieporn.com</a> from the Hilton Metropole, that you would find Mr Plod<br>
knocking on your hotel room door 15 minutes later. That being the<br>
driving time from New Scotland Yard.<br>
<br>
</blockquote></div><br></div>

--001a11c3b44e9996f405304c7f13--


From nobody Tue Apr 12 09:55:05 2016
Return-Path: <dhruv.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 ABBF612D576 for <ietf@ietfa.amsl.com>; Tue, 12 Apr 2016 09:55:03 -0700 (PDT)
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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 XhAtrPGie3QY for <ietf@ietfa.amsl.com>; Tue, 12 Apr 2016 09:55:02 -0700 (PDT)
Received: from mail-io0-x229.google.com (mail-io0-x229.google.com [IPv6:2607:f8b0:4001: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 E0D7112D517 for <ietf@ietf.org>; Tue, 12 Apr 2016 09:55:01 -0700 (PDT)
Received: by mail-io0-x229.google.com with SMTP id u185so36086495iod.3 for <ietf@ietf.org>; Tue, 12 Apr 2016 09:55:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc; bh=Yz1K9IGaZ4y9IWBtIHhcjVYLAOyftpKzzcgBPTDsR7E=; b=RJCeDODsJd53Xs/1M9owPxyV51wq9GluOWblmwagqYFfYZ5pMA8iDxzKp4WYLMsEzw pQojWyw+htdpvHpobT5IXwYJYJ4K8drsI3cfypwEisRiOngvxzzHwgpRAEyCcKxYeVB2 Sc+5Dg0VXL3jISqiwIjS+Wdqv6ilsluOG7kwahCIYTICixaYdvtIczomVqa02io+WO6s YQRozQFCRYJrt1TBnN1FPuOLEnrf5QmdgO4mgAoF7TL08oUYtZ6+ChtKuya7qaJpjR3x xY699J5GD8GRT6kaP1UcgVV3fTbsm3mUih3LaWNeNYsBPHgaA0X8iPUJa4LahVgc4jfc P0BQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:date :message-id:subject:from:to:cc; bh=Yz1K9IGaZ4y9IWBtIHhcjVYLAOyftpKzzcgBPTDsR7E=; b=UN7Ib98DIJNs+OSxKzumJxTj3TABA/rTotiTHXAg5URtiK5LcfQmMhHjUEBC4mZGxS b3bgz5QP2zhF961enfDw8oleCu+ABtaAFUhJRXuQ/SvlwUSC8tygRSI0RMQJZ4eH3ScY yAcuirToY6ZzFKxSIe75amSwskkeScnxQdhKapdhYb0NxhrHJvsXPeAnv4skOB1d9lZ+ PuH+ePhpefHTfzIWXa2ptJlZnaII4JaIlJI+x91zi4IK0oMlzJANGBf8buh+b1YOkpk5 WfBd632xkX4NPs9LmsUGDukkf8hJSgKQOyMZXIvXfnM1PA4f5eBTOJxeCVunhSVKgyW+ gejQ==
X-Gm-Message-State: AOPr4FVhpCyq9hn7DTZvqrISWdLom4YtI2nna360vLpc/Y5tW+OvXRUK5Qf3iO2fzU50VyulE3sC8zzfs7qt1g==
MIME-Version: 1.0
X-Received: by 10.107.10.206 with SMTP id 75mr5171200iok.155.1460480101185; Tue, 12 Apr 2016 09:55:01 -0700 (PDT)
Sender: dhruvdhody@gmail.com
X-Google-Sender-Delegation: dhruvdhody@gmail.com
Received: by 10.50.222.71 with HTTP; Tue, 12 Apr 2016 09:55:00 -0700 (PDT)
In-Reply-To: <CAPt1N1m_gbTMdxUfqgUDdKfw56E7Exfo6QU2GuxxueN_gPFCwQ@mail.gmail.com>
References: <m260vp7eke.wl%randy@psg.com> <570A6458.3050206@comcast.net> <m21t6d7c9t.wl%randy@psg.com> <570A67B4.3010206@comcast.net> <570AB3AF.2050401@gmail.com> <87twj99c6w.fsf@tops.chopps.org> <CAKe6YvMyp-DyeDwpPY6KYmbDbnpgnvVk_cUStnA32wmgDWcz3w@mail.gmail.com> <BBF5DDFE515C3946BC18D733B20DAD233A62AA18@XMB122CNC.rim.net> <20160411104519.GA19092@gsp.org> <3F48466D-390C-4C18-B958-732AE3E46FF1@gmail.com> <20160411223403.GA6743@gsp.org> <CAPt1N1nNo0=JSptQdWRZCFy1v-m6Q8NQy4WVGHtnRJuFZFmMig@mail.gmail.com> <CAKr6gn1KmNcgNwbPHZWB2aJQAuchz4eB7gxJhV2Dsbc1Z50kDw@mail.gmail.com> <CAPt1N1mWjg_-525avYJ4PnSECYQrtpVFJCXPfH=PryJ8q0vy4Q@mail.gmail.com> <A684A3C4-7161-49F5-919E-A5F948A3F316@ecs.soton.ac.uk> <EMEW3|d5cb2cb80712b3716e1ab4e2a54c9430s3BCG403tjc|ecs.soton.ac.uk|A684A3C4-7161-49F5-919E-A5F948A3F316@ecs.soton.ac.uk> <570CF594.5070509@pi.nu> <CAPt1N1m_gbTMdxUfqgUDdKfw56E7Exfo6QU2GuxxueN_gPFCwQ@mail.gmail.com>
Date: Tue, 12 Apr 2016 13:55:00 -0300
X-Google-Sender-Auth: eXbUUk-5SXkEOtyoLATUdtNYFr4
Message-ID: <CAB75xn6Ev6YhCu9T6nmqBEgK8wVUKqBLGJ+cn4HCPPnsZzkwNQ@mail.gmail.com>
Subject: Re: Concerns about Singapore
From: Dhruv Dhody <dhruv.ietf@gmail.com>
To: Ted Lemon <mellon@fugue.com>
Content-Type: multipart/alternative; boundary=001a113f89b4a206c505304c855b
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/B7HwahTImDFwJvCiCnJ9u0hgSsM>
Cc: ietf <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: Tue, 12 Apr 2016 16:55:03 -0000

--001a113f89b4a206c505304c855b
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi,

On Tue, Apr 12, 2016 at 10:34 AM, Ted Lemon <mellon@fugue.com> wrote:

> I think that at this point the question of what we can do to address the
> Singapore problem is in the hands of the IAOC, which has indicated a
> willingness to explore going even further than Ted asked them to in
> addressing the problem.   Ted asked them to not bring their families to
> Singapore in solidarity with him, since he doesn't feel safe bringing his
> family.
>

=E2=80=8BTed has a point and it is a concern that we (as a part of the gay
community) have to deal with it daily.


> The IAOC has said they are looking into how difficult it would be to
> actually move IETF 100 to a different country.
>

=E2=80=8BBut, to me this is interesting, that we took the discussion, from
solidarity and understanding of the difficulties that the gay community
faces, to sort of escaping it and not dealing with it. By setting this
precedence I am afraid IETF would not take place in a large part of the
world in coming years.

And isn't that excluding people (which BTW *also* includes the members of
the same gay community, but from this part of the world)?


> So I don't think there's anything for us to discuss here, unless you are =
a
> member of the LGBTQ+ community and have something to add about how you
> think Singapore should be handled.
>

=E2=80=8BI talked to my openly gay friends living in Singapore and told the=
m about
the discussions that's happening here. For what it's worth, I will pass on
details to IAOC if that helps.

Thanks!
Dhruv

=E2=80=8BPS. I agree that getting early feedback about a new place is a goo=
d idea
and should be followed in future. =E2=80=8B



>
> Your point about derailment makes sense, though--this is definitely a
> separate issue from the "virtual IETF" issue.
>
> On Tue, Apr 12, 2016 at 9:18 AM, Loa Andersson <loa@pi.nu> wrote:
>
>> Folks,
>>
>> On 2016-04-12 19:15, Tim Chown wrote:
>>
>>> On 12 Apr 2016, at 01:50, Ted Lemon <mellon@fugue.com> wrote:
>>>>
>>>> The only thing you mentioned that can't be done with existing
>>>> conferencing software is hums, and I'm sure we could figure out a way =
to
>>>> make that work.  It's not rocket science.   Chairs who judge consensus=
 by
>>>> looking at the room aren't following IETF process--consensus is judged=
 on
>>>> the mailing list.  Hums are useful for figuring out why we _don't_ hav=
e
>>>> consensus, and for _getting_ to consensus, but if you were to judge
>>>> consensus by hums or a show of hands, then you'd be taking a vote, wou=
ldn't
>>>> you?
>>>>
>>>
>>> Meetecho has a =E2=80=98hum=E2=80=99 button, which throws =E2=80=98hmmm=
mmm=E2=80=99 into the jabber room
>>> for the WG. I did see it used, once.
>>>
>>
>> Let me return to the start of this discussion.
>>
>> It seems to me that the LGBTQ peoples concern about a meeting in
>> Singapore is real, at least it is perceived to be real.
>>
>> I don't think anything that is within our power to do can change this
>> perception.
>>
>> Thus we need to take this seriously, the concerns is about our upcoming
>> meeting in Singapore. That should be our focus.
>>
>> /Loa
>>
>>
>>> Tim
>>>
>>>
>>
>

--001a113f89b4a206c505304c855b
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-family:trebuche=
t ms,sans-serif;color:#4c1130">Hi,=C2=A0</div><div class=3D"gmail_extra"><b=
r><div class=3D"gmail_quote">On Tue, Apr 12, 2016 at 10:34 AM, Ted Lemon <s=
pan dir=3D"ltr">&lt;<a href=3D"mailto:mellon@fugue.com" target=3D"_blank">m=
ellon@fugue.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" =
style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><di=
v dir=3D"ltr"><div>I think that at this point the question of what we can d=
o to address the Singapore problem is in the hands of the IAOC, which has i=
ndicated a willingness to explore going even further than Ted asked them to=
 in addressing the problem. =C2=A0 Ted asked them to not bring their famili=
es to Singapore in solidarity with him, since he doesn&#39;t feel safe brin=
ging his family. =C2=A0 </div></div></blockquote><div><br></div><div><div c=
lass=3D"gmail_default" style=3D"font-family:&quot;trebuchet ms&quot;,sans-s=
erif;color:rgb(76,17,48)">=E2=80=8BTed has a point and it is a concern that=
 we (as a part of the gay community) have to deal with it daily.</div></div=
><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .=
8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div>The =
IAOC has said they are looking into how difficult it would be to actually m=
ove IETF 100 to a different country. =C2=A0 </div></div></blockquote><div><=
br></div><div><div class=3D"gmail_default" style=3D"font-family:&quot;trebu=
chet ms&quot;,sans-serif;color:rgb(76,17,48)">=E2=80=8BBut, to me this is i=
nteresting, that we took the discussion,=C2=A0from solidarity and understan=
ding of the difficulties that the gay community faces,=C2=A0to sort of esca=
ping it and not dealing with it. By setting this precedence I=C2=A0am afrai=
d IETF would not take place in a large part of the world=C2=A0in coming yea=
rs.=C2=A0</div><div class=3D"gmail_default" style=3D"font-family:&quot;treb=
uchet ms&quot;,sans-serif;color:rgb(76,17,48)"><br></div><div class=3D"gmai=
l_default" style=3D"font-family:&quot;trebuchet ms&quot;,sans-serif;color:r=
gb(76,17,48)">And isn&#39;t that excluding people (which BTW *also* include=
s the members of the same gay community, but from this part of the world)? =
=C2=A0 =C2=A0=C2=A0</div></div><div>=C2=A0</div><blockquote class=3D"gmail_=
quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1=
ex"><div dir=3D"ltr"><div>So I don&#39;t think there&#39;s anything for us =
to discuss here, unless you are a member of the LGBTQ+ community and have s=
omething to add about how you think Singapore should be handled.</div></div=
></blockquote><div><br></div><div><div class=3D"gmail_default" style=3D"fon=
t-family:&quot;trebuchet ms&quot;,sans-serif;color:rgb(76,17,48)">=E2=80=8B=
I talked to my openly gay friends living in Singapore and told them about t=
he discussions that&#39;s happening here. For what=C2=A0it&#39;s worth, I w=
ill pass on details to IAOC if that helps.=C2=A0</div></div><div class=3D"g=
mail_default" style=3D"font-family:&quot;trebuchet ms&quot;,sans-serif;colo=
r:rgb(76,17,48)"><br></div><div class=3D"gmail_default" style=3D"font-famil=
y:&quot;trebuchet ms&quot;,sans-serif;color:rgb(76,17,48)">Thanks!=C2=A0</d=
iv><div class=3D"gmail_default" style=3D"font-family:&quot;trebuchet ms&quo=
t;,sans-serif;color:rgb(76,17,48)">Dhruv</div><div><br></div><div><div clas=
s=3D"gmail_default" style=3D"font-family:&quot;trebuchet ms&quot;,sans-seri=
f;color:rgb(76,17,48)">=E2=80=8BPS. I agree that getting early feedback abo=
ut a new place is a good idea and should be followed=C2=A0in future. =E2=80=
=8B</div><br></div><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=
=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=
=3D"ltr"><div><br>Your point about derailment makes sense, though--this is =
definitely a separate issue from the &quot;virtual IETF&quot; issue.</div><=
/div><div class=3D"HOEnZb"><div class=3D"h5"><div class=3D"gmail_extra"><br=
><div class=3D"gmail_quote">On Tue, Apr 12, 2016 at 9:18 AM, Loa Andersson =
<span dir=3D"ltr">&lt;<a href=3D"mailto:loa@pi.nu" target=3D"_blank">loa@pi=
.nu</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"mar=
gin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Folks,<span><br=
>
<br>
On 2016-04-12 19:15, Tim Chown wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><blockquote class=3D"gmail_quote" style=3D"m=
argin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On 12 Apr 2016, at 01:50, Ted Lemon &lt;<a href=3D"mailto:mellon@fugue.com"=
 target=3D"_blank">mellon@fugue.com</a>&gt; wrote:<br>
<br>
The only thing you mentioned that can&#39;t be done with existing conferenc=
ing software is hums, and I&#39;m sure we could figure out a way to make th=
at work.=C2=A0 It&#39;s not rocket science.=C2=A0 =C2=A0Chairs who judge co=
nsensus by looking at the room aren&#39;t following IETF process--consensus=
 is judged on the mailing list.=C2=A0 Hums are useful for figuring out why =
we _don&#39;t_ have consensus, and for _getting_ to consensus, but if you w=
ere to judge consensus by hums or a show of hands, then you&#39;d be taking=
 a vote, wouldn&#39;t you?<br>
</blockquote>
<br>
Meetecho has a =E2=80=98hum=E2=80=99 button, which throws =E2=80=98hmmmmmm=
=E2=80=99 into the jabber room for the WG. I did see it used, once.<br>
</blockquote>
<br></span>
Let me return to the start of this discussion.<br>
<br>
It seems to me that the LGBTQ peoples concern about a meeting in<br>
Singapore is real, at least it is perceived to be real.<br>
<br>
I don&#39;t think anything that is within our power to do can change this<b=
r>
perception.<br>
<br>
Thus we need to take this seriously, the concerns is about our upcoming<br>
meeting in Singapore. That should be our focus.<br>
<br>
/Loa<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<br>
Tim<br>
<br>
</blockquote>
<br>
</blockquote></div><br></div>
</div></div></blockquote></div><br></div></div>

--001a113f89b4a206c505304c855b--


From nobody Tue Apr 12 10:02:21 2016
Return-Path: <mellon@fugue.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 3DC4212E2C0 for <ietf@ietfa.amsl.com>; Tue, 12 Apr 2016 10:02:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.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 Qi2VXokowbAQ for <ietf@ietfa.amsl.com>; Tue, 12 Apr 2016 10:02:17 -0700 (PDT)
Received: from mail-lf0-x229.google.com (mail-lf0-x229.google.com [IPv6:2a00:1450:4010:c07::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 9251A12E29E for <ietf@ietf.org>; Tue, 12 Apr 2016 10:02:16 -0700 (PDT)
Received: by mail-lf0-x229.google.com with SMTP id e190so34400341lfe.0 for <ietf@ietf.org>; Tue, 12 Apr 2016 10:02:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=DvBFZZ7RsHXgMXpYdne/tGcVgmUBFHyfbCCFNaglB0U=; b=eCUAfd58KaK0gqJUpXEMzyq5SvHWx6/mPx99goSiH1E9AhnDzPnT74p921x6nrweiy tfBkRfgM85lL3J/gQ7LUwuqytZxiaIn8ZlOQ1VlxyuG3Gkrc2z52I2jtUrefAVXvg4Aj oEM/5VheSDkt0RlLQyiHVRJQYUnQoQZE/XjbHgM3T23v+IBO7i3Fxyp/e92oA687ko4Z QHzN0+x4cAa++vH/AjXfO1Tvz/kIneF2Ci4+AEGCChFmePMVNXdJzu8He3OxsuttXWBT lCI9WRbAN2Rn5qv0hnZT2kUWFZU4di0fL0M+hC0A6gR0Rt4A+opEKs4T33qZ5iCqZhLO zlUA==
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=DvBFZZ7RsHXgMXpYdne/tGcVgmUBFHyfbCCFNaglB0U=; b=KzhnNXceGBKwYwjNVPJOWeKTaB3vCtp+HRjV23+auePP1i7peQ0BNeoPNSsG4I/XZ6 eDRiC0Xu1ORpekhLxQEuU4Azf2PFBVI1vyoqV87qBgKx62jQh95S6T4N2wzoAThlbt6T ARn4JF9P9FgUBIhXHfUaAwQyVGBO7l0YnEv6J9bVe53ghjv+RdfDpqKitVzLLMG7kerA o5y2GhcLcu6bllCp20lBYjUYSpZJ8Hxq3Oeuiyao91gLu1CF4VJyZShE6L/SfE41yuMm ldPetMoTLRJEyva56DgqS25JB0GzXHoPrKPgKZYzcmKueMAIWsOtpRJhA0wu9XzY9aEi Ksig==
X-Gm-Message-State: AOPr4FUUGB5W/VUS9lq71lXzvB1u6Ku6Qrh5SvFzfg8rgTjLNcRu6FjqTX7ggrf/6BP2gd5DUNNUeODLZnGLWw==
X-Received: by 10.25.73.212 with SMTP id w203mr1582375lfa.22.1460480534789; Tue, 12 Apr 2016 10:02:14 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.25.40.136 with HTTP; Tue, 12 Apr 2016 10:01:34 -0700 (PDT)
X-Originating-IP: [71.233.41.235]
In-Reply-To: <CAB75xn6Ev6YhCu9T6nmqBEgK8wVUKqBLGJ+cn4HCPPnsZzkwNQ@mail.gmail.com>
References: <m260vp7eke.wl%randy@psg.com> <570A6458.3050206@comcast.net> <m21t6d7c9t.wl%randy@psg.com> <570A67B4.3010206@comcast.net> <570AB3AF.2050401@gmail.com> <87twj99c6w.fsf@tops.chopps.org> <CAKe6YvMyp-DyeDwpPY6KYmbDbnpgnvVk_cUStnA32wmgDWcz3w@mail.gmail.com> <BBF5DDFE515C3946BC18D733B20DAD233A62AA18@XMB122CNC.rim.net> <20160411104519.GA19092@gsp.org> <3F48466D-390C-4C18-B958-732AE3E46FF1@gmail.com> <20160411223403.GA6743@gsp.org> <CAPt1N1nNo0=JSptQdWRZCFy1v-m6Q8NQy4WVGHtnRJuFZFmMig@mail.gmail.com> <CAKr6gn1KmNcgNwbPHZWB2aJQAuchz4eB7gxJhV2Dsbc1Z50kDw@mail.gmail.com> <CAPt1N1mWjg_-525avYJ4PnSECYQrtpVFJCXPfH=PryJ8q0vy4Q@mail.gmail.com> <A684A3C4-7161-49F5-919E-A5F948A3F316@ecs.soton.ac.uk> <EMEW3|d5cb2cb80712b3716e1ab4e2a54c9430s3BCG403tjc|ecs.soton.ac.uk|A684A3C4-7161-49F5-919E-A5F948A3F316@ecs.soton.ac.uk> <570CF594.5070509@pi.nu> <CAPt1N1m_gbTMdxUfqgUDdKfw56E7Exfo6QU2GuxxueN_gPFCwQ@mail.gmail.com> <CAB75xn6Ev6YhCu9T6nmqBEgK8wVUKqBLGJ+cn4HCPPnsZzkwNQ@mail.gmail.com>
From: Ted Lemon <mellon@fugue.com>
Date: Tue, 12 Apr 2016 13:01:34 -0400
Message-ID: <CAPt1N1khBH4HzDg50LP9sziZXM2rURcA6b-yv=vi2M8i=4d91w@mail.gmail.com>
Subject: Re: Concerns about Singapore
To: Dhruv Dhody <dhruv.ietf@gmail.com>
Content-Type: multipart/alternative; boundary=001a114b15927a577d05304c9f7d
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/SdAETrUH2FiDifz5-Ed6Ukpxtss>
Cc: ietf <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: Tue, 12 Apr 2016 17:02:19 -0000

--001a114b15927a577d05304c9f7d
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

I suppose another way to frame it is to ask how many LGBTQ+ folks in
Singapore would be included because of an IETF in Singapore, versus how
many LGBTQ+ folks not in Singapore would feel excluded or disadvantaged
because of an IETF in Singapore.   Because I'm not personally impacted by
this, I don't really have a sense of how one could evaluate that.   I think
sharing your thoughts about this with the IAOC would be a very good idea.

On Tue, Apr 12, 2016 at 12:55 PM, Dhruv Dhody <dhruv.ietf@gmail.com> wrote:

> Hi,
>
> On Tue, Apr 12, 2016 at 10:34 AM, Ted Lemon <mellon@fugue.com> wrote:
>
>> I think that at this point the question of what we can do to address the
>> Singapore problem is in the hands of the IAOC, which has indicated a
>> willingness to explore going even further than Ted asked them to in
>> addressing the problem.   Ted asked them to not bring their families to
>> Singapore in solidarity with him, since he doesn't feel safe bringing hi=
s
>> family.
>>
>
> =E2=80=8BTed has a point and it is a concern that we (as a part of the ga=
y
> community) have to deal with it daily.
>
>
>> The IAOC has said they are looking into how difficult it would be to
>> actually move IETF 100 to a different country.
>>
>
> =E2=80=8BBut, to me this is interesting, that we took the discussion, fro=
m
> solidarity and understanding of the difficulties that the gay community
> faces, to sort of escaping it and not dealing with it. By setting this
> precedence I am afraid IETF would not take place in a large part of the
> world in coming years.
>
> And isn't that excluding people (which BTW *also* includes the members of
> the same gay community, but from this part of the world)?
>
>
>> So I don't think there's anything for us to discuss here, unless you are
>> a member of the LGBTQ+ community and have something to add about how you
>> think Singapore should be handled.
>>
>
> =E2=80=8BI talked to my openly gay friends living in Singapore and told t=
hem about
> the discussions that's happening here. For what it's worth, I will pass o=
n
> details to IAOC if that helps.
>
> Thanks!
> Dhruv
>
> =E2=80=8BPS. I agree that getting early feedback about a new place is a g=
ood idea
> and should be followed in future. =E2=80=8B
>
>
>
>>
>> Your point about derailment makes sense, though--this is definitely a
>> separate issue from the "virtual IETF" issue.
>>
>> On Tue, Apr 12, 2016 at 9:18 AM, Loa Andersson <loa@pi.nu> wrote:
>>
>>> Folks,
>>>
>>> On 2016-04-12 19:15, Tim Chown wrote:
>>>
>>>> On 12 Apr 2016, at 01:50, Ted Lemon <mellon@fugue.com> wrote:
>>>>>
>>>>> The only thing you mentioned that can't be done with existing
>>>>> conferencing software is hums, and I'm sure we could figure out a way=
 to
>>>>> make that work.  It's not rocket science.   Chairs who judge consensu=
s by
>>>>> looking at the room aren't following IETF process--consensus is judge=
d on
>>>>> the mailing list.  Hums are useful for figuring out why we _don't_ ha=
ve
>>>>> consensus, and for _getting_ to consensus, but if you were to judge
>>>>> consensus by hums or a show of hands, then you'd be taking a vote, wo=
uldn't
>>>>> you?
>>>>>
>>>>
>>>> Meetecho has a =E2=80=98hum=E2=80=99 button, which throws =E2=80=98hmm=
mmmm=E2=80=99 into the jabber
>>>> room for the WG. I did see it used, once.
>>>>
>>>
>>> Let me return to the start of this discussion.
>>>
>>> It seems to me that the LGBTQ peoples concern about a meeting in
>>> Singapore is real, at least it is perceived to be real.
>>>
>>> I don't think anything that is within our power to do can change this
>>> perception.
>>>
>>> Thus we need to take this seriously, the concerns is about our upcoming
>>> meeting in Singapore. That should be our focus.
>>>
>>> /Loa
>>>
>>>
>>>> Tim
>>>>
>>>>
>>>
>>
>

--001a114b15927a577d05304c9f7d
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">I suppose another way to frame it is to ask how many LGBTQ=
+ folks in Singapore would be included because of an IETF in Singapore, ver=
sus how many LGBTQ+ folks not in Singapore would feel excluded or disadvant=
aged because of an IETF in Singapore. =C2=A0 Because I&#39;m not personally=
 impacted by this, I don&#39;t really have a sense of how one could evaluat=
e that. =C2=A0 I think sharing your thoughts about this with the IAOC would=
 be a very good idea.</div><div class=3D"gmail_extra"><br><div class=3D"gma=
il_quote">On Tue, Apr 12, 2016 at 12:55 PM, Dhruv Dhody <span dir=3D"ltr">&=
lt;<a href=3D"mailto:dhruv.ietf@gmail.com" target=3D"_blank">dhruv.ietf@gma=
il.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"=
margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"=
ltr"><div class=3D"gmail_default" style=3D"font-family:trebuchet ms,sans-se=
rif;color:#4c1130">Hi,=C2=A0</div><div class=3D"gmail_extra"><br><div class=
=3D"gmail_quote"><span class=3D"">On Tue, Apr 12, 2016 at 10:34 AM, Ted Lem=
on <span dir=3D"ltr">&lt;<a href=3D"mailto:mellon@fugue.com" target=3D"_bla=
nk">mellon@fugue.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_qu=
ote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex=
"><div dir=3D"ltr"><div>I think that at this point the question of what we =
can do to address the Singapore problem is in the hands of the IAOC, which =
has indicated a willingness to explore going even further than Ted asked th=
em to in addressing the problem. =C2=A0 Ted asked them to not bring their f=
amilies to Singapore in solidarity with him, since he doesn&#39;t feel safe=
 bringing his family. =C2=A0 </div></div></blockquote><div><br></div></span=
><div><div class=3D"gmail_default" style=3D"font-family:&quot;trebuchet ms&=
quot;,sans-serif;color:rgb(76,17,48)">=E2=80=8BTed has a point and it is a =
concern that we (as a part of the gay community) have to deal with it daily=
.</div></div><span class=3D""><div>=C2=A0</div><blockquote class=3D"gmail_q=
uote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1e=
x"><div dir=3D"ltr"><div>The IAOC has said they are looking into how diffic=
ult it would be to actually move IETF 100 to a different country. =C2=A0 </=
div></div></blockquote><div><br></div></span><div><div class=3D"gmail_defau=
lt" style=3D"font-family:&quot;trebuchet ms&quot;,sans-serif;color:rgb(76,1=
7,48)">=E2=80=8BBut, to me this is interesting, that we took the discussion=
,=C2=A0from solidarity and understanding of the difficulties that the gay c=
ommunity faces,=C2=A0to sort of escaping it and not dealing with it. By set=
ting this precedence I=C2=A0am afraid IETF would not take place in a large =
part of the world=C2=A0in coming years.=C2=A0</div><div class=3D"gmail_defa=
ult" style=3D"font-family:&quot;trebuchet ms&quot;,sans-serif;color:rgb(76,=
17,48)"><br></div><div class=3D"gmail_default" style=3D"font-family:&quot;t=
rebuchet ms&quot;,sans-serif;color:rgb(76,17,48)">And isn&#39;t that exclud=
ing people (which BTW *also* includes the members of the same gay community=
, but from this part of the world)? =C2=A0 =C2=A0=C2=A0</div></div><span cl=
ass=3D""><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin=
:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr"><=
div>So I don&#39;t think there&#39;s anything for us to discuss here, unles=
s you are a member of the LGBTQ+ community and have something to add about =
how you think Singapore should be handled.</div></div></blockquote><div><br=
></div></span><div><div class=3D"gmail_default" style=3D"font-family:&quot;=
trebuchet ms&quot;,sans-serif;color:rgb(76,17,48)">=E2=80=8BI talked to my =
openly gay friends living in Singapore and told them about the discussions =
that&#39;s happening here. For what=C2=A0it&#39;s worth, I will pass on det=
ails to IAOC if that helps.=C2=A0</div></div><div class=3D"gmail_default" s=
tyle=3D"font-family:&quot;trebuchet ms&quot;,sans-serif;color:rgb(76,17,48)=
"><br></div><div class=3D"gmail_default" style=3D"font-family:&quot;trebuch=
et ms&quot;,sans-serif;color:rgb(76,17,48)">Thanks!=C2=A0</div><div class=
=3D"gmail_default" style=3D"font-family:&quot;trebuchet ms&quot;,sans-serif=
;color:rgb(76,17,48)">Dhruv</div><div><br></div><div><div class=3D"gmail_de=
fault" style=3D"font-family:&quot;trebuchet ms&quot;,sans-serif;color:rgb(7=
6,17,48)">=E2=80=8BPS. I agree that getting early feedback about a new plac=
e is a good idea and should be followed=C2=A0in future. =E2=80=8B</div><br>=
</div><span class=3D""><div>=C2=A0</div><blockquote class=3D"gmail_quote" s=
tyle=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div=
 dir=3D"ltr"><div><br>Your point about derailment makes sense, though--this=
 is definitely a separate issue from the &quot;virtual IETF&quot; issue.</d=
iv></div><div><div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote=
">On Tue, Apr 12, 2016 at 9:18 AM, Loa Andersson <span dir=3D"ltr">&lt;<a h=
ref=3D"mailto:loa@pi.nu" target=3D"_blank">loa@pi.nu</a>&gt;</span> wrote:<=
br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left=
:1px #ccc solid;padding-left:1ex">Folks,<span><br>
<br>
On 2016-04-12 19:15, Tim Chown wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><blockquote class=3D"gmail_quote" style=3D"m=
argin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On 12 Apr 2016, at 01:50, Ted Lemon &lt;<a href=3D"mailto:mellon@fugue.com"=
 target=3D"_blank">mellon@fugue.com</a>&gt; wrote:<br>
<br>
The only thing you mentioned that can&#39;t be done with existing conferenc=
ing software is hums, and I&#39;m sure we could figure out a way to make th=
at work.=C2=A0 It&#39;s not rocket science.=C2=A0 =C2=A0Chairs who judge co=
nsensus by looking at the room aren&#39;t following IETF process--consensus=
 is judged on the mailing list.=C2=A0 Hums are useful for figuring out why =
we _don&#39;t_ have consensus, and for _getting_ to consensus, but if you w=
ere to judge consensus by hums or a show of hands, then you&#39;d be taking=
 a vote, wouldn&#39;t you?<br>
</blockquote>
<br>
Meetecho has a =E2=80=98hum=E2=80=99 button, which throws =E2=80=98hmmmmmm=
=E2=80=99 into the jabber room for the WG. I did see it used, once.<br>
</blockquote>
<br></span>
Let me return to the start of this discussion.<br>
<br>
It seems to me that the LGBTQ peoples concern about a meeting in<br>
Singapore is real, at least it is perceived to be real.<br>
<br>
I don&#39;t think anything that is within our power to do can change this<b=
r>
perception.<br>
<br>
Thus we need to take this seriously, the concerns is about our upcoming<br>
meeting in Singapore. That should be our focus.<br>
<br>
/Loa<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<br>
Tim<br>
<br>
</blockquote>
<br>
</blockquote></div><br></div>
</div></div></blockquote></span></div><br></div></div>
</blockquote></div><br></div>

--001a114b15927a577d05304c9f7d--


From nobody Tue Apr 12 10:02:38 2016
Return-Path: <melinda.shore@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 9FFA412E59E for <ietf@ietfa.amsl.com>; Tue, 12 Apr 2016 10:02:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 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, RCVD_IN_DNSWL_LOW=-0.7, 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 qxaYENa705Bn for <ietf@ietfa.amsl.com>; Tue, 12 Apr 2016 10:02:33 -0700 (PDT)
Received: from mail-pa0-x234.google.com (mail-pa0-x234.google.com [IPv6:2607:f8b0:400e:c03::234]) (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 25F5D12E4AE for <ietf@ietf.org>; Tue, 12 Apr 2016 10:02:27 -0700 (PDT)
Received: by mail-pa0-x234.google.com with SMTP id zm5so16787184pac.0 for <ietf@ietf.org>; Tue, 12 Apr 2016 10:02:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding; bh=N+YVmNv6VMkUl3HMEMKyt8kLUwfPi5+uRLH785gT8wc=; b=W4sa0f6E0h3EgGD5qKLe94nxun2Oo9xTQHLrSro2EeZks3CzQN3srk6FhvcgswTg0k Fvkm4BSUdosvoBH58aXlgiBYqYW6emCuhHRN1hpsydxh3YGa7o8ddBOtGdMTsUp1xxs+ 01+T1y6avCbC5hyzTIH1i4TTnkF2Au3cay8dAiUXpUhBN8G5/J5ayHnG1Bunm/S+/rqX wDTpIY2JR5SDyPMvmIJtheGNzGlWaoPBSbYCwQ3DO6SjaQsazrF18Myj7QFOfItYQd31 GIo95hJ+Cw1YQEELcgOspxBxkZcU8y93ehxrpPD0bpliXtkuK3ZUZuvptl10hNjtTY83 vMKA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=N+YVmNv6VMkUl3HMEMKyt8kLUwfPi5+uRLH785gT8wc=; b=QLa3y3muCy9MmRue6AM2ZHzJwyLbEt69Js6x8tF+DKZeLdsqqwbb5IPmx6hYu9lvy/ DmU3fqnRq9hBiQGptkUvWzH8IbHXopUADUu6UuLjhqqYN00L3xFGluAoBAqMJfmPU687 dfaRZILlzTxCin7O/El/G6Iw0fgVMhIn61kwvE7wCkp0QWWq0HHkDMn1dbEPuJ/12oR8 CZhp8FM/Y8k+FDb5VtmOQjPtHJ3pnkKqJSRss4BF+0hVZbCCCKSNilvtnoH8vxOho9po Khv8U8yHdf/l7T9pnchyWoNVAIWtYfLu1nSUSzb9SqATXCY3oGOJ8O4ZcQBNad8Zo7Oi Cvhw==
X-Gm-Message-State: AOPr4FXNrm8z2J44l+Le0jRdI2SiaTnaJWJTwr5pqf5SvmIHCnJoe9uWrv55ZEToEh7rGg==
X-Received: by 10.66.160.168 with SMTP id xl8mr6091230pab.132.1460480546922; Tue, 12 Apr 2016 10:02:26 -0700 (PDT)
Received: from Melindas-MacBook-Pro.local (216-67-8-215-radius.dynamic.acsalaska.net. [216.67.8.215]) by smtp.googlemail.com with ESMTPSA id to9sm45051315pab.27.2016.04.12.10.02.25 for <ietf@ietf.org> (version=TLSv1/SSLv3 cipher=OTHER); Tue, 12 Apr 2016 10:02:25 -0700 (PDT)
Subject: Re: Remote only meetings? [Re: Concerns about Singapore]
To: ietf@ietf.org
References: <m21t6d7c9t.wl%randy@psg.com> <570A67B4.3010206@comcast.net> <570AB3AF.2050401@gmail.com> <87twj99c6w.fsf@tops.chopps.org> <CAKe6YvMyp-DyeDwpPY6KYmbDbnpgnvVk_cUStnA32wmgDWcz3w@mail.gmail.com> <BBF5DDFE515C3946BC18D733B20DAD233A62AA18@XMB122CNC.rim.net> <20160411104519.GA19092@gsp.org> <3F48466D-390C-4C18-B958-732AE3E46FF1@gmail.com> <20160411223403.GA6743@gsp.org> <87twj7eon7.fsf@tops.chopps.org> <20160412110839.GA20488@gsp.org> <8760vn82f2.fsf@tops.chopps.org>
From: Melinda Shore <melinda.shore@gmail.com>
Message-ID: <570D2A34.1030700@gmail.com>
Date: Tue, 12 Apr 2016 09:02:44 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:38.0) Gecko/20100101 Thunderbird/38.6.0
MIME-Version: 1.0
In-Reply-To: <8760vn82f2.fsf@tops.chopps.org>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/-3oDv6D13MGCGctzAXNqMbS3qh4>
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: Tue, 12 Apr 2016 17:02:35 -0000

On 4/12/16 3:57 AM, chopps@chopps.org wrote:
> Rich Kulawiec <rsk@gsp.org> writes:
>> Because it works exclusively for the elite, privileged few.  (And no
>> doubt: it works quite well.)  But it's the antithesis of inclusion
>> and diversity -- and I think those qualities are increasingly necessary.
>
> But this is not how the IETF operates.

Actually, it's very much how the IETF operates in practice,
particularly with meeting participation becoming increasingly
expensive and with increased participation from "standards
professionals."  If you've been to meetings you'll have
noticed some chairs taking votes in meetings (rather than
relying on consensus processes) and saying that they'll
ratify or confirm that decision on the mailing list (if
they remember - sometimes they don't).

In some sense the Singapore announcement felt to me as if
we'd completed the transition to plain ol' standards body,
distinguishable from the others by what we say rather than
by what we do.

One of the things I've been thinking about over the past
<n> years is how to reduce our reliance on meetings, and
I'm overdue on writing up a draft on it.  I think it's
an important question, since de-emphasizing (not eliminating)
meetings is one thing we can do to keep participation more
open and accessible.

Melinda


From nobody Tue Apr 12 10:08:44 2016
Return-Path: <melinda.shore@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 5C3B012DA0C for <ietf@ietfa.amsl.com>; Tue, 12 Apr 2016 10:08:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 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, RCVD_IN_DNSWL_LOW=-0.7, 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 h902RIoYPLOy for <ietf@ietfa.amsl.com>; Tue, 12 Apr 2016 10:08:40 -0700 (PDT)
Received: from mail-pf0-x22d.google.com (mail-pf0-x22d.google.com [IPv6:2607:f8b0:400e:c00::22d]) (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 7C52912DEA0 for <ietf@ietf.org>; Tue, 12 Apr 2016 10:08:39 -0700 (PDT)
Received: by mail-pf0-x22d.google.com with SMTP id c20so17159788pfc.1 for <ietf@ietf.org>; Tue, 12 Apr 2016 10:08:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding; bh=w+Mi03Flg2HXDJzikFfwwmjU2N4fvt6QqCBHOiW+jrY=; b=aDqw1VWL7+fL6peYnB+OMdCgSz65/CC+VDi9p5LsuQ+eq0GwqH1/NIvq911WUzKW0S M3zAK7saC5I4qVuHHjt6YDYDcuglCdEtzblLyLkGPcx+VX20aQnnzaSoTv7108KBAxhG JcMtfbGbb2HjF3P9RnFZCMWfFuqvbE+q30Mrm1Y6nXnWJT6EakIE5BDsV/jp9jSeSnbu Yk7XmDWBwgdiCHjp1gQCWKxKu957pottQL+qbRJgN376jjLxsI5orRAqahH2VZ/gX7YO P9YDhigzeL6bwx409iDep+nKRUYYQsWr/FP+iGgd0fQ22VCecmIY7hxnuNq04jCKNMu1 Vj9Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=w+Mi03Flg2HXDJzikFfwwmjU2N4fvt6QqCBHOiW+jrY=; b=hEC56CLf4CN5b5XhfIkPm3NbQYsM6nYPmAWMrLUrVLZ4LpfU8+b3G0fjmHJaCFtAj2 THrgsOllvwtLcayGO/daSAdrsWSFjdl0SQ4dI2Dqd9YJbKjM32xzDerLvnEYFdiwPyXZ V/PHC3Iliw8wSiUg4sHppW3YnxfSEeM76C0zU1lam8f1vCPiWExBrJAe6D0Zp2YeltEJ q2ZnOct7fks6vOg+rqEVpwOGT7ugDwNojSn31rhyuy295V7+56a8zjZkpnyCePMx1d7e LWj04iuFH0DGdg1kWvR1f1riO393c3ExBaorvpUyHuPKbA43iRVm9AQsANCtNncZzb9V bDHw==
X-Gm-Message-State: AOPr4FUKcR5EmvoG5EL1jlUP712qxJPvLjx42wdOpnnrina3kwzlqFQpgsrQtMmdAgHFFQ==
X-Received: by 10.98.79.203 with SMTP id f72mr6218683pfj.102.1460480919117; Tue, 12 Apr 2016 10:08:39 -0700 (PDT)
Received: from Melindas-MacBook-Pro.local (216-67-8-215-radius.dynamic.acsalaska.net. [216.67.8.215]) by smtp.googlemail.com with ESMTPSA id dy6sm45052065pab.48.2016.04.12.10.08.37 for <ietf@ietf.org> (version=TLSv1/SSLv3 cipher=OTHER); Tue, 12 Apr 2016 10:08:38 -0700 (PDT)
Subject: Re: Remote only meetings? [Re: Concerns about Singapore]
To: ietf@ietf.org
References: <570AB3AF.2050401@gmail.com> <87twj99c6w.fsf@tops.chopps.org> <CAKe6YvMyp-DyeDwpPY6KYmbDbnpgnvVk_cUStnA32wmgDWcz3w@mail.gmail.com> <BBF5DDFE515C3946BC18D733B20DAD233A62AA18@XMB122CNC.rim.net> <20160411104519.GA19092@gsp.org> <3F48466D-390C-4C18-B958-732AE3E46FF1@gmail.com> <20160411223403.GA6743@gsp.org> <87twj7eon7.fsf@tops.chopps.org> <20160412110839.GA20488@gsp.org> <8760vn82f2.fsf@tops.chopps.org> <20160412124639.GA27223@gsp.org> <87fuurgd8f.fsf@tops.chopps.org> <CABmDk8kCfTB_AKyqV4X+AghL2G7i+XcKR=tzV0jybM05k+UU4Q@mail.gmail.com> <65989154-BD08-45F0-B6F0-2AE3E435409C@chopps.org>
From: Melinda Shore <melinda.shore@gmail.com>
Message-ID: <570D2BAD.7000307@gmail.com>
Date: Tue, 12 Apr 2016 09:09:01 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:38.0) Gecko/20100101 Thunderbird/38.6.0
MIME-Version: 1.0
In-Reply-To: <65989154-BD08-45F0-B6F0-2AE3E435409C@chopps.org>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/jDj6CZRQ1A6ex0DS2db9XRWWFTs>
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: Tue, 12 Apr 2016 17:08:42 -0000

On 4/12/16 6:20 AM, Christian Hopps wrote:
> I think we need to look at a good sampling of the data at this point.

Have at it.

Melinda



From nobody Tue Apr 12 10:17:37 2016
Return-Path: <hallam@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 F2BDF12EA94 for <ietf@ietfa.amsl.com>; Tue, 12 Apr 2016 10:17:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.4
X-Spam-Level: 
X-Spam-Status: No, score=-2.4 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.199, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 i5gL_WcSX-eD for <ietf@ietfa.amsl.com>; Tue, 12 Apr 2016 10:17:31 -0700 (PDT)
Received: from mail-lf0-x234.google.com (mail-lf0-x234.google.com [IPv6:2a00:1450:4010:c07::234]) (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 4FB8C12EA6F for <ietf@ietf.org>; Tue, 12 Apr 2016 10:17:30 -0700 (PDT)
Received: by mail-lf0-x234.google.com with SMTP id g184so34818344lfb.3 for <ietf@ietf.org>; Tue, 12 Apr 2016 10:17:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc; bh=WXd1CwSv7EU8ROdvsqqVgvKCX1t9GycPhxeZ2+ESQ+0=; b=je9X03Ic+38SHVrN/VJg6heZFq3pp3W2BPD+cKZqiCt0w3gBIQXPd7qiyoi66QOMdm OQlOssLyG7jlRwHlxeAWNSVAy1xQU9GxlmDtfUcpyw+zeFNcNZ8xSNpYczDbpA9nQNF5 +/ER0FQRt1yTIeDlCR5Ojjup9IY5529m5zA79P+uluCO1VeaKg9AL6904t+g4lh+a/7k mzwwbaZt//QaRLKIeAZmNbxiH/GLIkb+4VOSpFzP82r4igMuU9BYpdj0S97Jt+DzQDXq udafUKycUju5sYrup26GtNxbOqLAEvrnwtYNv6baWhGN7pZDVKKu8sQfpZsvGs4fUTkT Q5mg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:date :message-id:subject:from:to:cc; bh=WXd1CwSv7EU8ROdvsqqVgvKCX1t9GycPhxeZ2+ESQ+0=; b=BKELimZl4L8D5IWbnqT2Emyf0wCuXvi9XgvZdgBWzcWPJEStrNj5w0C89fuJsWnm0+ ImwTZSh/NgdXknGWAD9GST8G8krnzkervRobK3pqbQ51mzhMqMYqxrCndAZZJe6Jk+Bk y4uGZ4ivc74SV8Q7h8SUY8agDVZ4tSN8H3R2EzxfwoR8oH5xfuxo7ejjigkBc+ZzK2eV edPV4eaKLbYHiW2NHFLwArILtoQ200WX+nGZtwLnpvjKRtvcacSvwRXiERexPg7IxqKc fPeMzxPWVSr7/Be6ADM777PR/78UKfrtu57K8D1IB/OyVeuhkgXpp2MTp+2inuDUyjRe dnqg==
X-Gm-Message-State: AOPr4FUWYeeho1xyjEjXlh4KqV55dVEO6mTtSd4Mm93uvitwxHkLLMcl+8o7UJd1SMWbW/2zUr+NqpTPvYRNWA==
MIME-Version: 1.0
X-Received: by 10.25.208.144 with SMTP id h138mr1531518lfg.48.1460481448479; Tue, 12 Apr 2016 10:17:28 -0700 (PDT)
Sender: hallam@gmail.com
Received: by 10.112.151.67 with HTTP; Tue, 12 Apr 2016 10:17:28 -0700 (PDT)
In-Reply-To: <CAPt1N1nLWrVqGpPh+h=Ano6PJyw2ZRaroiAMgG4RDKTFV7rkpA@mail.gmail.com>
References: <alpine.OSX.2.01.1604100736080.45987@rabdullah.local> <20160410181958.58762.qmail@ary.lan> <CAMm+LwgE_oOJSCjgsMGTSMDV2-LsUzw1zW3-+N_VCtE14m26BA@mail.gmail.com> <CAPt1N1nLWrVqGpPh+h=Ano6PJyw2ZRaroiAMgG4RDKTFV7rkpA@mail.gmail.com>
Date: Tue, 12 Apr 2016 14:17:28 -0300
X-Google-Sender-Auth: eScI4ms-VB9GSC6ejPes_kG69ic
Message-ID: <CAMm+Lwi=9ghLfQb-RKLr4ZZCjiLmhgBervZ3svytAe-DEY2=7w@mail.gmail.com>
Subject: Re: Concerns about Singapore and other places
From: Phillip Hallam-Baker <phill@hallambaker.com>
To: Ted Lemon <mellon@fugue.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/-FilI7GBKp-uggONOZAJ1kihFGk>
Cc: John Levine <johnl@taugh.com>, IETF Discussion Mailing List <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: Tue, 12 Apr 2016 17:17:36 -0000

That is the parental filter, if you don't opt out, you get pestered by
continuous messages asking you if you want to like it was an O/S
upgrade.

The child porn filtering is separate and I suspect is using the type
of BGP and IP intercept techniques that are commonly used to shut down
a large range of Internet crimes in pretty much every jurisdiction,
the US included.



On Tue, Apr 12, 2016 at 1:52 PM, Ted Lemon <mellon@fugue.com> wrote:
> The UK filter is an "opt out" filter, and I assume that we (the IETF) opted
> out.   Even the "opt out" blocking is voluntary at present--an ISP is not
> required by law to have a filter, but in practice the big ones do.
>
> On Tue, Apr 12, 2016 at 12:24 PM, Phillip Hallam-Baker
> <phill@hallambaker.com> wrote:
>>
>> On Sun, Apr 10, 2016 at 3:19 PM, John Levine <johnl@taugh.com> wrote:
>> >>The IETF has a meeting network requirements document that specifies a
>> >>number of parameters which includes no blocking.
>> >
>> > In London in 2014, do you know whether we were behind the national
>> > child porn filters?
>> >
>> > R's,
>> > John
>>
>> I am not sure that they actually filter.
>>
>> I think it rather more likely that if you were to surf to
>> kiddieporn.com from the Hilton Metropole, that you would find Mr Plod
>> knocking on your hotel room door 15 minutes later. That being the
>> driving time from New Scotland Yard.
>>
>


From nobody Tue Apr 12 10:33:24 2016
Return-Path: <michael.cameron@ericsson.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 9C0CB12E320 for <ietf@ietfa.amsl.com>; Tue, 12 Apr 2016 10:33:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] 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 qcatj28uWp7y for <ietf@ietfa.amsl.com>; Tue, 12 Apr 2016 10:33:21 -0700 (PDT)
Received: from usplmg20.ericsson.net (usplmg20.ericsson.net [198.24.6.45]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1BFF312E2BC for <ietf@ietf.org>; Tue, 12 Apr 2016 10:33:20 -0700 (PDT)
X-AuditID: c618062d-f79886d000002334-cd-570d2adf6ec4
Received: from EUSAAHC004.ericsson.se (Unknown_Domain [147.117.188.84]) by usplmg20.ericsson.net (Symantec Mail Security) with SMTP id 78.7C.09012.FDA2D075; Tue, 12 Apr 2016 19:05:35 +0200 (CEST)
Received: from EUSAAMB101.ericsson.se ([147.117.188.118]) by EUSAAHC004.ericsson.se ([147.117.188.84]) with mapi id 14.03.0248.002; Tue, 12 Apr 2016 13:33:19 -0400
From: Michael Cameron <michael.cameron@ericsson.com>
To: John C Klensin <john-ietf@jck.com>, Alissa Cooper <alissa@cooperw.in>, Jari Arkko <jari.arkko@piuha.net>
Subject: RE: Last Call on draft-bradner-rfc3979bis-08.txt ("Intellectual Property Rights in IETF Technology")
Thread-Topic: Last Call on draft-bradner-rfc3979bis-08.txt ("Intellectual Property Rights in IETF Technology")
Thread-Index: AQHRlJ3D1yp4GVo8UU23NQm3qFlmo5+GjoZQ
Date: Tue, 12 Apr 2016 17:33:17 +0000
Message-ID: <36BAA6A693139D4BBCB37CCCA660E08A14FD99DA@eusaamb101.ericsson.se>
References: <65AD4D713F340D761513414F@JcK-HP8200.jck.com>
In-Reply-To: <65AD4D713F340D761513414F@JcK-HP8200.jck.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [147.117.188.10]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFupjkeLIzCtJLcpLzFFi42KZXLonRPe+Fm+4wdJL+hbTz/xltHi2cT6L xYx9K9gsWi/9YXNg8fjy5CWTx5IlP5k8Lq98zeyxdcl0tgCWKC6blNSczLLUIn27BK6MfSce shTMlqhY/n8rewPjQuEuRk4OCQETiYv7ZjNB2GISF+6tZ+ti5OIQEjjKKHHo0QZ2CGc5o8Tn OYeBMhwcbEAdz5+xgJgiAnkSH876gvQyC0hIXJ/wDmyOsEC+xP0bvawgtohAgcT5vwdZIGwj iY/L9zCC2CwCqhIffkLs5RXwlfi8/w4ziC0kYCnxcNldsHpOASuJN+2r2EBsRqDbvp9awwSx S1zi1pP5UDcLSCzZc54ZwhaVePn4HyuErSQxaek5Voh6HYkFuz+xQdjaEssWvmaG2CsocXLm E5YJjGKzkIydhaRlFpKWWUhaFjCyrGLkKC0uyMlNNzLYxAiMpWMSbLo7GO9P9zzEKMDBqMTD uyCMJ1yINbGsuDL3EKMEB7OSCO97Hd5wId6UxMqq1KL8+KLSnNTiQ4zSHCxK4ryNwf/ChATS E0tSs1NTC1KLYLJMHJxSDYzrG72/7rl59D9DkyBTy/SA6yzTTnAsmf+q3Kl2cZpi+VcJ7sa0 QjbB6i/PW0S9XzT7T/zLbN6Ws+XWouhvLKwTdE43VC2VZuIX8LwW/1YyVHxawHfePVkl6T8W 60zavsBQaCH3Nu7U/643Sr598I19tWDT+rf9ddzLTiksiHA8V+rs9+7Ax39KLMUZiYZazEXF iQB8SPT0oQIAAA==
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/N2mJM1tBA9kmipP0n2QHx6HC9nA>
Cc: IETF <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: Tue, 12 Apr 2016 17:33:22 -0000

John said:

As a random member of the community, whether I'm participating in a WG, or =
even actively monitoring it, is fairly clear.  If, for example, I'm attendi=
ng its meetings (f2f or remotely) or signed up for its mailing list, the co=
mmunity should be able to assume that I'm watching the work in that WG and =
should be required to make relevant IPR disclosures even if I don't actuall=
y say anything or otherwise generate Contributions.   =20

My response:

I appreciate that some are advocating for what they want the rules to be, b=
ut let's level set as to what they are.  Attending meetings, being signed u=
p for mailing lists or watching work in a WG does not obligate one to make =
any IPR disclosures.  That was discussed in detail at the last IETF meeting=
 when the IPR Group met (Orlando, IIRC). The IPR disclosure obligation aris=
es only with respect to known IPR reading on Contributions (for Contributor=
s) and for non-Contributors, the disclosure obligation only applies to know=
n IPR reading on a draft on which such non-Contributor actively seeks to in=
fluence the outcome of the disposition of a draft (active participation).

John said:

If you are the AD responsible for a WG, then I think the community gets to =
assume that you know what its work items are, have approved document editor=
s, and have at least read the abstracts of the various drafts, i.e., that y=
ou are participating.  If you are some other AD in the same area, well, are=
as differ a lot and over time.  In some cases, ADs shadow each other as a m=
utual backup arrangements and I'd expect to be able to treat all ADs in the=
 same area as "participating" in all WGs.  In others, WGs get divided up am=
ong ADs, after which the area might as well be as many separate ones as the=
re are ADs.  At IETF evaluation time, any ADs who record a position other t=
hat "abstain" on a spec, or to engage in any IESG discussion about it, has =
presumably studied that spec closely enough to incur disclosure obligations=
 if IPR is known to them because making a decision to adopt (or not) is cle=
arly "participation".  The same issue might exist with Co-chairs of a WG wi=
th many tasks.  I'd normally assume that each one is familiar with and part=
icipating in every work item, but it isn't hard to imagine situations in wh=
ich work might be split up along clear boundaries with one co-chair getting=
 involved in the work of the other only at around the time of Last Call if =
then.

My response:

We need to be careful not to place on Area Directors unreasonable burdens a=
nd obligations.  Further, there needs to be certainty as to what the obliga=
tions are.   The obligations imposed on Area Directors to declare known IPR=
 should be limited to those activities in which they actively participate. =
 I'll defer to the ADs, but I would think that an AD acting on a recommenda=
tion or advice from a WG as to how to proceed on a Specification, without m=
ore, does not necessarily rise to the level of active participation.

Best, Mike


From nobody Tue Apr 12 10:34:13 2016
Return-Path: <prvs=90323f149=theodore.v.faber@aero.org>
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 56AAA12D0E0 for <ietf@ietfa.amsl.com>; Tue, 12 Apr 2016 10:34:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.896
X-Spam-Level: 
X-Spam-Status: No, score=-2.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RP_MATCHES_RCVD=-0.996] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=neutral reason="invalid (public key: not available)" header.d=aero.org header.b=NmVbfYP+; dkim=pass (1024-bit key) header.d=aerospacecloud.onmicrosoft.com header.b=muVKEu3+
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 0jCuhHIx_wZb for <ietf@ietfa.amsl.com>; Tue, 12 Apr 2016 10:34:10 -0700 (PDT)
Received: from email3-east.aero.org (email3-east.aero.org [130.221.184.167]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8F10612D093 for <ietf@ietf.org>; Tue, 12 Apr 2016 10:34:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=aero.org; i=@aero.org; q=dns/txt; s=mailhub; t=1460482450; x=1492018450; h=from:to:cc:subject:date:message-id:references: content-transfer-encoding:mime-version; bh=G6P+CAU0KYvsWa8zYHTY8E2nqxwxF9O6bC1pvbb1g7Y=; b=NmVbfYP+tnD5frZx4hxjyhc6wtv9U8lRvbQcBJhRtxQr3KqAui7exYl9 NoSchI1WwRFWPOk19zD6vzt9n1ieksv2AcFlxHV/bSUx2bH6DTK0wOKuD S4JNnY9u5Ey4iiyaUFlfzy9J81LRlO4QEUkwwe86653hkfUeezNTLrKKt Q=;
x-SBRS: None
x-SenderGroup: Inbound_Office365
X-IronPort-AV: E=McAfee;i="5700,7163,8133"; a="2570965"
X-IronPort-AV: E=Sophos;i="5.24,475,1454994000";  d="scan'208";a="2570965"
X-IPAS-Result: A2HpAQCNLg1X/xPGZxdbAxkBAQEBg219BrpgAQ2BMhwmIYVsAoFsFAEBAQEBAQEDYieCNgE4PAEBAQEBAQEBAQEBAQEcAg0nBjEBAQEBAgESAScGAQE3AQ8CAQgYHhAyJQIEAQ0FCBqHcQMKCA6hMAGBJwEcYQUoAopohSgBBIgiGIUCAQEBAQEBAQMBAQEBAQEBARICBIpshD0CISaCZIIrmA2Fd5cmjyceAQFCgXcMGoFKbAGJBgF9AQEB
Received: from mail-cy1gcc01lp0019.outbound.protection.outlook.com (HELO gcc01-CY1-obe.outbound.protection.outlook.com) ([23.103.198.19]) by email3-east.aero.org with ESMTP/TLS/AES256-SHA; 12 Apr 2016 13:34:08 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aerospacecloud.onmicrosoft.com; s=selector1-aero-org; h=From:To:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=cw5/llBYvDaQD8n1GcTwlexwmS848jkDqR/wCBxzSYI=; b=muVKEu3+mUELr0f11op158uirDdzMAmqqKOwWAcLJ9Mg7PlP0TdnC+IdxuVYwqK9DBsVYAcMtlGEvzSMCImTmmh5qNO9c7ZOtlJaf2Aozuca2NAShkCnlRiRIpgnCE54IdKpQSy3Pgj8PAqhD0ApTbzaKYUkEGZiDaeJrphuQh8=
Received: from DM2PR09MB0336.namprd09.prod.outlook.com (10.160.247.153) by DM2PR09MB0336.namprd09.prod.outlook.com (10.160.247.153) with Microsoft SMTP Server (TLS) id 15.1.453.26; Tue, 12 Apr 2016 17:33:49 +0000
Received: from DM2PR09MB0336.namprd09.prod.outlook.com ([10.160.247.153]) by DM2PR09MB0336.namprd09.prod.outlook.com ([10.160.247.153]) with mapi id 15.01.0453.029; Tue, 12 Apr 2016 17:33:49 +0000
From: Theodore V Faber <theodore.v.faber@aero.org>
To: "Joel M. Halpern" <jmh@joelhalpern.com>, Ted Lemon <mellon@fugue.com>
Subject: Re: Remote only meetings? [Re: Concerns about Singapore]
Thread-Topic: Remote only meetings? [Re: Concerns about Singapore]
Thread-Index: AQHRlEYlZbpPBKyoakiM2ara2w8qgA==
Date: Tue, 12 Apr 2016 17:33:49 +0000
Message-ID: <DM2PR09MB033614EDE92B2458163F0FB4B9950@DM2PR09MB0336.namprd09.prod.outlook.com>
References: <570AB3AF.2050401@gmail.com> <87twj99c6w.fsf@tops.chopps.org> <CAKe6YvMyp-DyeDwpPY6KYmbDbnpgnvVk_cUStnA32wmgDWcz3w@mail.gmail.com> <BBF5DDFE515C3946BC18D733B20DAD233A62AA18@XMB122CNC.rim.net> <20160411104519.GA19092@gsp.org> <3F48466D-390C-4C18-B958-732AE3E46FF1@gmail.com> <20160411223403.GA6743@gsp.org> <87twj7eon7.fsf@tops.chopps.org> <20160412110839.GA20488@gsp.org> <8760vn82f2.fsf@tops.chopps.org> <20160412124639.GA27223@gsp.org> <87fuurgd8f.fsf@tops.chopps.org> <CABmDk8kCfTB_AKyqV4X+AghL2G7i+XcKR=tzV0jybM05k+UU4Q@mail.gmail.com> <570D175A.1040001@joelhalpern.com> <CAPt1N1n0_UJ5AVzO=dyvzeLtYi0b8g5894wyhctwPwqTzme-PQ@mail.gmail.com> <570D1F04.8050701@joelhalpern.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: joelhalpern.com; dkim=none (message not signed) header.d=none;joelhalpern.com; dmarc=none action=none header.from=aero.org;
x-originating-ip: [130.221.224.7]
x-ms-office365-filtering-correlation-id: 37af9f30-a752-4612-70db-08d362f89bc9
x-microsoft-exchange-diagnostics: 1; DM2PR09MB0336; 5:6FDWpXVfilcRTAVFzBgEUbgQtJ1xcxTdRn5V2npqoLeNtFRuJnTuU5xavSth+mEvIqhhAqOGDGJc62ZK1iEC1+/6mtdXZaVtkMWMZue/Wu4+/OMzT8RwxajUf8oGh4LIO4kdMD74HgCA2kq0FfRk1w==; 24:VbdUT+k81Iqkv33QMyF7r0zjpm0+wF6q0LURB8eCZb2vAG6NJsPeTTrTd8JLVYXmXnv4AX6MHDvqhclFuf5bIc55YvLEvbeWhWPU6s1QZb4=
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:DM2PR09MB0336;
x-microsoft-antispam-prvs: <DM2PR09MB03363106F35F245E3C522143B9950@DM2PR09MB0336.namprd09.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(601004)(2401047)(5005006)(8121501046)(10201501046)(3002001); SRVR:DM2PR09MB0336; BCL:0; PCL:0; RULEID:; SRVR:DM2PR09MB0336; 
x-forefront-prvs: 0910AAF391
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(6009001)(54524002)(24454002)(102836003)(3660700001)(6116002)(3846002)(1096002)(586003)(4326007)(1220700001)(77096005)(2900100001)(15975445007)(5004730100002)(10400500002)(11100500001)(9686002)(5003600100002)(5001770100001)(5002640100001)(92566002)(3280700002)(81166005)(575784001)(50986999)(2906002)(99286002)(76176999)(54356999)(189998001)(19580395003)(122556002)(66066001)(76576001)(33656002)(19580405001)(74316001)(5008740100001)(106116001)(87936001)(86362001)(93886004)(19627235001); DIR:OUT; SFP:1101; SCL:1; SRVR:DM2PR09MB0336; H:DM2PR09MB0336.namprd09.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en; 
spamdiagnosticoutput: 1:23
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: aero.org
X-MS-Exchange-CrossTenant-originalarrivaltime: 12 Apr 2016 17:33:49.2890 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: c8294700-c5a4-4ca1-a876-1457d39899fd
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM2PR09MB0336
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/_nNh-WkMwsG__RiRSUAE0VK3DqE>
Cc: Rich Kulawiec <rsk@gsp.org>, "<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: Tue, 12 Apr 2016 17:34:12 -0000

-----BEGIN PGP SIGNED MESSAGE-----=0A=
Hash: SHA512=0A=
=0A=
On 4/12/16 09:15, Joel M. Halpern wrote:=0A=
> Ted, you missed my point.  Yes, I can arrange a call with the=0A=
> relevant people.  And I frequently do. It is harder, but that would=0A=
> be acceptable.=0A=
> =0A=
> The important part is that such calls are MUCH less effective than=0A=
>  face-to-face discussions.  There are lots of well-known reasons=0A=
> for this.=0A=
> =0A=
> And no, inc ase it was not obvious, without the face-to-face=0A=
> meeting, there is no way to arrange such face-to-face meetings.=0A=
=0A=
If the goal of the IETF is to replicate the experience of an IETF=0A=
meeting using telepresence tools, that is an impossible task.=0A=
Telepresence is not being present.=0A=
=0A=
To my mind, the question is if a large scale use of telepresence tools=0A=
can create a working environment that the IETF membership can use to=0A=
advance the IETF's goals.  I'm curious enough about that question to=0A=
support an assessment of how expensive and difficult it would be to=0A=
replace one IETF meeting with a large scale telepresence experiment.=0A=
=0A=
I think we should evaluate that experiment (should it occur) based on=0A=
whether or not the broader goals advance (standards and documents=0A=
advance, new ideas are sparked, the membership is appropriately=0A=
updated), not how they are advanced (discussions at the Scotch BOF,=0A=
plenary and BA, speaking at the mic in WG meetings).=0A=
=0A=
I seems to me that a successful experiment would mean that we use more=0A=
large scale telepresence.  It may someday turn out that such events=0A=
replace some IETF meetings; it may not.  I don't know of any=0A=
organizations of the scale of the IETF that have historically relied=0A=
on face to face meetings and transitioned solely to large scale=0A=
telepresence, so my expectation is that IETF meetings will continue.=0A=
=0A=
(Just to forestall the question: Anonymous seems to run entirely on=0A=
large scale telepresence (for some definition thereof).  It's got a=0A=
whole set of procedures and traditions that enable that.  It's a=0A=
fascinating situation, but I see little inspiration or intuition for=0A=
changing IETF procedures from it.)=0A=
=0A=
> =0A=
> Yes, we should work to make remote participation more effective.=0A=
> Doing away with the face-to-face meetings reminds me of the old SF=0A=
> story of the ballet dancers who were forced to dance wearing extra=0A=
> weights, to be "fair" to the less talented dancers.=0A=
=0A=
Paging Harrison Bergeron.=0A=
https://en.wikipedia.org/wiki/Harrison_Bergeron=0A=
=0A=
- -- =0A=
Ted Faber <theodore.v.faber@aero.org>=0A=
Engineering Specialist=0A=
Computer Systems Research Department=0A=
310-336-7373=0A=
-----BEGIN PGP SIGNATURE-----=0A=
Comment: GPGTools - https://gpgtools.org=0A=
=0A=
iQIcBAEBCgAGBQJXDTF7AAoJEFNjQnOBW8uOXRMP/1ynBlK7upPubIGAzvdqjLMx=0A=
dBxvS+8sJKbFBGSf2upkexjBYiDHMXnCGkNXi+rMbb70eq9h62jD1SjEMXt58TH5=0A=
I93M07KDzWk0AhBXZmrZ5aj/K6BrtdGl/+BnKkmudn5mgqSg/Yho9QPALG/9KBuk=0A=
1nl3k0zAl43GEIqV+2Aaff2Us5Lcl2U03PJNRp2XMMjm+btJ/mXYW6SRNUdlYsaL=0A=
+lIGAaQZ3D54LPrfyoMAQCLnA7/gAjU/KtM2lUxM3l6YJvYkcU1enBG/qFnbac1g=0A=
IZp4OTuhOmlcEppmMj5auFzROZz0mjmXH8tecxwl01vd3lIDqeqJbbqQEyySVTqD=0A=
7w8tYliHbYzjrMwezQ9XQdkal1uly6vzP9/CWtK1OiBsr+dKJKRm1j78zOEEcLxl=0A=
KimzbZLrvFfAWPwwKIpMf55Mc535bLviIsVPwmFGBbE0U7xs3d0OSK81BYUH57MZ=0A=
QuBHQxjamYRH8qCU4d+AH78yVTu89IIM/Ilu6HN956QPa5Na+QU6o02t/yyO2iiF=0A=
RBv8uJymDsvjoy5LoYHcQ7L3XO5LNwXin0lUtIY9KZ3mzqIJnBlGUVoh+whce9Al=0A=
Fx+GM4MZPKmRmSlYyhwPG33M357UVUMxKCdS/lGiwR6sQUxMzSuxfDQ/aYpqG1Fj=0A=
5WR1cl4yU64RK/qaIl5r=0A=
=3D7cfg=0A=
-----END PGP SIGNATURE-----=0A=


From nobody Tue Apr 12 10:42:09 2016
Return-Path: <mfidelman@meetinghouse.net>
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 D791512D7B2 for <ietf@ietfa.amsl.com>; Tue, 12 Apr 2016 10:42:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] 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 B_IJSOYsWa1t for <ietf@ietfa.amsl.com>; Tue, 12 Apr 2016 10:42:06 -0700 (PDT)
Received: from server1.neighborhoods.net (server1.neighborhoods.net [207.154.13.48]) by ietfa.amsl.com (Postfix) with ESMTP id 99FBB12B041 for <ietf@ietf.org>; Tue, 12 Apr 2016 10:42:06 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by server1.neighborhoods.net (Postfix) with ESMTP id C23994C8007 for <ietf@ietf.org>; Tue, 12 Apr 2016 13:42:05 -0400 (EDT)
X-Virus-Scanned: by amavisd-new-2.6.2 (20081215) (Debian) at neighborhoods.net
Received: from server1.neighborhoods.net ([127.0.0.1]) by localhost (server1.neighborhoods.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id FlPpecnIbsQf for <ietf@ietf.org>; Tue, 12 Apr 2016 13:42:00 -0400 (EDT)
Received: from Miless-MBP.fios-router.home (pool-108-26-191-201.bstnma.fios.verizon.net [108.26.191.201]) by server1.neighborhoods.net (Postfix) with ESMTPSA id 56C9F4C8006 for <ietf@ietf.org>; Tue, 12 Apr 2016 13:42:00 -0400 (EDT)
Subject: Re: Remote only meetings? [Re: Concerns about Singapore]
To: ietf@ietf.org
References: <570AB3AF.2050401@gmail.com> <87twj99c6w.fsf@tops.chopps.org> <CAKe6YvMyp-DyeDwpPY6KYmbDbnpgnvVk_cUStnA32wmgDWcz3w@mail.gmail.com> <BBF5DDFE515C3946BC18D733B20DAD233A62AA18@XMB122CNC.rim.net> <20160411104519.GA19092@gsp.org> <3F48466D-390C-4C18-B958-732AE3E46FF1@gmail.com> <20160411223403.GA6743@gsp.org> <87twj7eon7.fsf@tops.chopps.org> <20160412110839.GA20488@gsp.org> <8760vn82f2.fsf@tops.chopps.org> <20160412124639.GA27223@gsp.org> <87fuurgd8f.fsf@tops.chopps.org> <CABmDk8kCfTB_AKyqV4X+AghL2G7i+XcKR=tzV0jybM05k+UU4Q@mail.gmail.com> <570D175A.1040001@joelhalpern.com> <CAPt1N1n0_UJ5AVzO=dyvzeLtYi0b8g5894wyhctwPwqTzme-PQ@mail.gmail.com> <570D1F04.8050701@joelhalpern.com> <DM2PR09MB033614EDE92B2458163F0FB4B9950@DM2PR09MB0336.namprd09.prod.outlook.com>
From: Miles Fidelman <mfidelman@meetinghouse.net>
Message-ID: <570D3367.4040705@meetinghouse.net>
Date: Tue, 12 Apr 2016 13:41:59 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:38.0) Gecko/20100101 Thunderbird/38.7.2
MIME-Version: 1.0
In-Reply-To: <DM2PR09MB033614EDE92B2458163F0FB4B9950@DM2PR09MB0336.namprd09.prod.outlook.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/cQVMxJQG3XANqV-X6LDmqAV3MIU>
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: Tue, 12 Apr 2016 17:42:07 -0000

On 4/12/16 1:33 PM, Theodore V Faber wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA512
>
> On 4/12/16 09:15, Joel M. Halpern wrote:
>> Ted, you missed my point.  Yes, I can arrange a call with the
>> relevant people.  And I frequently do. It is harder, but that would
>> be acceptable.
>>
>> The important part is that such calls are MUCH less effective than
>>   face-to-face discussions.  There are lots of well-known reasons
>> for this.
>>
>> And no, inc ase it was not obvious, without the face-to-face
>> meeting, there is no way to arrange such face-to-face meetings.
> If the goal of the IETF is to replicate the experience of an IETF
> meeting using telepresence tools, that is an impossible task.
> Telepresence is not being present.
>
> To my mind, the question is if a large scale use of telepresence tools
> can create a working environment that the IETF membership can use to
> advance the IETF's goals.  I'm curious enough about that question to
> support an assessment of how expensive and difficult it would be to
> replace one IETF meeting with a large scale telepresence experiment.
>
> I think we should evaluate that experiment (should it occur) based on
> whether or not the broader goals advance (standards and documents
> advance, new ideas are sparked, the membership is appropriately
> updated), not how they are advanced (discussions at the Scotch BOF,
> plenary and BA, speaking at the mic in WG meetings).
>
> I seems to me that a successful experiment would mean that we use more
> large scale telepresence.  It may someday turn out that such events
> replace some IETF meetings; it may not.  I don't know of any
> organizations of the scale of the IETF that have historically relied
> on face to face meetings and transitioned solely to large scale
> telepresence, so my expectation is that IETF meetings will continue.
>
> (Just to forestall the question: Anonymous seems to run entirely on
> large scale telepresence (for some definition thereof).  It's got a
> whole set of procedures and traditions that enable that.  It's a
> fascinating situation, but I see little inspiration or intuition for
> changing IETF procedures from it.)
>

I would think that a major open source project might be more of an 
example - perhaps Debian?

-- 
In theory, there is no difference between theory and practice.
In practice, there is.  .... Yogi Berra


From nobody Tue Apr 12 10:58:20 2016
Return-Path: <prvs=90323f149=theodore.v.faber@aero.org>
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 2603712DFD9 for <ietf@ietfa.amsl.com>; Tue, 12 Apr 2016 10:58:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.896
X-Spam-Level: 
X-Spam-Status: No, score=-2.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RP_MATCHES_RCVD=-0.996] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=neutral reason="invalid (public key: not available)" header.d=aero.org header.b=SO1PFn+M; dkim=pass (1024-bit key) header.d=aerospacecloud.onmicrosoft.com header.b=Gq8jTo8J
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 sLyVX_Tnnd-x for <ietf@ietfa.amsl.com>; Tue, 12 Apr 2016 10:58:17 -0700 (PDT)
Received: from email5-west.aero.org (email5-west.aero.org [130.221.16.30]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 902A312DEDD for <ietf@ietf.org>; Tue, 12 Apr 2016 10:58:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=aero.org; i=@aero.org; q=dns/txt; s=mailhub; t=1460483897; x=1492019897; h=from:to:subject:date:message-id:references: content-transfer-encoding:mime-version; bh=OWuPd0UXg+jWph94uDkJUPZj7hgFkN5BxVsodSLBmpc=; b=SO1PFn+MFtWoQQ0j1egSs3xQ63N+8MkJDuN+BNjsgWHcqTwh8HZ6QtFx egSGGBvnWWlTuFNWDxEjuNTbmkTNrtCQZYkLpvDRZwez3sM0nn2b3awXx QZNKSFCVgxebxiJo3lvZrjGoVcJyE173RClsnd7IlT5y94KeKkae0iRKw U=;
x-SBRS: 4.7
x-SenderGroup: Inbound_Office365
X-IronPort-AV: E=McAfee;i="5700,7163,8133"; a="3140475"
X-IronPort-AV: E=Sophos;i="5.24,475,1455004800";  d="scan'208";a="3140475"
X-IPAS-Result: A2HAAAAuNg1Xkw/GZxdbAxkBAQEBg219BrpgAQ2BdBmFdAKBbRQBAQEBAQEBAw8BAQEBBw0JCSEvgjc4PAEBAQEBASMCDSc4AQEBAxIBJwYBASYSDwIBCA4KHhAyJQIEARIIGodxAxKhPQGBJwEcYQUoAopohSgBBIgeGIUCAQEBBwEBAQEBFQIEimyEPQIhJoJkgiuYDYV3lyaPJx4BAYI5DBIIgUpsAYkGAX0BAQE
Received: from mail-cy1gcc01lp0015.outbound.protection.outlook.com (HELO gcc01-CY1-obe.outbound.protection.outlook.com) ([23.103.198.15]) by email5-west.aero.org with ESMTP/TLS/AES256-SHA; 12 Apr 2016 10:58:16 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aerospacecloud.onmicrosoft.com; s=selector1-aero-org; h=From:To:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=dLnkZdr9OHy/5eES7DE2sBRkxD2arULOwTjiYO1hlR4=; b=Gq8jTo8JqYhIYPGKy9Y9T4mpLe0gd2T3mUTSYBmWpcKMirpUzliyvIJsdMIvlsrcy8NqMRWd3n2NLnznkjQHB9LERFARaEWT4klKwbx+nuavdqTAyouFJaXAUyeiv/VkHpOwA8cjLUZaVV+ay+aIaqD6dM+rre8F4rD/C+Ew4Nw=
Received: from DM2PR09MB0336.namprd09.prod.outlook.com (10.160.247.153) by DM2PR09MB0334.namprd09.prod.outlook.com (10.160.247.151) with Microsoft SMTP Server (TLS) id 15.1.453.26; Tue, 12 Apr 2016 17:58:15 +0000
Received: from DM2PR09MB0336.namprd09.prod.outlook.com ([10.160.247.153]) by DM2PR09MB0336.namprd09.prod.outlook.com ([10.160.247.153]) with mapi id 15.01.0453.029; Tue, 12 Apr 2016 17:58:15 +0000
From: Theodore V Faber <theodore.v.faber@aero.org>
To: Miles Fidelman <mfidelman@meetinghouse.net>, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: Remote only meetings? [Re: Concerns about Singapore]
Thread-Topic: Remote only meetings? [Re: Concerns about Singapore]
Thread-Index: AQHRlEYlZbpPBKyoakiM2ara2w8qgA==
Date: Tue, 12 Apr 2016 17:58:15 +0000
Message-ID: <DM2PR09MB0336C2EA99FE55BC43EA3811B9950@DM2PR09MB0336.namprd09.prod.outlook.com>
References: <570AB3AF.2050401@gmail.com> <87twj99c6w.fsf@tops.chopps.org> <CAKe6YvMyp-DyeDwpPY6KYmbDbnpgnvVk_cUStnA32wmgDWcz3w@mail.gmail.com> <BBF5DDFE515C3946BC18D733B20DAD233A62AA18@XMB122CNC.rim.net> <20160411104519.GA19092@gsp.org> <3F48466D-390C-4C18-B958-732AE3E46FF1@gmail.com> <20160411223403.GA6743@gsp.org> <87twj7eon7.fsf@tops.chopps.org> <20160412110839.GA20488@gsp.org> <8760vn82f2.fsf@tops.chopps.org> <20160412124639.GA27223@gsp.org> <87fuurgd8f.fsf@tops.chopps.org> <CABmDk8kCfTB_AKyqV4X+AghL2G7i+XcKR=tzV0jybM05k+UU4Q@mail.gmail.com> <570D175A.1040001@joelhalpern.com> <CAPt1N1n0_UJ5AVzO=dyvzeLtYi0b8g5894wyhctwPwqTzme-PQ@mail.gmail.com> <570D1F04.8050701@joelhalpern.com> <DM2PR09MB033614EDE92B2458163F0FB4B9950@DM2PR09MB0336.namprd09.prod.outlook.com> <570D3367.4040705@meetinghouse.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: meetinghouse.net; dkim=none (message not signed) header.d=none;meetinghouse.net; dmarc=none action=none header.from=aero.org;
x-originating-ip: [130.221.224.7]
x-ms-office365-filtering-correlation-id: 37465deb-9455-4458-07cb-08d362fc05ca
x-microsoft-exchange-diagnostics: 1; DM2PR09MB0334; 5:vXbMvo7s0KkzVUgHSzH53+ikpZ/XBfW+48U195ELl78C6SF5cG/yfTwUs2Q91D16/Xn52E6OxmoxL6SFGbeiPeHfnBnZ+OEoKvB79NYz4nk9Fe0LhgbuBZvz9EQpbLqhVh8adzXVKj2/OlOZuT8DzA==; 24:iSU0VyxOhFJRlKL0k+eSK1b+if9LSz70L59c7BEtg9ZiRWP2on0dO1evqAxWhajs/CGijfh5Y4upLi/G+q54GR1uM5pG45UP/pAmq4aWRYs=
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:DM2PR09MB0334;
x-microsoft-antispam-prvs: <DM2PR09MB033479AA9705E294185A2010B9950@DM2PR09MB0334.namprd09.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(601004)(2401047)(5005006)(8121501046)(10201501046)(3002001); SRVR:DM2PR09MB0334; BCL:0; PCL:0; RULEID:; SRVR:DM2PR09MB0334; 
x-forefront-prvs: 0910AAF391
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(6009001)(54524002)(377454003)(24454002)(575784001)(5003600100002)(5001770100001)(122556002)(77096005)(15975445007)(5002640100001)(107886002)(86362001)(2900100001)(1220700001)(102836003)(3846002)(5008740100001)(19580405001)(1096002)(189998001)(6116002)(586003)(19580395003)(76576001)(5004730100002)(54356999)(76176999)(11100500001)(92566002)(106116001)(81166005)(87936001)(74316001)(2906002)(93886004)(9686002)(3280700002)(3660700001)(33656002)(66066001)(2501003)(99286002)(50986999)(10400500002)(19627235001); DIR:OUT; SFP:1101; SCL:1; SRVR:DM2PR09MB0334; H:DM2PR09MB0336.namprd09.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en; 
spamdiagnosticoutput: 1:23
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: aero.org
X-MS-Exchange-CrossTenant-originalarrivaltime: 12 Apr 2016 17:58:15.6528 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: c8294700-c5a4-4ca1-a876-1457d39899fd
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM2PR09MB0334
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/RrGSauMRzXioSB2uLiYnz_5q73w>
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: Tue, 12 Apr 2016 17:58:19 -0000

-----BEGIN PGP SIGNED MESSAGE-----=0A=
Hash: SHA512=0A=
=0A=
On 4/12/16 10:42, Miles Fidelman wrote:=0A=
> On 4/12/16 1:33 PM, Theodore V Faber wrote:=0A=
>> (Just to forestall the question: Anonymous seems to run entirely=0A=
>> on large scale telepresence (for some definition thereof).  It's=0A=
>> got a whole set of procedures and traditions that enable that.=0A=
>> It's a fascinating situation, but I see little inspiration or=0A=
>> intuition for changing IETF procedures from it.)=0A=
>> =0A=
> =0A=
> I would think that a major open source project might be more of an=0A=
>  example - perhaps Debian?=0A=
> =0A=
=0A=
I don't want to get too far down this particular rathole, but in my=0A=
experience a lot of those organizations do have a significant=0A=
component of their interactions at conventions/conferences.  (Not in=0A=
the sense that total time is spent there, but that key interactions=0A=
occur there.) Most organizations (probably even Anonymous) sit=0A=
somewhere on a spectrum between face-to-face and online interactions.=0A=
 I'd rather not build a taxonomy, though.=0A=
=0A=
- -- =0A=
Ted Faber <theodore.v.faber@aero.org>=0A=
Engineering Specialist=0A=
Computer Systems Research Department=0A=
310-336-7373=0A=
-----BEGIN PGP SIGNATURE-----=0A=
Comment: GPGTools - https://gpgtools.org=0A=
=0A=
iQIcBAEBCgAGBQJXDTc2AAoJEFNjQnOBW8uO5IoP/36zrF3r0p345NqjWfm5rEcO=0A=
sA0WSgS8QO5Phohu+UV7oXI/LC7NkNHpqO0yHmBKsTGez/q7+iVYeC3BtsSY5zwW=0A=
KXDWZ5eJQZD8QEYU78f719+L74U1YG5XEsHMb39tGyuMTxayaYb19P67L52pZDgT=0A=
aIbCaXkdD2m8CBe5Oj01Vcpec9lkF2qQgbRaVxuf6/MVIULyHSylnjz9riS1IuWC=0A=
CMRXTfxmC7MfxbQQC9D4R0hAAmWjwyYSQMDeTvCAKXxaOMpHi+PNdbKDW9BizZFz=0A=
lSliFbfG5q4dEFfgypzOAMIBCKH0Jo6hMaHt7mp70QB5pyP/UMrCT0g79LvqAfuU=0A=
UZdmW64i+0+Rch+vw1IYbbHyxma8EiAuXJ44XcLQEAQ1086IsTU2y77R5XtMQUEl=0A=
vsbsPluHLfZzfnD/CU17VEXXlIS9uxS4J11dJ6Skdphel0TJUZgEZwW6eejWVL+4=0A=
ofsUHMifVWek058opSNmp4PGUXNLrG6CeqnkXPMXv5vTnkdu+xqNgvjWw2YwGFMN=0A=
VZjR9H6S81LbPk/JgFausCYNa+8I0TGBuWXI7Aa01BRoZuPhhiXUdEc5kZ5bnfro=0A=
40bxtTmcBHo8iE4ciWNIix6x2SMtP4oQiGaWIAoqajJDROTtYg/fE/itrTd/ipP6=0A=
vKX/FmNm0yNHHUVHQGVf=0A=
=3Dq+9F=0A=
-----END PGP SIGNATURE-----=0A=


From nobody Tue Apr 12 10:58:51 2016
Return-Path: <melinda.shore@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 6FEC212E08D for <ietf@ietfa.amsl.com>; Tue, 12 Apr 2016 10:58:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 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, SPF_PASS=-0.001] autolearn=unavailable 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 L5YpgGgq0Q4F for <ietf@ietfa.amsl.com>; Tue, 12 Apr 2016 10:58:49 -0700 (PDT)
Received: from mail-pf0-x229.google.com (mail-pf0-x229.google.com [IPv6:2607:f8b0:400e:c00::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 6546412D706 for <ietf@ietf.org>; Tue, 12 Apr 2016 10:50:45 -0700 (PDT)
Received: by mail-pf0-x229.google.com with SMTP id c20so17749797pfc.1 for <ietf@ietf.org>; Tue, 12 Apr 2016 10:50:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding; bh=VzNUf7MmO3tvl8AGDF1nHOUE9Di2PzygZg2yq97xY/4=; b=0GicP4ZTwpW51CWudb/N2xWMvYoD964T5H4DIssQtwm7xUCsOklfusNIE+lgfgMya0 nbnaQaB1jVlLAqDKx1CaGS6vxdrIRtM2zD6lA3aW/VBFeFlI3TJSNCAMqkzDzWGNtZQ9 ZqU4qbKd3NonsOxKXLH4o+bV4CaDUwX03kcSdA//8vwFBrvobWA217+/vJt1n3sZkThq /x2GSYGN7avM8+WLqmJxSDj9WRsXMqzBmF2jkPRc9S1ewlZRgdLriGsLaCs8DHgiNEBR xrA+/C7oZ0ULgR5TmIHmhgHK8JFNsDjagQcf0c1dCdDcbjowUAPw9MHht5zwd5DjHWKM VYCQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=VzNUf7MmO3tvl8AGDF1nHOUE9Di2PzygZg2yq97xY/4=; b=NLoO7ELAaBuNkYx5TI4rgLmCMUbH1tDMZTei83ZKauE/7lAwkPx3Xz9FWX/DLspljv 8OBi2K9ND+hr81UoYwbjm5U8IPzzsW/vJJrdzKCuW5iN73mzDgm1XzVBX8+MtybAok9b N5Vv8UFUlV1xwwIw1EeBTvuWFAakR0WIb6Xeq5BvzDU9So+eFLBHFw/OlFvLRn6RucLF DHGqU5TsRyydw/BKkbp9llwvB+uMv4v1f0AshJrItnl0lej3Kr4bH4AVxuH6fZypgrIQ GyBQF/bl3gj7iiPb2K5U6G9AjOgtuMUcOLoF6TjFzflVq03eD45YayBQ1VEQxTSptVfc e0fA==
X-Gm-Message-State: AOPr4FWHl1yWqjuZetktDYhE4DBt8tw7QqJxHiHJH4eIewkkqqezDgKFILPyGU3WNCI1zA==
X-Received: by 10.98.44.70 with SMTP id s67mr6398524pfs.59.1460483444982; Tue, 12 Apr 2016 10:50:44 -0700 (PDT)
Received: from Melindas-MacBook-Pro.local (216-67-8-215-radius.dynamic.acsalaska.net. [216.67.8.215]) by smtp.googlemail.com with ESMTPSA id p85sm45157069pfj.16.2016.04.12.10.50.43 for <ietf@ietf.org> (version=TLSv1/SSLv3 cipher=OTHER); Tue, 12 Apr 2016 10:50:44 -0700 (PDT)
Subject: Re: Remote only meetings? [Re: Concerns about Singapore]
To: ietf@ietf.org
References: <570AB3AF.2050401@gmail.com> <87twj99c6w.fsf@tops.chopps.org> <CAKe6YvMyp-DyeDwpPY6KYmbDbnpgnvVk_cUStnA32wmgDWcz3w@mail.gmail.com> <BBF5DDFE515C3946BC18D733B20DAD233A62AA18@XMB122CNC.rim.net> <20160411104519.GA19092@gsp.org> <3F48466D-390C-4C18-B958-732AE3E46FF1@gmail.com> <20160411223403.GA6743@gsp.org> <87twj7eon7.fsf@tops.chopps.org> <20160412110839.GA20488@gsp.org> <8760vn82f2.fsf@tops.chopps.org> <20160412124639.GA27223@gsp.org> <87fuurgd8f.fsf@tops.chopps.org> <CABmDk8kCfTB_AKyqV4X+AghL2G7i+XcKR=tzV0jybM05k+UU4Q@mail.gmail.com> <570D175A.1040001@joelhalpern.com> <CAPt1N1n0_UJ5AVzO=dyvzeLtYi0b8g5894wyhctwPwqTzme-PQ@mail.gmail.com> <570D1F04.8050701@joelhalpern.com> <DM2PR09MB033614EDE92B2458163F0FB4B9950@DM2PR09MB0336.namprd09.prod.outlook.com> <570D3367.4040705@meetinghouse.net>
From: Melinda Shore <melinda.shore@gmail.com>
Message-ID: <570D3587.4020903@gmail.com>
Date: Tue, 12 Apr 2016 09:51:03 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:38.0) Gecko/20100101 Thunderbird/38.6.0
MIME-Version: 1.0
In-Reply-To: <570D3367.4040705@meetinghouse.net>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/pw2W_8unzcBfJsja0s-4NvXj2TA>
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: Tue, 12 Apr 2016 17:58:50 -0000

On 4/12/16 9:41 AM, Miles Fidelman wrote:
> I would think that a major open source project might be more of an
> example - perhaps Debian?

A standards body example would be the W3C, which meets 1x/year,
but whose working groups have frequent teleconferences.

Melinda



From nobody Tue Apr 12 11:01:22 2016
Return-Path: <chopps@chopps.org>
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 11C6A12E06F for <ietf@ietfa.amsl.com>; Tue, 12 Apr 2016 11:01:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.896
X-Spam-Level: 
X-Spam-Status: No, score=-2.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.996] 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 3YXqsin5rreH for <ietf@ietfa.amsl.com>; Tue, 12 Apr 2016 11:01:19 -0700 (PDT)
Received: from smtp.chopps.org (smtp.chopps.org [54.88.81.56]) by ietfa.amsl.com (Postfix) with ESMTP id 897B612E0BC for <ietf@ietf.org>; Tue, 12 Apr 2016 11:01:18 -0700 (PDT)
Received: from tops.chopps.org (24-247-68-31.dhcp.trcy.mi.charter.com [24.247.68.31]) (using TLSv1.2 with cipher AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by smtp.chopps.org (Postfix) with ESMTPSA id 081CB60D09; Tue, 12 Apr 2016 18:01:17 +0000 (UTC)
References: <m21t6d7c9t.wl%randy@psg.com> <570A67B4.3010206@comcast.net> <570AB3AF.2050401@gmail.com> <87twj99c6w.fsf@tops.chopps.org> <CAKe6YvMyp-DyeDwpPY6KYmbDbnpgnvVk_cUStnA32wmgDWcz3w@mail.gmail.com> <BBF5DDFE515C3946BC18D733B20DAD233A62AA18@XMB122CNC.rim.net> <20160411104519.GA19092@gsp.org> <3F48466D-390C-4C18-B958-732AE3E46FF1@gmail.com> <20160411223403.GA6743@gsp.org> <87twj7eon7.fsf@tops.chopps.org> <20160412110839.GA20488@gsp.org> <8760vn82f2.fsf@tops.chopps.org> <570D2A34.1030700@gmail.com>
User-agent: mu4e 0.9.16; emacs 24.5.1
From: <chopps@chopps.org>
To: Melinda Shore <melinda.shore@gmail.com>
Subject: Re: Remote only meetings? [Re: Concerns about Singapore]
In-reply-to: <570D2A34.1030700@gmail.com>
Date: Tue, 12 Apr 2016 14:01:16 -0400
Message-ID: <87bn5ehfkj.fsf@tops.chopps.org>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature"
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/m2FLuJtVAHdA-Fk3H2Yp338mR0Y>
Cc: 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: Tue, 12 Apr 2016 18:01:21 -0000

--=-=-=
Content-Type: text/plain


Melinda Shore <melinda.shore@gmail.com> writes:

> On 4/12/16 3:57 AM, chopps@chopps.org wrote:
>> Rich Kulawiec <rsk@gsp.org> writes:
>>> Because it works exclusively for the elite, privileged few.  (And no
>>> doubt: it works quite well.)  But it's the antithesis of inclusion
>>> and diversity -- and I think those qualities are increasingly necessary.
>>
>> But this is not how the IETF operates.
>
> Actually, it's very much how the IETF operates in practice,
> particularly with meeting participation becoming increasingly
> expensive and with increased participation from "standards
> professionals."  If you've been to meetings you'll have
> noticed some chairs taking votes in meetings (rather than
> relying on consensus processes) and saying that they'll
> ratify or confirm that decision on the mailing list (if
> they remember - sometimes they don't).

I know for a fact it is not how I and my co-chair run the IS-IS WG. I
can't speak to whether other WGs are being run incorrectly. It's the
responsibility of the participants and the ADs to make sure the
chairs are not violating our own standards process though.

Thanks,
Chris.

--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQIcBAEBCgAGBQJXDTfsAAoJEC4dgw7XuDAlI1sP/RKZPZNnWTv5pI66EF14at3l
+l78WX86mOy4tVFmFwuZC1F51xp/iF6PdmgqoPNweqfKiifCAMP+jKK9T//6OBLg
YQRNwlXOwlgTxjuiqu7Qg4SFxBPK+erGpleqjijnmkmA3p7GueIbG3/dxJ9kbWAu
laJzX7iRoD9S+fx/6XH9VT9LTc9SDWcEPz890MrlKJkmCH/kZ5BRHGiKd6PG8VfB
gJ2gtRSpBV47sKI2g4n3zoZeFt5uWniL9CliipzS9abgl5VLAkcZjxyQANyfwQyk
k2YtsOGSAUxgN77ITfzjB2K3kFz7BVKYAZ35a7exII5k6KTgtiPO8ogWY6PjRBQl
La2X1LWrj4zgi81cGm5jlFLqpnmfjuVboiwdNk18Bki4z0KaZB0ZWrBX0plRHrYw
xgyj5d3YVzPcg3T1y1GOu1L3ol96G41AhUxiyXARwfo2VXA0+9qgkw8tBrEbb6IG
66dLAhrMiA8JqWOz8E7mgHn6Zg1sco9EM3yQbiphPvVqbM/kU9SAzT8Aa9yoH48M
N2ukG2FgC2XHlgOoV2YGP2B2SWIi5sXyDAiEzFCwQu89CcBwg8wO7J15BrgjnITr
2B8AaQ46nAuUPD5x9rp3OdVg6CsfiUrP8lbUdzqoqdFAyn/PMXOsnQCGD4MPkVlF
jDcWujJWvoMKazB7lQCn
=k4Az
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Tue Apr 12 11:07:33 2016
Return-Path: <chopps@chopps.org>
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 EDB8912E5D8 for <ietf@ietfa.amsl.com>; Tue, 12 Apr 2016 11:07:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.896
X-Spam-Level: 
X-Spam-Status: No, score=-2.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.996] 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 1ak0jlUffN23 for <ietf@ietfa.amsl.com>; Tue, 12 Apr 2016 11:07:29 -0700 (PDT)
Received: from smtp.chopps.org (smtp.chopps.org [54.88.81.56]) by ietfa.amsl.com (Postfix) with ESMTP id 7796D12E596 for <ietf@ietf.org>; Tue, 12 Apr 2016 11:07:28 -0700 (PDT)
Received: from tops.chopps.org (24-247-68-31.dhcp.trcy.mi.charter.com [24.247.68.31]) (using TLSv1.2 with cipher AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by smtp.chopps.org (Postfix) with ESMTPSA id C04E661166; Tue, 12 Apr 2016 18:07:27 +0000 (UTC)
References: <570AB3AF.2050401@gmail.com> <87twj99c6w.fsf@tops.chopps.org> <CAKe6YvMyp-DyeDwpPY6KYmbDbnpgnvVk_cUStnA32wmgDWcz3w@mail.gmail.com> <BBF5DDFE515C3946BC18D733B20DAD233A62AA18@XMB122CNC.rim.net> <20160411104519.GA19092@gsp.org> <3F48466D-390C-4C18-B958-732AE3E46FF1@gmail.com> <20160411223403.GA6743@gsp.org> <87twj7eon7.fsf@tops.chopps.org> <20160412110839.GA20488@gsp.org> <8760vn82f2.fsf@tops.chopps.org> <20160412124639.GA27223@gsp.org> <87fuurgd8f.fsf@tops.chopps.org> <CABmDk8kCfTB_AKyqV4X+AghL2G7i+XcKR=tzV0jybM05k+UU4Q@mail.gmail.com> <65989154-BD08-45F0-B6F0-2AE3E435409C@chopps.org> <570D2BAD.7000307@gmail.com>
User-agent: mu4e 0.9.16; emacs 24.5.1
From: <chopps@chopps.org>
To: Melinda Shore <melinda.shore@gmail.com>
Subject: Re: Remote only meetings? [Re: Concerns about Singapore]
In-reply-to: <570D2BAD.7000307@gmail.com>
Date: Tue, 12 Apr 2016 14:07:26 -0400
Message-ID: <87a8kyhfa9.fsf@tops.chopps.org>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature"
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/zH5AXByREeVvPG5tYKExvHKcjcw>
Cc: 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: Tue, 12 Apr 2016 18:07:31 -0000

--=-=-=
Content-Type: text/plain


Melinda Shore <melinda.shore@gmail.com> writes:

> On 4/12/16 6:20 AM, Christian Hopps wrote:
>> I think we need to look at a good sampling of the data at this point.
>
> Have at it.

I would like to actually. :) I'm wondering how I might go about getting
all the email From addresses from every WG archive for the last year.
I'm thinking if all archives are now hosted by mailman there's probably
a way to script this.

Thanks,
Chris.

>
> Melinda


--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQIcBAEBCgAGBQJXDTleAAoJEC4dgw7XuDAlVSUQAJaJN2XmpismEPoB1fmHqRl5
4CAjQVSaU4Z0mA4fMMTsc0eDbk2etL4EuIT+iDOJNN0r49KT+ivXbkqIEbI/ynki
JuhT/Uhjpq7bfDD/PkdlW75nhW8cLpdsOEEGsDZU8nVJE30Y1w7IQ7fmXgjPt9ER
umEo4Ska2GVyqsf2d7QjRdUJpIEl6z4qL6SavEpvtrkTMkydVMnBr/s2+HActKBp
uq8fA7PHJiAW4fHiAInacq3u4FwbHjghETNpJR2zU8CDp1A6azOiN5Zkn/21d4U1
seYfO4u3Tjuh62bcWSKQmFFcJ9Hl79VEYx6Q/nha3Xq8Fq1ll86/qn5t7TSCsylm
sqFT9Xo4Ay8UKXyTNp3oL3BgVUYmFEGYW4LhhyM87+imO5JaVAqhOgP7ABS/4d+J
kW82OhOgrS9Q2P/DkY1GG6ilv4A8hECxPMsVjqrbQA0/rmwmAPtgc951p86KMyhw
gjB96UbqsLZOsMSJko6ZyPZ5SBtxpFf2QOfzWJU/AOh/Y7CLLDwJy4Vwz2dmqUE4
BSnYUTqV2Blyty7x4XN6nRlSeVh3Kl1Qwi/VeHvXDgDsiSrWtqCyRv2CLKKEwnSL
fWr3Ts5ksyfeapmpglM/WR7Ee2m1KwunzcD/BAA+VM+gXYccgFZx5J+AEuM0X8Nn
UhhMI48v0s3qOGmJGax7
=QdtO
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Tue Apr 12 11:33:42 2016
Return-Path: <tony@att.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 9AE2012E1D4 for <ietf@ietfa.amsl.com>; Tue, 12 Apr 2016 11:33:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001] 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 H186ZKW4EN5j for <ietf@ietfa.amsl.com>; Tue, 12 Apr 2016 11:33:15 -0700 (PDT)
Received: from mx0b-00191d01.pphosted.com (mx0b-00191d01.pphosted.com [67.231.157.136]) (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 57FCE12E4B4 for <ietf@ietf.org>; Tue, 12 Apr 2016 11:33:14 -0700 (PDT)
Received: from pps.filterd (m0049463.ppops.net [127.0.0.1]) by m0049463.ppops.net-00191d01. (8.16.0.11/8.16.0.11) with SMTP id u3CIT75k048172; Tue, 12 Apr 2016 14:32:57 -0400
Received: from alpi155.enaf.aldc.att.com (sbcsmtp7.sbc.com [144.160.229.24]) by m0049463.ppops.net-00191d01. with ESMTP id 2294t0usp2-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 12 Apr 2016 14:32:57 -0400
Received: from enaf.aldc.att.com (localhost [127.0.0.1]) by alpi155.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id u3CIWtrH017114; Tue, 12 Apr 2016 14:32:56 -0400
Received: from mlpi409.sfdc.sbc.com (mlpi409.sfdc.sbc.com [130.9.128.241]) by alpi155.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id u3CIWoGw016999 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 12 Apr 2016 14:32:53 -0400
Received: from MISOUT7MSGHUBAG.ITServices.sbc.com (MISOUT7MSGHUBAG.itservices.sbc.com [130.9.129.151]) by mlpi409.sfdc.sbc.com (RSA Interceptor); Tue, 12 Apr 2016 18:32:39 GMT
Received: from MISOUT7MSGUSRCG.ITServices.sbc.com ([169.254.7.206]) by MISOUT7MSGHUBAG.ITServices.sbc.com ([130.9.129.151]) with mapi id 14.03.0248.002; Tue, 12 Apr 2016 14:32:39 -0400
From: "HANSEN, TONY L" <tony@att.com>
To: Rich Kulawiec <rsk@gsp.org>, ietf <ietf@ietf.org>
Subject: Re: Concerns about Singapore
Thread-Topic: Concerns about Singapore
Thread-Index: AQHRkPrmyaIeX02t9k2vDkQbYq+JzJ9/GEYAgAALigCAAAhOgIAAArkAgAACkgCAAAIPAIABI9GAgAF5/gCAAJkigIAAHRiAgAD2LYCAAATrgIAACooAgAADTgCAAACzAIAAWpOAgABVDYCAABLcgIAAXz+AgAAstICAABnMgIAArDoAgAAWc4CAALrLgIAAN+AA
Date: Tue, 12 Apr 2016 18:32:37 +0000
Message-ID: <A336C66D-2BCD-4693-ADA9-080EA1CD3B70@att.com>
References: <m21t6d7c9t.wl%randy@psg.com> <570A67B4.3010206@comcast.net> <570AB3AF.2050401@gmail.com> <87twj99c6w.fsf@tops.chopps.org> <CAKe6YvMyp-DyeDwpPY6KYmbDbnpgnvVk_cUStnA32wmgDWcz3w@mail.gmail.com> <BBF5DDFE515C3946BC18D733B20DAD233A62AA18@XMB122CNC.rim.net> <20160411104519.GA19092@gsp.org> <3F48466D-390C-4C18-B958-732AE3E46FF1@gmail.com> <20160411223403.GA6743@gsp.org> <CAPt1N1nNo0=JSptQdWRZCFy1v-m6Q8NQy4WVGHtnRJuFZFmMig@mail.gmail.com> <20160412110259.GA7267@gsp.org>
In-Reply-To: <20160412110259.GA7267@gsp.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.110.240.68]
Content-Type: text/plain; charset="utf-8"
Content-ID: <B1E54FC82D93D5418890AAB578F5F8D2@LOCAL>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-RSA-Inspected: yes
X-RSA-Classifications: public
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2016-04-12_09:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_policy_notspam policy=outbound_policy 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-1603180000 definitions=main-1604120265
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/x4lb73D9thbQU4eECZqFBCgx6KI>
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: Tue, 12 Apr 2016 18:33:23 -0000

SSBlbmNvdXJhZ2UgcGVvcGxlIHdobyBoYXZlIHN1Z2dlc3Rpb25zIG9uIGhvdyB0byBkbyByZW1v
dGUgbWVldGluZ3MgdG8gam9pbiB0aGUgY29udmVyc2F0aW9uIGluIHZtZWV0QGlldGYub3JnLg0K
DQoJVG9ueSBIYW5zZW4NCg0KT24gNC8xMi8xNiwgNzowMiBBTSwgImlldGYgb24gYmVoYWxmIG9m
IFJpY2ggS3VsYXdpZWMiIDxpZXRmLWJvdW5jZXNAaWV0Zi5vcmcgb24gYmVoYWxmIG9mIHJza0Bn
c3Aub3JnPiB3cm90ZToNCg0KPk9uIE1vbiwgQXByIDExLCAyMDE2IGF0IDA3OjU0OjI1UE0gLTA0
MDAsIFRlZCBMZW1vbiB3cm90ZToNCj4+IElmIHdlIHdlcmUgdG8gYXR0ZW1wdCBzdWNoIGEgdGhp
bmcsIGhvdyBkbyB5b3UgdGhpbmsgaXQgd291bGQgd29yaz8NCj4NCj5MZXQgbWUgcHJlZmFjZSB0
aGlzIGJ5IHNheWluZyB0aGF0IEkgdGhpbmsgYXR0ZW1wdHMgdG8gY29tcGxldGVseQ0KPm1pbWlj
IHRoZSBjdXJyZW50IGluLXBlcnNvbiBtZWV0aW5nIGV4cGVyaWVuY2UgYXMgaXQgZXhpc3RzIHBy
b2JhYmx5DQo+d29uJ3Qgd29yay4gIFRoZXkgbWlnaHQ6IGJ1dCB0aGV5IHByb2JhYmx5IHdvbid0
LiAgQnV0IHRoZW4gYWdhaW4sDQo+SSBkb24ndCB0aGluayB0aGF0J3MgZW50aXJlbHkgbmVjZXNz
YXJ5OiBwcm9jZXNzZXMgYW5kIHByb2NlZHVyZXMNCj5jaGFuZ2UgKGNvbXBhcmUgYm9hcmRpbmcg
YSBzdGVhbXNoaXAgaW4gMTkzMCB3aXRoIGFuIGFpcmNyYWZ0IGluIDIwMDUpDQo+YW5kIGV2b2x2
ZSBpbiBvcmRlciB0byB3b3JrIHdpdGggdGVjaG5vbG9neS4NCj4NCj5TbyBpZiBJIHdlcmUgdG8g
ZW52aXNpb24gdGhpcywgdGhpbmdzIEknZCB3YW50IHRvIGV4cGVyaW1lbnQgd2l0aA0KPndvdWxk
IGluY2x1ZGU6DQo+DQo+LSBwYXNzaXZlIHZpZXctb25seSwgbGlzdGVuLW9ubHkgcmVhZC1vbmx5
IGFjY2VzcyB0byBhbnlvbmUsIGFub255bW91c2x5Lg0KPihUaGF0IGlzOiBubyByZWdpc3RyYXRp
b24gcmVxdWlyZWQuKQ0KPg0KPi0gbGV2ZWxzIG9mIHJlYWQtd3JpdGUgYWNjZXNzLCBwZXJoYXBz
IChyb3VnaGx5IHNwZWFraW5nKSBkaXN0aW5ndWlzaGVkDQo+YXMgdGV4dCwgYXVkaW8sIGFuZCB2
aWRlby4gIFBhcnRpY2lwYW50cyBjb3VsZCBzZWxlY3QgYmFzZWQgb24gdGhlaXINCj5hdmFpbGFi
bGUgYmFuZHdpZHRoIGFuZCBvbiB0aGUgbGV2ZWwgdGhleSdyZSBjb21mb3J0YWJsZSB3aXRoLiAg
SSB0aGluaw0KPml0J3MgcmVhc29uYWJsZSB0byByZXF1aXJlIHJlZ2lzdHJhdGlvbiBmb3Igd3Jp
dGUgYWNjZXNzLg0KPg0KPi0gYSBjaGFubmVsIGZvciBwcmVzZW50YXRpb24gY29udGVudCBvbmx5
LiBBZ2FpbiwgdGhpcyBpcyBhbiBvcHRpb24gZm9yDQo+dGhvc2Ugd2l0aCBsaW1pdGVkIGJhbmR3
aWR0aCBvciBsaW1pdGVkIHRpbWUuDQo+DQo+LSBhYmlsaXR5IHRvIGRlbGF5L3RpbWUtc2hpZnQu
DQo+DQo+LSBwZXJoYXBzIHJlc3RydWN0dXJpbmcgbG9uZyBzZXNzaW9ucyBpbnRvIHNtYWxsZXIg
dGltZSBzbG90cy4gIElmIHBlb3BsZQ0KPmhhdmUgYWxsIHRyYXZlbGxlZCB0byB0aGUgc2FtZSBw
bGFjZSwgdGhlbiBpdCBtYWtlcyBzZW5zZSB0byBnZXQgYSBsb3QNCj5kb25lIGluIGEgc2hvcnQg
dGltZSwgYW5kIHNvIGEgZm91ciBob3VyIHNlc3Npb24gKGZvciBleGFtcGxlKSBtYWtlcw0KPnNl
bnNlLiAgQnV0IGlmIHBlb3BsZSBhcmUgaW4gZGlzcGFyYXRlIGxvY2F0aW9ucywgdGhlbiBtYXli
ZSBmb3VyIG9uZS1ob3VyDQo+c2Vzc2lvbnMgbWFrZSBtb3JlIHNlbnNlLiAgVGhpcyBhbHNvIGJl
dHRlciBhY2NvbW9kYXRlIHBlb3BsZSB3aG8gaGF2ZQ0KPnRyb3VibGUgY2FydmluZyBvdXQgZm91
ciBob3VycyBpbiB0aGUgbWlkZGxlIG9mIHRoZWlyIGRheS4gIE9yIG5pZ2h0Lg0KPg0KPi0gaW50
ZWdyYXRlZCBzdG9yYWdlIG9mIHNlc3Npb25zLCBzbyB0aGF0IHNvbWVvbmUgY2FuIHdhdGNoLCBs
aXN0ZW4sDQo+cmVhZCwgYW5kIGFic29yYiB0aGUgZW50aXJlIGV4cGVyaWVuY2UuICBVc2VmdWwg
Zm9yIHNvbWVvbmUgaGFsZiBhDQo+cGxhbmV0IGF3YXkgd2hvIHdvbid0IGJlIChvciBjYW4ndCBi
ZSkgYXdha2UgZm9yIHJlYWwtdGltZSBwYXJ0aWNpcGF0aW9uLg0KPg0KPi0gdHJhbnNsYXRpb25z
IGFuZC9vciB0ZXh0IGNhcHRpb25pbmcgYW5kL29yIHNvbWUga2luZCBvZiBhc3Npc3RhbmNlDQo+
Zm9yIG5vbi1uYXRpdmUgc3BlYWtlcnMgYW5kIHRoZSBoZWFyaW5nIGltcGFpcmVkLg0KPg0KPi0g
ZW1waGFzaXMgb24gdGhlIGluY2x1c2lvbiBvZiBwYXJ0aWNpcGFudHMgd2hvIGNhbid0IG1ha2Ug
aXQgdG8gbWVldGluZ3MNCj50b2RheSwgZWl0aGVyIGJlY2F1c2Ugb2YgdGltZSwgbW9uZXksIHBv
bGl0aWNzLCBkaXN0YW5jZSwgZmFtaWx5LCBqb2IsIGV0Yy4NCj4NCj5PdmVyIGFuZCBhYm92ZSBh
bGwgb2YgdGhpczogYSB3aWxsaW5nbmVzcyB0byBleHBlcmltZW50IGFuZCB0byBoYXZlDQo+c29t
ZSBvZiB0aG9zZSBleHBpcmVtZW50cyBmYWlsIC0tIHdoaWNoIHRoZXkgd2lsbC4NCj4NCj4tLS1y
c2sNCg==


From nobody Tue Apr 12 11:33:54 2016
Return-Path: <melinda.shore@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 084AE12E4B4 for <ietf@ietfa.amsl.com>; Tue, 12 Apr 2016 11:33:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 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, RCVD_IN_DNSWL_LOW=-0.7, 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 KP8m8b55RJWQ for <ietf@ietfa.amsl.com>; Tue, 12 Apr 2016 11:33:31 -0700 (PDT)
Received: from mail-pa0-x22a.google.com (mail-pa0-x22a.google.com [IPv6:2607:f8b0:400e:c03::22a]) (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 83CA012E1D4 for <ietf@ietf.org>; Tue, 12 Apr 2016 11:33:30 -0700 (PDT)
Received: by mail-pa0-x22a.google.com with SMTP id ot11so18018589pab.1 for <ietf@ietf.org>; Tue, 12 Apr 2016 11:33:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=mKaPYtyMcZmZn0rvjZiGDWWZ3Raz6Rjtvop51mloLzw=; b=CnS+xfhkd7IKQL+b8O6hsma4c+OiTwy6JHhqrCYOkckemmYIftg+SxXQbMOIABOJPN /ojO51H5ehYJlrM3vuaAPHkLjWpJjKe9ZGvzYc8r+W4w67RyaUQp31SVUTpFYmpBHryT vuFRINQW2Eii3025vObYViZ+cVwAYCToyodz09S/r/EVqLufB/Kp4LhFvmrhb5CuGQs7 lAfKv75FQoUQIqFUu2qEUKDwMF+lV5gDEWCZn+15zpF5dmdiF+RmOhNm8vZqhwzMUmvV bYfSQIcRIINWv0+RApl52X0EiW8izjzIp0acGmLg/OM3eCDIGyXS2iJJVGkve/B0JFvN rIOw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=mKaPYtyMcZmZn0rvjZiGDWWZ3Raz6Rjtvop51mloLzw=; b=AVxY1WGyGA7wZghuU1LVI0DLJcANyCWQ3VqG8HV2diYf4eDO/QDVD0baOZuqu0+896 XYyUiPcEuSMzzcxvrIZ4MDM33aEKh7u5ehaEo4S3D2Y5t0z8ANDfZ/13/ZfSrisY4MnW 21xhE2MtVk5AxMqxcG72jT/Ag6IWDvGwmIs/nfL7wlBfMFXPdljvbznUSMzTAlD1F/up AivnIG711Q+wsg1DyBKKB50YSfcrEl5Hjf9BKdJfusavlqGRWx2mG/TgoQ7Hc5MAeDsZ quxxqn96b6OF2SmyZ9PftKlrH7NF7Ee918jJtMU+xVHAVDlJ09FLryz07LqnFnB/WLhh AT6g==
X-Gm-Message-State: AOPr4FW6GYT31VmKVDmpmbML+MVK1DJmM28MNVmW6C/mWC2ZdjB8VrzsfOiGekYm++6M1g==
X-Received: by 10.66.118.70 with SMTP id kk6mr6748413pab.74.1460486010127; Tue, 12 Apr 2016 11:33:30 -0700 (PDT)
Received: from Melindas-MacBook-Pro.local (216-67-8-215-radius.dynamic.acsalaska.net. [216.67.8.215]) by smtp.googlemail.com with ESMTPSA id fk10sm45354218pab.33.2016.04.12.11.33.28 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 12 Apr 2016 11:33:29 -0700 (PDT)
Subject: Re: Remote only meetings? [Re: Concerns about Singapore]
To: chopps@chopps.org
References: <m21t6d7c9t.wl%randy@psg.com> <570A67B4.3010206@comcast.net> <570AB3AF.2050401@gmail.com> <87twj99c6w.fsf@tops.chopps.org> <CAKe6YvMyp-DyeDwpPY6KYmbDbnpgnvVk_cUStnA32wmgDWcz3w@mail.gmail.com> <BBF5DDFE515C3946BC18D733B20DAD233A62AA18@XMB122CNC.rim.net> <20160411104519.GA19092@gsp.org> <3F48466D-390C-4C18-B958-732AE3E46FF1@gmail.com> <20160411223403.GA6743@gsp.org> <87twj7eon7.fsf@tops.chopps.org> <20160412110839.GA20488@gsp.org> <8760vn82f2.fsf@tops.chopps.org> <570D2A34.1030700@gmail.com> <87bn5ehfkj.fsf@tops.chopps.org>
From: Melinda Shore <melinda.shore@gmail.com>
Message-ID: <570D3F91.2050200@gmail.com>
Date: Tue, 12 Apr 2016 10:33:53 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:38.0) Gecko/20100101 Thunderbird/38.6.0
MIME-Version: 1.0
In-Reply-To: <87bn5ehfkj.fsf@tops.chopps.org>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/l0DBVL8R7ExY82BEzoEIKZZ2Ym0>
Cc: 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: Tue, 12 Apr 2016 18:33:34 -0000

On 4/12/16 10:01 AM, chopps@chopps.org wrote:
> I know for a fact it is not how I and my co-chair run the IS-IS WG. I
> can't speak to whether other WGs are being run incorrectly. It's the
> responsibility of the participants and the ADs to make sure the
> chairs are not violating our own standards process though.

Well, I participate in working groups other than the ones
I chair and yes, there are working group chairs taking votes
and making decisions in meetings.  This is the way things are.
Ignoring how things are and hewing unreflectively to the ought-
to-be is one of the major things that got us to where we are
with NAT, among other problems.

Melinda



From nobody Tue Apr 12 11:36:49 2016
Return-Path: <melinda.shore@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 B934412D8E7 for <ietf@ietfa.amsl.com>; Tue, 12 Apr 2016 11:36:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1
X-Spam-Level: 
X-Spam-Status: No, score=-1 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, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLACK=1.7] autolearn=no 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 jbLMsD3gGYxr for <ietf@ietfa.amsl.com>; Tue, 12 Apr 2016 11:36:46 -0700 (PDT)
Received: from mail-pf0-x22d.google.com (mail-pf0-x22d.google.com [IPv6:2607:f8b0:400e:c00::22d]) (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 94AD712D9E0 for <ietf@ietf.org>; Tue, 12 Apr 2016 11:36:46 -0700 (PDT)
Received: by mail-pf0-x22d.google.com with SMTP id c20so18414315pfc.1 for <ietf@ietf.org>; Tue, 12 Apr 2016 11:36:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=mvKNODziontrjOgkTq6dAobVW1HemvBxH1hrJK7rKXA=; b=IxUwCUWABaFE/XqhwcIFHmj0aqx85yzvCM7oygWVaeokgJjFI8RUYeY/wa+r3aOBqs 8NQxnraIp1Z1sr7TC12zPP/q8hq1zjO8sc2gLvKXPh1VtulmomDXKGCL97baEbVvz6C3 f4InSiA46aZ9wba8Vfk5Cuh/+DQBU8kTOw4HXUQaQb/PL3dT2CynEFlmS6zpbBcA/Cx2 ZXih8zBf/5oJfxkHMzBa+AF85+QyHCCP911Y5PsKJt6b//VaWqcnNlNt4CJqwR2AO+Sa IYMk2SK1+oGndb3BFglBLd73NHhJHPsvrZsWNa83Chx30KSuHSH0q8CMo9GcVCCqOa6C WC8Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=mvKNODziontrjOgkTq6dAobVW1HemvBxH1hrJK7rKXA=; b=kLLaLWDllu7lSF+fY4TWN9Pv/lm24u9NKojHY92kuBsK7R9MJ5rYz9J9faIOxYA0s4 tiJLjIFg+L0PD05dggE+PUBI4sTG+bb+oehlBi/7dfZG2/MMjBAuzXh84LD2Ik4R1f9H jPFNweYBno55mBXuLVXCt9/V5Job7F0cQVw9xCBCezyZHTFKB8VqySCWWO3nPMgp08vo 6tCW0cu4A6VI1lcAimzv5p6EJkpFFlFSQ1JttL1DrdWmZtYN+n30CvTCXy66qRjpkks5 zBsOmzmOd7XG2WMu2yR9KFR/P65ezDOT/kkOTY0GDTWQ8oeSRtMjHEDsz2zbiCVlM7mL t3xw==
X-Gm-Message-State: AOPr4FWxC3XzAk2Hz2mKtSIkkAJ5Tk0MXtTpd+28qdXwvtI0btUN0OBYe1SP9Kk+cJ9I6Q==
X-Received: by 10.98.66.89 with SMTP id p86mr6671358pfa.42.1460486206271; Tue, 12 Apr 2016 11:36:46 -0700 (PDT)
Received: from Melindas-MacBook-Pro.local (216-67-8-215-radius.dynamic.acsalaska.net. [216.67.8.215]) by smtp.googlemail.com with ESMTPSA id q72sm45267788pfa.70.2016.04.12.11.36.45 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 12 Apr 2016 11:36:45 -0700 (PDT)
Subject: Re: Remote only meetings? [Re: Concerns about Singapore]
To: chopps@chopps.org
References: <570AB3AF.2050401@gmail.com> <87twj99c6w.fsf@tops.chopps.org> <CAKe6YvMyp-DyeDwpPY6KYmbDbnpgnvVk_cUStnA32wmgDWcz3w@mail.gmail.com> <BBF5DDFE515C3946BC18D733B20DAD233A62AA18@XMB122CNC.rim.net> <20160411104519.GA19092@gsp.org> <3F48466D-390C-4C18-B958-732AE3E46FF1@gmail.com> <20160411223403.GA6743@gsp.org> <87twj7eon7.fsf@tops.chopps.org> <20160412110839.GA20488@gsp.org> <8760vn82f2.fsf@tops.chopps.org> <20160412124639.GA27223@gsp.org> <87fuurgd8f.fsf@tops.chopps.org> <CABmDk8kCfTB_AKyqV4X+AghL2G7i+XcKR=tzV0jybM05k+UU4Q@mail.gmail.com> <65989154-BD08-45F0-B6F0-2AE3E435409C@chopps.org> <570D2BAD.7000307@gmail.com> <87a8kyhfa9.fsf@tops.chopps.org>
From: Melinda Shore <melinda.shore@gmail.com>
Message-ID: <570D4056.6000300@gmail.com>
Date: Tue, 12 Apr 2016 10:37:10 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:38.0) Gecko/20100101 Thunderbird/38.6.0
MIME-Version: 1.0
In-Reply-To: <87a8kyhfa9.fsf@tops.chopps.org>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/RUJnvfvRiCgqRGO8e4JmWYc57A0>
Cc: 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: Tue, 12 Apr 2016 18:36:47 -0000

On 4/12/16 10:07 AM, chopps@chopps.org wrote:
> I would like to actually. :) I'm wondering how I might go about getting
> all the email From addresses from every WG archive for the last year.
> I'm thinking if all archives are now hosted by mailman there's probably
> a way to script this.

I believe the IMAP interface is now available, and there's
always the option to screen-scrape the text archives:
http://ietf.org/mail-archive/text/

Melinda



From nobody Tue Apr 12 11:56:47 2016
Return-Path: <stewart.bryant@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 ADD1912DAED for <ietf@ietfa.amsl.com>; Tue, 12 Apr 2016 11:56:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 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, RCVD_IN_DNSWL_LOW=-0.7, 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 AwCspcY4b4xc for <ietf@ietfa.amsl.com>; Tue, 12 Apr 2016 11:56:44 -0700 (PDT)
Received: from mail-wm0-x22f.google.com (mail-wm0-x22f.google.com [IPv6:2a00:1450:400c:c09::22f]) (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 0904812DB21 for <ietf@ietf.org>; Tue, 12 Apr 2016 11:56:43 -0700 (PDT)
Received: by mail-wm0-x22f.google.com with SMTP id f198so199718620wme.0 for <ietf@ietf.org>; Tue, 12 Apr 2016 11:56:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding; bh=1umzNW3UaXMJhOXIvB0Xjdl5q/q3tsxL6RsAE4xnCqI=; b=DRyOgLd7OEyRHPdIOkhlrQrCB2nLZejHykIrb0ETggPQu5ypsV9cOglnhiuTQBGFrs P8uNFeF94nBK6ukjDFtNbZIq0glt21psqYSOXKzWxWxzvhQSqUD11tuoNdjd77KIFdZO menCinFkot+ejVXA+PHDivzbJ5skLLTijVzcD+9w98EAvrhYQDHKgek6iDSEN2On6WB3 vnuqcfZYN0z13psanM8D+c5YBsJKygeTd75phZRK5WsdkJfoG1KaQy7jPEbW+jCq9Hw9 APtIQC3Air8+IZ2kVGaFTQOWqmuAAKAdm14JCP5O0DwYHfymfIOXGvf3wihQ2wKmIJ6A 27QQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=1umzNW3UaXMJhOXIvB0Xjdl5q/q3tsxL6RsAE4xnCqI=; b=iktK3xLESwJWr5wPl4W2I3KJ7vbNMKtUojmR2k9d9igzF2S67jD2fVvOsrv8ZWZLmU eAs/kwEEs44yT3/QNCFv7ReBEJnZ068kWW9f7S4v8zAVLl1ClHEd1O9VxQiyQnM9ihzX nIvR03TX+VH3ySwn8qJ2nyylXqAPKJ2l6/aWYc+FQOPUxbzuYSopQxl8Dax78pAg5GmM zU5q1XRTMRdGcaz2SVOKTA9Y2P3FHIDgUD42I7FPfPGbTXs/QhwTwyGGVsgrobbz8gMk 0/TuKivh4J+krav1Jag+3NHI6ELaxW3DlgUtAhxS1vgyighbeKvuNBhEHu7ISyOhaSky CeXA==
X-Gm-Message-State: AD7BkJJgYmQ8Z1v9eiZXvrNkG2vKE2Z5SqhpAVqG5w9NMNNP8FfVdixXdQ1Y6DEXvN/ucg==
X-Received: by 10.28.63.73 with SMTP id m70mr27559234wma.55.1460487401538; Tue, 12 Apr 2016 11:56:41 -0700 (PDT)
Received: from [192.168.2.126] (host213-123-124-182.in-addr.btopenworld.com. [213.123.124.182]) by smtp.gmail.com with ESMTPSA id s10sm31899536wjp.3.2016.04.12.11.56.39 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 12 Apr 2016 11:56:40 -0700 (PDT)
Subject: Re: Concerns about Singapore
To: Richard Shockey <richard@shockey.us>, IETF discussion list <ietf@ietf.org>
References: <0D914666-C3D4-4CCE-AD5E-4E5B34EA1A73@piuha.net> <CAB75xn780nNDjGa_Cc222J20-+1CCHt09Xp8KHzaK=n0xx51pg@mail.gmail.com> <5706B100.9040509@mnt.se> <CAB75xn6fmj84ROUtG5eUB3GerHx83hrEr3w5vSADY_g=BRg5FA@mail.gmail.com> <5706BA40.3060005@mnt.se> <alpine.DEB.2.02.1604072157240.31096@uplift.swm.pp.se> <A9B63A6D-3102-482F-8FFC-2E57A5FD8336@nic.cz> <16925.1460122349@obiwan.sandelman.ca> <m27fg77zst.wl%randy@psg.com> <57097077.7040703@comcast.net> <m2fuuu75ls.wl%randy@psg.com> <87wpo5a8im.fsf@tops.chopps.org> <m260vp7eke.wl%randy@psg.com> <570A6458.3050206@comcast.net> <m21t6d7c9t.wl%randy@psg.com> <570A67B4.3010206@comcast.net> <570AB3AF.2050401@gmail.com> <87twj99c6w.fsf@tops.chopps.org> <CAKe6YvMyp-DyeDwpPY6KYmbDbnpgnvVk_cUStnA32wmgDWcz3w@mail.gmail.com> <BBF5DDFE515C3946BC18D733B20DAD233A62AA18@XMB122CNC.rim.net> <570B7B22.90801@cs.tcd.ie> <85DF4272E16A9292143D4AB5@JcK-HP8200.jck.com> <570BB4AA.5020307@gmail.com> <10C9F20A-F248-41CD-8131-79C5A7F9BD1D@shockey.us>
From: Stewart Bryant <stewart.bryant@gmail.com>
Message-ID: <570D44E2.9090008@gmail.com>
Date: Tue, 12 Apr 2016 19:56:34 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.7.0
MIME-Version: 1.0
In-Reply-To: <10C9F20A-F248-41CD-8131-79C5A7F9BD1D@shockey.us>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/9TfYacthuEgIsM8TDb1BjdjcU-I>
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: Tue, 12 Apr 2016 18:56:46 -0000

Note I did say "as far as I was concerned".

The only reason I go to IETF is to work F2F with people
to design protocols. All I am looking for in a venue
is to do that and nothing else for five and a half days.

Stewart

On 11/04/2016 22:04, Richard Shockey wrote:
>
> You canâ€™t do that!
>
> Didnâ€™t you get the memo. This is the Internet Engineering Travel Forum.
>
>
> â€”
> Richard Shockey
> Shockey Consulting LLC
> Chairman of the Board SIP Forum
> www.shockey.us
> www.sipforum.org
> richard<at>shockey.us
> Skype-Linkedin-Facebook rshockey101
> PSTN +1 703-593-2683
>
>
>
>
>
>
>
>
> On 4/11/16, 10:28 AM, "ietf on behalf of Stewart Bryant" <ietf-bounces@ietf.org on behalf of stewart.bryant@gmail.com> wrote:
>
>> I would be happy if we took a boring utilitarian
>> attitude to meeting venues:
>>
>> Find three places that more or less work and
>> just keep using them.
>>
>> Stewart
>>


From nobody Tue Apr 12 12:08:44 2016
Return-Path: <andy@yumaworks.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 20B2212E2BC for <ietf@ietfa.amsl.com>; Tue, 12 Apr 2016 12:08:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.9
X-Spam-Level: 
X-Spam-Status: No, score=-0.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLACK=1.7] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=yumaworks-com.20150623.gappssmtp.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 l9up8uxRwCYR for <ietf@ietfa.amsl.com>; Tue, 12 Apr 2016 12:08:41 -0700 (PDT)
Received: from mail-lf0-x235.google.com (mail-lf0-x235.google.com [IPv6:2a00:1450:4010:c07::235]) (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 957FE12E2EA for <ietf@ietf.org>; Tue, 12 Apr 2016 12:08:40 -0700 (PDT)
Received: by mail-lf0-x235.google.com with SMTP id g184so38904694lfb.3 for <ietf@ietf.org>; Tue, 12 Apr 2016 12:08:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yumaworks-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=yBnMk9EkBofAk6M8LX6n67NL0S0r1D3TEFvenolAy/8=; b=lcCMeMDOqW6+VIdEIvjhO9a/3ktcJnwfU+HOEM9da5eXO2QP+9fUJP5ZeSQTYXV8D6 jB3OAz8AV09eXE49YeEe+V5bgkHc3zv1le1FXS2NxPD9XvvyreMhVZRwisgAV1rU68ZQ /SlUaNrsPMXQJvGAu9Tsd5uVeAxmiHlsAxqL+3vkrcWbxGfcZ3qeIVRHHcWWSmfnL9Le QPkwB4G3EzsHto/U6hy8ankpgyWizDMIar9qEKA9lRfmIaCldMDLe/qifEDunkW80Wpg ez95sJwk8iqoxKBMs+R8WTuxe5ycZSOmP6mHckIDupnJmE1zI2klM2TRzd7Js52+LB5p p0Jw==
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:date :message-id:subject:from:to:cc; bh=yBnMk9EkBofAk6M8LX6n67NL0S0r1D3TEFvenolAy/8=; b=CubWXqkROLJ7wRyBq9MfhLklU4RZkSVUMHo9559C5srO+PXlY/YiVhvPB91WY0gH2l tzsLFrHhd+V424zONnFK1lNAVIVP2A+95N1p+Xu4bWsB3YE0ZtD+V4N0gcJ7y0AsRblJ pKKWkw6/tTHbSRlTOXJB+fg/NyIcnfLyHWxufnfWoFi70CGym4uj44KyaDcT1L3h+4PR 1MgwMnKX0t0AR/Bc33Y0AI/J7LmlY7QOXBVPTL7B6oBFUggn9CiFxpHg63i8UAkLDRh3 EbxEl9evpPnsHpnx6VvSKvh9VXqgkxsQohhOYuvi9CKvUHjFQJXfoLg+3H9rN/XMO6Jh ah7A==
X-Gm-Message-State: AOPr4FVTyZVLTX/pOt7+3gO0IX2oDjdPiKlihKR2Rt7ABYsmLGYXkblXeBCRNb3DgyszUMHNqQ/XtwjWvNsAMw==
MIME-Version: 1.0
X-Received: by 10.112.49.50 with SMTP id r18mr2125985lbn.65.1460488118617; Tue, 12 Apr 2016 12:08:38 -0700 (PDT)
Received: by 10.112.198.70 with HTTP; Tue, 12 Apr 2016 12:08:38 -0700 (PDT)
In-Reply-To: <570D1F04.8050701@joelhalpern.com>
References: <570AB3AF.2050401@gmail.com> <87twj99c6w.fsf@tops.chopps.org> <CAKe6YvMyp-DyeDwpPY6KYmbDbnpgnvVk_cUStnA32wmgDWcz3w@mail.gmail.com> <BBF5DDFE515C3946BC18D733B20DAD233A62AA18@XMB122CNC.rim.net> <20160411104519.GA19092@gsp.org> <3F48466D-390C-4C18-B958-732AE3E46FF1@gmail.com> <20160411223403.GA6743@gsp.org> <87twj7eon7.fsf@tops.chopps.org> <20160412110839.GA20488@gsp.org> <8760vn82f2.fsf@tops.chopps.org> <20160412124639.GA27223@gsp.org> <87fuurgd8f.fsf@tops.chopps.org> <CABmDk8kCfTB_AKyqV4X+AghL2G7i+XcKR=tzV0jybM05k+UU4Q@mail.gmail.com> <570D175A.1040001@joelhalpern.com> <CAPt1N1n0_UJ5AVzO=dyvzeLtYi0b8g5894wyhctwPwqTzme-PQ@mail.gmail.com> <570D1F04.8050701@joelhalpern.com>
Date: Tue, 12 Apr 2016 12:08:38 -0700
Message-ID: <CABCOCHTAnr+ugEx4+SJzdj0junZudx43kTn4bnHp1g79TZPPfg@mail.gmail.com>
Subject: Re: Remote only meetings? [Re: Concerns about Singapore]
From: Andy Bierman <andy@yumaworks.com>
To: "Joel M. Halpern" <jmh@joelhalpern.com>
Content-Type: multipart/alternative; boundary=001a113605a482724305304e63af
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/md4QPi2z2D8O2HA4k_WM5e60Xlc>
Cc: Rich Kulawiec <rsk@gsp.org>, "<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: Tue, 12 Apr 2016 19:08:43 -0000

--001a113605a482724305304e63af
Content-Type: text/plain; charset=UTF-8

Hi,

I agree that f2f meetings are best.
If not for the ad-hoc meetings, many of us would have
stopped going to IETFs a long time ago.  The official
meeting slots have devolved into status updates and slide presentations.

But don't think for a second that 20 hours of travel each way and thousands
of dollars in expenses are easy on anybody, As the remote tools keep getting
better, many of us will be asking if IETF travel is really worth it.


Andy




On Tue, Apr 12, 2016 at 9:15 AM, Joel M. Halpern <jmh@joelhalpern.com>
wrote:

> Ted, you missed my point.  Yes, I can arrange a call with the relevant
> people.  And I frequently do.
> It is harder, but that would be acceptable.
>
> The important part is that such calls are MUCH less effective than
> face-to-face discussions.  There are lots of well-known reasons for this.
>
> And no, inc ase it was not obvious, without the face-to-face meeting,
> there is no way to arrange such face-to-face meetings.
>
> Yes, we should work to make remote participation more effective.  Doing
> away with the face-to-face meetings reminds me of the old SF story of the
> ballet dancers who were forced to dance wearing extra weights, to be "fair"
> to the less talented dancers.
>
> Yours,
> Joel
>
> On 4/12/16 12:00 PM, Ted Lemon wrote:
>
>> This is all true, but the idea that it can't be replicated online is
>> silly.   How did you arrange to have lunch with these people?   You went
>> looking for them, rounded them up, and sat down to lunch.   You can do
>> that online as well.
>>
>> It is certainly true that random conversation in the halls can also
>> happen and lead to useful consequences, but having taken heavy advantage
>> of "running into people" in BA, I can tell you that a lot of it was
>> deliberate, and the parts that weren't probably would have been
>> triggered by WG meetings even if they hadn't been triggered by just
>> running into someone familiar in the lobby of the Hilton.
>>
>>
>> On Tue, Apr 12, 2016 at 11:42 AM, Joel M. Halpern <jmh@joelhalpern.com
>> <mailto:jmh@joelhalpern.com>> wrote:
>>
>>     I believe that there would be a real cost in moving to remote-only
>>     meetings.  Even putting aside the time zone difficulties, and the
>>     reduced effectiveness of in-meeting interaction, there are aspects
>>     of face-to-face interaction taht current remote technologies simply
>>     do not capture.
>>     It was very helpful in BA (and at many previous IETF meetings) to be
>>     able to find time to talk with a small number of people concerned
>>     about an aspect of one working group.  I did that over meals,
>>     breaks, etc.  It sorted out issues far more effectively than email
>>     conversations (in several cases, we had tried to sort it out via
>>     email.  10 minutes face-to-face clarified what was being missed, and
>>     found a good path forward.)
>>
>>     Even in-meeting, when the meeting works well it takes advantage of
>>     the nature of face-to-face interactions.  Admittedly, many sessions
>>     do not need this, but many do.
>>
>>     Yours,
>>     Joel
>>
>>     On 4/12/16 10:09 AM, Mary Barnes wrote:
>>
>>
>>
>>         On Tue, Apr 12, 2016 at 8:37 AM, <chopps@chopps.org
>>         <mailto:chopps@chopps.org>
>>         <mailto:chopps@chopps.org <mailto:chopps@chopps.org>>> wrote:
>>
>>
>>              Rich Kulawiec <rsk@gsp.org <mailto:rsk@gsp.org>
>>         <mailto:rsk@gsp.org <mailto:rsk@gsp.org>>> writes:
>>
>>
>>              > On Tue, Apr 12, 2016 at 07:57:53AM
>>         -0400,chopps@chopps.org <mailto:chopps@chopps.org>
>>         <mailto:chopps@chopps.org <mailto:chopps@chopps.org>> wrote:
>>              >> Your suggestion of not having them would subtract value
>>         from the process
>>              >> though. I don't see the win.
>>              >
>>              > The win is that all of the time and effort and expense
>>         (all of which
>>              > are finite resources) that go into those could be
>>         directed elsewhere.
>>
>>              The meetings and their fees are income positive, they
>>         aren't a drain on
>>              resource, the opposite in fact.
>>
>>         [MB] I would agree when it comes to dollars, but people (i.e., the
>>         effort to which Rich is referring) are also a resource and
>>         volunteers do
>>         the work.  If the only volunteers you get are from large
>>         companies, I
>>         think the IETF does lose.  With improved remote participation,
>>         individuals that aren't sponsored by large companies can continue
>> to
>>         contribute.  Without it, we become ineffective.  [/MB]
>>
>>
>>              > These meetings select for a highly limited (by
>>         circumstance, by necessity,
>>              > and by choice) subset.  And once upon a time, when the
>>         'net was much
>>              > younger and more limited in terms of geography and scope,
>>         that might
>>              > have been alright, because the subset mapped fairly well
>>         onto the larger
>>              > set of people involved in networking.  But that's no
>>         longer true.
>>              > And the difficulties/expense of travel are only going to
>>         get worse
>>              > for the forseeable future: they're not going to get better.
>>
>>              I think it would be useful to get some real data to measure
>>         exactly how
>>              highly limited that subset of people are. Perhaps as a
>>         simple first
>>              shot we could take email sent to IETF working group mailing
>>         lists over
>>              the last year, and cross reference that against the
>>         registrations lists
>>              of the last 3 IETFs and see what percentage of people doing
>>         IETF work
>>              cannot or choose not to attend the on-site meetings?
>>
>>         [MB] There was a separate list of registered remote attendees
>>         for this
>>         recent meeting. You can take a look there and see a number of
>>         long time
>>         contributors and some WG chairs (myself included) that have
>>         participated
>>         remotely.  The very reason I did not go was due to lack of
>> funding.
>>         There are a number of us that have contributed significantly
>>         over the
>>         past 15-30 years that would like to continue to do so but as
>>         independent
>>         consultants, some of these trips are just not fiscally
>>         possible.  I went
>>         to Yokohama so couldn't even entertain the idea of attending the
>>         meeting
>>         in BA without a sponsor.    And, I seriously doubt I can
>>         continue as a
>>         WG chair if I can't get funding in the future.  So, in the end,
>> the
>>         current model self selects and benefits the larger companies over
>>         individuals that really do want to do work for the "good of the
>>         Internet" but just can't justify the expense.   [/MB]
>>
>>              Thanks,
>>              Chris.
>>
>>
>>               >
>>               > ---rsk
>>
>>
>>
>>
>>
>

--001a113605a482724305304e63af
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi,<div><br></div><div>I agree that f2f meetings are best.=
</div><div>If not for the ad-hoc meetings, many of us would have</div><div>=
stopped going to IETFs a long time ago.=C2=A0 The official</div><div>meetin=
g slots have devolved into status updates and slide presentations.</div><di=
v><br></div><div>But don&#39;t think for a second that 20 hours of travel e=
ach way and thousands</div><div>of dollars in expenses are easy on anybody,=
 As the remote tools keep getting</div><div>better, many of us will be aski=
ng if IETF travel is really worth it.</div><div><br></div><div><br></div><d=
iv>Andy</div><div><br></div><div><br></div><div>=C2=A0</div></div><div clas=
s=3D"gmail_extra"><br><div class=3D"gmail_quote">On Tue, Apr 12, 2016 at 9:=
15 AM, Joel M. Halpern <span dir=3D"ltr">&lt;<a href=3D"mailto:jmh@joelhalp=
ern.com" target=3D"_blank">jmh@joelhalpern.com</a>&gt;</span> wrote:<br><bl=
ockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #=
ccc solid;padding-left:1ex">Ted, you missed my point.=C2=A0 Yes, I can arra=
nge a call with the relevant people.=C2=A0 And I frequently do.<br>
It is harder, but that would be acceptable.<br>
<br>
The important part is that such calls are MUCH less effective than face-to-=
face discussions.=C2=A0 There are lots of well-known reasons for this.<br>
<br>
And no, inc ase it was not obvious, without the face-to-face meeting, there=
 is no way to arrange such face-to-face meetings.<br>
<br>
Yes, we should work to make remote participation more effective.=C2=A0 Doin=
g away with the face-to-face meetings reminds me of the old SF story of the=
 ballet dancers who were forced to dance wearing extra weights, to be &quot=
;fair&quot; to the less talented dancers.<br>
<br>
Yours,<br>
Joel<br>
<br>
On 4/12/16 12:00 PM, Ted Lemon wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
This is all true, but the idea that it can&#39;t be replicated online is<br=
>
silly.=C2=A0 =C2=A0How did you arrange to have lunch with these people?=C2=
=A0 =C2=A0You went<br>
looking for them, rounded them up, and sat down to lunch.=C2=A0 =C2=A0You c=
an do<br>
that online as well.<br>
<br>
It is certainly true that random conversation in the halls can also<br>
happen and lead to useful consequences, but having taken heavy advantage<br=
>
of &quot;running into people&quot; in BA, I can tell you that a lot of it w=
as<br>
deliberate, and the parts that weren&#39;t probably would have been<br>
triggered by WG meetings even if they hadn&#39;t been triggered by just<br>
running into someone familiar in the lobby of the Hilton.<br>
<br>
<br>
On Tue, Apr 12, 2016 at 11:42 AM, Joel M. Halpern &lt;<a href=3D"mailto:jmh=
@joelhalpern.com" target=3D"_blank">jmh@joelhalpern.com</a><br>
&lt;mailto:<a href=3D"mailto:jmh@joelhalpern.com" target=3D"_blank">jmh@joe=
lhalpern.com</a>&gt;&gt; wrote:<br>
<br>
=C2=A0 =C2=A0 I believe that there would be a real cost in moving to remote=
-only<br>
=C2=A0 =C2=A0 meetings.=C2=A0 Even putting aside the time zone difficulties=
, and the<br>
=C2=A0 =C2=A0 reduced effectiveness of in-meeting interaction, there are as=
pects<br>
=C2=A0 =C2=A0 of face-to-face interaction taht current remote technologies =
simply<br>
=C2=A0 =C2=A0 do not capture.<br>
=C2=A0 =C2=A0 It was very helpful in BA (and at many previous IETF meetings=
) to be<br>
=C2=A0 =C2=A0 able to find time to talk with a small number of people conce=
rned<br>
=C2=A0 =C2=A0 about an aspect of one working group.=C2=A0 I did that over m=
eals,<br>
=C2=A0 =C2=A0 breaks, etc.=C2=A0 It sorted out issues far more effectively =
than email<br>
=C2=A0 =C2=A0 conversations (in several cases, we had tried to sort it out =
via<br>
=C2=A0 =C2=A0 email.=C2=A0 10 minutes face-to-face clarified what was being=
 missed, and<br>
=C2=A0 =C2=A0 found a good path forward.)<br>
<br>
=C2=A0 =C2=A0 Even in-meeting, when the meeting works well it takes advanta=
ge of<br>
=C2=A0 =C2=A0 the nature of face-to-face interactions.=C2=A0 Admittedly, ma=
ny sessions<br>
=C2=A0 =C2=A0 do not need this, but many do.<br>
<br>
=C2=A0 =C2=A0 Yours,<br>
=C2=A0 =C2=A0 Joel<br>
<br>
=C2=A0 =C2=A0 On 4/12/16 10:09 AM, Mary Barnes wrote:<br>
<br>
<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 On Tue, Apr 12, 2016 at 8:37 AM, &lt;<a href=3D=
"mailto:chopps@chopps.org" target=3D"_blank">chopps@chopps.org</a><br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 &lt;mailto:<a href=3D"mailto:chopps@chopps.org"=
 target=3D"_blank">chopps@chopps.org</a>&gt;<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 &lt;mailto:<a href=3D"mailto:chopps@chopps.org"=
 target=3D"_blank">chopps@chopps.org</a> &lt;mailto:<a href=3D"mailto:chopp=
s@chopps.org" target=3D"_blank">chopps@chopps.org</a>&gt;&gt;&gt; wrote:<br=
>
<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Rich Kulawiec &lt;<a href=
=3D"mailto:rsk@gsp.org" target=3D"_blank">rsk@gsp.org</a> &lt;mailto:<a hre=
f=3D"mailto:rsk@gsp.org" target=3D"_blank">rsk@gsp.org</a>&gt;<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 &lt;mailto:<a href=3D"mailto:rsk@gsp.org" targe=
t=3D"_blank">rsk@gsp.org</a> &lt;mailto:<a href=3D"mailto:rsk@gsp.org" targ=
et=3D"_blank">rsk@gsp.org</a>&gt;&gt;&gt; writes:<br>
<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&gt; On Tue, Apr 12, 2016 a=
t 07:57:53AM<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 -0400,<a href=3D"mailto:chopps@chopps.org" targ=
et=3D"_blank">chopps@chopps.org</a> &lt;mailto:<a href=3D"mailto:chopps@cho=
pps.org" target=3D"_blank">chopps@chopps.org</a>&gt;<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 &lt;mailto:<a href=3D"mailto:chopps@chopps.org"=
 target=3D"_blank">chopps@chopps.org</a> &lt;mailto:<a href=3D"mailto:chopp=
s@chopps.org" target=3D"_blank">chopps@chopps.org</a>&gt;&gt; wrote:<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&gt;&gt; Your suggestion of=
 not having them would subtract value<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 from the process<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&gt;&gt; though. I don&#39;=
t see the win.<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&gt;<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&gt; The win is that all of=
 the time and effort and expense<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 (all of which<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&gt; are finite resources) =
that go into those could be<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 directed elsewhere.<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0The meetings and their fees=
 are income positive, they<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 aren&#39;t a drain on<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0resource, the opposite in f=
act.<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 [MB] I would agree when it comes to dollars, bu=
t people (i.e., the<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 effort to which Rich is referring) are also a r=
esource and<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 volunteers do<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 the work.=C2=A0 If the only volunteers you get =
are from large<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 companies, I<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 think the IETF does lose.=C2=A0 With improved r=
emote participation,<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 individuals that aren&#39;t sponsored by large =
companies can continue to<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 contribute.=C2=A0 Without it, we become ineffec=
tive.=C2=A0 [/MB]<br>
<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&gt; These meetings select =
for a highly limited (by<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 circumstance, by necessity,<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&gt; and by choice) subset.=
=C2=A0 And once upon a time, when the<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 &#39;net was much<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&gt; younger and more limit=
ed in terms of geography and scope,<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 that might<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&gt; have been alright, bec=
ause the subset mapped fairly well<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 onto the larger<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&gt; set of people involved=
 in networking.=C2=A0 But that&#39;s no<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 longer true.<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&gt; And the difficulties/e=
xpense of travel are only going to<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 get worse<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&gt; for the forseeable fut=
ure: they&#39;re not going to get better.<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0I think it would be useful =
to get some real data to measure<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 exactly how<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0highly limited that subset =
of people are. Perhaps as a<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 simple first<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0shot we could take email se=
nt to IETF working group mailing<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 lists over<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0the last year, and cross re=
ference that against the<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 registrations lists<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0of the last 3 IETFs and see=
 what percentage of people doing<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 IETF work<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0cannot or choose not to att=
end the on-site meetings?<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 [MB] There was a separate list of registered re=
mote attendees<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 for this<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 recent meeting. You can take a look there and s=
ee a number of<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 long time<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 contributors and some WG chairs (myself include=
d) that have<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 participated<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 remotely.=C2=A0 The very reason I did not go wa=
s due to lack of funding.<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 There are a number of us that have contributed =
significantly<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 over the<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 past 15-30 years that would like to continue to=
 do so but as<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 independent<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 consultants, some of these trips are just not f=
iscally<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 possible.=C2=A0 I went<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 to Yokohama so couldn&#39;t even entertain the =
idea of attending the<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 meeting<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 in BA without a sponsor.=C2=A0 =C2=A0 And, I se=
riously doubt I can<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 continue as a<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 WG chair if I can&#39;t get funding in the futu=
re.=C2=A0 So, in the end, the<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 current model self selects and benefits the lar=
ger companies over<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 individuals that really do want to do work for =
the &quot;good of the<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Internet&quot; but just can&#39;t justify the e=
xpense.=C2=A0 =C2=A0[/MB]<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Thanks,<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Chris.<br>
<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 &gt;<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 &gt; ---rsk<br>
<br>
<br>
<br>
<br>
</blockquote>
<br>
</blockquote></div><br></div>

--001a113605a482724305304e63af--


From nobody Tue Apr 12 12:19:50 2016
Return-Path: <carlosm3011@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 C63E712E7B3 for <ietf@ietfa.amsl.com>; Tue, 12 Apr 2016 12:19:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.45
X-Spam-Level: 
X-Spam-Status: No, score=-2.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, RCVD_IN_DNSWL_LOW=-0.7, 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 tLHE-suDTQWV for <ietf@ietfa.amsl.com>; Tue, 12 Apr 2016 12:19:46 -0700 (PDT)
Received: from mail-vk0-x232.google.com (mail-vk0-x232.google.com [IPv6:2607:f8b0:400c:c05::232]) (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 13F3B12E8CB for <ietf@ietf.org>; Tue, 12 Apr 2016 12:19:44 -0700 (PDT)
Received: by mail-vk0-x232.google.com with SMTP id e185so38772084vkb.1 for <ietf@ietf.org>; Tue, 12 Apr 2016 12:19:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=reply-to:subject:references:to:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=PPMcG0XMpOZ8IqgR6lGzHOToRewHFpayNNuhSoSFO3g=; b=EWatoZ/odl8YHXbbRzfjehthqrGqkV2j/A7EwTRGLi1aOwKTTJpTi2ZtJ0iUqfYNkV mRyre5iOQn9kquHlsqK+NLLr64OqQzo00wH3jB5IcAKEhKFqz80GpSdQ8ysC8x+lEFyP MPVo3xoJYYwEYPdDnbl40YJTCVWmTXr81vuPgtV02f3o/IwxmSnkTeZSx412swoT2VOs ZJCGevCGJHaeMDMQwd9WgPKvUYY8ZpXZ1v6HZVSc83ZoXJoXjrWkNhgSoTy5jP7XoPLC aJDh1ebQkaQlF519LvWUWwCcRqnUxZqL/kTCyS7/hphhLVyCPNct56uwxMsYYzjgLTNQ Uv4A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:reply-to:subject:references:to:from:message-id :date:user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=PPMcG0XMpOZ8IqgR6lGzHOToRewHFpayNNuhSoSFO3g=; b=QYSVripdZMVagmJm0nBAaeJjyIlz0gthoyeJ/xQFEZd8aQwWoXD/r+KPy14QAlr3vu XnU+mr0Uq6/ydbyQBMyV18ccFOB9R7bO4Jt2nodl8sDE3uVhidLxP8qMpD+BuVXPeP5r 0vu3N891bp3+tR+uRqoAZuLZyfLPXo3lM1GckO0UuyFecKzF+yD2zcpglX/HoynvgORC Wl/xbWtP7jiazwBtSLD9vJHDOoC/NeDRdJFZ8eYEToPoBNAOoA7YjBpaxlrhU672dHHN yxPMXYalDws0I4CsXl1wZ10ynJ0dNIKSv9UhB1PKPSv5ybe8+CIrNeNF3pp+/l+J2lz9 nFAQ==
X-Gm-Message-State: AOPr4FVH8QfC16RyRRFn0nYLu16FXVvuROINB7p3dtTqCNjoEeJhZZK0Egf06TjSUm/Bgw==
X-Received: by 10.159.37.180 with SMTP id 49mr2625583uaf.148.1460488783675; Tue, 12 Apr 2016 12:19:43 -0700 (PDT)
Received: from [200.7.87.117] ([200.7.87.117]) by smtp.googlemail.com with ESMTPSA id i126sm5341957vke.23.2016.04.12.12.19.42 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 12 Apr 2016 12:19:42 -0700 (PDT)
Subject: Re: thank you
References: <m24mb76cns.wl%randy@psg.com>
To: Randy Bush <randy@psg.com>, IETF Disgust List <ietf@ietf.org>
From: "Carlos M. Martinez" <carlosm3011@gmail.com>
Message-ID: <570D4A4C.5050406@gmail.com>
Date: Tue, 12 Apr 2016 16:19:40 -0300
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:38.0) Gecko/20100101 Thunderbird/38.7.2
MIME-Version: 1.0
In-Reply-To: <m24mb76cns.wl%randy@psg.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/N0IqOde7Zvovtl1JxjoYG3kSPWU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: carlos@lacnic.net
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: Tue, 12 Apr 2016 19:19:49 -0000

Thank you Randy. I'm extremely happy that the meeting went well, and
that, except for a few glitches here and there, every one had a good and
productive time in BA.

On 4/11/16 6:47 PM, Randy Bush wrote:
> buenos aires is a beautiful latin american city, hospitable, and with
> great folk.  kudos for such a great meeting go to many people and
> organizations that i will not enumerate for fear of missing one.  thank
> you.
> 
> randy
> 


From nobody Tue Apr 12 12:21:34 2016
Return-Path: <mellon@fugue.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 C300012E6C8 for <ietf@ietfa.amsl.com>; Tue, 12 Apr 2016 12:21:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.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 rJI9cVDokN-r for <ietf@ietfa.amsl.com>; Tue, 12 Apr 2016 12:21:31 -0700 (PDT)
Received: from mail-lf0-x22c.google.com (mail-lf0-x22c.google.com [IPv6:2a00:1450:4010:c07::22c]) (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 2E1ED12D617 for <ietf@ietf.org>; Tue, 12 Apr 2016 12:21:31 -0700 (PDT)
Received: by mail-lf0-x22c.google.com with SMTP id e190so39521424lfe.0 for <ietf@ietf.org>; Tue, 12 Apr 2016 12:21:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=AnewRDX7gnQCsOo2ge62BhKsG1Ufuq1rel//3SkCoyA=; b=vioi0AmstFefnkuQd4xqMTPIxsM1BcSlJjPzPFE2O5+SwtgVk4da+qYmVU54SXO0B0 jWHPE3BVTcC7dYk/j/rQkKVbKMIpBayGNJ7/Uku7mLwBzuxvatSY+O7xyOKcxtlfRPlH b4QDaMmb8OaBIabAOWo5sWKq1Y9cB151mGFebJWYdcMDpDwiwoqXWEgrmN4XFMX2RggE nuInVVAxkzhrL+jnop1Vf75lCW31Ej63xRXNQ0y8sC2eyr7pXoA5MUD8RG5OdTUO3x5S yn9ATFFIl5tbne4PSgvPHH058hwEtfsXet+h7NCvMMvtyj50kJrOji07ZlKUhwOjMR69 e4Hw==
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=AnewRDX7gnQCsOo2ge62BhKsG1Ufuq1rel//3SkCoyA=; b=MkXTFhbfeBtS+1o6z+A0VDU6UI9UUJoeoyXMCEOdB0tS4IHHlAveTyIDyFdTwB+Xnn XOui1uuux6wKYr2pJkU94On9aTgPu7CDiVN9hCHMwm3iF31JLwNcJah8GINFHj01GzgD jO5xWqjrIn1nMxFU+izqMl6DyGjYGfLMU0bVuk0dYHn8qc6qKjzEOPu3WdOhSn3vdTDH 4e4D0J6bM6QlLwKZoh68LETH8eiCOrsnbM9GCv8p69Orw2c4G/6gO0hEqZ4tpsocfM6N ll/ZkDbOM6RSW8/B3O8cEFtpB9Ii4vM6S/aGOCtHoE7xhCc+xYxJK3QMUTeaQOU4Ywju RRhg==
X-Gm-Message-State: AOPr4FUW+MgSQ0f9P9uMcEd7wi/vmUQ4i2JDiiU4tbK5s3tiSLfNnQcERVqpezuKzxaeTx7ukHZyA+FBD3ClAw==
X-Received: by 10.25.143.212 with SMTP id r203mr2189653lfd.119.1460488889334;  Tue, 12 Apr 2016 12:21:29 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.25.40.136 with HTTP; Tue, 12 Apr 2016 12:20:49 -0700 (PDT)
X-Originating-IP: [71.233.41.235]
In-Reply-To: <570D44E2.9090008@gmail.com>
References: <0D914666-C3D4-4CCE-AD5E-4E5B34EA1A73@piuha.net> <CAB75xn780nNDjGa_Cc222J20-+1CCHt09Xp8KHzaK=n0xx51pg@mail.gmail.com> <5706B100.9040509@mnt.se> <CAB75xn6fmj84ROUtG5eUB3GerHx83hrEr3w5vSADY_g=BRg5FA@mail.gmail.com> <5706BA40.3060005@mnt.se> <alpine.DEB.2.02.1604072157240.31096@uplift.swm.pp.se> <A9B63A6D-3102-482F-8FFC-2E57A5FD8336@nic.cz> <16925.1460122349@obiwan.sandelman.ca> <m27fg77zst.wl%randy@psg.com> <57097077.7040703@comcast.net> <m2fuuu75ls.wl%randy@psg.com> <87wpo5a8im.fsf@tops.chopps.org> <m260vp7eke.wl%randy@psg.com> <570A6458.3050206@comcast.net> <m21t6d7c9t.wl%randy@psg.com> <570A67B4.3010206@comcast.net> <570AB3AF.2050401@gmail.com> <87twj99c6w.fsf@tops.chopps.org> <CAKe6YvMyp-DyeDwpPY6KYmbDbnpgnvVk_cUStnA32wmgDWcz3w@mail.gmail.com> <BBF5DDFE515C3946BC18D733B20DAD233A62AA18@XMB122CNC.rim.net> <570B7B22.90801@cs.tcd.ie> <85DF4272E16A9292143D4AB5@JcK-HP8200.jck.com> <570BB4AA.5020307@gmail.com> <10C9F20A-F248-41CD-8131-79C5A7F9BD1D@shockey.us> <570D44E2.9090008@gmail.com>
From: Ted Lemon <mellon@fugue.com>
Date: Tue, 12 Apr 2016 15:20:49 -0400
Message-ID: <CAPt1N1nux=hGTtuawHuzK5GoXSFxX66pzu_AMqoCKQGji717nQ@mail.gmail.com>
Subject: Re: Concerns about Singapore
To: Stewart Bryant <stewart.bryant@gmail.com>
Content-Type: multipart/alternative; boundary=001a1140225472961305304e9135
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/jPaWqCDi7459PoIgXht-rBN0m9Y>
Cc: IETF discussion list <ietf@ietf.org>, Richard Shockey <richard@shockey.us>
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: Tue, 12 Apr 2016 19:21:34 -0000

--001a1140225472961305304e9135
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

True.   I flew to BA, got to speak a little bit of Spanish (badly) and a
lot of english, then flew home.   I took some pictures of El Puente de la
Mujer, but basically didn't get more than a quarter mile from the hotel
more than once the whole time I was there.   But the point of going to
different places is for the people who live there, not for us (except to
the extent that we live there).

On Tue, Apr 12, 2016 at 2:56 PM, Stewart Bryant <stewart.bryant@gmail.com>
wrote:

> Note I did say "as far as I was concerned".
>
> The only reason I go to IETF is to work F2F with people
> to design protocols. All I am looking for in a venue
> is to do that and nothing else for five and a half days.
>
> Stewart
>
>
> On 11/04/2016 22:04, Richard Shockey wrote:
>
>>
>> You can=E2=80=99t do that!
>>
>> Didn=E2=80=99t you get the memo. This is the Internet Engineering Travel=
 Forum.
>>
>>
>> =E2=80=94
>> Richard Shockey
>> Shockey Consulting LLC
>> Chairman of the Board SIP Forum
>> www.shockey.us
>> www.sipforum.org
>> richard<at>shockey.us
>> Skype-Linkedin-Facebook rshockey101
>> PSTN +1 703-593-2683
>>
>>
>>
>>
>>
>>
>>
>>
>> On 4/11/16, 10:28 AM, "ietf on behalf of Stewart Bryant" <
>> ietf-bounces@ietf.org on behalf of stewart.bryant@gmail.com> wrote:
>>
>> I would be happy if we took a boring utilitarian
>>> attitude to meeting venues:
>>>
>>> Find three places that more or less work and
>>> just keep using them.
>>>
>>> Stewart
>>>
>>>
>

--001a1140225472961305304e9135
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">True. =C2=A0 I flew to BA, got to speak a little bit of Sp=
anish (badly) and a lot of english, then flew home. =C2=A0 I took some pict=
ures of El Puente de la Mujer, but basically didn&#39;t get more than a qua=
rter mile from the hotel more than once the whole time I was there. =C2=A0 =
But the point of going to different places is for the people who live there=
, not for us (except to the extent that we live there).</div><div class=3D"=
gmail_extra"><br><div class=3D"gmail_quote">On Tue, Apr 12, 2016 at 2:56 PM=
, Stewart Bryant <span dir=3D"ltr">&lt;<a href=3D"mailto:stewart.bryant@gma=
il.com" target=3D"_blank">stewart.bryant@gmail.com</a>&gt;</span> wrote:<br=
><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1=
px #ccc solid;padding-left:1ex">Note I did say &quot;as far as I was concer=
ned&quot;.<br>
<br>
The only reason I go to IETF is to work F2F with people<br>
to design protocols. All I am looking for in a venue<br>
is to do that and nothing else for five and a half days.<span class=3D"HOEn=
Zb"><font color=3D"#888888"><br>
<br>
Stewart</font></span><div class=3D"HOEnZb"><div class=3D"h5"><br>
<br>
On 11/04/2016 22:04, Richard Shockey wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<br>
You can=E2=80=99t do that!<br>
<br>
Didn=E2=80=99t you get the memo. This is the Internet Engineering Travel Fo=
rum.<br>
<br>
<br>
=E2=80=94<br>
Richard Shockey<br>
Shockey Consulting LLC<br>
Chairman of the Board SIP Forum<br>
<a href=3D"http://www.shockey.us" rel=3D"noreferrer" target=3D"_blank">www.=
shockey.us</a><br>
<a href=3D"http://www.sipforum.org" rel=3D"noreferrer" target=3D"_blank">ww=
w.sipforum.org</a><br>
richard&lt;at&gt;<a href=3D"http://shockey.us" rel=3D"noreferrer" target=3D=
"_blank">shockey.us</a><br>
Skype-Linkedin-Facebook rshockey101<br>
PSTN <a href=3D"tel:%2B1%20703-593-2683" value=3D"+17035932683" target=3D"_=
blank">+1 703-593-2683</a><br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
On 4/11/16, 10:28 AM, &quot;ietf on behalf of Stewart Bryant&quot; &lt;<a h=
ref=3D"mailto:ietf-bounces@ietf.org" target=3D"_blank">ietf-bounces@ietf.or=
g</a> on behalf of <a href=3D"mailto:stewart.bryant@gmail.com" target=3D"_b=
lank">stewart.bryant@gmail.com</a>&gt; wrote:<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
I would be happy if we took a boring utilitarian<br>
attitude to meeting venues:<br>
<br>
Find three places that more or less work and<br>
just keep using them.<br>
<br>
Stewart<br>
<br>
</blockquote></blockquote>
<br>
</div></div></blockquote></div><br></div>

--001a1140225472961305304e9135--


From nobody Tue Apr 12 13:07:15 2016
Return-Path: <sm@resistor.net>
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 8ECF312DB50 for <ietf@ietfa.amsl.com>; Tue, 12 Apr 2016 13:07:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.79
X-Spam-Level: 
X-Spam-Status: No, score=-1.79 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, RCVD_IN_DNSWL_NONE=-0.0001, T_DKIM_INVALID=0.01] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=opendkim.org header.b=Vf763zrf; dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=resistor.net header.b=AogmX2oi
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 C1OYEOzXPl2w for <ietf@ietfa.amsl.com>; Tue, 12 Apr 2016 13:07:12 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 8CD5612DA1B for <ietf@ietf.org>; Tue, 12 Apr 2016 13:07:12 -0700 (PDT)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id u3CK6xKb028470 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 12 Apr 2016 13:07:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1460491626; x=1460578026; bh=54MzQhrWZJ+ktX04xGbjtfzi/l0D34G5OFOjjenYFac=; h=Date:To:From:Subject:In-Reply-To:References; b=Vf763zrf9dfyd2cCzSigt8SXCLiqsoETjEHhfSCnAnD4SHb9XumVNR616bU1ZON+i 9HzfltLpmgM/6mrui0TKsz/cqtdnXjvfm2Q5aUKmuwpXC6WDiy2RThg+xYbTBVG//t /o3Qqc1cK12lkaWw4cWq8TcLQKBQj6DTRRYYDCrA=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1460491626; x=1460578026; i=@resistor.net; bh=54MzQhrWZJ+ktX04xGbjtfzi/l0D34G5OFOjjenYFac=; h=Date:To:From:Subject:In-Reply-To:References; b=AogmX2oieBM6iYKR6aWFKzkFDMUDTrnvaG5QjoprEBP0RWl9HYIocokBUH0FeEydi ignvBzoVTlf3cB4KHDirCyqVT9ihrjJzCD4puNnnCm+8zzMvi3YK2ohrER5EImuobK 0VvWtAiphtuywnNOkLGg3DtX8e9x0w/UO/PpeQ1g=
Message-Id: <6.2.5.6.2.20160412114424.0e7061b0@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Tue, 12 Apr 2016 13:00:20 -0700
To: Dave Crocker <dcrocker@bbiw.net>, ietf@ietf.org
From: SM <sm@resistor.net>
Subject: Re: Transparency of IAOC
In-Reply-To: <6.2.5.6.2.20160412031201.0da034e8@elandnews.com>
References: <6.2.5.6.2.20160412031201.0da034e8@elandnews.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/D9w4H_PrNArvXzrUTFw5uNeqjMw>
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: Tue, 12 Apr 2016 20:07:13 -0000

Hi Dave,

I mentioned that I'll reply to the questions which you asked during 
our discussion.  The arguments for transparency is that one does not 
have to rely on gossip or have to assess the level of honesty of a 
person providing the information to understand the rationale for a 
decision.  One argument against transparency is that not all 
information can be made public.

The latest minutes of the IESG are at 
http://ietf.org/iesg/minutes/2016/narrative-minutes-2016-03-03.html 
I don't know whether there was community pressure for any IETF 
participant to be able to join an IESG Teleconference.  The option is 
there though.  Is the IESG more open than five years back?  Yes.

Is it appropriate to ask questions to the IAOC?  I don't see people 
who have been part of the "leadership" doing that.  Maybe, it will be 
viewed as politically incorrect and it is not good for a person's 
IETF career.  In other words, it is a matter of perception.

Regards,
-sm


From nobody Tue Apr 12 13:17:09 2016
Return-Path: <johnl@taugh.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 9AF9312EA9C for <ietf@ietfa.amsl.com>; Tue, 12 Apr 2016 13:17:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1536-bit key) header.d=iecc.com header.b=5yMd9n3J; dkim=pass (1536-bit key) header.d=taugh.com header.b=aDzYxnJE
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 LQswYKP4xj4H for <ietf@ietfa.amsl.com>; Tue, 12 Apr 2016 13:17:05 -0700 (PDT)
Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E9C4612EAB2 for <ietf@ietf.org>; Tue, 12 Apr 2016 13:17:04 -0700 (PDT)
Received: (qmail 47337 invoked from network); 12 Apr 2016 20:17:03 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent; s=b8e8.570d57bf.k1604; bh=WvWcDJ+3AHnCxkJ1fYS49Q19Zy9wgfK2SZU6Leg4TIA=; b=5yMd9n3JKMtDM7WvPeMr/njVAIWBzfX0OA16YQtiALtCLp6i7I4CYsW1R1Xuq626BOYGpZZwJ6EsFBkRZqO0HoS30z+2dELOObbxMjwaQIirmX0HdUcLO2gaZAc9r8BTQonupPAEvO5IiBklA2wF5UkcPLl7p4LHdfWFslvI0AN6WQRcrBxpZdrVxM0xffTFJrQ5ap7AlEJ86dxdo8wByV1OZCn5JO8Sl9aodyvyGq4OIGVMGm3kJpEJcSMca3ZI
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent; s=b8e8.570d57bf.k1604; bh=WvWcDJ+3AHnCxkJ1fYS49Q19Zy9wgfK2SZU6Leg4TIA=; b=aDzYxnJEOIHP3eeNGmNyKGu+O8415nV0AX5Tr3GrgYGvc4l7yKhwNKbp+21hmvCUwIkFKc09JyOwOkaIg+WGydxvoOoLjF9ltvYibDPVCpAwCsgHY2LHBdmFb5w9+ZXCdH2YVqApqamEabE8690aBDmBsWQYT3IGuVCp8rQVu53YSrNpIOFS4XcvBTgPLI+e+ZhI93XHm9Mb70QKd0WNtL5cukdSVjdO5Pap7ZBAwjs+xdOun1OOMoz4WN5lCmLe
Received: from localhost ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.0/X.509/SHA1) via TCP6; 12 Apr 2016 20:17:02 -0000
Date: 12 Apr 2016 16:17:02 -0400
Message-ID: <alpine.OSX.2.11.1604121614250.2223@ary.lan>
From: "John R Levine" <johnl@taugh.com>
To: "Ted Lemon" <mellon@fugue.com>
Subject: Re: Concerns about Singapore and other places
In-Reply-To: <CAPt1N1nLWrVqGpPh+h=Ano6PJyw2ZRaroiAMgG4RDKTFV7rkpA@mail.gmail.com>
References: <alpine.OSX.2.01.1604100736080.45987@rabdullah.local> <20160410181958.58762.qmail@ary.lan> <CAMm+LwgE_oOJSCjgsMGTSMDV2-LsUzw1zW3-+N_VCtE14m26BA@mail.gmail.com> <CAPt1N1nLWrVqGpPh+h=Ano6PJyw2ZRaroiAMgG4RDKTFV7rkpA@mail.gmail.com>
User-Agent: Alpine 2.11 (OSX 23 2013-08-11)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/VBjAwH33fbqgmIpXqxbZPKaCDZI>
Cc: Phillip Hallam-Baker <phill@hallambaker.com>, IETF Discussion Mailing List <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: Tue, 12 Apr 2016 20:17:07 -0000

> The UK filter is an "opt out" filter, and I assume that we (the IETF) opted
> out. ...

This isn't the parental filter, this is the child porn filter, which I am 
fairly sure is mandatory, at last on consumer ISPs.

A few years ago they listed a Wikipedia page which had an image of an old 
rock record cover with a small nude girl behind a cracked pain of glass. 
They eventually backed down when people pointed out why that particular 
entry was silly, e.g., the record had been available in used record stores 
for decades.

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
Please consider the environment before reading this e-mail.


From nobody Tue Apr 12 13:32:21 2016
Return-Path: <brian.e.carpenter@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 9ADDD12D0FA for <ietf@ietfa.amsl.com>; Tue, 12 Apr 2016 13:32:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 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, 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 acEYSW1k-lGL for <ietf@ietfa.amsl.com>; Tue, 12 Apr 2016 13:32:18 -0700 (PDT)
Received: from mail-pf0-x229.google.com (mail-pf0-x229.google.com [IPv6:2607:f8b0:400e:c00::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 318C212D0DF for <ietf@ietf.org>; Tue, 12 Apr 2016 13:32:18 -0700 (PDT)
Received: by mail-pf0-x229.google.com with SMTP id e128so19949383pfe.3 for <ietf@ietf.org>; Tue, 12 Apr 2016 13:32:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=subject:to:references:from:organization:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=Hv7ylYf00vdOQ5rA9baJ9MpxobysiGGdCPDbQ7hzxSA=; b=scSeOLzx2xi/kHc/MhaujXknpis3Kt6FUQl18XACq/kWxkFXZRCdv8xv+2LpjHmY1l PoaKY1qNXQgOaGvYV7Wah8ZEGCEygq0xFLr0BJsmSVoM0q00x+eXofBFZY+KSCh+P8op UrxrWQI0ywSGnJ3hGjPZUvqwVnh0YdNjNiVmVuZSLY2mMR1a0niZjX3HViJXqHkPZ06K UhIf8V63YJF8xhcy1RNyy0/q83aVLMJ7u6WaMdt9EAv89iral3EnQbkVWw67PaBOIz0n 77h7g3/Njepqr1Bl90er+4kOsygZik8gpccfvT1A4X0eqbfa6XgVgm6Xjn4MSezekGiP wDTg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=Hv7ylYf00vdOQ5rA9baJ9MpxobysiGGdCPDbQ7hzxSA=; b=FueLsDWcdUAyY+37EJEVeXcXj/heh3oLHcSz2Lg52siMzfX9r4QmSR7oNCnS0KzIrN 4fC3fP8O6nNISo7CWeaiUg4YjV1kayCE5zkc3szzptXYsfEdc5q268x+3uJKPrkChUIk XueMiXeGbplcdZ+zfnZ3+M1jdr5H5nY2BJuqVdHoLIboDUcNfDOR/CeQhITWjvtnFn6q JB4045M8698OHNJMqO/XzTXLA24soRPB6Z+9jKnwesF/6SnZ/XofBsB6G11/1U69/hTn 1CwyViMoB+lx633GfmtPrb6ZHPDM29GG3FL0Ib4/iaKrPfrjRVgK9sO+oXTAiW8lfNS/ JCOg==
X-Gm-Message-State: AOPr4FWlaqFIZLvjgy7X8xYoiTrnxVQJz+jnv7Z5a0J8jwDjyzDzN3ME2NZ1kzHsWyuYPw==
X-Received: by 10.98.87.216 with SMTP id i85mr7440657pfj.61.1460493137769; Tue, 12 Apr 2016 13:32:17 -0700 (PDT)
Received: from ?IPv6:2406:e007:422f:1:28cc:dc4c:9703:6781? ([2406:e007:422f:1:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id c9sm45636952pfd.24.2016.04.12.13.32.14 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 12 Apr 2016 13:32:16 -0700 (PDT)
Subject: Re: Transparency of IAOC
To: SM <sm@resistor.net>, Dave Crocker <dcrocker@bbiw.net>, ietf@ietf.org
References: <6.2.5.6.2.20160412031201.0da034e8@elandnews.com> <6.2.5.6.2.20160412114424.0e7061b0@resistor.net>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <570D5B51.8090307@gmail.com>
Date: Wed, 13 Apr 2016 08:32:17 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2
MIME-Version: 1.0
In-Reply-To: <6.2.5.6.2.20160412114424.0e7061b0@resistor.net>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/GKsmvm2vogs5-AjunR0jQwJtwMo>
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: Tue, 12 Apr 2016 20:32:19 -0000

Hi SM,

> Is it appropriate to ask questions to the IAOC?  

Of course it is. But (compared to the IESG) the IAOC does deal with a
comparatively large fraction of issues that have confidential aspects -
budget negotiation, contract negotiations, staff issues, operation security,
and (with their Trustee hats on) legal issues. So there are going to be more
problems about community access to IAOC proceedings than for the IESG.

> I don't see people who have been part of the "leadership" doing that.  

Really not? Of course some of us who've actually been in the IAOC in
the past may not have quite so many questions, because we understand
the constraints.

> Maybe,
> it will be viewed as politically incorrect and it is not good for a person's IETF career.  In other words, it is a matter of
> perception.

I think someone who's been asking tricky questions of the IAOC would
be a very good candidate for Nomcom to consider for an IAOC seat.

    Brian


From nobody Tue Apr 12 13:34:21 2016
Return-Path: <mellon@fugue.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 69EC012D553 for <ietf@ietfa.amsl.com>; Tue, 12 Apr 2016 13:34:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.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 HXjFJ0pI5zT9 for <ietf@ietfa.amsl.com>; Tue, 12 Apr 2016 13:34:17 -0700 (PDT)
Received: from mail-lf0-x234.google.com (mail-lf0-x234.google.com [IPv6:2a00:1450:4010:c07::234]) (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 8585B12B044 for <ietf@ietf.org>; Tue, 12 Apr 2016 13:34:17 -0700 (PDT)
Received: by mail-lf0-x234.google.com with SMTP id j11so41804219lfb.1 for <ietf@ietf.org>; Tue, 12 Apr 2016 13:34:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=vuuG4JxzuTf1mo7c30avGcgzlEcLGyf0/Zuh9BSaMh8=; b=JvJ9vczj4xZyvgbcs7ryLgIqfkB5HIrNcRXJXwJIeH/g+y5vR9XEflIR8Sl8YCKuP4 P08yR5K0ITg3E6D9wAo2Xxovmyp52MVRZa0+9Jk3SxKk+/NiHcxepQ8Sk0uSCsJIBPNZ 54KMa8XtwbU6zJYotyQnBWnLhLOnaE/Q8YPFm8OIZZQMEFnAtFwhxaQN4TyksIhZ9Fel 7SsZXEh1F70GvFWkprclf8R4bMbBVk3RdkX+nJSYPFDv4gEmzQT2dBcuwc0juu/0JRMP bhqZppH6/xtxmRKIRiCDdQBG6jCR00GAzOVO7/CXq4wzssNK/ORP6WsJS+UqmdV7F4c9 MPyQ==
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=vuuG4JxzuTf1mo7c30avGcgzlEcLGyf0/Zuh9BSaMh8=; b=m81gxVqpXB6QqNvpyQH9QW7FX9lTOCIGqKEUm8TWyDCNGyIZXO2mR5FbRe8B29Vhjl rf2mT6ESWLnkvcJj8la/RSzCL40GB9wl9zepnhS44Rhslrm0aCqI6C3SxXt2ynF+0Y84 Dv+o1ba8gRv2QOrtd9QZADPIPMlDVNs6IG+8W17FNDz3IuSTJSvm0CseHJcJVzMHx/rU m7boRLnIYvVI1aEQzu4Fcjpsax8HMUwxhmx5mNCHVX1Zd5DjiIHz4rrgSXaFOwHedHXE SnBjUitSQjnkx7XaTYWPuAr2UuGDFlCz6WavbB0uiS+e2LN0LA0RdDHFSj+Di9kbRbyt gQig==
X-Gm-Message-State: AOPr4FWzIJJAV+njy4OUVQ/WxECijGYzalJeC0V/+hCsF04CkPfwr680Uogm52oZ72zRDCNcF0WK8qFwVU35ag==
X-Received: by 10.112.143.40 with SMTP id sb8mr2273310lbb.83.1460493255700; Tue, 12 Apr 2016 13:34:15 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.25.40.136 with HTTP; Tue, 12 Apr 2016 13:33:36 -0700 (PDT)
X-Originating-IP: [71.233.41.235]
In-Reply-To: <6.2.5.6.2.20160412114424.0e7061b0@resistor.net>
References: <6.2.5.6.2.20160412031201.0da034e8@elandnews.com> <6.2.5.6.2.20160412114424.0e7061b0@resistor.net>
From: Ted Lemon <mellon@fugue.com>
Date: Tue, 12 Apr 2016 16:33:36 -0400
Message-ID: <CAPt1N1kVbJdFH-XYpD7FREOooQOn3BYu20tvWSZFR7TrROMP4g@mail.gmail.com>
Subject: Re: Transparency of IAOC
To: SM <sm@resistor.net>
Content-Type: multipart/alternative; boundary=089e011832bab407ac05304f952e
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/nKoEVNO_0Ysun4xE8_YqGyKREaU>
Cc: Dave Crocker <dcrocker@bbiw.net>, ietf <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: Tue, 12 Apr 2016 20:34:19 -0000

--089e011832bab407ac05304f952e
Content-Type: text/plain; charset=UTF-8

On Tue, Apr 12, 2016 at 4:00 PM, SM <sm@resistor.net> wrote:

> Is it appropriate to ask questions to the IAOC?  I don't see people who
> have been part of the "leadership" doing that.  Maybe, it will be viewed as
> politically incorrect and it is not good for a person's IETF career.  In
> other words, it is a matter of perception.
>

I feel I can speak as an authority on this topic when I say that there is
zero chance that this is a problem.   If the IAOC do not always do what we
want, it is because (a) that is impossible, since there is no "we" that is
both in agreement and also representative of the wishes of all IETF
participants and (b) I know everybody on the IAOC and they just don't
behave as if they think complaining by IESG people is a problem.   Granted,
that's not necessarily always a good thing, but IESG people say plenty of
things to the IAOC about stuff like this, and I have never seen them act in
the slightest bit impatient about it.   Not only that, but we had a BoF in
BA about this topic.

Importantly, while the IESG is officially the host for IETFs, and therefore
obviously should have some say in this sort of thing, if we want more
transparency from the IAOC, it is we, the participants in the IETF, who are
responsible for asking for it, not the IESG, except to the extent that like
us, they are participants.

--089e011832bab407ac05304f952e
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On T=
ue, Apr 12, 2016 at 4:00 PM, SM <span dir=3D"ltr">&lt;<a href=3D"mailto:sm@=
resistor.net" target=3D"_blank">sm@resistor.net</a>&gt;</span> wrote:<br><b=
lockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px =
#ccc solid;padding-left:1ex">Is it appropriate to ask questions to the IAOC=
?=C2=A0 I don&#39;t see people who have been part of the &quot;leadership&q=
uot; doing that.=C2=A0 Maybe, it will be viewed as politically incorrect an=
d it is not good for a person&#39;s IETF career.=C2=A0 In other words, it i=
s a matter of perception.<br></blockquote><div><br></div><div>I feel I can =
speak as an authority on this topic when I say that there is zero chance th=
at this is a problem. =C2=A0 If the IAOC do not always do what we want, it =
is because (a) that is impossible, since there is no &quot;we&quot; that is=
 both in agreement and also representative of the wishes of all IETF partic=
ipants and (b) I know everybody on the IAOC and they just don&#39;t behave =
as if they think complaining by IESG people is a problem. =C2=A0 Granted, t=
hat&#39;s not necessarily always a good thing, but IESG people say plenty o=
f things to the IAOC about stuff like this, and I have never seen them act =
in the slightest bit impatient about it. =C2=A0 Not only that, but we had a=
 BoF in BA about this topic.</div><div><br></div><div>Importantly, while th=
e IESG is officially the host for IETFs, and therefore obviously should hav=
e some say in this sort of thing, if we want more transparency from the IAO=
C, it is we, the participants in the IETF, who are responsible for asking f=
or it, not the IESG, except to the extent that like us, they are participan=
ts.</div></div></div></div>

--089e011832bab407ac05304f952e--


From nobody Tue Apr 12 13:35:59 2016
Return-Path: <mellon@fugue.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 1429012D7E5 for <ietf@ietfa.amsl.com>; Tue, 12 Apr 2016 13:35:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.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 fOloY9yQsL92 for <ietf@ietfa.amsl.com>; Tue, 12 Apr 2016 13:35:56 -0700 (PDT)
Received: from mail-lf0-x231.google.com (mail-lf0-x231.google.com [IPv6:2a00:1450:4010:c07::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 28B2012D9A1 for <ietf@ietf.org>; Tue, 12 Apr 2016 13:35:51 -0700 (PDT)
Received: by mail-lf0-x231.google.com with SMTP id e190so42087931lfe.0 for <ietf@ietf.org>; Tue, 12 Apr 2016 13:35:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=b1j18z9lxvl7XAscNeDZSn0hLHtOaiYLQpha/nYw17o=; b=CIH7N86c1CFz41z5Qxd65qsJkufCjPrO9YneqU/rJ4Lpc2+o58G2sKIJWjdjPtEwGS L8jLaZzbCqKEz6Q5INRk2Scd6AjJi4kEezPZmeNAEWMNHzDju5NVY5wP6ksmxwQIRuoB ZxigU/N382sPBdQpCOd4DGVITDniRIUZrEC3FNjDDzSO/aXemdtYRe64/K6K4HejhbKU wGFEl6JFPiDOFnwSu4LVDubTXC9fZGchQZEvLJjsQfBpXl+l7HST8AiF2Yghk8noiEyH vK5IYKAXYkkHe3+bMi+UOBweEFWoj9taLYQTIefE0LoJADtNAscNkg5slAFdLX3hZLJz UPcw==
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=b1j18z9lxvl7XAscNeDZSn0hLHtOaiYLQpha/nYw17o=; b=hglwSOMMeDwDTqU/WrTIWzwEUh01msLVZZ71g6lTWXXmalOihqCENHL6aps9xWnVpW nPnG8V/kI19lsRS6LNhp5Ojb8RNJ5RLLmv8qYPKR5gMstz1fD61cDrYcZ6op5HEN1sar X9B21Fo3k81UF8APCUShLlKt/zwgY55tLMk4AtoeRHPLJJILtL+RwCi406AM8dQ24u5/ sl7PHBuTf5VbEWyOdvKYKaGKNoJJGMw76nX3Se+ynt854flweEh07+CMlmNUEYCKDfU7 nTf2mZkP7MuvaLAOjvAV4snY2IoiMULWdj5HrO5tUMpYe2LD4hr2qyO7NXmRlTQJWD5Z LVbw==
X-Gm-Message-State: AOPr4FVdg3sf2U3hsayiRQ9EDv7Td73rIdN50xOutvDHZUUcAESLDI3gWJspv7MKelp1fZvgF8pE60qL8Tf5uw==
X-Received: by 10.25.73.212 with SMTP id w203mr1992844lfa.22.1460493349409; Tue, 12 Apr 2016 13:35:49 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.25.40.136 with HTTP; Tue, 12 Apr 2016 13:35:09 -0700 (PDT)
X-Originating-IP: [71.233.41.235]
In-Reply-To: <570D5B51.8090307@gmail.com>
References: <6.2.5.6.2.20160412031201.0da034e8@elandnews.com> <6.2.5.6.2.20160412114424.0e7061b0@resistor.net> <570D5B51.8090307@gmail.com>
From: Ted Lemon <mellon@fugue.com>
Date: Tue, 12 Apr 2016 16:35:09 -0400
Message-ID: <CAPt1N1=CViQxgkZEGUY+0nvP0xyQJZHD8Ftecvu-rQ4oNeFgxA@mail.gmail.com>
Subject: Re: Transparency of IAOC
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Content-Type: multipart/alternative; boundary=001a114b159249ebcb05304f9b25
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/NCNCFr6g0dly8lIQAvvPFDJD1tg>
Cc: SM <sm@resistor.net>, Dave Crocker <dcrocker@bbiw.net>, ietf <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: Tue, 12 Apr 2016 20:35:58 -0000

--001a114b159249ebcb05304f9b25
Content-Type: text/plain; charset=UTF-8

On Tue, Apr 12, 2016 at 4:32 PM, Brian E Carpenter <
brian.e.carpenter@gmail.com> wrote:

> > Maybe,
> > it will be viewed as politically incorrect and it is not good for a
> person's IETF career.  In other words, it is a matter of
> > perception.
>
> I think someone who's been asking tricky questions of the IAOC would
> be a very good candidate for Nomcom to consider for an IAOC seat


So, to paraphrase, "yes."

--001a114b159249ebcb05304f9b25
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On T=
ue, Apr 12, 2016 at 4:32 PM, Brian E Carpenter <span dir=3D"ltr">&lt;<a hre=
f=3D"mailto:brian.e.carpenter@gmail.com" target=3D"_blank">brian.e.carpente=
r@gmail.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" styl=
e=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span c=
lass=3D"">&gt; Maybe,<br>
&gt; it will be viewed as politically incorrect and it is not good for a pe=
rson&#39;s IETF career.=C2=A0 In other words, it is a matter of<br>
&gt; perception.<br>
<br>
</span>I think someone who&#39;s been asking tricky questions of the IAOC w=
ould<br>
be a very good candidate for Nomcom to consider for an IAOC seat</blockquot=
e><div><br></div><div>So, to paraphrase, &quot;yes.&quot;</div></div></div>=
</div>

--001a114b159249ebcb05304f9b25--


From nobody Tue Apr 12 13:51:37 2016
Return-Path: <spencerdawkins.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 743BA12DDE6 for <ietf@ietfa.amsl.com>; Tue, 12 Apr 2016 13:51:35 -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 bymwwB10I5tB for <ietf@ietfa.amsl.com>; Tue, 12 Apr 2016 13:51:33 -0700 (PDT)
Received: from mail-yw0-x229.google.com (mail-yw0-x229.google.com [IPv6:2607:f8b0:4002:c05::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 510E912DE04 for <ietf@ietf.org>; Tue, 12 Apr 2016 13:51:33 -0700 (PDT)
Received: by mail-yw0-x229.google.com with SMTP id d68so41603398ywe.1 for <ietf@ietf.org>; Tue, 12 Apr 2016 13:51:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=sVcc/kaT0pspoUIUPiQpqN0jrXXYXm4mOoxJNpfD1Rw=; b=WpBqCEevzt7UJnwAsOQUwJkHNyN57zzW/e0bbIDZQ0GDE8ONV079jL49jCF1IWa8BX u8RZMUnvqRNXLQBVkFVyiyVSyW3PEsI8i0EoqV4h1ieoUm+Pnog/E4FWLb2Ifw4GrUn0 TLB3Xzghp2CGipj8dTFhuaeYxVc0UXUsY3nGTAU4jsAI1GadFDzJBzlwoBao6LHklxlu W1mM2bUNOhXt7SnUeeFg8olM6zIbsmpfo9hDPum6ZRGiyrO0F98459i2JOScxSAZYLkn IOmLdheb9ZPvDLBDHFSHDT8mDQe2NulOo9NUa7TlbIoU7jLUFARSNMOP4re4l7vbf+iC j0jg==
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:date :message-id:subject:from:to:cc; bh=sVcc/kaT0pspoUIUPiQpqN0jrXXYXm4mOoxJNpfD1Rw=; b=afP+7gHbawT8kueqMc/K5Hzr1sqKaKtMv8wtbJ3LcXWAN4Bn/EvJyzsD8lM0Vnx6of Rjbgs8+bxbwS6caE55BRmmH2H+IPEzYzHkjQ2YHKoAo83o3aYZs0JdaULeXzKSMYLbnK KAWIQKuYo93PdSq0ufec1oBvDBQzIw2QcWfOHWXhSxN8IP0YP5PC4B6EijaCpto20hex 81mJI7SjqtD3eMlT4faP9H4LgI46atfS5K1Wv5JosXvo+YbMSuYXChqjwyCyjH1/X/HV +g2uLtvveMNBs+vAc2dqBuj8o4bL2HjboDEdYpWRvUBCeNFu6ZONlkH1i2fkg15w3kHq Q/Pg==
X-Gm-Message-State: AOPr4FVpzn09sO9i5SFYqWdYmhejaCCnCWYK4nGiBGJFvD8TIGQX2q9xN5by3V3Ql7Tu7wAAlLEe9/xsUnnLZw==
MIME-Version: 1.0
X-Received: by 10.37.74.193 with SMTP id x184mr2712022yba.76.1460494292587; Tue, 12 Apr 2016 13:51:32 -0700 (PDT)
Received: by 10.37.207.211 with HTTP; Tue, 12 Apr 2016 13:51:32 -0700 (PDT)
In-Reply-To: <570D5B51.8090307@gmail.com>
References: <6.2.5.6.2.20160412031201.0da034e8@elandnews.com> <6.2.5.6.2.20160412114424.0e7061b0@resistor.net> <570D5B51.8090307@gmail.com>
Date: Tue, 12 Apr 2016 15:51:32 -0500
Message-ID: <CAKKJt-c2KR4dfLSmuUSpR9_jxmDX3jGBidUHzxPWOa3dWq=MZw@mail.gmail.com>
Subject: Re: Transparency of IAOC
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Content-Type: multipart/alternative; boundary=001a113e6400819cda05304fd31e
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/vIzmx8QLotxDo3h-oIALuaLLZ44>
Cc: SM <sm@resistor.net>, Dave Crocker <dcrocker@bbiw.net>, "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: Tue, 12 Apr 2016 20:51:35 -0000

--001a113e6400819cda05304fd31e
Content-Type: text/plain; charset=UTF-8

On this one ...

On Tue, Apr 12, 2016 at 3:32 PM, Brian E Carpenter <
brian.e.carpenter@gmail.com> wrote:

> Hi SM,
>
> > Is it appropriate to ask questions to the IAOC?
>
> Of course it is. But (compared to the IESG) the IAOC does deal with a
> comparatively large fraction of issues that have confidential aspects -
> budget negotiation, contract negotiations, staff issues, operation
> security,
> and (with their Trustee hats on) legal issues. So there are going to be
> more
> problems about community access to IAOC proceedings than for the IESG.
>
> > I don't see people who have been part of the "leadership" doing that.
>
> Really not? Of course some of us who've actually been in the IAOC in
> the past may not have quite so many questions, because we understand
> the constraints.


SM, if you're talking about people in "leadership" (is that what we are?)
asking questions of the IAOC on the IETF mailing list, you may very well be
right.

But I do drop notes to the IAOC directly, either to the IAD or to the
overall IAOC, and I don't know how anyone in the broader community would
know that I've done that.

I suspect others do, as well.

Spencer

--001a113e6400819cda05304fd31e
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">On this one ...<div class=3D"gmail_extra"><br><div class=
=3D"gmail_quote">On Tue, Apr 12, 2016 at 3:32 PM, Brian E Carpenter <span d=
ir=3D"ltr">&lt;<a href=3D"mailto:brian.e.carpenter@gmail.com" target=3D"_bl=
ank">brian.e.carpenter@gmail.com</a>&gt;</span> wrote:<br><blockquote class=
=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padd=
ing-left:1ex">Hi SM,<br>
<span class=3D""><br>
&gt; Is it appropriate to ask questions to the IAOC?<br>
<br>
</span>Of course it is. But (compared to the IESG) the IAOC does deal with =
a<br>
comparatively large fraction of issues that have confidential aspects -<br>
budget negotiation, contract negotiations, staff issues, operation security=
,<br>
and (with their Trustee hats on) legal issues. So there are going to be mor=
e<br>
problems about community access to IAOC proceedings than for the IESG.<br>
<span class=3D""><br>
&gt; I don&#39;t see people who have been part of the &quot;leadership&quot=
; doing that.<br>
<br>
</span>Really not? Of course some of us who&#39;ve actually been in the IAO=
C in<br>
the past may not have quite so many questions, because we understand<br>
the constraints.</blockquote><div><br></div><div>SM, if you&#39;re talking =
about people in &quot;leadership&quot; (is that what we are?) asking questi=
ons of the IAOC on the IETF mailing list, you may very well be right.</div>=
<div><br></div><div>But I do drop notes to the IAOC directly, either to the=
 IAD or to the overall IAOC, and I don&#39;t know how anyone in the broader=
 community would know that I&#39;ve done that.</div><div><br></div><div>I s=
uspect others do, as well.</div><div><br></div><div>Spencer=C2=A0</div></di=
v></div></div>

--001a113e6400819cda05304fd31e--


From nobody Tue Apr 12 14:10:02 2016
Return-Path: <harald@alvestrand.no>
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 6F4DC12E4F0 for <ietf@ietfa.amsl.com>; Tue, 12 Apr 2016 14:10:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.896
X-Spam-Level: 
X-Spam-Status: No, score=-2.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.996] 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 IlQ70EQL4_sJ for <ietf@ietfa.amsl.com>; Tue, 12 Apr 2016 14:09:56 -0700 (PDT)
Received: from mork.alvestrand.no (mork.alvestrand.no [IPv6:2001:700:1:2::117]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9F6C212E1E6 for <ietf@ietf.org>; Tue, 12 Apr 2016 14:09:56 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mork.alvestrand.no (Postfix) with ESMTP id CB03B7C7CED for <ietf@ietf.org>; Tue, 12 Apr 2016 23:09:54 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at alvestrand.no
Received: from mork.alvestrand.no ([127.0.0.1]) by localhost (mork.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Gus0G1xRkD_V for <ietf@ietf.org>; Tue, 12 Apr 2016 23:09:50 +0200 (CEST)
Received: from [IPv6:2001:470:de0a:1:34fd:aec1:692d:e316] (unknown [IPv6:2001:470:de0a:1:34fd:aec1:692d:e316]) by mork.alvestrand.no (Postfix) with ESMTPSA id 69EF87C7CEC for <ietf@ietf.org>; Tue, 12 Apr 2016 23:09:50 +0200 (CEST)
Subject: UK blacklist (Re: Concerns about Singapore and other places)
To: ietf@ietf.org
References: <alpine.OSX.2.01.1604100736080.45987@rabdullah.local> <20160410181958.58762.qmail@ary.lan> <CAMm+LwgE_oOJSCjgsMGTSMDV2-LsUzw1zW3-+N_VCtE14m26BA@mail.gmail.com> <CAPt1N1nLWrVqGpPh+h=Ano6PJyw2ZRaroiAMgG4RDKTFV7rkpA@mail.gmail.com>
From: Harald Alvestrand <harald@alvestrand.no>
Message-ID: <570D641D.6070509@alvestrand.no>
Date: Tue, 12 Apr 2016 23:09:49 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0
MIME-Version: 1.0
In-Reply-To: <CAPt1N1nLWrVqGpPh+h=Ano6PJyw2ZRaroiAMgG4RDKTFV7rkpA@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/5AQ1S3q80gfLsMZwtqMk6ZamBw4>
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: Tue, 12 Apr 2016 21:10:01 -0000

Den 12. april 2016 18:52, skrev Ted Lemon:
> The UK filter is an "opt out" filter, and I assume that we (the IETF)
> opted out.   Even the "opt out" blocking is voluntary at present--an ISP
> is not required by law to have a filter, but in practice the big ones do.


The particular case that made the blacklist famous in at least some
fora, and exposed quite a bit on how it worked:

https://en.wikipedia.org/wiki/Internet_Watch_Foundation_and_Wikipedia

"the action also had some indirect effects on Wikipedia, namely
temporarily preventing all editors using said ISPs in the UK from
contributing to any page of the encyclopaedia, and preventing anonymous
edits from these ISPs while the URL remained on the blacklist. This was
described by the IWF as unintended "collateral damage".[7] This was due
to the proxies used to access Wikipedia, as Wikipedia implements a
blocking policy whereby contributors can be blocked if they vandalise
the encyclopaedia. Therefore, all vandalism coming from one ISP would be
directed through one proxyâ€”hence one IPâ€”and all of the ISP's customers
using that proxy would be barred from editing."

> 
> On Tue, Apr 12, 2016 at 12:24 PM, Phillip Hallam-Baker
> <phill@hallambaker.com <mailto:phill@hallambaker.com>> wrote:
> 
>     On Sun, Apr 10, 2016 at 3:19 PM, John Levine <johnl@taugh.com
>     <mailto:johnl@taugh.com>> wrote:
>     >>The IETF has a meeting network requirements document that specifies a
>     >>number of parameters which includes no blocking.
>     >
>     > In London in 2014, do you know whether we were behind the national
>     > child porn filters?
>     >
>     > R's,
>     > John
> 
>     I am not sure that they actually filter.
> 
>     I think it rather more likely that if you were to surf to
>     kiddieporn.com <http://kiddieporn.com> from the Hilton Metropole,
>     that you would find Mr Plod
>     knocking on your hotel room door 15 minutes later. That being the
>     driving time from New Scotland Yard.
> 
> 


From nobody Tue Apr 12 14:27:49 2016
Return-Path: <christopher.morrow@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 3236412EA6B for <ietf@ietfa.amsl.com>; Tue, 12 Apr 2016 14:27:47 -0700 (PDT)
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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 9nf99jRMOaqI for <ietf@ietfa.amsl.com>; Tue, 12 Apr 2016 14:27:45 -0700 (PDT)
Received: from mail-yw0-x22c.google.com (mail-yw0-x22c.google.com [IPv6:2607:f8b0:4002:c05::22c]) (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 789EB12EA65 for <ietf@ietf.org>; Tue, 12 Apr 2016 14:27:45 -0700 (PDT)
Received: by mail-yw0-x22c.google.com with SMTP id o66so42766701ywc.3 for <ietf@ietf.org>; Tue, 12 Apr 2016 14:27:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc; bh=tePYBbqUbWoICP7fY4g5YzqAqfcdLxmQfuQ0CmXu9SU=; b=lbumQcFeJu3szbDi8xsPNvZdfDQAqc3eVAn1MA2Hp8RW631tgSPOKKZ7JWsLCG6xtd eO2+uTLMrUBqs8L8PzEAu/ikZaFCTlE203BPzLrhw3ctSxogqYNNkyACjsRU3sGDf8Dw JAPAbNoRxjAzTdIBvu0IktuaV4BQiQsG0FReAFl5xUlPkojgkSaNKhvAiQzoy61302fB TYDUUA39mCREbsoZOVDQ2zR9orJEAwR2FnpFcnyEZIEVzYh0wrQwzHtq1wyiXvGDmdcK BygSXPPg89F50rQBUfujNdLdsUMVA15+aKybM5hbApBuEw8zErYzWfN0Ad5VJqv0iDHU bE+Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:date :message-id:subject:from:to:cc; bh=tePYBbqUbWoICP7fY4g5YzqAqfcdLxmQfuQ0CmXu9SU=; b=TH7bn+QhHj+whyMyQtoqXHeX1ZDXAGa50ZArYf0GR7BVkPzsTl2KdUXb+Kfhiw7fPe dp3lKUPwKfi7g0TA/fyrskMNBixuJrLCyyOAtxeeJT5dLH1A1YIWuAyPEEmD4FnWIzAN ytNSOdZ0FyMu4DBre2lGQU8ZOXLfEUA4agf1m0H9O0Rsg2ZqSi0DengzjsdqFqRvWWp5 jJzHD0SS1mB0mLJYPFvv1isEdQNWgSLiadDVsT+P0BvgCOrPDKx0HbIFA1a8+Wun87Pl bF4+qjUKa0jGoBzNfztiZMgx3jb79ZOjVzVX6GWCriwsuMicz6BAxpGhF5/9RqClMRIK 4QKw==
X-Gm-Message-State: AOPr4FWZauE4cHItpTRsk5zo1GZBj3g1dZKcrYYbV8Fc50W4rGGTB1l89SDzyYGO+SyBV04JOe5x4Wyz3FWvnA==
MIME-Version: 1.0
X-Received: by 10.129.85.196 with SMTP id j187mr2914956ywb.177.1460496464623;  Tue, 12 Apr 2016 14:27:44 -0700 (PDT)
Sender: christopher.morrow@gmail.com
Received: by 10.13.209.198 with HTTP; Tue, 12 Apr 2016 14:27:44 -0700 (PDT)
In-Reply-To: <570D641D.6070509@alvestrand.no>
References: <alpine.OSX.2.01.1604100736080.45987@rabdullah.local> <20160410181958.58762.qmail@ary.lan> <CAMm+LwgE_oOJSCjgsMGTSMDV2-LsUzw1zW3-+N_VCtE14m26BA@mail.gmail.com> <CAPt1N1nLWrVqGpPh+h=Ano6PJyw2ZRaroiAMgG4RDKTFV7rkpA@mail.gmail.com> <570D641D.6070509@alvestrand.no>
Date: Tue, 12 Apr 2016 17:27:44 -0400
X-Google-Sender-Auth: rvdZW2jglduW1XqwzjHRkLd_dOU
Message-ID: <CAL9jLaZdiFV6g87xRmM-M=UobKbGMF+R9ZUP5ZBLTPLCq8mbfA@mail.gmail.com>
Subject: Re: UK blacklist (Re: Concerns about Singapore and other places)
From: Christopher Morrow <morrowc.lists@gmail.com>
To: Harald Alvestrand <harald@alvestrand.no>
Content-Type: multipart/alternative; boundary=001a113f1b0ef8409905305054d6
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/CSsJBFWQTV0F_9C5V8sgMZndo0s>
Cc: ietf <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: Tue, 12 Apr 2016 21:27:47 -0000

--001a113f1b0ef8409905305054d6
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Tue, Apr 12, 2016 at 5:09 PM, Harald Alvestrand <harald@alvestrand.no>
wrote:

> Den 12. april 2016 18:52, skrev Ted Lemon:
> > The UK filter is an "opt out" filter, and I assume that we (the IETF)
> > opted out.   Even the "opt out" blocking is voluntary at present--an IS=
P
> > is not required by law to have a filter, but in practice the big ones d=
o.
>
>
> The particular case that made the blacklist famous in at least some
> fora, and exposed quite a bit on how it worked:
>
> https://en.wikipedia.org/wiki/Internet_Watch_Foundation_and_Wikipedia
>
> "the action also had some indirect effects on Wikipedia, namely
> temporarily preventing all editors using said ISPs in the UK from
>
>
=E2=80=8Bthis =E2=80=8B

=E2=80=8Bis PROBABLY also for 'consumer isp connections' mostly and not 'bu=
siness
isp' links, which the IETF uses at meetings. I suspect, anyway.. else you
may filter on the dsl/ftth/dial network AND re-filter on the backbone-isp
network and again if there's a third tier...

so the IETF simply sidestepped by pretending to be an 'enterprise' network.=
=E2=80=8B

--001a113f1b0ef8409905305054d6
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-size:small"><br=
></div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Tue, Ap=
r 12, 2016 at 5:09 PM, Harald Alvestrand <span dir=3D"ltr">&lt;<a href=3D"m=
ailto:harald@alvestrand.no" target=3D"_blank">harald@alvestrand.no</a>&gt;<=
/span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8=
ex;border-left:1px #ccc solid;padding-left:1ex">Den 12. april 2016 18:52, s=
krev Ted Lemon:<br>
&gt; The UK filter is an &quot;opt out&quot; filter, and I assume that we (=
the IETF)<br>
&gt; opted out.=C2=A0 =C2=A0Even the &quot;opt out&quot; blocking is volunt=
ary at present--an ISP<br>
&gt; is not required by law to have a filter, but in practice the big ones =
do.<br>
<br>
<br>
The particular case that made the blacklist famous in at least some<br>
fora, and exposed quite a bit on how it worked:<br>
<br>
<a href=3D"https://en.wikipedia.org/wiki/Internet_Watch_Foundation_and_Wiki=
pedia" rel=3D"noreferrer" target=3D"_blank">https://en.wikipedia.org/wiki/I=
nternet_Watch_Foundation_and_Wikipedia</a><br>
<br>
&quot;the action also had some indirect effects on Wikipedia, namely<br>
temporarily preventing all editors using said ISPs in the UK from<br><br></=
blockquote><div><div class=3D"gmail_default" style=3D"font-size:small;displ=
ay:inline"><br></div></div><div><div class=3D"gmail_default" style=3D"font-=
size:small;display:inline">=E2=80=8Bthis =E2=80=8B</div>=C2=A0<div class=3D=
"gmail_default" style=3D"font-size:small;display:inline">=E2=80=8Bis PROBAB=
LY also for &#39;consumer isp connections&#39; mostly and not &#39;business=
 isp&#39; links, which the IETF uses at meetings. I suspect, anyway.. else =
you may filter on the dsl/ftth/dial network AND re-filter on the backbone-i=
sp network and again if there&#39;s a third tier...</div></div><div><div cl=
ass=3D"gmail_default" style=3D"font-size:small;display:inline"><br></div></=
div><div><div class=3D"gmail_default" style=3D"font-size:small;display:inli=
ne">so the IETF simply sidestepped by pretending to be an &#39;enterprise&#=
39; network.=E2=80=8B</div></div></div><br></div></div>

--001a113f1b0ef8409905305054d6--


From nobody Tue Apr 12 14:34:33 2016
Return-Path: <stephen.farrell@cs.tcd.ie>
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 7BFD412D6BB for <ietf@ietfa.amsl.com>; Tue, 12 Apr 2016 14:34:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.297
X-Spam-Level: 
X-Spam-Status: No, score=-5.297 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.996, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cs.tcd.ie
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 23vYA1QjFzeZ for <ietf@ietfa.amsl.com>; Tue, 12 Apr 2016 14:34:29 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 86D0F12D764 for <ietf@ietf.org>; Tue, 12 Apr 2016 14:34:29 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id F29FABE25; Tue, 12 Apr 2016 22:34:26 +0100 (IST)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 67LpDRiN7yF0; Tue, 12 Apr 2016 22:34:25 +0100 (IST)
Received: from [10.87.49.100] (unknown [86.42.21.187]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id DB37EBE2F; Tue, 12 Apr 2016 22:34:24 +0100 (IST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; s=mail; t=1460496865; bh=GkmcUfiU+uYxciEwZwiqYMysuz89K0E3xd9TBvatWQ0=; h=Subject:To:References:From:Date:In-Reply-To:From; b=pKGYae2mX9y9y2aVuV5tqY7KL+rFKlQLRPBGKn6Aa2k7xtOrccUmeus9tRakv1aje MmGT5u+wK8e1jI95LQDGzN4ey1WYzd4xml/J6SjEsn34Exp9Ihb/Q9/ORCrwD0clCE odpeBN+DDkbxnFSWi8ZvKgt42lN1yDUPOxOmn3RY=
Subject: Re: Transparency of IAOC
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, SM <sm@resistor.net>, Dave Crocker <dcrocker@bbiw.net>, ietf@ietf.org
References: <6.2.5.6.2.20160412031201.0da034e8@elandnews.com> <6.2.5.6.2.20160412114424.0e7061b0@resistor.net> <570D5B51.8090307@gmail.com>
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Openpgp: id=D66EA7906F0B897FB2E97D582F3C8736805F8DA2; url=
Message-ID: <570D69E0.30209@cs.tcd.ie>
Date: Tue, 12 Apr 2016 22:34:24 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0
MIME-Version: 1.0
In-Reply-To: <570D5B51.8090307@gmail.com>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha-256; boundary="------------ms040600010703070102050206"
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/C4Fm55jKeC_7UMI1htIXN8-rZkE>
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: Tue, 12 Apr 2016 21:34:32 -0000

This is a cryptographically signed message in MIME format.

--------------ms040600010703070102050206
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


Hi Brian,

On 12/04/16 21:32, Brian E Carpenter wrote:
> Of course it is. But (compared to the IESG) the IAOC does deal with
> a comparatively large fraction of issues that have confidential
> aspects - budget negotiation, contract negotiations, staff issues,
> operation security, and (with their Trustee hats on) legal issues. So
> there are going to be more problems about community access to IAOC
> proceedings than for the IESG.

What I'm wondering is if, given the above, anyone has done an
analysis of what the IAOC really needs to keep confidential and
what does not need to be confidential?

For example, recent events have fairly conclusively shown that
the "cities being considered" data which is related to "contract
negotiation" really ought not be confidential, at least in some
aggregated form. If you go back some years, the IETF meeting
hotel was also a not-so-well-kept secret until bookings opened,
and when we changed that the sky did not fall. So that's another
example. And if say the vmeet mailing list had been the place
where it was decided that IETF-95 remote attendees would have to
register, then we might have avoided that fuss. I can't see how
making that decision on that public list would have hurt anything
even though the fine meetecho support overall nvolves quite a few
of the issues related to confidentiality you list above.

I don't know if the IAOC has analysed such things more generally.
But I hope it does do that once it's sorted out what to do about
IETF-100. I suspect that to date, the IAOC has been treating too
much data as confidential when that's not really needed. I figure
ending up in that state is quite understandable, but is not in the
end a good plan.

And I don't believe we've actually heard the IAOC say that they
do think such a general exercise is or is not worthwhile. I do
think that some such statement now that the IAOC will consider a
switch to a default-open posture would be very very useful and
has not yet been made. (*)

Cheers,
S.

(*) Leslie's mail [1] only referred to reviewing meeting planning,
but not e.g. to any broader re-consideration which is what I'm
arguing would be better.

[1] https://www.ietf.org/mail-archive/web/ietf/current/msg97545.html




--------------ms040600010703070102050206
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIAGCSqGSIb3DQEHAqCAMIACAQExDzANBglghkgBZQMEAgEFADCABgkqhkiG9w0BBwEAAKCC
CvIwggUIMIID8KADAgECAhBPzaE7pzYviUJyhmHTFBdnMA0GCSqGSIb3DQEBCwUAMHUxCzAJ
BgNVBAYTAklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSkwJwYDVQQLEyBTdGFydENvbSBD
ZXJ0aWZpY2F0aW9uIEF1dGhvcml0eTEjMCEGA1UEAxMaU3RhcnRDb20gQ2xhc3MgMSBDbGll
bnQgQ0EwHhcNMTYwMjA5MDkyODE1WhcNMTcwMjA5MDkyODE1WjBOMSIwIAYDVQQDDBlzdGVw
aGVuLmZhcnJlbGxAY3MudGNkLmllMSgwJgYJKoZIhvcNAQkBFhlzdGVwaGVuLmZhcnJlbGxA
Y3MudGNkLmllMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAtuC0rYze/2JinSra
C9F2RjGdQZjNALLcW9C3WKTwYII3wBslobmHuPEYE5JaGItmzuKnAW619R1rD/kfoNWC19N3
rBZ6UX9Cmb9D9exCwYIwVuSwjrCQWGxgCtNQTrwKzCCpI790GRiMTvxvO7UmzmBrCaBLiZW5
R0fBjK5Yn6hUhAzGBkNbkIEL28cLJqH0yVz7Kl92OlzrQqTPEts5m6cDnNdY/ADfeAX18c1r
dxZqcAxhLotrCqgsVA4ilbQDMMXGTLlB5TP35HeWZuGBU7xu003rLcFLdOkD8xvpJoYZy9Kt
3oABXPS5yqtMK+XCNdqmMn+4mOtLwQSMmPCSiQIDAQABo4IBuTCCAbUwCwYDVR0PBAQDAgSw
MB0GA1UdJQQWMBQGCCsGAQUFBwMCBggrBgEFBQcDBDAJBgNVHRMEAjAAMB0GA1UdDgQWBBQJ
QhvwQ5Fl372Z6xqo6fdn8XejTTAfBgNVHSMEGDAWgBQkgWw5Yb5JD4+3G0YrySi1J0htaDBv
BggrBgEFBQcBAQRjMGEwJAYIKwYBBQUHMAGGGGh0dHA6Ly9vY3NwLnN0YXJ0c3NsLmNvbTA5
BggrBgEFBQcwAoYtaHR0cDovL2FpYS5zdGFydHNzbC5jb20vY2VydHMvc2NhLmNsaWVudDEu
Y3J0MDgGA1UdHwQxMC8wLaAroCmGJ2h0dHA6Ly9jcmwuc3RhcnRzc2wuY29tL3NjYS1jbGll
bnQxLmNybDAkBgNVHREEHTAbgRlzdGVwaGVuLmZhcnJlbGxAY3MudGNkLmllMCMGA1UdEgQc
MBqGGGh0dHA6Ly93d3cuc3RhcnRzc2wuY29tLzBGBgNVHSAEPzA9MDsGCysGAQQBgbU3AQIE
MCwwKgYIKwYBBQUHAgEWHmh0dHA6Ly93d3cuc3RhcnRzc2wuY29tL3BvbGljeTANBgkqhkiG
9w0BAQsFAAOCAQEArzrSv2C8PlBBmGuiGrzm2Wma46/KHtXmZYS0bsd43pM66Pc/MsqPE0HD
C1GzMFfwB6BfkJn8ijNSIhlgj898WzjvnpM/SO8KStjlB8719ig/xKISrOl5mX55XbFlQtX9
U6MrqRgbDIATxhD9IDr+ryvovDzChqgQj7mt2jYr4mdlRjsjod3H1VY6XglRmaaNGZfsCARM
aE/TU5SXIiqauwt5KxNGYAY67QkOBs7O1FkSXpTk7+1MmzJMF4nP8QQ5n8vhVNseF+/Wm7ai
9mtnrkLbaznMsy/ULo/C2yuLUWTbZZbf4EKNmVdme6tUDgYkFjAFOblfA7W1fSPiQGagYzCC
BeIwggPKoAMCAQICEGunin0K14jWUQr5WeTntOEwDQYJKoZIhvcNAQELBQAwfTELMAkGA1UE
BhMCSUwxFjAUBgNVBAoTDVN0YXJ0Q29tIEx0ZC4xKzApBgNVBAsTIlNlY3VyZSBEaWdpdGFs
IENlcnRpZmljYXRlIFNpZ25pbmcxKTAnBgNVBAMTIFN0YXJ0Q29tIENlcnRpZmljYXRpb24g
QXV0aG9yaXR5MB4XDTE1MTIxNjAxMDAwNVoXDTMwMTIxNjAxMDAwNVowdTELMAkGA1UEBhMC
SUwxFjAUBgNVBAoTDVN0YXJ0Q29tIEx0ZC4xKTAnBgNVBAsTIFN0YXJ0Q29tIENlcnRpZmlj
YXRpb24gQXV0aG9yaXR5MSMwIQYDVQQDExpTdGFydENvbSBDbGFzcyAxIENsaWVudCBDQTCC
ASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAL192vfDon2D9luC/dtbX64eG3XAtRmv
mCSsu1d52DXsCR58zJQbCtB2/A5uFqNxWacpXGGtTCRk9dEDBlmixEd8QiLkUfvHpJX/xKnm
VkS6Iye8wUbYzMsDzgnpazlPg19dnSqfhM+Cevdfa89VLnUztRr2cgmCfyO9Otrh7LJDPG+4
D8ZnAqDtVB8MKYJL6QgKyVhhaBc4y3bGWxKyXEtx7QIZZGxPwSkzK3WIN+VKNdkiwTubW5PI
dopmykwvIjLPqbJK7yPwFZYekKE015OsW6FV+s4DIM8UlVS8pkIsoGGJtMuWjLL4tq2hYQuu
N0jhrxK1ljz50hH23gA9cbMCAwEAAaOCAWQwggFgMA4GA1UdDwEB/wQEAwIBBjAdBgNVHSUE
FjAUBggrBgEFBQcDAgYIKwYBBQUHAwQwEgYDVR0TAQH/BAgwBgEB/wIBADAyBgNVHR8EKzAp
MCegJaAjhiFodHRwOi8vY3JsLnN0YXJ0c3NsLmNvbS9zZnNjYS5jcmwwZgYIKwYBBQUHAQEE
WjBYMCQGCCsGAQUFBzABhhhodHRwOi8vb2NzcC5zdGFydHNzbC5jb20wMAYIKwYBBQUHMAKG
JGh0dHA6Ly9haWEuc3RhcnRzc2wuY29tL2NlcnRzL2NhLmNydDAdBgNVHQ4EFgQUJIFsOWG+
SQ+PtxtGK8kotSdIbWgwHwYDVR0jBBgwFoAUTgvvGqRAW6UXaYcwyjRoQ9BBrvIwPwYDVR0g
BDgwNjA0BgRVHSAAMCwwKgYIKwYBBQUHAgEWHmh0dHA6Ly93d3cuc3RhcnRzc2wuY29tL3Bv
bGljeTANBgkqhkiG9w0BAQsFAAOCAgEAi+P3h+wBi4StDwECW5zhIycjBL008HACblIf26HY
0JdOruKbrWDsXUsiI0j/7Crft9S5oxvPiDtVqspBOB/y5uzSns1lZwh7sG96bYBZpcGzGxpF
NjDmQbcM3yl3WFIRS4WhNrsOY14V7y2IrUGsvetsD+bjyOngCIVeC/GmsmtbuLOzJ606tEc9
uRbhjTu/b0x2Fo+/e7UkQvKzNeo7OMhijixaULyINBfCBJb+e29bLafgu6JqjOUJ9eXXj20p
6q/CW+uVrZiSW57+q5an2P2i7hP85jQJcy5j4HzA0rSiF3YPhKGAWUxKPMAVGgcYoXzWydOv
Z3UDsTDTagXpRDIKQLZo02wrlxY6iMFqvlzsemVf1odhQJmi7Eh5TbxI40kDGcBOBHhwnaOu
mZhLP+SWJQnjpLpSlUOj95uf1zo9oz9e0NgIJoz/tdfrBzez76xtDsK0KfUDHt1/q59BvDI7
RX6gVr0fQoCyMczNzCTcRXYHY0tq2J0oT+bsb6sH2b4WVWAiJKnSYaWDjdA70qHX4mq9MIjO
/ZskmSY8wtAk24orAc0vwXgYanqNsBX5Yv4sN4Z9VyrwMdLcusP7HJgRdAGKpkR2I9U4zEsN
JQJewM7S4Jalo1DyPrLpL2nTET8ZrSl5Utp1UeGp/2deoprGevfnxWB+vHNQiu85o6MxggPM
MIIDyAIBATCBiTB1MQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRDb20gTHRkLjEpMCcG
A1UECxMgU3RhcnRDb20gQ2VydGlmaWNhdGlvbiBBdXRob3JpdHkxIzAhBgNVBAMTGlN0YXJ0
Q29tIENsYXNzIDEgQ2xpZW50IENBAhBPzaE7pzYviUJyhmHTFBdnMA0GCWCGSAFlAwQCAQUA
oIICEzAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0xNjA0MTIy
MTM0MjRaMC8GCSqGSIb3DQEJBDEiBCD9gg1W7i0SEmkNc1Orihq0UPpNaU84mVFa51zbrlol
sTBsBgkqhkiG9w0BCQ8xXzBdMAsGCWCGSAFlAwQBKjALBglghkgBZQMEAQIwCgYIKoZIhvcN
AwcwDgYIKoZIhvcNAwICAgCAMA0GCCqGSIb3DQMCAgFAMAcGBSsOAwIHMA0GCCqGSIb3DQMC
AgEoMIGaBgkrBgEEAYI3EAQxgYwwgYkwdTELMAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0
Q29tIEx0ZC4xKTAnBgNVBAsTIFN0YXJ0Q29tIENlcnRpZmljYXRpb24gQXV0aG9yaXR5MSMw
IQYDVQQDExpTdGFydENvbSBDbGFzcyAxIENsaWVudCBDQQIQT82hO6c2L4lCcoZh0xQXZzCB
nAYLKoZIhvcNAQkQAgsxgYyggYkwdTELMAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0Q29t
IEx0ZC4xKTAnBgNVBAsTIFN0YXJ0Q29tIENlcnRpZmljYXRpb24gQXV0aG9yaXR5MSMwIQYD
VQQDExpTdGFydENvbSBDbGFzcyAxIENsaWVudCBDQQIQT82hO6c2L4lCcoZh0xQXZzANBgkq
hkiG9w0BAQEFAASCAQAfaiT1fXitZAJ6J6Ia3Dk39DzK0d62rCTRBV0LdvXwK+W4OSdINFet
bz5eJNORXuEpDxyiz8cQs/Oz8XzimUz/nAWsIRpW4neAPmkevGQDkvGAuAf0kG16gBD/JHOL
T5n1WUDzmwYjBBx1TQhNvEZOxo+R/ktE5IyUkvL7jn+SFzAzpcGs7dJhyYkUuBVru8JL0w4l
vq1Psee1HS3yaQmP2RgjlMOcFuN7CuWzoncV/n04/BEf659VPC6QVZR2uZsq7reQLcy8WLjn
z5nEDjyL8fOgFnuXdjLIL0RIb+woSdvzbLTkiGmdRCNJTjs0frL6SFM7uW7j7Rm23IHOOUYE
AAAAAAAA
--------------ms040600010703070102050206--


From nobody Tue Apr 12 14:45:40 2016
Return-Path: <sob@sobco.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 1EC0112D8E5 for <ietf@ietfa.amsl.com>; Tue, 12 Apr 2016 14:45:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.109
X-Spam-Level: 
X-Spam-Status: No, score=-1.109 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RDNS_NONE=0.793, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=no 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 tcup5Yq1gNQA for <ietf@ietfa.amsl.com>; Tue, 12 Apr 2016 14:45:37 -0700 (PDT)
Received: from sobco.sobco.com (unknown [136.248.127.164]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 90C6612D855 for <ietf@ietf.org>; Tue, 12 Apr 2016 14:45:37 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by sobco.sobco.com (Postfix) with ESMTP id 378FC1BA634C; Tue, 12 Apr 2016 17:45:36 -0400 (EDT)
X-Virus-Scanned: amavisd-new at sobco.com
Received: from sobco.sobco.com ([127.0.0.1]) by localhost (sobco.sobco.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XTrmLspJBisN; Tue, 12 Apr 2016 17:45:34 -0400 (EDT)
Received: from [10.0.1.16] (173-166-5-69-newengland.hfc.comcastbusiness.net [173.166.5.69]) by sobco.sobco.com (Postfix) with ESMTPSA id 23DAD1BA633E; Tue, 12 Apr 2016 17:45:34 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Subject: Re: Transparency of IAOC
From: "Scott O. Bradner" <sob@sobco.com>
In-Reply-To: <570D69E0.30209@cs.tcd.ie>
Date: Tue, 12 Apr 2016 17:46:19 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <ECD0A4B2-7C8C-4FB0-B9BD-D3C6B3E96E0A@sobco.com>
References: <6.2.5.6.2.20160412031201.0da034e8@elandnews.com> <6.2.5.6.2.20160412114424.0e7061b0@resistor.net> <570D5B51.8090307@gmail.com> <570D69E0.30209@cs.tcd.ie>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
X-Mailer: Apple Mail (2.3124)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/YuXHubgTQkcYO-UbJXsnDafxrWI>
Cc: SM <sm@resistor.net>, ietf@ietf.org, Dave Crocker <dcrocker@bbiw.net>
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: Tue, 12 Apr 2016 21:45:39 -0000

such an exercise is worthwhile & has been underway for a few weeks=20
you will see some results very soon

Scott

> On Apr 12, 2016, at 5:34 PM, Stephen Farrell =
<stephen.farrell@cs.tcd.ie> wrote:
>=20
>=20
> Hi Brian,
>=20
> On 12/04/16 21:32, Brian E Carpenter wrote:
>> Of course it is. But (compared to the IESG) the IAOC does deal with
>> a comparatively large fraction of issues that have confidential
>> aspects - budget negotiation, contract negotiations, staff issues,
>> operation security, and (with their Trustee hats on) legal issues. So
>> there are going to be more problems about community access to IAOC
>> proceedings than for the IESG.
>=20
> What I'm wondering is if, given the above, anyone has done an
> analysis of what the IAOC really needs to keep confidential and
> what does not need to be confidential?
>=20
> For example, recent events have fairly conclusively shown that
> the "cities being considered" data which is related to "contract
> negotiation" really ought not be confidential, at least in some
> aggregated form. If you go back some years, the IETF meeting
> hotel was also a not-so-well-kept secret until bookings opened,
> and when we changed that the sky did not fall. So that's another
> example. And if say the vmeet mailing list had been the place
> where it was decided that IETF-95 remote attendees would have to
> register, then we might have avoided that fuss. I can't see how
> making that decision on that public list would have hurt anything
> even though the fine meetecho support overall nvolves quite a few
> of the issues related to confidentiality you list above.
>=20
> I don't know if the IAOC has analysed such things more generally.
> But I hope it does do that once it's sorted out what to do about
> IETF-100. I suspect that to date, the IAOC has been treating too
> much data as confidential when that's not really needed. I figure
> ending up in that state is quite understandable, but is not in the
> end a good plan.
>=20
> And I don't believe we've actually heard the IAOC say that they
> do think such a general exercise is or is not worthwhile. I do
> think that some such statement now that the IAOC will consider a
> switch to a default-open posture would be very very useful and
> has not yet been made. (*)
>=20
> Cheers,
> S.
>=20
> (*) Leslie's mail [1] only referred to reviewing meeting planning,
> but not e.g. to any broader re-consideration which is what I'm
> arguing would be better.
>=20
> [1] https://www.ietf.org/mail-archive/web/ietf/current/msg97545.html
>=20
>=20
>=20


From nobody Tue Apr 12 14:48:54 2016
Return-Path: <stephen.farrell@cs.tcd.ie>
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 15FE512D80D for <ietf@ietfa.amsl.com>; Tue, 12 Apr 2016 14:48:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.297
X-Spam-Level: 
X-Spam-Status: No, score=-5.297 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.996, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cs.tcd.ie
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 88idzF2kkvB5 for <ietf@ietfa.amsl.com>; Tue, 12 Apr 2016 14:48:50 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7AE7912D632 for <ietf@ietf.org>; Tue, 12 Apr 2016 14:48:50 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 42FBFBE33; Tue, 12 Apr 2016 22:48:49 +0100 (IST)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZkVSvltaQKCt; Tue, 12 Apr 2016 22:48:47 +0100 (IST)
Received: from [10.87.49.100] (unknown [86.42.21.187]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 130A5BDF9; Tue, 12 Apr 2016 22:48:47 +0100 (IST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; s=mail; t=1460497727; bh=uM2nHBXuBO+dGvtLsfZtLzOyNEFfIuaTbNIBv3dV38s=; h=Subject:To:References:Cc:From:Date:In-Reply-To:From; b=fjPA6fHHrZ3fjwBCLdXxfX/kMHjtECA577jlkcMcvEdEkPIVuir6kYddpImy481bC SbuAVRQIzgUyS0FLb6/gcWujtTg62B86EhOfrkY9XoA0iinqCZSWoPNRO7dgMQi5wq 8DIoMdMxSiS/Vy4swBN8znz/gCz7yjX3Tj8M6IN0=
Subject: Re: Transparency of IAOC
To: "Scott O. Bradner" <sob@sobco.com>
References: <6.2.5.6.2.20160412031201.0da034e8@elandnews.com> <6.2.5.6.2.20160412114424.0e7061b0@resistor.net> <570D5B51.8090307@gmail.com> <570D69E0.30209@cs.tcd.ie> <ECD0A4B2-7C8C-4FB0-B9BD-D3C6B3E96E0A@sobco.com>
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Openpgp: id=D66EA7906F0B897FB2E97D582F3C8736805F8DA2; url=
Message-ID: <570D6D3E.1060904@cs.tcd.ie>
Date: Tue, 12 Apr 2016 22:48:46 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0
MIME-Version: 1.0
In-Reply-To: <ECD0A4B2-7C8C-4FB0-B9BD-D3C6B3E96E0A@sobco.com>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha-256; boundary="------------ms040009040608000108040509"
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/BPSqd_JIG-f28kgiBgpP79PdSMI>
Cc: SM <sm@resistor.net>, ietf@ietf.org, Dave Crocker <dcrocker@bbiw.net>
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: Tue, 12 Apr 2016 21:48:52 -0000

This is a cryptographically signed message in MIME format.

--------------ms040009040608000108040509
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable



On 12/04/16 22:46, Scott O. Bradner wrote:
> such an exercise is worthwhile & has been underway for a few weeks=20
> you will see some results very soon

Excellent!

Thanks,
S.

>=20
> Scott
>=20
>> On Apr 12, 2016, at 5:34 PM, Stephen Farrell <stephen.farrell@cs.tcd.i=
e> wrote:
>>
>>
>> Hi Brian,
>>
>> On 12/04/16 21:32, Brian E Carpenter wrote:
>>> Of course it is. But (compared to the IESG) the IAOC does deal with
>>> a comparatively large fraction of issues that have confidential
>>> aspects - budget negotiation, contract negotiations, staff issues,
>>> operation security, and (with their Trustee hats on) legal issues. So=

>>> there are going to be more problems about community access to IAOC
>>> proceedings than for the IESG.
>>
>> What I'm wondering is if, given the above, anyone has done an
>> analysis of what the IAOC really needs to keep confidential and
>> what does not need to be confidential?
>>
>> For example, recent events have fairly conclusively shown that
>> the "cities being considered" data which is related to "contract
>> negotiation" really ought not be confidential, at least in some
>> aggregated form. If you go back some years, the IETF meeting
>> hotel was also a not-so-well-kept secret until bookings opened,
>> and when we changed that the sky did not fall. So that's another
>> example. And if say the vmeet mailing list had been the place
>> where it was decided that IETF-95 remote attendees would have to
>> register, then we might have avoided that fuss. I can't see how
>> making that decision on that public list would have hurt anything
>> even though the fine meetecho support overall nvolves quite a few
>> of the issues related to confidentiality you list above.
>>
>> I don't know if the IAOC has analysed such things more generally.
>> But I hope it does do that once it's sorted out what to do about
>> IETF-100. I suspect that to date, the IAOC has been treating too
>> much data as confidential when that's not really needed. I figure
>> ending up in that state is quite understandable, but is not in the
>> end a good plan.
>>
>> And I don't believe we've actually heard the IAOC say that they
>> do think such a general exercise is or is not worthwhile. I do
>> think that some such statement now that the IAOC will consider a
>> switch to a default-open posture would be very very useful and
>> has not yet been made. (*)
>>
>> Cheers,
>> S.
>>
>> (*) Leslie's mail [1] only referred to reviewing meeting planning,
>> but not e.g. to any broader re-consideration which is what I'm
>> arguing would be better.
>>
>> [1] https://www.ietf.org/mail-archive/web/ietf/current/msg97545.html
>>
>>
>>
>=20
>=20


--------------ms040009040608000108040509
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIAGCSqGSIb3DQEHAqCAMIACAQExDzANBglghkgBZQMEAgEFADCABgkqhkiG9w0BBwEAAKCC
CvIwggUIMIID8KADAgECAhBPzaE7pzYviUJyhmHTFBdnMA0GCSqGSIb3DQEBCwUAMHUxCzAJ
BgNVBAYTAklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSkwJwYDVQQLEyBTdGFydENvbSBD
ZXJ0aWZpY2F0aW9uIEF1dGhvcml0eTEjMCEGA1UEAxMaU3RhcnRDb20gQ2xhc3MgMSBDbGll
bnQgQ0EwHhcNMTYwMjA5MDkyODE1WhcNMTcwMjA5MDkyODE1WjBOMSIwIAYDVQQDDBlzdGVw
aGVuLmZhcnJlbGxAY3MudGNkLmllMSgwJgYJKoZIhvcNAQkBFhlzdGVwaGVuLmZhcnJlbGxA
Y3MudGNkLmllMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAtuC0rYze/2JinSra
C9F2RjGdQZjNALLcW9C3WKTwYII3wBslobmHuPEYE5JaGItmzuKnAW619R1rD/kfoNWC19N3
rBZ6UX9Cmb9D9exCwYIwVuSwjrCQWGxgCtNQTrwKzCCpI790GRiMTvxvO7UmzmBrCaBLiZW5
R0fBjK5Yn6hUhAzGBkNbkIEL28cLJqH0yVz7Kl92OlzrQqTPEts5m6cDnNdY/ADfeAX18c1r
dxZqcAxhLotrCqgsVA4ilbQDMMXGTLlB5TP35HeWZuGBU7xu003rLcFLdOkD8xvpJoYZy9Kt
3oABXPS5yqtMK+XCNdqmMn+4mOtLwQSMmPCSiQIDAQABo4IBuTCCAbUwCwYDVR0PBAQDAgSw
MB0GA1UdJQQWMBQGCCsGAQUFBwMCBggrBgEFBQcDBDAJBgNVHRMEAjAAMB0GA1UdDgQWBBQJ
QhvwQ5Fl372Z6xqo6fdn8XejTTAfBgNVHSMEGDAWgBQkgWw5Yb5JD4+3G0YrySi1J0htaDBv
BggrBgEFBQcBAQRjMGEwJAYIKwYBBQUHMAGGGGh0dHA6Ly9vY3NwLnN0YXJ0c3NsLmNvbTA5
BggrBgEFBQcwAoYtaHR0cDovL2FpYS5zdGFydHNzbC5jb20vY2VydHMvc2NhLmNsaWVudDEu
Y3J0MDgGA1UdHwQxMC8wLaAroCmGJ2h0dHA6Ly9jcmwuc3RhcnRzc2wuY29tL3NjYS1jbGll
bnQxLmNybDAkBgNVHREEHTAbgRlzdGVwaGVuLmZhcnJlbGxAY3MudGNkLmllMCMGA1UdEgQc
MBqGGGh0dHA6Ly93d3cuc3RhcnRzc2wuY29tLzBGBgNVHSAEPzA9MDsGCysGAQQBgbU3AQIE
MCwwKgYIKwYBBQUHAgEWHmh0dHA6Ly93d3cuc3RhcnRzc2wuY29tL3BvbGljeTANBgkqhkiG
9w0BAQsFAAOCAQEArzrSv2C8PlBBmGuiGrzm2Wma46/KHtXmZYS0bsd43pM66Pc/MsqPE0HD
C1GzMFfwB6BfkJn8ijNSIhlgj898WzjvnpM/SO8KStjlB8719ig/xKISrOl5mX55XbFlQtX9
U6MrqRgbDIATxhD9IDr+ryvovDzChqgQj7mt2jYr4mdlRjsjod3H1VY6XglRmaaNGZfsCARM
aE/TU5SXIiqauwt5KxNGYAY67QkOBs7O1FkSXpTk7+1MmzJMF4nP8QQ5n8vhVNseF+/Wm7ai
9mtnrkLbaznMsy/ULo/C2yuLUWTbZZbf4EKNmVdme6tUDgYkFjAFOblfA7W1fSPiQGagYzCC
BeIwggPKoAMCAQICEGunin0K14jWUQr5WeTntOEwDQYJKoZIhvcNAQELBQAwfTELMAkGA1UE
BhMCSUwxFjAUBgNVBAoTDVN0YXJ0Q29tIEx0ZC4xKzApBgNVBAsTIlNlY3VyZSBEaWdpdGFs
IENlcnRpZmljYXRlIFNpZ25pbmcxKTAnBgNVBAMTIFN0YXJ0Q29tIENlcnRpZmljYXRpb24g
QXV0aG9yaXR5MB4XDTE1MTIxNjAxMDAwNVoXDTMwMTIxNjAxMDAwNVowdTELMAkGA1UEBhMC
SUwxFjAUBgNVBAoTDVN0YXJ0Q29tIEx0ZC4xKTAnBgNVBAsTIFN0YXJ0Q29tIENlcnRpZmlj
YXRpb24gQXV0aG9yaXR5MSMwIQYDVQQDExpTdGFydENvbSBDbGFzcyAxIENsaWVudCBDQTCC
ASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAL192vfDon2D9luC/dtbX64eG3XAtRmv
mCSsu1d52DXsCR58zJQbCtB2/A5uFqNxWacpXGGtTCRk9dEDBlmixEd8QiLkUfvHpJX/xKnm
VkS6Iye8wUbYzMsDzgnpazlPg19dnSqfhM+Cevdfa89VLnUztRr2cgmCfyO9Otrh7LJDPG+4
D8ZnAqDtVB8MKYJL6QgKyVhhaBc4y3bGWxKyXEtx7QIZZGxPwSkzK3WIN+VKNdkiwTubW5PI
dopmykwvIjLPqbJK7yPwFZYekKE015OsW6FV+s4DIM8UlVS8pkIsoGGJtMuWjLL4tq2hYQuu
N0jhrxK1ljz50hH23gA9cbMCAwEAAaOCAWQwggFgMA4GA1UdDwEB/wQEAwIBBjAdBgNVHSUE
FjAUBggrBgEFBQcDAgYIKwYBBQUHAwQwEgYDVR0TAQH/BAgwBgEB/wIBADAyBgNVHR8EKzAp
MCegJaAjhiFodHRwOi8vY3JsLnN0YXJ0c3NsLmNvbS9zZnNjYS5jcmwwZgYIKwYBBQUHAQEE
WjBYMCQGCCsGAQUFBzABhhhodHRwOi8vb2NzcC5zdGFydHNzbC5jb20wMAYIKwYBBQUHMAKG
JGh0dHA6Ly9haWEuc3RhcnRzc2wuY29tL2NlcnRzL2NhLmNydDAdBgNVHQ4EFgQUJIFsOWG+
SQ+PtxtGK8kotSdIbWgwHwYDVR0jBBgwFoAUTgvvGqRAW6UXaYcwyjRoQ9BBrvIwPwYDVR0g
BDgwNjA0BgRVHSAAMCwwKgYIKwYBBQUHAgEWHmh0dHA6Ly93d3cuc3RhcnRzc2wuY29tL3Bv
bGljeTANBgkqhkiG9w0BAQsFAAOCAgEAi+P3h+wBi4StDwECW5zhIycjBL008HACblIf26HY
0JdOruKbrWDsXUsiI0j/7Crft9S5oxvPiDtVqspBOB/y5uzSns1lZwh7sG96bYBZpcGzGxpF
NjDmQbcM3yl3WFIRS4WhNrsOY14V7y2IrUGsvetsD+bjyOngCIVeC/GmsmtbuLOzJ606tEc9
uRbhjTu/b0x2Fo+/e7UkQvKzNeo7OMhijixaULyINBfCBJb+e29bLafgu6JqjOUJ9eXXj20p
6q/CW+uVrZiSW57+q5an2P2i7hP85jQJcy5j4HzA0rSiF3YPhKGAWUxKPMAVGgcYoXzWydOv
Z3UDsTDTagXpRDIKQLZo02wrlxY6iMFqvlzsemVf1odhQJmi7Eh5TbxI40kDGcBOBHhwnaOu
mZhLP+SWJQnjpLpSlUOj95uf1zo9oz9e0NgIJoz/tdfrBzez76xtDsK0KfUDHt1/q59BvDI7
RX6gVr0fQoCyMczNzCTcRXYHY0tq2J0oT+bsb6sH2b4WVWAiJKnSYaWDjdA70qHX4mq9MIjO
/ZskmSY8wtAk24orAc0vwXgYanqNsBX5Yv4sN4Z9VyrwMdLcusP7HJgRdAGKpkR2I9U4zEsN
JQJewM7S4Jalo1DyPrLpL2nTET8ZrSl5Utp1UeGp/2deoprGevfnxWB+vHNQiu85o6MxggPM
MIIDyAIBATCBiTB1MQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRDb20gTHRkLjEpMCcG
A1UECxMgU3RhcnRDb20gQ2VydGlmaWNhdGlvbiBBdXRob3JpdHkxIzAhBgNVBAMTGlN0YXJ0
Q29tIENsYXNzIDEgQ2xpZW50IENBAhBPzaE7pzYviUJyhmHTFBdnMA0GCWCGSAFlAwQCAQUA
oIICEzAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0xNjA0MTIy
MTQ4NDZaMC8GCSqGSIb3DQEJBDEiBCC3VUsTe/h8EXkiR2eP9ZAoa/BVieesA6/NW00Iy4Xb
0jBsBgkqhkiG9w0BCQ8xXzBdMAsGCWCGSAFlAwQBKjALBglghkgBZQMEAQIwCgYIKoZIhvcN
AwcwDgYIKoZIhvcNAwICAgCAMA0GCCqGSIb3DQMCAgFAMAcGBSsOAwIHMA0GCCqGSIb3DQMC
AgEoMIGaBgkrBgEEAYI3EAQxgYwwgYkwdTELMAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0
Q29tIEx0ZC4xKTAnBgNVBAsTIFN0YXJ0Q29tIENlcnRpZmljYXRpb24gQXV0aG9yaXR5MSMw
IQYDVQQDExpTdGFydENvbSBDbGFzcyAxIENsaWVudCBDQQIQT82hO6c2L4lCcoZh0xQXZzCB
nAYLKoZIhvcNAQkQAgsxgYyggYkwdTELMAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0Q29t
IEx0ZC4xKTAnBgNVBAsTIFN0YXJ0Q29tIENlcnRpZmljYXRpb24gQXV0aG9yaXR5MSMwIQYD
VQQDExpTdGFydENvbSBDbGFzcyAxIENsaWVudCBDQQIQT82hO6c2L4lCcoZh0xQXZzANBgkq
hkiG9w0BAQEFAASCAQBFl9sMpox4bDNRBLWfz7UWzQyyupBjEwdv973uUKIPTR9P+2xTt1if
0EFOE1+Khm4E1lsZlB6yJ7TTskdBTY//ojSPOCFV9mUSCmp41lSvlKQUt5tb26GyEPF60Edw
xjCkQ+ALo+NrfJTzw5AEF1d/xncWAi/nNEi8oX8rG/IHEV+WQET/r61hwPXmrPiqTF7J5wHm
QSui1DNM85tz5Fu8MrmWvLCbAPdm6R/kAFpHt4/zTlr0v9KNhwFuNtqo2t9TbwIYQF1TWmxf
AWx5nmsTnMntkNivwbrIUGF98XgNMK13OwMR+A2PMLB5hMaiBqrtEPdgpHnVW99yuh+Yuajx
AAAAAAAA
--------------ms040009040608000108040509--


From nobody Tue Apr 12 18:25:36 2016
Return-Path: <randy@psg.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 1A67512D0D8 for <ietf@ietfa.amsl.com>; Tue, 12 Apr 2016 18:25:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.896
X-Spam-Level: 
X-Spam-Status: No, score=-7.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.996] 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 pPwvyXd0l-eV for <ietf@ietfa.amsl.com>; Tue, 12 Apr 2016 18:25:34 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4384012D0A0 for <ietf@ietf.org>; Tue, 12 Apr 2016 18:25:34 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com) by ran.psg.com with esmtp (Exim 4.82) (envelope-from <randy@psg.com>) id 1aq9Ye-00074Z-Ak; Wed, 13 Apr 2016 01:25:28 +0000
Date: Wed, 13 Apr 2016 10:25:27 +0900
Message-ID: <m2fuuq1erc.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: SM <sm@resistor.net>
Subject: Re: Transparency of IAOC
In-Reply-To: <570D5B51.8090307@gmail.com>
References: <6.2.5.6.2.20160412031201.0da034e8@elandnews.com> <6.2.5.6.2.20160412114424.0e7061b0@resistor.net> <570D5B51.8090307@gmail.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/DfxWbqej3xxAj_pgoT_08vrMfT8>
Cc: IETF Disgust List <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, 13 Apr 2016 01:25:35 -0000

> a person's IETF career

why does this phrase make me very uncomfortable?

randy


From nobody Tue Apr 12 19:08:49 2016
Return-Path: <brian.e.carpenter@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 E959E12DE1E for <ietf@ietfa.amsl.com>; Tue, 12 Apr 2016 19:08:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 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, RCVD_IN_DNSWL_LOW=-0.7, 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 4_H6gBbLyDEa for <ietf@ietfa.amsl.com>; Tue, 12 Apr 2016 19:08:46 -0700 (PDT)
Received: from mail-pf0-x233.google.com (mail-pf0-x233.google.com [IPv6:2607:f8b0:400e:c00::233]) (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 8DB4912DC2D for <ietf@ietf.org>; Tue, 12 Apr 2016 19:08:46 -0700 (PDT)
Received: by mail-pf0-x233.google.com with SMTP id c20so24699111pfc.1 for <ietf@ietf.org>; Tue, 12 Apr 2016 19:08:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=subject:to:references:from:organization:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=H03Eys4+zuYtmYR1DC9Hx/8tRhPx4e3/G9rI5K/gIzQ=; b=zl8jDceeRklhLDg6hJSH5h5x/wmgSlDT/W/nVCJGFFj+IKls0OUmkcwLlsu+TCv8J/ edOfwdzun05TPvB+leXuSOQuidDQdV3Jcd714XvNdUiS+Byh6Apx/gM2dMeAuKS6ZkMm fcsG4SL3k1NwyAeIDk91D85HTMqjs22IOk9JnihES8NVEI9zPaDsiGqjX0YLSDujCcz6 It3/MuDjqMYQLNfxAmeC5WZO8j5J5OlIcuZ7ApnQDLTts+qeNnOfYeSAzGVCc8/alhjV 0DMA5rjuRxiASMjIHK8X0ljLL1qa1DQfe1RfAHUR5vL4DVcsSfvw/xTpZVfc0NFCTm34 2vOw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=H03Eys4+zuYtmYR1DC9Hx/8tRhPx4e3/G9rI5K/gIzQ=; b=dfW4qdO8+rWK2WckEkcsSXRfAylQMtHhn5E96xbMgq8dOX+8ggURzQIcQdkQlef0XS jbh11cwG5z48fHbtr7K/zEBO9WfAFYcrLm9YkZpZ3VH2bf1exvAUB1OBwfctHFnyilze pf51VA7ZDeoyOvmOAeORprjZ94zm7m7EUPkHHy8SN9/pSZ2buePKYEp9TceygJYckgtN IdQhAZYGSJtuHl7KZpuCaZVXMDkb1kqgqTr+YfHUGB4TeS8u4ha1l0Ll9mz/xEYQIq97 Xy0gQcFG/oiO0POjyptLwcWxQG1lulf3i79ZIsPoF7D3+nm8VpsQ65Ih/Z9a2DbyP9Cy AWew==
X-Gm-Message-State: AOPr4FVTZCyXON0FWK/BQ6wk0wdqJjcVBLvTQf16+7fYxkPkqJNmIh7fVJdRRhaKEq+/Rw==
X-Received: by 10.98.31.218 with SMTP id l87mr9264757pfj.101.1460513326165; Tue, 12 Apr 2016 19:08:46 -0700 (PDT)
Received: from ?IPv6:2001:df0:0:2006:c0da:ac17:5f6d:8e76? ([2001:df0:0:2006:c0da:ac17:5f6d:8e76]) by smtp.gmail.com with ESMTPSA id i9sm46502397pfi.95.2016.04.12.19.08.42 for <ietf@ietf.org> (version=TLSv1/SSLv3 cipher=OTHER); Tue, 12 Apr 2016 19:08:44 -0700 (PDT)
Subject: Re: Remote only meetings? [Re: Concerns about Singapore]
To: IETF discussion list <ietf@ietf.org>
References: <570AB3AF.2050401@gmail.com> <87twj99c6w.fsf@tops.chopps.org> <CAKe6YvMyp-DyeDwpPY6KYmbDbnpgnvVk_cUStnA32wmgDWcz3w@mail.gmail.com> <BBF5DDFE515C3946BC18D733B20DAD233A62AA18@XMB122CNC.rim.net> <20160411104519.GA19092@gsp.org> <3F48466D-390C-4C18-B958-732AE3E46FF1@gmail.com> <20160411223403.GA6743@gsp.org> <87twj7eon7.fsf@tops.chopps.org> <20160412110839.GA20488@gsp.org> <8760vn82f2.fsf@tops.chopps.org> <20160412124639.GA27223@gsp.org>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <570DAA2F.1040007@gmail.com>
Date: Wed, 13 Apr 2016 14:08:47 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2
MIME-Version: 1.0
In-Reply-To: <20160412124639.GA27223@gsp.org>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/vY9YppCUl-fQEDb4h-Lo0_iOzLc>
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, 13 Apr 2016 02:08:48 -0000

Cherry-picking a few points:
On 13/04/2016 00:46, Rich Kulawiec wrote:
...
> And the difficulties/expense of travel are only going to get worse
> for the forseeable future: they're not going to get better.

That is indisputable.

On 13/04/2016 00:49, Loa Andersson wrote:

> Let us say that we set aside enough time about half way between two IETF
> meetings and schedule all the meetings, as requested by wg chairs or
> people in charge of other meetings, as a long series.

That won't work with 4-monthly meetings as today. It might work with
6-monthly meetings.

> Let us assume that the wg meetings is on average 1.5 hours, scheduling
> 100 wg meetings would require 150 hours.

I think that's optimistic. Remote meetings go more slowly due to technology
glitches and the need for more formal patterns of Q/A. It's still faster than
email though (see Alia's message).

On 13/04/2016 03:42, Joel M. Halpern wrote:

> I believe that there would be a real cost in moving to remote-only meetings.
> Even putting aside the time zone difficulties, and the reduced effectiveness
> of in-meeting interaction, there are aspects of face-to-face interaction
> taht current remote technologies simply do not capture.

Yes. I've been on a one-meeting-per-year model once or twice for personal
reasons and it is *inferior* to attending every meeting. Some people
can manage to time shift their lives for a week for remote participation,
but most people can't; family, day job, and sunshine combine against it.
The time zone issue is exclusionary. Also, there is nothing like the
intensity of being on site with everybody.

Not to say that we shouldn't improve even more on what we can do
with Meetecho. But an important part of being able to make the best
use of remote participation is *knowing* the people at the other
end from previous in-person meetings.

> It was very helpful in BA (and at many previous IETF meetings) to be able
> to find time to talk with a small number of people concerned about an
> aspect of one working group. I did that over meals, breaks, etc. It
> sorted out issues far more effectively than email conversations (in several
> cases, we had tried to sort it out via email. 10 minutes face-to-face
> clarified what was being missed, and found a good path forward.)

On 13/04/2016 04:00, Ted Lemon wrote:
> This is all true, but the idea that it can't be replicated online is silly.
> How did you arrange to have lunch with these people? You went looking
> for them, rounded them up, and sat down to lunch. You can do that online
> as well.

You can, but it's a much more deliberate action and you're less
likely to get serendipity effects. I would probably have been in
some of those discussions in BA that Joel mentioned, but unfortunately
I was on the wrong side of the world and fast asleep.

IMHO we need the right blend of in-person and virtual meetings, and
we'll find that blend by progressive change, not by revolution.

   Brian






From nobody Tue Apr 12 19:42:34 2016
Return-Path: <akatlas@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 DE20A12DD98 for <ietf@ietfa.amsl.com>; Tue, 12 Apr 2016 19:42:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.699
X-Spam-Level: 
X-Spam-Status: No, score=-102.699 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, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] 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 AB1xR1tQRWDP for <ietf@ietfa.amsl.com>; Tue, 12 Apr 2016 19:42:30 -0700 (PDT)
Received: from mail-oi0-x22a.google.com (mail-oi0-x22a.google.com [IPv6:2607:f8b0:4003:c06::22a]) (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 6842112DD7D for <ietf@ietf.org>; Tue, 12 Apr 2016 19:42:29 -0700 (PDT)
Received: by mail-oi0-x22a.google.com with SMTP id w85so46973964oiw.0 for <ietf@ietf.org>; Tue, 12 Apr 2016 19:42:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=McFJyBRP9tbvnvkC5EsFcABlvGkcY1UV1mf4ahKxAOw=; b=NsSLclQT3tUz0ekk6uuHt8xmwkR9Q5DjN0De+GMXREgG1NrtfTpaF6vupcyA3V4uPE OSRJLPJohA8ieFh9ywtNkFnt5qqjyB5kOj7oY1wSQ0Id/NIFJb3xH4L1Yed/lYBV0nR+ s1PtA0Qbaw+b5B4pz4h+0GSVM1w0y5H/QQj5pYXVZ7fEYkanRUBmKKC5pToMwbzQv6y0 GPLryBsSwihznXyUZKOiG0XTgB2W6eYtntV/cdhIi6madJcM5SW+wGDr7FXs5+U0gH/6 S3SLdXa5FwahzbR0UxMh9TrYghkiZF6vkT9XmkVQTTn406o5iw2xAe3BWTc1NZM2Nmwf 7yvw==
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:date :message-id:subject:from:to:cc; bh=McFJyBRP9tbvnvkC5EsFcABlvGkcY1UV1mf4ahKxAOw=; b=QscF8fH0b4zxr1Q7Wq0g3fizdv0i0clpQTFp7e9+CQFc8ZrlS7PirAeSYCWzC+Oj6c V4g9gR3N2zXjbmreRBO7W+9a/1k07LUQ2f82vqzb5/fLW2dBE/VYFdam1n4puU4uqup4 nuLMGHu/x+hIrqAItcy7S7ZyG/kH0kA0YICftEoKa8jjmUp5rhz4zN3sNwxyMJINV8Z3 +NJfJKY+u2DYDmV4lrPZkLoIAYrcdqBWXPSSW4UpldLtnVtBYu9+RYgxZ/E9tELoEyPa t773S/6SCD52j1YXFo2+7o086400CG9nMACjyAdhn7JcifYSWkiHHAf04OGbZjBEg5/v fMGQ==
X-Gm-Message-State: AOPr4FW6wEXcib3HqOGVTlS7+7HfCkwCUwkrR9iNR1kSR23nWL0vHHTs5X6Z9wBUq+GB/6WUTXj8aKlwWkKaIw==
MIME-Version: 1.0
X-Received: by 10.202.172.201 with SMTP id v192mr2836870oie.29.1460515348731;  Tue, 12 Apr 2016 19:42:28 -0700 (PDT)
Received: by 10.60.115.168 with HTTP; Tue, 12 Apr 2016 19:42:28 -0700 (PDT)
In-Reply-To: <570DAA2F.1040007@gmail.com>
References: <570AB3AF.2050401@gmail.com> <87twj99c6w.fsf@tops.chopps.org> <CAKe6YvMyp-DyeDwpPY6KYmbDbnpgnvVk_cUStnA32wmgDWcz3w@mail.gmail.com> <BBF5DDFE515C3946BC18D733B20DAD233A62AA18@XMB122CNC.rim.net> <20160411104519.GA19092@gsp.org> <3F48466D-390C-4C18-B958-732AE3E46FF1@gmail.com> <20160411223403.GA6743@gsp.org> <87twj7eon7.fsf@tops.chopps.org> <20160412110839.GA20488@gsp.org> <8760vn82f2.fsf@tops.chopps.org> <20160412124639.GA27223@gsp.org> <570DAA2F.1040007@gmail.com>
Date: Tue, 12 Apr 2016 22:42:28 -0400
Message-ID: <CAG4d1rdtyfZWiUD7yGAF8YoTiuN1TaE+Zqe+q0hpXZHdtUZ1oA@mail.gmail.com>
Subject: Re: Remote only meetings? [Re: Concerns about Singapore]
From: Alia Atlas <akatlas@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Content-Type: multipart/alternative; boundary=001a113ced748cdf95053054ba7e
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/yfdd5QVV4jA43d5B49fQjj7tgnA>
Cc: IETF discussion list <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, 13 Apr 2016 02:42:33 -0000

--001a113ced748cdf95053054ba7e
Content-Type: text/plain; charset=UTF-8

What I would love to see is some brainstorming on how to recreate the
serendipity of IETF hallway interactions.

For instance, could we have people sign up for "random 15-minute
conversations"
while indicating a general area (or set of WGs) of interest?   Think sort
of like
"speed-mentoring" but for all?   It could include video to get closer to
in-person
and maybe start with some suggested ice-breakers (favorite IETF meeting
site,
preferred beverage, best snack, first IETF meeting....)?

I can't beat the benefits of randomly seeing someone who didn't come
immediately
to mind - and knowing precisely who to go talk to (ok - I'm an AD -
encourage into
volunteering to do something).

Until we can recreate some of that randomness and recognition that we are
all
people who care about technology and the Internet (and have families,
opinions
on books, etc), I can't see that decreasing physical IETF meetings would be
at
all productive.

Regards,
Alia

On Tue, Apr 12, 2016 at 10:08 PM, Brian E Carpenter <
brian.e.carpenter@gmail.com> wrote:

> Cherry-picking a few points:
> On 13/04/2016 00:46, Rich Kulawiec wrote:
> ...
> > And the difficulties/expense of travel are only going to get worse
> > for the forseeable future: they're not going to get better.
>
> That is indisputable.
>
> On 13/04/2016 00:49, Loa Andersson wrote:
>
> > Let us say that we set aside enough time about half way between two IETF
> > meetings and schedule all the meetings, as requested by wg chairs or
> > people in charge of other meetings, as a long series.
>
> That won't work with 4-monthly meetings as today. It might work with
> 6-monthly meetings.
>
> > Let us assume that the wg meetings is on average 1.5 hours, scheduling
> > 100 wg meetings would require 150 hours.
>
> I think that's optimistic. Remote meetings go more slowly due to technology
> glitches and the need for more formal patterns of Q/A. It's still faster
> than
> email though (see Alia's message).
>
> On 13/04/2016 03:42, Joel M. Halpern wrote:
>
> > I believe that there would be a real cost in moving to remote-only
> meetings.
> > Even putting aside the time zone difficulties, and the reduced
> effectiveness
> > of in-meeting interaction, there are aspects of face-to-face interaction
> > taht current remote technologies simply do not capture.
>
> Yes. I've been on a one-meeting-per-year model once or twice for personal
> reasons and it is *inferior* to attending every meeting. Some people
> can manage to time shift their lives for a week for remote participation,
> but most people can't; family, day job, and sunshine combine against it.
> The time zone issue is exclusionary. Also, there is nothing like the
> intensity of being on site with everybody.
>
> Not to say that we shouldn't improve even more on what we can do
> with Meetecho. But an important part of being able to make the best
> use of remote participation is *knowing* the people at the other
> end from previous in-person meetings.
>
> > It was very helpful in BA (and at many previous IETF meetings) to be able
> > to find time to talk with a small number of people concerned about an
> > aspect of one working group. I did that over meals, breaks, etc. It
> > sorted out issues far more effectively than email conversations (in
> several
> > cases, we had tried to sort it out via email. 10 minutes face-to-face
> > clarified what was being missed, and found a good path forward.)
>
> On 13/04/2016 04:00, Ted Lemon wrote:
> > This is all true, but the idea that it can't be replicated online is
> silly.
> > How did you arrange to have lunch with these people? You went looking
> > for them, rounded them up, and sat down to lunch. You can do that online
> > as well.
>
> You can, but it's a much more deliberate action and you're less
> likely to get serendipity effects. I would probably have been in
> some of those discussions in BA that Joel mentioned, but unfortunately
> I was on the wrong side of the world and fast asleep.
>
> IMHO we need the right blend of in-person and virtual meetings, and
> we'll find that blend by progressive change, not by revolution.
>
>    Brian
>
>
>
>
>
>

--001a113ced748cdf95053054ba7e
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">What I would love to see is some brainstorming on how to r=
ecreate the<div>serendipity of IETF hallway interactions.</div><div><br></d=
iv><div>For instance, could we have people sign up for &quot;random 15-minu=
te conversations&quot;</div><div>while indicating a general area (or set of=
 WGs) of interest? =C2=A0 Think sort of like</div><div>&quot;speed-mentorin=
g&quot; but for all? =C2=A0 It could include video to get closer to in-pers=
on</div><div>and maybe start with some suggested ice-breakers (favorite IET=
F meeting site,</div><div>preferred beverage, best snack, first IETF meetin=
g....)?</div><div><br></div><div>I can&#39;t beat the benefits of randomly =
seeing someone who didn&#39;t come immediately</div><div>to mind - and know=
ing precisely who to go talk to (ok - I&#39;m an AD - encourage into</div><=
div>volunteering to do something).</div><div><br></div><div>Until we can re=
create some of that randomness and recognition that we are all</div><div>pe=
ople who care about technology and the Internet (and have families, opinion=
s</div><div>on books, etc), I can&#39;t see that decreasing physical IETF m=
eetings would be at</div><div>all productive.</div><div><br></div><div>Rega=
rds,</div><div>Alia</div></div><div class=3D"gmail_extra"><br><div class=3D=
"gmail_quote">On Tue, Apr 12, 2016 at 10:08 PM, Brian E Carpenter <span dir=
=3D"ltr">&lt;<a href=3D"mailto:brian.e.carpenter@gmail.com" target=3D"_blan=
k">brian.e.carpenter@gmail.com</a>&gt;</span> wrote:<br><blockquote class=
=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padd=
ing-left:1ex">Cherry-picking a few points:<br>
On 13/04/2016 00:46, Rich Kulawiec wrote:<br>
...<br>
<span class=3D"">&gt; And the difficulties/expense of travel are only going=
 to get worse<br>
&gt; for the forseeable future: they&#39;re not going to get better.<br>
<br>
</span>That is indisputable.<br>
<span class=3D""><br>
On 13/04/2016 00:49, Loa Andersson wrote:<br>
<br>
&gt; Let us say that we set aside enough time about half way between two IE=
TF<br>
&gt; meetings and schedule all the meetings, as requested by wg chairs or<b=
r>
&gt; people in charge of other meetings, as a long series.<br>
<br>
</span>That won&#39;t work with 4-monthly meetings as today. It might work =
with<br>
6-monthly meetings.<br>
<span class=3D""><br>
&gt; Let us assume that the wg meetings is on average 1.5 hours, scheduling=
<br>
&gt; 100 wg meetings would require 150 hours.<br>
<br>
</span>I think that&#39;s optimistic. Remote meetings go more slowly due to=
 technology<br>
glitches and the need for more formal patterns of Q/A. It&#39;s still faste=
r than<br>
email though (see Alia&#39;s message).<br>
<span class=3D""><br>
On 13/04/2016 03:42, Joel M. Halpern wrote:<br>
<br>
&gt; I believe that there would be a real cost in moving to remote-only mee=
tings.<br>
&gt; Even putting aside the time zone difficulties, and the reduced effecti=
veness<br>
&gt; of in-meeting interaction, there are aspects of face-to-face interacti=
on<br>
&gt; taht current remote technologies simply do not capture.<br>
<br>
</span>Yes. I&#39;ve been on a one-meeting-per-year model once or twice for=
 personal<br>
reasons and it is *inferior* to attending every meeting. Some people<br>
can manage to time shift their lives for a week for remote participation,<b=
r>
but most people can&#39;t; family, day job, and sunshine combine against it=
.<br>
The time zone issue is exclusionary. Also, there is nothing like the<br>
intensity of being on site with everybody.<br>
<br>
Not to say that we shouldn&#39;t improve even more on what we can do<br>
with Meetecho. But an important part of being able to make the best<br>
use of remote participation is *knowing* the people at the other<br>
end from previous in-person meetings.<br>
<span class=3D""><br>
&gt; It was very helpful in BA (and at many previous IETF meetings) to be a=
ble<br>
&gt; to find time to talk with a small number of people concerned about an<=
br>
&gt; aspect of one working group. I did that over meals, breaks, etc. It<br=
>
&gt; sorted out issues far more effectively than email conversations (in se=
veral<br>
&gt; cases, we had tried to sort it out via email. 10 minutes face-to-face<=
br>
&gt; clarified what was being missed, and found a good path forward.)<br>
<br>
</span><span class=3D"">On 13/04/2016 04:00, Ted Lemon wrote:<br>
&gt; This is all true, but the idea that it can&#39;t be replicated online =
is silly.<br>
&gt; How did you arrange to have lunch with these people? You went looking<=
br>
&gt; for them, rounded them up, and sat down to lunch. You can do that onli=
ne<br>
&gt; as well.<br>
<br>
</span>You can, but it&#39;s a much more deliberate action and you&#39;re l=
ess<br>
likely to get serendipity effects. I would probably have been in<br>
some of those discussions in BA that Joel mentioned, but unfortunately<br>
I was on the wrong side of the world and fast asleep.<br>
<br>
IMHO we need the right blend of in-person and virtual meetings, and<br>
we&#39;ll find that blend by progressive change, not by revolution.<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
=C2=A0 =C2=A0Brian<br>
<br>
<br>
<br>
<br>
<br>
</font></span></blockquote></div><br></div>

--001a113ced748cdf95053054ba7e--


From nobody Tue Apr 12 22:30:35 2016
Return-Path: <dactechng@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 D97B912D588 for <ietf@ietfa.amsl.com>; Tue, 12 Apr 2016 22:30:33 -0700 (PDT)
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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 O6ZypJJxb0ou for <ietf@ietfa.amsl.com>; Tue, 12 Apr 2016 22:30:32 -0700 (PDT)
Received: from mail-pa0-x243.google.com (mail-pa0-x243.google.com [IPv6:2607:f8b0:400e:c03::243]) (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 D3F7912D179 for <ietf@ietf.org>; Tue, 12 Apr 2016 22:30:31 -0700 (PDT)
Received: by mail-pa0-x243.google.com with SMTP id vv3so2980928pab.0 for <ietf@ietf.org>; Tue, 12 Apr 2016 22:30:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=date:subject:message-id:importance:from:to:cc:mime-version;  bh=DbFS9yBA18AnanhR++BimIl1nBvqxWW/PaGXaUYh6YY=; b=CjZ9Raos3E48w6Rbisnvf9xO37bdR6RaKnpUpz9WctqPi2/8oJe1GmK8Yzoiydlsy/ vkfA3DEv5/3m0HHIuFmtYuTbC2f0aJ27NFCKj+/jBA1nI8TaTLxN6WtulL6VmXmeV5+G MoE//47q2u4z6/gnYgRGEkaeeV3Jltv1PzDRi0flU3gODefu56SS6EhhwUNE7vomV4K8 +IjqV3402QOz7CpMaAM0FVCCuJLm7jvM7Jsz9zxl0n7H+/XTvv56ZI+LrWQLF4YLomBn nDMZ2VqH9yNy8zoVmoYuHLSq6rKD0C61PN4lfg3CZ3UCmYU6zR1ri/71fhXIXIX3zYRD mZTw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:subject:message-id:importance:from:to:cc :mime-version; bh=DbFS9yBA18AnanhR++BimIl1nBvqxWW/PaGXaUYh6YY=; b=Evwh+Rd3GW3wZwkSNakEpyeHcxf2CByfE8MrxiBJOVYISzp1CjWJ8y2CgPbYqnqK3W uFfx50sSy7WnEqvs9+FoYgtM3W5lHHkYyejo6LJ8MVQW/AMpCt04H+L9u8zOmPS1ouJs 4Aak2rWev9z/MfrTUDkFyGQ64xZy1pF3IrGP7d8XsF3kQEzfojsVJUGpz728UH8KAG2i NYWDB7IeWB/F5C5aWiFBxaJhxwbVLNQL303hxk5pQfr23skQkirYMdHplA2klbyjbIyE b8HIPblQk1PpdBaMz7cwjxYggUlHMLLDVIAPe1y5cqudeqf2RqmIyRuDDtJNy+mi03UN aMvA==
X-Gm-Message-State: AOPr4FV+5jgIJo/CQC596s7ii57EWueFcXZgQ41uyQjjtaMKWyIN3bGbxAR/pnVovtc27g==
X-Received: by 10.66.246.165 with SMTP id xx5mr10231333pac.87.1460525431455; Tue, 12 Apr 2016 22:30:31 -0700 (PDT)
Received: from [10.0.0.164] (151-236-44-231.static.as29550.net. [151.236.44.231]) by smtp.gmail.com with ESMTPSA id v74sm47610100pfa.7.2016.04.12.22.30.27 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 12 Apr 2016 22:30:30 -0700 (PDT)
Date: Wed, 13 Apr 2016 06:30:19 +0100
Subject: Re: Virtual IETFs (was: Re: Concerns about Singapore)
Message-ID: <8hmexuao0v6uj7vgeyf8e863.1460525419380@email.android.com>
Importance: normal
From: Daniel Ajike Chidi <dactechng@gmail.com>
To: Ted Lemon <mellon@fugue.com>, Tim Chown <tjc@ecs.soton.ac.uk>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="--_com.samsung.android.email_16206164285010"
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/_GJvl2mD4ZWsaBsrtUCgrcF8Meo>
Cc: ietf <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, 13 Apr 2016 05:30:34 -0000

----_com.samsung.android.email_16206164285010
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: base64

UmVtb3ZlIG1lIGZyb20gbWFpbGluZyBsaXN0IG9vb28KCgpTZW50IGZyb20gbXkgU2Ftc3VuZyBH
YWxheHkgc21hcnRwaG9uZS4tLS0tLS0tLSBPcmlnaW5hbCBtZXNzYWdlIC0tLS0tLS0tRnJvbTog
VGVkIExlbW9uIDxtZWxsb25AZnVndWUuY29tPiBEYXRlOiAxMi8wNC8yMDE2ICAyOjQ3IHBtICAo
R01UKzAxOjAwKSBUbzogVGltIENob3duIDx0amNAZWNzLnNvdG9uLmFjLnVrPiBDYzogaWV0ZiA8
aWV0ZkBpZXRmLm9yZz4gU3ViamVjdDogUmU6IFZpcnR1YWwgSUVURnMgKHdhczogUmU6IENvbmNl
cm5zIGFib3V0IFNpbmdhcG9yZSkgCldoZW4gSSBoYWQgdG8gbWlzcyBQcmFndWUsIEkganVzdCB0
aW1lLXNoaWZ0ZWQgZm9yIHRoZSB3ZWVrLiDCoCBXb3VsZG4ndCB3b3JrIGZvciBldmVyeW9uZSwg
YnV0IGl0IHNlZW1lZCBmaW5lIHRvIG1lLgpPbiBUdWUsIEFwciAxMiwgMjAxNiBhdCA5OjQyIEFN
LCBUaW0gQ2hvd24gPHRqY0BlY3Muc290b24uYWMudWs+IHdyb3RlOgpPbiAxMiBBcHIgMjAxNiwg
YXQgMTQ6MjIsIFRlZCBMZW1vbiA8bWVsbG9uQGZ1Z3VlLmNvbT4gd3JvdGU6ClRoZSBwcm9ibGVt
IHdpdGggYSBsYXJnZXIgdmlydHVhbCBpbnRlcmltIGlzIHRoYXQgaXQgZG9lc24ndCByZXBsYWNl
IGFuIElFVEYsIGFuZCBzbyB5b3UncmUgYWRkaW5nIHdvcmtsb2FkIGJ1dCBub3Qgc3VidHJhY3Rp
bmcgYW55IHdvcmtsb2FkLiDCoCBJIGRvbid0IHNlZSB0aGUgcG9pbnQgaW4gdGhhdC4KV2VsbCwg
dGhlcmUgbWF5IGJlIGEgbnVtYmVyIG9mIFdHcyB0aGF0IHdpc2ggdG8gcHJvZ3Jlc3MgdGhlaXIg
d29yayBhIGJpdCBtb3JlIGJyaXNrbHksIG9yIGhhdmUgb25lIG9yIG1vcmUgc3BlY2lmaWMgdG9w
aWNzIHRoYXQgbmVlZCBwcm9tcHQgZGlzY3Vzc2lvbiwgYW5kIHVzZSBhbiBpbnRlcmltIG1lZXRp
bmcgdG8gYWNoaWV2ZSB0aGF0LiBTbyBJ4oCZbSBub3Qgc3VyZSBpdOKAmXMgYWRkaW5nIHRvIHdv
cmtsb2FkLCByYXRoZXIgaXQgbWF5IGFsbG93IHVzIHRvIGJlIG1vcmUgZWZmaWNpZW50LsKgIEJ1
dCB0aGUgbWFpbiBpc3N1ZSB3aXRoIGFueSB2aXJ0dWFsIG1lZXRpbmcgaXMgdGltZXpvbmVzLiBU
aGVyZeKAmXMgcmVhbGx5IG5vIHdheSB0byBkZWFsIHdpdGggdGhhdCBwcm9ibGVtIHNhdGlzZmFj
dG9yaWx5LsKgClRpbQoKT24gVHVlLCBBcHIgMTIsIDIwMTYgYXQgODozMCBBTSwgVGltIENob3du
IDx0amNAZWNzLnNvdG9uLmFjLnVrPiB3cm90ZToKT24gMTIgQXByIDIwMTYsIGF0IDEyOjQ5LCBU
ZWQgTGVtb24gPG1lbGxvbkBmdWd1ZS5jb20+IHdyb3RlOgpBZ3JlZSBhYm91dCBCdWVub3MgQWly
ZXMuIMKgIFdlIGFscmVhZHkgZG8gZXhjZWxsZW50IHZpcnR1YWwgaW50ZXJpbXMtLUkgdGhpbmsg
aWYgeW91ciBzdGFuZGFyZCBmb3Igd2hldGhlciB3ZSBjYW4gZG8gYSB2aXJ0dWFsIElFVEYgaXMg
dGhhdCB2aXJ0dWFsIGludGVyaW1zIHdvcmssIHdlIGFyZSBhbHJlYWR5IHRoZXJlLgpJIHRoaW5r
IHRoYXQgaWYgd2Ugd2FudCB0byB0ZXN0IHRoaXMgaWRlYSwgd2hhdCB3ZSBuZWVkIHRvIGRvIGlz
IGRlc2lnbmF0ZSBzb21lIGZ1dHVyZSBJRVRGIHZpcnR1YWwgX25vd18sIGFuZCB0aGVuIHN0YXJ0
IHByZXBhcmluZywgcmF0aGVyIHRoYW4gc2F5ICJvaCwgd2Ugc2hvdWxkIGRvIGEgdmlydHVhbCIg
YW5kIHRoZW4gZGl0aGVyIGFib3V0IHdoZW4gd2UgbWlnaHQgYmUgcmVhZHkuIMKgIFdlIHdpbGwg
bmV2ZXIgYmUgc28gcmVhZHkgdGhhdCBhIHZpcnR1YWwgSUVURiBmZWVscyBpZGVudGljYWwgdG8g
YW4gaW4tcGVyc29uIElFVEYsIHNvIGxldCdzIGp1c3QgYWJhbmRvbiB0aGF0IGlkZWEgYW5kIGdl
dCBzdGFydGVkIG9uIG1ha2luZyBhIHZpcnR1YWwgSUVURiB0aGF0LCB3aGlsZSBkaWZmZXJlbnQs
IGlzIHN0aWxsIGEgc3VjY2Vzcy4KU291bmRzIGludGVyZXN0aW5nLCBpZiBzb21ldGhpbmcgb2Yg
YSBiaWcgbGVhcCB0byBhdHRlbXB0LiBJcyBhIGxhcmdlciB3aG9sbHkgdmlydHVhbCwgbXVsdGlw
bGUgV0cgaW50ZXJpbSBtZWV0aW5nIGEgbmV4dCBzdGVwIHRoZW4/CkJ0dyB3aGVyZSBkbyB3ZSBn
ZXQgdGhlIHZpcnR1YWwgVC1zaGlydD8gOykKVGltCgpPbiBUdWUsIEFwciAxMiwgMjAxNiBhdCA3
OjQzIEFNLCBUaW0gQ2hvd24gPHRqY0BlY3Muc290b24uYWMudWs+IHdyb3RlOgpIaSwKCgoKVG8g
bWluaW1pc2UgdGhlIGNoYW5jZXMgb2YgYSDigJhTaW5nYXBvcmXigJkgaGFwcGVuaW5nIGFnYWlu
IGl0IHdvdWxkIHNlZW0gcHJ1ZGVudCB0bwoKCgphKSByZS11c2UgcHJldmlvdXMgc3VjY2Vzc2Z1
bCBtZWV0aW5nIHZlbnVlcyBmb3IgdGhlIGJ1bGsgb2Ygb3VyIG1lZXRpbmdzIChzYXksIGV2ZXJ5
IDUgaW4gNiBtZWV0aW5ncyk7IHRoaXMgaXMgb25lIGNyaXRlcmlhIGZvciBtZWV0aW5nIHNlbGVj
dGlvbiBhcyBpdCBzdGFuZHMgYW55d2F5OyB0aGF0IGxpc3QgbWlnaHQgaW5jbHVkZSB2ZW51ZXMg
bGlrZSBQcmFndWUsIEJlcmxpbiwgVmFuY291dmVyLCBldGMuOyB3ZeKAmWQgbmVlZCB0byBiZSBj
bGVhciBpbiB3aGF0IOKAmHN1Y2Nlc3NmdWzigJkgbWVhbnMgLSB0aGUgbWVldGluZyBmZWVkYmFj
ayBmb3JtcyBwcm92aWRlIG9uZSBzdWNoIG1lY2hhbmlzbTsKCgoKYikgYmUgdHJhbnNwYXJlbnQg
YXQgYW4gZWFybHkgc3RhZ2UgYWJvdXQgd2hlcmUgbmV3IHZlbnVlcyBtaWdodCBiZSwgd2hldGhl
ciBieSBjb3VudHJ5IG9yIGNpdHksIHNvIHRoZXJlIGlzIGEgZmFpciBjaGFuY2UgZm9yIHBlb3Bs
ZSB0byBnaXZlIGZlZWRiYWNrOyBvZiBjb3Vyc2UsIGhvdyBzdWNoIGZlZWRiYWNrIGlzIHdlaWdo
ZWQgaXMgYW4gb3BlbiBxdWVzdGlvbiwgYnV0IGF0IGxlYXN0IGl0IHdvdWxkIGJlIHRoZXJlLCBh
bmQgdGhlIElBT0MgY2FuIHRoZW4gbWFrZSBhIGRlY2lzaW9uIOKAmGV5ZXMgd2lkZSBvcGVu4oCZ
LgoKCgpJbiBzdWNoIGEgc3lzdGVtLCBCdWVub3MgQWlyZXMgd291bGQgaGF2ZSBiZWVuIGEg4oCY
MSBpbiA24oCZIHZlbnVlLiBJbiB0aGF0IGxpZ2h0LCBJ4oCZZCBub3RlIHRoYXQgbWFueSBwZW9w
bGUgaGF2ZSBzYWlkIGhvdyBtdWNoIHRoZXkgZW5qb3llZCBCdWVub3MgQWlyZXMgYXMgYSBtZWV0
aW5nIHBsYWNlLiBBbmQgd2hpbGUgdGhlIElBT0MgcHJvYmFibHkgZmVlbCByYXRoZXIgZG93biBv
dmVyIHRoZSBjb21tZW50cyBhYm91dCBTaW5nYXBvcmUsIHRoZXkgc2hvdWxkIGJlIHByYWlzZWQg
Zm9yIGdvaW5nIG91dCBvbiBzb21ldGhpbmcgb2YgYSBsaW1iIGluIG1ha2luZyB0aGUgQnVlbm9z
IEFpcmVzIHNlbGVjdGlvbi4gKEFuZCBJ4oCZZCBhZGQgdGhhdCB0aGUgZW50aHVzaWFzbSBhbmQg
aGVscGZ1bG5lc3Mgb2YgdGhlIExBQ05JQyBob3N0cyB3YXMgYWxzbyBmYW50YXN0aWMuKQoKCgpJ
biB0ZXJtcyBvZiB2aXJ0dWFsIG1lZXRpbmdzLCBJ4oCZZCBzdWdnZXN0IHdlIHRyeSB0byBob2xk
IG1vcmUgaW50ZXJpbSBXRyBtZWV0aW5ncywgc29tZSBjb21wbGV0ZWx5IHZpcnR1YWxseSwgYW5k
IGxlYXJuIGhvdyB0byBtYWtlIHRob3NlIGJldHRlci4gSWYgd2UgY2FuIHJlZ3VsYXJseSBob2xk
IGdvb2QgcXVhbGl0eSB3aG9sbHkgdmlydHVhbCBpbnRlcmltIG1lZXRpbmdzLCB0aGVuIHdlIGNh
biBjb25zaWRlciB3aGV0aGVyIHRoZSBzYW1lIHRlY2hub2xvZ3kgbWlnaHQgYmUgdXNlZCBmb3Ig
YSBsYXJnZXIgbWVldGluZy4KCgoKVGltCgoKCj4gT24gMTIgQXByIDIwMTYsIGF0IDAwOjU0LCBU
ZWQgTGVtb24gPG1lbGxvbkBmdWd1ZS5jb20+IHdyb3RlOgoKPgoKPiBXaGlsZSBJIGRvIG5vdCB0
aGluayBpdCdzIHRydWUgdGhhdCB3ZSBjYW4gZW50aXJlbHkgZ2V0IGF3YXkgd2l0aG91dCBkb2lu
ZyBpbi1wZXJzb24gbWVldGluZ3MsIEkgZG8gYWdyZWUgd2l0aCB5b3UgdGhhdCB3ZSBjYW4gZG8g
YmV0dGVyIGF0IGRvaW5nIHJlbW90ZSBtZWV0aW5ncy7CoCDCoFBlcmhhcHMgd2Ugc2hvdWxkIGxl
dCB0aGlzIHVuZm9ydHVuYXRlIGV2ZW50IGRyaXZlIHVzIHRvIG1ha2UgdGhlIGF0dGVtcHQuCgo+
Cgo+IElmIHdlIHdlcmUgdG8gYXR0ZW1wdCBzdWNoIGEgdGhpbmcsIGhvdyBkbyB5b3UgdGhpbmsg
aXQgd291bGQgd29yaz8KCgoKCgoKCgoKCgo=

----_com.samsung.android.email_16206164285010
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: base64

PGh0bWw+PGhlYWQ+PG1ldGEgaHR0cC1lcXVpdj0iQ29udGVudC1UeXBlIiBjb250ZW50PSJ0ZXh0
L2h0bWw7IGNoYXJzZXQ9VVRGLTgiPjwvaGVhZD48Ym9keT48ZGl2PlJlbW92ZSBtZSBmcm9tIG1h
aWxpbmcgbGlzdCBvb29vPC9kaXY+PGRpdj48YnI+PC9kaXY+PGRpdj48YnI+PC9kaXY+PGRpdj48
YnI+PC9kaXY+PGRpdiBpZD0iY29tcG9zZXJfc2lnbmF0dXJlIj48ZGl2IHN0eWxlPSJmb250LXNp
emU6ODUlO2NvbG9yOiM1NzU3NTciPlNlbnQgZnJvbSBteSBTYW1zdW5nIEdhbGF4eSBzbWFydHBo
b25lLjwvZGl2PjwvZGl2PjxkaXYgc3R5bGU9ImZvbnQtc2l6ZToxMDAlO2NvbG9yOiMwMDAwMDAi
PjwhLS0gb3JpZ2luYWxNZXNzYWdlIC0tPjxkaXY+LS0tLS0tLS0gT3JpZ2luYWwgbWVzc2FnZSAt
LS0tLS0tLTwvZGl2PjxkaXY+RnJvbTogVGVkIExlbW9uICZsdDttZWxsb25AZnVndWUuY29tJmd0
OyA8L2Rpdj48ZGl2PkRhdGU6IDEyLzA0LzIwMTYgIDI6NDcgcG0gIChHTVQrMDE6MDApIDwvZGl2
PjxkaXY+VG86IFRpbSBDaG93biAmbHQ7dGpjQGVjcy5zb3Rvbi5hYy51ayZndDsgPC9kaXY+PGRp
dj5DYzogaWV0ZiAmbHQ7aWV0ZkBpZXRmLm9yZyZndDsgPC9kaXY+PGRpdj5TdWJqZWN0OiBSZTog
VmlydHVhbCBJRVRGcyAod2FzOiBSZTogQ29uY2VybnMgYWJvdXQgU2luZ2Fwb3JlKSA8L2Rpdj48
ZGl2Pjxicj48L2Rpdj48L2Rpdj48ZGl2IGRpcj0ibHRyIj5XaGVuIEkgaGFkIHRvIG1pc3MgUHJh
Z3VlLCBJIGp1c3QgdGltZS1zaGlmdGVkIGZvciB0aGUgd2Vlay4gJm5ic3A7IFdvdWxkbid0IHdv
cmsgZm9yIGV2ZXJ5b25lLCBidXQgaXQgc2VlbWVkIGZpbmUgdG8gbWUuPC9kaXY+PGRpdiBjbGFz
cz0iZ21haWxfZXh0cmEiPjxicj48ZGl2IGNsYXNzPSJnbWFpbF9xdW90ZSI+T24gVHVlLCBBcHIg
MTIsIDIwMTYgYXQgOTo0MiBBTSwgVGltIENob3duIDxzcGFuIGRpcj0ibHRyIj4mbHQ7PGEgaHJl
Zj0ibWFpbHRvOnRqY0BlY3Muc290b24uYWMudWsiIHRhcmdldD0iX2JsYW5rIj50amNAZWNzLnNv
dG9uLmFjLnVrPC9hPiZndDs8L3NwYW4+IHdyb3RlOjxicj48YmxvY2txdW90ZSBjbGFzcz0iZ21h
aWxfcXVvdGUiIHN0eWxlPSJtYXJnaW46MCAwIDAgLjhleDtib3JkZXItbGVmdDoxcHggI2NjYyBz
b2xpZDtwYWRkaW5nLWxlZnQ6MWV4Ij48ZGl2IHN0eWxlPSJ3b3JkLXdyYXA6YnJlYWstd29yZCI+
PGRpdj48c3BhbiBjbGFzcz0iIj48YmxvY2txdW90ZSB0eXBlPSJjaXRlIj48ZGl2Pk9uIDEyIEFw
ciAyMDE2LCBhdCAxNDoyMiwgVGVkIExlbW9uICZsdDs8YSBocmVmPSJtYWlsdG86bWVsbG9uQGZ1
Z3VlLmNvbSIgdGFyZ2V0PSJfYmxhbmsiPm1lbGxvbkBmdWd1ZS5jb208L2E+Jmd0OyB3cm90ZTo8
L2Rpdj48YnI+PGRpdj48ZGl2IGRpcj0ibHRyIj5UaGUgcHJvYmxlbSB3aXRoIGEgbGFyZ2VyIHZp
cnR1YWwgaW50ZXJpbSBpcyB0aGF0IGl0IGRvZXNuJ3QgcmVwbGFjZSBhbiBJRVRGLCBhbmQgc28g
eW91J3JlIGFkZGluZyB3b3JrbG9hZCBidXQgbm90IHN1YnRyYWN0aW5nIGFueSB3b3JrbG9hZC4g
Jm5ic3A7IEkgZG9uJ3Qgc2VlIHRoZSBwb2ludCBpbiB0aGF0LjwvZGl2PjwvZGl2PjwvYmxvY2tx
dW90ZT48ZGl2Pjxicj48L2Rpdj48L3NwYW4+PGRpdj5XZWxsLCB0aGVyZSBtYXkgYmUgYSBudW1i
ZXIgb2YgV0dzIHRoYXQgd2lzaCB0byBwcm9ncmVzcyB0aGVpciB3b3JrIGEgYml0IG1vcmUgYnJp
c2tseSwgb3IgaGF2ZSBvbmUgb3IgbW9yZSBzcGVjaWZpYyB0b3BpY3MgdGhhdCBuZWVkIHByb21w
dCBkaXNjdXNzaW9uLCBhbmQgdXNlIGFuIGludGVyaW0gbWVldGluZyB0byBhY2hpZXZlIHRoYXQu
IFNvIEnigJltIG5vdCBzdXJlIGl04oCZcyBhZGRpbmcgdG8gd29ya2xvYWQsIHJhdGhlciBpdCBt
YXkgYWxsb3cgdXMgdG8gYmUgbW9yZSBlZmZpY2llbnQuJm5ic3A7IEJ1dCB0aGUgbWFpbiBpc3N1
ZSB3aXRoIGFueSB2aXJ0dWFsIG1lZXRpbmcgaXMgdGltZXpvbmVzLiBUaGVyZeKAmXMgcmVhbGx5
IG5vIHdheSB0byBkZWFsIHdpdGggdGhhdCBwcm9ibGVtIHNhdGlzZmFjdG9yaWx5LiZuYnNwOzwv
ZGl2PjxzcGFuIGNsYXNzPSJIT0VuWmIiPjxmb250IGNvbG9yPSIjODg4ODg4Ij48ZGl2Pjxicj48
L2Rpdj5UaW08L2ZvbnQ+PC9zcGFuPjwvZGl2PjxzcGFuIGNsYXNzPSIiPjxkaXY+PGJyPjxibG9j
a3F1b3RlIHR5cGU9ImNpdGUiPjxkaXY+PGRpdiBjbGFzcz0iZ21haWxfZXh0cmEiPjxicj48ZGl2
IGNsYXNzPSJnbWFpbF9xdW90ZSI+T24gVHVlLCBBcHIgMTIsIDIwMTYgYXQgODozMCBBTSwgVGlt
IENob3duIDxzcGFuIGRpcj0ibHRyIj4mbHQ7PGEgaHJlZj0ibWFpbHRvOnRqY0BlY3Muc290b24u
YWMudWsiIHRhcmdldD0iX2JsYW5rIj50amNAZWNzLnNvdG9uLmFjLnVrPC9hPiZndDs8L3NwYW4+
IHdyb3RlOjxicj48YmxvY2txdW90ZSBjbGFzcz0iZ21haWxfcXVvdGUiIHN0eWxlPSJtYXJnaW46
MCAwIDAgLjhleDtib3JkZXItbGVmdDoxcHggI2NjYyBzb2xpZDtwYWRkaW5nLWxlZnQ6MWV4Ij48
ZGl2IHN0eWxlPSJ3b3JkLXdyYXA6YnJlYWstd29yZCI+PGRpdj48YmxvY2txdW90ZSB0eXBlPSJj
aXRlIj48ZGl2Pk9uIDEyIEFwciAyMDE2LCBhdCAxMjo0OSwgVGVkIExlbW9uICZsdDs8YSBocmVm
PSJtYWlsdG86bWVsbG9uQGZ1Z3VlLmNvbSIgdGFyZ2V0PSJfYmxhbmsiPm1lbGxvbkBmdWd1ZS5j
b208L2E+Jmd0OyB3cm90ZTo8L2Rpdj48YnI+PGRpdj48ZGl2IGRpcj0ibHRyIj5BZ3JlZSBhYm91
dCBCdWVub3MgQWlyZXMuICZuYnNwOyBXZSBhbHJlYWR5IGRvIGV4Y2VsbGVudCB2aXJ0dWFsIGlu
dGVyaW1zLS1JIHRoaW5rIGlmIHlvdXIgc3RhbmRhcmQgZm9yIHdoZXRoZXIgd2UgY2FuIGRvIGEg
dmlydHVhbCBJRVRGIGlzIHRoYXQgdmlydHVhbCBpbnRlcmltcyB3b3JrLCB3ZSBhcmUgYWxyZWFk
eSB0aGVyZS48ZGl2Pjxicj48L2Rpdj48ZGl2PkkgdGhpbmsgdGhhdCBpZiB3ZSB3YW50IHRvIHRl
c3QgdGhpcyBpZGVhLCB3aGF0IHdlIG5lZWQgdG8gZG8gaXMgZGVzaWduYXRlIHNvbWUgZnV0dXJl
IElFVEYgdmlydHVhbCBfbm93XywgYW5kIHRoZW4gc3RhcnQgcHJlcGFyaW5nLCByYXRoZXIgdGhh
biBzYXkgIm9oLCB3ZSBzaG91bGQgZG8gYSB2aXJ0dWFsIiBhbmQgdGhlbiBkaXRoZXIgYWJvdXQg
d2hlbiB3ZSBtaWdodCBiZSByZWFkeS4gJm5ic3A7IFdlIHdpbGwgbmV2ZXIgYmUgc28gcmVhZHkg
dGhhdCBhIHZpcnR1YWwgSUVURiBmZWVscyBpZGVudGljYWwgdG8gYW4gaW4tcGVyc29uIElFVEYs
IHNvIGxldCdzIGp1c3QgYWJhbmRvbiB0aGF0IGlkZWEgYW5kIGdldCBzdGFydGVkIG9uIG1ha2lu
ZyBhIHZpcnR1YWwgSUVURiB0aGF0LCB3aGlsZSBkaWZmZXJlbnQsIGlzIHN0aWxsIGEgc3VjY2Vz
cy48L2Rpdj48L2Rpdj48L2Rpdj48L2Jsb2NrcXVvdGU+PGRpdj48YnI+PC9kaXY+PGRpdj5Tb3Vu
ZHMgaW50ZXJlc3RpbmcsIGlmIHNvbWV0aGluZyBvZiBhIGJpZyBsZWFwIHRvIGF0dGVtcHQuIElz
IGEgbGFyZ2VyIHdob2xseSB2aXJ0dWFsLCBtdWx0aXBsZSBXRyBpbnRlcmltIG1lZXRpbmcgYSBu
ZXh0IHN0ZXAgdGhlbj88L2Rpdj48ZGl2Pjxicj48L2Rpdj48ZGl2PkJ0dyB3aGVyZSBkbyB3ZSBn
ZXQgdGhlIHZpcnR1YWwgVC1zaGlydD8gOyk8L2Rpdj48ZGl2Pjxicj48L2Rpdj5UaW08L2Rpdj48
ZGl2Pjxicj48YmxvY2txdW90ZSB0eXBlPSJjaXRlIj48ZGl2PjxkaXYgY2xhc3M9ImdtYWlsX2V4
dHJhIj48YnI+PGRpdiBjbGFzcz0iZ21haWxfcXVvdGUiPk9uIFR1ZSwgQXByIDEyLCAyMDE2IGF0
IDc6NDMgQU0sIFRpbSBDaG93biA8c3BhbiBkaXI9Imx0ciI+Jmx0OzxhIGhyZWY9Im1haWx0bzp0
amNAZWNzLnNvdG9uLmFjLnVrIiB0YXJnZXQ9Il9ibGFuayI+dGpjQGVjcy5zb3Rvbi5hYy51azwv
YT4mZ3Q7PC9zcGFuPiB3cm90ZTo8YnI+PGJsb2NrcXVvdGUgY2xhc3M9ImdtYWlsX3F1b3RlIiBz
dHlsZT0ibWFyZ2luOjAgMCAwIC44ZXg7Ym9yZGVyLWxlZnQ6MXB4ICNjY2Mgc29saWQ7cGFkZGlu
Zy1sZWZ0OjFleCI+SGksPGJyPgo8YnI+ClRvIG1pbmltaXNlIHRoZSBjaGFuY2VzIG9mIGEg4oCY
U2luZ2Fwb3Jl4oCZIGhhcHBlbmluZyBhZ2FpbiBpdCB3b3VsZCBzZWVtIHBydWRlbnQgdG88YnI+
Cjxicj4KYSkgcmUtdXNlIHByZXZpb3VzIHN1Y2Nlc3NmdWwgbWVldGluZyB2ZW51ZXMgZm9yIHRo
ZSBidWxrIG9mIG91ciBtZWV0aW5ncyAoc2F5LCBldmVyeSA1IGluIDYgbWVldGluZ3MpOyB0aGlz
IGlzIG9uZSBjcml0ZXJpYSBmb3IgbWVldGluZyBzZWxlY3Rpb24gYXMgaXQgc3RhbmRzIGFueXdh
eTsgdGhhdCBsaXN0IG1pZ2h0IGluY2x1ZGUgdmVudWVzIGxpa2UgUHJhZ3VlLCBCZXJsaW4sIFZh
bmNvdXZlciwgZXRjLjsgd2XigJlkIG5lZWQgdG8gYmUgY2xlYXIgaW4gd2hhdCDigJhzdWNjZXNz
ZnVs4oCZIG1lYW5zIC0gdGhlIG1lZXRpbmcgZmVlZGJhY2sgZm9ybXMgcHJvdmlkZSBvbmUgc3Vj
aCBtZWNoYW5pc207PGJyPgo8YnI+CmIpIGJlIHRyYW5zcGFyZW50IGF0IGFuIGVhcmx5IHN0YWdl
IGFib3V0IHdoZXJlIG5ldyB2ZW51ZXMgbWlnaHQgYmUsIHdoZXRoZXIgYnkgY291bnRyeSBvciBj
aXR5LCBzbyB0aGVyZSBpcyBhIGZhaXIgY2hhbmNlIGZvciBwZW9wbGUgdG8gZ2l2ZSBmZWVkYmFj
azsgb2YgY291cnNlLCBob3cgc3VjaCBmZWVkYmFjayBpcyB3ZWlnaGVkIGlzIGFuIG9wZW4gcXVl
c3Rpb24sIGJ1dCBhdCBsZWFzdCBpdCB3b3VsZCBiZSB0aGVyZSwgYW5kIHRoZSBJQU9DIGNhbiB0
aGVuIG1ha2UgYSBkZWNpc2lvbiDigJhleWVzIHdpZGUgb3BlbuKAmS48YnI+Cjxicj4KSW4gc3Vj
aCBhIHN5c3RlbSwgQnVlbm9zIEFpcmVzIHdvdWxkIGhhdmUgYmVlbiBhIOKAmDEgaW4gNuKAmSB2
ZW51ZS4gSW4gdGhhdCBsaWdodCwgSeKAmWQgbm90ZSB0aGF0IG1hbnkgcGVvcGxlIGhhdmUgc2Fp
ZCBob3cgbXVjaCB0aGV5IGVuam95ZWQgQnVlbm9zIEFpcmVzIGFzIGEgbWVldGluZyBwbGFjZS4g
QW5kIHdoaWxlIHRoZSBJQU9DIHByb2JhYmx5IGZlZWwgcmF0aGVyIGRvd24gb3ZlciB0aGUgY29t
bWVudHMgYWJvdXQgU2luZ2Fwb3JlLCB0aGV5IHNob3VsZCBiZSBwcmFpc2VkIGZvciBnb2luZyBv
dXQgb24gc29tZXRoaW5nIG9mIGEgbGltYiBpbiBtYWtpbmcgdGhlIEJ1ZW5vcyBBaXJlcyBzZWxl
Y3Rpb24uIChBbmQgSeKAmWQgYWRkIHRoYXQgdGhlIGVudGh1c2lhc20gYW5kIGhlbHBmdWxuZXNz
IG9mIHRoZSBMQUNOSUMgaG9zdHMgd2FzIGFsc28gZmFudGFzdGljLik8YnI+Cjxicj4KSW4gdGVy
bXMgb2YgdmlydHVhbCBtZWV0aW5ncywgSeKAmWQgc3VnZ2VzdCB3ZSB0cnkgdG8gaG9sZCBtb3Jl
IGludGVyaW0gV0cgbWVldGluZ3MsIHNvbWUgY29tcGxldGVseSB2aXJ0dWFsbHksIGFuZCBsZWFy
biBob3cgdG8gbWFrZSB0aG9zZSBiZXR0ZXIuIElmIHdlIGNhbiByZWd1bGFybHkgaG9sZCBnb29k
IHF1YWxpdHkgd2hvbGx5IHZpcnR1YWwgaW50ZXJpbSBtZWV0aW5ncywgdGhlbiB3ZSBjYW4gY29u
c2lkZXIgd2hldGhlciB0aGUgc2FtZSB0ZWNobm9sb2d5IG1pZ2h0IGJlIHVzZWQgZm9yIGEgbGFy
Z2VyIG1lZXRpbmcuPGJyPgo8c3Bhbj48Zm9udCBjb2xvcj0iIzg4ODg4OCI+PGJyPgpUaW08YnI+
CjwvZm9udD48L3NwYW4+PGRpdj48ZGl2Pjxicj4KJmd0OyBPbiAxMiBBcHIgMjAxNiwgYXQgMDA6
NTQsIFRlZCBMZW1vbiAmbHQ7PGEgaHJlZj0ibWFpbHRvOm1lbGxvbkBmdWd1ZS5jb20iIHRhcmdl
dD0iX2JsYW5rIj5tZWxsb25AZnVndWUuY29tPC9hPiZndDsgd3JvdGU6PGJyPgomZ3Q7PGJyPgom
Z3Q7IFdoaWxlIEkgZG8gbm90IHRoaW5rIGl0J3MgdHJ1ZSB0aGF0IHdlIGNhbiBlbnRpcmVseSBn
ZXQgYXdheSB3aXRob3V0IGRvaW5nIGluLXBlcnNvbiBtZWV0aW5ncywgSSBkbyBhZ3JlZSB3aXRo
IHlvdSB0aGF0IHdlIGNhbiBkbyBiZXR0ZXIgYXQgZG9pbmcgcmVtb3RlIG1lZXRpbmdzLiZuYnNw
OyAmbmJzcDtQZXJoYXBzIHdlIHNob3VsZCBsZXQgdGhpcyB1bmZvcnR1bmF0ZSBldmVudCBkcml2
ZSB1cyB0byBtYWtlIHRoZSBhdHRlbXB0Ljxicj4KJmd0Ozxicj4KJmd0OyBJZiB3ZSB3ZXJlIHRv
IGF0dGVtcHQgc3VjaCBhIHRoaW5nLCBob3cgZG8geW91IHRoaW5rIGl0IHdvdWxkIHdvcms/PGJy
Pgo8YnI+CjwvZGl2PjwvZGl2PjwvYmxvY2txdW90ZT48L2Rpdj48YnI+PC9kaXY+CjwvZGl2Pjwv
YmxvY2txdW90ZT48L2Rpdj48YnI+PC9kaXY+PC9ibG9ja3F1b3RlPjwvZGl2Pjxicj48L2Rpdj4K
PC9kaXY+PC9ibG9ja3F1b3RlPjwvZGl2Pjxicj48L3NwYW4+PC9kaXY+PC9ibG9ja3F1b3RlPjwv
ZGl2Pjxicj48L2Rpdj4KPC9ib2R5PjwvaHRtbD4=

----_com.samsung.android.email_16206164285010--


From nobody Wed Apr 13 00:18:06 2016
Return-Path: <harald@alvestrand.no>
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 A3FDF12E318 for <ietf@ietfa.amsl.com>; Wed, 13 Apr 2016 00:18:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.196
X-Spam-Level: 
X-Spam-Status: No, score=-5.196 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.996] 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 QD-z9ydY3rX1 for <ietf@ietfa.amsl.com>; Wed, 13 Apr 2016 00:18:02 -0700 (PDT)
Received: from mork.alvestrand.no (mork.alvestrand.no [158.38.152.117]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 18DEE12E317 for <ietf@ietf.org>; Wed, 13 Apr 2016 00:17:59 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mork.alvestrand.no (Postfix) with ESMTP id 828447C7CD2 for <ietf@ietf.org>; Wed, 13 Apr 2016 09:17:57 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at alvestrand.no
Received: from mork.alvestrand.no ([127.0.0.1]) by localhost (mork.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PVshyFhZJyCu for <ietf@ietf.org>; Wed, 13 Apr 2016 09:17:55 +0200 (CEST)
Received: from [IPv6:2001:470:de0a:1:1022:9286:2683:530e] (unknown [IPv6:2001:470:de0a:1:1022:9286:2683:530e]) by mork.alvestrand.no (Postfix) with ESMTPSA id B1AEE7C77C6 for <ietf@ietf.org>; Wed, 13 Apr 2016 09:17:55 +0200 (CEST)
Subject: Re: Remote only meetings? [Re: Concerns about Singapore]
To: ietf@ietf.org
References: <570AB3AF.2050401@gmail.com> <87twj99c6w.fsf@tops.chopps.org> <CAKe6YvMyp-DyeDwpPY6KYmbDbnpgnvVk_cUStnA32wmgDWcz3w@mail.gmail.com> <BBF5DDFE515C3946BC18D733B20DAD233A62AA18@XMB122CNC.rim.net> <20160411104519.GA19092@gsp.org> <3F48466D-390C-4C18-B958-732AE3E46FF1@gmail.com> <20160411223403.GA6743@gsp.org> <87twj7eon7.fsf@tops.chopps.org> <20160412110839.GA20488@gsp.org> <8760vn82f2.fsf@tops.chopps.org> <20160412124639.GA27223@gsp.org> <570DAA2F.1040007@gmail.com>
From: Harald Alvestrand <harald@alvestrand.no>
Message-ID: <570DF2A3.1050902@alvestrand.no>
Date: Wed, 13 Apr 2016 09:17:55 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0
MIME-Version: 1.0
In-Reply-To: <570DAA2F.1040007@gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/ldYd0kDyfDX81cCNrwdKpBw5-LU>
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, 13 Apr 2016 07:18:05 -0000

Den 13. april 2016 04:08, skrev Brian E Carpenter:
> Cherry-picking a few points:
> On 13/04/2016 00:46, Rich Kulawiec wrote:
> ...
>> > And the difficulties/expense of travel are only going to get worse
>> > for the forseeable future: they're not going to get better.
> That is indisputable.

Difficulties, yes. Expense - not so much.

http://www.rita.dot.gov/bts/airfares/programs/economics_and_finance/air_travel_price_index/html/AnnualFares.html

Average US domestic itinerary cost has gone down 30% over the last 20
years (inflation-adjusted); they seem to have hit a floor after 2009.

Note: Virtual interims tend towards more frequent meetings. Once you
pass the once-a-month level and move towards the once-a-week level, that
form of participation *severely* restricts the ability to participate of
the timezone-challenged compared to an email-heavy style of interaction.


From nobody Wed Apr 13 01:33:38 2016
Return-Path: <sm@resistor.net>
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 502E712DF51 for <ietf@ietfa.amsl.com>; Wed, 13 Apr 2016 01:33:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.79
X-Spam-Level: 
X-Spam-Status: No, score=-1.79 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, RCVD_IN_DNSWL_NONE=-0.0001, T_DKIM_INVALID=0.01] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=opendkim.org header.b=Mi5+7MVK; dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=resistor.net header.b=WaC4BNTC
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 SI9ijh7ptXJv for <ietf@ietfa.amsl.com>; Wed, 13 Apr 2016 01:33:35 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 2050712D0A9 for <ietf@ietf.org>; Wed, 13 Apr 2016 01:33:35 -0700 (PDT)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id u3D8XNHG024386 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 13 Apr 2016 01:33:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1460536412; x=1460622812; bh=510SPMxihDodVyf96aimERuJbDblDICZVb46kH4Ku40=; h=Date:To:From:Subject:In-Reply-To:References; b=Mi5+7MVKjLWJ5EJp4ZFrrLOcyqrdt8xxkU+4ckk4Hbe3wY7pxCw1UTxHHUMinJvwi JYUCTGbvDHiskJNHqokjaKdgLP0P3mZNFlBcpISQRqY1V9BlJ3I94w7v8iXaHi97/H oWBAFXQUKkTt7tAFh1jOGioRLfQvD+JUWXm7gRtI=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1460536412; x=1460622812; i=@resistor.net; bh=510SPMxihDodVyf96aimERuJbDblDICZVb46kH4Ku40=; h=Date:To:From:Subject:In-Reply-To:References; b=WaC4BNTCFMPvTXuLa97dqsjAhNgzDu+AqGCMVYEwVNB7Cy3BuJTbhCabbz9yYWCaJ APyuguoa2M5r3K1H/xz4vDI9OVM+TJQJLREzZRVlbjI2Db4U5Z3ziuQAqfmNhigYoP DG7geOXdRZPCH3W251vBchGc5oHO/Ccceg1CwSpg=
Message-Id: <6.2.5.6.2.20160413002237.0f592e80@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Wed, 13 Apr 2016 01:30:21 -0700
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, Ted Lemon <mellon@fugue.com>, Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>, ietf@ietf.org
From: SM <sm@resistor.net>
Subject: Re: Transparency of IAOC
In-Reply-To: <570D5B51.8090307@gmail.com>
References: <6.2.5.6.2.20160412031201.0da034e8@elandnews.com> <6.2.5.6.2.20160412114424.0e7061b0@resistor.net> <570D5B51.8090307@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"; format=flowed
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/RaBePJJk59Lb4zl1_-LknBkub8U>
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, 13 Apr 2016 08:33:37 -0000

Hi Brian, Ted, Spencer,
At 13:32 12-04-2016, Brian E Carpenter wrote:
>Of course it is. But (compared to the IESG) the IAOC does deal with a
>comparatively large fraction of issues that have confidential aspects -

I'll skip this as there is a comment at=20
http://www.ietf.org/mail-archive/web/ietf/current/msg97822.html

At 13:33 12-04-2016, Ted Lemon wrote:
>I feel I can speak as an authority on this topic=20
>when I say that there is zero chance that this=20
>is a problem. =C2  If the IAOC do not always do=20
>what we want, it is because (a) that is=20
>impossible, since there is no "we" that is both=20
>in agreement and also representative of the=20
>wishes of all IETF participants and (b) I know=20
>everybody on the IAOC and they just don't behave=20
>as if they think complaining by IESG people is a problem.

Ok.

At 13:51 12-04-2016, Spencer Dawkins at IETF wrote:
>SM, if you're talking about people in=20
>"leadership" (is that what we are?) asking=20
>questions of the IAOC on the IETF mailing list, you may very well be right.

The term "leadership" was used in the message at=20
https://www.ietf.org/mail-archive/web/ietf/current/msg77723.html

>But I do drop notes to the IAOC directly, either=20
>to the IAD or to the overall IAOC, and I don't=20
>know how anyone in the broader community would know that I've done that.

Ok.

Regards,
-sm=20


From nobody Wed Apr 13 02:49:23 2016
Return-Path: <tjc@ecs.soton.ac.uk>
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 C1ED412DBFD for <ietf@ietfa.amsl.com>; Wed, 13 Apr 2016 02:49:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.517
X-Spam-Level: 
X-Spam-Status: No, score=-4.517 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.996, SPF_NEUTRAL=0.779] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ecs.soton.ac.uk
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 YG45sLD0JuKc for <ietf@ietfa.amsl.com>; Wed, 13 Apr 2016 02:49:20 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [IPv6:2001:630:d0:f102::25e]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5C8A412D813 for <ietf@ietf.org>; Wed, 13 Apr 2016 02:49:19 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (localhost [127.0.0.1]) by falcon.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id u3D9nE4H020342; Wed, 13 Apr 2016 10:49:14 +0100
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk u3D9nE4H020342
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=201304; t=1460540954; bh=WMCgiPOBysbob5CaRrSaEQtS+Xs=; h=Mime-Version:Subject:From:In-Reply-To:Date:Cc:References:To; b=4/0D7ydMeq0YbFfBcbDU+v+MNCL/Wl5Akgf0T5vRUAfaYBeF0e9ZKTH+ej3S7Xr5L fI0eY55pw/Ph7FgiRr8kIxcQ3lw16ly/INUrtEEZPi1ixM9B8GJqgE8g1NtMpBy7HP nUNiqe6nIPxDvl8bEz09+zoXeRnfKBTRkHTLRjD8=
Received: from gander.ecs.soton.ac.uk ([2001:630:d0:f102:250:56ff:fea0:401]) by falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [2001:630:d0:f102:250:56ff:fea0:68da]) envelope-from <tjc@ecs.soton.ac.uk> with ESMTP (valid=N/A) id s3CAnE17396026281g ret-id none; Wed, 13 Apr 2016 10:49:14 +0100
Received: from 20010a88d51011.ipv6.customer.clara.net (20010a88d51011.ipv6.customer.clara.net [IPv6:2001:a88:d510:1101:a93e:5914:9e35:ffe3] (may be forged)) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id u3D9n4FN024345 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 13 Apr 2016 10:49:05 +0100
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 9.2 \(3112\))
Subject: Re: UK blacklist (Re: Concerns about Singapore and other places)
From: Tim Chown <tjc@ecs.soton.ac.uk>
In-Reply-To: <570D641D.6070509@alvestrand.no>
Date: Wed, 13 Apr 2016 10:49:04 +0100
Content-Transfer-Encoding: quoted-printable
Message-ID: <EMEW3|e2a57eeabaa4f6086ac8a48cd4b4e53ds3CAnE03tjc|ecs.soton.ac.uk|66D9FA23-9D92-4645-B7AF-CC649CAF4A5F@ecs.soton.ac.uk>
References: <alpine.OSX.2.01.1604100736080.45987@rabdullah.local> <20160410181958.58762.qmail@ary.lan> <CAMm+LwgE_oOJSCjgsMGTSMDV2-LsUzw1zW3-+N_VCtE14m26BA@mail.gmail.com> <CAPt1N1nLWrVqGpPh+h=Ano6PJyw2ZRaroiAMgG4RDKTFV7rkpA@mail.gmail.com> <570D641D.6070509@alvestrand.no> <66D9FA23-9D92-4645-B7AF-CC649CAF4A5F@ecs.soton.ac.uk>
To: Harald Alvestrand <harald@alvestrand.no>
X-Mailer: Apple Mail (2.3112)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=s3CAnE173960262800; tid=s3CAnE17396026281g; client=relay,forged,no_ptr,ipv6; mail=; rcpt=; nrcpt=2:0; fails=0
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: u3D9nE4H020342
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/TmqoHV3ldSCNHJOqIalSFfXJ8SE>
Cc: 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, 13 Apr 2016 09:49:22 -0000

> On 12 Apr 2016, at 22:09, Harald Alvestrand <harald@alvestrand.no> =
wrote:
>=20
> Den 12. april 2016 18:52, skrev Ted Lemon:
>> The UK filter is an "opt out" filter, and I assume that we (the IETF)
>> opted out.   Even the "opt out" blocking is voluntary at present--an =
ISP
>> is not required by law to have a filter, but in practice the big ones =
do.
>=20
>=20
> The particular case that made the blacklist famous in at least some
> fora, and exposed quite a bit on how it worked:
>=20
> https://en.wikipedia.org/wiki/Internet_Watch_Foundation_and_Wikipedia
>=20
> "the action also had some indirect effects on Wikipedia, namely
> temporarily preventing all editors using said ISPs in the UK from
> contributing to any page of the encyclopaedia, and preventing =
anonymous
> edits from these ISPs while the URL remained on the blacklist. This =
was
> described by the IWF as unintended "collateral damage".[7] This was =
due
> to the proxies used to access Wikipedia, as Wikipedia implements a
> blocking policy whereby contributors can be blocked if they vandalise
> the encyclopaedia. Therefore, all vandalism coming from one ISP would =
be
> directed through one proxy=E2=80=94hence one IP=E2=80=94and all of the =
ISP's customers
> using that proxy would be barred from editing.=E2=80=9D

The broader context is here (with all the usual caveats over Wikipedia =
accuracy):

https://en.wikipedia.org/wiki/Internet_censorship_in_the_United_Kingdom

See the section on the Introduction of Cleanfeed.

The other controversy, as mentioned in the link above, is that in 2011 a =
judge ordered Cleanfeed be used to block access to a p2p filesharing =
system called Newzbin2, hence concern over creeping and unaccountable =
scope of filtering (because the filter list is not viewable due to the =
primary use of the system), see =
http://www.bbc.co.uk/news/technology-14322957.=20

Tim=


From nobody Wed Apr 13 03:06:25 2016
Return-Path: <fanf2@hermes.cam.ac.uk>
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 2508F12E41A for <ietf@ietfa.amsl.com>; Wed, 13 Apr 2016 03:06:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.916
X-Spam-Level: 
X-Spam-Status: No, score=-2.916 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.996, SPF_HELO_PASS=-0.001] 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 BX3rLZkHHoc9 for <ietf@ietfa.amsl.com>; Wed, 13 Apr 2016 03:06:19 -0700 (PDT)
Received: from ppsw-43.csi.cam.ac.uk (ppsw-43.csi.cam.ac.uk [131.111.8.143]) (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 9858A12E418 for <ietf@ietf.org>; Wed, 13 Apr 2016 03:06:19 -0700 (PDT)
X-Cam-AntiVirus: no malware found
X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/
Received: from grey.csi.cam.ac.uk ([131.111.57.57]:32842) by ppsw-43.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.159]:25) with esmtpsa (PLAIN:fanf2) (TLSv1:ECDHE-RSA-AES256-SHA:256) id 1aqHgb-00079v-np (Exim 4.86_36-e07b163) (return-path <fanf2@hermes.cam.ac.uk>); Wed, 13 Apr 2016 11:06:13 +0100
Date: Wed, 13 Apr 2016 11:06:08 +0100
From: Tony Finch <dot@dotat.at>
X-X-Sender: fanf2@grey.csi.cam.ac.uk
To: John R Levine <johnl@taugh.com>
Subject: Re: Concerns about Singapore and other places
In-Reply-To: <alpine.OSX.2.11.1604121614250.2223@ary.lan>
Message-ID: <alpine.DEB.2.11.1604131103410.5646@grey.csi.cam.ac.uk>
References: <alpine.OSX.2.01.1604100736080.45987@rabdullah.local> <20160410181958.58762.qmail@ary.lan> <CAMm+LwgE_oOJSCjgsMGTSMDV2-LsUzw1zW3-+N_VCtE14m26BA@mail.gmail.com> <CAPt1N1nLWrVqGpPh+h=Ano6PJyw2ZRaroiAMgG4RDKTFV7rkpA@mail.gmail.com> <alpine.OSX.2.11.1604121614250.2223@ary.lan>
User-Agent: Alpine 2.11 (DEB 23 2013-08-11)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: Tony Finch <fanf2@hermes.cam.ac.uk>
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/ZJYuHVCVm3GUxNCFcLqa1AtcAlI>
Cc: Phillip Hallam-Baker <phill@hallambaker.com>, IETF Discussion Mailing List <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, 13 Apr 2016 10:06:24 -0000

John R Levine <johnl@taugh.com> wrote:

> > The UK filter is an "opt out" filter, and I assume that we (the IETF) opted
> > out. ...
>
> This isn't the parental filter, this is the child porn filter, which I am
> fairly sure is mandatory, at last on consumer ISPs.

As I understand it this kind of filtering only applies to the largest
consumer ISPs. We don't have any filtering of that kind on the academic
network I help to look after, for example. The IETF network would not have
any filtering unless the IETF NOC put it in.

Tony.
-- 
f.anthony.n.finch  <dot@dotat.at>  http://dotat.at/  -  I xn--zr8h punycode
South Utsire: Easterly 4 or 5 decreasing 3. Moderate at first in west,
otherwise slight. Showers. Good.


From nobody Wed Apr 13 04:12:58 2016
Return-Path: <daedulus@btconnect.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 7AF2612DB7B for <ietf@ietfa.amsl.com>; Wed, 13 Apr 2016 04:12:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=btconnect.onmicrosoft.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 7LCloa78qmZA for <ietf@ietfa.amsl.com>; Wed, 13 Apr 2016 04:12:53 -0700 (PDT)
Received: from emea01-am1-obe.outbound.protection.outlook.com (mail-am1on0795.outbound.protection.outlook.com [IPv6:2a01:111:f400:fe00::795]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C23F012DD9D for <ietf@ietf.org>; Wed, 13 Apr 2016 04:12:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=btconnect.onmicrosoft.com; s=selector1-btconnect-com; h=From:To:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=IpuKGNED+1ZAjPRYzLdZbMZrx4nETASC6szxSwRUjv8=; b=KUtAWl8FcTzSe35qOcK1awITRIH9FwO0NtXe5FCiA35LdOD9lIUbHJjrIlwmz18mKD18DxCfzukHAmnTTQN+7NxzNcltNtkkScBeiK+hfDvzD1YzXYBejEVAdGgWPMn94Mm6Mm9btOmrOd1Yk58QEfYCHK4ibtusil2Vd4X3m1c=
Authentication-Results: dotat.at; dkim=none (message not signed) header.d=none;dotat.at; dmarc=none action=none header.from=btconnect.com;
Received: from pc6 (86.171.1.17) by HE1PR07MB1564.eurprd07.prod.outlook.com (10.169.123.14) with Microsoft SMTP Server (TLS) id 15.1.466.12; Wed, 13 Apr 2016 11:12:29 +0000
Message-ID: <020c01d19574$f0d9b700$4001a8c0@gateway.2wire.net>
From: tom p. <daedulus@btconnect.com>
To: Tony Finch <dot@dotat.at>, John R Levine <johnl@taugh.com>
References: <alpine.OSX.2.01.1604100736080.45987@rabdullah.local> <20160410181958.58762.qmail@ary.lan> <CAMm+LwgE_oOJSCjgsMGTSMDV2-LsUzw1zW3-+N_VCtE14m26BA@mail.gmail.com> <CAPt1N1nLWrVqGpPh+h=Ano6PJyw2ZRaroiAMgG4RDKTFV7rkpA@mail.gmail.com> <alpine.OSX.2.11.1604121614250.2223@ary.lan> <alpine.DEB.2.11.1604131103410.5646@grey.csi.cam.ac.uk>
Subject: Re: Concerns about Singapore and other places
Date: Wed, 13 Apr 2016 12:09:18 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Originating-IP: [86.171.1.17]
X-ClientProxiedBy: HE1PR08CA0015.eurprd08.prod.outlook.com (10.161.112.25) To HE1PR07MB1564.eurprd07.prod.outlook.com (10.169.123.14)
X-MS-Office365-Filtering-Correlation-Id: a4509b28-ede2-4924-03b4-08d3638c811f
X-Microsoft-Exchange-Diagnostics: 1; HE1PR07MB1564; 2:1eqxUiW0ArGnCE6tfjUet4FScOo5Fxg30oqLxq3aQiLQSwBNLbrDBcNvtIez3u8oCoBfSGa4+CT3sOvcPjfr4kFlWefdB3oChPvVuWajtVfYrte1SBGUqXZfWgFfvMxRZ1sLfTbSD4N/rwCs8OsbC68+R7/1uQ5meUHxUflD/hnPqwMVIkv1AiSjKT/wAtIU; 3:gVY9pIpcyLjs4cYpiL/vLGc5QO4M5PBChz6r5J0MmU9RI7tqDqpxr/ZTioVi4yL20spP8RMV1gakOIANFx6lNXuoOwpyHswBRZURjmY8i2jvj9S5tZ9BPEbPUd5ZHEhP
X-Microsoft-Antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:HE1PR07MB1564;
X-Microsoft-Exchange-Diagnostics: 1; HE1PR07MB1564; 25:LEiCRrKmjBg2Jx+imQ/liR7KISDYyjkQtYbaaFZATpTjEXXFQvtJ2IyhMf47B0X4l9r/H6WMfGhePa5ILY7vGVlmxkyE2W6mqseza5Yby7EO5EIOQsK1ivrfd0dcScHJjNbV4fCnRYgaHELcTP/k6qSbNc2WsSP1ozVxRNQIybtQ8GArfA0sFf7bHllQ7XOf4jdh3Olc7dB/WTvzWQ8MRsLbvhHyjtrpsLTKhyJH6v3+BeNv5/BG4YzeL9I7Q8Naz5VIl0LgNxu2s2+RY7hh5yoUoxMNtZls+ycJ0qGS8E0ucyDoRwA/14JVzXecI2u8IkhL/mEA9f3XspgEdrwYMrAx27RNefzzM8ga2VCmoNAJzriFISfRPGdEXaGYQwJBbqIUt2RbAfxXItAxH0yn0r15wnuZmkmuMUw+Qh0x5YZTrKXU6+8n5RC9Y6vp+ao406+HZFfiKZtFUrhmKNcDx87r2aiKWmc1qyRPZOJLwSvNSaOydhcqNEpm6Pk4x++YB3nF/R64SGvElvZiDIIYRj0vJ7hKkBVfetrOzqgVF6M3SnjLAVRsP1hCGOrodR18npLbOl31RX+VhyvP4q/gOiPZZ8PswZKeEJZP4vUj8lpTWogMtaOF4biP29SXOIuNUuDKoKYS0Ej8VgcB3Srx+2x/LWh3bTkLHPuHre6S3r3HU8JNBSp2vr7c70et1woZ3613Nf9bl7IgNJbm9l7FTg2yWSLlL/siHjDdNpWmA0OdBg+wCO+FQnrrgnnzuKfS
X-Microsoft-Antispam-PRVS: <HE1PR07MB1564AD0B58AAAFADE9702538C6960@HE1PR07MB1564.eurprd07.prod.outlook.com>
X-Exchange-Antispam-Report-Test: UriScan:;
X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(601004)(2401047)(5005006)(8121501046)(3002001)(10201501046)(6055026);  SRVR:HE1PR07MB1564; BCL:0; PCL:0; RULEID:; SRVR:HE1PR07MB1564; 
X-Microsoft-Exchange-Diagnostics: 1; HE1PR07MB1564; 4:/WqE2xTMemDggAU/DCAmbALa66wKbkFCg0o9MWcbrHisWag3z8/8QHlbZxbV4EhwI1fujqFqTQpscuR5CqUBSCd5w0wu6/DfLIIMw4l9Kh83MyuKwsUDWY1AfqIvzsAS2BWTDn5BsSnPV+AW3E8imBu65F4wa3drSkz6v2KSsDmRZj9n+L2nQS79SpfHM7jGvbTRnO0/mx02/1fnWu8e3m5OOO7YifVG2CamCQduejk4EUtb6mxEZNovqWmnJJDZGC84K5+rF2U/9rhDsAbnHJxUPvaZDc9p4zYl7iGXR8TdMdTxoIrPy+JRhH9k8zOfMLqhpCgJjzp717WTxGT5S+VQCbUXaNnVgMztfoxI9LtznkN/DP+w8gSvDkF2CUcylAmOQ7culzZqcFCn5kam5w==
X-Forefront-PRVS: 0911D5CE78
X-Forefront-Antispam-Report: SFV:NSPM; SFS:(10019020)(4630300001)(6009001)(13464003)(377454003)(24454002)(5001770100001)(116806002)(15395725005)(62236002)(77096005)(92566002)(81166005)(47776003)(230700001)(44716002)(66066001)(42186005)(84392002)(19580395003)(2906002)(4326007)(14496001)(15975445007)(5008740100001)(19580405001)(1456003)(44736004)(189998001)(93886004)(50226001)(9686002)(1096002)(33646002)(586003)(3846002)(61296003)(5004730100002)(23756003)(76176999)(81686999)(81816999)(50466002)(50986999)(1556002)(86362001)(6116002)(74416001)(98824002)(7726001)(4720700001); DIR:OUT; SFP:1102; SCL:1; SRVR:HE1PR07MB1564; H:pc6; FPR:; SPF:None; MLV:nov;  PTR:InfoNoRecords; LANG:en; 
X-Microsoft-Exchange-Diagnostics: =?iso-8859-1?Q?1; HE1PR07MB1564; 23:X+HuRTTy8ptEYZ799TIHCQ0TT/jgSif8oBecaHP?= =?iso-8859-1?Q?nMXl/kOKz5M7GDlBuTlRKCIOrUrrgsUT+u0G1O50jq0ZOTgAYqWruGZfyg?= =?iso-8859-1?Q?3usnatZzAEfe7T8c5k+9Wsf1MTZacgJMAz/GCz/SK5DNKc4wSGM7JpsbAr?= =?iso-8859-1?Q?SsGtkQPw3z6bZq+9wl0/AwuzFzvD2T+VoZ3VgOHUwzcorgTO0kpn3siete?= =?iso-8859-1?Q?PzP+8qIR9HwkI8qWD0fmi018TcoJWDLT/0YHJxq5vpdGS4VRIgkWNG34V+?= =?iso-8859-1?Q?+ts4+uoDVk3RbDx+NJzkfWWY7dSSaHdCGcZ3VZFcBmJs6u2KJUpdtmSSr6?= =?iso-8859-1?Q?ci3HpVOCa24DhCW49SfTE8HCbRf0nlz6YtpJKk/uczxNG0/fKqaIHSlcXP?= =?iso-8859-1?Q?B1pZfbEpXsc3wsJqzbXjXwrXwM48njftRjrPrdlDC+9yGl0//CfftsTaTz?= =?iso-8859-1?Q?MZW30aO9cqtLgPpyjbPpskX3RUS2ERYHrlO0m3GCpqhbGJ7KMbXToCovVZ?= =?iso-8859-1?Q?sHwJzv83R3vDjC1WxhvAUc5vdAEFuWW7dWPVCiBSIMI0FZsbHz8+yeInKd?= =?iso-8859-1?Q?NyNwqSDjTsS8Sufou+HYPiJej7xrqffegd44/GdrUdXcdR1ai6cP4AgPid?= =?iso-8859-1?Q?W1CYt8Aroni7724pQgNupFpJfgM5JqPUlD3hOAIbFxW4VHDXZEbhI6F/9e?= =?iso-8859-1?Q?Pm3aCUGHgPTc6WTigmvqsymFmDFeNKCrGXBcubUDRbERXNBC+B4hQWpJDo?= =?iso-8859-1?Q?QVtAMiO9yzgwi/lx9+9dZ6StxgN/LVwigSsfgjD2bNntFcwX0J1IhH1ds2?= =?iso-8859-1?Q?fiMfeKegdCchRQRrw2Rh7u8vMXuFR/v8XfcDiTyHSKbFn1jdD5+Tch+G/b?= =?iso-8859-1?Q?m93p1+EQYoEcMwKYKKuJsPXvdhC6UNRpWiCWww9Q4235HOEDy4C3DTHU2x?= =?iso-8859-1?Q?hAhy1eNU0dNBpvSgg0qDNq8WIJnI4sJHcX8NhDfvoWSWo1wVlN6F4Ug90r?= =?iso-8859-1?Q?Yv1SfxfBoXfeDA5LfzSbXsyqmgqfnROBagCF3KDTyrCwfL6y8kJ0uksciP?= =?iso-8859-1?Q?VJdZNWaLjWW9hH9Xc9nztisIlUTYyNUAMj/AL3XLt4E9xiiY5HzIG3mv8h?= =?iso-8859-1?Q?idkK5eoSZpFhWGj2NmOqJR3ARRXYe/Bt6vvL0iwDQ3QCnnp8ikRjVWThBA?= =?iso-8859-1?Q?lt0mEWXttVrLum8ihQsds9wr80n2fvyaobJTaYvxr1YmNPm/DoOgjDaqQM?= =?iso-8859-1?Q?4UR5swLXwGefzfQ6uFeQEWhSlJ/cRfOM06jcitg8JsEFRjIFKZA2IDH7KK?= =?iso-8859-1?Q?9Zf7AfrLampX7pLe7AqkS9PJz8tODQ9CUEcfzxZYnW1HQ=3D=3D?=
X-Microsoft-Exchange-Diagnostics: 1; HE1PR07MB1564; 5:ETP/CYA3GAzNu9fhngJkvR+PAi/d4Fod+4A+hla0i7ZBHIQBvUVYGr6lns1VEbHCUJHrh1ZlGu5TH/xkCkJ3hMp9FCQ2xIXU+c+gWCfgy9nsUsSEJ0qKf37QObjgK9N9fFs6Tp2p4NQ6dh5nitZiSdDZnnupLnl1mnqn+Ea1bBX6N0QhcA/cR0DLmTuL6FlL; 24:SS79aNcv22U4bl9hA9aKvi1BTFnY/NdXH4HJXPHSt+LE6SOZNy2cKA8ieQu7jWzNh/kA626O9IqTdzr3fcZ9i3Z0/HoCUIqC8D/WCKjqsnM=; 7:L+GlM+fARoeq7R+kEuyCHvJLrCT6LpZ3JYU9+pt1oRp7Ax5+v7ytzvYux4ruSXh2c6SQ6oHF2jiiM7GJLV+jxVHVtEKLraTOGiU+FQWgiYn9S0yE48L4+lDU6Saan5f/RIyTNJCGxtc79DW/Magp3SDlfXiZtD3YVFQD/Ljuk50Cd3KsqyLXG5l7HtR7KV+Gka3mD1GixEtBjU97AXb9s/pFfL4aWgfD1jy09OEs9UM=
SpamDiagnosticOutput: 1:23
SpamDiagnosticMetadata: NSPM
X-OriginatorOrg: btconnect.com
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 13 Apr 2016 11:12:29.7861 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-Transport-CrossTenantHeadersStamped: HE1PR07MB1564
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/CWz9NDlsG38ANQQJxdREwHjqdMs>
Cc: Phillip Hallam-Baker <phill@hallambaker.com>, IETF Discussion Mailing List <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, 13 Apr 2016 11:12:56 -0000

----- Original Message -----
From: "Tony Finch" <dot@dotat.at>
To: "John R Levine" <johnl@taugh.com>
Cc: "Phillip Hallam-Baker" <phill@hallambaker.com>; "IETF Discussion
Mailing List" <ietf@ietf.org>
Sent: Wednesday, April 13, 2016 11:06 AM

> John R Levine <johnl@taugh.com> wrote:
>
> > > The UK filter is an "opt out" filter, and I assume that we (the
IETF) opted
> > > out. ...
> >
> > This isn't the parental filter, this is the child porn filter, which
I am
> > fairly sure is mandatory, at last on consumer ISPs.
>
> As I understand it this kind of filtering only applies to the largest
> consumer ISPs. We don't have any filtering of that kind on the
academic
> network I help to look after, for example. The IETF network would not
have
> any filtering unless the IETF NOC put it in.

Well, applies to the consumer access supported by the ISP; get a
business contract with the ISP and AFAICT there is no filtering.  (Well,
there is, but of e-mail, not web access, based on rules on what is and
is not an acceptable e-mail, rules which are confidential and customers
are not allowed to know. I came across them when I sent an e-mail with
no subject and a three word body - this contravenes the AUP of the
ISP:-(

On the other hand, my local council filters web access heavily and
denies access to a number of wholy innocent sites, such as a bed and
breakfast in the country.  I have viewed the site from an academic
network and cannot see what it is the council have latched on to.

Tom Petch
>
> Tony.
> --
> f.anthony.n.finch  <dot@dotat.at>  http://dotat.at/  -  I xn--zr8h
punycode


From nobody Wed Apr 13 04:31:41 2016
Return-Path: <ynir.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 6651112DC51 for <ietf@ietfa.amsl.com>; Wed, 13 Apr 2016 04:31:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 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, RCVD_IN_DNSWL_LOW=-0.7, 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 0l0pWyOh_tZL for <ietf@ietfa.amsl.com>; Wed, 13 Apr 2016 04:31:39 -0700 (PDT)
Received: from mail-wm0-x235.google.com (mail-wm0-x235.google.com [IPv6:2a00:1450:400c:c09::235]) (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 EB10F12DC23 for <ietf@ietf.org>; Wed, 13 Apr 2016 04:31:38 -0700 (PDT)
Received: by mail-wm0-x235.google.com with SMTP id a140so95813807wma.0 for <ietf@ietf.org>; Wed, 13 Apr 2016 04:31:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=nWfSOz8ii02qwf+Almjtqe+At4TlrwwIEkOA05Fgxvg=; b=n8Jqjd2cg3/QAyNagxyjkS/32jQr/gHg2qGbl+fxvp8/o3LJL3kjxe+j0ZKlugE9jM fNpJp5SSYAPDDwPOopo1xasqpJD8LgiDNltD15i7JoR2U0FPQVRUn3aKx3kG1Lrx33NZ CW8ni+CUry297IK31grgTIa+UnDm0Bvw62kKvC9ZyjWY2/tDCIThvZ/szQO4h7wHxg1Y ssoh4s70WHJ0jj5oI0MyM5T7kHAsMHQ8H0wLmFyRSAG379jUbo1s6Dbr9EZetFxcoAZR 8+7hHN//U51+QLLrhwATBt1TDlVX8evcndk54X7azmROkVpqIFFQx+RdwIeHq5AFj6Kd rAcQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=nWfSOz8ii02qwf+Almjtqe+At4TlrwwIEkOA05Fgxvg=; b=K685KiRoJpD43HjwG5fl9OcJ1kboxdGXQGBd3XDcBqjIY1J42F1/vmaY/H6tVU5kk6 B2CtkE/wArc1T3SFYUvUxgKOwaAbvb7Cgyx66XA5Sha3DmN8OHJXHP93q/+4PtpP9z5O Ce+XeHorooC3UGTdbBE55YTgXji3RHw7b5aS6aw7e5Wv++0PZC7/qq9PBjeNijXh6aQX PfgH37pYDwJp5W1esr4zbWpt3ZTVbNk33mT24WdlEFanDxIkJKi5dR4OPOgBKon6voG2 pYTrzJL5qSctELodjmDl17Gx61R+7J34oA3I2PZLedeay8pi+z92ObpBIBzakNSp52yQ dI1A==
X-Gm-Message-State: AOPr4FXYshKymUzkBUxzpGX61gjO8jpxjjSx3CMm/gsvs6hcKQdK/4PdiSIDl98lvgQ6gA==
X-Received: by 10.194.202.168 with SMTP id kj8mr8734662wjc.8.1460547097514; Wed, 13 Apr 2016 04:31:37 -0700 (PDT)
Received: from [192.168.4.111] ([199.203.248.154]) by smtp.gmail.com with ESMTPSA id fu9sm26820020wjb.44.2016.04.13.04.31.36 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Wed, 13 Apr 2016 04:31:36 -0700 (PDT)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Subject: Re: Remote only meetings? [Re: Concerns about Singapore]
From: Yoav Nir <ynir.ietf@gmail.com>
In-Reply-To: <570DAA2F.1040007@gmail.com>
Date: Wed, 13 Apr 2016 14:31:35 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <81B4533B-0F39-442D-8546-019D9253047A@gmail.com>
References: <570AB3AF.2050401@gmail.com> <87twj99c6w.fsf@tops.chopps.org> <CAKe6YvMyp-DyeDwpPY6KYmbDbnpgnvVk_cUStnA32wmgDWcz3w@mail.gmail.com> <BBF5DDFE515C3946BC18D733B20DAD233A62AA18@XMB122CNC.rim.net> <20160411104519.GA19092@gsp.org> <3F48466D-390C-4C18-B958-732AE3E46FF1@gmail.com> <20160411223403.GA6743@gsp.org> <87twj7eon7.fsf@tops.chopps.org> <20160412110839.GA20488@gsp.org> <8760vn82f2.fsf@tops.chopps.org> <20160412124639.GA27223@gsp.org> <570DAA2F.1040007@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.3124)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/Ha_8ozRt-5RLVKF-zoTl319Jtkk>
Cc: IETF discussion list <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, 13 Apr 2016 11:31:40 -0000

> On 13 Apr 2016, at 5:08 AM, Brian E Carpenter =
<brian.e.carpenter@gmail.com> wrote:
>=20
> Cherry-picking a few points:
> On 13/04/2016 00:46, Rich Kulawiec wrote:
> ...
>> And the difficulties/expense of travel are only going to get worse
>> for the forseeable future: they're not going to get better.
>=20
> That is indisputable.

OK, I=E2=80=99ll bite.=20

Expense goes up and down with the price of oil, competition, regulation =
and a zillion other factors.=20

Difficulty?  Why do you think that is getting worse?  There was an =
increase in hassle shortly after 9/11, but I haven=E2=80=99t experienced =
any greater difficulties now as opposed to 10 years ago. Why do you =
think it=E2=80=99s set to become more difficult?

Yoav


From nobody Wed Apr 13 04:51:05 2016
Return-Path: <loa@pi.nu>
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 79C6A12E0BF for <ietf@ietfa.amsl.com>; Wed, 13 Apr 2016 04:51:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.896
X-Spam-Level: 
X-Spam-Status: No, score=-2.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.996] 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 ci7k38TMA01Y for <ietf@ietfa.amsl.com>; Wed, 13 Apr 2016 04:51:00 -0700 (PDT)
Received: from pipi.pi.nu (pipi.pi.nu [83.168.239.141]) (using TLSv1.1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3AD3C12E086 for <ietf@ietf.org>; Wed, 13 Apr 2016 04:51:00 -0700 (PDT)
Received: from [192.168.1.2] (unknown [122.53.41.246]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: loa@pi.nu) by pipi.pi.nu (Postfix) with ESMTPSA id 3DFEB180158D; Wed, 13 Apr 2016 13:50:57 +0200 (CEST)
Subject: Re: Remote only meetings? [Re: Concerns about Singapore]
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, IETF discussion list <ietf@ietf.org>
References: <570AB3AF.2050401@gmail.com> <87twj99c6w.fsf@tops.chopps.org> <CAKe6YvMyp-DyeDwpPY6KYmbDbnpgnvVk_cUStnA32wmgDWcz3w@mail.gmail.com> <BBF5DDFE515C3946BC18D733B20DAD233A62AA18@XMB122CNC.rim.net> <20160411104519.GA19092@gsp.org> <3F48466D-390C-4C18-B958-732AE3E46FF1@gmail.com> <20160411223403.GA6743@gsp.org> <87twj7eon7.fsf@tops.chopps.org> <20160412110839.GA20488@gsp.org> <8760vn82f2.fsf@tops.chopps.org> <20160412124639.GA27223@gsp.org> <570DAA2F.1040007@gmail.com>
From: Loa Andersson <loa@pi.nu>
Message-ID: <570E3298.7040405@pi.nu>
Date: Wed, 13 Apr 2016 19:50:48 +0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2
MIME-Version: 1.0
In-Reply-To: <570DAA2F.1040007@gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/K2MJjz5IVAVimu1adZ6gi_4a8M0>
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, 13 Apr 2016 11:51:03 -0000

Brian,

On 2016-04-13 10:08, Brian E Carpenter wrote:
> Cherry-picking a few points:
> On 13/04/2016 00:46, Rich Kulawiec wrote:
> ...
>> And the difficulties/expense of travel are only going to get worse
>> for the forseeable future: they're not going to get better.
>
> That is indisputable.
>
> On 13/04/2016 00:49, Loa Andersson wrote:
>
>> Let us say that we set aside enough time about half way between two IETF
>> meetings and schedule all the meetings, as requested by wg chairs or
>> people in charge of other meetings, as a long series.
>
> That won't work with 4-monthly meetings as today. It might work with
> 6-monthly meetings.

I'm inclined to agree. It would be, unless we are willing to throw
over board the tradition with 3 f2f meetings per year the same as saying
that remote IETF meetings are not on the agenda.

There are many reasons why we need the f2f meetings, I would not be
willing to give that mode of operation up.

/Loa

>> Let us assume that the wg meetings is on average 1.5 hours, scheduling
>> 100 wg meetings would require 150 hours.
>
> I think that's optimistic. Remote meetings go more slowly due to technology
> glitches and the need for more formal patterns of Q/A. It's still faster than
> email though (see Alia's message).
>
> On 13/04/2016 03:42, Joel M. Halpern wrote:
>
>> I believe that there would be a real cost in moving to remote-only meetings.
>> Even putting aside the time zone difficulties, and the reduced effectiveness
>> of in-meeting interaction, there are aspects of face-to-face interaction
>> taht current remote technologies simply do not capture.
>
> Yes. I've been on a one-meeting-per-year model once or twice for personal
> reasons and it is *inferior* to attending every meeting. Some people
> can manage to time shift their lives for a week for remote participation,
> but most people can't; family, day job, and sunshine combine against it.
> The time zone issue is exclusionary. Also, there is nothing like the
> intensity of being on site with everybody.
>
> Not to say that we shouldn't improve even more on what we can do
> with Meetecho. But an important part of being able to make the best
> use of remote participation is *knowing* the people at the other
> end from previous in-person meetings.
>
>> It was very helpful in BA (and at many previous IETF meetings) to be able
>> to find time to talk with a small number of people concerned about an
>> aspect of one working group. I did that over meals, breaks, etc. It
>> sorted out issues far more effectively than email conversations (in several
>> cases, we had tried to sort it out via email. 10 minutes face-to-face
>> clarified what was being missed, and found a good path forward.)
>
> On 13/04/2016 04:00, Ted Lemon wrote:
>> This is all true, but the idea that it can't be replicated online is silly.
>> How did you arrange to have lunch with these people? You went looking
>> for them, rounded them up, and sat down to lunch. You can do that online
>> as well.
>
> You can, but it's a much more deliberate action and you're less
> likely to get serendipity effects. I would probably have been in
> some of those discussions in BA that Joel mentioned, but unfortunately
> I was on the wrong side of the world and fast asleep.
>
> IMHO we need the right blend of in-person and virtual meetings, and
> we'll find that blend by progressive change, not by revolution.
>
>     Brian
>
>
>
>
>


From nobody Wed Apr 13 04:53:42 2016
Return-Path: <rsk@gsp.org>
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 761C912DC23 for <ietf@ietfa.amsl.com>; Wed, 13 Apr 2016 04:53:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] 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 Eo-zaRnIvfvz for <ietf@ietfa.amsl.com>; Wed, 13 Apr 2016 04:53:38 -0700 (PDT)
Received: from taos.firemountain.net (taos.firemountain.net [207.114.3.54]) (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 B823212DFC7 for <ietf@ietf.org>; Wed, 13 Apr 2016 04:53:38 -0700 (PDT)
Received: from gsp.org (localhost [127.0.0.1]) by taos.firemountain.net (8.15.1/8.14.9) with SMTP id u3DBraGo030800 for <ietf@ietf.org>; Wed, 13 Apr 2016 07:53:37 -0400 (EDT)
Date: Wed, 13 Apr 2016 07:53:36 -0400
From: Rich Kulawiec <rsk@gsp.org>
To: ietf@ietf.org
Subject: Re: Concerns about Singapore
Message-ID: <20160413115336.GA27354@gsp.org>
References: <570AB3AF.2050401@gmail.com> <87twj99c6w.fsf@tops.chopps.org> <CAKe6YvMyp-DyeDwpPY6KYmbDbnpgnvVk_cUStnA32wmgDWcz3w@mail.gmail.com> <BBF5DDFE515C3946BC18D733B20DAD233A62AA18@XMB122CNC.rim.net> <20160411104519.GA19092@gsp.org> <3F48466D-390C-4C18-B958-732AE3E46FF1@gmail.com> <20160411223403.GA6743@gsp.org> <CAPt1N1nNo0=JSptQdWRZCFy1v-m6Q8NQy4WVGHtnRJuFZFmMig@mail.gmail.com> <20160412110259.GA7267@gsp.org> <A336C66D-2BCD-4693-ADA9-080EA1CD3B70@att.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <A336C66D-2BCD-4693-ADA9-080EA1CD3B70@att.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/cRs0nj4coYCcjOdVPl6uc1DBaLw>
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, 13 Apr 2016 11:53:40 -0000

On Tue, Apr 12, 2016 at 06:32:37PM +0000, HANSEN, TONY L wrote:
> I encourage people who have suggestions on how to do remote meetings to join the conversation in vmeet@ietf.org.

That'd be great, but at the moment the subscription form on this page:

	https://www.ietf.org/mailman/listinfo/vmeet

does not work.  (It results in a "403: Forbidden" error.  I've hit this
a bunch of times over the past few years with various IETF mailing lists,
so let me suggest that someone running the Mailman instance should step
through all of them and make sure that all the subscription pages work.)

---rsk



From nobody Wed Apr 13 06:05:31 2016
Return-Path: <jhaas@slice.pfrc.org>
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 CF9F212D736 for <ietf@ietfa.amsl.com>; Wed, 13 Apr 2016 06:05:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.898
X-Spam-Level: 
X-Spam-Status: No, score=-2.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.996, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] 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 UJV9Qut-EVk7 for <ietf@ietfa.amsl.com>; Wed, 13 Apr 2016 06:05:29 -0700 (PDT)
Received: from slice.pfrc.org (slice.pfrc.org [67.207.130.108]) by ietfa.amsl.com (Postfix) with ESMTP id ED55012D704 for <ietf@ietf.org>; Wed, 13 Apr 2016 06:05:28 -0700 (PDT)
Received: by slice.pfrc.org (Postfix, from userid 1001) id C66B01E478; Wed, 13 Apr 2016 09:09:48 -0400 (EDT)
Date: Wed, 13 Apr 2016 09:09:48 -0400
From: Jeffrey Haas <jhaas@pfrc.org>
To: Ole Jacobsen <olejacobsen@me.com>
Subject: Re: Concerns about Singapore
Message-ID: <20160413130948.GC9940@pfrc.org>
References: <20160411104519.GA19092@gsp.org> <3F48466D-390C-4C18-B958-732AE3E46FF1@gmail.com> <20160411223403.GA6743@gsp.org> <CAPt1N1nNo0=JSptQdWRZCFy1v-m6Q8NQy4WVGHtnRJuFZFmMig@mail.gmail.com> <CAKr6gn1KmNcgNwbPHZWB2aJQAuchz4eB7gxJhV2Dsbc1Z50kDw@mail.gmail.com> <CAPt1N1mWjg_-525avYJ4PnSECYQrtpVFJCXPfH=PryJ8q0vy4Q@mail.gmail.com> <A684A3C4-7161-49F5-919E-A5F948A3F316@ecs.soton.ac.uk> <EMEW3|d5cb2cb80712b3716e1ab4e2a54c9430s3BCG403tjc|ecs.soton.ac.uk|A684A3C4-7161-49F5-919E-A5F948A3F316@ecs.soton.ac.uk> <570CF594.5070509@pi.nu> <alpine.OSX.2.01.1604120745250.52880@rabdullah.local>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <alpine.OSX.2.01.1604120745250.52880@rabdullah.local>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/7HqzB81MjMIguj_9Jk7vuRkA5Lk>
Cc: 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, 13 Apr 2016 13:05:30 -0000

On Tue, Apr 12, 2016 at 07:47:25AM -0700, Ole Jacobsen wrote:
> "I don't think anything that is within our power to do can change this
> perception."
> 
> Perhaps some information from "the ground" and from frequent visitors
> to Singapore who would have concerns about these issue *might* help.
> 
> Let's gather the data before we throw the baby out with the bath water
> so to speak.

My point much earlier on. :-)

-- Jeff


From nobody Wed Apr 13 06:23:40 2016
Return-Path: <bensons@queuefull.net>
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 543B012D194 for <ietf@ietfa.amsl.com>; Wed, 13 Apr 2016 06:23:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 3.757
X-Spam-Level: ***
X-Spam-Status: No, score=3.757 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, HTML_MESSAGE=0.001, RCVD_IN_BRBL_LASTEXT=1.449, RCVD_IN_MSPIKE_BL=0.01, RCVD_IN_MSPIKE_L4=2.299, SPF_HELO_PASS=-0.001] autolearn=no 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 2PckcY6Za4Li for <ietf@ietfa.amsl.com>; Wed, 13 Apr 2016 06:23:38 -0700 (PDT)
Received: from iwaki-pa.or.jp (iwaki-pa.or.jp [122.1.226.75]) (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 3720812D106 for <Ietf@ietf.org>; Wed, 13 Apr 2016 06:23:38 -0700 (PDT)
Received: from ctaddz.net (unknown [181.91.84.48]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by iwaki-pa.or.jp (Postfix) with ESMTPSA id B8A11A803E09; Wed, 13 Apr 2016 22:15:46 +0900 (JST)
From: <bensons@queuefull.net>
To: "Ian Smith" <I.Smith@f5.com>, "Ian.Foo" <Ian.Foo@huawei.com>, "Ian"  <ian.jolliffe@windriver.com>, "Icaro Camelo" <icamelo@inocybe.ca>, "Ietf" <Ietf@ietf.org>
Subject: Fw: new important message
Date: Wed, 13 Apr 2016 16:15:44 +0300
Message-ID: <000055a68e6e$f49f0357$12fa096b$@queuefull.net>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0001_60E34F11.21C5D35A"
X-Mailer: Microsoft Outlook 15.0
Thread-Index: AdGY5WbESbfDAEXJumzaK+14KjyC+g==
Content-Language: en-us
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/9cAnJUQeCIHxYOHvwXAlbKyyzqM>
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, 13 Apr 2016 13:23:39 -0000

This is a multipart message in MIME format.

------=_NextPart_000_0001_60E34F11.21C5D35A
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit

Hello!

 

New message, please read <http://www.freedstyle.com/alone.php?d>

 

bensons@queuefull.net


------=_NextPart_000_0001_60E34F11.21C5D35A
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas=
-microsoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:off=
ice:word" xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml"=
 xmlns=3D"http://www.w3.org/TR/REC-html40"><head><META HTTP-EQUIV=3D"C=
ontent-Type" CONTENT=3D"text/html; charset=3Dus-ascii"><meta name=3DGe=
nerator content=3D"Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;
	mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:#0563C1;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
=2EMsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri",sans-serif;
	mso-fareast-language:EN-US;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:2.0cm 42.5pt 2.0cm 3.0cm;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN link=3D"#0563=
C1" vlink=3D"#954F72"><div class=3DWordSection1><p class=3DMsoNormal><=
span lang=3DEN-US>Hello!<o:p></o:p></span></p><p class=3DMsoNormal><sp=
an lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span=
 lang=3DEN-US><b>New message, please read</b> <a href=3D"http://www.fr=
eedstyle.com/alone.php?d">http://www.freedstyle.com/alone.php</a><o:p>=
</o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US><o:p>&nbsp;</=
o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US>bensons@queuefu=
ll.net<o:p></o:p></span></p></div></body></html>

------=_NextPart_000_0001_60E34F11.21C5D35A--


From nobody Wed Apr 13 07:47:29 2016
Return-Path: <mellon@fugue.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 C403812E2EE for <ietf@ietfa.amsl.com>; Wed, 13 Apr 2016 07:47:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.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 uYLlQJ_svVKb for <ietf@ietfa.amsl.com>; Wed, 13 Apr 2016 07:47:23 -0700 (PDT)
Received: from mail-lf0-x234.google.com (mail-lf0-x234.google.com [IPv6:2a00:1450:4010:c07::234]) (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 3D46012E2E6 for <ietf@ietf.org>; Wed, 13 Apr 2016 07:47:23 -0700 (PDT)
Received: by mail-lf0-x234.google.com with SMTP id c126so73148616lfb.2 for <ietf@ietf.org>; Wed, 13 Apr 2016 07:47:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=IH0UDFmFjsS7ZMtY01p9y32+mhCTIG2J8RZPbjiZ7ss=; b=QJfEzMqPDCjWcfxDqcSNwyEIMaircQj8sG7FptR96QzN1KqzxeuHeWHmbTk+q04dUe UmxAZ7zMSi2XLMu28E/9txK4M2TvaDGSnKPndhAb0bBlGC87WG+ETtjIHGlXE0NWSLce Mty4nla1ZYeNJLotdDU33zJHIhz6ZJ+BO0v91HVvczR8uwQnQEC15hodZCefpZDVJ79J aQqerZ+qm+jMogyqaA9C9X3u8uGXR3hewiIbXM6dVdtwdkmcf8SNfjbR6gO1cEL48zxm /Pbp9EcnS7ImcQIdIMmfSS5F2hK1ITXTA8OpMgS+YtP8wEvsvEvj8ls2kE/rhqVq2ZKM oqNA==
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=IH0UDFmFjsS7ZMtY01p9y32+mhCTIG2J8RZPbjiZ7ss=; b=cMmW2GlUfAPqNIeyvHwzz3Aa+R4g7+o36pI9T5eQha0IuFT8cRCu7mQfrUOMQ/9x29 VeX40pNO0YLhhj2kg5UevwPgyg2TgOfzhotiQTuflk22+LS1SERXQmtTQPZVo2pjRXpr zIL3iyX2vqlZa/pDBDy1Dc0mhPgvJ01JiYXNS7O6JGqOrJxb1LrLiBKJ+0p6eLAn1P5o VA0A8DZLDOX/o/QTgos1j/M6WIfLKR1N+gMwp1SpWNQ6xl/pw2eoZ/gjT4ek9vfV3RKW BayhfULvSJi0lRJImAJ8T26R+qvgps9zE3vsT0N6ruPEm2B+adDTGYC4ZXuZc2/em6dc AL9A==
X-Gm-Message-State: AOPr4FUu9uNFUic3eIQtQtxFp/wWIMaDhfe0I4GYclSjdZ//GcidlgQsSDcHdll8+XVTlT/233m18e+taHP+lw==
X-Received: by 10.25.205.146 with SMTP id d140mr4498228lfg.109.1460558841377;  Wed, 13 Apr 2016 07:47:21 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.25.40.136 with HTTP; Wed, 13 Apr 2016 07:46:41 -0700 (PDT)
X-Originating-IP: [71.233.41.235]
In-Reply-To: <20160413130948.GC9940@pfrc.org>
References: <20160411104519.GA19092@gsp.org> <3F48466D-390C-4C18-B958-732AE3E46FF1@gmail.com> <20160411223403.GA6743@gsp.org> <CAPt1N1nNo0=JSptQdWRZCFy1v-m6Q8NQy4WVGHtnRJuFZFmMig@mail.gmail.com> <CAKr6gn1KmNcgNwbPHZWB2aJQAuchz4eB7gxJhV2Dsbc1Z50kDw@mail.gmail.com> <CAPt1N1mWjg_-525avYJ4PnSECYQrtpVFJCXPfH=PryJ8q0vy4Q@mail.gmail.com> <A684A3C4-7161-49F5-919E-A5F948A3F316@ecs.soton.ac.uk> <EMEW3|d5cb2cb80712b3716e1ab4e2a54c9430s3BCG403tjc|ecs.soton.ac.uk|A684A3C4-7161-49F5-919E-A5F948A3F316@ecs.soton.ac.uk> <570CF594.5070509@pi.nu> <alpine.OSX.2.01.1604120745250.52880@rabdullah.local> <20160413130948.GC9940@pfrc.org>
From: Ted Lemon <mellon@fugue.com>
Date: Wed, 13 Apr 2016 10:46:41 -0400
Message-ID: <CAPt1N1nRNYdqJzPdNrzHRW8sUGOm4ngnJCqd2i9H7wD5QV+-zg@mail.gmail.com>
Subject: Re: Concerns about Singapore
To: Jeffrey Haas <jhaas@pfrc.org>
Content-Type: multipart/alternative; boundary=001a114128caea167d05305eda9a
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/GGm2Xqu7la72JixqN7Cc_95IB60>
Cc: ietf <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, 13 Apr 2016 14:47:28 -0000

--001a114128caea167d05305eda9a
Content-Type: text/plain; charset=UTF-8

Hm.  Beware of the Leopard.   However, it did work for me when I tried it
yesterday.

On Wed, Apr 13, 2016 at 9:09 AM, Jeffrey Haas <jhaas@pfrc.org> wrote:

> On Tue, Apr 12, 2016 at 07:47:25AM -0700, Ole Jacobsen wrote:
> > "I don't think anything that is within our power to do can change this
> > perception."
> >
> > Perhaps some information from "the ground" and from frequent visitors
> > to Singapore who would have concerns about these issue *might* help.
> >
> > Let's gather the data before we throw the baby out with the bath water
> > so to speak.
>
> My point much earlier on. :-)
>
> -- Jeff
>
>

--001a114128caea167d05305eda9a
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hm.=C2=A0 Beware of the Leopard. =C2=A0 However, it did wo=
rk for me when I tried it yesterday.</div><div class=3D"gmail_extra"><br><d=
iv class=3D"gmail_quote">On Wed, Apr 13, 2016 at 9:09 AM, Jeffrey Haas <spa=
n dir=3D"ltr">&lt;<a href=3D"mailto:jhaas@pfrc.org" target=3D"_blank">jhaas=
@pfrc.org</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=
=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span cl=
ass=3D"">On Tue, Apr 12, 2016 at 07:47:25AM -0700, Ole Jacobsen wrote:<br>
&gt; &quot;I don&#39;t think anything that is within our power to do can ch=
ange this<br>
&gt; perception.&quot;<br>
&gt;<br>
&gt; Perhaps some information from &quot;the ground&quot; and from frequent=
 visitors<br>
&gt; to Singapore who would have concerns about these issue *might* help.<b=
r>
&gt;<br>
&gt; Let&#39;s gather the data before we throw the baby out with the bath w=
ater<br>
&gt; so to speak.<br>
<br>
</span>My point much earlier on. :-)<br>
<br>
-- Jeff<br>
<br>
</blockquote></div><br></div>

--001a114128caea167d05305eda9a--


From nobody Wed Apr 13 07:50:39 2016
Return-Path: <prvs=9046cac78=theodore.v.faber@aero.org>
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 F35BD12D9ED for <ietf@ietfa.amsl.com>; Wed, 13 Apr 2016 07:50:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.896
X-Spam-Level: 
X-Spam-Status: No, score=-2.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RP_MATCHES_RCVD=-0.996] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=neutral reason="invalid (public key: not available)" header.d=aero.org header.b=FuqkqwBQ; dkim=pass (1024-bit key) header.d=aerospacecloud.onmicrosoft.com header.b=hoogwbm6
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 GbaxNq2TSysV for <ietf@ietfa.amsl.com>; Wed, 13 Apr 2016 07:50:35 -0700 (PDT)
Received: from email3-east.aero.org (email3-east.aero.org [130.221.184.167]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3C04912D9D7 for <ietf@ietf.org>; Wed, 13 Apr 2016 07:50:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=aero.org; i=@aero.org; q=dns/txt; s=mailhub; t=1460559035; x=1492095035; h=from:to:subject:date:message-id:references: content-transfer-encoding:mime-version; bh=4sLvvN2s790uD3uqigM4e6ayv1r6itMjJ+OCDJqYBsM=; b=FuqkqwBQh2Vzm1GQt+3t9vkoo6b4F3iou9grzX+i3dC5460gjHDLp0sv TKOHxQFN1cWjz08cc9vRCr1WySuLZ4kIdEaXqjd9o9y6kJjxtyESOoYUq eyvGKGP7aU0fDxbKNPgEcI2F3HNdKVWw4CaWTVtUPLEcjxmkzPjHJrLQo w=;
x-SBRS: None
x-SenderGroup: Inbound_Office365
X-IronPort-AV: E=McAfee;i="5700,7163,8134"; a="2579455"
X-IronPort-AV: E=Sophos;i="5.24,480,1454994000";  d="scan'208";a="2579455"
X-IPAS-Result: A2H3AQBzXA5X/w/GZxdbAxkBAQEBg219BrpGAQ2BTRoNFwuFbAKBdxQBAQEBAQEBA2IngjchFxABAQEBAQEmAQEBAQEBIwINJwouAQEBAwEBAQ8BJwYBATgPAgEIDgoMAREQJwslAgQBEggah3EDEg6iNQGBJwEcYQUoAopohSgBBIhJGIUiAQEBBwEBAQEBAQETAgSKbIQ9AiEmgmSCK5gNhXeXJo8nHgEBQoF3DBqBSmwBiHsBfQEBAQ
Received: from mail-cy1gcc01lp0015.outbound.protection.outlook.com (HELO gcc01-CY1-obe.outbound.protection.outlook.com) ([23.103.198.15]) by email3-east.aero.org with ESMTP/TLS/AES256-SHA; 13 Apr 2016 10:50:04 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aerospacecloud.onmicrosoft.com; s=selector1-aero-org; h=From:To:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=4sLvvN2s790uD3uqigM4e6ayv1r6itMjJ+OCDJqYBsM=; b=hoogwbm6Vm3gI4FOuGnKaUQFRVgCLSryuLRsKbtP9oILNMIeBHmUeoR36x6cif0OMQgYcJ9gUAMHc63kK7Ja/YgY8SDjbltxSnKlX61dv1A9pqcICiNhdr3FjJAXvqe9m6LokxOEUEZmgW2HvBrSuP9T2omVmRESszPEArboTrc=
Received: from DM2PR09MB0336.namprd09.prod.outlook.com (10.160.247.153) by DM2PR09MB0334.namprd09.prod.outlook.com (10.160.247.151) with Microsoft SMTP Server (TLS) id 15.1.453.26; Wed, 13 Apr 2016 14:49:44 +0000
Received: from DM2PR09MB0336.namprd09.prod.outlook.com ([10.160.247.153]) by DM2PR09MB0336.namprd09.prod.outlook.com ([10.160.247.153]) with mapi id 15.01.0453.029; Wed, 13 Apr 2016 14:49:44 +0000
From: Theodore V Faber <theodore.v.faber@aero.org>
To: Rich Kulawiec <rsk@gsp.org>, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: Concerns about Singapore
Thread-Topic: Concerns about Singapore
Thread-Index: AQHRkOMTs3DHSqtWXUaKt2vKlrce+A==
Date: Wed, 13 Apr 2016 14:49:43 +0000
Message-ID: <DM2PR09MB0336FF03201E471FA1D0FE8AB9960@DM2PR09MB0336.namprd09.prod.outlook.com>
References: <570AB3AF.2050401@gmail.com> <87twj99c6w.fsf@tops.chopps.org> <CAKe6YvMyp-DyeDwpPY6KYmbDbnpgnvVk_cUStnA32wmgDWcz3w@mail.gmail.com> <BBF5DDFE515C3946BC18D733B20DAD233A62AA18@XMB122CNC.rim.net> <20160411104519.GA19092@gsp.org> <3F48466D-390C-4C18-B958-732AE3E46FF1@gmail.com> <20160411223403.GA6743@gsp.org> <CAPt1N1nNo0=JSptQdWRZCFy1v-m6Q8NQy4WVGHtnRJuFZFmMig@mail.gmail.com> <20160412110259.GA7267@gsp.org> <A336C66D-2BCD-4693-ADA9-080EA1CD3B70@att.com> <20160413115336.GA27354@gsp.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: gsp.org; dkim=none (message not signed) header.d=none;gsp.org; dmarc=none action=none header.from=aero.org;
x-originating-ip: [130.221.224.7]
x-ms-office365-filtering-correlation-id: 5b1fd947-1317-4834-3788-08d363aad9ed
x-microsoft-exchange-diagnostics: 1; DM2PR09MB0334; 5:mEhzM+j6FWlOX5mzAMkHnQnzYk1sHqw1ENMCOu3ayG+K3bNhBXcshWg97/vSWvJW/fDmlbucXC8fphbrjUliTUud/1DCK9QS/Wlvm9q1p86E+dUcFNfigDlUiU5kNCW4Jgnefe+otaPQJAi78/CF9A==; 24:ZRd8i/Jxh7R06gaJR1N9Ti2uZO2NbeQO6kzHrZUAU9r0PbE0DwIQBg7hAyf+JZSva+QLVwBs/F8hB3aXZ8tH3GQo/ZIhn3tf9Ig4MiwADD8=
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:DM2PR09MB0334;
x-microsoft-antispam-prvs: <DM2PR09MB03345D32ED9F8A78A39407C2B9960@DM2PR09MB0334.namprd09.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(601004)(2401047)(5005006)(8121501046)(3002001)(10201501046); SRVR:DM2PR09MB0334; BCL:0; PCL:0; RULEID:; SRVR:DM2PR09MB0334; 
x-forefront-prvs: 0911D5CE78
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(6009001)(24454002)(5003600100002)(575784001)(122556002)(15975445007)(5002640100001)(5001770100001)(586003)(86362001)(1220700001)(102836003)(19580405001)(77096005)(189998001)(5008740100001)(6116002)(19580395003)(1096002)(76576001)(107886002)(5004730100002)(54356999)(76176999)(92566002)(11100500001)(81166005)(66066001)(87936001)(106116001)(74316001)(2906002)(93886004)(3280700002)(3480700003)(33656002)(2501003)(50986999)(99286002)(10400500002)(9686002)(3660700001)(19627235001); DIR:OUT; SFP:1101; SCL:1; SRVR:DM2PR09MB0334; H:DM2PR09MB0336.namprd09.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en; 
spamdiagnosticoutput: 1:23
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: aero.org
X-MS-Exchange-CrossTenant-originalarrivaltime: 13 Apr 2016 14:49:43.9289 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: c8294700-c5a4-4ca1-a876-1457d39899fd
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM2PR09MB0334
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/ZwxVXGtZtmlrsV2Un2qlfM7K9KU>
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, 13 Apr 2016 14:50:37 -0000

-----BEGIN PGP SIGNED MESSAGE-----=0A=
Hash: SHA512=0A=
=0A=
On 4/13/16 04:53, Rich Kulawiec wrote:=0A=
> On Tue, Apr 12, 2016 at 06:32:37PM +0000, HANSEN, TONY L wrote:=0A=
>> I encourage people who have suggestions on how to do remote=0A=
>> meetings to join the conversation in vmeet@ietf.org.=0A=
> =0A=
> That'd be great, but at the moment the subscription form on this=0A=
> page:=0A=
> =0A=
> https://www.ietf.org/mailman/listinfo/vmeet=0A=
> =0A=
> does not work.=0A=
=0A=
As another data point, I was able to subscribe by following that link.=0A=
 FWIW I even had to go through an http proxy (corporate config, not=0A=
choice).=0A=
=0A=
- -- =0A=
Ted Faber <theodore.v.faber@aero.org>=0A=
Engineering Specialist=0A=
Computer Systems Research Department=0A=
310-336-7373=0A=
-----BEGIN PGP SIGNATURE-----=0A=
Comment: GPGTools - https://gpgtools.org=0A=
=0A=
iQIcBAEBCgAGBQJXDlyGAAoJEFNjQnOBW8uOI0EP/3EAfN+Ylb6/GClHK28N2/1m=0A=
U+tr0mqNh59ySHJhTTLL790yXSAxraudTlv5YUj8/yNLojgwTQ2nVKx8AJzRRI72=0A=
zobn/YEMAOeGZ7F6k8ZIgLEMDlI7IxUEMZyNrm5i5asO98U2MrLy3yGZjIrxhofI=0A=
tmLzEteFsXz04YyqPu8hP22lF81UDH9V82IV6pbQkQFEPdemFah/GJGHCL8FoAgL=0A=
iHltETyr22WYyb5zkQbzxOUHsr4o9iy7mV06nqD9SpBJo0bGZV2OrRFoyZNeJ55k=0A=
E9U0feX9cXN2L34Ln0aog8ikB7asSicqriex/SYOSjLd3ByYSIQxTT0jeod9dx3b=0A=
C4krBfBP2wOJShRyNFnbOKw/P9o4dXarIwQ1w37143uCifew4WnyuP5UChjozKIs=0A=
LfkpnmVnNZ+0OUEOueJ0wuB9QQkgoK5tTww6zb66ppCfuop7Clncn0xxsxDYPB2Q=0A=
1/jBt1SY3PHL3uXQONiyX4P/X/oBkIVsYLf0rbwTNZRmQlieEmj5tGvt/WyFzY6+=0A=
CnvaN7T75bVPMcXeqb8Zvsc3KTKwyRtnGmEAmCiEp51WEUaLeU3jPIIGrXkdRGpW=0A=
fUFruKgGFLFTDMdI2WSObRZcGwc+00JQQmqpq4jumA0KjQMm0aEBscoPJ/L+6qba=0A=
t0s1QnhePBhmGRyAJvSw=0A=
=3DECpS=0A=
-----END PGP SIGNATURE-----=0A=


From nobody Wed Apr 13 10:41:29 2016
Return-Path: <john-ietf@jck.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 C202312DEFC for <ietf@ietfa.amsl.com>; Wed, 13 Apr 2016 10:41:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.896
X-Spam-Level: 
X-Spam-Status: No, score=-2.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.996] 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 5rm0K3LfeKgu for <ietf@ietfa.amsl.com>; Wed, 13 Apr 2016 10:41:25 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4AC7B12DE21 for <ietf@ietf.org>; Wed, 13 Apr 2016 10:41:23 -0700 (PDT)
Received: from [198.252.137.10] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1aqOmw-000Nsg-DR; Wed, 13 Apr 2016 13:41:14 -0400
Date: Wed, 13 Apr 2016 13:41:09 -0400
From: John C Klensin <john-ietf@jck.com>
To: Michael Cameron <michael.cameron@ericsson.com>, Alissa Cooper <alissa@cooperw.in>, Jari Arkko <jari.arkko@piuha.net>
Subject: RE: Last Call on draft-bradner-rfc3979bis-08.txt ("Intellectual Property Rights in IETF Technology")
Message-ID: <16849BC54F958DF4DB61843A@JcK-HP8200.jck.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/4KmZKCDwdHeVAIlutUsPsPS6bzE>
Cc: IETF <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, 13 Apr 2016 17:41:28 -0000

--On Tuesday, April 12, 2016 17:33 +0000 Michael Cameron
<michael.cameron@ericsson.com> wrote:

> John said:
> 
> As a random member of the community, whether I'm participating
> in a WG, or even actively monitoring it, is fairly clear.  If,
> for example, I'm attending its meetings (f2f or remotely) or
> signed up for its mailing list, the community should be able
> to assume that I'm watching the work in that WG and should be
> required to make relevant IPR disclosures even if I don't
> actually say anything or otherwise generate Contributions.    
> 
> My response:
> 
> I appreciate that some are advocating for what they want the
> rules to be, but let's level set as to what they are.
> Attending meetings, being signed up for mailing lists or
> watching work in a WG does not obligate one to make any IPR
> disclosures.  That was discussed in detail at the last IETF
> meeting when the IPR Group met (Orlando, IIRC). The IPR
> disclosure obligation arises only with respect to known IPR
> reading on Contributions (for Contributors) and for
> non-Contributors, the disclosure obligation only applies to
> known IPR reading on a draft on which such non-Contributor
> actively seeks to influence the outcome of the disposition of
> a draft (active participation).

Again, you are splitting hairs in a very lawyer-like fashion
(you may take that as a complement if you like).   But I suggest
that, e.g., responding to a request for a hum, or even not
humming when a WG Chair asks a question and does not ask for
hums on the opposite or on any other alternatives, constitutes
"actively seeking to influence the outcome...".  If I'm sitting
in the WG session at a time a WG Chair asks
consensus-determining questions and I don't want to be counted
as for, against, or indifferent (itself a potentially
influencing position), I'd best head for the door rather than
sitting there.

My recollection of that last meeting of the IPR WG (and several
before it, both immediately before and over the years) is
apparently a bit different from yours.   My understanding of the
discussion there was that the community's intent is that, if one
knew of IPR that might reasonably be expected to bear on the
work of a WG or a particular document, the expectation was that
one would disclose (with the level of that expectation
deliberately lower if one was not directly connected to the IPR
than if one was directly connected.  If, for some reason,
disclosure was impossible and/or would violate other
commitments, then one was expected to be clearly isolated from
the work generally and from any reasonable doubts about whether
one had influenced a decision or attempted to do so.    IMO, the
alternatives lead to madness, e.g., can you imagine wanting to
know who was sitting next to someone so as to be able to ask is
he or she hummed, made silly faces, or otherwise tried to
influence the outcome of a discussion about a draft?

Now, I think there is a separate issue, which is when the cases
arise from which the IETF threatens to apply sanctions for
violating the rules.  I think we need to deal with the gray
areas in which someone made a reasonable judgment call
(including cases in which there is question about whether
first-party or third-party rules apply) in a reasoned, flexible,
and generous way, reserving the punishments and nasty behavior
for clear cases or patterns of abuse.     I think our actual
practice has been consistent with that approach.

> John said:
> 
> If you are the AD responsible for a WG, then I think the
> community gets to assume that you know what its work items
> are, have approved document editors, and have at least read
> the abstracts of the various drafts, i.e., that you are
> participating.  If you are some other AD in the same area,
> well, areas differ a lot and over time.  In some cases, ADs
> shadow each other as a mutual backup arrangements and I'd
> expect to be able to treat all ADs in the same area as
> "participating" in all WGs.  In others, WGs get divided up
> among ADs, after which the area might as well be as many
> separate ones as there are ADs.  At IETF evaluation time, any
> ADs who record a position other that "abstain" on a spec, or
> to engage in any IESG discussion about it, has presumably
> studied that spec closely enough to incur disclosure
> obligations if IPR is known to them because making a decision
> to adopt (or not) is clearly "participation".  The same issue
> might exist with Co-chairs of a WG with many tasks.  I'd
> normally assume that each one is familiar with and
> participating in every work item, but it isn't hard to imagine
> situations in which work might be split up along clear
> boundaries with one co-chair getting involved in the work of
> the other only at around the time of Last Call if then.
> 
> My response:
> 
> We need to be careful not to place on Area Directors
> unreasonable burdens and obligations.  Further, there needs to
> be certainty as to what the obligations are.   The obligations
> imposed on Area Directors to declare known IPR should be
> limited to those activities in which they actively
> participate.  I'll defer to the ADs, but I would think that an
> AD acting on a recommendation or advice from a WG as to how to
> proceed on a Specification, without more, does not necessarily
> rise to the level of active participation.

That would be great, but it is just not consistent with how the
IESG functions.   ADs are just not expected to passively accept
WG recommendations, at least unless they have been very actively
involved in the WG and is management.  Instead, they are called
upon to evaluate those recommendations and make recommendations
to the community about them.  That is just not a passive,
"without more" sort of relationship.  

However, I think this is showing up a more fundamental problem.
If the community still has the same understanding of the general
intent of the IPR and disclosure rules as it did when the WG
concluded, then treating a document update that clarifies and/or
better aligned with that general intent as an individual
submission from Scott and Jorge.  If, however, we have
significant disagreements about what the intent was, and maybe
even about whether things have changed enough that the intent
needs to be re-evaluated, then, at least IMO, it is unreasonable
to expect that we can gets things right on the IETF list as part
of a Last Call on an individual submission.  Instead, if we have
reacted the point where a debate about principles is needed, it
is almost certainly time to reconvene/ recharter the WG.

    john





From nobody Wed Apr 13 11:32:59 2016
Return-Path: <michael.cameron@ericsson.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 BBDEF12DABF for <ietf@ietfa.amsl.com>; Wed, 13 Apr 2016 11:32:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] 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 iwk1u4lsBxbd for <ietf@ietfa.amsl.com>; Wed, 13 Apr 2016 11:32:56 -0700 (PDT)
Received: from usplmg20.ericsson.net (usplmg20.ericsson.net [198.24.6.45]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B82D312DA4B for <ietf@ietf.org>; Wed, 13 Apr 2016 11:32:56 -0700 (PDT)
X-AuditID: c618062d-f79886d000002334-ca-570e8a4a6858
Received: from EUSAAHC007.ericsson.se (Unknown_Domain [147.117.188.93]) by usplmg20.ericsson.net (Symantec Mail Security) with SMTP id E8.7A.09012.A4A8E075; Wed, 13 Apr 2016 20:04:58 +0200 (CEST)
Received: from EUSAAMB101.ericsson.se ([147.117.188.118]) by EUSAAHC007.ericsson.se ([147.117.188.93]) with mapi id 14.03.0248.002; Wed, 13 Apr 2016 14:32:55 -0400
From: Michael Cameron <michael.cameron@ericsson.com>
To: John C Klensin <john-ietf@jck.com>, Alissa Cooper <alissa@cooperw.in>, Jari Arkko <jari.arkko@piuha.net>
Subject: RE: Last Call on draft-bradner-rfc3979bis-08.txt ("Intellectual Property Rights in IETF Technology")
Thread-Topic: Last Call on draft-bradner-rfc3979bis-08.txt ("Intellectual Property Rights in IETF Technology")
Thread-Index: AQHRlauzwPAz1p1T+UCpf3Tkbe6ELJ+ILd3A
Date: Wed, 13 Apr 2016 18:32:51 +0000
Message-ID: <36BAA6A693139D4BBCB37CCCA660E08A14FDCB16@eusaamb101.ericsson.se>
References: <16849BC54F958DF4DB61843A@JcK-HP8200.jck.com>
In-Reply-To: <16849BC54F958DF4DB61843A@JcK-HP8200.jck.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [147.117.188.9]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFuplkeLIzCtJLcpLzFFi42KZXLonVteriy/c4E23scX0M38ZLZ5tnM9i MWPfCjaL1kt/2BxYPL48ecnksWTJTyaPyytfM3tsXTKdLYAlissmJTUnsyy1SN8ugSuj/8Fu 9oIlzBX/lhxkbWA8zNTFyMkhIWAicezgfGYIW0ziwr31bCC2kMBRRomv7wq6GLmA7OWMEs23 2oCKODjYgBqeP2MBMUUE8iQ+nPUFKWcWkJC4PuEd2EhhgXyJ+zd6WUFsEYECifN/D7JA2EYS tx9OBLNZBFQlNq2eww5i8wr4SvR/u8AEsdZSYub/KYwgNqeAlcSmrk9g9YxAp30/tYYJYpe4 xK0n86HOF5BYsuc81PmiEi8f/2OFsBUl9vVPZ4eo15FYsPsTG4StLbFs4WtmiL2CEidnPmGZ wCg2C8nYWUhaZiFpmYWkZQEjyypGjtLigpzcdCODTYzASDomwaa7g/H+dM9DjAIcjEo8vAor eMOFWBPLiitzDzFKcDArifCK9fGFC/GmJFZWpRblxxeV5qQWH2KU5mBREudtDP4XJiSQnliS mp2aWpBaBJNl4uCUamCUe26ZWsK52YKnYuGpLDbBfRe5pK7t2SCkerR7UvLO/fnardOmy9uK TNy+uDrt4/8y29R95tvelwm+fbpNSJjDrnLrTA6fdNm0ruwl2zZ16F0s3JbYcrKD/8C+Mwd3 tjK+CzH1cfU3WDvn7nSDppMLV1s5Ni+yc29svrN5SkfwOR4Xnw18TnZKLMUZiYZazEXFiQDj HvNPoAIAAA==
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/dgG9JOjH6_6yJrudqhI3l8tL-tc>
Cc: IETF <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, 13 Apr 2016 18:32:57 -0000

Hi John, if we can't split legal hairs in a purely legal domain, then I pro=
bably need to find another line of work :-)=20

I'lI try to respond to some of your other points in a later post, but one t=
hing stood out that I'd like to address right away.   I disagree that sitti=
ng passively in a meeting and not humming could constitute "actively seekin=
g to influence the outcome..." =20

Best, Mike





From nobody Wed Apr 13 13:04:25 2016
Return-Path: <jmh@joelhalpern.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 6F5A312DDE6 for <ietf@ietfa.amsl.com>; Wed, 13 Apr 2016 13:04:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.702
X-Spam-Level: 
X-Spam-Status: No, score=-2.702 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=joelhalpern.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 uB57YaGud1ky for <ietf@ietfa.amsl.com>; Wed, 13 Apr 2016 13:04:21 -0700 (PDT)
Received: from mailb2.tigertech.net (mailb2.tigertech.net [208.80.4.154]) (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 DA7D012B055 for <ietf@ietf.org>; Wed, 13 Apr 2016 13:04:21 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id AEFBB520105; Wed, 13 Apr 2016 13:04:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=1.tigertech; t=1460577861; bh=knoCxVXymIiX7izneRZhuSNpz4ZqKcDyLNTLnoDn+dM=; h=Subject:To:References:Cc:From:Date:In-Reply-To:From; b=OrWUDqr8I7UtovrZG5FuiCjIl6YY7e+fe3bzrJ4/jxaCLGUgu6x9uL/qDzGnZ2VAs Z6M6PmbmC5hnpo7xswCI2ivvEa30yJhBSd0YGwPcw+xoUkm7Ra+3K+L/D5/rXvFfS0 jIssAFjGEorbZpltoJIUJ+pasP3yPoHFHTzvsgeM=
X-Virus-Scanned: Debian amavisd-new at b2.tigertech.net
Received: from Joels-MacBook-Pro.local (209-255-163-147.ip.mcleodusa.net [209.255.163.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mailb2.tigertech.net (Postfix) with ESMTPSA id D6BC31C0346; Wed, 13 Apr 2016 13:04:20 -0700 (PDT)
Subject: Re: Last Call on draft-bradner-rfc3979bis-08.txt ("Intellectual Property Rights in IETF Technology")
To: John C Klensin <john-ietf@jck.com>, Michael Cameron <michael.cameron@ericsson.com>, Alissa Cooper <alissa@cooperw.in>, Jari Arkko <jari.arkko@piuha.net>
References: <16849BC54F958DF4DB61843A@JcK-HP8200.jck.com>
From: "Joel M. Halpern" <jmh@joelhalpern.com>
Message-ID: <570EA63E.6090601@joelhalpern.com>
Date: Wed, 13 Apr 2016 16:04:14 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:38.0) Gecko/20100101 Thunderbird/38.7.2
MIME-Version: 1.0
In-Reply-To: <16849BC54F958DF4DB61843A@JcK-HP8200.jck.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/hh2HisUNSM_d99L6NTVad78Xgjw>
Cc: IETF <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, 13 Apr 2016 20:04:23 -0000

John, your memory / perception of the discussion around participation 
differs markedly from mine.
Your interpretation that even sitting quietly is still attempting to 
influence the outcome is specifically at variance with the discussion 
that gave rise to that wording, as I heard it.

I would also note htat any chair who tries to use the number of people 
who don't say anything as aqn indication of any aspect of a WG decision 
is simply asking for trouble.  Which is why most chairs, when trying to 
get a sense of the room on something, always ask the obverse question, 
and sometimes even ask "how many people don't care."

Yours,
Joel

On 4/13/16 1:41 PM, John C Klensin wrote:
>
>
> --On Tuesday, April 12, 2016 17:33 +0000 Michael Cameron
> <michael.cameron@ericsson.com> wrote:
>
>> John said:
>>
>> As a random member of the community, whether I'm participating
>> in a WG, or even actively monitoring it, is fairly clear.  If,
>> for example, I'm attending its meetings (f2f or remotely) or
>> signed up for its mailing list, the community should be able
>> to assume that I'm watching the work in that WG and should be
>> required to make relevant IPR disclosures even if I don't
>> actually say anything or otherwise generate Contributions.
>>
>> My response:
>>
>> I appreciate that some are advocating for what they want the
>> rules to be, but let's level set as to what they are.
>> Attending meetings, being signed up for mailing lists or
>> watching work in a WG does not obligate one to make any IPR
>> disclosures.  That was discussed in detail at the last IETF
>> meeting when the IPR Group met (Orlando, IIRC). The IPR
>> disclosure obligation arises only with respect to known IPR
>> reading on Contributions (for Contributors) and for
>> non-Contributors, the disclosure obligation only applies to
>> known IPR reading on a draft on which such non-Contributor
>> actively seeks to influence the outcome of the disposition of
>> a draft (active participation).
>
> Again, you are splitting hairs in a very lawyer-like fashion
> (you may take that as a complement if you like).   But I suggest
> that, e.g., responding to a request for a hum, or even not
> humming when a WG Chair asks a question and does not ask for
> hums on the opposite or on any other alternatives, constitutes
> "actively seeking to influence the outcome...".  If I'm sitting
> in the WG session at a time a WG Chair asks
> consensus-determining questions and I don't want to be counted
> as for, against, or indifferent (itself a potentially
> influencing position), I'd best head for the door rather than
> sitting there.
>
> My recollection of that last meeting of the IPR WG (and several
> before it, both immediately before and over the years) is
> apparently a bit different from yours.   My understanding of the
> discussion there was that the community's intent is that, if one
> knew of IPR that might reasonably be expected to bear on the
> work of a WG or a particular document, the expectation was that
> one would disclose (with the level of that expectation
> deliberately lower if one was not directly connected to the IPR
> than if one was directly connected.  If, for some reason,
> disclosure was impossible and/or would violate other
> commitments, then one was expected to be clearly isolated from
> the work generally and from any reasonable doubts about whether
> one had influenced a decision or attempted to do so.    IMO, the
> alternatives lead to madness, e.g., can you imagine wanting to
> know who was sitting next to someone so as to be able to ask is
> he or she hummed, made silly faces, or otherwise tried to
> influence the outcome of a discussion about a draft?
>
> Now, I think there is a separate issue, which is when the cases
> arise from which the IETF threatens to apply sanctions for
> violating the rules.  I think we need to deal with the gray
> areas in which someone made a reasonable judgment call
> (including cases in which there is question about whether
> first-party or third-party rules apply) in a reasoned, flexible,
> and generous way, reserving the punishments and nasty behavior
> for clear cases or patterns of abuse.     I think our actual
> practice has been consistent with that approach.
>
>> John said:
>>
>> If you are the AD responsible for a WG, then I think the
>> community gets to assume that you know what its work items
>> are, have approved document editors, and have at least read
>> the abstracts of the various drafts, i.e., that you are
>> participating.  If you are some other AD in the same area,
>> well, areas differ a lot and over time.  In some cases, ADs
>> shadow each other as a mutual backup arrangements and I'd
>> expect to be able to treat all ADs in the same area as
>> "participating" in all WGs.  In others, WGs get divided up
>> among ADs, after which the area might as well be as many
>> separate ones as there are ADs.  At IETF evaluation time, any
>> ADs who record a position other that "abstain" on a spec, or
>> to engage in any IESG discussion about it, has presumably
>> studied that spec closely enough to incur disclosure
>> obligations if IPR is known to them because making a decision
>> to adopt (or not) is clearly "participation".  The same issue
>> might exist with Co-chairs of a WG with many tasks.  I'd
>> normally assume that each one is familiar with and
>> participating in every work item, but it isn't hard to imagine
>> situations in which work might be split up along clear
>> boundaries with one co-chair getting involved in the work of
>> the other only at around the time of Last Call if then.
>>
>> My response:
>>
>> We need to be careful not to place on Area Directors
>> unreasonable burdens and obligations.  Further, there needs to
>> be certainty as to what the obligations are.   The obligations
>> imposed on Area Directors to declare known IPR should be
>> limited to those activities in which they actively
>> participate.  I'll defer to the ADs, but I would think that an
>> AD acting on a recommendation or advice from a WG as to how to
>> proceed on a Specification, without more, does not necessarily
>> rise to the level of active participation.
>
> That would be great, but it is just not consistent with how the
> IESG functions.   ADs are just not expected to passively accept
> WG recommendations, at least unless they have been very actively
> involved in the WG and is management.  Instead, they are called
> upon to evaluate those recommendations and make recommendations
> to the community about them.  That is just not a passive,
> "without more" sort of relationship.
>
> However, I think this is showing up a more fundamental problem.
> If the community still has the same understanding of the general
> intent of the IPR and disclosure rules as it did when the WG
> concluded, then treating a document update that clarifies and/or
> better aligned with that general intent as an individual
> submission from Scott and Jorge.  If, however, we have
> significant disagreements about what the intent was, and maybe
> even about whether things have changed enough that the intent
> needs to be re-evaluated, then, at least IMO, it is unreasonable
> to expect that we can gets things right on the IETF list as part
> of a Last Call on an individual submission.  Instead, if we have
> reacted the point where a debate about principles is needed, it
> is almost certainly time to reconvene/ recharter the WG.
>
>      john
>
>
>
>
>


From nobody Wed Apr 13 13:06:14 2016
Return-Path: <stewe@stewe.org>
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 A5E0612B055 for <ietf@ietfa.amsl.com>; Wed, 13 Apr 2016 13:06:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.903
X-Spam-Level: 
X-Spam-Status: No, score=-1.903 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] 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 dNRk6ogxYnat for <ietf@ietfa.amsl.com>; Wed, 13 Apr 2016 13:06:10 -0700 (PDT)
Received: from na01-bl2-obe.outbound.protection.outlook.com (mail-bl2on0122.outbound.protection.outlook.com [65.55.169.122]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7439912E12F for <ietf@ietf.org>; Wed, 13 Apr 2016 13:06:10 -0700 (PDT)
Received: from BLUPR17MB0275.namprd17.prod.outlook.com (10.162.235.146) by BLUPR17MB0274.namprd17.prod.outlook.com (10.162.235.145) with Microsoft SMTP Server (TLS) id 15.1.453.26; Wed, 13 Apr 2016 20:06:06 +0000
Received: from BLUPR17MB0275.namprd17.prod.outlook.com ([10.162.235.146]) by BLUPR17MB0275.namprd17.prod.outlook.com ([10.162.235.146]) with mapi id 15.01.0453.030; Wed, 13 Apr 2016 20:06:06 +0000
From: Stephan Wenger <stewe@stewe.org>
To: Michael Cameron <michael.cameron@ericsson.com>, John C Klensin <john-ietf@jck.com>, Alissa Cooper <alissa@cooperw.in>, Jari Arkko <jari.arkko@piuha.net>
Subject: Re: Last Call on draft-bradner-rfc3979bis-08.txt ("Intellectual Property Rights in IETF Technology")
Thread-Topic: Last Call on draft-bradner-rfc3979bis-08.txt ("Intellectual Property Rights in IETF Technology")
Thread-Index: AQHRlaupKR9yu1RueEWA9RrAiHSISp+IOm6A//+ks4A=
Date: Wed, 13 Apr 2016 20:06:06 +0000
Message-ID: <063308B8-478F-48D4-9A67-7381105D4DAF@stewe.org>
References: <16849BC54F958DF4DB61843A@JcK-HP8200.jck.com> <36BAA6A693139D4BBCB37CCCA660E08A14FDCB16@eusaamb101.ericsson.se>
In-Reply-To: <36BAA6A693139D4BBCB37CCCA660E08A14FDCB16@eusaamb101.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: ericsson.com; dkim=none (message not signed) header.d=none;ericsson.com; dmarc=none action=none header.from=stewe.org;
x-ms-exchange-messagesentrepresentingtype: 1
x-originating-ip: [50.174.30.183]
x-ms-office365-filtering-correlation-id: 125c8550-23d6-498c-4a9d-08d363d70c24
x-microsoft-exchange-diagnostics: 1; BLUPR17MB0274; 5:bPfTqN06WLXKIHLdIgrcZqsvJLCKN2Ehg0JCgiV77P478XB2g9qfBrJuIKiWd0I/9E8b0HUIpL3aKiYYiKBCImxEv2PNGk3yPG7l7lUVEGFlcb0tbmPXC+PcdGUo9iMISUhlHPPFnadFFDCK67m2MA==; 24:EraMAIIQgT5YMi50rwg3L9H+Cs1bhOC0RMUFG659RnzOVGtD7dJ7qDSvb10XbeVitTh2FdiT0d2ohHZONA4vTK2MvkcYAB9f1eR21DitblU=
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:BLUPR17MB0274;
x-microsoft-antispam-prvs: <BLUPR17MB027486F684C02EDF11D8423DAE960@BLUPR17MB0274.namprd17.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040074)(601004)(2401047)(8121501046)(5005006)(10201501046)(3002001)(6041046)(6043046); SRVR:BLUPR17MB0274; BCL:0; PCL:0; RULEID:; SRVR:BLUPR17MB0274; 
x-forefront-prvs: 0911D5CE78
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(24454002)(586003)(102836003)(3846002)(6116002)(1220700001)(1096002)(1720100001)(15975445007)(77096005)(83716003)(122556002)(92566002)(2950100001)(2900100001)(11100500001)(87936001)(5004730100002)(66066001)(54356999)(81166005)(50986999)(76176999)(82746002)(36756003)(5008740100001)(2906002)(19580395003)(5002640100001)(106116001)(19580405001)(86362001)(230783001)(10400500002)(99286002)(189998001)(33656002)(5001770100001)(4326007)(42262002)(104396002); DIR:OUT; SFP:1102; SCL:1; SRVR:BLUPR17MB0274; H:BLUPR17MB0275.namprd17.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en; 
spamdiagnosticoutput: 1:23
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
Content-ID: <BA500049B35BC24CAECCCDC0CBC699AD@namprd17.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: stewe.org
X-MS-Exchange-CrossTenant-originalarrivaltime: 13 Apr 2016 20:06:06.1101 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 865fc51c-5fae-4322-98ef-0121a85df0b6
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BLUPR17MB0274
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/HmUGxi5T-uTBW0_feMftksYXr-I>
Cc: IETF <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, 13 Apr 2016 20:06:13 -0000

SGkgSm9obiBhbmQgTWlrZSwNCg0KDQoNCk9uIDQvMTMvMTYsIDExOjMyLCAiaWV0ZiBvbiBiZWhh
bGYgb2YgTWljaGFlbCBDYW1lcm9uIiA8aWV0Zi1ib3VuY2VzQGlldGYub3JnIG9uIGJlaGFsZiBv
ZiBtaWNoYWVsLmNhbWVyb25AZXJpY3Nzb24uY29tPiB3cm90ZToNCg0KPlsuLi5dDQo+SSdsSSB0
cnkgdG8gcmVzcG9uZCB0byBzb21lIG9mIHlvdXIgb3RoZXIgcG9pbnRzIGluIGEgbGF0ZXIgcG9z
dCwgYnV0IG9uZSB0aGluZyBzdG9vZCBvdXQgdGhhdCBJJ2QgbGlrZSB0byBhZGRyZXNzIHJpZ2h0
IGF3YXkuICAgSSBkaXNhZ3JlZSB0aGF0IHNpdHRpbmcgcGFzc2l2ZWx5IGluIGEgbWVldGluZyBh
bmQgbm90IGh1bW1pbmcgY291bGQgY29uc3RpdHV0ZSAiYWN0aXZlbHkgc2Vla2luZyB0byBpbmZs
dWVuY2UgdGhlIG91dGNvbWUuLi4iICANCg0KVGhlIE9ybGFuZG8gSVBSYmlzIG1lZXRpbmcgcmVw
b3J0IGNhbiBiZSBmb3VuZCBoZXJlOiBodHRwOi8vd3d3LmlldGYub3JnL3Byb2NlZWRpbmdzLzg2
L21pbnV0ZXMvbWludXRlcy04Ni1pcHJiaXMNCg0KVGhlIHJlbGV2YW50IHNlY3Rpb24gaXMgdGhp
czoNCiINClNFTlNFIE9GIFRIRSBST09NDQoNClJ1c3MgSG91c2xleTogTGV0J3MgdGFrZSBhIHNl
bnNlIG9mIHRoZSByb29tIG9uIHRoaXMgdG9waWMuICBJcyBhY3RpbmcgaW4NCm9yZGVyIHRvIGlu
Zmx1ZW5jZSB0aGUgb3V0Y29tZSBvZiB0aGUgZGlzY3Vzc2lvbiwgYW5kIG5vdCBsaXN0ZW5pbmcg
b3INCndhdGNoaW5nIHRoZSBhY3Rpb24gb2Ygb3RoZXJzPyAgVGhhdCBpbmNsdWRlcyBzaG93IG9m
IGhhbmRzLCB3cml0aW5nLA0KaHVtbWluZywgYW5kIHNvIG9uLg0KDQpTdHJvbmcgc2Vuc2Ugb2Yg
dGhlIHJvb20gdGhhdCBhY3RpdmUgaW5mbHVlbmNlIGNvdW50cyBhcyBwYXJ0aWNpcGF0aW9uLA0K
YnV0IGxpc3RlbmluZyBhbmQgd2F0Y2hpbmcgZG9lcyBub3QuDQrigJwNCg0KSSBhdCBsZWFzdCBm
b3VuZCB0aGUgb3V0Y29tZSBvZiB0aGUgZGlzY3Vzc2lvbiBzZW5zaWJsZSB0aGVuLCBhbmQgYXBw
cm9wcmlhdGVseSByZXByZXNlbnRlZCBpbiAzOTc5YmlzLTA4IG5vdy4NCg0KVG91cmlzbSBpcyBh
bGxvd2VkLiAgU2l0dGluZyBpbiB0aGUgcm9vbSAob3Igb24gYSBtYWlsaW5nIGxpc3QgZm9yIHRo
YXQgbWF0dGVyKSwgbGlzdGluZyBxdWlldGx5LCB3aXRoIGdvb2Qgb3IgaWxsIGludGVudGlvbnMs
IGlzIGFsbG93ZWQuICBQaHlzaWNhbCBwcmVzZW5jZSBpbiB0aGUgcm9vbSAob3Igc3Vic2NyaXB0
aW9uIHRvIGEgbWFpbGluZyBsaXN0KSBkb2VzIG5vdCBjb25zdGl0dXRlIFBhcnRpY2lwYXRpb24u
ICBXZSBsaXZlIHdpdGggdGhlIHJpc2sgb2Ygc3BlY3VsYXRpdmUgcGF0ZW50IGFwcGxpY2F0aW9u
IGZpbGluZ3MsIGFuZCB3aXRoIHBlb3BsZSBvd25pbmcgZXNzZW50aWFsIElQUiBiZWluZyBxdWll
dCBhbmQga2VlcCB0aGUgSVBSIHNlY3JldCB3aGVuIHRoZXkgZmVlbCB0aGF0IG90aGVycyBkbyBl
bm91Z2ggdG8gaW5jbHVkZSB0aGVpciBJUFIgaW4gYSAgZm9ydGhjb21pbmcgUkZDLCBhbmQgc28g
b24tLWFsbCB0aGF0IGluIHRoZSBuYW1lIG9mIG9wZW5uZXNzLCBpbmNsdXNpdmVuZXNzIChpbmNs
dWRpbmcgaW5jbHVzaXZlbmVzcyB0byBuZXdjb21lcnMgb24gdG8gdGhlIElFVEYsIG9yIHRoZSBz
dWJqZWN0IG1hdHRlciBvZiB0aGUgV0cpLCBjcm9zcyBmZXJ0aWxpemF0aW9uIGFuZCBzbyBvbi4g
IFdlIGRvIG5vdCB3YW50IGNsb3NlZCByb29tcyBhbmQgY2xvc2VkIG1haWxpbmcgbGlzdHMuICBU
aGUgdW5kZW5pYWJsZSByaXNrLCBhbmQgdGhlIGNvc3QgYXNzb2NpYXRlZCB3aXRoIHRoaXMsIHdl
IGFyZSB3aWxsaW5nIHRvIHBheS4gIA0KDQpTdGVwaGFuDQoNCj4NCj5CZXN0LCBNaWtlDQo+DQo+
DQo+DQo+DQo=


From nobody Wed Apr 13 13:12:59 2016
Return-Path: <brian.e.carpenter@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 35CB212E438 for <ietf@ietfa.amsl.com>; Wed, 13 Apr 2016 13:12:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 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, RCVD_IN_DNSWL_LOW=-0.7, 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 0sFADJ9kqsLv for <ietf@ietfa.amsl.com>; Wed, 13 Apr 2016 13:12:56 -0700 (PDT)
Received: from mail-pf0-x233.google.com (mail-pf0-x233.google.com [IPv6:2607:f8b0:400e:c00::233]) (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 ED17C12E42D for <ietf@ietf.org>; Wed, 13 Apr 2016 13:12:55 -0700 (PDT)
Received: by mail-pf0-x233.google.com with SMTP id 184so38392556pff.0 for <ietf@ietf.org>; Wed, 13 Apr 2016 13:12:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=subject:to:references:cc:from:organization:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=TGvg2QG/5ZmcdY4Kr0Vhw6Bt6rkxgKMhK0zFfvZ3GY4=; b=eYeYaMJ50cmKZt8OhIj0bdKI7s8jGZi7H27gd4YIxT6nn79bQzN9QV74AmXx/TvCbE jrVP6PD6U9+Ic8NAQd2a/WnY0b6IMt09l0MjGKOdjA1NvOO15AEc3K2XTlr9sDDMk0pF BygR5IRKGB5OOJ6ij7BQBrP+OzccsA0WeMZ90GgPte8oJnL+btH+TZ6gSIibQogZt26K InlQbxcfw47KnqAqcB8SbOIzI/0qUQx5O9lZO9uP0YBNZj41e9oerqe/MpCsq9YhRXDc U1i+HpSTE1Jsk/cL7ZDfidJUqSrWdc6sBzQOCrbu3nvaItHKJazDbcdpi5dL+ibn/iTp II/A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:cc:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=TGvg2QG/5ZmcdY4Kr0Vhw6Bt6rkxgKMhK0zFfvZ3GY4=; b=mpJiJit/hz8pGk36NWDzCi5AxImRp5f8IZWJ5FPAg8gtroDLdTPlNo/lMefIod0B8d gth/nyly62tJ2AlVZp7326gHh3qPpLRg+vvUpzT07k4T8TE1rQxQCQolob2Y1hwIjNrv T/O+8XnMgVzGDWgUDsmx9e/fPk9u7YjFkgNEL7OZkuSQKvQPwv/EyubuwnUOGUC4aK5u uAXE6qHCBmjiaKawEgexKvcp9xqWt9US9U9eHFdBAC1mJoDa6e0YxvxNZWfzZOsWVoyn c4YKpRNlkqpXyS62qYeZ6o4zejehmBmxD3tSmzSPUnXiscsQEpSK/jPJJwHM5hEmCYrW Dt1g==
X-Gm-Message-State: AOPr4FUA9h3NBK0wFDU6mGrMNSwvoNc/yMJc2lshgxAQbONFKot2HC1KCdB5lBrecDF2PQ==
X-Received: by 10.98.1.69 with SMTP id 66mr15976754pfb.10.1460578375589; Wed, 13 Apr 2016 13:12:55 -0700 (PDT)
Received: from ?IPv6:2406:e007:5576:1:28cc:dc4c:9703:6781? ([2406:e007:5576:1:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id rw2sm53096645pab.30.2016.04.13.13.12.51 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 13 Apr 2016 13:12:54 -0700 (PDT)
Subject: Re: Last Call on draft-bradner-rfc3979bis-08.txt ("Intellectual Property Rights in IETF Technology")
To: John C Klensin <john-ietf@jck.com>, Michael Cameron <michael.cameron@ericsson.com>, Alissa Cooper <alissa@cooperw.in>, Jari Arkko <jari.arkko@piuha.net>
References: <16849BC54F958DF4DB61843A@JcK-HP8200.jck.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <570EA847.2090208@gmail.com>
Date: Thu, 14 Apr 2016 08:12:55 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2
MIME-Version: 1.0
In-Reply-To: <16849BC54F958DF4DB61843A@JcK-HP8200.jck.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/rgGbrLJO1Ir8ZoHU7vtKQBuIUjY>
Cc: IETF <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, 13 Apr 2016 20:12:57 -0000

On 14/04/2016 05:41, John C Klensin wrote:
...
> ... My understanding of the
> discussion there was that the community's intent is that, if one
> knew of IPR that might reasonably be expected to bear on the
> work of a WG or a particular document, the expectation was that
> one would disclose (with the level of that expectation
> deliberately lower if one was not directly connected to the IPR
> than if one was directly connected.  If, for some reason,
> disclosure was impossible and/or would violate other
> commitments, then one was expected to be clearly isolated from
> the work generally and from any reasonable doubts about whether
> one had influenced a decision or attempted to do so. 

Yes. Our aim, as I understand it, is to facilitate open discussion
and publication of open, interoperable standards, without damaging
the legitimate rights of IPR owners. That does not include allowing
IPR owners to disguise their IPR during the discussion, even by silence.
It also does not include forcing individuals to trigger onerous patent
searches, which is why our criterion has always been "reasonably and
personally known". This still seems like a reasonable compromise, and
I don't see the proposed updates as a fundamental change to the way ADs
and WG Chairs have always been expected to behave. We're just trying
to make it crystal clear.

As far as I know, the IETF isn't infected by people from non-practicing
entities, and all the major patent-writing companies have generally
played the game honestly. So I don't think we have a burning issue
here, just a desire to clarify the documents for future participants
and contributors.

    Brian


From nobody Wed Apr 13 13:27:09 2016
Return-Path: <brian.e.carpenter@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 80CA512E0A1 for <ietf@ietfa.amsl.com>; Wed, 13 Apr 2016 13:27:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 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, RCVD_IN_DNSWL_LOW=-0.7, 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 tvHNkQregMcM for <ietf@ietfa.amsl.com>; Wed, 13 Apr 2016 13:27:06 -0700 (PDT)
Received: from mail-pf0-x230.google.com (mail-pf0-x230.google.com [IPv6:2607:f8b0:400e:c00::230]) (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 39A6E12DFDB for <ietf@ietf.org>; Wed, 13 Apr 2016 13:27:06 -0700 (PDT)
Received: by mail-pf0-x230.google.com with SMTP id c20so38356656pfc.1 for <ietf@ietf.org>; Wed, 13 Apr 2016 13:27:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=subject:references:from:organization:to:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=hLdB2fAPKgDNB7AGNEDaUwSn9xGDOE2+mJxXa+Ip2VQ=; b=LSihfL6IYAqka6pdfYviGQk1WI5Wic7sM0hkMpVFgMkjJwzKDmxp3h2i36HCIcfQoI wOoKWCuArYViUtdu3CKmnxLwnSjUTF5O9uiwLH5JCdUv3Op9D/barqBNXqTup2RFSYgh VMJCJKm3p9pGnFJoXhgaMdfp91WjzfXnkqxNTq8X2lJ1SEd5hVDNp+8sn04SpDrDJBIs mHTpxEuXpZB6QxVNDWFGerZc5cMNxsLXF7u+I6x8/MgXdAk/5D5cszTxGt3SnKa6SHSw DfuvlEtaT0X3yFJDFLMOgvhfHEAj8YIi5OjfSQc2PEJdHq2KhMFK1xxdXSx5GABVqdK4 L57Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:references:from:organization:to :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=hLdB2fAPKgDNB7AGNEDaUwSn9xGDOE2+mJxXa+Ip2VQ=; b=MHk72mK8UTV6By+372dhWQlb9oeos94F7Ej/eFmEdZcQqGbvnWDAp8/cylXJE290lk wSY4Uo8b0urfgE9fqqSg/XJai4eQtisQd+QtWp9S4WBuSUJfaLBqYCzboGhvHYYkVxOf lbQc+3/esV7NKiQxvu3DvAkLn+vhu6CjRc2uDMrpkWmVwFcFvFjE87y3EI0EshUSdqJj vl0PfuVm6gVZfGjzUSIVfXsVJMNqm2dgtX0tj1GA0Avihf2AsZQDZnIho9ygK9X37+k9 a79hilbMxrvPLHfA3+W08hZEOyNTOlgdvXYL6uAiUl+CuUIXrHvODQU2DB2Zv8aAisHH zYCw==
X-Gm-Message-State: AOPr4FXKP7rFZU0K0WlIvSUulKSIVze9F8us2thSscjZ+6SwpP0qGjS2Vh44snnlen2suA==
X-Received: by 10.98.18.28 with SMTP id a28mr15591098pfj.145.1460579225808; Wed, 13 Apr 2016 13:27:05 -0700 (PDT)
Received: from ?IPv6:2406:e007:5576:1:28cc:dc4c:9703:6781? ([2406:e007:5576:1:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id d2sm13039074pfd.80.2016.04.13.13.27.03 for <ietf@ietf.org> (version=TLSv1/SSLv3 cipher=OTHER); Wed, 13 Apr 2016 13:27:04 -0700 (PDT)
Subject: Re: Last Call on draft-bradner-rfc3979bis-08.txt ("Intellectual Property Rights in IETF Technology")
References: <16849BC54F958DF4DB61843A@JcK-HP8200.jck.com> <36BAA6A693139D4BBCB37CCCA660E08A14FDCB16@eusaamb101.ericsson.se> <063308B8-478F-48D4-9A67-7381105D4DAF@stewe.org>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
To: IETF <ietf@ietf.org>
Message-ID: <570EAB9D.4060104@gmail.com>
Date: Thu, 14 Apr 2016 08:27:09 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2
MIME-Version: 1.0
In-Reply-To: <063308B8-478F-48D4-9A67-7381105D4DAF@stewe.org>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/Omj5MYmgItmel4hrDwuULvWwqPU>
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, 13 Apr 2016 20:27:07 -0000

On 14/04/2016 08:04, Joel M. Halpern wrote:
...
> Which is why most chairs, when trying to get a sense of the room on something, always ask the obverse question, and sometimes even ask "how many people don't care." 

I've also heard "who is abstaining?" and even "who is not listening?".

I think what John is getting at (please correct me if I'm wrong) is
individuals who have influenced the draft behind the scenes but stay
silent in public. Whether they are in the room is a little beside the
point.

On 14/04/2016 08:06, Stephan Wenger wrote:
> Hi John and Mike,
...
> "Strong sense of the room that active influence counts as participation,
> but listening and watching does not."

Fair enough - but that doesn't mean that the IETF condones non-disclosure.
And (for the topic originally under discussion) it's clear that a WG Chair
who declares consensus for adopting a document, or forwards it to the IESG
for publication, or an AD who reviews a document prior to an IESG ballot, is
participating. If the text doesn't make that clear to all readers, the text
is defective.

    Brian


From nobody Wed Apr 13 14:10:19 2016
Return-Path: <brian.e.carpenter@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 9744212D990 for <ietf@ietfa.amsl.com>; Wed, 13 Apr 2016 14:10:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 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, RCVD_IN_DNSWL_LOW=-0.7, 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 wefK7TzVIMZv for <ietf@ietfa.amsl.com>; Wed, 13 Apr 2016 14:10:15 -0700 (PDT)
Received: from mail-pa0-x235.google.com (mail-pa0-x235.google.com [IPv6:2607:f8b0:400e:c03::235]) (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 50BB612D9A4 for <ietf@ietf.org>; Wed, 13 Apr 2016 14:10:08 -0700 (PDT)
Received: by mail-pa0-x235.google.com with SMTP id fs9so19086576pac.2 for <ietf@ietf.org>; Wed, 13 Apr 2016 14:10:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=subject:to:references:cc:from:organization:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=6alhTX322tZEnxdqbFpeC84CoIfK1ZFRq4/cAv3A6l0=; b=GM09gJLPzl1uvAu/mZQ3KPrIROOJbR9kKn7S3u5qFMXX6hBo8pzTdxKI78VzwjeGVL qRJ69GqMzOQ208wPKHRH3MVQ2fmIYOGKa/IlHryFMhKCyaUMGhu12Pf+u5LIC/5cYb0e ubZveDXeR2jiq3Vru0ln8WX209Nd9Xrj1FXF3hw6dVJ8cu6QljBlKT+jFIf8sKW8L7/R b9kVKCE9crdyIZ99ogJRBZZToxxHl6mGT4VwgwWnyaJR78ZHMD5oBb5ohAKscbWUWRAt fjYlxHef7IWuxmO4eqCqNGKliYVp4YEvIuVVAUju1IN+vXe1Dpcy+m+8yVsBm0IYB04G oV4g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:cc:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=6alhTX322tZEnxdqbFpeC84CoIfK1ZFRq4/cAv3A6l0=; b=AoLU7HAYfjMOokQWNGhfdmQnT5g5G8KSp6mCfYk5EFYjM8CfZ2WsQEOwje6sn3CTTi Q9RfyQOvk+jj9Ml2pcpp6MlI+MFhgwSIAK88W7Gd9vyazLiVJSzdPpTkKSmQGA6TZADj Qx5i+c3jOiT+xRVmJFMr3zdsLK5i4c51ehpbRLFaD6cAaYETqdGCYWL+qfyBNQ/AY4Dt LMlVkpzrkeiOjUBA4FIQOTc8IJsJf6eck3yYI0fBr5j6xqiPIEFQteBg4/hRQuCxlDjn OlMLpXY9Co8V8nGBpq2leQyvguJSiFQOcSvOexugOHOCeD/My+YpyCoqdetobNoeHhQp evag==
X-Gm-Message-State: AOPr4FWNWSfo7DcBqzr4G//JLASP5JvTTv22MXC/dUQzK+r5X0U5R+W3WvHItGZOnAiFow==
X-Received: by 10.66.246.165 with SMTP id xx5mr15909772pac.87.1460581807926; Wed, 13 Apr 2016 14:10:07 -0700 (PDT)
Received: from ?IPv6:2406:e007:5576:1:28cc:dc4c:9703:6781? ([2406:e007:5576:1:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id s64sm53124037pfi.77.2016.04.13.14.10.05 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 13 Apr 2016 14:10:06 -0700 (PDT)
Subject: Re: Remote only meetings? [Re: Concerns about Singapore]
To: Yoav Nir <ynir.ietf@gmail.com>
References: <570AB3AF.2050401@gmail.com> <87twj99c6w.fsf@tops.chopps.org> <CAKe6YvMyp-DyeDwpPY6KYmbDbnpgnvVk_cUStnA32wmgDWcz3w@mail.gmail.com> <BBF5DDFE515C3946BC18D733B20DAD233A62AA18@XMB122CNC.rim.net> <20160411104519.GA19092@gsp.org> <3F48466D-390C-4C18-B958-732AE3E46FF1@gmail.com> <20160411223403.GA6743@gsp.org> <87twj7eon7.fsf@tops.chopps.org> <20160412110839.GA20488@gsp.org> <8760vn82f2.fsf@tops.chopps.org> <20160412124639.GA27223@gsp.org> <570DAA2F.1040007@gmail.com> <81B4533B-0F39-442D-8546-019D9253047A@gmail.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <570EB5B3.4000806@gmail.com>
Date: Thu, 14 Apr 2016 09:10:11 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2
MIME-Version: 1.0
In-Reply-To: <81B4533B-0F39-442D-8546-019D9253047A@gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/NlXdDjvMmX7sMcC6uGVwiIZg4wA>
Cc: IETF discussion list <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, 13 Apr 2016 21:10:17 -0000

> Difficulty?  Why do you think that is getting worse?  There was an incr=
ease in hassle shortly after 9/11, but I haven=E2=80=99t experienced any =
greater difficulties now as opposed to 10 years ago. Why do you think it=E2=
=80=99s set to become more difficult?

You live in a country that's had very strict airport security since the 1=
970s
(and since I lived in Geneva then, I also remember when Geneva airport wa=
s
almost a military encampment, caused by exactly the same events). London =
got
tough in the 1970s too, for a different reason. It slowly spread across E=
urope
and the world, with the US remaining amazingly lax until 2001. There was =
certainly
a step function after 9/11 but it's really been a constant trend since ~1=
970.
I think you'll find that Paris and Brussels have recently got a lot tough=
er.
Now it's becoming an issue for long-distance trains in Europe. Expect mor=
e.

Regards
   Brian

On 13/04/2016 23:31, Yoav Nir wrote:
>=20
>> On 13 Apr 2016, at 5:08 AM, Brian E Carpenter <brian.e.carpenter@gmail=
=2Ecom> wrote:
>>
>> Cherry-picking a few points:
>> On 13/04/2016 00:46, Rich Kulawiec wrote:
>> ...
>>> And the difficulties/expense of travel are only going to get worse
>>> for the forseeable future: they're not going to get better.
>>
>> That is indisputable.
>=20
> OK, I=E2=80=99ll bite.=20
>=20
> Expense goes up and down with the price of oil, competition, regulation=
 and a zillion other factors.=20
>=20
> Difficulty?  Why do you think that is getting worse?  There was an incr=
ease in hassle shortly after 9/11, but I haven=E2=80=99t experienced any =
greater difficulties now as opposed to 10 years ago. Why do you think it=E2=
=80=99s set to become more difficult?
>=20
> Yoav
>=20
> .
>=20


From nobody Wed Apr 13 16:15:40 2016
Return-Path: <john-ietf@jck.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 8A7DC12DE5C for <ietf@ietfa.amsl.com>; Wed, 13 Apr 2016 16:15:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.896
X-Spam-Level: 
X-Spam-Status: No, score=-2.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.996] 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 f8e-ghu43kZo for <ietf@ietfa.amsl.com>; Wed, 13 Apr 2016 16:15:35 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5AD2E12DE78 for <ietf@ietf.org>; Wed, 13 Apr 2016 16:15:35 -0700 (PDT)
Received: from [198.252.137.10] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1aqU0N-0003pA-4J; Wed, 13 Apr 2016 19:15:27 -0400
Date: Wed, 13 Apr 2016 19:15:22 -0400
From: John C Klensin <john-ietf@jck.com>
To: "Joel M. Halpern" <jmh@joelhalpern.com>, Michael Cameron <michael.cameron@ericsson.com>, Alissa Cooper <alissa@cooperw.in>, Jari Arkko <jari.arkko@piuha.net>
Subject: Re: Last Call on draft-bradner-rfc3979bis-08.txt ("Intellectual Property Rights in IETF Technology")
Message-ID: <ACCBB67844B9C997E5128176@JcK-HP8200.jck.com>
In-Reply-To: <570EA63E.6090601@joelhalpern.com>
References: <16849BC54F958DF4DB61843A@JcK-HP8200.jck.com> <570EA63E.6090601@joelhalpern.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/VnzysQ_ius3qrgum8fUrRg7JBNg>
Cc: IETF <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, 13 Apr 2016 23:15:38 -0000

--On Wednesday, April 13, 2016 16:04 -0400 "Joel M. Halpern"
<jmh@joelhalpern.com> wrote:

> John, your memory / perception of the discussion around
> participation differs markedly from mine.
> Your interpretation that even sitting quietly is still
> attempting to influence the outcome is specifically at
> variance with the discussion that gave rise to that wording,
> as I heard it.

ok.  I certainly agree that sitting quietly would be pushing it
and defer to your memory and that of Stephen and the Orlando
minutes.  Again, what I think is more important is avoiding
getting into a discussion of "did he or did he not actually
hum?"   Or do you think humming is not "attempting to influence
a decision" and, if so, how loudly is needed?   See below.

> I would also note htat any chair who tries to use the number
> of people who don't say anything as aqn indication of any
> aspect of a WG decision is simply asking for trouble.  Which
> is why most chairs, when trying to get a sense of the room on
> something, always ask the obverse question, and sometimes even
> ask "how many people don't care."

I absolutely agree with that.  But the last time I heard a chair
try to take only a "for" hum, only to be asked by the group to
ask the negative question was, hmm, in a WG last week.  It may
be a bad practice, but it isn't an uncommon behavior.   Note
that these distinctions will get increasingly important as
remote participation (as distinct from remote watching or
observing or lurking increases).  For example, last week,
Meetecho required that I check a box to distinguish between
being "a participant" and "an observer".  If I check the
"participant" box, but don't get myself in queue, say anything
substantive on Jabber, or click on "hum" does "solely to the
extent of such participation" [3979bis section 1(f)] protect me
from IPR obligations regardless of what 3979bis section 1(k)
might say?    If the answer is "yes, I am protected", how
substantive do my Jabber comments have to be to to constitute
participation?  Can I say "the audio isn't working" without that
being a comment to the WG?    

Just to be clear about how muddled this is, I note that 39796bis
Section 3.3 is titled "Obligations on Participants" and starts
"By Participating in IETF, each Participant..." but then the
specific statements that follow talk only about Contributors.
Given the level of hair-splitting we seem to be getting into,
could that be taken to mean that non-Contributor Participants
are really not Participants?

At the other extreme, Section 6 says "Since disclosure is
required for anyone making a Contribution or _participating in
IETF activities_..." (emphasis mine) [1].  Note that doesn't
say, e.g., "entangled with a particular document or even WG or
trying to influence its outcome", it refers to IETF activities
generally.  Now, showing up at the Social, or coming to a
meeting break and eating the cookies is fairly clearly
"participating in an IETF activity".  Or, if you take the 3979
wording as better reflecting the intent, involvement in a
discussion of meeting locations (with not participation in the
IETF's technical work at all) is "participating in IETF
discussions).  Now a sentence further on adds "about a
technology", but that doesn't seem to modify the earlier
sentences or to actually add much to "disclosure is required".

Now I don't know if Section 13 of 3979bis is considered
normative, but, if it is, we have yet another definition, i.e.,
"Participation...At a high level, suggested that anyone who says
something on a list or in a WG meeting is required to make IPR
disclosures".   Now, given that or just the text earlier in
3979bis or, for that matter, in 3979, please answer the
following questions:

(i) If an AD sends a note to a WG list that reads "We are
debating whether the WG needs to meet at IETF 97", does that
constitute participating in all of the work of the WG?  Any of
the work?   The current text of 3979bis fairly clearly says
"yes" because of the sweeping obligations it puts on ADs but we
have been debating that.

(ii) If someone stands up in a WG meeting and says "would people
please be more careful to announce their names clearly before
speaking", is that different from "saying something... in a WG
meeting"?  How about if a remote participant says exactly the
same thing on Jabber?   Good sense says that it clearly is
different from participation that would incur disclosure
obligations (especially if the sections of IETF 86 minutes
quoted by Steve count), but one can't derive that from the text
of 3979bis (or, AFAICT, 3979).

(iii) If an AD, via the tracking machinery, posts a note that
says, roughly, "Joe Blow has no objection to
draft-ietf-foo-barbaz-99" and that note, as is contemporary
practice, is posted to the foo WG mailing list, isn't that
"saying something on a list"?  Note that saying exactly the same
thing, in the same way, in 2006, would not have, by itself,
incurred any obligation (or any posting) because the tracker
didn't routinely copy things to WG mailing lists.  On the other
other hand, if an AD chose to explicitly tell a WG about her
decision on a particular document, that would fairly clearly be
a Contribution even under 3979.

(iv) If a remote participant enters something into Jabber
preceded by "MIC" and someone in the room stands up and reads
it, has the latter person thereby said something in a WG meeting
and therefore incurred participation and disclosure obligations?

To the extent to which I agree with Michael that people should
have clear expectations about when they are, or are not,
expected to disclose, the above suggests that things have gotten
rather muddled.  I'm suggesting that is exactly the case, that
we need to return to principles, and that those principles need
to not depend on "well, I didn't hum and therefore don't have to
disclose" or, much worse, "you can't prove I hummed audibly and
therefore I don't have to disclose".   

best,
   john


     john



[1] That comes almost directly from the slight different
statement in RFC 3979 Section 7, which reads "Since disclosure
is required for anyone submitting documents or participating in
IETF discussions...".  It is not clear to me which of the two is
narrower or if the rephrasing is a change in intent.



From nobody Wed Apr 13 16:28:35 2016
Return-Path: <john-ietf@jck.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 D0D4712D94D for <ietf@ietfa.amsl.com>; Wed, 13 Apr 2016 16:28:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.896
X-Spam-Level: 
X-Spam-Status: No, score=-2.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.996] 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 X77p2tgkg2G7 for <ietf@ietfa.amsl.com>; Wed, 13 Apr 2016 16:28:32 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5496B12DF76 for <ietf@ietf.org>; Wed, 13 Apr 2016 16:28:32 -0700 (PDT)
Received: from [198.252.137.10] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1aqUD0-0003rq-V8; Wed, 13 Apr 2016 19:28:30 -0400
Date: Wed, 13 Apr 2016 19:28:25 -0400
From: John C Klensin <john-ietf@jck.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, IETF <ietf@ietf.org>
Subject: Re: Last Call on draft-bradner-rfc3979bis-08.txt ("Intellectual Property Rights in IETF Technology")
Message-ID: <D57824C44CDD3EAB14344776@JcK-HP8200.jck.com>
In-Reply-To: <570EAB9D.4060104@gmail.com>
References: <16849BC54F958DF4DB61843A@JcK-HP8200.jck.com> <36BAA6A693139D4BBCB37CCCA660E08A14FDCB16@eusaamb101.ericsson.se> <063308B8-478F-48D4-9A67-7381105D4DAF@stewe.org> <570EAB9D.4060104@gmail.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/fryaHNj-A-jqVJjBF8UsHppFNlI>
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, 13 Apr 2016 23:28:34 -0000

--On Thursday, April 14, 2016 08:27 +1200 Brian E Carpenter
<brian.e.carpenter@gmail.com> wrote:

> On 14/04/2016 08:04, Joel M. Halpern wrote:
> ...
>> Which is why most chairs, when trying to get a sense of the
>> room on something, always ask the obverse question, and
>> sometimes even ask "how many people don't care." 
> 
> I've also heard "who is abstaining?" and even "who is not
> listening?".
> 
> I think what John is getting at (please correct me if I'm
> wrong) is individuals who have influenced the draft behind the
> scenes but stay silent in public. Whether they are in the room
> is a little beside the point.

Yes, that is my main concern -- that we do not let such
publicly-quiet influencers off the hook.

> On 14/04/2016 08:06, Stephan Wenger wrote:
>> Hi John and Mike,
> ...
>> "Strong sense of the room that active influence counts as
>> participation, but listening and watching does not."
 
> Fair enough - but that doesn't mean that the IETF condones
> non-disclosure. And (for the topic originally under
> discussion) it's clear that a WG Chair who declares consensus
> for adopting a document, or forwards it to the IESG for
> publication, or an AD who reviews a document prior to an IESG
> ballot, is participating. If the text doesn't make that clear
> to all readers, the text is defective.

And that is another key part of the point I'm trying to make.
It seems to directly contradict Michael's position that, AFAICT,
posits some sort of non-involved acceptance of a WG
recommendation that would not constitute participation.   Along
with wanting to stay very far from "I didn't really hum and
therefore I don't need to disclose", I want to be sure we
_never_ get into a situation in which Company A has a rule
against its employees disclosing IPR before patents have been
issued, a WG has a chair who works for company A, all ADs in the
Area of that WG work for company A, all three of them are
personally aware of relevant IPR, and yet there is some way to
dance around the rules such that no one is obligated to
disclose.  

The problem I see with trying to make extremely fine
distinctions about ways to not-quite-participate is that they
will almost certainly open up loopholes or edge cases that could
make such a scenario possible.  We could, of course, avoid such
scenarios by adopting firm rules that no AD can be responsible
for a WG whose Chair (or any co-chair) is from the same company
and perhaps that areas with two or more ADs must have all of
them from separate companies, but I think that cure might be
worse than the problem.

best,
   john


From nobody Thu Apr 14 05:59:35 2016
Return-Path: <hallam@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 64CE512DBD6 for <ietf@ietfa.amsl.com>; Thu, 14 Apr 2016 05:59:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.4
X-Spam-Level: 
X-Spam-Status: No, score=-2.4 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.199, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 dnEsZqDBHjGl for <ietf@ietfa.amsl.com>; Thu, 14 Apr 2016 05:59:31 -0700 (PDT)
Received: from mail-lf0-x22f.google.com (mail-lf0-x22f.google.com [IPv6:2a00:1450:4010:c07::22f]) (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 88ACE12D958 for <ietf@ietf.org>; Thu, 14 Apr 2016 05:59:31 -0700 (PDT)
Received: by mail-lf0-x22f.google.com with SMTP id c126so107629780lfb.2 for <ietf@ietf.org>; Thu, 14 Apr 2016 05:59:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:sender:date:message-id:subject:from:to; bh=SsRrOaEtBjHL9L3Ci/PZE1DUVB0L/AOOF9hasUC4nJI=; b=tjbLWNLk6RVOzM4sE4Rt53DXg1u/sKbm1WfvbKeqeYkgmyMyLDkcoWFYLH2Ae10dWf cAYIE7BA0RnXoDsFffEMoiEgoLdsxTbOTnnahJsSWHTnKAd1MhD7kvF14dFuBKBnIJ4Z nO+pnf46/n/yfxG56GpQF2Rk464eHbFWkMAY8GsixqilRVwkyV8rSHx15EJ60HrGxSye RJsoTjJmGP6PAbVQWj8/DzUNMcjV9rDvoXk9A3nzxqCV7CViYcnYOqZv5kaauWGgrzLa 5Kt2PLHDu0Lkg6fdkQoGNjr140H30eovQJ//0tAUU9jNsyZYuvayQGRIEmT7V+CHOQnl zogg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:date:message-id:subject:from :to; bh=SsRrOaEtBjHL9L3Ci/PZE1DUVB0L/AOOF9hasUC4nJI=; b=Z7IIhm78Wfz16kw9yM2IAmNiocP29aoixXPJYOPod/m8oetoUXyPse5nVtREr75Z3C w5JsOnmaN1hH2pYzUuEM1IxUni8Wp3/n/43D9ETdoipg6sjVzYfnp8clgq5m5ZjvejPg m74zNRigAInEAua3YrxWZCYJsM405opPa9lUKf1YX7R7vUCA60mrS+Ws1mKgD9VqJqiL yVaewJkJ/y8/sBDW6dj9ahWpnEGviSfIjrs9pUkzDBOlnnm8NPTr1F02J54Wn5xrxZqG RIA5k1uNSsvU8RryZMd+2uA6CJEng8PzgN6Ue6wBo9tpM7rT3IGSHJ//LK3Zm0VflO4d iO/w==
X-Gm-Message-State: AOPr4FWh8Nr5lBdyqwONBcScHHSsIYW3YfGRAXBMD1EhO5a8hggb9zkWgSvUeTh56cllW/gQaa91JhnfAfnWVg==
MIME-Version: 1.0
X-Received: by 10.25.138.7 with SMTP id m7mr1651361lfd.153.1460638769675; Thu, 14 Apr 2016 05:59:29 -0700 (PDT)
Sender: hallam@gmail.com
Received: by 10.112.151.67 with HTTP; Thu, 14 Apr 2016 05:59:29 -0700 (PDT)
Date: Thu, 14 Apr 2016 08:59:29 -0400
X-Google-Sender-Auth: ZIPV55bNf64vnvy6YI_itmMkw5c
Message-ID: <CAMm+Lwg-HTYCv2pGt=SP2+Xjoko6GcJ73kVzqXC1LBTOMDKV_A@mail.gmail.com>
Subject: Time to kill layer 2
From: Phillip Hallam-Baker <phill@hallambaker.com>
To: IETF Discussion Mailing List <ietf@ietf.org>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/0VNcRVSkPTiaR2ljNN-kskkpjQE>
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, 14 Apr 2016 12:59:33 -0000

This morning I spent an hour debugging the network to print out two
class projects that were due. Some points:

1) My ability to debug the network is better than 99% of the population
2) The interaction of Bonjour, DHCP and auto power saving is unfortunate
3) Things should still work after I have been away for a week
4) If vendors want to be selling all that IoT gear, they have to solve
these issues.

5) I want someone to blame. Right now when the network doesn't work, I
don't know who is the cause. I want one point of contact. Whoever is
that point of contact will get most of my networking money.


One of the biggest headaches in debugging is that 'smart hubs' are
not. They are actually very stupid. They make assumptions of network
topology that are not true. Another is the unfortunate implementation
of DHCP.

I don't use SNMP for a simple reason - it is not available to most
ordinary people. I want to understand networking for the 99%, not the
IETF 1%-ers.

All this networking gear is presented to me as black boxes over which
I have absolutely no control (which is fine-ish) and no visibility.

What we have today is the product of a historical process. I remember
the days when Ethernet ran on 10BaseT. But I installed my first switch
30 years ago and it has been a switched protocol for 20 years now.


It seems to me that there is a business opportunity for any vendor who
takes the rather obvious step of simplifying the system.

People talk about 'IP everywhere' and 'IP end-to-end' which is rather
odd when you think about the fact that virtually every local network
uses MAC addresses for routing.

One of the reasons that IP won against OSI was that it was simpler.
Applications ran on top of the IP layer with only TCP inbetween. Of
course these days we do have a Presentation layer, Web Services run on
HTTP. But unlike the OSI presentation layer, ours does not introduce
extra moving parts.

It seems to me that if we really believed in IP everywhere and IP
end-to-end we would insist that network switches be IP routers that
can be managed using BGP/OSPF or at least routing tables rather than
heuristic devices that try to guess where packets should go based on
goat entrails, phases of the moon or whatever they use.


What should have happened many moons ago was that DHCP should have
become a bidirectional protocol or a bootstrap to a bidirectional
protocol. So when a printer joins the network, it authenticates and
tells the network what it is. And this is all defined in one set of
specifications from one organization, none of which assumes that
security is an 'advanced', 'optional' or 'enterprise' feature.

Instead we have an ad-hoc layer trying to achieve the same result in
peer-to-peer fashion. A similar approach works for frogs as a
reproductive mechanism but only at the species level. It certainly
does not work for the individual ova which may or may not connect to
the printer it is trying to use to print the kids damned homework.


Seriously, the fact that things have scaled thus far and the 1% can
get them to work does not mean that we can get to the next level
without a serious rethink of the local network architecture.

The type of device I think we need would be first and foremost an IP
router. It would have ethernet plugs on the box and use ethernet layer
1 specs. But when a another 'True-IP' device was plugged in, it would
quickly negotiate a direct IP connection, oh and with proper 64KB
packets. It would also, authenticate, announce and turn on link layer
encryption.

Such a device would also be a legacy router. It would fake all the
signals necessary for a legacy ethernet device to function. It would
also be responsible for maintaining the local information for the
network service database and intercommunicating with other hubs to
achieve a global network view.


The net result of all this would be that I would never ever need to
install another printer (no, it is not actually necessary for every
stupid printer to have its own stupid printer driver). Opening the
'printers' folder would automatically show every printer that is on
the network or can be woken from slumber by the hub it connects to.


From nobody Thu Apr 14 06:48:59 2016
Return-Path: <mcr+ietf@sandelman.ca>
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 8343B12B021 for <ietf@ietfa.amsl.com>; Thu, 14 Apr 2016 06:48:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.897
X-Spam-Level: 
X-Spam-Status: No, score=-2.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.996, SPF_PASS=-0.001] 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 bca9pLqGW07D for <ietf@ietfa.amsl.com>; Thu, 14 Apr 2016 06:48:55 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ACA7512B012 for <ietf@ietf.org>; Thu, 14 Apr 2016 06:48:55 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 394D82002A; Thu, 14 Apr 2016 09:52:54 -0400 (EDT)
Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 533786375A; Thu, 14 Apr 2016 09:48:54 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Phillip Hallam-Baker <phill@hallambaker.com>
Subject: Re: Time to kill layer 2
In-Reply-To: <CAMm+Lwg-HTYCv2pGt=SP2+Xjoko6GcJ73kVzqXC1LBTOMDKV_A@mail.gmail.com>
References: <CAMm+Lwg-HTYCv2pGt=SP2+Xjoko6GcJ73kVzqXC1LBTOMDKV_A@mail.gmail.com>
X-Mailer: MH-E 8.6; nmh 1.6+dev; GNU Emacs 24.4.2
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Thu, 14 Apr 2016 09:48:54 -0400
Message-ID: <19051.1460641734@obiwan.sandelman.ca>
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/s6FExBKnWBAWxpJg6yWaR1CZ7Js>
Cc: IETF Discussion Mailing List <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, 14 Apr 2016 13:48:57 -0000

--=-=-=
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable


Phillip Hallam-Baker <phill@hallambaker.com> wrote:
    > People talk about 'IP everywhere' and 'IP end-to-end' which is rather
    > odd when you think about the fact that virtually every local network
    > uses MAC addresses for routing.

Agreed. We have 30 years of stupid layer-2 tricks, first caused by lack of
subnet'ing before CIDR, and then caused by lack of IPv4 space afterwards.

With IPv6, we have link-local addresses which essentially do what MAC
addresses did before, and we can throw around /128 routes and the like.

My contention is that once "homenet" takes off, that layer-2 switches will
simply disappear from the home.  They will all be layer-3, just because.

    > What should have happened many moons ago was that DHCP should have
    > become a bidirectional protocol or a bootstrap to a bidirectional
    > protocol. So when a printer joins the network, it authenticates and
    > tells the network what it is. And this is all defined in one set of
    > specifications from one organization, none of which assumes that
    > security is an 'advanced', 'optional' or 'enterprise' feature.

Yes, and DHCPv6 is very much like that.
And ANIMA and NETCONF and Eliot's MUD proposal are doing things like what y=
ou
suggest.

The problem is that there is too little investment, and those who want to
innovate are having to fight the FCC, etc.


=2D-=20
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -=3D IPv6 IoT consulting =3D-




--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQEVAwUBVw+fw4CLcPvd0N1lAQJlWwf8DPhQekOvKXPDexUzhsRK102VNdmVl+5R
xu0I6M5D454W4rT0Bzwh0qmi5KB9KIGAPkJI+YD859eZfNOkcdsHKoxlSllk4Pl6
ga+gwREDKL1WnrZdwz/zwaJV3tlHhvUhHG0b1RYdiBcyGMqB0R+zkqpnOkVvzrci
jux4Nzq1mNDjitbzS27OwY0IAyLkxRF8duI0JjIwc8Qrwhf+SWcgYkMhh1jl17gF
lATGBI2FV3+qfeF8ie+ZKZdZgHplgKtIky0PxyG9n9TH400aynCQQ7xhPh1fKNS9
THg1yqLu+KMk9VWgkiSMm/tXn+0Na+iZd+60+MmRZfZaUGuGToX5Jg==
=zI1p
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Thu Apr 14 07:15:23 2016
Return-Path: <chopps@chopps.org>
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 3BAA712D5D1 for <ietf@ietfa.amsl.com>; Thu, 14 Apr 2016 07:15:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.896
X-Spam-Level: 
X-Spam-Status: No, score=-2.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.996] 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 GkBW7cS8CIGQ for <ietf@ietfa.amsl.com>; Thu, 14 Apr 2016 07:15:19 -0700 (PDT)
Received: from smtp.chopps.org (smtp.chopps.org [54.88.81.56]) by ietfa.amsl.com (Postfix) with ESMTP id E6CC512D5A9 for <ietf@ietf.org>; Thu, 14 Apr 2016 07:15:18 -0700 (PDT)
Received: from tops.chopps.org (24-247-68-31.dhcp.trcy.mi.charter.com [24.247.68.31]) (using TLSv1.2 with cipher AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by smtp.chopps.org (Postfix) with ESMTPSA id D9E4460D08; Thu, 14 Apr 2016 14:15:17 +0000 (UTC)
References: <CAMm+Lwg-HTYCv2pGt=SP2+Xjoko6GcJ73kVzqXC1LBTOMDKV_A@mail.gmail.com>
User-agent: mu4e 0.9.16; emacs 24.5.1
From: <chopps@chopps.org>
To: Phillip Hallam-Baker <phill@hallambaker.com>
Subject: Re: Time to kill layer 2
In-reply-to: <CAMm+Lwg-HTYCv2pGt=SP2+Xjoko6GcJ73kVzqXC1LBTOMDKV_A@mail.gmail.com>
Date: Thu, 14 Apr 2016 10:15:16 -0400
Message-ID: <87shyol1jf.fsf@tops.chopps.org>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature"
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/I_x9tabnodmVoIGn_pC-8aUYgg8>
Cc: IETF Discussion Mailing List <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, 14 Apr 2016 14:15:20 -0000

--=-=-=
Content-Type: text/plain


Phillip Hallam-Baker <phill@hallambaker.com> writes:

> This morning I spent an hour debugging the network to print out two
> class projects that were due. Some points:
>
> 1) My ability to debug the network is better than 99% of the population
> 2) The interaction of Bonjour, DHCP and auto power saving is unfortunate
> 3) Things should still work after I have been away for a week
> 4) If vendors want to be selling all that IoT gear, they have to solve
> these issues.
>
> 5) I want someone to blame. Right now when the network doesn't work, I
> don't know who is the cause. I want one point of contact. Whoever is
> that point of contact will get most of my networking money.

...

> One of the reasons that IP won against OSI was that it was simpler.
> Applications ran on top of the IP layer with only TCP inbetween. Of
> course these days we do have a Presentation layer, Web Services run on
> HTTP. But unlike the OSI presentation layer, ours does not introduce
> extra moving parts.

The funny thing about mentioning OSI here is that it would probably be
very easy indeed to triage your network issue if your hosts were running
ES-IS, and your routers IS-IS. You could plug into IS-IS and see
everything. :)

Thanks,
Chris.

--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQIcBAEBCgAGBQJXD6X0AAoJEC4dgw7XuDAljWEQAJECS+X2Otumm7RCy2KQTiD1
LMHG8yOLb7jOQ1/i8KdJ2wWp9CiKy36yBR/Ia6w9/uRe582V4yJPMTPwvLxei33X
MEn4Zhh4BMmT7hS3vrn+MDzxsOZ1ALv9imkh5hLtCeyCsdyOqY58DRLi5irUbUj3
i5TyuHOw8TXIh78caKF8Sm/Yq0XYVKClxlsFHM+B91HX+qjaAReazM15A+eTTXeF
styOc6sbn9apEuZvpUJKAW1HyLf1G+PehhcLOe9cpxz0WD+HQsiK6UyI8raYtVsq
Wm0uOLUAPoYobcKck1m1NjgI4qiqC5FLqu7wk2EfKvScl5vIuXbp1jxsw67BBtE8
8S8iGxem5xhR2BIWsnbNHKPllESbMg/YicEQfw8gGU7dtdBVhsSqIPcrGJ7Bdl8m
Ys8DKQfef7E6oeFTXKc44rBeXa1tNnw8Kyi6qkdkO5I8vJLi747TBggYHxzP1yFJ
jUo0Yl1vbT9MTjVhkhs6P+HGFC5wZLmqbnv690a4ycuAqrJIEdcB0qjH4gsEvmt2
AotWYE+yWv2sjWfNpTUDsRu5RUVrZp6sK8FAEvBq2iqI/Z0yL3YCWy0e0w2DcU3y
AcbbR2hjjNtBXQMsohTgECUVLVQ6SgAJuMqxdc9ibLpWaU0pxrz8NyM/7jiufItt
MX0m7j/kB7cvBWCMHPx+
=MxMC
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Thu Apr 14 08:22:33 2016
Return-Path: <mellon@fugue.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 306F512E5C2 for <ietf@ietfa.amsl.com>; Thu, 14 Apr 2016 08:22:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.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 EL4Nyrrxdpqj for <ietf@ietfa.amsl.com>; Thu, 14 Apr 2016 08:22:13 -0700 (PDT)
Received: from mail-lf0-x231.google.com (mail-lf0-x231.google.com [IPv6:2a00:1450:4010:c07::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 7F57C12E52E for <ietf@ietf.org>; Thu, 14 Apr 2016 08:22:05 -0700 (PDT)
Received: by mail-lf0-x231.google.com with SMTP id g184so112940873lfb.3 for <ietf@ietf.org>; Thu, 14 Apr 2016 08:22:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=yNRY/pkumXb11o1p8CjHHwM3vSOmlsP9NV6KwN5F4pU=; b=jEJLSlbefzbk/741d85S1XvrD1iKbOSnEHFZk/G8S4NVdWEtU1N7/mjGE3c16+nyIC NSe7y4Onj1Umzzmw/5OqVk+DRQ723x2JsIacoq3WXqxKe6kMQ2o1AIw1hzOhSLjABkAh SmMRIZdaMW8oCRjNnUGXpOFKku5Ly4i6jZA4VRvjEiZo3oq1dnOb7vhcDObe6OgNjYWP 7TAMbrL1JLSTq4tzza/pT5CoeOs3kAqvhDdRvMHTjPFTtUqRoeLXY77aiAZSE9RjrOlt WjwqezQC8aHVIZIQEu5nN4AHSW4jA381KLQrE3GKLhivnIS4qE2wVaTwWfBhK8h6+qPi pbpQ==
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=yNRY/pkumXb11o1p8CjHHwM3vSOmlsP9NV6KwN5F4pU=; b=Ivs8Gj7TZWn/wlJ8xwTFKaMPdCvh5cSgKthdMKfuLUFdAsdKRG/qrf778mHbGKx1oM JdP7NDooM9cF+vlX4ocQhCZzijhdLu7WCstZPGdlurjAGOzUXAT9+PM+VyDQ/yLn7XKU JUs9Qc8l8hRORmCEbiZE95GETIGE6Hf8qA+5vhOc1I8dDA1Pql7cPAdbDLAAGX9bQxxL 2sZNHCTQ5+GH+3uFXbEbk3Eq9XSiLr1IqxtVJ8C1Te9gd1ohOh995lbEpfCCT0JaY/Vh MCd/PXmSbJ9x5ttmJvBQL0m9lFzG0wTZ+RmiHyiOKttgIRTniP9+VTSJADeZ2N9XEnMg +gRg==
X-Gm-Message-State: AOPr4FV7M72U0ySpXcWon7MRZC0wy89HBibDwjfqKUoPevBmOtJ3ITRT9ElNLNJKAoxUPeflB3+dt5lgBnNoPg==
X-Received: by 10.112.159.70 with SMTP id xa6mr6708140lbb.87.1460647323153; Thu, 14 Apr 2016 08:22:03 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.25.213.19 with HTTP; Thu, 14 Apr 2016 08:21:23 -0700 (PDT)
X-Originating-IP: [71.233.41.235]
In-Reply-To: <87shyol1jf.fsf@tops.chopps.org>
References: <CAMm+Lwg-HTYCv2pGt=SP2+Xjoko6GcJ73kVzqXC1LBTOMDKV_A@mail.gmail.com> <87shyol1jf.fsf@tops.chopps.org>
From: Ted Lemon <mellon@fugue.com>
Date: Thu, 14 Apr 2016 11:21:23 -0400
Message-ID: <CAPt1N1mRR+1iq9ueu=76WMd0K891ELvA-_YU1yar96kdcRa4CA@mail.gmail.com>
Subject: Re: Time to kill layer 2
To: chopps@chopps.org
Content-Type: multipart/alternative; boundary=001a11c28608d6cf5f05307374b4
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/HETe8WB7TrVv578MRmgx7oguu5k>
Cc: Phillip Hallam-Baker <phill@hallambaker.com>, IETF Discussion Mailing List <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, 14 Apr 2016 15:22:23 -0000

--001a11c28608d6cf5f05307374b4
Content-Type: text/plain; charset=UTF-8

This problem is solved in a multicast way with mDNS and DNSSD.   DNSSD is
working on a way to make this work better in a multiple-subnet environment.
  I'm hoping to produce a solution for homenet that allows devices to
register using unicast rather than multicast and does a better job of
actually tracking what services are connected to the network.   You can see
a bit of this in the -00 of the homenet naming architecture document.

On Thu, Apr 14, 2016 at 10:15 AM, <chopps@chopps.org> wrote:

>
> Phillip Hallam-Baker <phill@hallambaker.com> writes:
>
> > This morning I spent an hour debugging the network to print out two
> > class projects that were due. Some points:
> >
> > 1) My ability to debug the network is better than 99% of the population
> > 2) The interaction of Bonjour, DHCP and auto power saving is unfortunate
> > 3) Things should still work after I have been away for a week
> > 4) If vendors want to be selling all that IoT gear, they have to solve
> > these issues.
> >
> > 5) I want someone to blame. Right now when the network doesn't work, I
> > don't know who is the cause. I want one point of contact. Whoever is
> > that point of contact will get most of my networking money.
>
> ...
>
> > One of the reasons that IP won against OSI was that it was simpler.
> > Applications ran on top of the IP layer with only TCP inbetween. Of
> > course these days we do have a Presentation layer, Web Services run on
> > HTTP. But unlike the OSI presentation layer, ours does not introduce
> > extra moving parts.
>
> The funny thing about mentioning OSI here is that it would probably be
> very easy indeed to triage your network issue if your hosts were running
> ES-IS, and your routers IS-IS. You could plug into IS-IS and see
> everything. :)
>
> Thanks,
> Chris.
>

--001a11c28608d6cf5f05307374b4
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">This problem is solved in a multicast way with mDNS and DN=
SSD. =C2=A0 DNSSD is working on a way to make this work better in a multipl=
e-subnet environment. =C2=A0 I&#39;m hoping to produce a solution for homen=
et that allows devices to register using unicast rather than multicast and =
does a better job of actually tracking what services are connected to the n=
etwork. =C2=A0 You can see a bit of this in the -00 of the homenet naming a=
rchitecture document.</div><div class=3D"gmail_extra"><br><div class=3D"gma=
il_quote">On Thu, Apr 14, 2016 at 10:15 AM,  <span dir=3D"ltr">&lt;<a href=
=3D"mailto:chopps@chopps.org" target=3D"_blank">chopps@chopps.org</a>&gt;</=
span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8e=
x;border-left:1px #ccc solid;padding-left:1ex"><span class=3D""><br>
Phillip Hallam-Baker &lt;<a href=3D"mailto:phill@hallambaker.com">phill@hal=
lambaker.com</a>&gt; writes:<br>
<br>
&gt; This morning I spent an hour debugging the network to print out two<br=
>
&gt; class projects that were due. Some points:<br>
&gt;<br>
&gt; 1) My ability to debug the network is better than 99% of the populatio=
n<br>
&gt; 2) The interaction of Bonjour, DHCP and auto power saving is unfortuna=
te<br>
&gt; 3) Things should still work after I have been away for a week<br>
&gt; 4) If vendors want to be selling all that IoT gear, they have to solve=
<br>
&gt; these issues.<br>
&gt;<br>
&gt; 5) I want someone to blame. Right now when the network doesn&#39;t wor=
k, I<br>
&gt; don&#39;t know who is the cause. I want one point of contact. Whoever =
is<br>
&gt; that point of contact will get most of my networking money.<br>
<br>
</span>...<br>
<span class=3D""><br>
&gt; One of the reasons that IP won against OSI was that it was simpler.<br=
>
&gt; Applications ran on top of the IP layer with only TCP inbetween. Of<br=
>
&gt; course these days we do have a Presentation layer, Web Services run on=
<br>
&gt; HTTP. But unlike the OSI presentation layer, ours does not introduce<b=
r>
&gt; extra moving parts.<br>
<br>
</span>The funny thing about mentioning OSI here is that it would probably =
be<br>
very easy indeed to triage your network issue if your hosts were running<br=
>
ES-IS, and your routers IS-IS. You could plug into IS-IS and see<br>
everything. :)<br>
<br>
Thanks,<br>
Chris.<br>
</blockquote></div><br></div>

--001a11c28608d6cf5f05307374b4--


From nobody Thu Apr 14 09:32:41 2016
Return-Path: <hallam@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 AD74312E4FE for <ietf@ietfa.amsl.com>; Thu, 14 Apr 2016 09:32:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.4
X-Spam-Level: 
X-Spam-Status: No, score=-2.4 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.199, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 QSo3VuQ4TmzC for <ietf@ietfa.amsl.com>; Thu, 14 Apr 2016 09:32:36 -0700 (PDT)
Received: from mail-lf0-x22f.google.com (mail-lf0-x22f.google.com [IPv6:2a00:1450:4010:c07::22f]) (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 2EEBB12E4EF for <ietf@ietf.org>; Thu, 14 Apr 2016 09:32:36 -0700 (PDT)
Received: by mail-lf0-x22f.google.com with SMTP id g184so115432411lfb.3 for <ietf@ietf.org>; Thu, 14 Apr 2016 09:32:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc; bh=mt7JI62JzPEW3I2F+mLdBJlVMhBUoMwCEEVNqEdkRI8=; b=F3cmU/GIqt7s7r0OsYuZ4pj2hR1qqIyzFOMd/EMl/ocVEMv1q/mz/aE3GE+TGK9+zB wcUNXOR3WaXJcRd13kyJORk5t/f2Q5mRe/7mCw2yWig6UbQu37jQssWuMjdliylLX+1h 9fO824MoMmsGMmgIr4iZRvkwO4nfSi/ClKsCgyrY7EIuKCVYHy9R5uaipi2yj1S6adoj 7cojBiopiRN22cUAaZIYGdWHRgTDKknSty79wDcx88Ij6Wt4ESYVHKdFQRvRxhxwBWVq C3M7pApUmSvSQgaMhRqv0FQu562t+7RGamUMoqjpaGcfDwJTHSgYLw2bAho11hae2NvL A9dA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:date :message-id:subject:from:to:cc; bh=mt7JI62JzPEW3I2F+mLdBJlVMhBUoMwCEEVNqEdkRI8=; b=BFEbNRjWES06+f84sHnsIOB+fm/H1AEo4LE5bCdN4xBQFIFmJUSeAOXu2EMSdZmn6d PQ1wmXdPyJsQVNKcRyg0O28dcmCuDXUI6HzvD50kRh691JLFMLnkXA8OqyBE08b0+CmN F8U7t+Yx0w0DaQ8TutTN+86lsJ9Lioggse46mbUjqEztjs2XmolR+ZDl9SzOorp4UNzY WB2U/wbrVCN7Nc5LM+qejTV/4UuCPpzDaWQA6cMFgnCwpU7oH+xBEl5C4ID6umhXs4bs 5eD2YbqiV7kX7eCrx/AxWXQZ6//l9sJaBCSLpRRBiBVTG28cPUYn0CQB8swdIIHgOFa+ RViA==
X-Gm-Message-State: AOPr4FUY/4iTGetGySyc4akq+o+4/z+5aU/Xm2eDanKG1HFK5qo1EBIADEWBKuYIN6HKvdYinXr75oOUmBJivQ==
MIME-Version: 1.0
X-Received: by 10.112.51.8 with SMTP id g8mr5661080lbo.109.1460651554386; Thu, 14 Apr 2016 09:32:34 -0700 (PDT)
Sender: hallam@gmail.com
Received: by 10.112.151.67 with HTTP; Thu, 14 Apr 2016 09:32:34 -0700 (PDT)
In-Reply-To: <CAPt1N1mRR+1iq9ueu=76WMd0K891ELvA-_YU1yar96kdcRa4CA@mail.gmail.com>
References: <CAMm+Lwg-HTYCv2pGt=SP2+Xjoko6GcJ73kVzqXC1LBTOMDKV_A@mail.gmail.com> <87shyol1jf.fsf@tops.chopps.org> <CAPt1N1mRR+1iq9ueu=76WMd0K891ELvA-_YU1yar96kdcRa4CA@mail.gmail.com>
Date: Thu, 14 Apr 2016 12:32:34 -0400
X-Google-Sender-Auth: NDWZ_U0C_m41KeBBaUyq6Pga77A
Message-ID: <CAMm+LwhXY=nmMj+V7chRZZjpFY-ZAOaC0fqpfz83=LM-hsMCOQ@mail.gmail.com>
Subject: Re: Time to kill layer 2
From: Phillip Hallam-Baker <phill@hallambaker.com>
To: Ted Lemon <mellon@fugue.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/rhg1deDCAxiqpQQvTW6SeTlEw3E>
Cc: IETF Discussion Mailing List <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, 14 Apr 2016 16:32:41 -0000

On Thu, Apr 14, 2016 at 11:21 AM, Ted Lemon <mellon@fugue.com> wrote:
> This problem is solved in a multicast way with mDNS and DNSSD.

No, the problem is 'addressed'. If it was solved, it would work.

The problem is that it isn't working and I can't identify a single
point of failure. Whenever that happens, it is the standard at fault.


> DNSSD is
> working on a way to make this work better in a multiple-subnet environment.
> I'm hoping to produce a solution for homenet that allows devices to register
> using unicast rather than multicast and does a better job of actually
> tracking what services are connected to the network.   You can see a bit of
> this in the -00 of the homenet naming architecture document.

Going to unicast should help. Multicast configuration really doesn't
work on a network with as many hubs and devices as mine has.


From nobody Thu Apr 14 09:43:02 2016
Return-Path: <alissa@cooperw.in>
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 7DA4D12E69B for <ietf@ietfa.amsl.com>; Thu, 14 Apr 2016 09:42:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.721
X-Spam-Level: 
X-Spam-Status: No, score=-2.721 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cooperw.in header.b=IVc3gMzS; dkim=pass (1024-bit key) header.d=messagingengine.com header.b=ibVuimsW
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 7JAVjFVMmjnL for <ietf@ietfa.amsl.com>; Thu, 14 Apr 2016 09:42:57 -0700 (PDT)
Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ACB6812E694 for <ietf@ietf.org>; Thu, 14 Apr 2016 09:42:57 -0700 (PDT)
Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.nyi.internal (Postfix) with ESMTP id 1C9CA207D8 for <ietf@ietf.org>; Thu, 14 Apr 2016 12:42:56 -0400 (EDT)
Received: from frontend2 ([10.202.2.161]) by compute2.internal (MEProxy); Thu, 14 Apr 2016 12:42:56 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=cooperw.in; h=cc :content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-sasl-enc :x-sasl-enc; s=mesmtp; bh=E2LZIwx15zIqIFljbZrXGmaVUP8=; b=IVc3gM zSJ2Q2ps+7QUIRJpRc9QbCUdWUwSY5RfbmyWWrouiiXwJz2bJ5Ox+MJ/IyXz+mdj lY2a0O706JCbDOl1c3TC9FXvkAQDsFmmYbebl9T8wAAti1sXnxBOaeKIjgz8bNZP ALDKFLOjN1k36lryI2B0ALBPVOwvWwi63bUwk=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-sasl-enc:x-sasl-enc; s=smtpout; bh=E2LZIwx15zIqIFl jbZrXGmaVUP8=; b=ibVuimsWYLRJuujarUGc427p/hD8e/hkoyF3KlXpVKmUEfy mD+n+JbI4GMDHgoTAGULGIQSKvS5W4Z5tAVZ6pdd9itRlsp6CKmjOWbyzbqsPY3H okmPgZCa8UNW399OjdmMh58Iv0GFJ0JwpPQqngO66ds5BHUdn4ePNkMdkiYw=
X-Sasl-enc: iJiRfKg+XljPM1R/Qxq2W3Kdx0wSYyPVkj2p8RopES2h 1460652175
Received: from dhcp-171-68-21-99.cisco.com (dhcp-171-68-21-99.cisco.com [171.68.21.99]) by mail.messagingengine.com (Postfix) with ESMTPA id 91BAB680250; Thu, 14 Apr 2016 12:42:55 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 9.2 \(3112\))
Subject: Re: [rtcweb] Last call redux: draft-ietf-rtcweb-rtp-usage-26
From: Alissa Cooper <alissa@cooperw.in>
In-Reply-To: <4F3B615A-A77A-434E-B3A9-DDABE8994373@cooperw.in>
Date: Thu, 14 Apr 2016 09:42:54 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <D38D1C32-F465-47EB-8FBC-69B294AAB324@cooperw.in>
References: <4F3B615A-A77A-434E-B3A9-DDABE8994373@cooperw.in>
To: ietf@ietf.org
X-Mailer: Apple Mail (2.3112)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/xClzvP0-KJDSx_QRpr9sAXrPJ2k>
Cc: rtcweb@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, 14 Apr 2016 16:43:00 -0000

No comments were received, so this document will revert to the RFC =
Editor.

> On Mar 23, 2016, at 1:44 PM, Alissa Cooper <alissa@cooperw.in> wrote:
>=20
> draft-ietf-rtcweb-rtp-usage-25 was approved for publication in July =
2015 and is in the RFC Editor's queue. Subsequently, the RTCWEB WG =
identified a change that needed to be made in Section 4.5 related to =
multiplexing RTP and RTCP. The change is reflected in =
draft-ietf-rtcweb-rtp-usage-26 and copied below.
>=20
> The IESG will not revisit its decision to approve this document for =
publication unless it receives feedback from the community indicating a =
need to do so. Please send substantive comments to the ietf@ietf.org =
mailing list by 2016-04-13. Exceptionally, comments may be sent to =
iesg@ietf.org instead.
>=20
> The change is:
>=20
> OLD:
>=20
> If SDP is used for signalling, this
> negotiation MUST use the attributes defined in [RFC5761].  For
> backwards compatibility, implementations are also REQUIRED to support
> RTP and RTCP sent on separate transport-layer flows.
>=20
> NEW:
>=20
> If SDP is used for signalling, this
> negotiation MUST use the mechanism defined in [RFC5761].
> Implementations can also support sending RTP and RTCP on separate
> transport-layer flows, but this is OPTIONAL to implement.  If an
> implementation does not support RTP and RTCP sent on separate
> transport-layer flows, it MUST indicate that using the mechanism
> defined in [I-D.ietf-mmusic-mux-exclusive].
>=20
> The document is available at =
https://datatracker.ietf.org/doc/draft-ietf-rtcweb-rtp-usage/
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb


From nobody Thu Apr 14 09:54:06 2016
Return-Path: <christopher.morrow@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 4AE8912D626 for <ietf@ietfa.amsl.com>; Thu, 14 Apr 2016 09:54:03 -0700 (PDT)
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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 IX0dFkUQyAGp for <ietf@ietfa.amsl.com>; Thu, 14 Apr 2016 09:54:02 -0700 (PDT)
Received: from mail-yw0-x231.google.com (mail-yw0-x231.google.com [IPv6:2607:f8b0:4002: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 D465B12D7BE for <ietf@ietf.org>; Thu, 14 Apr 2016 09:54:01 -0700 (PDT)
Received: by mail-yw0-x231.google.com with SMTP id i84so110035647ywc.2 for <ietf@ietf.org>; Thu, 14 Apr 2016 09:54:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc; bh=fDwaBS8Vkze19F0XlRkmERsYawPGptvtx5UJGWphdKo=; b=SF0r9+DWI4qMLJEgupkVwDHEbBEAxsnjk8qjzMfJG81ZsrhWrw5S9g03dcrKQ0LQU6 LkNCIK0M05a4b68bNrd1xYNDq/WXCHGZ7LoopgoR2a396UuIwZXS4sOKAGAUK53DE93/ 9BHRIBekLGOWZKqwMsCxhrMxHuyAXZ0Up3S/x3M6VKOnlcjjv/plJSiyU2M4NswShYup MGaXq+WbgQQw4iWZ0em6uS3HPU7u5U93IThv69RiS9zG0hx256Wfw11JRehTlnXbBMXi 7ybFAlFPZ8nqVEvgW53Ema5R8CKnlvKgRkkJTgxIyzbxCKeWPGTON5WSB80zr2uHRBJp sFgw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:date :message-id:subject:from:to:cc; bh=fDwaBS8Vkze19F0XlRkmERsYawPGptvtx5UJGWphdKo=; b=DhAG8bUzzOUwAKlzgX9gGRR5rC18TFRw5kalatXdTjFJtUF8ubCrSkY8gYV2J32GYA T/WV1e1ySqx196aXzkq9bhNADM3RBEC4mXp9FHBVHchIvEkNn/QeEP9VNWuAOAoNvKY5 n4XqaorgH4sF1TGd96HbK3BIQRm/K1li+GZ401oa+XQdnOr2koDrlICDI2RgJ3unngw8 8p7ZUj5lbXrkd6YbBCSZ37xVQAWfqlkfVTSEYsJD+RltXQb1iugtrl3wGxKRSUzv4olU DBKpu49QRYxy4ainKojKwE38QO8UOIURmTq26/00o2bdjr3mJDj2rmJFmdG7AJKlkmXm wG+A==
X-Gm-Message-State: AOPr4FWZIJ0x3n4BljZ/3ccFhahZ3dfMo7u9EgCWtcc86HZ1PTDo5QH0NhKr5zjVbH4XaX9Za8xrwomydRtthA==
MIME-Version: 1.0
X-Received: by 10.37.108.7 with SMTP id h7mr5720998ybc.102.1460652841094; Thu, 14 Apr 2016 09:54:01 -0700 (PDT)
Sender: christopher.morrow@gmail.com
Received: by 10.13.209.198 with HTTP; Thu, 14 Apr 2016 09:54:01 -0700 (PDT)
In-Reply-To: <CAMm+LwhXY=nmMj+V7chRZZjpFY-ZAOaC0fqpfz83=LM-hsMCOQ@mail.gmail.com>
References: <CAMm+Lwg-HTYCv2pGt=SP2+Xjoko6GcJ73kVzqXC1LBTOMDKV_A@mail.gmail.com> <87shyol1jf.fsf@tops.chopps.org> <CAPt1N1mRR+1iq9ueu=76WMd0K891ELvA-_YU1yar96kdcRa4CA@mail.gmail.com> <CAMm+LwhXY=nmMj+V7chRZZjpFY-ZAOaC0fqpfz83=LM-hsMCOQ@mail.gmail.com>
Date: Thu, 14 Apr 2016 12:54:01 -0400
X-Google-Sender-Auth: lq6J8p9dLwKA28u6LXJquyAgD1g
Message-ID: <CAL9jLab9+gfiyNy6KY3gq+0wq5jCp14NpHMK+ZeN1An=SaqvSg@mail.gmail.com>
Subject: Re: Time to kill layer 2
From: Christopher Morrow <morrowc.lists@gmail.com>
To: Phillip Hallam-Baker <phill@hallambaker.com>
Content-Type: multipart/alternative; boundary=001a1148b6eebbd4a5053074bdea
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/NKPXJBeZjlYrMFb8647_GnY5eBs>
Cc: IETF Discussion Mailing List <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, 14 Apr 2016 16:54:03 -0000

--001a1148b6eebbd4a5053074bdea
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Thu, Apr 14, 2016 at 12:32 PM, Phillip Hallam-Baker <
phill@hallambaker.com> wrote:

> Going to unicast should help. Multicast configuration really doesn't
> work on a network with as many hubs and devices as mine has.
>

=E2=80=8Bmulticast would work, if all the hubs/devices did multicast proper=
ly,
right? :)
it's not clear that unicast works, if the problem you are trying to solve
is service-discovery... absent some registry of 'services' for your clients
to use, of course (which is the point of the mdns thingy).=E2=80=8B

--001a1148b6eebbd4a5053074bdea
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">=
On Thu, Apr 14, 2016 at 12:32 PM, Phillip Hallam-Baker <span dir=3D"ltr">&l=
t;<a href=3D"mailto:phill@hallambaker.com" target=3D"_blank">phill@hallamba=
ker.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D=
"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div id=3D"=
:2tp" class=3D"a3s aXjCH">Going to unicast should help. Multicast configura=
tion really doesn&#39;t<br>
work on a network with as many hubs and devices as mine has.</div></blockqu=
ote></div><br><div class=3D"gmail_default" style=3D"font-size:small">=E2=80=
=8Bmulticast would work, if all the hubs/devices did multicast properly, ri=
ght? :)</div><div class=3D"gmail_default" style=3D"font-size:small">it&#39;=
s not clear that unicast works, if the problem you are trying to solve is s=
ervice-discovery... absent some registry of &#39;services&#39; for your cli=
ents to use, of course (which is the point of the mdns thingy).=E2=80=8B</d=
iv><br></div></div>

--001a1148b6eebbd4a5053074bdea--


From nobody Thu Apr 14 09:54:46 2016
Return-Path: <charles.perkins@earthlink.net>
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 B8FD612D93D for <ietf@ietfa.amsl.com>; Thu, 14 Apr 2016 09:54:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.716
X-Spam-Level: 
X-Spam-Status: No, score=-3.716 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.996] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); domainkeys=pass (384-bit key) header.from=charles.perkins@earthlink.net header.d=earthlink.net
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 077pH-LiNNLl for <ietf@ietfa.amsl.com>; Thu, 14 Apr 2016 09:54:34 -0700 (PDT)
Received: from elasmtp-kukur.atl.sa.earthlink.net (elasmtp-kukur.atl.sa.earthlink.net [209.86.89.65]) by ietfa.amsl.com (Postfix) with ESMTP id E1A0912D74B for <ietf@ietf.org>; Thu, 14 Apr 2016 09:54:33 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=DrUodT7qenW4NtcpLgHJ+fV/+osbIX7571llUPgLk/oVX8YCkP87klc2tv353QQJ; h=Received:Subject:To:References:Cc:From:Message-ID:Date:User-Agent:MIME-Version:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP;
Received: from [99.51.72.196] (helo=[192.168.1.67]) by elasmtp-kukur.atl.sa.earthlink.net with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.67) (envelope-from <charles.perkins@earthlink.net>) id 1aqkX2-0005uY-6O; Thu, 14 Apr 2016 12:54:16 -0400
Subject: Re: Time to kill layer 2
To: Phillip Hallam-Baker <phill@hallambaker.com>
References: <CAMm+Lwg-HTYCv2pGt=SP2+Xjoko6GcJ73kVzqXC1LBTOMDKV_A@mail.gmail.com> <87shyol1jf.fsf@tops.chopps.org> <CAPt1N1mRR+1iq9ueu=76WMd0K891ELvA-_YU1yar96kdcRa4CA@mail.gmail.com> <CAMm+LwhXY=nmMj+V7chRZZjpFY-ZAOaC0fqpfz83=LM-hsMCOQ@mail.gmail.com>
From: Charlie Perkins <charles.perkins@earthlink.net>
Message-ID: <570FCB34.2080701@earthlink.net>
Date: Thu, 14 Apr 2016 09:54:12 -0700
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2
MIME-Version: 1.0
In-Reply-To: <CAMm+LwhXY=nmMj+V7chRZZjpFY-ZAOaC0fqpfz83=LM-hsMCOQ@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
X-ELNK-Trace: 137d7d78656ed6919973fd6a8f21c4f2d780f4a490ca6956527bd5036cbc8ac7631eadfac5a9e6844f7321e82bce7285350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 99.51.72.196
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/stH8Dq697xT_RmA6BRAWNxmAUg8>
Cc: IETF Discussion Mailing List <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, 14 Apr 2016 16:54:42 -0000

Hello Phillip,

Layer 2 isn't just one thing.  Do you specifically mean to eliminate 
layer-2 addresses, or something more?

Regards,
Charlie P.


On 4/14/2016 9:32 AM, Phillip Hallam-Baker wrote:
> On Thu, Apr 14, 2016 at 11:21 AM, Ted Lemon <mellon@fugue.com> wrote:
>> This problem is solved in a multicast way with mDNS and DNSSD.
> No, the problem is 'addressed'. If it was solved, it would work.
>
> The problem is that it isn't working and I can't identify a single
> point of failure. Whenever that happens, it is the standard at fault.
>
>
>> DNSSD is
>> working on a way to make this work better in a multiple-subnet environment.
>> I'm hoping to produce a solution for homenet that allows devices to register
>> using unicast rather than multicast and does a better job of actually
>> tracking what services are connected to the network.   You can see a bit of
>> this in the -00 of the homenet naming architecture document.
> Going to unicast should help. Multicast configuration really doesn't
> work on a network with as many hubs and devices as mine has.
>
>


From nobody Thu Apr 14 09:55:35 2016
Return-Path: <mellon@fugue.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 573B112DF5A for <ietf@ietfa.amsl.com>; Thu, 14 Apr 2016 09:55:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.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 MB-Jr8dqUVl0 for <ietf@ietfa.amsl.com>; Thu, 14 Apr 2016 09:55:29 -0700 (PDT)
Received: from mail-lf0-x22b.google.com (mail-lf0-x22b.google.com [IPv6:2a00:1450:4010:c07::22b]) (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 2D2D812DEDE for <ietf@ietf.org>; Thu, 14 Apr 2016 09:55:29 -0700 (PDT)
Received: by mail-lf0-x22b.google.com with SMTP id j11so116015059lfb.1 for <ietf@ietf.org>; Thu, 14 Apr 2016 09:55:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=pOKYqrcodpoFPjdKGzuOEFzUt/vj7TR+qt5LE8usBos=; b=XOdY65RryWNDtKOekFcGMMPJcrkUC+76QbPCTaQvrK3VuoNrAOLbhV9xFZok371hZl 0tun0EFdxshbth/dXXymhSyu7KNSk25j4fVCBS5WMuH+92ABluTiQ0XVBZgeUE6vyfnk OFCPUvCE7PUXRr4rhCMx22j+iVSWOYXNVV9FNO+SgQQ5edfstaz1+jaJl4DArYDhFd8y kOaY2YR0J6GmeKT6nzWJis47JlJ19vsENbYzUhMiF63lONd/syZ4RYH95Vh3H80KNWHS Ml+Sph/hpTVTl4PSnb8T2YRz3VwFShjwcghxkAKXSAvnPAjfbLBE7S1c8BJHQeatjVm9 74ew==
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=pOKYqrcodpoFPjdKGzuOEFzUt/vj7TR+qt5LE8usBos=; b=JLq+5cR0Fo5SXwHhc4/vNMcArezlG+Bs2tcbzhibTaclMeGuqsaxr0NJp2EspzQovN ob8V1A9KxKkSXgHx4vjEcWXjhc+CT1dVOdqHhdvNcgomoi2CAmpP9YEs7fcu5g35eQWX 1sajhQ0DbQHQitmIQ0REhu4zAn8G2K7LhsFhv3AInLwF1ZxpEDsAbDKmvA3BoBCkobv+ jhldIOKXrJto1sJOEjiboVYgzbqz1QSOvRxOMhFCfd5dRXq7PSTRZEK4rsq5iW738gau PSE1fUfDY/WDkzF+ej9mXHIUcXqa8pVeQnMjZrhjbgWHtr13mMdjZB/zDHTF0JZMe0/o cy0A==
X-Gm-Message-State: AOPr4FUoBfMO/KyftKsFFakAn4md7b6EBlIB8VLv3tGxE8Xc61jLvPkRpxNqesjTZyU1Tain/qqxPyVFoKFsCw==
X-Received: by 10.25.85.210 with SMTP id j201mr5982430lfb.132.1460652927341; Thu, 14 Apr 2016 09:55:27 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.25.213.19 with HTTP; Thu, 14 Apr 2016 09:54:47 -0700 (PDT)
X-Originating-IP: [71.233.41.235]
In-Reply-To: <CAL9jLab9+gfiyNy6KY3gq+0wq5jCp14NpHMK+ZeN1An=SaqvSg@mail.gmail.com>
References: <CAMm+Lwg-HTYCv2pGt=SP2+Xjoko6GcJ73kVzqXC1LBTOMDKV_A@mail.gmail.com> <87shyol1jf.fsf@tops.chopps.org> <CAPt1N1mRR+1iq9ueu=76WMd0K891ELvA-_YU1yar96kdcRa4CA@mail.gmail.com> <CAMm+LwhXY=nmMj+V7chRZZjpFY-ZAOaC0fqpfz83=LM-hsMCOQ@mail.gmail.com> <CAL9jLab9+gfiyNy6KY3gq+0wq5jCp14NpHMK+ZeN1An=SaqvSg@mail.gmail.com>
From: Ted Lemon <mellon@fugue.com>
Date: Thu, 14 Apr 2016 12:54:47 -0400
Message-ID: <CAPt1N1nD856T81DBhd3qDiiiS_=Q4UTR_+p_4Q9q7Q5GutaJeg@mail.gmail.com>
Subject: Re: Time to kill layer 2
To: Christopher Morrow <morrowc.lists@gmail.com>
Content-Type: multipart/alternative; boundary=001a1141d826dff05f053074c2d9
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/9HKtdV6aWBPSLG2gTeYAYXh4yec>
Cc: Phillip Hallam-Baker <phill@hallambaker.com>, IETF Discussion Mailing List <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, 14 Apr 2016 16:55:32 -0000

--001a1141d826dff05f053074c2d9
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

You should read the homenet naming and service discovery architecture
document. :)

On Thu, Apr 14, 2016 at 12:54 PM, Christopher Morrow <
morrowc.lists@gmail.com> wrote:

>
> On Thu, Apr 14, 2016 at 12:32 PM, Phillip Hallam-Baker <
> phill@hallambaker.com> wrote:
>
>> Going to unicast should help. Multicast configuration really doesn't
>> work on a network with as many hubs and devices as mine has.
>>
>
> =E2=80=8Bmulticast would work, if all the hubs/devices did multicast prop=
erly,
> right? :)
> it's not clear that unicast works, if the problem you are trying to solve
> is service-discovery... absent some registry of 'services' for your clien=
ts
> to use, of course (which is the point of the mdns thingy).=E2=80=8B
>
>

--001a1141d826dff05f053074c2d9
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">You should read the homenet naming and service discovery a=
rchitecture document. :)</div><div class=3D"gmail_extra"><br><div class=3D"=
gmail_quote">On Thu, Apr 14, 2016 at 12:54 PM, Christopher Morrow <span dir=
=3D"ltr">&lt;<a href=3D"mailto:morrowc.lists@gmail.com" target=3D"_blank">m=
orrowc.lists@gmail.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_=
quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1=
ex"><div dir=3D"ltr"><div class=3D"gmail_extra"><span class=3D""><br><div c=
lass=3D"gmail_quote">On Thu, Apr 14, 2016 at 12:32 PM, Phillip Hallam-Baker=
 <span dir=3D"ltr">&lt;<a href=3D"mailto:phill@hallambaker.com" target=3D"_=
blank">phill@hallambaker.com</a>&gt;</span> wrote:<br><blockquote class=3D"=
gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-=
left:1ex"><div>Going to unicast should help. Multicast configuration really=
 doesn&#39;t<br>
work on a network with as many hubs and devices as mine has.</div></blockqu=
ote></div><br></span><div class=3D"gmail_default" style=3D"font-size:small"=
>=E2=80=8Bmulticast would work, if all the hubs/devices did multicast prope=
rly, right? :)</div><div class=3D"gmail_default" style=3D"font-size:small">=
it&#39;s not clear that unicast works, if the problem you are trying to sol=
ve is service-discovery... absent some registry of &#39;services&#39; for y=
our clients to use, of course (which is the point of the mdns thingy).=E2=
=80=8B</div><br></div></div>
</blockquote></div><br></div>

--001a1141d826dff05f053074c2d9--


From nobody Thu Apr 14 12:42:55 2016
Return-Path: <nalini.elkins@insidethestack.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 56B3F12DA0F for <ietf@ietfa.amsl.com>; Thu, 14 Apr 2016 12:42:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.196
X-Spam-Level: 
X-Spam-Status: No, score=-2.196 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, URIBL_GREY=0.424] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=yahoo.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 i3eq1egKYDgQ for <ietf@ietfa.amsl.com>; Thu, 14 Apr 2016 12:42:51 -0700 (PDT)
Received: from nm15-vm2.bullet.mail.ne1.yahoo.com (nm15-vm2.bullet.mail.ne1.yahoo.com [98.138.91.91]) (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 49D4C12DA6F for <ietf@ietf.org>; Thu, 14 Apr 2016 12:42:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1460662983; bh=1wwQpEzeET9fqXdeH9T+TDxTmd7wPIRO8VcUgpcPrqs=; h=Date:From:Reply-To:To:Cc:Subject:References:From:Subject; b=GXu0dzb8p9lZN6mB009gReCwuQ+mOQz1OIvV9APhuA7pJU/FaUR91ig7FIHqxR3GtiAGybKw8xXjzVAbqTM1g3zfAa2uS+4JnuDfKYpjy9dgSfMSCfwxIcaO/ZCo129gl2mbMQhMoCTUTSkOeYw10a3DaqWUaor3W92Ui4WreYGABdRMrrKhqK0o2tX9Zfg8G/ohqttcmEMRxpu5JIYWxsS8Rdqyl6H0ojaTqRyK7JG8OxTBKokYeWZ4RsJjnaxh3J/2I4SD1UY79ySQckJUBAX/HMO8TNx3qIS3NcIq4ejVNoTC5TPJyDf2yMfKgqyIyEtT6a1ZRVIZtK0fh2YEsg==
Received: from [98.138.226.176] by nm15.bullet.mail.ne1.yahoo.com with NNFMP;  14 Apr 2016 19:43:03 -0000
Received: from [98.138.89.167] by tm11.bullet.mail.ne1.yahoo.com with NNFMP; 14 Apr 2016 19:42:50 -0000
Received: from [127.0.0.1] by omp1023.mail.ne1.yahoo.com with NNFMP; 14 Apr 2016 19:42:50 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 329367.83038.bm@omp1023.mail.ne1.yahoo.com
X-YMail-OSG: w2z3VQwVM1lXX3bWcosksjdozYG1pdEv3Pw1ciYvMKiAhEO8uq5NRGyTgCdSV2y BoWAPG0q8ki0SeR04ThooWZAsdfxn.xyWIfz1nmzaG1VSLuhSSB.glYMJUF5ySV6bVYQOCgVXZJW uFNFZz1oVNkBo5YDefe0284nVPpiNiKrsGf_pa73LT_0jYrEnL_byh_o2b_XFzsf_ikBMiS1Wl3I z4RUU_gXViwAmimapAL63y_8ldxFMC1cXJtqeGCIQjI4n.ZSj9PXEKX0vsNUxvBVKkFxDgBfxFKr BeipfSfrnGBj4gbUjUI2Tb6MuF2YgN7R.jtA7NoTg1an7P7Gx._Vkwrcj7Uq9.ay1YTlyhj8Ol_H cTXSAu9Qp.rgomuRP84HZjTrh71t3w_QEDZQ5DCr11woC9.O1WgTDhx.doYtpOO9aVug6M7nf4Kb 9zvnZSa9_.PnXLeILF7sniiLSmevWfTiueS1x5sSlrHqm9voJ4w7O1Kr9nOEmi7XwkUrJCdlXOdw kvDwXAqw71tOTtB8bSXVCxjKLEodkbXThjCR5_E83zdKxJGXqG.5Rr.uQMZL7T4LtC0nvDA--
Received: by 98.138.105.217; Thu, 14 Apr 2016 19:42:49 +0000 
Date: Thu, 14 Apr 2016 19:42:49 +0000 (UTC)
From: <nalini.elkins@insidethestack.com>
To: IETF Discussion List <ietf@ietf.org>, Vmeet <vmeet@ietf.org>,  "95-1st-timers@ietf.org" <95-1st-timers@ietf.org>,  "95-mentees@ietf.org" <95-mentees@ietf.org>
Message-ID: <181005448.601818.1460662969585.JavaMail.yahoo@mail.yahoo.com>
Subject: Remote Mentoring: Internet Draft Review Teams
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
References: <181005448.601818.1460662969585.JavaMail.yahoo.ref@mail.yahoo.com>
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/mNn00N4eNWQYqL68mecVy3wTFI4>
Cc: "mentoring-coordinators@ietf.org" <mentoring-coordinators@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: nalini.elkins@insidethestack.com
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, 14 Apr 2016 19:42:52 -0000

All,

The IETF Mentoring Team is starting a new initiative to form teams to review Internet Drafts together.  You may sign up at: 

https://www.surveymonkey.com/r/Z8KD8GB

The purpose of Internet Draft review teams is to provide a way for people to get started posting to the email list for an IETF Working Group or reading Internet Drafts together. Sometimes people (especially when new) are not comfortable with the process of posting to the Working Group email list or want to check with others about their understanding of an Internet Draft before asking a question or posting a suggestion.

So, you may fill out this form if you want to be a member of such a team.  Once we get 4 or 5 members who wish to participate in such a team, we will email everyone to form the group and start working together.   You may meet once or many times.  It is up to you.  Your first task will be to select together the Internet Draft that you want to review.   We also ask the language that you prefer to speak so that we can put you into groups based on language preference.

You may also request a remote mentor to help you with selection of the draft or in your discussions.   The result of your discussions should be comments to the email list of the Working Group.

Again, sign ups are at:

https://www.surveymonkey.com/r/Z8KD8GB

Please let me know any comments & please forward this to any people you think may be interested.
Thanks,

Nalini Elkins

IETF Mentoring Team

Inside Products, Inc.
www.insidethestack.com
(831) 659-8360


From nobody Thu Apr 14 13:23:52 2016
Return-Path: <brian.e.carpenter@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 4807412D948 for <ietf@ietfa.amsl.com>; Thu, 14 Apr 2016 13:23:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 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, RCVD_IN_DNSWL_LOW=-0.7, 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 1-Km7edZyvtL for <ietf@ietfa.amsl.com>; Thu, 14 Apr 2016 13:23:46 -0700 (PDT)
Received: from mail-pf0-x229.google.com (mail-pf0-x229.google.com [IPv6:2607:f8b0:400e:c00::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 2FC1F12DABE for <ietf@ietf.org>; Thu, 14 Apr 2016 13:23:43 -0700 (PDT)
Received: by mail-pf0-x229.google.com with SMTP id 184so49343048pff.0 for <ietf@ietf.org>; Thu, 14 Apr 2016 13:23:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=subject:to:references:from:organization:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=dwoYZGNsPDv3B4f/i2KLR7DpLa2IcEAjV7y+d3mcmaw=; b=KREilRDSHtcFj18dMyGcddxQdZv5MzxlusITCfmP9gDYXbF0o4wTDpiF7gDVUXjA/k /W/zvAOErNt8dEWYoa9BDuOeJHA5p3/IV8BZj0l1UJhLydyKsZARr7pPzhKQNSnrz/8d 4Vn3hmuJQ/xMb1Pj1sXsWZ4xELplVaVVLGvfGnzr7HNENUdxzVk65+gEbmqN8wOMXsPK NJir9raT34JDoc0ahK4nF9CHKtc3BTtYehiDNiwnMHwGBUYbLk4EiXnhtiu5G0npXZoT 06McFFFDwClkZYnF0G1yIfGgYYc9IvsF+vQqXJ6keiGXXKkN9pfQFdYl7WzxETy58yzs dkhw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=dwoYZGNsPDv3B4f/i2KLR7DpLa2IcEAjV7y+d3mcmaw=; b=JP9iOV4T9gooO9rnb3aHxjhSlrLsPO5TEuHtnXQAcnIS/HcA/+rS1r1FsEsJiy7HTW xuv9VsibC7ISnSn7OWcHIaLytSBnnDmSGP+Y4zkb/rDOkPIEq4FrIT2uZL813g6Y4vIX 3nlV3bttlTqqIcuDd4DcIQO8XyrN5YqfFdjaZnzp2IFUXupaiQDPNDRv9ThpH2VluoPb kMlKCYhYtxYPPx+Qlbuv7s4I0OKT1wg5NZWGIGljWrfR91dPcgKwg71P0u7wolNywAfv LSYBF7Uk9kh/Cft0M5OUmW2Dvmsajf74c/QCskWl5ZVt1qjw6EhQjphyD8J+3ezCfN/c 8IhQ==
X-Gm-Message-State: AOPr4FX3ZKSZS/vLhkrDpO4RMMo1xDPRaj88NWZtjy/OAVF/uoC+o3mkr/Ppw2zUlr0IFg==
X-Received: by 10.98.18.212 with SMTP id 81mr24249675pfs.104.1460665422663; Thu, 14 Apr 2016 13:23:42 -0700 (PDT)
Received: from ?IPv6:2406:e007:4759:1:28cc:dc4c:9703:6781? ([2406:e007:4759:1:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id i7sm15711251pfc.47.2016.04.14.13.23.39 for <ietf@ietf.org> (version=TLSv1/SSLv3 cipher=OTHER); Thu, 14 Apr 2016 13:23:41 -0700 (PDT)
Subject: Re: Time to kill layer 2
To: ietf@ietf.org
References: <CAMm+Lwg-HTYCv2pGt=SP2+Xjoko6GcJ73kVzqXC1LBTOMDKV_A@mail.gmail.com> <87shyol1jf.fsf@tops.chopps.org> <CAPt1N1mRR+1iq9ueu=76WMd0K891ELvA-_YU1yar96kdcRa4CA@mail.gmail.com> <CAMm+LwhXY=nmMj+V7chRZZjpFY-ZAOaC0fqpfz83=LM-hsMCOQ@mail.gmail.com> <CAL9jLab9+gfiyNy6KY3gq+0wq5jCp14NpHMK+ZeN1An=SaqvSg@mail.gmail.com> <CAPt1N1nD856T81DBhd3qDiiiS_=Q4UTR_+p_4Q9q7Q5GutaJeg@mail.gmail.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <570FFC54.7040602@gmail.com>
Date: Fri, 15 Apr 2016 08:23:48 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2
MIME-Version: 1.0
In-Reply-To: <CAPt1N1nD856T81DBhd3qDiiiS_=Q4UTR_+p_4Q9q7Q5GutaJeg@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/vOf76i6Whm5CKcy5J0B1vRH2AFs>
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, 14 Apr 2016 20:23:48 -0000

On 15/04/2016 04:54, Ted Lemon wrote:
> You should read the homenet naming and service discovery architecture
> document. :)
>=20
> On Thu, Apr 14, 2016 at 12:54 PM, Christopher Morrow <
> morrowc.lists@gmail.com> wrote:
>=20
>>
>> On Thu, Apr 14, 2016 at 12:32 PM, Phillip Hallam-Baker <
>> phill@hallambaker.com> wrote:
>>
>>> Going to unicast should help. Multicast configuration really doesn't
>>> work on a network with as many hubs and devices as mine has.
>>>
>>
>> =E2=80=8Bmulticast would work, if all the hubs/devices did multicast p=
roperly,
>> right? :)

Really stupid devices do multicast properly because they are genuinely
transparent to layer 2. The annoying devices are the ones that pretend
to be layer 2 + layer 3 devices but are actually half-baked layer violati=
on
devices. (To be specific, I have recently been burned by a layer 2/3 swit=
ch
that does not perform correct MLD snooping. And I agree that you have to =
be
in the 1% to diagnose that.)

>> it's not clear that unicast works, if the problem you are trying to so=
lve
>> is service-discovery... absent some registry of 'services' for your cl=
ients
>> to use, of course (which is the point of the mdns thingy).=E2=80=8B

It seems to me that doing everything unicast makes life harder for no
reason. I don't know how we could make the Anima signaling work without
multicast, but we are restricting it strictly to link-local multicast.

    Brian


From nobody Thu Apr 14 14:43:10 2016
Return-Path: <hallam@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 3E0C812E3FA for <ietf@ietfa.amsl.com>; Thu, 14 Apr 2016 14:43:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.4
X-Spam-Level: 
X-Spam-Status: No, score=-2.4 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.199, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 1cR1BUmT3HFC for <ietf@ietfa.amsl.com>; Thu, 14 Apr 2016 14:43:06 -0700 (PDT)
Received: from mail-lf0-x230.google.com (mail-lf0-x230.google.com [IPv6:2a00:1450:4010:c07::230]) (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 45EC212E3F6 for <ietf@ietf.org>; Thu, 14 Apr 2016 14:43:06 -0700 (PDT)
Received: by mail-lf0-x230.google.com with SMTP id c126so124737887lfb.2 for <ietf@ietf.org>; Thu, 14 Apr 2016 14:43:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc; bh=z+cKasXseGW0CbyN1GHuaPRDvRhmmM/Aflt0zq+WPa0=; b=Z/sYFajKONyqeEtN/pNjKWBhtQaJYNvq+ylP6le78bRSYbGYOoLMixVP9lydxmTvfu Jp0pcTO04rtA/UjAGqVuT1zN0FJ4Xf3Y6RWFx2+Ab3LLlpmfUr+FXg4TyRyehn8o9QoA G9OlFAOhIj3RGJfLTK0f4NoSNStH8ravsji/nIFlm/XrO2vL5NkAOND2od8sbQ0SlTkc RK0XOoTabZ4l5D7Z7Hd85Ii2Xf/lf4xJDD8Z1KWDhR7NONQA+7ZwRcZzl8dzvZRvH0wW wdGEQunE7TdVzSVMv3rew+Nls3xN+OKLXxZfNC9P9EPwFnTBDAWVDrMT/cPnyooSGpRK k1gA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:date :message-id:subject:from:to:cc; bh=z+cKasXseGW0CbyN1GHuaPRDvRhmmM/Aflt0zq+WPa0=; b=XbUAhhJF1EqtK/JX5WJE/j6q09rJawe8tL4akcY+q3tj1b9DZk58Yf8p2k3tvqnn57 66lE8n9yKSiIklN3Wn/jSTHppOy05YlOXhiwnR8UOYMPdf5uNJicr8sOM6Kh2jbiziE5 SD54avq9JetSlYhCHJe2BV89ZNX2uGRdIWAActjm37Y8/dtqZTkjJ+OoTudQK63/LJKE yDptZOCic6E6CHn+c0U7AIsVgCM11c6jCAONpGi23JpvF2KhRbTe00NoYEkjr6S5J2u5 rRnYNq7ddvL95otx8IIsrchg3ne8XF85JV7/2yLRHR9k5zWzrTACMdhePjv5/GFbv2EK uAJQ==
X-Gm-Message-State: AOPr4FVp2JOu0YwfOSYVQmuQCbFlf5i3q+2nsbKRO3Kpibnq6ehUXptRIeytUo+QLo7+RIMwh63WNxubfHSW+w==
MIME-Version: 1.0
X-Received: by 10.112.161.41 with SMTP id xp9mr7237997lbb.133.1460670184405; Thu, 14 Apr 2016 14:43:04 -0700 (PDT)
Sender: hallam@gmail.com
Received: by 10.112.151.67 with HTTP; Thu, 14 Apr 2016 14:43:04 -0700 (PDT)
In-Reply-To: <570FFC54.7040602@gmail.com>
References: <CAMm+Lwg-HTYCv2pGt=SP2+Xjoko6GcJ73kVzqXC1LBTOMDKV_A@mail.gmail.com> <87shyol1jf.fsf@tops.chopps.org> <CAPt1N1mRR+1iq9ueu=76WMd0K891ELvA-_YU1yar96kdcRa4CA@mail.gmail.com> <CAMm+LwhXY=nmMj+V7chRZZjpFY-ZAOaC0fqpfz83=LM-hsMCOQ@mail.gmail.com> <CAL9jLab9+gfiyNy6KY3gq+0wq5jCp14NpHMK+ZeN1An=SaqvSg@mail.gmail.com> <CAPt1N1nD856T81DBhd3qDiiiS_=Q4UTR_+p_4Q9q7Q5GutaJeg@mail.gmail.com> <570FFC54.7040602@gmail.com>
Date: Thu, 14 Apr 2016 17:43:04 -0400
X-Google-Sender-Auth: YkPTsfEMQ-CEsfnfW7eM608rdPE
Message-ID: <CAMm+Lwi6_XjcFRStMXBAqsdGhFne+cJjdLfZ+LH6zqre4dwO9w@mail.gmail.com>
Subject: Re: Time to kill layer 2
From: Phillip Hallam-Baker <phill@hallambaker.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/ohBFJ2JBJEcP5mgyrw5xV5Vam88>
Cc: IETF Discussion Mailing List <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, 14 Apr 2016 21:43:08 -0000

On Thu, Apr 14, 2016 at 4:23 PM, Brian E Carpenter
<brian.e.carpenter@gmail.com> wrote:
> On 15/04/2016 04:54, Ted Lemon wrote:
>> You should read the homenet naming and service discovery architecture
>> document. :)
>>
>> On Thu, Apr 14, 2016 at 12:54 PM, Christopher Morrow <
>> morrowc.lists@gmail.com> wrote:
>>
>>>
>>> On Thu, Apr 14, 2016 at 12:32 PM, Phillip Hallam-Baker <
>>> phill@hallambaker.com> wrote:
>>>
>>>> Going to unicast should help. Multicast configuration really doesn't
>>>> work on a network with as many hubs and devices as mine has.
>>>>
>>>
>>> multicast would work, if all the hubs/devices did multicast properly,
>>> right? :)
>
> Really stupid devices do multicast properly because they are genuinely
> transparent to layer 2. The annoying devices are the ones that pretend
> to be layer 2 + layer 3 devices but are actually half-baked layer violation
> devices. (To be specific, I have recently been burned by a layer 2/3 switch
> that does not perform correct MLD snooping. And I agree that you have to be
> in the 1% to diagnose that.)

As a general rule, any time a network device attempts anything
heuristic, it is going to get things wrong. The heuristic becomes a
source of error. Which was why so many of the early NATs were so
comically bad. They would attempt to patch up protocols like FTP, make
a hash of it and break things.

Sure, Homenet might solve some of these problems. But the reason for
my 'screed' is that listening to folk in Buenos Aires, I think a lot
of you are trying to build a network for yourselves and not a network
that works for someone like Jeremy Clarkson.

One of the rather more frustrating recent developments has been an
understanding of 'usability' that comes down to 'don't give the user
any information that might confuse them'. Windows and OSX both suffer
from their own particular flavors of this approach. In networking it
is the hub that is dropping the packets and not saying why or even
mentioning the fact that it did so.


>>> it's not clear that unicast works, if the problem you are trying to solve
>>> is service-discovery... absent some registry of 'services' for your clients
>>> to use, of course (which is the point of the mdns thingy).
>
> It seems to me that doing everything unicast makes life harder for no
> reason. I don't know how we could make the Anima signaling work without
> multicast, but we are restricting it strictly to link-local multicast.

As another general rule, all protocols that rely on superfluous
communication are bad protocols.

Before talking on a network, a device should authenticate. Is the
device going to authenticate with every other device on the network?
Does anyone imagine that to be scalable? I have over a hundred devices
on my network and in ten years time, I think that will be considered
small. If we are serious about IoT then every socket, every
lightswitch is a network device, thats another couple of hundred right
there.

Recourse to multicast is the network equivalent of suck it and see
programming. Instead of having a concept of fault tolerant network
control with failover, every device on the network is constantly
yammering to the network as a whole just to tell people its there.
When people do that, we call in a psychologist.

In process control, networks are much quieter because the plant
managers want to be able to tell why every packet on their network
appeared. Noisy protocols that talk for the sake of talk are severely
frowned on.


From nobody Thu Apr 14 14:55:17 2016
Return-Path: <dimitri.staessens@intec.ugent.be>
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 02B4312D104 for <ietf@ietfa.amsl.com>; Thu, 14 Apr 2016 14:55:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.196
X-Spam-Level: 
X-Spam-Status: No, score=-5.196 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.996] 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 naJIkCgsWuoe for <ietf@ietfa.amsl.com>; Thu, 14 Apr 2016 14:55:13 -0700 (PDT)
Received: from smtp3.ugent.be (smtp3.ugent.be [157.193.49.127]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 202C212D0B0 for <ietf@ietf.org>; Thu, 14 Apr 2016 14:55:12 -0700 (PDT)
Received: from localhost (mcheck2.ugent.be [157.193.49.249]) by smtp3.ugent.be (Postfix) with ESMTP id DC45FC184 for <ietf@ietf.org>; Thu, 14 Apr 2016 23:55:10 +0200 (CEST)
X-Virus-Scanned: by UGent DICT
Received: from smtp3.ugent.be ([IPv6:::ffff:157.193.49.127]) by localhost (mcheck2.UGent.be [::ffff:157.193.43.11]) (amavisd-new, port 10024) with ESMTP id y2J5KMpP0TCr for <ietf@ietf.org>; Thu, 14 Apr 2016 23:55:10 +0200 (CEST)
Received: from mail2.intec.ugent.be (mail2.intec.ugent.be [157.193.214.245]) by smtp3.ugent.be (Postfix) with ESMTP id 8394AC17F for <ietf@ietf.org>; Thu, 14 Apr 2016 23:55:10 +0200 (CEST)
Received: from localhost (localhost [127.0.0.1]) by mail2.intec.ugent.be (Postfix) with ESMTP id 6C72F2D for <ietf@ietf.org>; Thu, 14 Apr 2016 23:55:10 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at intec.ugent.be
Received: from mail2.intec.ugent.be ([127.0.0.1]) by localhost (mail2.intec.ugent.be [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ny8JlEemckdW for <ietf@ietf.org>; Thu, 14 Apr 2016 23:55:10 +0200 (CEST)
Received: from [192.168.126.15] (vpn-zp-126-15.vpn [192.168.126.15]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: dstaesse) by mail2.intec.ugent.be (Postfix) with ESMTPSA id 4A7952C for <ietf@ietf.org>; Thu, 14 Apr 2016 23:55:10 +0200 (CEST)
Subject: Re: Time to kill layer 2
To: ietf@ietf.org
References: <CAMm+Lwg-HTYCv2pGt=SP2+Xjoko6GcJ73kVzqXC1LBTOMDKV_A@mail.gmail.com>
From: Dimitri Staessens <dimitri.staessens@intec.ugent.be>
Message-ID: <571011B2.9080003@intec.ugent.be>
Date: Thu, 14 Apr 2016 23:54:58 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2
MIME-Version: 1.0
In-Reply-To: <CAMm+Lwg-HTYCv2pGt=SP2+Xjoko6GcJ73kVzqXC1LBTOMDKV_A@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Miltered: at jchkm1 with ID 571011BE.001 by Joe's j-chkmail (http://helpdesk.ugent.be/email/)!
X-j-chkmail-Enveloppe: 571011BE.001 from mail2.intec.ugent.be/mail2.intec.ugent.be/157.193.214.245/mail2.intec.ugent.be/<dimitri.staessens@intec.ugent.be>
X-j-chkmail-Score: MSGID : 571011BE.001 on smtp3.ugent.be : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Status: Ham
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/4fkgMLsAmB_IDf7VJCQ5546uqSo>
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, 14 Apr 2016 21:55:15 -0000

anyone thought of killing everything on top of layer 2?

On 04/14/16 14:59, Phillip Hallam-Baker wrote:
> This morning I spent an hour debugging the network to print out two
> class projects that were due. Some points:
>
> 1) My ability to debug the network is better than 99% of the population
> 2) The interaction of Bonjour, DHCP and auto power saving is unfortunate
> 3) Things should still work after I have been away for a week
> 4) If vendors want to be selling all that IoT gear, they have to solve
> these issues.
>
> 5) I want someone to blame. Right now when the network doesn't work, I
> don't know who is the cause. I want one point of contact. Whoever is
> that point of contact will get most of my networking money.
>
>
> One of the biggest headaches in debugging is that 'smart hubs' are
> not. They are actually very stupid. They make assumptions of network
> topology that are not true. Another is the unfortunate implementation
> of DHCP.
>
> I don't use SNMP for a simple reason - it is not available to most
> ordinary people. I want to understand networking for the 99%, not the
> IETF 1%-ers.
>
> All this networking gear is presented to me as black boxes over which
> I have absolutely no control (which is fine-ish) and no visibility.
>
> What we have today is the product of a historical process. I remember
> the days when Ethernet ran on 10BaseT. But I installed my first switch
> 30 years ago and it has been a switched protocol for 20 years now.
>
>
> It seems to me that there is a business opportunity for any vendor who
> takes the rather obvious step of simplifying the system.
>
> People talk about 'IP everywhere' and 'IP end-to-end' which is rather
> odd when you think about the fact that virtually every local network
> uses MAC addresses for routing.
>
> One of the reasons that IP won against OSI was that it was simpler.
> Applications ran on top of the IP layer with only TCP inbetween. Of
> course these days we do have a Presentation layer, Web Services run on
> HTTP. But unlike the OSI presentation layer, ours does not introduce
> extra moving parts.
>
> It seems to me that if we really believed in IP everywhere and IP
> end-to-end we would insist that network switches be IP routers that
> can be managed using BGP/OSPF or at least routing tables rather than
> heuristic devices that try to guess where packets should go based on
> goat entrails, phases of the moon or whatever they use.
>
>
> What should have happened many moons ago was that DHCP should have
> become a bidirectional protocol or a bootstrap to a bidirectional
> protocol. So when a printer joins the network, it authenticates and
> tells the network what it is. And this is all defined in one set of
> specifications from one organization, none of which assumes that
> security is an 'advanced', 'optional' or 'enterprise' feature.
>
> Instead we have an ad-hoc layer trying to achieve the same result in
> peer-to-peer fashion. A similar approach works for frogs as a
> reproductive mechanism but only at the species level. It certainly
> does not work for the individual ova which may or may not connect to
> the printer it is trying to use to print the kids damned homework.
>
>
> Seriously, the fact that things have scaled thus far and the 1% can
> get them to work does not mean that we can get to the next level
> without a serious rethink of the local network architecture.
>
> The type of device I think we need would be first and foremost an IP
> router. It would have ethernet plugs on the box and use ethernet layer
> 1 specs. But when a another 'True-IP' device was plugged in, it would
> quickly negotiate a direct IP connection, oh and with proper 64KB
> packets. It would also, authenticate, announce and turn on link layer
> encryption.
>
> Such a device would also be a legacy router. It would fake all the
> signals necessary for a legacy ethernet device to function. It would
> also be responsible for maintaining the local information for the
> network service database and intercommunicating with other hubs to
> achieve a global network view.
>
>
> The net result of all this would be that I would never ever need to
> install another printer (no, it is not actually necessary for every
> stupid printer to have its own stupid printer driver). Opening the
> 'printers' folder would automatically show every printer that is on
> the network or can be woken from slumber by the hub it connects to.
>


From nobody Thu Apr 14 14:57:24 2016
Return-Path: <mellon@fugue.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 AB8A112D955 for <ietf@ietfa.amsl.com>; Thu, 14 Apr 2016 14:57:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.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 NSufsp29isNT for <ietf@ietfa.amsl.com>; Thu, 14 Apr 2016 14:57:20 -0700 (PDT)
Received: from mail-lf0-x22e.google.com (mail-lf0-x22e.google.com [IPv6:2a00:1450:4010:c07::22e]) (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 2888F12D9A9 for <ietf@ietf.org>; Thu, 14 Apr 2016 14:57:20 -0700 (PDT)
Received: by mail-lf0-x22e.google.com with SMTP id e190so125163158lfe.0 for <ietf@ietf.org>; Thu, 14 Apr 2016 14:57:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=bGi65gjzPbZOgl6MpYcl+PFNihrP/XzlXTP7VmPR10c=; b=DK/G4hcFqDO4z3iccGgS5KLektfi9rBycheC6gqFmzeZWSOD/GFucitPZ86+QFz/0r +zK2Zxg5DnaOORagUloOryk5gZrOgOIVfQQpQi2FkMOqtpZn2GnMLJLQIxP9CAYrS/P3 GzvnIg5XUJgY2N+Qqctq4G6KmbhLcHkmIRkIqXCr7FcEYLOAovGSgSChEaf58X4Hlf2a A+cQ8lx79m4xr+pzo4GzthYtwBg5oL2qvp0bNFf6wzq10I/kYAG+lsWuaqkfK7neUMxj jRbwrlsEXPFXkVbFZBdU5KJCR8+U3kYMNsPH9yk4JcGr3iNkdKpPnHYyG8G39kpPBe8Q Wz0Q==
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=bGi65gjzPbZOgl6MpYcl+PFNihrP/XzlXTP7VmPR10c=; b=l7vDZagIAmemUehTt9gOC6frX43YqysPguXhwEjATBraLMZXzD+mFcBevZVQX6gC/R nASy2qRcJxe/rtgH9ilhb1RCly140jU/G5yRSmo4tKgrr3KdQSn2Yyxkz5zAh8LsuRe1 meQfLSZ4PYIZSj+cdJKZFW1dNGhJwuuMT7rhqYNPzqP3k9u1KstXgxpnYyzfRnr1N0V7 1fmpAkdG23WjFLhyhvOBuM9iIuXu30BOmuerYf7J4hs5xSjQJ0f/W7ccOZJED4HORX8N UMGMZtuRD02+UR5ckUSpcycbbZetb9xxOHTSkWoEudv30754HNKJb/AovHz3jS3RN267 qUHg==
X-Gm-Message-State: AOPr4FW3wypLpzr67O/KtoMDUWKCh7Yyz8me9/4Edh24gpnZwItLEiRdcurahzsk/wH7e2Hj8W0z4e3BwqkZMA==
X-Received: by 10.25.32.213 with SMTP id g204mr4520031lfg.119.1460671038308; Thu, 14 Apr 2016 14:57:18 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.25.213.19 with HTTP; Thu, 14 Apr 2016 14:56:38 -0700 (PDT)
X-Originating-IP: [71.233.41.235]
In-Reply-To: <571011B2.9080003@intec.ugent.be>
References: <CAMm+Lwg-HTYCv2pGt=SP2+Xjoko6GcJ73kVzqXC1LBTOMDKV_A@mail.gmail.com> <571011B2.9080003@intec.ugent.be>
From: Ted Lemon <mellon@fugue.com>
Date: Thu, 14 Apr 2016 17:56:38 -0400
Message-ID: <CAPt1N1m71Vx6LX-dTuHVoYfZG_X7wykax2QMteqFjcsRt+RThw@mail.gmail.com>
Subject: Re: Time to kill layer 2
To: Dimitri Staessens <dimitri.staessens@intec.ugent.be>
Content-Type: multipart/alternative; boundary=001a11401fec5f596a053078fafe
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/oNpmRceDYaJONsUvZWIQLKKADkw>
Cc: ietf <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, 14 Apr 2016 21:57:22 -0000

--001a11401fec5f596a053078fafe
Content-Type: text/plain; charset=UTF-8

Of course!

On Thu, Apr 14, 2016 at 5:54 PM, Dimitri Staessens <
dimitri.staessens@intec.ugent.be> wrote:

> anyone thought of killing everything on top of layer 2?
>
>
> On 04/14/16 14:59, Phillip Hallam-Baker wrote:
>
>> This morning I spent an hour debugging the network to print out two
>> class projects that were due. Some points:
>>
>> 1) My ability to debug the network is better than 99% of the population
>> 2) The interaction of Bonjour, DHCP and auto power saving is unfortunate
>> 3) Things should still work after I have been away for a week
>> 4) If vendors want to be selling all that IoT gear, they have to solve
>> these issues.
>>
>> 5) I want someone to blame. Right now when the network doesn't work, I
>> don't know who is the cause. I want one point of contact. Whoever is
>> that point of contact will get most of my networking money.
>>
>>
>> One of the biggest headaches in debugging is that 'smart hubs' are
>> not. They are actually very stupid. They make assumptions of network
>> topology that are not true. Another is the unfortunate implementation
>> of DHCP.
>>
>> I don't use SNMP for a simple reason - it is not available to most
>> ordinary people. I want to understand networking for the 99%, not the
>> IETF 1%-ers.
>>
>> All this networking gear is presented to me as black boxes over which
>> I have absolutely no control (which is fine-ish) and no visibility.
>>
>> What we have today is the product of a historical process. I remember
>> the days when Ethernet ran on 10BaseT. But I installed my first switch
>> 30 years ago and it has been a switched protocol for 20 years now.
>>
>>
>> It seems to me that there is a business opportunity for any vendor who
>> takes the rather obvious step of simplifying the system.
>>
>> People talk about 'IP everywhere' and 'IP end-to-end' which is rather
>> odd when you think about the fact that virtually every local network
>> uses MAC addresses for routing.
>>
>> One of the reasons that IP won against OSI was that it was simpler.
>> Applications ran on top of the IP layer with only TCP inbetween. Of
>> course these days we do have a Presentation layer, Web Services run on
>> HTTP. But unlike the OSI presentation layer, ours does not introduce
>> extra moving parts.
>>
>> It seems to me that if we really believed in IP everywhere and IP
>> end-to-end we would insist that network switches be IP routers that
>> can be managed using BGP/OSPF or at least routing tables rather than
>> heuristic devices that try to guess where packets should go based on
>> goat entrails, phases of the moon or whatever they use.
>>
>>
>> What should have happened many moons ago was that DHCP should have
>> become a bidirectional protocol or a bootstrap to a bidirectional
>> protocol. So when a printer joins the network, it authenticates and
>> tells the network what it is. And this is all defined in one set of
>> specifications from one organization, none of which assumes that
>> security is an 'advanced', 'optional' or 'enterprise' feature.
>>
>> Instead we have an ad-hoc layer trying to achieve the same result in
>> peer-to-peer fashion. A similar approach works for frogs as a
>> reproductive mechanism but only at the species level. It certainly
>> does not work for the individual ova which may or may not connect to
>> the printer it is trying to use to print the kids damned homework.
>>
>>
>> Seriously, the fact that things have scaled thus far and the 1% can
>> get them to work does not mean that we can get to the next level
>> without a serious rethink of the local network architecture.
>>
>> The type of device I think we need would be first and foremost an IP
>> router. It would have ethernet plugs on the box and use ethernet layer
>> 1 specs. But when a another 'True-IP' device was plugged in, it would
>> quickly negotiate a direct IP connection, oh and with proper 64KB
>> packets. It would also, authenticate, announce and turn on link layer
>> encryption.
>>
>> Such a device would also be a legacy router. It would fake all the
>> signals necessary for a legacy ethernet device to function. It would
>> also be responsible for maintaining the local information for the
>> network service database and intercommunicating with other hubs to
>> achieve a global network view.
>>
>>
>> The net result of all this would be that I would never ever need to
>> install another printer (no, it is not actually necessary for every
>> stupid printer to have its own stupid printer driver). Opening the
>> 'printers' folder would automatically show every printer that is on
>> the network or can be woken from slumber by the hub it connects to.
>>
>>
>

--001a11401fec5f596a053078fafe
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Of course!</div><div class=3D"gmail_extra"><br><div class=
=3D"gmail_quote">On Thu, Apr 14, 2016 at 5:54 PM, Dimitri Staessens <span d=
ir=3D"ltr">&lt;<a href=3D"mailto:dimitri.staessens@intec.ugent.be" target=
=3D"_blank">dimitri.staessens@intec.ugent.be</a>&gt;</span> wrote:<br><bloc=
kquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #cc=
c solid;padding-left:1ex">anyone thought of killing everything on top of la=
yer 2?<div class=3D"HOEnZb"><div class=3D"h5"><br>
<br>
On 04/14/16 14:59, Phillip Hallam-Baker wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
This morning I spent an hour debugging the network to print out two<br>
class projects that were due. Some points:<br>
<br>
1) My ability to debug the network is better than 99% of the population<br>
2) The interaction of Bonjour, DHCP and auto power saving is unfortunate<br=
>
3) Things should still work after I have been away for a week<br>
4) If vendors want to be selling all that IoT gear, they have to solve<br>
these issues.<br>
<br>
5) I want someone to blame. Right now when the network doesn&#39;t work, I<=
br>
don&#39;t know who is the cause. I want one point of contact. Whoever is<br=
>
that point of contact will get most of my networking money.<br>
<br>
<br>
One of the biggest headaches in debugging is that &#39;smart hubs&#39; are<=
br>
not. They are actually very stupid. They make assumptions of network<br>
topology that are not true. Another is the unfortunate implementation<br>
of DHCP.<br>
<br>
I don&#39;t use SNMP for a simple reason - it is not available to most<br>
ordinary people. I want to understand networking for the 99%, not the<br>
IETF 1%-ers.<br>
<br>
All this networking gear is presented to me as black boxes over which<br>
I have absolutely no control (which is fine-ish) and no visibility.<br>
<br>
What we have today is the product of a historical process. I remember<br>
the days when Ethernet ran on 10BaseT. But I installed my first switch<br>
30 years ago and it has been a switched protocol for 20 years now.<br>
<br>
<br>
It seems to me that there is a business opportunity for any vendor who<br>
takes the rather obvious step of simplifying the system.<br>
<br>
People talk about &#39;IP everywhere&#39; and &#39;IP end-to-end&#39; which=
 is rather<br>
odd when you think about the fact that virtually every local network<br>
uses MAC addresses for routing.<br>
<br>
One of the reasons that IP won against OSI was that it was simpler.<br>
Applications ran on top of the IP layer with only TCP inbetween. Of<br>
course these days we do have a Presentation layer, Web Services run on<br>
HTTP. But unlike the OSI presentation layer, ours does not introduce<br>
extra moving parts.<br>
<br>
It seems to me that if we really believed in IP everywhere and IP<br>
end-to-end we would insist that network switches be IP routers that<br>
can be managed using BGP/OSPF or at least routing tables rather than<br>
heuristic devices that try to guess where packets should go based on<br>
goat entrails, phases of the moon or whatever they use.<br>
<br>
<br>
What should have happened many moons ago was that DHCP should have<br>
become a bidirectional protocol or a bootstrap to a bidirectional<br>
protocol. So when a printer joins the network, it authenticates and<br>
tells the network what it is. And this is all defined in one set of<br>
specifications from one organization, none of which assumes that<br>
security is an &#39;advanced&#39;, &#39;optional&#39; or &#39;enterprise&#3=
9; feature.<br>
<br>
Instead we have an ad-hoc layer trying to achieve the same result in<br>
peer-to-peer fashion. A similar approach works for frogs as a<br>
reproductive mechanism but only at the species level. It certainly<br>
does not work for the individual ova which may or may not connect to<br>
the printer it is trying to use to print the kids damned homework.<br>
<br>
<br>
Seriously, the fact that things have scaled thus far and the 1% can<br>
get them to work does not mean that we can get to the next level<br>
without a serious rethink of the local network architecture.<br>
<br>
The type of device I think we need would be first and foremost an IP<br>
router. It would have ethernet plugs on the box and use ethernet layer<br>
1 specs. But when a another &#39;True-IP&#39; device was plugged in, it wou=
ld<br>
quickly negotiate a direct IP connection, oh and with proper 64KB<br>
packets. It would also, authenticate, announce and turn on link layer<br>
encryption.<br>
<br>
Such a device would also be a legacy router. It would fake all the<br>
signals necessary for a legacy ethernet device to function. It would<br>
also be responsible for maintaining the local information for the<br>
network service database and intercommunicating with other hubs to<br>
achieve a global network view.<br>
<br>
<br>
The net result of all this would be that I would never ever need to<br>
install another printer (no, it is not actually necessary for every<br>
stupid printer to have its own stupid printer driver). Opening the<br>
&#39;printers&#39; folder would automatically show every printer that is on=
<br>
the network or can be woken from slumber by the hub it connects to.<br>
<br>
</blockquote>
<br>
</div></div></blockquote></div><br></div>

--001a11401fec5f596a053078fafe--


From nobody Thu Apr 14 19:47:59 2016
Return-Path: <carlosm3011@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 2059312E6B9 for <ietf@ietfa.amsl.com>; Thu, 14 Apr 2016 19:47:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.45
X-Spam-Level: 
X-Spam-Status: No, score=-2.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, RCVD_IN_DNSWL_LOW=-0.7, 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 LHkVdLEBtdbC for <ietf@ietfa.amsl.com>; Thu, 14 Apr 2016 19:47:56 -0700 (PDT)
Received: from mail-vk0-x235.google.com (mail-vk0-x235.google.com [IPv6:2607:f8b0:400c:c05::235]) (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 8275B12E6B7 for <ietf@ietf.org>; Thu, 14 Apr 2016 19:47:56 -0700 (PDT)
Received: by mail-vk0-x235.google.com with SMTP id t129so132482659vkg.2 for <ietf@ietf.org>; Thu, 14 Apr 2016 19:47:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=reply-to:subject:references:to:cc:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=9e1pk6QSAN8jfmZ/+Jx9Cb91xdYAlPYiQjIK9TJjz0I=; b=hl2zj42SOIqQQBHQFu/QX9FNDDY6I2NQtNtajhHbN+QQOcGoEG3F0/MZBPJnp73dIm Z0zXoFmwHnoSQy4J5Ic/1gYw5M3crOs0Vs5mVPvd5A8wQqcoQqEf8P6Zl4QmyZ8a7KVx 58B3KAl7iQxG6AX0UHUU8K+7t8Bbf1++vVNPEsuAFVBpdHEH0j/E/hH3xS+qt0BNPdTN D2MjEHUsqud00WycyAkeHtDBHrcU/WAu8hSpRket19X/U0Xtielu+nAfzliWyBwN+qZf PN2l48219xvDwkSleS1QJ9qdqrIPHnJPGkMoL0VdR7kmJqVT4K6LRe/ojJ1hpMMDlgdH p+vA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:reply-to:subject:references:to:cc:from :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=9e1pk6QSAN8jfmZ/+Jx9Cb91xdYAlPYiQjIK9TJjz0I=; b=ehBXlrXWHSWtoUjnRU4fyNzkxfKA2qOBjGiMuhkyoh4ydKfKsNW3j2jP+VU3ONQpUJ nwUtSQvIfws1SYp7Cb709qez5T/+TAAcnJRKWi6KiGcfBojQ70EsJmjMETIdDpo0i584 QuKVYxqBKaHk6EXU+q7/uPlkFt6Me/lmxhaHVZ9pxS0oXFzbXuVRFGwvWZ4iw7m5ookV hD0rT0aU7dkLatbVWc/8qc7v5PUNkXQfs1fifQZnir97S9ra8SkVvT3pWfK+zEAnx3ir KGX8TA3iPz+y0/n4/7EmXI1vGeYxD/9IIgvtKvBD9CAmQp/LIdxHEKlyXnJ+7finQ9BN wLjw==
X-Gm-Message-State: AOPr4FWOIXjvuaVdSx8wlNuAvZCzbSLu79+CeNr9glK2QDtJkv3nrNQa84Ry8q6OeSbWGw==
X-Received: by 10.31.150.76 with SMTP id y73mr9382241vkd.84.1460688475437; Thu, 14 Apr 2016 19:47:55 -0700 (PDT)
Received: from grenada.local ([2800:af:a73d:8e7d:4184:7d3e:b1f8:bef0]) by smtp.googlemail.com with ESMTPSA id m85sm2350627vka.15.2016.04.14.19.47.53 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 14 Apr 2016 19:47:54 -0700 (PDT)
Subject: Re: Time to kill layer 2
References: <CAMm+Lwg-HTYCv2pGt=SP2+Xjoko6GcJ73kVzqXC1LBTOMDKV_A@mail.gmail.com> <571011B2.9080003@intec.ugent.be> <CAPt1N1m71Vx6LX-dTuHVoYfZG_X7wykax2QMteqFjcsRt+RThw@mail.gmail.com>
To: Ted Lemon <mellon@fugue.com>, Dimitri Staessens <dimitri.staessens@intec.ugent.be>
From: "Carlos M. Martinez" <carlosm3011@gmail.com>
Message-ID: <57105657.80006@gmail.com>
Date: Thu, 14 Apr 2016 23:47:51 -0300
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:38.0) Gecko/20100101 Thunderbird/38.7.2
MIME-Version: 1.0
In-Reply-To: <CAPt1N1m71Vx6LX-dTuHVoYfZG_X7wykax2QMteqFjcsRt+RThw@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/07cSoosLG8WUlAr4a1_4Q-3xIvg>
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: carlos@lacnic.net
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: Fri, 15 Apr 2016 02:47:58 -0000

All the way up to the user ? Many times.

On 4/14/16 6:56 PM, Ted Lemon wrote:
> Of course!
> 
> On Thu, Apr 14, 2016 at 5:54 PM, Dimitri Staessens
> <dimitri.staessens@intec.ugent.be
> <mailto:dimitri.staessens@intec.ugent.be>> wrote:
> 
>     anyone thought of killing everything on top of layer 2?
> 
> 
>     On 04/14/16 14:59, Phillip Hallam-Baker wrote:
> 
>         This morning I spent an hour debugging the network to print out two
>         class projects that were due. Some points:
> 
>         1) My ability to debug the network is better than 99% of the
>         population
>         2) The interaction of Bonjour, DHCP and auto power saving is
>         unfortunate
>         3) Things should still work after I have been away for a week
>         4) If vendors want to be selling all that IoT gear, they have to
>         solve
>         these issues.
> 
>         5) I want someone to blame. Right now when the network doesn't
>         work, I
>         don't know who is the cause. I want one point of contact. Whoever is
>         that point of contact will get most of my networking money.
> 
> 
>         One of the biggest headaches in debugging is that 'smart hubs' are
>         not. They are actually very stupid. They make assumptions of network
>         topology that are not true. Another is the unfortunate
>         implementation
>         of DHCP.
> 
>         I don't use SNMP for a simple reason - it is not available to most
>         ordinary people. I want to understand networking for the 99%,
>         not the
>         IETF 1%-ers.
> 
>         All this networking gear is presented to me as black boxes over
>         which
>         I have absolutely no control (which is fine-ish) and no visibility.
> 
>         What we have today is the product of a historical process. I
>         remember
>         the days when Ethernet ran on 10BaseT. But I installed my first
>         switch
>         30 years ago and it has been a switched protocol for 20 years now.
> 
> 
>         It seems to me that there is a business opportunity for any
>         vendor who
>         takes the rather obvious step of simplifying the system.
> 
>         People talk about 'IP everywhere' and 'IP end-to-end' which is
>         rather
>         odd when you think about the fact that virtually every local network
>         uses MAC addresses for routing.
> 
>         One of the reasons that IP won against OSI was that it was simpler.
>         Applications ran on top of the IP layer with only TCP inbetween. Of
>         course these days we do have a Presentation layer, Web Services
>         run on
>         HTTP. But unlike the OSI presentation layer, ours does not introduce
>         extra moving parts.
> 
>         It seems to me that if we really believed in IP everywhere and IP
>         end-to-end we would insist that network switches be IP routers that
>         can be managed using BGP/OSPF or at least routing tables rather than
>         heuristic devices that try to guess where packets should go based on
>         goat entrails, phases of the moon or whatever they use.
> 
> 
>         What should have happened many moons ago was that DHCP should have
>         become a bidirectional protocol or a bootstrap to a bidirectional
>         protocol. So when a printer joins the network, it authenticates and
>         tells the network what it is. And this is all defined in one set of
>         specifications from one organization, none of which assumes that
>         security is an 'advanced', 'optional' or 'enterprise' feature.
> 
>         Instead we have an ad-hoc layer trying to achieve the same result in
>         peer-to-peer fashion. A similar approach works for frogs as a
>         reproductive mechanism but only at the species level. It certainly
>         does not work for the individual ova which may or may not connect to
>         the printer it is trying to use to print the kids damned homework.
> 
> 
>         Seriously, the fact that things have scaled thus far and the 1% can
>         get them to work does not mean that we can get to the next level
>         without a serious rethink of the local network architecture.
> 
>         The type of device I think we need would be first and foremost an IP
>         router. It would have ethernet plugs on the box and use ethernet
>         layer
>         1 specs. But when a another 'True-IP' device was plugged in, it
>         would
>         quickly negotiate a direct IP connection, oh and with proper 64KB
>         packets. It would also, authenticate, announce and turn on link
>         layer
>         encryption.
> 
>         Such a device would also be a legacy router. It would fake all the
>         signals necessary for a legacy ethernet device to function. It would
>         also be responsible for maintaining the local information for the
>         network service database and intercommunicating with other hubs to
>         achieve a global network view.
> 
> 
>         The net result of all this would be that I would never ever need to
>         install another printer (no, it is not actually necessary for every
>         stupid printer to have its own stupid printer driver). Opening the
>         'printers' folder would automatically show every printer that is on
>         the network or can be woken from slumber by the hub it connects to.
> 
> 
> 


From nobody Thu Apr 14 20:30:24 2016
Return-Path: <chaitanyabd@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 4597A12D73E for <ietf@ietfa.amsl.com>; Thu, 14 Apr 2016 20:30:23 -0700 (PDT)
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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 k7XDDwL6a51V for <ietf@ietfa.amsl.com>; Thu, 14 Apr 2016 20:30:21 -0700 (PDT)
Received: from mail-pf0-x232.google.com (mail-pf0-x232.google.com [IPv6:2607:f8b0:400e:c00::232]) (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 D871F12D6B2 for <ietf@ietf.org>; Thu, 14 Apr 2016 20:30:20 -0700 (PDT)
Received: by mail-pf0-x232.google.com with SMTP id e128so52263574pfe.3 for <ietf@ietf.org>; Thu, 14 Apr 2016 20:30:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:mime-version:to:cc:from:subject:date:importance :in-reply-to:references; bh=HbVGcWCplnjByJVWqVD6bQbv8X72gAELz6TFO/ZjybM=; b=xUWTW0sYFSj09UhCSlb2krsmDosxyPai0SvdOW3pFDwqPDjnkMd98F7LD/PQUR/LHA HkJ/OshtDRGYt/nUfVUrRxd+vNaQHiTNhKLgpgDltPoyn69js0aN1ruiN8RLJ9OJcKYY em99ouL+ukRGMu4tFPbNn7L/d5rhB1JNO0dnKp7NrQfI7WtP5oK7y3Hn2FD7wj/wvkiI EII55ekm4k5gRyY/jfXzybVqDJSgLwbSIl3YdRkovJpARuh7TNgBuIbYqYYFa4p2lsC4 gjyRKjI3Wt9U8zCmaHPTYE4gYYoZe7lW95gCGdV5+M+EOi1ksWsbKcN0n3ExrdOOibWv p4PQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:mime-version:to:cc:from:subject:date :importance:in-reply-to:references; bh=HbVGcWCplnjByJVWqVD6bQbv8X72gAELz6TFO/ZjybM=; b=dWVvb8sAZWo/399adWQ5acDYi1zErv5hYoGKfN27RUBHicm8BtBEPVwNyvbtMeuzmw cCVV53ow39cmIq4gqCX8WiGpxmhQvUUECjW/GI/1yWSGuXMe0xkGeh6lpsKBbi/cv2if sIUmsax0L+Dq3bRluuBnOwhGDdYvjW1CHFoRUfOLCCmhKTf64VGL/qq6NDTYqD6lwu4I 1gsPdDJYJIlOm1lH67Bin4OXNI7S6BUQhBnsZwEi8igj9jBtCn5rHNUYFGh/TBIjl/0w g5SoA2K+TpxXQa5MRTmakpAzAWGe0ft2IUKqDK0p8S01go2Mez1CADrQIxF/th/PzcCU z1qg==
X-Gm-Message-State: AOPr4FXi11V2RHzYDKnOuPEAHUk1SMWl5JIDcXb7uVKacJc5C55gLCbIMGnvh5jiBNhILg==
X-Received: by 10.98.66.89 with SMTP id p86mr26045952pfa.42.1460691020408; Thu, 14 Apr 2016 20:30:20 -0700 (PDT)
Received: from ?IPv6:::ffff:10.164.136.101? ([1.39.10.74]) by smtp.gmail.com with ESMTPSA id n74sm60995411pfa.45.2016.04.14.20.30.16 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 14 Apr 2016 20:30:18 -0700 (PDT)
Message-ID: <5710604a.4d40620a.1fffb.ffffd647@mx.google.com>
MIME-Version: 1.0
To: "Carlos M. Martinez" <carlosm3011@gmail.com>,  Ted Lemon <mellon@fugue.com>,  Dimitri Staessens <dimitri.staessens@intec.ugent.be>
From: Chaitanya D <chaitanyabd@gmail.com>
Subject: RE: Time to kill layer 2
Date: Fri, 15 Apr 2016 09:00:04 +0530
Importance: normal
X-Priority: 3
In-Reply-To: <57105657.80006@gmail.com>
References: <CAMm+Lwg-HTYCv2pGt=SP2+Xjoko6GcJ73kVzqXC1LBTOMDKV_A@mail.gmail.com> <571011B2.9080003@intec.ugent.be> <CAPt1N1m71Vx6LX-dTuHVoYfZG_X7wykax2QMteqFjcsRt+RThw@mail.gmail.com> <57105657.80006@gmail.com>
Content-Type: multipart/alternative; boundary="_A3734A22-007D-4A0C-8D66-83BDED9F63E1_"
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/zbuDF-Ell4xQQ-nNpmpyq3XAnd0>
Cc: ietf <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: Fri, 15 Apr 2016 03:30:23 -0000

--_A3734A22-007D-4A0C-8D66-83BDED9F63E1_
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="utf-8"

The BOFH way - kill the user and let the network be.... ;)

Kidding of course



From: Carlos M. Martinez
Sent: 15 April 2016 08:18
To: Ted Lemon;Dimitri Staessens
Cc: ietf
Subject: Re: Time to kill layer 2


All the way up to the user ? Many times.

On 4/14/16 6:56 PM, Ted Lemon wrote:
> Of course!
>=20
> On Thu, Apr 14, 2016 at 5:54 PM, Dimitri Staessens
> <dimitri.staessens@intec.ugent.be
> <mailto:dimitri.staessens@intec.ugent.be>> wrote:
>=20
>     anyone thought of killing everything on top of layer 2?
>=20
>=20
>     On 04/14/16 14:59, Phillip Hallam-Baker wrote:
>=20
>         This morning I spent an hour debugging the network to print out t=
wo
>         class projects that were due. Some points:
>=20
>         1) My ability to debug the network is better than 99% of the
>         population
>         2) The interaction of Bonjour, DHCP and auto power saving is
>         unfortunate
>         3) Things should still work after I have been away for a week
>         4) If vendors want to be selling all that IoT gear, they have to
>         solve
>         these issues.
>=20
>         5) I want someone to blame. Right now when the network doesn't
>         work, I
>         don't know who is the cause. I want one point of contact. Whoever=
 is
>         that point of contact will get most of my networking money.
>=20
>=20
>         One of the biggest headaches in debugging is that 'smart hubs' ar=
e
>         not. They are actually very stupid. They make assumptions of netw=
ork
>         topology that are not true. Another is the unfortunate
>         implementation
>         of DHCP.
>=20
>         I don't use SNMP for a simple reason - it is not available to mos=
t
>         ordinary people. I want to understand networking for the 99%,
>         not the
>         IETF 1%-ers.
>=20
>         All this networking gear is presented to me as black boxes over
>         which
>         I have absolutely no control (which is fine-ish) and no visibilit=
y.
>=20
>         What we have today is the product of a historical process. I
>         remember
>         the days when Ethernet ran on 10BaseT. But I installed my first
>         switch
>         30 years ago and it has been a switched protocol for 20 years now=
.
>=20
>=20
>         It seems to me that there is a business opportunity for any
>         vendor who
>         takes the rather obvious step of simplifying the system.
>=20
>         People talk about 'IP everywhere' and 'IP end-to-end' which is
>         rather
>         odd when you think about the fact that virtually every local netw=
ork
>         uses MAC addresses for routing.
>=20
>         One of the reasons that IP won against OSI was that it was simple=
r.
>         Applications ran on top of the IP layer with only TCP inbetween. =
Of
>         course these days we do have a Presentation layer, Web Services
>         run on
>         HTTP. But unlike the OSI presentation layer, ours does not introd=
uce
>         extra moving parts.
>=20
>         It seems to me that if we really believed in IP everywhere and IP
>         end-to-end we would insist that network switches be IP routers th=
at
>         can be managed using BGP/OSPF or at least routing tables rather t=
han
>         heuristic devices that try to guess where packets should go based=
 on
>         goat entrails, phases of the moon or whatever they use.
>=20
>=20
>         What should have happened many moons ago was that DHCP should hav=
e
>         become a bidirectional protocol or a bootstrap to a bidirectional
>         protocol. So when a printer joins the network, it authenticates a=
nd
>         tells the network what it is. And this is all defined in one set =
of
>         specifications from one organization, none of which assumes that
>         security is an 'advanced', 'optional' or 'enterprise' feature.
>=20
>         Instead we have an ad-hoc layer trying to achieve the same result=
 in
>         peer-to-peer fashion. A similar approach works for frogs as a
>         reproductive mechanism but only at the species level. It certainl=
y
>         does not work for the individual ova which may or may not connect=
 to
>         the printer it is trying to use to print the kids damned homework=
.
>=20
>=20
>         Seriously, the fact that things have scaled thus far and the 1% c=
an
>         get them to work does not mean that we can get to the next level
>         without a serious rethink of the local network architecture.
>=20
>         The type of device I think we need would be first and foremost an=
 IP
>         router. It would have ethernet plugs on the box and use ethernet
>         layer
>         1 specs. But when a another 'True-IP' device was plugged in, it
>         would
>         quickly negotiate a direct IP connection, oh and with proper 64KB
>         packets. It would also, authenticate, announce and turn on link
>         layer
>         encryption.
>=20
>         Such a device would also be a legacy router. It would fake all th=
e
>         signals necessary for a legacy ethernet device to function. It wo=
uld
>         also be responsible for maintaining the local information for the
>         network service database and intercommunicating with other hubs t=
o
>         achieve a global network view.
>=20
>=20
>         The net result of all this would be that I would never ever need =
to
>         install another printer (no, it is not actually necessary for eve=
ry
>         stupid printer to have its own stupid printer driver). Opening th=
e
>         'printers' folder would automatically show every printer that is =
on
>         the network or can be woken from slumber by the hub it connects t=
o.
>=20
>=20
>=20




--_A3734A22-007D-4A0C-8D66-83BDED9F63E1_
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html; charset="utf-8"

<html xmlns:o=3D"urn:schemas-microsoft-com:office:office" xmlns:w=3D"urn:sc=
hemas-microsoft-com:office:word" xmlns:m=3D"http://schemas.microsoft.com/of=
fice/2004/12/omml" xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta ht=
tp-equiv=3DContent-Type content=3D"text/html; charset=3Dutf-8"><meta name=
=3DGenerator content=3D"Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;}
p
	{mso-style-priority:99;
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
.MsoChpDefault
	{mso-style-type:export-only;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style></head><body lang=3DEN-IN link=3Dblue vlink=3D"#954F72"><div cla=
ss=3DWordSection1><p>The BOFH way - kill the user and let the network be...=
. ;)</p><p><o:p>&nbsp;</o:p></p><p>Kidding of course</p><p><o:p>&nbsp;</o:p=
></p><p><o:p>&nbsp;</o:p></p><div style=3D'mso-element:para-border-div;bord=
er:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p style=
=3D'border:none;padding:0cm'><br><b>From: </b>Carlos M. Martinez<br><b>Sent=
: </b>15 April 2016 08:18<br><b>To: </b>Ted Lemon;Dimitri Staessens<br><b>C=
c: </b>ietf<br><b>Subject: </b>Re: Time to kill layer 2</p></div><p class=
=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal><span style=3D'font-=
family:"Times New Roman",serif'><o:p>&nbsp;</o:p></span></p><p class=3DMsoN=
ormal>All the way up to the user ? Many times.</p><p class=3DMsoNormal><o:p=
>&nbsp;</o:p></p><p class=3DMsoNormal>On 4/14/16 6:56 PM, Ted Lemon wrote:<=
/p><p class=3DMsoNormal>&gt; Of course!</p><p class=3DMsoNormal>&gt; </p><p=
 class=3DMsoNormal>&gt; On Thu, Apr 14, 2016 at 5:54 PM, Dimitri Staessens<=
/p><p class=3DMsoNormal>&gt; &lt;dimitri.staessens@intec.ugent.be</p><p cla=
ss=3DMsoNormal>&gt; &lt;mailto:dimitri.staessens@intec.ugent.be&gt;&gt; wro=
te:</p><p class=3DMsoNormal>&gt; </p><p class=3DMsoNormal>&gt;=C2=A0=C2=A0=
=C2=A0=C2=A0 anyone thought of killing everything on top of layer 2?</p><p =
class=3DMsoNormal>&gt; </p><p class=3DMsoNormal>&gt; </p><p class=3DMsoNorm=
al>&gt;=C2=A0=C2=A0=C2=A0=C2=A0 On 04/14/16 14:59, Phillip Hallam-Baker wro=
te:</p><p class=3DMsoNormal>&gt; </p><p class=3DMsoNormal>&gt;=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 This morning I spent an hour debugging=
 the network to print out two</p><p class=3DMsoNormal>&gt;=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 class projects that were due. Some points=
:</p><p class=3DMsoNormal>&gt; </p><p class=3DMsoNormal>&gt;=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 1) My ability to debug the network is bet=
ter than 99% of the</p><p class=3DMsoNormal>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0 population</p><p class=3DMsoNormal>&gt;=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 2) The interaction of Bonjour, DHCP an=
d auto power saving is</p><p class=3DMsoNormal>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0 unfortunate</p><p class=3DMsoNormal>&gt;=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 3) Things should still work after I=
 have been away for a week</p><p class=3DMsoNormal>&gt;=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 4) If vendors want to be selling all that Io=
T gear, they have to</p><p class=3DMsoNormal>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0 solve</p><p class=3DMsoNormal>&gt;=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 these issues.</p><p class=3DMsoNormal>&gt=
; </p><p class=3DMsoNormal>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0 5) I want someone to blame. Right now when the network doesn't</p><p=
 class=3DMsoNormal>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 wor=
k, I</p><p class=3DMsoNormal>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0 don't know who is the cause. I want one point of contact. Whoever is=
</p><p class=3DMsoNormal>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0 that point of contact will get most of my networking money.</p><p class=
=3DMsoNormal>&gt; </p><p class=3DMsoNormal>&gt; </p><p class=3DMsoNormal>&g=
t;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 One of the biggest heada=
ches in debugging is that 'smart hubs' are</p><p class=3DMsoNormal>&gt;=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 not. They are actually very s=
tupid. They make assumptions of network</p><p class=3DMsoNormal>&gt;=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 topology that are not true. Anot=
her is the unfortunate</p><p class=3DMsoNormal>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0 implementation</p><p class=3DMsoNormal>&gt;=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 of DHCP.</p><p class=3DMsoNormal=
>&gt; </p><p class=3DMsoNormal>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0 I don't use SNMP for a simple reason - it is not available to mos=
t</p><p class=3DMsoNormal>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0 ordinary people. I want to understand networking for the 99%,</p><p cla=
ss=3DMsoNormal>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 not the=
</p><p class=3DMsoNormal>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0 IETF 1%-ers.</p><p class=3DMsoNormal>&gt; </p><p class=3DMsoNormal>&gt;=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 All this networking gear i=
s presented to me as black boxes over</p><p class=3DMsoNormal>&gt;=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 which</p><p class=3DMsoNormal>&gt;=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 I have absolutely no contr=
ol (which is fine-ish) and no visibility.</p><p class=3DMsoNormal>&gt; </p>=
<p class=3DMsoNormal>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 W=
hat we have today is the product of a historical process. I</p><p class=3DM=
soNormal>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 remember</p><=
p class=3DMsoNormal>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 th=
e days when Ethernet ran on 10BaseT. But I installed my first</p><p class=
=3DMsoNormal>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 switch</p=
><p class=3DMsoNormal>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 =
30 years ago and it has been a switched protocol for 20 years now.</p><p cl=
ass=3DMsoNormal>&gt; </p><p class=3DMsoNormal>&gt; </p><p class=3DMsoNormal=
>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 It seems to me that t=
here is a business opportunity for any</p><p class=3DMsoNormal>&gt;=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 vendor who</p><p class=3DMsoNorm=
al>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 takes the rather ob=
vious step of simplifying the system.</p><p class=3DMsoNormal>&gt; </p><p c=
lass=3DMsoNormal>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Peopl=
e talk about 'IP everywhere' and 'IP end-to-end' which is</p><p class=3DMso=
Normal>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 rather</p><p cl=
ass=3DMsoNormal>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 odd wh=
en you think about the fact that virtually every local network</p><p class=
=3DMsoNormal>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 uses MAC =
addresses for routing.</p><p class=3DMsoNormal>&gt; </p><p class=3DMsoNorma=
l>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 One of the reasons t=
hat IP won against OSI was that it was simpler.</p><p class=3DMsoNormal>&gt=
;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Applications ran on top o=
f the IP layer with only TCP inbetween. Of</p><p class=3DMsoNormal>&gt;=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 course these days we do have =
a Presentation layer, Web Services</p><p class=3DMsoNormal>&gt;=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 run on</p><p class=3DMsoNormal>&gt;=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 HTTP. But unlike the OSI pres=
entation layer, ours does not introduce</p><p class=3DMsoNormal>&gt;=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 =C2=A0=C2=A0extra moving parts.</p><p class=
=3DMsoNormal>&gt; </p><p class=3DMsoNormal>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0 It seems to me that if we really believed in IP every=
where and IP</p><p class=3DMsoNormal>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0 end-to-end we would insist that network switches be IP rout=
ers that</p><p class=3DMsoNormal>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0 can be managed using BGP/OSPF or at least routing tables rathe=
r than</p><p class=3DMsoNormal>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0 heuristic devices that try to guess where packets should go based=
 on</p><p class=3DMsoNormal>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0 goat entrails, phases of the moon or whatever they use.</p><p class=
=3DMsoNormal>&gt; </p><p class=3DMsoNormal>&gt; </p><p class=3DMsoNormal>&g=
t;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 What should have happene=
d many moons ago was that DHCP should have</p><p class=3DMsoNormal>&gt;=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 become a bidirectional protoc=
ol or a bootstrap to a bidirectional</p><p class=3DMsoNormal>&gt;=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 protocol. So when a printer joins t=
he network, it authenticates and</p><p class=3DMsoNormal>&gt;=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 tells the network what it is. And this=
 is all defined in one set of</p><p class=3DMsoNormal>&gt;=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 specifications from one organization, non=
e of which assumes that</p><p class=3DMsoNormal>&gt;=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0 security is an 'advanced', 'optional' or 'enter=
prise' feature.</p><p class=3DMsoNormal>&gt; </p><p class=3DMsoNormal>&gt;=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Instead we have an ad-hoc =
layer trying to achieve the same result in</p><p class=3DMsoNormal>&gt;=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 peer-to-peer fashion. A simil=
ar approach works for frogs as a</p><p class=3DMsoNormal>&gt;=C2=A0=C2=A0 =
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0reproductive mechanism but only at the =
species level. It certainly</p><p class=3DMsoNormal>&gt;=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 does not work for the individual ova which m=
ay or may not connect to</p><p class=3DMsoNormal>&gt;=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0 the printer it is trying to use to print the ki=
ds damned homework.</p><p class=3DMsoNormal>&gt; </p><p class=3DMsoNormal>&=
gt; </p><p class=3DMsoNormal>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0 Seriously, the fact that things have scaled thus far and the 1% can<=
/p><p class=3DMsoNormal>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0 get them to work does not mean that we can get to the next level</p><p =
class=3DMsoNormal>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 with=
out a serious rethink of the local network architecture.</p><p class=3DMsoN=
ormal>&gt; </p><p class=3DMsoNormal>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0 The type of device I think we need would be first and forem=
ost an IP</p><p class=3DMsoNormal>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0 router. It would have ethernet plugs on the box and use ethern=
et</p><p class=3DMsoNormal>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0 layer</p><p class=3DMsoNormal>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0 1 specs. But when a another 'True-IP' device was plugged in=
, it</p><p class=3DMsoNormal>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0 would</p><p class=3DMsoNormal>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0 quickly negotiate a direct IP connection, oh and with prope=
r 64KB</p><p class=3DMsoNormal>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0 packets. It would also, authenticate, announce and turn on link</=
p><p class=3DMsoNormal>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
 layer</p><p class=3DMsoNormal>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0 encryption.</p><p class=3DMsoNormal>&gt; </p><p class=3DMsoNormal=
>&gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Such a device would a=
lso be a legacy router. It would fake all the</p><p class=3DMsoNormal>&gt;=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 signals necessary for a le=
gacy ethernet device to function. It would</p><p class=3DMsoNormal>&gt;=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 also be responsible for maint=
aining the local information for the</p><p class=3DMsoNormal>&gt;=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 network service database and interc=
ommunicating with other hubs to</p><p class=3DMsoNormal>&gt;=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 achieve a global network view.</p><p clas=
s=3DMsoNormal>&gt; </p><p class=3DMsoNormal>&gt; </p><p class=3DMsoNormal>&=
gt;=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 The net result of all t=
his would be that I would never ever need to</p><p class=3DMsoNormal>&gt;=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 install another printer (n=
o, it is not actually necessary for every</p><p class=3DMsoNormal>&gt;=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 stupid printer to have its ow=
n stupid printer driver). Opening the</p><p class=3DMsoNormal>&gt;=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 'printers' folder would automatical=
ly show every printer that is on</p><p class=3DMsoNormal>&gt;=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 the network or can be woken from slumb=
er by the hub it connects to.</p><p class=3DMsoNormal>&gt; </p><p class=3DM=
soNormal>&gt; </p><p class=3DMsoNormal>&gt; </p><p class=3DMsoNormal><o:p>&=
nbsp;</o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNorm=
al><o:p>&nbsp;</o:p></p></div></body></html>=

--_A3734A22-007D-4A0C-8D66-83BDED9F63E1_--


From nobody Thu Apr 14 21:53:14 2016
Return-Path: <narten@us.ibm.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 D53D312E5A7 for <ietf@ietfa.amsl.com>; Thu, 14 Apr 2016 21:53:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.917
X-Spam-Level: 
X-Spam-Status: No, score=-7.917 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.996, SPF_PASS=-0.001] 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 qtuI1UG7Jf5X for <ietf@ietfa.amsl.com>; Thu, 14 Apr 2016 21:53:10 -0700 (PDT)
Received: from e32.co.us.ibm.com (e32.co.us.ibm.com [32.97.110.150]) (using TLSv1.2 with cipher CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D36B112E59D for <ietf@ietf.org>; Thu, 14 Apr 2016 21:53:09 -0700 (PDT)
Received: from localhost by e32.co.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for <ietf@ietf.org> from <narten@us.ibm.com>; Thu, 14 Apr 2016 22:53:08 -0600
Received: from d03dlp01.boulder.ibm.com (9.17.202.177) by e32.co.us.ibm.com (192.168.1.132) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Thu, 14 Apr 2016 22:53:05 -0600
X-IBM-Helo: d03dlp01.boulder.ibm.com
X-IBM-MailFrom: narten@us.ibm.com
X-IBM-RcptTo: ietf@ietf.org
Received: from b01cxnp22035.gho.pok.ibm.com (b01cxnp22035.gho.pok.ibm.com [9.57.198.25]) by d03dlp01.boulder.ibm.com (Postfix) with ESMTP id AB4AD1FF004A for <ietf@ietf.org>; Thu, 14 Apr 2016 22:41:13 -0600 (MDT)
Received: from b01ledav03.gho.pok.ibm.com (b01ledav003.gho.pok.ibm.com [9.57.199.108]) by b01cxnp22035.gho.pok.ibm.com (8.14.9/8.14.9/NCO v10.0) with ESMTP id u3F4r4sp32243930 for <ietf@ietf.org>; Fri, 15 Apr 2016 04:53:04 GMT
Received: from b01ledav03.gho.pok.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 3D89AB204D for <ietf@ietf.org>; Fri, 15 Apr 2016 05:51:47 -0400 (EDT)
Received: from rotala.raleigh.ibm.com (unknown [9.27.222.27]) by b01ledav03.gho.pok.ibm.com (Postfix) with ESMTPS id 0C1C7B2046 for <ietf@ietf.org>; Fri, 15 Apr 2016 05:51:46 -0400 (EDT)
Received: from rotala.raleigh.ibm.com (localhost [127.0.0.1]) by rotala.raleigh.ibm.com (8.15.2/8.12.5) with ESMTP id u3F4r3iP014169 for <ietf@ietf.org>; Fri, 15 Apr 2016 00:53:03 -0400
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.15.2/8.15.2/Submit) id u3F4r2g6014109 for ietf@ietf.org; Fri, 15 Apr 2016 00:53:02 -0400
From: narten@us.ibm.com
Message-Id: <201604150453.u3F4r2g6014109@rotala.raleigh.ibm.com>
Date: Fri, 15 Apr 2016 00:53:02 -0400
To: ietf@ietf.org
Subject: Weekly posting summary for ietf@ietf.org
User-Agent: Heirloom mailx 12.5 7/5/10
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-TM-AS-GCONF: 00
X-Content-Scanned: Fidelis XPS MAILER
x-cbid: 16041504-0005-0000-0000-0000271F5495
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/vcEI-MWvsUDfnLrqrNP8krS2FxI>
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: Fri, 15 Apr 2016 04:53:13 -0000

Total of 260 messages in the last 7 days.
 
script run at: Fri Apr 15 00:53:02 EDT 2016
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
  8.46% |   22 | 12.27% |   303502 | mellon@fugue.com
  4.62% |   12 |  4.28% |   105808 | brian.e.carpenter@gmail.com
  4.62% |   12 |  3.59% |    88706 | olejacobsen@me.com
  4.23% |   11 |  3.81% |    94281 | john-ietf@jck.com
  3.85% |   10 |  3.62% |    89616 | ynir.ietf@gmail.com
  3.85% |   10 |  3.52% |    86955 | chopps@chopps.org
  3.85% |   10 |  3.30% |    81539 | melinda.shore@gmail.com
  2.69% |    7 |  3.18% |    78664 | tjc@ecs.soton.ac.uk
  2.69% |    7 |  3.10% |    76626 | aallen@blackberry.com
  2.31% |    6 |  3.42% |    84616 | stephen.farrell@cs.tcd.ie
  3.08% |    8 |  2.31% |    57038 | mcr+ietf@sandelman.ca
  3.08% |    8 |  1.92% |    47398 | randy@psg.com
  2.31% |    6 |  1.57% |    38815 | rsk@gsp.org
  1.92% |    5 |  1.80% |    44534 | phill@hallambaker.com
  1.54% |    4 |  1.96% |    48465 | theodore.v.faber@aero.org
  1.54% |    4 |  1.80% |    44515 | jmh@joelhalpern.com
  1.92% |    5 |  1.37% |    33904 | dhc@dcrocker.net
  1.54% |    4 |  1.42% |    35139 | superuser@gmail.com
  1.15% |    3 |  1.75% |    43221 | rpelletier@isoc.org
  1.54% |    4 |  1.35% |    33366 | mstjohns@comcast.net
  1.15% |    3 |  1.46% |    36191 | tony@att.com
  1.15% |    3 |  1.33% |    32951 | spencerdawkins.ietf@gmail.com
  1.15% |    3 |  1.13% |    27844 | nalini.elkins@insidethestack.com
  1.15% |    3 |  1.10% |    27102 | alissa@cooperw.in
  0.77% |    2 |  1.46% |    36128 | akatlas@gmail.com
  1.15% |    3 |  1.02% |    25239 | harald@alvestrand.no
  1.15% |    3 |  0.99% |    24574 | stewart.bryant@gmail.com
  1.15% |    3 |  0.92% |    22716 | loa@pi.nu
  1.15% |    3 |  0.91% |    22473 | harish.pillay@gmail.com
  1.15% |    3 |  0.86% |    21289 | sm@resistor.net
  1.15% |    3 |  0.80% |    19876 | jared@puck.nether.net
  0.77% |    2 |  1.04% |    25649 | mary.h.barnes@gmail.com
  0.77% |    2 |  0.97% |    24012 | robert.w.withers@gmail.com
  0.77% |    2 |  0.81% |    20157 | fred@cisco.com
  0.77% |    2 |  0.81% |    19931 | carlosm3011@gmail.com
  0.77% |    2 |  0.78% |    19383 | morrowc.lists@gmail.com
  0.38% |    1 |  1.11% |    27399 | chaitanyabd@gmail.com
  0.77% |    2 |  0.68% |    16781 | michael.cameron@ericsson.com
  0.38% |    1 |  1.06% |    26105 | andy@yumaworks.com
  0.77% |    2 |  0.63% |    15678 | mfidelman@meetinghouse.net
  0.77% |    2 |  0.63% |    15512 | sob@sobco.com
  0.77% |    2 |  0.61% |    15116 | leifj@mnt.se
  0.77% |    2 |  0.61% |    15059 | richard@shockey.us
  0.77% |    2 |  0.58% |    14323 | swmike@swm.pp.se
  0.77% |    2 |  0.54% |    13422 | paf@frobbit.se
  0.77% |    2 |  0.51% |    12555 | johnl@taugh.com
  0.77% |    2 |  0.49% |    12001 | jhaas@pfrc.org
  0.38% |    1 |  0.85% |    20924 | dactechng@gmail.com
  0.38% |    1 |  0.70% |    17291 | dhruv.ietf@gmail.com
  0.38% |    1 |  0.58% |    14233 | presnick@qti.qualcomm.com
  0.38% |    1 |  0.55% |    13573 | daedulus@btconnect.com
  0.38% |    1 |  0.51% |    12602 | stefan.winter@restena.lu
  0.38% |    1 |  0.49% |    12173 | farmer@umn.edu
  0.38% |    1 |  0.46% |    11357 | ron.even.tlv@gmail.com
  0.38% |    1 |  0.45% |    11036 | dimitri.staessens@intec.ugent.be
  0.38% |    1 |  0.43% |    10619 | narten@us.ibm.com
  0.38% |    1 |  0.41% |    10174 | cpignata@cisco.com
  0.38% |    1 |  0.40% |     9991 | sean@sn3rd.com
  0.38% |    1 |  0.40% |     9970 | stewe@stewe.org
  0.38% |    1 |  0.40% |     9955 | eckert@cisco.com
  0.38% |    1 |  0.40% |     9818 | andrew.hutton@unify.com
  0.38% |    1 |  0.39% |     9593 | warren@kumari.net
  0.38% |    1 |  0.38% |     9424 | jordi.palet@consulintel.es
  0.38% |    1 |  0.37% |     9162 | anne-marie.eklund-lowinder@iis.se
  0.38% |    1 |  0.36% |     8857 | john@jlc.net
  0.38% |    1 |  0.36% |     8787 | joelja@bogus.com
  0.38% |    1 |  0.35% |     8718 | lloyd.wood@yahoo.co.uk
  0.38% |    1 |  0.34% |     8439 | vinayakh@gmail.com
  0.38% |    1 |  0.34% |     8381 | jari.arkko@piuha.net
  0.38% |    1 |  0.33% |     8243 | ggm@algebras.org
  0.38% |    1 |  0.32% |     7990 | lee@asgard.org
  0.38% |    1 |  0.30% |     7474 | llynch@civil-tongue.net
  0.38% |    1 |  0.30% |     7429 | samita.chakrabarti@ericsson.com
  0.38% |    1 |  0.30% |     7406 | gjshep@gmail.com
  0.38% |    1 |  0.30% |     7345 | lhotka@nic.cz
  0.38% |    1 |  0.29% |     7162 | charles.perkins@earthlink.net
  0.38% |    1 |  0.29% |     7154 | marka@isc.org
  0.38% |    1 |  0.27% |     6723 | dirkx@webweaving.org
  0.38% |    1 |  0.27% |     6648 | dwm@xpasc.com
  0.38% |    1 |  0.27% |     6637 | paul@nohats.ca
  0.38% |    1 |  0.26% |     6509 | mrex@sap.com
  0.38% |    1 |  0.26% |     6433 | dot@dotat.at
  0.38% |    1 |  0.26% |     6340 | jgs@bgp.nu
  0.38% |    1 |  0.26% |     6308 | mcr@sandelman.ca
  0.38% |    1 |  0.23% |     5781 | fgont@si6networks.com
  0.38% |    1 |  0.22% |     5422 | bertietf@bwijnen.net
  0.38% |    1 |  0.21% |     5280 | paul.hoffman@vpnc.org
--------+------+--------+----------+------------------------
100.00% |  260 |100.00% |  2473535 | Total


From nobody Thu Apr 14 23:36:55 2016
Return-Path: <dimitri.staessens@intec.ugent.be>
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 9BF9112E060 for <ietf@ietfa.amsl.com>; Thu, 14 Apr 2016 23:36:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.215
X-Spam-Level: 
X-Spam-Status: No, score=-5.215 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.996] 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 EYyy72IQvLX5 for <ietf@ietfa.amsl.com>; Thu, 14 Apr 2016 23:36:51 -0700 (PDT)
Received: from smtp2.ugent.be (smtp2.ugent.be [157.193.49.126]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 30AFE12E05D for <ietf@ietf.org>; Thu, 14 Apr 2016 23:36:51 -0700 (PDT)
Received: from localhost (mcheck2.ugent.be [157.193.49.249]) by smtp2.ugent.be (Postfix) with ESMTP id 4AC2012C26F; Fri, 15 Apr 2016 08:36:49 +0200 (CEST)
X-Virus-Scanned: by UGent DICT
Received: from smtp2.ugent.be ([IPv6:::ffff:157.193.49.126]) by localhost (mcheck2.UGent.be [::ffff:157.193.43.11]) (amavisd-new, port 10024) with ESMTP id heeHEWJ5XJYw; Fri, 15 Apr 2016 08:36:48 +0200 (CEST)
Received: from mail2.intec.ugent.be (mail2.intec.ugent.be [157.193.214.245]) by smtp2.ugent.be (Postfix) with ESMTP id 79BDF12C26C; Fri, 15 Apr 2016 08:36:48 +0200 (CEST)
Received: from localhost (localhost [127.0.0.1]) by mail2.intec.ugent.be (Postfix) with ESMTP id 67E3F2D; Fri, 15 Apr 2016 08:36:48 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at intec.ugent.be
Received: from mail2.intec.ugent.be ([127.0.0.1]) by localhost (mail2.intec.ugent.be [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DDCN0_TluwK2; Fri, 15 Apr 2016 08:36:48 +0200 (CEST)
Received: from [192.168.66.170] (78-22-161-144.access.telenet.be [78.22.161.144]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: dstaesse) by mail2.intec.ugent.be (Postfix) with ESMTPSA id 9F8552C; Fri, 15 Apr 2016 08:36:47 +0200 (CEST)
Subject: Re: Time to kill layer 2
To: Chaitanya D <chaitanyabd@gmail.com>, "Carlos M. Martinez" <carlosm3011@gmail.com>, Ted Lemon <mellon@fugue.com>
References: <CAMm+Lwg-HTYCv2pGt=SP2+Xjoko6GcJ73kVzqXC1LBTOMDKV_A@mail.gmail.com> <571011B2.9080003@intec.ugent.be> <CAPt1N1m71Vx6LX-dTuHVoYfZG_X7wykax2QMteqFjcsRt+RThw@mail.gmail.com> <57105657.80006@gmail.com> <5710604a.4d40620a.1fffb.ffffd647@mx.google.com>
From: Dimitri Staessens <dimitri.staessens@intec.ugent.be>
Message-ID: <57108BF3.4030608@intec.ugent.be>
Date: Fri, 15 Apr 2016 08:36:35 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2
MIME-Version: 1.0
In-Reply-To: <5710604a.4d40620a.1fffb.ffffd647@mx.google.com>
Content-Type: multipart/alternative; boundary="------------060905080202050803090502"
X-Miltered: at jchkm3 with ID 57108C00.000 by Joe's j-chkmail (http://helpdesk.ugent.be/email/)!
X-j-chkmail-Enveloppe: 57108C00.000 from mail2.intec.ugent.be/mail2.intec.ugent.be/157.193.214.245/mail2.intec.ugent.be/<dimitri.staessens@intec.ugent.be>
X-j-chkmail-Score: MSGID : 57108C00.000 on smtp2.ugent.be : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Status: Ham
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/v4OSkN5KkjJ0E4Z3KyqpN2MZ4f0>
Cc: ietf <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: Fri, 15 Apr 2016 06:36:54 -0000

This is a multi-part message in MIME format.
--------------060905080202050803090502
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit

If you killed the user, Layer 3 would stop working...

On 04/15/16 05:30, Chaitanya D wrote:
>
> The BOFH way - kill the user and let the network be.... ;)
>
> Kidding of course
>
>
> *From: *Carlos M. Martinez
> *Sent: *15 April 2016 08:18
> *To: *Ted Lemon;Dimitri Staessens
> *Cc: *ietf
> *Subject: *Re: Time to kill layer 2
>
> All the way up to the user ? Many times.
>
> On 4/14/16 6:56 PM, Ted Lemon wrote:
>
> > Of course!
>
> >
>
> > On Thu, Apr 14, 2016 at 5:54 PM, Dimitri Staessens
>
> > <dimitri.staessens@intec.ugent.be
>
> > <mailto:dimitri.staessens@intec.ugent.be>> wrote:
>
> >
>
> >     anyone thought of killing everything on top of layer 2?
>
> >
>
> >
>
> >     On 04/14/16 14:59, Phillip Hallam-Baker wrote:
>
> >
>
> >         This morning I spent an hour debugging the network to print 
> out two
>
> >         class projects that were due. Some points:
>
> >
>
> >         1) My ability to debug the network is better than 99% of the
>
> >         population
>
> >         2) The interaction of Bonjour, DHCP and auto power saving is
>
> >         unfortunate
>
> >         3) Things should still work after I have been away for a week
>
> >         4) If vendors want to be selling all that IoT gear, they have to
>
> >         solve
>
> >         these issues.
>
> >
>
> >         5) I want someone to blame. Right now when the network doesn't
>
> >         work, I
>
> >         don't know who is the cause. I want one point of contact. 
> Whoever is
>
> >         that point of contact will get most of my networking money.
>
> >
>
> >
>
> >         One of the biggest headaches in debugging is that 'smart 
> hubs' are
>
> >         not. They are actually very stupid. They make assumptions of 
> network
>
> >         topology that are not true. Another is the unfortunate
>
> >         implementation
>
> >         of DHCP.
>
> >
>
> >         I don't use SNMP for a simple reason - it is not available 
> to most
>
> >         ordinary people. I want to understand networking for the 99%,
>
> >         not the
>
> >         IETF 1%-ers.
>
> >
>
> >         All this networking gear is presented to me as black boxes over
>
> >         which
>
> >         I have absolutely no control (which is fine-ish) and no 
> visibility.
>
> >
>
> >         What we have today is the product of a historical process. I
>
> >         remember
>
> >         the days when Ethernet ran on 10BaseT. But I installed my first
>
> >         switch
>
> >         30 years ago and it has been a switched protocol for 20 
> years now.
>
> >
>
> >
>
> >         It seems to me that there is a business opportunity for any
>
> >         vendor who
>
> >         takes the rather obvious step of simplifying the system.
>
> >
>
> >         People talk about 'IP everywhere' and 'IP end-to-end' which is
>
> >         rather
>
> >         odd when you think about the fact that virtually every local 
> network
>
> >         uses MAC addresses for routing.
>
> >
>
> >         One of the reasons that IP won against OSI was that it was 
> simpler.
>
> >         Applications ran on top of the IP layer with only TCP 
> inbetween. Of
>
> >         course these days we do have a Presentation layer, Web Services
>
> >         run on
>
> >         HTTP. But unlike the OSI presentation layer, ours does not 
> introduce
>
> >         extra moving parts.
>
> >
>
> >         It seems to me that if we really believed in IP everywhere 
> and IP
>
> >         end-to-end we would insist that network switches be IP 
> routers that
>
> >         can be managed using BGP/OSPF or at least routing tables 
> rather than
>
> >         heuristic devices that try to guess where packets should go 
> based on
>
> >         goat entrails, phases of the moon or whatever they use.
>
> >
>
> >
>
> >         What should have happened many moons ago was that DHCP 
> should have
>
> >         become a bidirectional protocol or a bootstrap to a 
> bidirectional
>
> >         protocol. So when a printer joins the network, it 
> authenticates and
>
> >         tells the network what it is. And this is all defined in one 
> set of
>
> >         specifications from one organization, none of which assumes that
>
> >         security is an 'advanced', 'optional' or 'enterprise' feature.
>
> >
>
> >         Instead we have an ad-hoc layer trying to achieve the same 
> result in
>
> >         peer-to-peer fashion. A similar approach works for frogs as a
>
> >         reproductive mechanism but only at the species level. It 
> certainly
>
> >         does not work for the individual ova which may or may not 
> connect to
>
> >         the printer it is trying to use to print the kids damned 
> homework.
>
> >
>
> >
>
> >         Seriously, the fact that things have scaled thus far and the 
> 1% can
>
> >         get them to work does not mean that we can get to the next level
>
> >         without a serious rethink of the local network architecture.
>
> >
>
> >         The type of device I think we need would be first and 
> foremost an IP
>
> >         router. It would have ethernet plugs on the box and use ethernet
>
> >         layer
>
> >         1 specs. But when a another 'True-IP' device was plugged in, it
>
> >         would
>
> >         quickly negotiate a direct IP connection, oh and with proper 
> 64KB
>
> >         packets. It would also, authenticate, announce and turn on link
>
> >         layer
>
> >         encryption.
>
> >
>
> >         Such a device would also be a legacy router. It would fake 
> all the
>
> >         signals necessary for a legacy ethernet device to function. 
> It would
>
> >         also be responsible for maintaining the local information 
> for the
>
> >         network service database and intercommunicating with other 
> hubs to
>
> >         achieve a global network view.
>
> >
>
> >
>
> >         The net result of all this would be that I would never ever 
> need to
>
> >         install another printer (no, it is not actually necessary 
> for every
>
> >         stupid printer to have its own stupid printer driver). 
> Opening the
>
> >         'printers' folder would automatically show every printer 
> that is on
>
> >         the network or can be woken from slumber by the hub it 
> connects to.
>
> >
>
> >
>
> >
>


--------------060905080202050803090502
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta content="text/html; charset=windows-1252"
      http-equiv="Content-Type">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    If you killed the user, Layer 3 would stop working...<br>
    <br>
    <div class="moz-cite-prefix">On 04/15/16 05:30, Chaitanya D wrote:<br>
    </div>
    <blockquote
      cite="mid:5710604a.4d40620a.1fffb.ffffd647@mx.google.com"
      type="cite">
      <meta http-equiv="Content-Type" content="text/html;
        charset=windows-1252">
      <meta name="Generator" content="Microsoft Word 15 (filtered
        medium)">
      <style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;}
p
	{mso-style-priority:99;
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
.MsoChpDefault
	{mso-style-type:export-only;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style>
      <div class="WordSection1">
        <p>The BOFH way - kill the user and let the network be.... ;)</p>
        <p><o:p> </o:p></p>
        <p>Kidding of course</p>
        <p><o:p> </o:p></p>
        <p><o:p> </o:p></p>
        <div
          style="mso-element:para-border-div;border:none;border-top:solid
          #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
          <p style="border:none;padding:0cm"><br>
            <b>From: </b>Carlos M. Martinez<br>
            <b>Sent: </b>15 April 2016 08:18<br>
            <b>To: </b>Ted Lemon;Dimitri Staessens<br>
            <b>Cc: </b>ietf<br>
            <b>Subject: </b>Re: Time to kill layer 2</p>
        </div>
        <p class="MsoNormal"><o:p> </o:p></p>
        <p class="MsoNormal"><span style="font-family:&quot;Times New
            Roman&quot;,serif"><o:p> </o:p></span></p>
        <p class="MsoNormal">All the way up to the user ? Many times.</p>
        <p class="MsoNormal"><o:p> </o:p></p>
        <p class="MsoNormal">On 4/14/16 6:56 PM, Ted Lemon wrote:</p>
        <p class="MsoNormal">&gt; Of course!</p>
        <p class="MsoNormal">&gt; </p>
        <p class="MsoNormal">&gt; On Thu, Apr 14, 2016 at 5:54 PM,
          Dimitri Staessens</p>
        <p class="MsoNormal">&gt; &lt;<a class="moz-txt-link-abbreviated" href="mailto:dimitri.staessens@intec.ugent.be">dimitri.staessens@intec.ugent.be</a></p>
        <p class="MsoNormal">&gt;
          <a class="moz-txt-link-rfc2396E" href="mailto:dimitri.staessens@intec.ugent.be">&lt;mailto:dimitri.staessens@intec.ugent.be&gt;</a>&gt; wrote:</p>
        <p class="MsoNormal">&gt; </p>
        <p class="MsoNormal">&gt;     anyone thought of killing
          everything on top of layer 2?</p>
        <p class="MsoNormal">&gt; </p>
        <p class="MsoNormal">&gt; </p>
        <p class="MsoNormal">&gt;     On 04/14/16 14:59, Phillip
          Hallam-Baker wrote:</p>
        <p class="MsoNormal">&gt; </p>
        <p class="MsoNormal">&gt;         This morning I spent an hour
          debugging the network to print out two</p>
        <p class="MsoNormal">&gt;         class projects that were due.
          Some points:</p>
        <p class="MsoNormal">&gt; </p>
        <p class="MsoNormal">&gt;         1) My ability to debug the
          network is better than 99% of the</p>
        <p class="MsoNormal">&gt;         population</p>
        <p class="MsoNormal">&gt;         2) The interaction of Bonjour,
          DHCP and auto power saving is</p>
        <p class="MsoNormal">&gt;         unfortunate</p>
        <p class="MsoNormal">&gt;         3) Things should still work
          after I have been away for a week</p>
        <p class="MsoNormal">&gt;         4) If vendors want to be
          selling all that IoT gear, they have to</p>
        <p class="MsoNormal">&gt;         solve</p>
        <p class="MsoNormal">&gt;         these issues.</p>
        <p class="MsoNormal">&gt; </p>
        <p class="MsoNormal">&gt;         5) I want someone to blame.
          Right now when the network doesn't</p>
        <p class="MsoNormal">&gt;         work, I</p>
        <p class="MsoNormal">&gt;         don't know who is the cause. I
          want one point of contact. Whoever is</p>
        <p class="MsoNormal">&gt;         that point of contact will get
          most of my networking money.</p>
        <p class="MsoNormal">&gt; </p>
        <p class="MsoNormal">&gt; </p>
        <p class="MsoNormal">&gt;         One of the biggest headaches
          in debugging is that 'smart hubs' are</p>
        <p class="MsoNormal">&gt;         not. They are actually very
          stupid. They make assumptions of network</p>
        <p class="MsoNormal">&gt;         topology that are not true.
          Another is the unfortunate</p>
        <p class="MsoNormal">&gt;         implementation</p>
        <p class="MsoNormal">&gt;         of DHCP.</p>
        <p class="MsoNormal">&gt; </p>
        <p class="MsoNormal">&gt;         I don't use SNMP for a simple
          reason - it is not available to most</p>
        <p class="MsoNormal">&gt;         ordinary people. I want to
          understand networking for the 99%,</p>
        <p class="MsoNormal">&gt;         not the</p>
        <p class="MsoNormal">&gt;         IETF 1%-ers.</p>
        <p class="MsoNormal">&gt; </p>
        <p class="MsoNormal">&gt;         All this networking gear is
          presented to me as black boxes over</p>
        <p class="MsoNormal">&gt;         which</p>
        <p class="MsoNormal">&gt;         I have absolutely no control
          (which is fine-ish) and no visibility.</p>
        <p class="MsoNormal">&gt; </p>
        <p class="MsoNormal">&gt;         What we have today is the
          product of a historical process. I</p>
        <p class="MsoNormal">&gt;         remember</p>
        <p class="MsoNormal">&gt;         the days when Ethernet ran on
          10BaseT. But I installed my first</p>
        <p class="MsoNormal">&gt;         switch</p>
        <p class="MsoNormal">&gt;         30 years ago and it has been a
          switched protocol for 20 years now.</p>
        <p class="MsoNormal">&gt; </p>
        <p class="MsoNormal">&gt; </p>
        <p class="MsoNormal">&gt;         It seems to me that there is a
          business opportunity for any</p>
        <p class="MsoNormal">&gt;         vendor who</p>
        <p class="MsoNormal">&gt;         takes the rather obvious step
          of simplifying the system.</p>
        <p class="MsoNormal">&gt; </p>
        <p class="MsoNormal">&gt;         People talk about 'IP
          everywhere' and 'IP end-to-end' which is</p>
        <p class="MsoNormal">&gt;         rather</p>
        <p class="MsoNormal">&gt;         odd when you think about the
          fact that virtually every local network</p>
        <p class="MsoNormal">&gt;         uses MAC addresses for
          routing.</p>
        <p class="MsoNormal">&gt; </p>
        <p class="MsoNormal">&gt;         One of the reasons that IP won
          against OSI was that it was simpler.</p>
        <p class="MsoNormal">&gt;         Applications ran on top of the
          IP layer with only TCP inbetween. Of</p>
        <p class="MsoNormal">&gt;         course these days we do have a
          Presentation layer, Web Services</p>
        <p class="MsoNormal">&gt;         run on</p>
        <p class="MsoNormal">&gt;         HTTP. But unlike the OSI
          presentation layer, ours does not introduce</p>
        <p class="MsoNormal">&gt;         extra moving parts.</p>
        <p class="MsoNormal">&gt; </p>
        <p class="MsoNormal">&gt;         It seems to me that if we
          really believed in IP everywhere and IP</p>
        <p class="MsoNormal">&gt;         end-to-end we would insist
          that network switches be IP routers that</p>
        <p class="MsoNormal">&gt;         can be managed using BGP/OSPF
          or at least routing tables rather than</p>
        <p class="MsoNormal">&gt;         heuristic devices that try to
          guess where packets should go based on</p>
        <p class="MsoNormal">&gt;         goat entrails, phases of the
          moon or whatever they use.</p>
        <p class="MsoNormal">&gt; </p>
        <p class="MsoNormal">&gt; </p>
        <p class="MsoNormal">&gt;         What should have happened many
          moons ago was that DHCP should have</p>
        <p class="MsoNormal">&gt;         become a bidirectional
          protocol or a bootstrap to a bidirectional</p>
        <p class="MsoNormal">&gt;         protocol. So when a printer
          joins the network, it authenticates and</p>
        <p class="MsoNormal">&gt;         tells the network what it is.
          And this is all defined in one set of</p>
        <p class="MsoNormal">&gt;         specifications from one
          organization, none of which assumes that</p>
        <p class="MsoNormal">&gt;         security is an 'advanced',
          'optional' or 'enterprise' feature.</p>
        <p class="MsoNormal">&gt; </p>
        <p class="MsoNormal">&gt;         Instead we have an ad-hoc
          layer trying to achieve the same result in</p>
        <p class="MsoNormal">&gt;         peer-to-peer fashion. A
          similar approach works for frogs as a</p>
        <p class="MsoNormal">&gt;         reproductive mechanism but
          only at the species level. It certainly</p>
        <p class="MsoNormal">&gt;         does not work for the
          individual ova which may or may not connect to</p>
        <p class="MsoNormal">&gt;         the printer it is trying to
          use to print the kids damned homework.</p>
        <p class="MsoNormal">&gt; </p>
        <p class="MsoNormal">&gt; </p>
        <p class="MsoNormal">&gt;         Seriously, the fact that
          things have scaled thus far and the 1% can</p>
        <p class="MsoNormal">&gt;         get them to work does not mean
          that we can get to the next level</p>
        <p class="MsoNormal">&gt;         without a serious rethink of
          the local network architecture.</p>
        <p class="MsoNormal">&gt; </p>
        <p class="MsoNormal">&gt;         The type of device I think we
          need would be first and foremost an IP</p>
        <p class="MsoNormal">&gt;         router. It would have ethernet
          plugs on the box and use ethernet</p>
        <p class="MsoNormal">&gt;         layer</p>
        <p class="MsoNormal">&gt;         1 specs. But when a another
          'True-IP' device was plugged in, it</p>
        <p class="MsoNormal">&gt;         would</p>
        <p class="MsoNormal">&gt;         quickly negotiate a direct IP
          connection, oh and with proper 64KB</p>
        <p class="MsoNormal">&gt;         packets. It would also,
          authenticate, announce and turn on link</p>
        <p class="MsoNormal">&gt;         layer</p>
        <p class="MsoNormal">&gt;         encryption.</p>
        <p class="MsoNormal">&gt; </p>
        <p class="MsoNormal">&gt;         Such a device would also be a
          legacy router. It would fake all the</p>
        <p class="MsoNormal">&gt;         signals necessary for a legacy
          ethernet device to function. It would</p>
        <p class="MsoNormal">&gt;         also be responsible for
          maintaining the local information for the</p>
        <p class="MsoNormal">&gt;         network service database and
          intercommunicating with other hubs to</p>
        <p class="MsoNormal">&gt;         achieve a global network view.</p>
        <p class="MsoNormal">&gt; </p>
        <p class="MsoNormal">&gt; </p>
        <p class="MsoNormal">&gt;         The net result of all this
          would be that I would never ever need to</p>
        <p class="MsoNormal">&gt;         install another printer (no,
          it is not actually necessary for every</p>
        <p class="MsoNormal">&gt;         stupid printer to have its own
          stupid printer driver). Opening the</p>
        <p class="MsoNormal">&gt;         'printers' folder would
          automatically show every printer that is on</p>
        <p class="MsoNormal">&gt;         the network or can be woken
          from slumber by the hub it connects to.</p>
        <p class="MsoNormal">&gt; </p>
        <p class="MsoNormal">&gt; </p>
        <p class="MsoNormal">&gt; </p>
        <p class="MsoNormal"><o:p> </o:p></p>
        <p class="MsoNormal"><o:p> </o:p></p>
        <p class="MsoNormal"><o:p> </o:p></p>
      </div>
    </blockquote>
    <br>
  </body>
</html>

--------------060905080202050803090502--


From nobody Thu Apr 14 23:55:58 2016
Return-Path: <dimitri.staessens@intec.ugent.be>
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 8720C12DFBE for <ietf@ietfa.amsl.com>; Thu, 14 Apr 2016 23:55:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.215
X-Spam-Level: 
X-Spam-Status: No, score=-5.215 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.996] 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 aVQfpvrxnGjl for <ietf@ietfa.amsl.com>; Thu, 14 Apr 2016 23:55:55 -0700 (PDT)
Received: from smtp2.ugent.be (smtp2.ugent.be [157.193.49.126]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C28B612DF7F for <ietf@ietf.org>; Thu, 14 Apr 2016 23:55:54 -0700 (PDT)
Received: from localhost (mcheck3.ugent.be [157.193.71.89]) by smtp2.ugent.be (Postfix) with ESMTP id 9015212C267 for <ietf@ietf.org>; Fri, 15 Apr 2016 08:55:53 +0200 (CEST)
X-Virus-Scanned: by UGent DICT
Received: from smtp2.ugent.be ([IPv6:::ffff:157.193.49.126]) by localhost (mcheck3.UGent.be [::ffff:157.193.43.11]) (amavisd-new, port 10024) with ESMTP id ixWD16EHv8g2 for <ietf@ietf.org>; Fri, 15 Apr 2016 08:55:52 +0200 (CEST)
Received: from mail2.intec.ugent.be (mail2.intec.ugent.be [157.193.214.245]) by smtp2.ugent.be (Postfix) with ESMTP id 0112212C25D for <ietf@ietf.org>; Fri, 15 Apr 2016 08:55:51 +0200 (CEST)
Received: from localhost (localhost [127.0.0.1]) by mail2.intec.ugent.be (Postfix) with ESMTP id 5D9272D for <ietf@ietf.org>; Fri, 15 Apr 2016 08:55:51 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at intec.ugent.be
Received: from mail2.intec.ugent.be ([127.0.0.1]) by localhost (mail2.intec.ugent.be [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uGDx3AFIPfvu for <ietf@ietf.org>; Fri, 15 Apr 2016 08:55:51 +0200 (CEST)
Received: from [192.168.66.170] (78-22-161-144.access.telenet.be [78.22.161.144]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: dstaesse) by mail2.intec.ugent.be (Postfix) with ESMTPSA id BD7D22C for <ietf@ietf.org>; Fri, 15 Apr 2016 08:55:50 +0200 (CEST)
Subject: Re: Time to kill layer 2
To: ietf@ietf.org
References: <CAMm+Lwg-HTYCv2pGt=SP2+Xjoko6GcJ73kVzqXC1LBTOMDKV_A@mail.gmail.com> <571011B2.9080003@intec.ugent.be> <CAPt1N1m71Vx6LX-dTuHVoYfZG_X7wykax2QMteqFjcsRt+RThw@mail.gmail.com> <57105657.80006@gmail.com> <5710604a.4d40620a.1fffb.ffffd647@mx.google.com> <57108BF3.4030608@intec.ugent.be>
From: Dimitri Staessens <dimitri.staessens@intec.ugent.be>
Message-ID: <5710906A.3050608@intec.ugent.be>
Date: Fri, 15 Apr 2016 08:55:38 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2
MIME-Version: 1.0
In-Reply-To: <57108BF3.4030608@intec.ugent.be>
Content-Type: multipart/alternative; boundary="------------070709050401090503020400"
X-Miltered: at jchkm1 with ID 57109077.000 by Joe's j-chkmail (http://helpdesk.ugent.be/email/)!
X-j-chkmail-Enveloppe: 57109077.000 from mail2.intec.ugent.be/mail2.intec.ugent.be/157.193.214.245/mail2.intec.ugent.be/<dimitri.staessens@intec.ugent.be>
X-j-chkmail-Score: MSGID : 57109077.000 on smtp2.ugent.be : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Status: Ham
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/8XNxqo7n35nS2DLQZc_QYNXs8kQ>
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: Fri, 15 Apr 2016 06:55:57 -0000

This is a multi-part message in MIME format.
--------------070709050401090503020400
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit

Upss. I meant Layer 4 of course ;)

On 04/15/16 08:36, Dimitri Staessens wrote:
> If you killed the user, Layer 3 would stop working...
>
> On 04/15/16 05:30, Chaitanya D wrote:
>>
>> The BOFH way - kill the user and let the network be.... ;)
>>
>> Kidding of course
>>
>>
>> *From: *Carlos M. Martinez
>> *Sent: *15 April 2016 08:18
>> *To: *Ted Lemon;Dimitri Staessens
>> *Cc: *ietf
>> *Subject: *Re: Time to kill layer 2
>>
>> All the way up to the user ? Many times.
>>
>> On 4/14/16 6:56 PM, Ted Lemon wrote:
>>
>> > Of course!
>>
>> >
>>
>> > On Thu, Apr 14, 2016 at 5:54 PM, Dimitri Staessens
>>
>> > <dimitri.staessens@intec.ugent.be
>>
>> > <mailto:dimitri.staessens@intec.ugent.be>> wrote:
>>
>> >
>>
>> >     anyone thought of killing everything on top of layer 2?
>>
>> >
>>
>> >
>>
>> >     On 04/14/16 14:59, Phillip Hallam-Baker wrote:
>>
>> >
>>
>> >         This morning I spent an hour debugging the network to print 
>> out two
>>
>> >         class projects that were due. Some points:
>>
>> >
>>
>> >         1) My ability to debug the network is better than 99% of the
>>
>> >         population
>>
>> >         2) The interaction of Bonjour, DHCP and auto power saving is
>>
>> >         unfortunate
>>
>> >         3) Things should still work after I have been away for a week
>>
>> >         4) If vendors want to be selling all that IoT gear, they 
>> have to
>>
>> >         solve
>>
>> >         these issues.
>>
>> >
>>
>> >         5) I want someone to blame. Right now when the network doesn't
>>
>> >         work, I
>>
>> >         don't know who is the cause. I want one point of contact. 
>> Whoever is
>>
>> >         that point of contact will get most of my networking money.
>>
>> >
>>
>> >
>>
>> >         One of the biggest headaches in debugging is that 'smart 
>> hubs' are
>>
>> >         not. They are actually very stupid. They make assumptions 
>> of network
>>
>> >         topology that are not true. Another is the unfortunate
>>
>> >         implementation
>>
>> >         of DHCP.
>>
>> >
>>
>> >         I don't use SNMP for a simple reason - it is not available 
>> to most
>>
>> >         ordinary people. I want to understand networking for the 99%,
>>
>> >         not the
>>
>> >         IETF 1%-ers.
>>
>> >
>>
>> >         All this networking gear is presented to me as black boxes over
>>
>> >         which
>>
>> >         I have absolutely no control (which is fine-ish) and no 
>> visibility.
>>
>> >
>>
>> >         What we have today is the product of a historical process. I
>>
>> >         remember
>>
>> >         the days when Ethernet ran on 10BaseT. But I installed my first
>>
>> >         switch
>>
>> >         30 years ago and it has been a switched protocol for 20 
>> years now.
>>
>> >
>>
>> >
>>
>> >         It seems to me that there is a business opportunity for any
>>
>> >         vendor who
>>
>> >         takes the rather obvious step of simplifying the system.
>>
>> >
>>
>> >         People talk about 'IP everywhere' and 'IP end-to-end' which is
>>
>> >         rather
>>
>> >         odd when you think about the fact that virtually every 
>> local network
>>
>> >         uses MAC addresses for routing.
>>
>> >
>>
>> >         One of the reasons that IP won against OSI was that it was 
>> simpler.
>>
>> >         Applications ran on top of the IP layer with only TCP 
>> inbetween. Of
>>
>> >         course these days we do have a Presentation layer, Web Services
>>
>> >         run on
>>
>> >         HTTP. But unlike the OSI presentation layer, ours does not 
>> introduce
>>
>> >         extra moving parts.
>>
>> >
>>
>> >         It seems to me that if we really believed in IP everywhere 
>> and IP
>>
>> >         end-to-end we would insist that network switches be IP 
>> routers that
>>
>> >         can be managed using BGP/OSPF or at least routing tables 
>> rather than
>>
>> >         heuristic devices that try to guess where packets should go 
>> based on
>>
>> >         goat entrails, phases of the moon or whatever they use.
>>
>> >
>>
>> >
>>
>> >         What should have happened many moons ago was that DHCP 
>> should have
>>
>> >         become a bidirectional protocol or a bootstrap to a 
>> bidirectional
>>
>> >         protocol. So when a printer joins the network, it 
>> authenticates and
>>
>> >         tells the network what it is. And this is all defined in 
>> one set of
>>
>> >         specifications from one organization, none of which assumes 
>> that
>>
>> >         security is an 'advanced', 'optional' or 'enterprise' feature.
>>
>> >
>>
>> >         Instead we have an ad-hoc layer trying to achieve the same 
>> result in
>>
>> >         peer-to-peer fashion. A similar approach works for frogs as a
>>
>> >         reproductive mechanism but only at the species level. It 
>> certainly
>>
>> >         does not work for the individual ova which may or may not 
>> connect to
>>
>> >         the printer it is trying to use to print the kids damned 
>> homework.
>>
>> >
>>
>> >
>>
>> >         Seriously, the fact that things have scaled thus far and 
>> the 1% can
>>
>> >         get them to work does not mean that we can get to the next 
>> level
>>
>> >         without a serious rethink of the local network architecture.
>>
>> >
>>
>> >         The type of device I think we need would be first and 
>> foremost an IP
>>
>> >         router. It would have ethernet plugs on the box and use 
>> ethernet
>>
>> >         layer
>>
>> >         1 specs. But when a another 'True-IP' device was plugged in, it
>>
>> >         would
>>
>> >         quickly negotiate a direct IP connection, oh and with 
>> proper 64KB
>>
>> >         packets. It would also, authenticate, announce and turn on link
>>
>> >         layer
>>
>> >         encryption.
>>
>> >
>>
>> >         Such a device would also be a legacy router. It would fake 
>> all the
>>
>> >         signals necessary for a legacy ethernet device to function. 
>> It would
>>
>> >         also be responsible for maintaining the local information 
>> for the
>>
>> >         network service database and intercommunicating with other 
>> hubs to
>>
>> >         achieve a global network view.
>>
>> >
>>
>> >
>>
>> >         The net result of all this would be that I would never ever 
>> need to
>>
>> >         install another printer (no, it is not actually necessary 
>> for every
>>
>> >         stupid printer to have its own stupid printer driver). 
>> Opening the
>>
>> >         'printers' folder would automatically show every printer 
>> that is on
>>
>> >         the network or can be woken from slumber by the hub it 
>> connects to.
>>
>> >
>>
>> >
>>
>> >
>>
>


--------------070709050401090503020400
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta content="text/html; charset=windows-1252"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    Upss. I meant Layer 4 of course ;)<br>
    <br>
    <div class="moz-cite-prefix">On 04/15/16 08:36, Dimitri Staessens
      wrote:<br>
    </div>
    <blockquote cite="mid:57108BF3.4030608@intec.ugent.be" type="cite">
      <meta content="text/html; charset=windows-1252"
        http-equiv="Content-Type">
      If you killed the user, Layer 3 would stop working...<br>
      <br>
      <div class="moz-cite-prefix">On 04/15/16 05:30, Chaitanya D wrote:<br>
      </div>
      <blockquote
        cite="mid:5710604a.4d40620a.1fffb.ffffd647@mx.google.com"
        type="cite">
        <meta http-equiv="Content-Type" content="text/html;
          charset=windows-1252">
        <meta name="Generator" content="Microsoft Word 15 (filtered
          medium)">
        <style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;}
p
	{mso-style-priority:99;
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
.MsoChpDefault
	{mso-style-type:export-only;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style>
        <div class="WordSection1">
          <p>The BOFH way - kill the user and let the network be.... ;)</p>
          <p><o:p> </o:p></p>
          <p>Kidding of course</p>
          <p><o:p> </o:p></p>
          <p><o:p> </o:p></p>
          <div
            style="mso-element:para-border-div;border:none;border-top:solid
            #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
            <p style="border:none;padding:0cm"><br>
              <b>From: </b>Carlos M. Martinez<br>
              <b>Sent: </b>15 April 2016 08:18<br>
              <b>To: </b>Ted Lemon;Dimitri Staessens<br>
              <b>Cc: </b>ietf<br>
              <b>Subject: </b>Re: Time to kill layer 2</p>
          </div>
          <p class="MsoNormal"><o:p> </o:p></p>
          <p class="MsoNormal"><span style="font-family:&quot;Times New
              Roman&quot;,serif"><o:p> </o:p></span></p>
          <p class="MsoNormal">All the way up to the user ? Many times.</p>
          <p class="MsoNormal"><o:p> </o:p></p>
          <p class="MsoNormal">On 4/14/16 6:56 PM, Ted Lemon wrote:</p>
          <p class="MsoNormal">&gt; Of course!</p>
          <p class="MsoNormal">&gt; </p>
          <p class="MsoNormal">&gt; On Thu, Apr 14, 2016 at 5:54 PM,
            Dimitri Staessens</p>
          <p class="MsoNormal">&gt; &lt;<a moz-do-not-send="true"
              class="moz-txt-link-abbreviated"
              href="mailto:dimitri.staessens@intec.ugent.be">dimitri.staessens@intec.ugent.be</a></p>
          <p class="MsoNormal">&gt; <a moz-do-not-send="true"
              class="moz-txt-link-rfc2396E"
              href="mailto:dimitri.staessens@intec.ugent.be">&lt;mailto:dimitri.staessens@intec.ugent.be&gt;</a>&gt;
            wrote:</p>
          <p class="MsoNormal">&gt; </p>
          <p class="MsoNormal">&gt;     anyone thought of killing
            everything on top of layer 2?</p>
          <p class="MsoNormal">&gt; </p>
          <p class="MsoNormal">&gt; </p>
          <p class="MsoNormal">&gt;     On 04/14/16 14:59, Phillip
            Hallam-Baker wrote:</p>
          <p class="MsoNormal">&gt; </p>
          <p class="MsoNormal">&gt;         This morning I spent an hour
            debugging the network to print out two</p>
          <p class="MsoNormal">&gt;         class projects that were
            due. Some points:</p>
          <p class="MsoNormal">&gt; </p>
          <p class="MsoNormal">&gt;         1) My ability to debug the
            network is better than 99% of the</p>
          <p class="MsoNormal">&gt;         population</p>
          <p class="MsoNormal">&gt;         2) The interaction of
            Bonjour, DHCP and auto power saving is</p>
          <p class="MsoNormal">&gt;         unfortunate</p>
          <p class="MsoNormal">&gt;         3) Things should still work
            after I have been away for a week</p>
          <p class="MsoNormal">&gt;         4) If vendors want to be
            selling all that IoT gear, they have to</p>
          <p class="MsoNormal">&gt;         solve</p>
          <p class="MsoNormal">&gt;         these issues.</p>
          <p class="MsoNormal">&gt; </p>
          <p class="MsoNormal">&gt;         5) I want someone to blame.
            Right now when the network doesn't</p>
          <p class="MsoNormal">&gt;         work, I</p>
          <p class="MsoNormal">&gt;         don't know who is the cause.
            I want one point of contact. Whoever is</p>
          <p class="MsoNormal">&gt;         that point of contact will
            get most of my networking money.</p>
          <p class="MsoNormal">&gt; </p>
          <p class="MsoNormal">&gt; </p>
          <p class="MsoNormal">&gt;         One of the biggest headaches
            in debugging is that 'smart hubs' are</p>
          <p class="MsoNormal">&gt;         not. They are actually very
            stupid. They make assumptions of network</p>
          <p class="MsoNormal">&gt;         topology that are not true.
            Another is the unfortunate</p>
          <p class="MsoNormal">&gt;         implementation</p>
          <p class="MsoNormal">&gt;         of DHCP.</p>
          <p class="MsoNormal">&gt; </p>
          <p class="MsoNormal">&gt;         I don't use SNMP for a
            simple reason - it is not available to most</p>
          <p class="MsoNormal">&gt;         ordinary people. I want to
            understand networking for the 99%,</p>
          <p class="MsoNormal">&gt;         not the</p>
          <p class="MsoNormal">&gt;         IETF 1%-ers.</p>
          <p class="MsoNormal">&gt; </p>
          <p class="MsoNormal">&gt;         All this networking gear is
            presented to me as black boxes over</p>
          <p class="MsoNormal">&gt;         which</p>
          <p class="MsoNormal">&gt;         I have absolutely no control
            (which is fine-ish) and no visibility.</p>
          <p class="MsoNormal">&gt; </p>
          <p class="MsoNormal">&gt;         What we have today is the
            product of a historical process. I</p>
          <p class="MsoNormal">&gt;         remember</p>
          <p class="MsoNormal">&gt;         the days when Ethernet ran
            on 10BaseT. But I installed my first</p>
          <p class="MsoNormal">&gt;         switch</p>
          <p class="MsoNormal">&gt;         30 years ago and it has been
            a switched protocol for 20 years now.</p>
          <p class="MsoNormal">&gt; </p>
          <p class="MsoNormal">&gt; </p>
          <p class="MsoNormal">&gt;         It seems to me that there is
            a business opportunity for any</p>
          <p class="MsoNormal">&gt;         vendor who</p>
          <p class="MsoNormal">&gt;         takes the rather obvious
            step of simplifying the system.</p>
          <p class="MsoNormal">&gt; </p>
          <p class="MsoNormal">&gt;         People talk about 'IP
            everywhere' and 'IP end-to-end' which is</p>
          <p class="MsoNormal">&gt;         rather</p>
          <p class="MsoNormal">&gt;         odd when you think about the
            fact that virtually every local network</p>
          <p class="MsoNormal">&gt;         uses MAC addresses for
            routing.</p>
          <p class="MsoNormal">&gt; </p>
          <p class="MsoNormal">&gt;         One of the reasons that IP
            won against OSI was that it was simpler.</p>
          <p class="MsoNormal">&gt;         Applications ran on top of
            the IP layer with only TCP inbetween. Of</p>
          <p class="MsoNormal">&gt;         course these days we do have
            a Presentation layer, Web Services</p>
          <p class="MsoNormal">&gt;         run on</p>
          <p class="MsoNormal">&gt;         HTTP. But unlike the OSI
            presentation layer, ours does not introduce</p>
          <p class="MsoNormal">&gt;         extra moving parts.</p>
          <p class="MsoNormal">&gt; </p>
          <p class="MsoNormal">&gt;         It seems to me that if we
            really believed in IP everywhere and IP</p>
          <p class="MsoNormal">&gt;         end-to-end we would insist
            that network switches be IP routers that</p>
          <p class="MsoNormal">&gt;         can be managed using
            BGP/OSPF or at least routing tables rather than</p>
          <p class="MsoNormal">&gt;         heuristic devices that try
            to guess where packets should go based on</p>
          <p class="MsoNormal">&gt;         goat entrails, phases of the
            moon or whatever they use.</p>
          <p class="MsoNormal">&gt; </p>
          <p class="MsoNormal">&gt; </p>
          <p class="MsoNormal">&gt;         What should have happened
            many moons ago was that DHCP should have</p>
          <p class="MsoNormal">&gt;         become a bidirectional
            protocol or a bootstrap to a bidirectional</p>
          <p class="MsoNormal">&gt;         protocol. So when a printer
            joins the network, it authenticates and</p>
          <p class="MsoNormal">&gt;         tells the network what it
            is. And this is all defined in one set of</p>
          <p class="MsoNormal">&gt;         specifications from one
            organization, none of which assumes that</p>
          <p class="MsoNormal">&gt;         security is an 'advanced',
            'optional' or 'enterprise' feature.</p>
          <p class="MsoNormal">&gt; </p>
          <p class="MsoNormal">&gt;         Instead we have an ad-hoc
            layer trying to achieve the same result in</p>
          <p class="MsoNormal">&gt;         peer-to-peer fashion. A
            similar approach works for frogs as a</p>
          <p class="MsoNormal">&gt;         reproductive mechanism but
            only at the species level. It certainly</p>
          <p class="MsoNormal">&gt;         does not work for the
            individual ova which may or may not connect to</p>
          <p class="MsoNormal">&gt;         the printer it is trying to
            use to print the kids damned homework.</p>
          <p class="MsoNormal">&gt; </p>
          <p class="MsoNormal">&gt; </p>
          <p class="MsoNormal">&gt;         Seriously, the fact that
            things have scaled thus far and the 1% can</p>
          <p class="MsoNormal">&gt;         get them to work does not
            mean that we can get to the next level</p>
          <p class="MsoNormal">&gt;         without a serious rethink of
            the local network architecture.</p>
          <p class="MsoNormal">&gt; </p>
          <p class="MsoNormal">&gt;         The type of device I think
            we need would be first and foremost an IP</p>
          <p class="MsoNormal">&gt;         router. It would have
            ethernet plugs on the box and use ethernet</p>
          <p class="MsoNormal">&gt;         layer</p>
          <p class="MsoNormal">&gt;         1 specs. But when a another
            'True-IP' device was plugged in, it</p>
          <p class="MsoNormal">&gt;         would</p>
          <p class="MsoNormal">&gt;         quickly negotiate a direct
            IP connection, oh and with proper 64KB</p>
          <p class="MsoNormal">&gt;         packets. It would also,
            authenticate, announce and turn on link</p>
          <p class="MsoNormal">&gt;         layer</p>
          <p class="MsoNormal">&gt;         encryption.</p>
          <p class="MsoNormal">&gt; </p>
          <p class="MsoNormal">&gt;         Such a device would also be
            a legacy router. It would fake all the</p>
          <p class="MsoNormal">&gt;         signals necessary for a
            legacy ethernet device to function. It would</p>
          <p class="MsoNormal">&gt;         also be responsible for
            maintaining the local information for the</p>
          <p class="MsoNormal">&gt;         network service database and
            intercommunicating with other hubs to</p>
          <p class="MsoNormal">&gt;         achieve a global network
            view.</p>
          <p class="MsoNormal">&gt; </p>
          <p class="MsoNormal">&gt; </p>
          <p class="MsoNormal">&gt;         The net result of all this
            would be that I would never ever need to</p>
          <p class="MsoNormal">&gt;         install another printer (no,
            it is not actually necessary for every</p>
          <p class="MsoNormal">&gt;         stupid printer to have its
            own stupid printer driver). Opening the</p>
          <p class="MsoNormal">&gt;         'printers' folder would
            automatically show every printer that is on</p>
          <p class="MsoNormal">&gt;         the network or can be woken
            from slumber by the hub it connects to.</p>
          <p class="MsoNormal">&gt; </p>
          <p class="MsoNormal">&gt; </p>
          <p class="MsoNormal">&gt; </p>
          <p class="MsoNormal"><o:p> </o:p></p>
          <p class="MsoNormal"><o:p> </o:p></p>
          <p class="MsoNormal"><o:p> </o:p></p>
        </div>
      </blockquote>
      <br>
    </blockquote>
    <br>
  </body>
</html>

--------------070709050401090503020400--


From nobody Fri Apr 15 04:03:41 2016
Return-Path: <ietf@meetecho.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 C7A0D12D89E for <ietf@ietfa.amsl.com>; Fri, 15 Apr 2016 04:03:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001] autolearn=unavailable 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 61c1oFS9Owvq for <ietf@ietfa.amsl.com>; Fri, 15 Apr 2016 04:03:36 -0700 (PDT)
Received: from smtpdg225.aruba.it (smtpcmd0998.aruba.it [62.149.156.98]) by ietfa.amsl.com (Postfix) with ESMTP id AF5A012DC79 for <ietf@ietf.org>; Fri, 15 Apr 2016 04:03:35 -0700 (PDT)
Received: from [192.168.1.106] ([151.77.134.3]) by smtpcmd09.ad.aruba.it with bizsmtp id ib3Y1s01m04Zlvb01b3Zuq; Fri, 15 Apr 2016 13:03:34 +0200
To: ietf@ietf.org
From: Meetecho IETF support <ietf@meetecho.com>
Subject: IETF95 remote attendance
Message-ID: <5710CA7F.3050207@meetecho.com>
Date: Fri, 15 Apr 2016 13:03:27 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.7.1
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-15; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/Vt7ONW46zBTXjDgD0Viy912EuVs>
Cc: vmeet@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: Fri, 15 Apr 2016 11:03:39 -0000

All,

please find below some data about remote attendance at IETF95 in Buenos 
Aires.

- 1976 accesses to Meetecho (multiple accesses by the same user within 
the same session are counted only once).

- 621 registered remote participants.

- 712 unique remote participants joined Meetecho through the week; among 
these, 282 opted to also put their Registration ID.

- 44 successful remote presentations.
- 2 failed remote presentations.

- 33 successful remote interventions through the virtual queue.
- 10 failed remote interventions through the virtual queue.

Virtual queue's success rate evolution during the week:
- Monday:     7 OK, 5 KO
- Tuesday:    8 OK, 3 KO
- Wednesday:  7 OK, 2 KO
- Thursday:   4 OK, 0 KO
- Friday:     7 OK, 0 KO

Note #1: starting on Monday night we made more explicit that people who 
wanted to use the virtual queue were recommended to perform the 
self-test in order to check everything was working on their side.

Note #2: almost all participants which failed on Monday/Tuesday, managed 
to succeed during the rest of the week.

Cheers,
the Meetecho team


From nobody Fri Apr 15 04:13:34 2016
Return-Path: <sm@elandsys.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 8B3AC12DD16 for <ietf@ietfa.amsl.com>; Fri, 15 Apr 2016 04:13:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.786
X-Spam-Level: 
X-Spam-Status: No, score=-2.786 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.996, T_DKIM_INVALID=0.01] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=opendkim.org header.b=h+jNA92r; dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=elandsys.com header.b=zOnl8uvr
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 isKU1EH8_w9H for <ietf@ietfa.amsl.com>; Fri, 15 Apr 2016 04:13:31 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 7EDDD12D688 for <ietf@ietf.org>; Fri, 15 Apr 2016 04:05:46 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.227.85.52]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id u3FB5SBC006294 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 15 Apr 2016 04:05:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1460718340; x=1460804740; bh=tcGiLndMKQxt7PaRq8HBadvni11MT/0B5uJfpjStV1o=; h=Date:To:From:Subject:In-Reply-To:References; b=h+jNA92rIE5BJgWFh3E1I0D6aGmhpVrlqte+bc6uAZIrpOU05M7qqpomwz+XjMUxm 0xZ14BJfLBZ3fKjwiVDFCgC8GlV+/uyfrpcs3D1dqiElr6i5cLNQ7EPsZCTeHUEFCo fJesIjpCapUeaIfs3qOsqgFcrWd2eDDGKz81lFpY=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1460718340; x=1460804740; i=@elandsys.com; bh=tcGiLndMKQxt7PaRq8HBadvni11MT/0B5uJfpjStV1o=; h=Date:To:From:Subject:In-Reply-To:References; b=zOnl8uvr6hdcHoqIokITZtwKiTZ3sR8aPQMG4zB7caxR94XhjjQs1qNvVLMAGeQq5 7lDY4jm5jk6BNGHP005T1g+teyGGpn08KepD2zAcBAuwPb/jIc6OBXavnZYoMNDhCx nHeyScFbuft57vJMJzkcv5k4VqyvC9aNlcSGZE68=
Message-Id: <6.2.5.6.2.20160415010222.107f21f0@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Fri, 15 Apr 2016 04:03:43 -0700
To: Michael Cameron <michael.cameron@ericsson.com>, ietf@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: RE: Last Call on draft-bradner-rfc3979bis-08.txt ("Intellectual Property Rights in IETF Technology")
In-Reply-To: <36BAA6A693139D4BBCB37CCCA660E08A14FD99DA@eusaamb101.ericss on.se>
References: <65AD4D713F340D761513414F@JcK-HP8200.jck.com> <36BAA6A693139D4BBCB37CCCA660E08A14FD99DA@eusaamb101.ericsson.se>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/CIo6FhE0fEFSf2p7WEEka9hQfxM>
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: Fri, 15 Apr 2016 11:13:32 -0000

Hi Mike,
At 10:33 12-04-2016, Michael Cameron wrote:
>My response:
>
>We need to be careful not to place on Area Directors unreasonable 
>burdens and obligations.  Further, there needs to be certainty as to 
>what the obligations are.   The obligations imposed on Area 
>Directors to declare known IPR should be limited to those activities 
>in which they actively participate.  I'll defer to the ADs, but I 
>would think that an AD acting on a recommendation or advice from a 
>WG as to how to proceed on a Specification, without more, does not 
>necessarily rise to the level of active participation.

 From what I read, the duty to disclose in the U.S. "does not extend 
to typists, clerks, and similar personnel".

There is the following text in Standards Track RFCs: "It has received 
public review and has been approved for publication by the Internet 
Engineering Steering Group (IESG)".

In the last sentence of the text quoted above there is the following: 
"I'll defer to the ADs".  Would a reasonable person conclude that an 
IETF participant with a good understanding of the IETF "Note Well" 
defer to a typist on a matter which is important?  Furthermore, would 
an Area Director describe his/her work as being similar to a clerk in 
his/her biography?

Does the fact that an Area Director has the authority to share the 
responsibility for the approval of a Standards Track RFC constitute 
"active participation"?

Regards,
S. Moonesamy  


From nobody Fri Apr 15 04:18:40 2016
Return-Path: <stewart.bryant@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 130D412DE4E; Fri, 15 Apr 2016 04:18:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 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, RCVD_IN_DNSWL_LOW=-0.7, 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 Ka4RcasW18ly; Fri, 15 Apr 2016 04:18:36 -0700 (PDT)
Received: from mail-wm0-x22f.google.com (mail-wm0-x22f.google.com [IPv6:2a00:1450:400c:c09::22f]) (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 E15A212E1CA; Fri, 15 Apr 2016 04:18:35 -0700 (PDT)
Received: by mail-wm0-x22f.google.com with SMTP id u206so27441428wme.1; Fri, 15 Apr 2016 04:18:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=lVYkCZ0tlZN5sOyoyZQb6cqI3JPk4QbYs3WR2kPttRU=; b=JLypJfPDM3APV1KYrVL81svCgJdrGrRS/cG6UXPlu7vJx5XwCbGhKouwMlhxJnt1Zp le2KQcK5e1OqeHpCYYnTM9TqJSlI3oWhbiOFY97mmBirAR20ws0TVwaku6+FH7q49q8l YJ/7JhazrgsJYfrqzpouRcQdZH7usXpzEHat1W4gsOZ/2u97k4tpoBWwV/RYQpTmhA9o 1CCtTR0bdwLmvupfTAwNohiq6mwHgt20pFkGSrGLowgwH1fjVpsheoNKbE9FXTrQRQoI s137uMlP1NnGRFhiVublnwr09dlbxxgxLoNNYL8DsRRY9u9BRmYyCknPmA7qCZoywqmA QC7g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=lVYkCZ0tlZN5sOyoyZQb6cqI3JPk4QbYs3WR2kPttRU=; b=bNt4csl2TMYgZqmalZ21SogHfEooqfVa6d9rFkTUjTr3Dux2wdf3LE5CGhEzZlYNwy t/QHkDyWIvHamkgbzVIzkZW2SdF0MVqtKRy63vNOpCn8gD8UQwTnJdwhRGLdQHFF14IM lMsKxFs94xSOCx5+rKqdr2DsP7JROBg//r2IPz8+2BeDlDqv6IJYOgiPbuh24zK1X00x sXCQXRuipgl18aUMgs8rmocLtBphFyc9iacaITv4WvrQDaiICNjMO7s53zHiQpmoanZY qgMsmPUaYH8Uv2rJWYjyTn/nMlZSZz9+ECmLSSRC77xedFEFJcZE+k8sPBZttftlb1z8 rdEw==
X-Gm-Message-State: AOPr4FWzVUJTK1dcP8XOp6pgSGzzQvNlr4ESvJBu0DhQZ7KmBsCZTTmqhOE+LRC8QcwJYQ==
X-Received: by 10.28.27.73 with SMTP id b70mr3810689wmb.19.1460719114375; Fri, 15 Apr 2016 04:18:34 -0700 (PDT)
Received: from [192.168.2.126] (host213-123-124-182.in-addr.btopenworld.com. [213.123.124.182]) by smtp.gmail.com with ESMTPSA id x2sm48522769wjr.33.2016.04.15.04.18.32 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 15 Apr 2016 04:18:33 -0700 (PDT)
Subject: Re: IETF95 remote attendance
To: Meetecho IETF support <ietf@meetecho.com>, ietf@ietf.org
References: <5710CA7F.3050207@meetecho.com>
From: Stewart Bryant <stewart.bryant@gmail.com>
Message-ID: <5710CE07.9090104@gmail.com>
Date: Fri, 15 Apr 2016 12:18:31 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.7.0
MIME-Version: 1.0
In-Reply-To: <5710CA7F.3050207@meetecho.com>
Content-Type: text/plain; charset=iso-8859-15; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/fKXCNEi4mukxiCibCLbgZfmxggI>
Cc: vmeet@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: Fri, 15 Apr 2016 11:18:37 -0000

On 15/04/2016 12:03, Meetecho IETF support wrote:
> - 712 unique remote participants joined Meetecho through the week; 
> among these, 282 opted to also put their Registration ID. 

There was something odd about the registration number system.

I tried to enter my registration number a few times but it rejected it 
every time.

Since it did not REQUIRE(sic)  the registration number  I just used the 
option not to enter it.

- Stewart


From nobody Fri Apr 15 04:56:32 2016
Return-Path: <jhall@cdt.org>
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 7BF7712D980 for <ietf@ietfa.amsl.com>; Fri, 15 Apr 2016 04:56:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cdt.org
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 DW2YS3hDQVqt for <ietf@ietfa.amsl.com>; Fri, 15 Apr 2016 04:56:30 -0700 (PDT)
Received: from mail-vk0-x22f.google.com (mail-vk0-x22f.google.com [IPv6:2607:f8b0:400c:c05::22f]) (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 19A5E12D8FB for <ietf@ietf.org>; Fri, 15 Apr 2016 04:56:30 -0700 (PDT)
Received: by mail-vk0-x22f.google.com with SMTP id c4so143854010vkb.3 for <ietf@ietf.org>; Fri, 15 Apr 2016 04:56:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cdt.org; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=NGsm11kOBIIXiopYfrwu8Rc8w1PQ4QivOcSl60UxzfI=; b=FjUG+0oY2OBzp63iCgp1BACTjH7WVwFJ5gRcd5qcB6WCySW92raZda/vX3cTJQ/C+D KWCIq9dIyZnGoAScvi5eSAcGZc08tp8u/YLSDkLBmQqOcceAX79f3Vs6nQ/npdL8Gl2C wvQvlKbofCptRn0JoxkNYUFOjfIV34xbG5s8w=
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=NGsm11kOBIIXiopYfrwu8Rc8w1PQ4QivOcSl60UxzfI=; b=libVNp19KVrj0kWVEcxJ5EHuJ0VVyLBZZog5wsHu+bSLzuawgrz78EECTUI46a/0h/ Mi8tuakl9V3or3ezGtqtNRqL1JNqPHQvjMsNiWEJCYggUB01IYCb0px3x7Ok0Pv90xjW HLfC0UEw6GpD6c4z1Vw8EI8Ow9zFFMa3u4/sVpxF3oTVBKXofr+XXqaBUKi9btPgh97z MhUl0TCMI8E3COeFK7uDrGISTI65HO/RT9NVb9550uG+FQbNhetqXfthn7hAesBV1xiN jzvFAabH7o3OkXNy8eXFu6EN5Dg54+NdGD3Nc4NlM5aLWKE0Y/mGtkNK+bzK2JXq4P6U LZhA==
X-Gm-Message-State: AOPr4FUS4GWjtXe6FordhJGE8cvrAJeTC+kMUqnaocDO0CZ1SMMwHvStrJ9AXkAPfJA8cWjb4pPsFV+BuzEHkxwL
X-Received: by 10.31.151.75 with SMTP id z72mr9706137vkd.104.1460721389167; Fri, 15 Apr 2016 04:56:29 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.103.94.3 with HTTP; Fri, 15 Apr 2016 04:56:09 -0700 (PDT)
In-Reply-To: <5710CE07.9090104@gmail.com>
References: <5710CA7F.3050207@meetecho.com> <5710CE07.9090104@gmail.com>
From: Joseph Lorenzo Hall <joe@cdt.org>
Date: Fri, 15 Apr 2016 07:56:09 -0400
Message-ID: <CABtrr-W4bmaG2vEEokbwCLED2P9_eiEgmeM2zHO8-RQUt7BZ0Q@mail.gmail.com>
Subject: Re: IETF95 remote attendance
To: Stewart Bryant <stewart.bryant@gmail.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/mx--LkeljfrRc9jR0GiYlI-Ommk>
Cc: IETF Discussion Mailing List <ietf@ietf.org>, vmeet@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: Fri, 15 Apr 2016 11:56:31 -0000

On Fri, Apr 15, 2016 at 7:18 AM, Stewart Bryant
<stewart.bryant@gmail.com> wrote:
>
>
> On 15/04/2016 12:03, Meetecho IETF support wrote:
>>
>> - 712 unique remote participants joined Meetecho through the week; among
>> these, 282 opted to also put their Registration ID.
>
>
> There was something odd about the registration number system.
>
> I tried to enter my registration number a few times but it rejected it every
> time.
>
> Since it did not REQUIRE(sic)  the registration number  I just used the
> option not to enter it.

I had to enter "Joseph Hall" instead of "Joe Hall" to get it to take my Reg. ID.

-- 
Joseph Lorenzo Hall
Chief Technologist, Center for Democracy & Technology [https://www.cdt.org]
e: joe@cdt.org, p: 202.407.8825, pgp: https://josephhall.org/gpg-key
Fingerprint: 3CA2 8D7B 9F6D DBD3 4B10  1607 5F86 6987 40A9 A871


From nobody Fri Apr 15 05:07:27 2016
Return-Path: <spromano@unina.it>
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 8E95912D8D1 for <ietf@ietfa.amsl.com>; Fri, 15 Apr 2016 05:07:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.896
X-Spam-Level: 
X-Spam-Status: No, score=-2.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.996, SPF_PASS=-0.001] autolearn=unavailable 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 0HOFnoFjOOMz for <ietf@ietfa.amsl.com>; Fri, 15 Apr 2016 05:07:22 -0700 (PDT)
Received: from brc2.unina.it (brc2.unina.it [192.132.34.42]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0C14C12D8D2 for <ietf@ietf.org>; Fri, 15 Apr 2016 05:07:22 -0700 (PDT)
X-ASG-Debug-ID: 1460722037-05f275030dbb790001-h9jmKw
Received: from smtp2.unina.it (smtp2.unina.it [192.132.34.62]) by brc2.unina.it with ESMTP id ZqwSk7tCzQ0s0SJL (version=TLSv1 cipher=AES256-SHA bits=256 verify=NO); Fri, 15 Apr 2016 14:07:17 +0200 (CEST)
X-Barracuda-Envelope-From: spromano@unina.it
X-Barracuda-Apparent-Source-IP: 192.132.34.62
Received: from [143.225.28.169] ([143.225.28.169]) (authenticated bits=0) by smtp2.unina.it (8.14.4/8.14.4) with ESMTP id u3FC7G80018773 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 15 Apr 2016 14:07:16 +0200
Content-Type: multipart/alternative; boundary="Apple-Mail=_0CA34064-6183-4D3A-AC0E-3D9E20A88CD1"
Mime-Version: 1.0 (Mac OS X Mail 8.1 \(1993\))
Subject: Re: IETF95 remote attendance
From: Simon Pietro Romano <spromano@unina.it>
X-ASG-Orig-Subj: Re: IETF95 remote attendance
In-Reply-To: <CABtrr-W4bmaG2vEEokbwCLED2P9_eiEgmeM2zHO8-RQUt7BZ0Q@mail.gmail.com>
Date: Fri, 15 Apr 2016 14:07:17 +0200
Message-Id: <CBA2E5F4-E083-4D91-8B96-2C5F3C4D6517@unina.it>
References: <5710CA7F.3050207@meetecho.com> <5710CE07.9090104@gmail.com> <CABtrr-W4bmaG2vEEokbwCLED2P9_eiEgmeM2zHO8-RQUt7BZ0Q@mail.gmail.com>
To: Joseph Lorenzo Hall <joe@cdt.org>
X-Mailer: Apple Mail (2.1993)
X-Barracuda-Connect: smtp2.unina.it[192.132.34.62]
X-Barracuda-Start-Time: 1460722037
X-Barracuda-Encrypted: AES256-SHA
X-Barracuda-URL: http://192.132.34.42:8000/cgi-mod/mark.cgi
X-Virus-Scanned: by bsmtpd at unina.it
X-Barracuda-BRTS-Status: 1
X-Barracuda-Spam-Score: 0.00
X-Barracuda-Spam-Status: No, SCORE=0.00 using global scores of TAG_LEVEL=1000.0 QUARANTINE_LEVEL=1000.0 KILL_LEVEL=6.0 tests=BSF_SC0_MISMATCH_TO, HTML_MESSAGE
X-Barracuda-Spam-Report: Code version 3.2, rules version 3.2.3.28758 Rule breakdown below pts rule name              description ---- ---------------------- -------------------------------------------------- 0.00 BSF_SC0_MISMATCH_TO    Envelope rcpt doesn't match header 0.00 HTML_MESSAGE           BODY: HTML included in message
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/cmOdxr4L1Aoc0Ct9SAejp4JBv0w>
Cc: IETF Discussion Mailing List <ietf@ietf.org>, vmeet@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: Fri, 15 Apr 2016 12:07:25 -0000

--Apple-Mail=_0CA34064-6183-4D3A-AC0E-3D9E20A88CD1
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

It was indeed required to insert =E2=80=9Cexactly=E2=80=9D the same =
information as the one you provided when filling in the IETF =
registration form.=20

Simon


> On 15/apr/2016, at 13:56, Joseph Lorenzo Hall <joe@cdt.org> wrote:
>=20
> On Fri, Apr 15, 2016 at 7:18 AM, Stewart Bryant
> <stewart.bryant@gmail.com> wrote:
>>=20
>>=20
>> On 15/04/2016 12:03, Meetecho IETF support wrote:
>>>=20
>>> - 712 unique remote participants joined Meetecho through the week; =
among
>>> these, 282 opted to also put their Registration ID.
>>=20
>>=20
>> There was something odd about the registration number system.
>>=20
>> I tried to enter my registration number a few times but it rejected =
it every
>> time.
>>=20
>> Since it did not REQUIRE(sic)  the registration number  I just used =
the
>> option not to enter it.
>=20
> I had to enter "Joseph Hall" instead of "Joe Hall" to get it to take =
my Reg. ID.
>=20
> --=20
> Joseph Lorenzo Hall
> Chief Technologist, Center for Democracy & Technology =
[https://www.cdt.org]
> e: joe@cdt.org, p: 202.407.8825, pgp: https://josephhall.org/gpg-key
> Fingerprint: 3CA2 8D7B 9F6D DBD3 4B10  1607 5F86 6987 40A9 A871
>=20

                     					       _\\|//_
                           				      ( O-O )
   ~~~~~~~~~~~~~~~~~~~~~~o00~~(_)~~00o~~~~~~~~~~~~~~~~~~~~~~~~
                    				Simon Pietro Romano
             				 Universita' di Napoli Federico =
II
                		     Computer Engineering Department=20
	             Phone: +39 081 7683823 -- Fax: +39 081 7683816
                                           e-mail: spromano@unina.it

		    <<Molti mi dicono che lo scoraggiamento =C3=A8 =
l'alibi degli=20
		    idioti. Ci rifletto un istante; e mi scoraggio>>. =
Magritte.
               			                     oooO
  ~~~~~~~~~~~~~~~~~~~~~~~(   )~~~ Oooo~~~~~~~~~~~~~~~~~~~~~~~~~
					                 \ (            =
(   )
			                                  \_)          ) =
/
                                                                       =
(_/







--Apple-Mail=_0CA34064-6183-4D3A-AC0E-3D9E20A88CD1
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D"">It was indeed required to insert =E2=80=9Cexactly=E2=80=9D =
the same information as the one you provided when filling in the IETF =
registration form.&nbsp;<div class=3D""><br class=3D""></div><div =
class=3D"">Simon<br class=3D""><div class=3D""><br class=3D""></div><div =
class=3D""><br class=3D""><div><blockquote type=3D"cite" class=3D""><div =
class=3D"">On 15/apr/2016, at 13:56, Joseph Lorenzo Hall &lt;<a =
href=3D"mailto:joe@cdt.org" class=3D"">joe@cdt.org</a>&gt; =
wrote:</div><br class=3D"Apple-interchange-newline"><div class=3D"">On =
Fri, Apr 15, 2016 at 7:18 AM, Stewart Bryant<br class=3D"">&lt;<a =
href=3D"mailto:stewart.bryant@gmail.com" =
class=3D"">stewart.bryant@gmail.com</a>&gt; wrote:<br =
class=3D""><blockquote type=3D"cite" class=3D""><br class=3D""><br =
class=3D"">On 15/04/2016 12:03, Meetecho IETF support wrote:<br =
class=3D""><blockquote type=3D"cite" class=3D""><br class=3D"">- 712 =
unique remote participants joined Meetecho through the week; among<br =
class=3D"">these, 282 opted to also put their Registration ID.<br =
class=3D""></blockquote><br class=3D""><br class=3D"">There was =
something odd about the registration number system.<br class=3D""><br =
class=3D"">I tried to enter my registration number a few times but it =
rejected it every<br class=3D"">time.<br class=3D""><br class=3D"">Since =
it did not REQUIRE(sic) &nbsp;the registration number &nbsp;I just used =
the<br class=3D"">option not to enter it.<br class=3D""></blockquote><br =
class=3D"">I had to enter "Joseph Hall" instead of "Joe Hall" to get it =
to take my Reg. ID.<br class=3D""><br class=3D"">-- <br class=3D"">Joseph =
Lorenzo Hall<br class=3D"">Chief Technologist, Center for Democracy =
&amp; Technology [<a href=3D"https://www.cdt.org" =
class=3D"">https://www.cdt.org</a>]<br class=3D"">e: <a =
href=3D"mailto:joe@cdt.org" class=3D"">joe@cdt.org</a>, p: 202.407.8825, =
pgp: <a href=3D"https://josephhall.org/gpg-key" =
class=3D"">https://josephhall.org/gpg-key</a><br class=3D"">Fingerprint: =
3CA2 8D7B 9F6D DBD3 4B10 &nbsp;1607 5F86 6987 40A9 A871<br class=3D""><br =
class=3D""></div></blockquote></div><br class=3D""><div =
apple-content-edited=3D"true" class=3D"">
<span class=3D"Apple-style-span" style=3D"border-collapse: separate; =
color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; =
font-variant: normal; font-weight: normal; letter-spacing: normal; =
line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: =
0px; text-transform: none; white-space: normal; widows: 2; word-spacing: =
0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px;  "><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; color: rgb(0, 0, 0); font-family: =
Helvetica; font-style: normal; font-variant: normal; font-weight: =
normal; letter-spacing: normal; line-height: normal; orphans: 2; =
text-align: -webkit-auto; text-indent: 0px; text-transform: none; =
white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px;  "><div style=3D"word-wrap: =
break-word; -webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space; " class=3D""><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; color: rgb(0, 0, 0); font-family: =
Helvetica; font-style: normal; font-variant: normal; font-weight: =
normal; letter-spacing: normal; line-height: normal; orphans: 2; =
text-align: -webkit-auto; text-indent: 0px; text-transform: none; =
white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px;  "><div style=3D"word-wrap: =
break-word; -webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space; " class=3D""><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; color: rgb(0, 0, 0); font-family: =
Helvetica; font-style: normal; font-variant: normal; font-weight: =
normal; letter-spacing: normal; line-height: normal; orphans: 2; =
text-align: -webkit-auto; text-indent: 0px; text-transform: none; =
white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px;  "><div style=3D"word-wrap: =
break-word; -webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space; " class=3D""><div class=3D""><div class=3D"">&nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;<span class=3D"Apple-tab-span" style=3D"white-space: pre; ">		=
			</span><span =
class=3D"Apple-converted-space">&nbsp;</span>&nbsp; &nbsp; &nbsp; =
_\\|//_</div><div class=3D"">&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;<span =
class=3D"Apple-tab-span" style=3D"white-space: pre; ">				=
</span>&nbsp; &nbsp; &nbsp;&nbsp;( O-O )</div><div class=3D"">&nbsp; =
&nbsp;~~~~~~~~~~~~~~~~~~~~~~o00~~(_)~~00o~~~~~~~~~~~~~~~~~~~~~~~~</div><di=
v class=3D"">&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp;<span class=3D"Apple-converted-space">&nbsp;</span><span =
class=3D"Apple-tab-span" style=3D"white-space: pre; ">				=
</span>Simon Pietro Romano</div><div class=3D"">&nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp;<span class=3D"Apple-tab-span" =
style=3D"white-space: pre; ">				</span><span =
class=3D"Apple-converted-space">&nbsp;</span>Universita' di Napoli =
Federico II</div><div class=3D"">&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp;&nbsp;<span class=3D"Apple-tab-span" =
style=3D"white-space: pre; ">		</span>&nbsp; &nbsp; =
&nbsp;Computer Engineering Department&nbsp;</div><div class=3D""><span =
class=3D"Apple-tab-span" style=3D"white-space: pre; ">	</span>&nbsp; =
&nbsp; &nbsp;&nbsp; &nbsp; &nbsp; &nbsp; Phone: +39 081 7683823 -- Fax: =
+39 081 7683816</div><div class=3D"">&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;e-mail: <a =
href=3D"mailto:spromano@unina.it" =
class=3D"">spromano@unina.it</a></div><div class=3D""><br =
class=3D""></div><div class=3D""><span class=3D"Apple-tab-span" =
style=3D"white-space: pre; ">		</span>&nbsp; &nbsp; =
&lt;&lt;Molti mi dicono che lo scoraggiamento =C3=A8 l'alibi =
degli&nbsp;</div><div class=3D""><span class=3D"Apple-tab-span" =
style=3D"white-space: pre; ">		</span>&nbsp;&nbsp; =
&nbsp;idioti. Ci rifletto un istante; e mi scoraggio&gt;&gt;. =
Magritte.</div><div class=3D"">&nbsp; &nbsp; &nbsp; &nbsp;&nbsp; &nbsp; =
&nbsp; &nbsp;<span class=3D"Apple-converted-space">&nbsp;</span><span =
class=3D"Apple-tab-span" style=3D"white-space: pre; ">			=
</span>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp;oooO</div><div class=3D"">&nbsp; ~~~~~~~~~~~~~~~~~~~~~~~( =
&nbsp; )~~~&nbsp;Oooo~~~~~~~~~~~~~~~~~~~~~~~~~</div><div class=3D""><span =
class=3D"Apple-tab-span" style=3D"white-space: pre; ">				=
	</span>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;\ ( &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;( &nbsp; )</div><div =
class=3D""><span class=3D"Apple-tab-span" style=3D"white-space: pre; ">		=
	</span>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; \_) =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;) /</div><div class=3D"">&nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp;(_/</div></div><div class=3D""><br =
class=3D""></div></div></span><br =
class=3D"Apple-interchange-newline"></div></span><br =
class=3D"Apple-interchange-newline"></div></span><br =
class=3D"Apple-interchange-newline"></span><br =
class=3D"Apple-interchange-newline">
</div>
<br class=3D""></div></div></body></html>=

--Apple-Mail=_0CA34064-6183-4D3A-AC0E-3D9E20A88CD1--


From nobody Fri Apr 15 05:07:44 2016
Return-Path: <ietf@meetecho.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 668A912DA40 for <ietf@ietfa.amsl.com>; Fri, 15 Apr 2016 05:07:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001] 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 iwhsjUGTIi8j for <ietf@ietfa.amsl.com>; Fri, 15 Apr 2016 05:07:41 -0700 (PDT)
Received: from smtpdg225.aruba.it (smtpcmd0998.aruba.it [62.149.156.98]) by ietfa.amsl.com (Postfix) with ESMTP id 6964B12D86C for <ietf@ietf.org>; Fri, 15 Apr 2016 05:07:40 -0700 (PDT)
Received: from [192.168.1.106] ([151.77.134.3]) by smtpcmd09.ad.aruba.it with bizsmtp id ic7c1s00M04Zlvb01c7dH5; Fri, 15 Apr 2016 14:07:39 +0200
Subject: Re: IETF95 remote attendance
To: Joseph Lorenzo Hall <joe@cdt.org>, Stewart Bryant <stewart.bryant@gmail.com>
References: <5710CA7F.3050207@meetecho.com> <5710CE07.9090104@gmail.com> <CABtrr-W4bmaG2vEEokbwCLED2P9_eiEgmeM2zHO8-RQUt7BZ0Q@mail.gmail.com>
From: Meetecho IETF support <ietf@meetecho.com>
Message-ID: <5710D983.5040006@meetecho.com>
Date: Fri, 15 Apr 2016 14:07:31 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.7.1
MIME-Version: 1.0
In-Reply-To: <CABtrr-W4bmaG2vEEokbwCLED2P9_eiEgmeM2zHO8-RQUt7BZ0Q@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/53Etm3vOJ_PZiKed8PIh9cB1x2M>
Cc: IETF Discussion Mailing List <ietf@ietf.org>, vmeet@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: Fri, 15 Apr 2016 12:07:42 -0000

Il 15/04/2016 13:56, Joseph Lorenzo Hall ha scritto:
> On Fri, Apr 15, 2016 at 7:18 AM, Stewart Bryant
> <stewart.bryant@gmail.com> wrote:
>>
>>
>> On 15/04/2016 12:03, Meetecho IETF support wrote:
>>>
>>> - 712 unique remote participants joined Meetecho through the week; among
>>> these, 282 opted to also put their Registration ID.
>>
>>
>> There was something odd about the registration number system.
>>
>> I tried to enter my registration number a few times but it rejected it every
>> time.
>>
>> Since it did not REQUIRE(sic)  the registration number  I just used the
>> option not to enter it.
>
> I had to enter "Joseph Hall" instead of "Joe Hall" to get it to take my Reg. ID.
>

Your first and last name must be identical to the name used to register.


From nobody Fri Apr 15 06:50:10 2016
Return-Path: <nalini.elkins@insidethestack.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 A765712E704 for <ietf@ietfa.amsl.com>; Fri, 15 Apr 2016 06:50:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.196
X-Spam-Level: 
X-Spam-Status: No, score=-2.196 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, URIBL_GREY=0.424] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=yahoo.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 3ndw8hiMtyRe for <ietf@ietfa.amsl.com>; Fri, 15 Apr 2016 06:49:59 -0700 (PDT)
Received: from nm9-vm6.bullet.mail.ne1.yahoo.com (nm9-vm6.bullet.mail.ne1.yahoo.com [98.138.91.102]) (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 202D312E700 for <ietf@ietf.org>; Fri, 15 Apr 2016 06:49:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1460728197; bh=V/F4zHKm6ZYcjmnq2dx4xNyOiWRufB+WqjyeJVkHwns=; h=Date:From:Reply-To:To:Cc:Subject:References:From:Subject; b=TKohcnE0H6wzOlWXBZy3H6okxeKewyu+ZY1WFxu7tpEsInifu26PyCKXG+H+bn/78s8Ht5Jk3zORDwWj/WXYqXIrvWMJkbQvlK9dc7dRZhMWOPRQf5M4ytimT/9ifj0bGB4TL0BoiNCTjizoRuVuMG4bDBoBL3q5GiVtxiYwyzOsPsWWYi3WO7uzrOlUilQ+TPr57Bcjo+y9GjfIvgLzE8SIqaiaVnenWvzG2o+BZE3mp6iweElalWk9ZD3/QEbXPudLln4Le3ZyNGDYIIXpFtObAsQrkBfTBI48lX5Kh1bFs/L6GL2oTyIkF718thk9J3pTDpLZQ9Snypx1pVChuA==
Received: from [98.138.226.179] by nm9.bullet.mail.ne1.yahoo.com with NNFMP; 15 Apr 2016 13:49:57 -0000
Received: from [98.138.89.245] by tm14.bullet.mail.ne1.yahoo.com with NNFMP; 15 Apr 2016 13:49:57 -0000
Received: from [127.0.0.1] by omp1059.mail.ne1.yahoo.com with NNFMP; 15 Apr 2016 13:49:57 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 583681.81119.bm@omp1059.mail.ne1.yahoo.com
X-YMail-OSG: FDHVV3YVM1lh5MCGBKXVwg7if4Tz21nFiK4mDuuJmWpTWUkDocYxmg8UgM1Bhde TBl_bWIa4t2vT8jVLC5uKeAjBPtpvt4Nxo.3jJaoBkhRS2JsS1NG6zF1w20YnEqgSO.7PxRz0Xif IAf7_rK.d4H874Qxwpufx54Pn3u8oihODlO8Fk8m9RTvW9kHQmZLgKv1qelswSUljWlyckIaZkQj _hkDoIl5yYDPZdSAKwcqJ_Ow4sKxb0B3_ZAl1NqcMZl6VZ3X98913kWOhvmi7fy7RTAqx80F3Sr4 aJn.H.q57FGo9L2J_YBlY16TXeI2a9KdzRRDj5LIT2.I8oMT1EQD8XsstD393tpXJGL.DEL19.jf IMuh0DorTBl_aGxo4GrAMDlendpX6m2eZXB8drFbmiNTqiTCoPIPyFfARWLt3e542OfW6ZEGMmpe Qw6aSAhFroMxnJX2ouLngqLjgXOgUjjWa0c9JJg2nTVmg9hP0LEZhlyDBhCgPUL0f.vdBx7Ot23x ejPL4q_vpuujLYPIKZyJri0DE0smcmWZ_S7DOddcDITvSXn_cDMrsQceaFfBH0zS1UtfNlA--
Received: by 98.138.101.169; Fri, 15 Apr 2016 13:49:57 +0000 
Date: Fri, 15 Apr 2016 13:49:56 +0000 (UTC)
From: <nalini.elkins@insidethestack.com>
To: IETF Discussion List <ietf@ietf.org>,  "95-1st-timers@ietf.org" <95-1st-timers@ietf.org>,  "95-mentees@ietf.org" <95-mentees@ietf.org>,  "95-mentors@ietf.org" <95-mentors@ietf.org>,  95 Attendees <95attendees@ietf.org>
Message-ID: <23205583.958170.1460728196765.JavaMail.yahoo@mail.yahoo.com>
Subject: IETF95 Mentoring Counts
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
References: <23205583.958170.1460728196765.JavaMail.yahoo.ref@mail.yahoo.com>
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/IfmT3w3K1T-rSe9t3zBvD7gsyAg>
Cc: "mentoring-coordinators@ietf.org" <mentoring-coordinators@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: nalini.elkins@insidethestack.com
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: Fri, 15 Apr 2016 13:50:00 -0000

All,

At IETF95, we had:

20 individual mentee / mentor pairs
25 speed mentoring attendees (18 on Sunday, 7 on Monday)
40~ attendees for the "Journey from I-D to RFC" presentation
40~ attendees for the "Unwritten rules and values of IETF" presentation

The sessions on Sunday were quite well attended.  We also had breakfast meetings which duplicated the sessions & were not very well attended.  We will discontinue the breakfast meetings.

If you were a mentor or mentee at IETF95 and have not filled out the feedback form:
 
https://www.surveymonkey.com/r/P5K5P9N

Please do that now.  We have 23 entries.  Once we have more feedback, we will publish results.

We have also started the remote mentoring : Internet Draft review team initiative.  I suspect this will be quite popular.  After one day, we have already 12 people who want to participate.  It will take some time to get enough people to have a group of 4 who all want to work in the same area.  After we get maybe 2 people who want to work in the same WG & have overlap on language & time zone, we will ask the WG itself if it has more people who want to work on the team.

If you know of others who may benefit by this initiative or you yourself want to participate, please fill out the form here:

https://www.surveymonkey.com/r/Z8KD8GB

Please forward the form to anyone you think will be interested.

If you would like to help the mentoring team in doing any of this coordination, we would love to have you.  Please email me unicast & we will put you to work.

 Thanks,

Nalini Elkins
Inside Products, Inc.
www.insidethestack.com
(831) 659-8360


From nobody Fri Apr 15 07:47:52 2016
Return-Path: <fluffy@iii.ca>
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 C49B212E7BF for <ietf@ietfa.amsl.com>; Fri, 15 Apr 2016 07:47:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001] 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 IXIG9UQ4kjtu for <ietf@ietfa.amsl.com>; Fri, 15 Apr 2016 07:47:50 -0700 (PDT)
Received: from smtp94.iad3a.emailsrvr.com (smtp94.iad3a.emailsrvr.com [173.203.187.94]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B2A3112E7BE for <ietf@ietf.org>; Fri, 15 Apr 2016 07:47:50 -0700 (PDT)
Received: from smtp28.relay.iad3a.emailsrvr.com (localhost.localdomain [127.0.0.1]) by smtp28.relay.iad3a.emailsrvr.com (SMTP Server) with ESMTP id ED642380456; Fri, 15 Apr 2016 10:47:49 -0400 (EDT)
X-Auth-ID: fluffy@iii.ca
Received: by smtp28.relay.iad3a.emailsrvr.com (Authenticated sender: fluffy-AT-iii.ca) with ESMTPSA id 06D2A380499;  Fri, 15 Apr 2016 10:47:48 -0400 (EDT)
X-Sender-Id: fluffy@iii.ca
Received: from [192.168.4.100] ([UNAVAILABLE]. [128.107.241.191]) (using TLSv1 with cipher DHE-RSA-AES256-SHA) by 0.0.0.0:465 (trex/5.5.4); Fri, 15 Apr 2016 10:47:49 -0400
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Subject: Re: [tsvwg] Last Call: <draft-ietf-tsvwg-rtcweb-qos-15.txt> (DSCP and other packet markings for WebRTC QoS) to Proposed Standard
From: Cullen Jennings <fluffy@iii.ca>
In-Reply-To: <CE03DB3D7B45C245BCA0D243277949362E92B245@MX104CL02.corp.emc.com>
Date: Fri, 15 Apr 2016 08:47:50 -0600
Content-Transfer-Encoding: quoted-printable
Message-Id: <D12A5B0E-EF12-4BC8-999B-6ED50029C95A@iii.ca>
References: <20160321174750.31944.71903.idtracker@ietfa.amsl.com> <56F26AD3.3010403@ericsson.com> <5BB71158-3530-47A2-9A33-811F65B2F677@iii.ca> <56FBBBC1.5060902@ericsson.com> <CE03DB3D7B45C245BCA0D243277949362E92B245@MX104CL02.corp.emc.com>
To: "Black, David" <david.black@emc.com>
X-Mailer: Apple Mail (2.3124)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/fkDeyoiWGdr8d-8iQTwpAty_l1A>
Cc: Magnus Westerlund <magnus.westerlund@ericsson.com>, "tsvwg@ietf.org" <tsvwg@ietf.org>, "draft-ietf-tsvwg-rtcweb-qos@ietf.org" <draft-ietf-tsvwg-rtcweb-qos@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "tsvwg-chairs@ietf.org" <tsvwg-chairs@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: Fri, 15 Apr 2016 14:47:52 -0000

> On Apr 3, 2016, at 3:37 PM, Black, David <david.black@emc.com> wrote:
>=20
> I see a couple of Magnus's points that appear to need additional text
> in the draft:
>=20
> [1] Flow Type in application-facing browser API:
>=20
>>>>>> o Flow Type: The browser provides this input as it knows if
>>>>>> the flow is audio, interactive video with or without audio,
>>>>>> non-interactive video with or without audio, or data.
>=20
> [... snip ...]
>=20
>> The main issue here is that to me it was not clear that "Interactive
>> Video with or without audio" allows for setting these DSCP values =
also
>> for the RTP stream containing audio also. This, I do see a need for
>> clarification on.
>=20
> Propose an additional sentence:
> OLD
>   o  Flow Type: The browser provides this input as it knows if the =
flow
>      is audio, interactive video with or without audio, =
non-interactive
>      video with or without audio, or data.
> NEW
>   o  Flow Type: The browser provides this input as it knows if the =
flow
>      is audio, interactive video with or without audio, =
non-interactive
>      video with or without audio, or data.  For audio that is =
associated
>      with a video flow, the flow type of the associated video MAY
>      be used instead of the associated audio type.
>=20
> I hesitate to say anything stronger than "MAY" here.

Looks good.=20

>=20
> [2] What does "interactive" mean in an implementation?:

We could add something along lines of ..... Currently in WebRTC, media =
sent over RTP is assumed to be interactive while media streamed over =
HTTP is assumed not to be. Future WebRTC extensions could allow streamed =
media over RTP.


>=20
>> The issue is that this document is called: DSCP and other packet
>> markings for WebRTC QoS. Then this document define something that is =
not
>> immediately mappable onto what is being defined in the other WebRTC
>> specifications. That is why I am raising that there need to be more
>> clear coupling. If that coupling is to mostly happen in another
>> document, can we at least then have a proposal on the table for that
>> change to ensure that the result is understandable.
>=20
> Well, this TSVWG draft is definitely not the right place for a =
discussion of
> when a video flow is interactive or non-interactive - I hope we can =
agree
> on that.
>=20
> Beyond that, as Cullen (Jennings) is both an author of this document =
and
> one of the chairs of the rtcweb WG, I'd suggest that he and/or the =
rtcweb
> WG propose an appropriate location for discussion of when a video flow
> is interactive or non-interactive.  This TSVWG draft would then have =
an
> additional sentence added, e.g.,
>=20
> 	See [TBD] for further discussion of how to determine
> 	whether a video flow is interactive vs. non-interactive.
>=20
> I believe that the added reference here ([TBD] above) would be =
normative.
>=20
> Cullen?

That discussion happened long ago for WebRTC and we decided we did not =
need a JavaScript controls point in the WebRTC API to indicate if RTP =
was interactive or not. If people start doing streaming video over RTP =
we can come back and revisit this and trivially add an API to indicate =
that in the W3C WebRTC API. Part of what drove this decision is the =
likes of Netflix / ITunes / Youtube are not asking the browser vendors =
for streaming media over RTSP or RTP. They think HTTP works much better =
for this. Thus the browser vendors see no need for non interactive video =
over RTP. I agree with Magnus that this might change some day in the =
future but right now, I think it's close enough that everyone can live =
with it.=20

I'm not OK in treating it like some open issue that is still in =
discussion that somehow holds up this spec - it's not.=20

>=20
> Thanks, --David (as document  shepherd)
>=20


From nobody Fri Apr 15 08:07:49 2016
Return-Path: <Lee@asgard.org>
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 4FF8012DC36 for <ietf@ietfa.amsl.com>; Fri, 15 Apr 2016 08:07:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001] 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 hZ-QiKvMZkwh for <ietf@ietfa.amsl.com>; Fri, 15 Apr 2016 08:07:47 -0700 (PDT)
Received: from atl4mhob15.myregisteredsite.com (atl4mhob15.myregisteredsite.com [209.17.115.53]) by ietfa.amsl.com (Postfix) with ESMTP id D486112DF28 for <ietf@ietf.org>; Fri, 15 Apr 2016 08:07:46 -0700 (PDT)
Received: from mailpod.hostingplatform.com ([10.30.71.211]) by atl4mhob15.myregisteredsite.com (8.14.4/8.14.4) with ESMTP id u3FF7h5p014531 for <ietf@ietf.org>; Fri, 15 Apr 2016 11:07:43 -0400
Received: (qmail 10310 invoked by uid 0); 15 Apr 2016 15:07:43 -0000
X-TCPREMOTEIP: 204.235.115.167
X-Authenticated-UID: lee@asgard.org
Received: from unknown (HELO ?10.71.36.55?) (lee@asgard.org@204.235.115.167) by 0 with ESMTPA; 15 Apr 2016 15:07:43 -0000
User-Agent: Microsoft-MacOutlook/0.0.0.150911
Date: Fri, 15 Apr 2016 11:07:42 -0400
Subject: Re: Time to kill layer 2
From: Time Warner Cable <Lee@asgard.org>
To: Phillip Hallam-Baker <phill@hallambaker.com>, IETF Discussion Mailing List <ietf@ietf.org>
Message-ID: <CB8FC0F5-DD04-4478-AC41-09B4F8BA583B@asgard.org>
Thread-Topic: Time to kill layer 2
References: <CAMm+Lwg-HTYCv2pGt=SP2+Xjoko6GcJ73kVzqXC1LBTOMDKV_A@mail.gmail.com>
In-Reply-To: <CAMm+Lwg-HTYCv2pGt=SP2+Xjoko6GcJ73kVzqXC1LBTOMDKV_A@mail.gmail.com>
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/1QyfMXPrps0PSvWCaRuz29lDb6I>
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: Fri, 15 Apr 2016 15:07:48 -0000

On 4/14/16, 8:59 AM, "ietf on behalf of Phillip Hallam-Baker" <ietf-bounces@ietf.org on behalf of phill@hallambaker.com> wrote:

>This morning I spent an hour debugging the network to print out two
>class projects that were due. Some points:
>
>1) My ability to debug the network is better than 99% of the population
>2) The interaction of Bonjour, DHCP and auto power saving is unfortunate
>3) Things should still work after I have been away for a week
>4) If vendors want to be selling all that IoT gear, they have to solve
>these issues.
>
>5) I want someone to blame. Right now when the network doesn't work, I
>don't know who is the cause. I want one point of contact. Whoever is
>that point of contact will get most of my networking money.
>
>
>One of the biggest headaches in debugging is that 'smart hubs' are
>not. They are actually very stupid. They make assumptions of network
>topology that are not true. Another is the unfortunate implementation
>of DHCP.
>
>I don't use SNMP for a simple reason - it is not available to most
>ordinary people. I want to understand networking for the 99%, not the
>IETF 1%-ers.
>
>All this networking gear is presented to me as black boxes over which
>I have absolutely no control (which is fine-ish) and no visibility.

What visibility do you want? Error messages on the printer's console?
Syslog messages?
SNMP traps? Oh, apparently not, since "SNMP isn't available most ordinary people."

>
>It seems to me that there is a business opportunity for any vendor who
>takes the rather obvious step of simplifying the system.

If a vendor tries to solve the problem, they'll just add more intelligence, which will neither simplify nor stabilize the system.

>
>
>What should have happened many moons ago was that DHCP should have
>become a bidirectional protocol or a bootstrap to a bidirectional
>protocol. So when a printer joins the network, it authenticates and
>tells the network what it is. And this is all defined in one set of
>specifications from one organization, none of which assumes that
>security is an 'advanced', 'optional' or 'enterprise' feature.

See Homenet.

Lee


From nobody Fri Apr 15 08:29:26 2016
Return-Path: <hallam@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 9158212D1AB for <ietf@ietfa.amsl.com>; Fri, 15 Apr 2016 08:29:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.4
X-Spam-Level: 
X-Spam-Status: No, score=-2.4 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.199, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 6NeOjuRHo2L0 for <ietf@ietfa.amsl.com>; Fri, 15 Apr 2016 08:29:23 -0700 (PDT)
Received: from mail-lf0-x22d.google.com (mail-lf0-x22d.google.com [IPv6:2a00:1450:4010:c07::22d]) (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 ECB8912B004 for <ietf@ietf.org>; Fri, 15 Apr 2016 08:29:22 -0700 (PDT)
Received: by mail-lf0-x22d.google.com with SMTP id e190so149793396lfe.0 for <ietf@ietf.org>; Fri, 15 Apr 2016 08:29:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc; bh=rIE+0VBQc9NUe3vXI6scrxOhVxlMviCcNcgAlQnwqfg=; b=K6sUZZKrXQ+QqmBwXUgMpMAE1T5kIcfwYzTiWM6LitxU1ed20KiucSfoBEM1fgozkU Vk3tnWuRq3WXgtGlmhk8tEAcZjSc2l2Nzi4Aorp0ipbcJg1ly5bX5Kepb8LwSYXci3X8 lrRviWZDl4y55cJWTbrblXWg5VFl2tuKlqziSbQDRs94AvNW7JO3675n7x8nRsTuwaUP D2yCRNVtnc7kOxOxv/x+1ZgqjVuTYiPTcwpuMgN9pReChenu1Yby9bAvdz91DSDf8dPl vhecGxoA94RaE5z1AD5KVd70AofAXbwPpLccLSf1stJpSIvbL7/3XsqlAPjQV1gKI/Yo UCFQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:date :message-id:subject:from:to:cc; bh=rIE+0VBQc9NUe3vXI6scrxOhVxlMviCcNcgAlQnwqfg=; b=jgaUsDWO3xkyXBARA3FPAj0uKdkkyNfXnKzAj9W4hshgLUjQwGRyJNaOM9w8LNngq4 i77pGJOMV7KEaqaRfXDT1lCrDIy15XVRv11li9INagTRZQaQnCpcJ1g7frYWUW3cVKHu yqe0/z2EoiRn7ch2My7Ou6RSuUHbUvSNOk7qRbc6NdgpmmL/0nc2lCwLpoxfjiieaiYV Ean8mU4FVOCwKwTp2Abrl7yJD760vmUf4qVx7EFhyuXGtgk5ab42CfInKbENp2imYmKD r2w/kcofQp4D2lCL1wgIoLQlCw32iW35BnpsKjyYcTPj+QIzutg+lVBJiKYRIeYqKQXI dKZw==
X-Gm-Message-State: AOPr4FWNyv4ITuUkDwX3ohndcN1TW+94dUeE5KeNGduZtZwuJ8vF5VFl1E9nyVk7n+toEJIzfEEDEASukdnMVg==
MIME-Version: 1.0
X-Received: by 10.25.208.144 with SMTP id h138mr7427953lfg.48.1460734161094; Fri, 15 Apr 2016 08:29:21 -0700 (PDT)
Sender: hallam@gmail.com
Received: by 10.112.3.102 with HTTP; Fri, 15 Apr 2016 08:29:20 -0700 (PDT)
In-Reply-To: <CB8FC0F5-DD04-4478-AC41-09B4F8BA583B@asgard.org>
References: <CAMm+Lwg-HTYCv2pGt=SP2+Xjoko6GcJ73kVzqXC1LBTOMDKV_A@mail.gmail.com> <CB8FC0F5-DD04-4478-AC41-09B4F8BA583B@asgard.org>
Date: Fri, 15 Apr 2016 11:29:20 -0400
X-Google-Sender-Auth: _FOv04TCag0wYeoWGRkh2oKYyEw
Message-ID: <CAMm+LwiymMc=mqqdj9hupG7AoJMCxxJY7oz7DAX6K1zJ6H3g9g@mail.gmail.com>
Subject: Re: Time to kill layer 2
From: Phillip Hallam-Baker <phill@hallambaker.com>
To: Time Warner Cable <Lee@asgard.org>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/sEYNGppHLRS48zcLZpjSR_jN3BU>
Cc: IETF Discussion Mailing List <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: Fri, 15 Apr 2016 15:29:24 -0000

On Fri, Apr 15, 2016 at 11:07 AM, Time Warner Cable <Lee@asgard.org> wrote:

> On 4/14/16, 8:59 AM, "ietf on behalf of Phillip Hallam-Baker" <ietf-bounces@ietf.org on behalf of phill@hallambaker.com> wrote:

>>All this networking gear is presented to me as black boxes over which
>>I have absolutely no control (which is fine-ish) and no visibility.
>
> What visibility do you want? Error messages on the printer's console?
> Syslog messages?
> SNMP traps? Oh, apparently not, since "SNMP isn't available most ordinary people."

What I would like is something like a WiFi certification scheme that
means 'there is a collection of technology here that is sufficient and
complete'.

Right now I would have to pay a ridiculous amount of money to get SNMP
support because it is positioned as a differentiator between SOHO and
'enterprise' class devices.

Getting the feedback necessary to make it work should not be an
'enterprise' feature.


>>What should have happened many moons ago was that DHCP should have
>>become a bidirectional protocol or a bootstrap to a bidirectional
>>protocol. So when a printer joins the network, it authenticates and
>>tells the network what it is. And this is all defined in one set of
>>specifications from one organization, none of which assumes that
>>security is an 'advanced', 'optional' or 'enterprise' feature.
>
> See Homenet.

That seems to be premised on the assumption that the home network will
be a simplified version of today's enterprise network rather than
having far more moving parts.


From nobody Fri Apr 15 08:37:18 2016
Return-Path: <mellon@fugue.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 D823412E1D3 for <ietf@ietfa.amsl.com>; Fri, 15 Apr 2016 08:37:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.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 NMsaJRe1W_yN for <ietf@ietfa.amsl.com>; Fri, 15 Apr 2016 08:37:15 -0700 (PDT)
Received: from mail-lf0-x22b.google.com (mail-lf0-x22b.google.com [IPv6:2a00:1450:4010:c07::22b]) (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 A96E912DFD2 for <ietf@ietf.org>; Fri, 15 Apr 2016 08:37:09 -0700 (PDT)
Received: by mail-lf0-x22b.google.com with SMTP id j11so149726771lfb.1 for <ietf@ietf.org>; Fri, 15 Apr 2016 08:37:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=52T0UVkweIO5g6vbygxGOOkcYuwbOa3js0cqIpcPqwQ=; b=0D85U2mIWxeczh9SOvd+C/67nBRCJm5X6v9aKxgChYwUHusnl2McQM3Hj/BawR+BdA c/abU477CndvoyM3k2aYBnTvT/Ih68SZFiEmDkbtXagCbHLq70Ocb+vAMG0KbsgLD1+j TZRolOZX1ySq/VXeaMGGG/BNBqW1CXlVIx9z3EjdQ7JO1iDDJlwUPWr9DfEJehun3JBB rdLatMb2Kio6naHdPjWKKmo2BO8LxyL88udm3TRkL79eQwm24gjXwJDghWENhuSdhEE4 4rL1FP9trALpVvLQMTRmmLTfuAWn/19eWsSBb/yUjVLXfQa5dpV73jVECmPiNRKkhn4d K3hw==
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=52T0UVkweIO5g6vbygxGOOkcYuwbOa3js0cqIpcPqwQ=; b=h8fXUHBOpln9UmGvepvhJzOe4fyVSZU+JeyxEdB88wv2gQy/+dfdX8bmtiFwpq8z3W DBtVKyydZ7HlK2pc0hJvbGD7YxB6pVxWaXE3KeA7DDW3Ox89bk6oTDMHqoimdh0mYdzs fSIPttKMeyy5fuDbvxmc98joa3+SkVQQkC2Ffsy47ytw/CIbV54R7hvIE8PGQ3OS2cqQ LqldBPW2JQvwQdsZnVMR3No+QktWAhQ8iPO8TO+fRsf50NSs5F6kv0ZE+urWuZcEYWzs h/JttC6f7SODWj+QQk6SLJGAfua2u4WTZ01mxIxg+3LqfGhMXjlGa3DoyFvViwwYMxbX 9Z6g==
X-Gm-Message-State: AOPr4FWPaHjWrG1MJuuvBUAR5S1JPMbelphNsf9wpxTt8YDEXH6MiUp5Z/4593OQnzxHI0peHK9JUY+pSazcgw==
X-Received: by 10.112.227.71 with SMTP id ry7mr8988094lbc.78.1460734628006; Fri, 15 Apr 2016 08:37:08 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.25.213.19 with HTTP; Fri, 15 Apr 2016 08:36:28 -0700 (PDT)
X-Originating-IP: [71.233.41.235]
In-Reply-To: <CAMm+LwiymMc=mqqdj9hupG7AoJMCxxJY7oz7DAX6K1zJ6H3g9g@mail.gmail.com>
References: <CAMm+Lwg-HTYCv2pGt=SP2+Xjoko6GcJ73kVzqXC1LBTOMDKV_A@mail.gmail.com> <CB8FC0F5-DD04-4478-AC41-09B4F8BA583B@asgard.org> <CAMm+LwiymMc=mqqdj9hupG7AoJMCxxJY7oz7DAX6K1zJ6H3g9g@mail.gmail.com>
From: Ted Lemon <mellon@fugue.com>
Date: Fri, 15 Apr 2016 11:36:28 -0400
Message-ID: <CAPt1N1kNAU+iKhFycE2mO3gjOh-43pRRxA3NpTyi3+A=x-85QQ@mail.gmail.com>
Subject: Re: Time to kill layer 2
To: Phillip Hallam-Baker <phill@hallambaker.com>
Content-Type: multipart/alternative; boundary=001a11347e8e9d21ab053087c851
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/3NOA68FW_H6KUZVKHkH0N1VI36U>
Cc: IETF Discussion Mailing List <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: Fri, 15 Apr 2016 15:37:17 -0000

--001a11347e8e9d21ab053087c851
Content-Type: text/plain; charset=UTF-8

There's a very interesting discussion about NetJSON as a management
strategy for homenets going on on the babel mailing list right now.   There
is a very cool but not very informative demo here:
http://ninux-graph.netjson.org/topology/e384464c-d1d2-4af3-aae1-4e852a28d956/

The thread is here:
https://mailarchive.ietf.org/arch/search/?email_list=babel&gbt=1&index=MSVfepqNBnEahhioJocbbCqHODg

(Subject line: NetJSON outreach)


On Fri, Apr 15, 2016 at 11:29 AM, Phillip Hallam-Baker <
phill@hallambaker.com> wrote:

> On Fri, Apr 15, 2016 at 11:07 AM, Time Warner Cable <Lee@asgard.org>
> wrote:
>
> > On 4/14/16, 8:59 AM, "ietf on behalf of Phillip Hallam-Baker" <
> ietf-bounces@ietf.org on behalf of phill@hallambaker.com> wrote:
>
> >>All this networking gear is presented to me as black boxes over which
> >>I have absolutely no control (which is fine-ish) and no visibility.
> >
> > What visibility do you want? Error messages on the printer's console?
> > Syslog messages?
> > SNMP traps? Oh, apparently not, since "SNMP isn't available most
> ordinary people."
>
> What I would like is something like a WiFi certification scheme that
> means 'there is a collection of technology here that is sufficient and
> complete'.
>
> Right now I would have to pay a ridiculous amount of money to get SNMP
> support because it is positioned as a differentiator between SOHO and
> 'enterprise' class devices.
>
> Getting the feedback necessary to make it work should not be an
> 'enterprise' feature.
>
>
> >>What should have happened many moons ago was that DHCP should have
> >>become a bidirectional protocol or a bootstrap to a bidirectional
> >>protocol. So when a printer joins the network, it authenticates and
> >>tells the network what it is. And this is all defined in one set of
> >>specifications from one organization, none of which assumes that
> >>security is an 'advanced', 'optional' or 'enterprise' feature.
> >
> > See Homenet.
>
> That seems to be premised on the assumption that the home network will
> be a simplified version of today's enterprise network rather than
> having far more moving parts.
>
>

--001a11347e8e9d21ab053087c851
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">There&#39;s a very interesting discussion about NetJSON as=
 a management strategy for homenets going on on the babel mailing list righ=
t now. =C2=A0 There is a very cool but not very informative demo here:=C2=
=A0<a href=3D"http://ninux-graph.netjson.org/topology/e384464c-d1d2-4af3-aa=
e1-4e852a28d956/">http://ninux-graph.netjson.org/topology/e384464c-d1d2-4af=
3-aae1-4e852a28d956/</a><div><br></div><div>The thread is here:=C2=A0<a hre=
f=3D"https://mailarchive.ietf.org/arch/search/?email_list=3Dbabel&amp;gbt=
=3D1&amp;index=3DMSVfepqNBnEahhioJocbbCqHODg">https://mailarchive.ietf.org/=
arch/search/?email_list=3Dbabel&amp;gbt=3D1&amp;index=3DMSVfepqNBnEahhioJoc=
bbCqHODg</a></div><div><br></div><div>(Subject line: NetJSON outreach)</div=
><div><br></div></div><div class=3D"gmail_extra"><br><div class=3D"gmail_qu=
ote">On Fri, Apr 15, 2016 at 11:29 AM, Phillip Hallam-Baker <span dir=3D"lt=
r">&lt;<a href=3D"mailto:phill@hallambaker.com" target=3D"_blank">phill@hal=
lambaker.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" sty=
le=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span =
class=3D"">On Fri, Apr 15, 2016 at 11:07 AM, Time Warner Cable &lt;<a href=
=3D"mailto:Lee@asgard.org">Lee@asgard.org</a>&gt; wrote:<br>
<br>
&gt; On 4/14/16, 8:59 AM, &quot;ietf on behalf of Phillip Hallam-Baker&quot=
; &lt;<a href=3D"mailto:ietf-bounces@ietf.org">ietf-bounces@ietf.org</a> on=
 behalf of <a href=3D"mailto:phill@hallambaker.com">phill@hallambaker.com</=
a>&gt; wrote:<br>
<br>
</span><span class=3D"">&gt;&gt;All this networking gear is presented to me=
 as black boxes over which<br>
&gt;&gt;I have absolutely no control (which is fine-ish) and no visibility.=
<br>
&gt;<br>
&gt; What visibility do you want? Error messages on the printer&#39;s conso=
le?<br>
&gt; Syslog messages?<br>
&gt; SNMP traps? Oh, apparently not, since &quot;SNMP isn&#39;t available m=
ost ordinary people.&quot;<br>
<br>
</span>What I would like is something like a WiFi certification scheme that=
<br>
means &#39;there is a collection of technology here that is sufficient and<=
br>
complete&#39;.<br>
<br>
Right now I would have to pay a ridiculous amount of money to get SNMP<br>
support because it is positioned as a differentiator between SOHO and<br>
&#39;enterprise&#39; class devices.<br>
<br>
Getting the feedback necessary to make it work should not be an<br>
&#39;enterprise&#39; feature.<br>
<span class=3D""><br>
<br>
&gt;&gt;What should have happened many moons ago was that DHCP should have<=
br>
&gt;&gt;become a bidirectional protocol or a bootstrap to a bidirectional<b=
r>
&gt;&gt;protocol. So when a printer joins the network, it authenticates and=
<br>
&gt;&gt;tells the network what it is. And this is all defined in one set of=
<br>
&gt;&gt;specifications from one organization, none of which assumes that<br=
>
&gt;&gt;security is an &#39;advanced&#39;, &#39;optional&#39; or &#39;enter=
prise&#39; feature.<br>
&gt;<br>
&gt; See Homenet.<br>
<br>
</span>That seems to be premised on the assumption that the home network wi=
ll<br>
be a simplified version of today&#39;s enterprise network rather than<br>
having far more moving parts.<br>
<br>
</blockquote></div><br></div>

--001a11347e8e9d21ab053087c851--


From nobody Fri Apr 15 08:48:07 2016
Return-Path: <mcr+ietf@sandelman.ca>
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 8606D12DF42; Fri, 15 Apr 2016 08:48:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.897
X-Spam-Level: 
X-Spam-Status: No, score=-2.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.996, SPF_PASS=-0.001] 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 9FWMn2ZxJ2o5; Fri, 15 Apr 2016 08:48:01 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B5C7D12DF0A; Fri, 15 Apr 2016 08:48:01 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 8EB6A203B7; Fri, 15 Apr 2016 11:52:04 -0400 (EDT)
Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id D4BCB6375A; Fri, 15 Apr 2016 11:48:00 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Meetecho IETF support <ietf@meetecho.com>
Subject: Re: [vmeet] IETF95 remote attendance
In-Reply-To: <5710CA7F.3050207@meetecho.com>
References: <5710CA7F.3050207@meetecho.com>
X-Mailer: MH-E 8.6; nmh 1.6+dev; GNU Emacs 24.4.2
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Fri, 15 Apr 2016 11:48:00 -0400
Message-ID: <1204.1460735280@obiwan.sandelman.ca>
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/EYR2rz5QfY4hk5xTf61NWb5ALNw>
Cc: ietf@ietf.org, vmeet@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: Fri, 15 Apr 2016 15:48:02 -0000

--=-=-=
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable


Meetecho IETF support <ietf@meetecho.com> wrote:
    > - 621 registered remote participants.

    > - 712 unique remote participants joined Meetecho through the week;
    > among these, 282 opted to also put their Registration ID.

These numbers seem weird.
621 people registered, but then somewhere between 339 and 430 of them decid=
ed
not to put in their ID.
Clearly 91 people attended without having registered.

Some people might have put their registration in sometimes, and not other
times?    Would that couild as two?

If someone didn't put their number in for multiple sessions, would that cou=
nt
as multiple?

Well, it says "712 unique".. how was that uniqueness determined, if not thr=
ough IDs?=20
If I used different devices (work/home/tablet/laptop) would that cound as
multiple?

I'm very impressed with the numbers: something like 50% of participants wer=
e remote.

=2D-=20
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -=3D IPv6 IoT consulting =3D-




--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQEVAwUBVxENLoCLcPvd0N1lAQI+sAgAg9qGPTXdgAzEFWbQm/QIFGBLG7PS8phq
9su7XoVmfd1WL67iNyAXwnAmel4NSnPHksiqVccZx5yhhkX4wZoi4Yp6zvxfzSie
IhkpxB2PVLt4B6N7FxIH1mctTZPhAZIzUvRo/WcZN98FuzZLQ6zENH2XYzN+j9N/
bXEwQzHBkNhaqU7Q8GfTBorU79V0fg8qlaE83cdh8UerL4fUaoLW0Wm+/WUlymkT
7hTV4BL4CsOrMfLF3byIQRfJpgzcoLOusP8wV+Cw8YXc4SEa7nwQwed7t0rRdcPg
KaTlKayQn33gnN0o45o017ea/P+9KMXdwWVKhucgY7l0nB1yRiJE2A==
=2QCJ
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Fri Apr 15 08:58:45 2016
Return-Path: <swmike@swm.pp.se>
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 82D3C12D6DA; Fri, 15 Apr 2016 08:58:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.297
X-Spam-Level: 
X-Spam-Status: No, score=-5.297 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.996, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=swm.pp.se
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 07xx1H9y1XUR; Fri, 15 Apr 2016 08:58:36 -0700 (PDT)
Received: from uplift.swm.pp.se (swm.pp.se [212.247.200.143]) (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 A449612DB8B; Fri, 15 Apr 2016 08:58:36 -0700 (PDT)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id 7FB82A2; Fri, 15 Apr 2016 17:58:34 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1460735914; bh=DopkuBcHu/I8fX2cFG7/3vTR7jeV5pIeyQPtYhyCous=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=nbgAk1YdoMjlCwCPTLm/o5KOOak/dgfmpCv+dAO8LB6SyCbknM2qPk7hYbqPiDtT5 rURX5DAPGl5myfXywARicTw5On3Yl+bNQqhFBnrs2osGQwcdzLbgniXc4mANjS1Gg8 O2/+PD5pKnUakoLjnd1goqAxpQgcBTLoqb04MXTc=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 773B9A1; Fri, 15 Apr 2016 17:58:34 +0200 (CEST)
Date: Fri, 15 Apr 2016 17:58:34 +0200 (CEST)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Meetecho IETF support <ietf@meetecho.com>
Subject: Re: IETF95 remote attendance
In-Reply-To: <5710CA7F.3050207@meetecho.com>
Message-ID: <alpine.DEB.2.02.1604151756570.16013@uplift.swm.pp.se>
References: <5710CA7F.3050207@meetecho.com>
User-Agent: Alpine 2.02 (DEB 1266 2009-07-14)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/sMeFHbCVmMka40q9yj600GlT3fI>
Cc: ietf@ietf.org, vmeet@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: Fri, 15 Apr 2016 15:58:42 -0000

On Fri, 15 Apr 2016, Meetecho IETF support wrote:

>
> - 1976 accesses to Meetecho (multiple accesses by the same user within the 
> same session are counted only once).
>
> - 621 registered remote participants.
>
> - 712 unique remote participants joined Meetecho through the week; among 
> these, 282 opted to also put their Registration ID.

I attended at least 5 different sessions using Meetecho, didn't register 
my meeting ID (because I couldn't get it to work). I was sitting in the 
session room on the "ietf" wifi, primarily using Meetecho to fulfil my 
jabber scribe duties.

Was I counted as remote attendee?

-- 
Mikael Abrahamsson    email: swmike@swm.pp.se


From nobody Fri Apr 15 09:00:49 2016
Return-Path: <swmike@swm.pp.se>
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 D7F3C12D779; Fri, 15 Apr 2016 09:00:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.297
X-Spam-Level: 
X-Spam-Status: No, score=-5.297 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.996, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=swm.pp.se
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 RSu8Xm6wDZsE; Fri, 15 Apr 2016 09:00:32 -0700 (PDT)
Received: from uplift.swm.pp.se (swm.pp.se [212.247.200.143]) (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 4394512D7E3; Fri, 15 Apr 2016 09:00:32 -0700 (PDT)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id A2B4CA2; Fri, 15 Apr 2016 18:00:30 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1460736030; bh=JVPO78B3VPAxD1RNP1vwypIOP+MFZAjMm5BvHSi2tC4=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=Djv5VMbtDRvrCV8qFoRZc0doX7pXuOwjqwfa4XAnOciPNTf2pZqRsbQbIaiFBAiBi XfF0KvN00eC95JFI9fk/0z2utHa8Llro0VTZlRAEESI5sDLRDq1g8ADpcmfyMkHp1l Qv0qCqfl6dkaOUyDrC+w07le+OQMIAz43PqBEAow=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 9DED1A1; Fri, 15 Apr 2016 18:00:30 +0200 (CEST)
Date: Fri, 15 Apr 2016 18:00:30 +0200 (CEST)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Meetecho IETF support <ietf@meetecho.com>
Subject: Re: IETF95 remote attendance
In-Reply-To: <alpine.DEB.2.02.1604151756570.16013@uplift.swm.pp.se>
Message-ID: <alpine.DEB.2.02.1604151759050.16013@uplift.swm.pp.se>
References: <5710CA7F.3050207@meetecho.com> <alpine.DEB.2.02.1604151756570.16013@uplift.swm.pp.se>
User-Agent: Alpine 2.02 (DEB 1266 2009-07-14)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/iXD6ET57ejq35mBGxpBsUJBLhb4>
Cc: ietf@ietf.org, vmeet@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: Fri, 15 Apr 2016 16:00:35 -0000

On Fri, 15 Apr 2016, Mikael Abrahamsson wrote:

> Was I counted as remote attendee?

Oh, also I sometimes used

"Mikael","Abrahamsson" as first and last name, sometimes "Mikael" 
,"Abrahamsson (scribe)", and at least once I had to use (I believe) 
"Mikael","Abrahamsson2" because I was disconnected mid-session because the 
wifi connectivity broke.

How were all of these counted?

-- 
Mikael Abrahamsson    email: swmike@swm.pp.se


From nobody Fri Apr 15 09:12:26 2016
Return-Path: <ietf@meetecho.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 D00CF12D870 for <ietf@ietfa.amsl.com>; Fri, 15 Apr 2016 09:12:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.921
X-Spam-Level: 
X-Spam-Status: No, score=-1.921 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=unavailable 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 dT37MlRwxcid for <ietf@ietfa.amsl.com>; Fri, 15 Apr 2016 09:12:16 -0700 (PDT)
Received: from smtpcmd04134.aruba.it (smtpcmd04134.aruba.it [62.149.158.134]) by ietfa.amsl.com (Postfix) with ESMTP id 51C7812DC11 for <ietf@ietf.org>; Fri, 15 Apr 2016 09:12:16 -0700 (PDT)
Received: from [192.168.1.106] ([151.77.134.3]) by smtpcmd04.ad.aruba.it with bizsmtp id igCC1s02A04Zlvb01gCD9E; Fri, 15 Apr 2016 18:12:15 +0200
Subject: Re: IETF95 remote attendance
To: Mikael Abrahamsson <swmike@swm.pp.se>
References: <5710CA7F.3050207@meetecho.com> <alpine.DEB.2.02.1604151756570.16013@uplift.swm.pp.se>
From: Meetecho IETF support <ietf@meetecho.com>
Message-ID: <571112D7.9020300@meetecho.com>
Date: Fri, 15 Apr 2016 18:12:07 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.7.1
MIME-Version: 1.0
In-Reply-To: <alpine.DEB.2.02.1604151756570.16013@uplift.swm.pp.se>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/WtPbNibfcd2Ofp9778UA8HWmibY>
Cc: ietf@ietf.org, vmeet@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: Fri, 15 Apr 2016 16:12:23 -0000

Il 15/04/2016 17:58, Mikael Abrahamsson ha scritto:
> On Fri, 15 Apr 2016, Meetecho IETF support wrote:
>
>>
>> - 1976 accesses to Meetecho (multiple accesses by the same user within
>> the same session are counted only once).
>>
>> - 621 registered remote participants.
>>
>> - 712 unique remote participants joined Meetecho through the week;
>> among these, 282 opted to also put their Registration ID.
>
> I attended at least 5 different sessions using Meetecho, didn't register
> my meeting ID (because I couldn't get it to work). I was sitting in the
> session room on the "ietf" wifi, primarily using Meetecho to fulfil my
> jabber scribe duties.
>
> Was I counted as remote attendee?
>

Yes.

We'll share some more data shortly, where we also distinguish between 
"remote participants" and "on-site remote participants", on a per 
session basis.


From nobody Fri Apr 15 10:08:12 2016
Return-Path: <tony@att.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 2F1D512E5E8; Fri, 15 Apr 2016 10:08:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.58
X-Spam-Level: 
X-Spam-Status: No, score=-1.58 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MISSING_HEADERS=1.021, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001] autolearn=no 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 26W2yZm5IslI; Fri, 15 Apr 2016 10:08:08 -0700 (PDT)
Received: from mx0a-00191d01.pphosted.com (mx0a-00191d01.pphosted.com [67.231.149.140]) (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 668E712E5CA; Fri, 15 Apr 2016 10:08:08 -0700 (PDT)
Received: from pps.filterd (m0053301.ppops.net [127.0.0.1]) by mx0a-00191d01.pphosted.com (8.16.0.11/8.16.0.11) with SMTP id u3FH4In0022924; Fri, 15 Apr 2016 13:08:08 -0400
Received: from alpi155.enaf.aldc.att.com (sbcsmtp7.sbc.com [144.160.229.24]) by mx0a-00191d01.pphosted.com with ESMTP id 22b44s8gb2-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Fri, 15 Apr 2016 13:08:07 -0400
Received: from enaf.aldc.att.com (localhost [127.0.0.1]) by alpi155.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id u3FH86A3029608; Fri, 15 Apr 2016 13:08:06 -0400
Received: from mlpi408.sfdc.sbc.com (mlpi408.sfdc.sbc.com [130.9.128.240]) by alpi155.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id u3FH7sto029287 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 15 Apr 2016 13:08:00 -0400
Received: from MISOUT7MSGHUBAF.ITServices.sbc.com (MISOUT7MSGHUBAF.itservices.sbc.com [130.9.129.150]) by mlpi408.sfdc.sbc.com (RSA Interceptor); Fri, 15 Apr 2016 17:07:41 GMT
Received: from MISOUT7MSGUSRCG.ITServices.sbc.com ([169.254.7.64]) by MISOUT7MSGHUBAF.ITServices.sbc.com ([130.9.129.150]) with mapi id 14.03.0248.002; Fri, 15 Apr 2016 13:07:41 -0400
From: "HANSEN, TONY L" <tony@att.com>
Subject: Re: [vmeet] IETF95 remote attendance
Thread-Topic: [vmeet] IETF95 remote attendance
Thread-Index: AQHRlw3iy5VdOE1Z0U+u5O6blmxD2Z+LM7iAgAAQzgA=
Date: Fri, 15 Apr 2016 17:07:40 +0000
Message-ID: <275306E4-F577-4CF1-B089-B594A0201EAE@att.com>
References: <5710CA7F.3050207@meetecho.com> <5710CE07.9090104@gmail.com> <CABtrr-W4bmaG2vEEokbwCLED2P9_eiEgmeM2zHO8-RQUt7BZ0Q@mail.gmail.com> <5710D983.5040006@meetecho.com>
In-Reply-To: <5710D983.5040006@meetecho.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.110.240.243]
Content-Type: text/plain; charset="utf-8"
Content-ID: <4C71E8A1C69AB343B51039B8381145DB@LOCAL>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-RSA-Inspected: yes
X-RSA-Classifications: public
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2016-04-15_13:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_policy_notspam policy=outbound_policy 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-1603290000 definitions=main-1604150242
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/RMWvgVtzPiiCRIEqhfkgEk8Wmf0>
Cc: IETF Discussion Mailing List <ietf@ietf.org>, "vmeet@ietf.org" <vmeet@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: Fri, 15 Apr 2016 17:08:10 -0000

T24gNC8xNS8xNiwgODowNyBBTSwgInZtZWV0IG9uIGJlaGFsZiBvZiBNZWV0ZWNobyBJRVRGIHN1
cHBvcnQiIDx2bWVldC1ib3VuY2VzQGlldGYub3JnIG9uIGJlaGFsZiBvZiBpZXRmQG1lZXRlY2hv
LmNvbT4gd3JvdGU6DQoNCg0KPklsIDE1LzA0LzIwMTYgMTM6NTYsIEpvc2VwaCBMb3JlbnpvIEhh
bGwgaGEgc2NyaXR0bzoNCj4+IE9uIEZyaSwgQXByIDE1LCAyMDE2IGF0IDc6MTggQU0sIFN0ZXdh
cnQgQnJ5YW50DQo+PiA8c3Rld2FydC5icnlhbnRAZ21haWwuY29tPiB3cm90ZToNCj4+Pg0KPj4+
DQo+Pj5UaGVyZSB3YXMgc29tZXRoaW5nIG9kZCBhYm91dCB0aGUgcmVnaXN0cmF0aW9uIG51bWJl
ciBzeXN0ZW0uDQo+Pj4NCj4+PiBJIHRyaWVkIHRvIGVudGVyIG15IHJlZ2lzdHJhdGlvbiBudW1i
ZXIgYSBmZXcgdGltZXMgYnV0IGl0IHJlamVjdGVkIGl0IGV2ZXJ5DQo+Pj4gdGltZS4NCj4+Pg0K
Pj4+IFNpbmNlIGl0IGRpZCBub3QgUkVRVUlSRShzaWMpICB0aGUgcmVnaXN0cmF0aW9uIG51bWJl
ciAgSSBqdXN0IHVzZWQgdGhlDQo+Pj4gb3B0aW9uIG5vdCB0byBlbnRlciBpdC4NCj4+DQo+PiBJ
IGhhZCB0byBlbnRlciAiSm9zZXBoIEhhbGwiIGluc3RlYWQgb2YgIkpvZSBIYWxsIiB0byBnZXQg
aXQgdG8gdGFrZSBteSBSZWcuIElELg0KPj4NCj4NCj5Zb3VyIGZpcnN0IGFuZCBsYXN0IG5hbWUg
bXVzdCBiZSBpZGVudGljYWwgdG8gdGhlIG5hbWUgdXNlZCB0byByZWdpc3Rlci4NCg0KRXZlbiBt
b3JlIHJlYXNvbiBmb3IgdGhlIHNvZnR3YXJlIHRvIHJlbWVtYmVyIHRoZSBkYXRhLCB1c2luZyBj
b29raWVzIG9yIHdoYXRldmVyLCBzbyB3ZSBkb24ndCBoYXZlIHRvIGNvbnRpbnVlIHJlLXR5cGlu
ZyBpdCBpbi4NCg0KCVRvbnkNCg==


From nobody Fri Apr 15 10:12:00 2016
Return-Path: <paul@nohats.ca>
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 783D112E62B for <ietf@ietfa.amsl.com>; Fri, 15 Apr 2016 10:11:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level: 
X-Spam-Status: No, score=-2.096 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_ALL=0.8, RP_MATCHES_RCVD=-0.996] autolearn=no 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 oItSmn0cXGqd for <ietf@ietfa.amsl.com>; Fri, 15 Apr 2016 10:11:56 -0700 (PDT)
Received: from mx.nohats.ca (mx.nohats.ca [193.110.157.68]) (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 5504B12E668 for <ietf@ietf.org>; Fri, 15 Apr 2016 10:11:54 -0700 (PDT)
Received: from localhost (localhost [IPv6:::1]) by mx.nohats.ca (Postfix) with ESMTP id 3qmkbh5gn0zHYQ for <ietf@ietf.org>; Fri, 15 Apr 2016 19:11:44 +0200 (CEST)
X-OPENPGPKEY: Message passed unmodified
X-Virus-Scanned: amavisd-new at mx.nohats.ca
Received: from mx.nohats.ca ([IPv6:::1]) by localhost (mx.nohats.ca [IPv6:::1]) (amavisd-new, port 10024) with ESMTP id 2EuHsuPmEX3T for <ietf@ietf.org>; Fri, 15 Apr 2016 19:11:42 +0200 (CEST)
Received: from ns0.nohats.ca (ns0.nohats.ca [IPv6:2a03:6000:1004:1::102]) by mx.nohats.ca (Postfix) with ESMTP for <ietf@ietf.org>; Fri, 15 Apr 2016 19:11:42 +0200 (CEST)
Received: by ns0.nohats.ca (Postfix, from userid 500) id EA8CB4278C; Fri, 15 Apr 2016 13:11:40 -0400 (EDT)
Received: from localhost (localhost [127.0.0.1]) by ns0.nohats.ca (Postfix) with ESMTP id E455841277 for <ietf@ietf.org>; Fri, 15 Apr 2016 13:11:40 -0400 (EDT)
Date: Fri, 15 Apr 2016 13:11:39 -0400 (EDT)
From: paul@nohats.ca
To: ietf@ietf.org
Subject: spam on old lists - was [89attendees] Fw: new important message (fwd)
Message-ID: <alpine.LRH.2.20.1604151309440.27222@ns0.nohats.ca>
User-Agent: Alpine 2.20 (LRH 67 2015-01-07)
MIME-Version: 1.0
Content-Type: multipart/mixed; BOUNDARY="===============0871110775886981789=="
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/NoMCgEZQsKkdNd6MqVxvZ3UGT8A>
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: Fri, 15 Apr 2016 17:11:58 -0000

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.

--===============0871110775886981789==
Content-Type: text/plain; CHARSET=US-ASCII; format=flowed


Can we have a process where we disallow posting by _everyone_ on the
attendees lists of previous IETF meetings? I think after 4 months there
is no valid reason for allowing to post on those old lists anymore.

Paul

---------- Forwarded message ----------
Date: Wed, 13 Apr 2016 09:15:12
From: bensons@queuefull.net
To: 89attendees <89attendees@ietf.org>,
     Alexandru Petrescu <alexandru.petrescu@gmail.com>,
     Antoin Verschuren <antoin.verschuren@sidn.nl>,
     Arran Cudbard-Bell <a.cudbardb@freeradius.org>,
     Dave Cottlehuber <dch@skunkwerks.at>
Subject: [89attendees] Fw: new important message

[ spam deleted]
--===============0871110775886981789==
Content-Type: text/plain; CHARSET=us-ascii
Content-ID: <alpine.LRH.2.20.1604151309441.27222@ns0.nohats.ca>
Content-Description: 
Content-Disposition: INLINE

_______________________________________________
89attendees mailing list
89attendees@ietf.org
https://www.ietf.org/mailman/listinfo/89attendees

--===============0871110775886981789==--


From nobody Fri Apr 15 10:21:37 2016
Return-Path: <ietf@meetecho.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 E7CDF12E6DE for <ietf@ietfa.amsl.com>; Fri, 15 Apr 2016 10:21:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.921
X-Spam-Level: 
X-Spam-Status: No, score=-1.921 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] 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 88LTyazu-8sQ for <ietf@ietfa.amsl.com>; Fri, 15 Apr 2016 10:21:34 -0700 (PDT)
Received: from smtpcmd04134.aruba.it (smtpcmd04134.aruba.it [62.149.158.134]) by ietfa.amsl.com (Postfix) with ESMTP id 0F80A12E6CD for <ietf@ietf.org>; Fri, 15 Apr 2016 10:21:33 -0700 (PDT)
Received: from [192.168.1.106] ([151.77.134.3]) by smtpcmd04.ad.aruba.it with bizsmtp id ihMX1s00r04Zlvb01hMXZ6; Fri, 15 Apr 2016 19:21:32 +0200
Subject: Re: IETF95 remote attendance
To: Mikael Abrahamsson <swmike@swm.pp.se>
References: <5710CA7F.3050207@meetecho.com> <alpine.DEB.2.02.1604151756570.16013@uplift.swm.pp.se> <alpine.DEB.2.02.1604151759050.16013@uplift.swm.pp.se>
From: Meetecho IETF support <ietf@meetecho.com>
Message-ID: <57112316.3060007@meetecho.com>
Date: Fri, 15 Apr 2016 19:21:26 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.7.1
MIME-Version: 1.0
In-Reply-To: <alpine.DEB.2.02.1604151759050.16013@uplift.swm.pp.se>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/uMlhdgiWObwiFpjllvBfKZFn7RA>
Cc: ietf@ietf.org, vmeet@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: Fri, 15 Apr 2016 17:21:36 -0000

Il 15/04/2016 18:00, Mikael Abrahamsson ha scritto:
> On Fri, 15 Apr 2016, Mikael Abrahamsson wrote:
>
>> Was I counted as remote attendee?
>
> Oh, also I sometimes used
>
> "Mikael","Abrahamsson" as first and last name, sometimes "Mikael"
> ,"Abrahamsson (scribe)", and at least once I had to use (I believe)
> "Mikael","Abrahamsson2" because I was disconnected mid-session because
> the wifi connectivity broke.
>
> How were all of these counted?
>

It's not easy to answer this question.

We tried to eliminate duplicates as much as possible. Unique names were 
computed by also taking into account IP addresses, stripping off the 
"_1234" suffix that Meetecho automatically adds when a username is 
already picked, and some other parameters. But it's still possible that 
you were counted more than once.

We believe this can give a fairly realistic flavor of remote attendance 
figures. Of course, if we mandate the use of the Registration ID, we can 
easily have the real numbers...


From nobody Fri Apr 15 10:22:44 2016
Return-Path: <rwfranks@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 97EF012E77E for <ietf@ietfa.amsl.com>; Fri, 15 Apr 2016 10:22:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.399
X-Spam-Level: 
X-Spam-Status: No, score=-2.399 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.199, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 SMADVShRLVdt for <ietf@ietfa.amsl.com>; Fri, 15 Apr 2016 10:22:41 -0700 (PDT)
Received: from mail-oi0-x235.google.com (mail-oi0-x235.google.com [IPv6:2607:f8b0:4003:c06::235]) (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 4E0B612E747 for <ietf@ietf.org>; Fri, 15 Apr 2016 10:22:41 -0700 (PDT)
Received: by mail-oi0-x235.google.com with SMTP id s79so130524098oie.1 for <ietf@ietf.org>; Fri, 15 Apr 2016 10:22:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=2HMYtupWj9kB039DlovDQRBLQtQ+Q9ybYojQR7SQsm8=; b=CWc2THcSvE/iYhT6jwzwZMNGMGa5UdQwmjJi/qTiDOPzNsGYYrHgwlRj+DQCm0uSx3 wOkoGWs1nwR31KLHDbBrJR7scFqp/MBsDvkiGi7fjfztRlLvNCVcK5bAiovVVMhH1k23 3aXQB8cAcmuBwAlcFg9VLuwT+6zwsMqH9ySQI3p+fxfE8eAk9H92hKzXEX/9ee2xFDFH wZWW/p47lkuktusLp6nEdpsb9Bx2UZRVeN1oZ8R7BdQofsEKN1K1bqTflfv9S6NIkf6M O2GzWlS7ECWm7hrxteTWbZ6VsGo76HOr3u6Vmr/sPLkmLfx19HsIeElMfwvSdATp3h2M TAEw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=2HMYtupWj9kB039DlovDQRBLQtQ+Q9ybYojQR7SQsm8=; b=lDGjW8D0oF97bK7QeOEDoBdRk4lKFUhsSja0T/tGPrDEWmsb3SR8x19bo2f77iSNFs gwBeeSmCALewQsPuQbwue/vzrq075TBZRc2K5HhJwp0fBfnCFYxYehjxjLaGBdmuHCxs qCc3iCNiUodJLajU8GKO/lROt91Dzv4A4bjU1ZpLrq1Bl8JU8WtNJ9ukr2HysGPwDjtl Cmqt7LcSff0F2UbRUCkbPoQiN8t2yQO9behjtV+VnV2oZ9735xu1plxJJtZCKCbD6ooG HG0BMww0Ou8Pv0FP+4zOaoiNJ8+4VZf64Cmu7+MCd6Rm8QXyW6FMopqM93bBMBiro1vO nJNw==
X-Gm-Message-State: AOPr4FVo4u+UtzVN8xxmEKHvdH17cEwbKWFu8y7JQAHycVANCcVbFwXjfLGXwIEM94loTfveKBofZl+jDlbWMw==
X-Received: by 10.157.32.114 with SMTP id n105mr5491568ota.69.1460740960731; Fri, 15 Apr 2016 10:22:40 -0700 (PDT)
MIME-Version: 1.0
Sender: rwfranks@gmail.com
Received: by 10.182.114.136 with HTTP; Fri, 15 Apr 2016 10:22:01 -0700 (PDT)
In-Reply-To: <alpine.LRH.2.20.1604151309440.27222@ns0.nohats.ca>
References: <alpine.LRH.2.20.1604151309440.27222@ns0.nohats.ca>
From: Dick Franks <rwfranks@acm.org>
Date: Fri, 15 Apr 2016 18:22:01 +0100
X-Google-Sender-Auth: XHnVkcQGSLfUE69RAkIXOON1V9k
Message-ID: <CAKW6Ri6rzgYOZ-9xGFs5zHezbZ5RbUrVwGJag0JYKZZbft87Nw@mail.gmail.com>
Subject: Re: spam on old lists - was [89attendees] Fw: new important message (fwd)
To: Paul Wouters <paul@nohats.ca>
Content-Type: multipart/alternative; boundary=001a1137c37412c8fa0530894296
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/N6Hfb84omlYsdObkQzod2h1nUDM>
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: Fri, 15 Apr 2016 17:22:42 -0000

--001a1137c37412c8fa0530894296
Content-Type: text/plain; charset=UTF-8

On 15 April 2016 at 18:11, <paul@nohats.ca> wrote:

>
> Can we have a process where we disallow posting by _everyone_ on the
> attendees lists of previous IETF meetings? I think after 4 months there
> is no valid reason for allowing to post on those old lists anymore.
>

Is there any valid reason for the list to exist after 4 months?

--001a1137c37412c8fa0530894296
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div><div class=3D"gmail_signat=
ure"><div dir=3D"ltr"><span></span></div></div></div>
<br><div class=3D"gmail_quote">On 15 April 2016 at 18:11,  <span dir=3D"ltr=
">&lt;<a href=3D"mailto:paul@nohats.ca" target=3D"_blank">paul@nohats.ca</a=
>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 =
0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
Can we have a process where we disallow posting by _everyone_ on the<br>
attendees lists of previous IETF meetings? I think after 4 months there<br>
is no valid reason for allowing to post on those old lists anymore.<br></bl=
ockquote><div><br></div><div>Is there any valid reason for the list to exis=
t after 4 months? <br></div><div><br>=C2=A0<br></div></div></div></div>

--001a1137c37412c8fa0530894296--


From nobody Fri Apr 15 10:27:21 2016
Return-Path: <prvs=191307ffb3=jordi.palet@consulintel.es>
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 6BB4312E7E4 for <ietf@ietfa.amsl.com>; Fri, 15 Apr 2016 10:27:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.899
X-Spam-Level: 
X-Spam-Status: No, score=-101.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_QP_LONG_LINE=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 lvbNgAt41mwg for <ietf@ietfa.amsl.com>; Fri, 15 Apr 2016 10:27:17 -0700 (PDT)
Received: from mail.consulintel.com (mail.consulintel.com [213.0.69.132]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 152F012E7E2 for <ietf@ietf.org>; Fri, 15 Apr 2016 10:27:16 -0700 (PDT)
X-MDAV-Processed: mail.consulintel.com, Fri, 15 Apr 2016 19:27:14 +0200
Received: from [10.10.10.212] by mail.consulintel.com (MDaemon PRO v11.0.3) with ESMTP id md50000394098.msg for <ietf@ietf.org>; Fri, 15 Apr 2016 19:27:12 +0200
X-Spam-Processed: mail.consulintel.com, Fri, 15 Apr 2016 19:27:12 +0200 (not processed: spam filter heuristic analysis disabled)
X-MDOP-RefID: re=0.000,fgs=0 (_st=1 _vt=0 _iwf=0)
X-Return-Path: prvs=191307ffb3=jordi.palet@consulintel.es
X-Envelope-From: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: ietf@ietf.org
User-Agent: Microsoft-MacOutlook/0.0.0.160212
Date: Fri, 15 Apr 2016 19:27:10 +0200
Subject: Re: spam on old lists - was [89attendees] Fw: new important message
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: IETF discussion list <ietf@ietf.org>
Message-ID: <00DFA933-A21B-4C0C-AFC8-319FF7AA1DFD@consulintel.es>
Thread-Topic: spam on old lists - was [89attendees] Fw: new important message
References: <alpine.LRH.2.20.1604151309440.27222@ns0.nohats.ca>
In-Reply-To: <alpine.LRH.2.20.1604151309440.27222@ns0.nohats.ca>
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/UMmp84u_Icjwrs0OCG5TET9T3Ng>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: jordi.palet@consulintel.es
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: Fri, 15 Apr 2016 17:27:19 -0000

I think the problem is bigger than that.

I=E2=80=99ve not checked those specific emails headers, but some time ago, I noti=
ced that subscribers of IETF using DNS-BL black listed email servers were al=
lowed to post.

This means that if a spammer is subscribed, or an actual subscriber infecte=
d with a virus/bot/whatever, he is able to send all kind of rubbish to the l=
ist.

As a consequence of that, because my email server is configured to reject m=
essages that have an IP in any header which is DNS-BL, then my email address=
 was unsubscribed.

I exchanged a few email with AMS and IAOC, and suggested that we MUST rejec=
t any sender that is black listed. NEVER got a response back from the IAOC, =
despite having been told that they will take care of that.

Again: I really think we must reject emails coming from DNS-BL black listed=
 servers.

Is up to each postmaster to make sure that the IP addresses of his/her serv=
ers are not listed in DNS-BL and his network free of malware that can create=
 problems to others.

May be some day, someone at the IAOC can take care of this =E2=80=A6 instead of i=
gnoring our complains.

Regards,
Jordi








-----Mensaje original-----
De: ietf <ietf-bounces@ietf.org> en nombre de <paul@nohats.ca>
Responder a: <paul@nohats.ca>
Fecha: viernes, 15 de abril de 2016, 19:11
Para: <ietf@ietf.org>
Asunto: spam on old lists - was [89attendees] Fw: new important message (fw=
d)

>
>Can we have a process where we disallow posting by _everyone_ on the
>attendees lists of previous IETF meetings? I think after 4 months there
>is no valid reason for allowing to post on those old lists anymore.
>
>Paul
>
>---------- Forwarded message ----------
>Date: Wed, 13 Apr 2016 09:15:12
>From: bensons@queuefull.net
>To: 89attendees <89attendees@ietf.org>,
>     Alexandru Petrescu <alexandru.petrescu@gmail.com>,
>     Antoin Verschuren <antoin.verschuren@sidn.nl>,
>     Arran Cudbard-Bell <a.cudbardb@freeradius.org>,
>     Dave Cottlehuber <dch@skunkwerks.at>
>Subject: [89attendees] Fw: new important message
>
>[ spam deleted]_______________________________________________
>89attendees mailing list
>89attendees@ietf.org
>https://www.ietf.org/mailman/listinfo/89attendees



From nobody Fri Apr 15 10:45:35 2016
Return-Path: <ietf@meetecho.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 72ADB12E0F7 for <ietf@ietfa.amsl.com>; Fri, 15 Apr 2016 10:45:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.921
X-Spam-Level: 
X-Spam-Status: No, score=-1.921 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=unavailable 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 psKCg1EEh2ws for <ietf@ietfa.amsl.com>; Fri, 15 Apr 2016 10:45:30 -0700 (PDT)
Received: from smtpcmd04134.aruba.it (smtpcmd04134.aruba.it [62.149.158.134]) by ietfa.amsl.com (Postfix) with ESMTP id 9EBEB12DF6F for <ietf@ietf.org>; Fri, 15 Apr 2016 10:45:29 -0700 (PDT)
Received: from [192.168.1.106] ([151.77.134.3]) by smtpcmd04.ad.aruba.it with bizsmtp id ihlT1s01104Zlvb01hlTky; Fri, 15 Apr 2016 19:45:28 +0200
Subject: Re: [vmeet] IETF95 remote attendance
To: Michael Richardson <mcr+ietf@sandelman.ca>
References: <5710CA7F.3050207@meetecho.com> <1204.1460735280@obiwan.sandelman.ca>
From: Meetecho IETF support <ietf@meetecho.com>
Message-ID: <571128B2.7010702@meetecho.com>
Date: Fri, 15 Apr 2016 19:45:22 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.7.1
MIME-Version: 1.0
In-Reply-To: <1204.1460735280@obiwan.sandelman.ca>
Content-Type: text/plain; charset=iso-8859-15; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/zVKBSKtonJE2BY6XjXrJxXRxYtE>
Cc: ietf@ietf.org, vmeet@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: Fri, 15 Apr 2016 17:45:32 -0000

Il 15/04/2016 17:48, Michael Richardson ha scritto:
>
> Meetecho IETF support <ietf@meetecho.com> wrote:
>      > - 621 registered remote participants.
>
>      > - 712 unique remote participants joined Meetecho through the week;
>      > among these, 282 opted to also put their Registration ID.
>
> These numbers seem weird.
> 621 people registered, but then somewhere between 339 and 430 of them decided
> not to put in their ID.

Well, Reg IDs are hard to remember. As there were not mandatory, our 
feeling is that a lot of people just didn't want to spend time 
retrieving the confirmation email the registration system sent them.

> Clearly 91 people attended without having registered.
>
> Some people might have put their registration in sometimes, and not other
> times?    Would that couild as two?

This actually depends on the name they used, the IP address, and some 
other parameters we take into account to minimize duplication.

>
> If someone didn't put their number in for multiple sessions, would that count
> as multiple?

See above.

>
> Well, it says "712 unique".. how was that uniqueness determined, if not through IDs?
> If I used different devices (work/home/tablet/laptop) would that cound as
> multiple?

Again, see above. :)

>
> I'm very impressed with the numbers: something like 50% of participants were remote.
>

Please remember that some remote participants were actually "on-site". 
We've even seen a couple of remote questions through the virtual queue 
from people we met in BA! ;)


From nobody Fri Apr 15 10:53:44 2016
Return-Path: <john@jlc.net>
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 B6D0312DFA4 for <ietf@ietfa.amsl.com>; Fri, 15 Apr 2016 10:53:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.861
X-Spam-Level: 
X-Spam-Status: No, score=-1.861 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_SBL_CSS=3.335, RP_MATCHES_RCVD=-0.996] autolearn=no 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 rzpw3YkYqwxo for <ietf@ietfa.amsl.com>; Fri, 15 Apr 2016 10:53:41 -0700 (PDT)
Received: from mailhost.jlc.net (mailhost.jlc.net [199.201.159.4]) by ietfa.amsl.com (Postfix) with ESMTP id 3D3E112DC99 for <ietf@ietf.org>; Fri, 15 Apr 2016 10:53:41 -0700 (PDT)
Received: by mailhost.jlc.net (Postfix, from userid 104) id 3F8ACC9417; Fri, 15 Apr 2016 13:53:36 -0400 (EDT)
Date: Fri, 15 Apr 2016 13:53:36 -0400
From: John Leslie <john@jlc.net>
To: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
Subject: Re: spam on old lists - was [89attendees] Fw: new important message
Message-ID: <20160415175336.GU3997@verdi>
References: <alpine.LRH.2.20.1604151309440.27222@ns0.nohats.ca> <00DFA933-A21B-4C0C-AFC8-319FF7AA1DFD@consulintel.es>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <00DFA933-A21B-4C0C-AFC8-319FF7AA1DFD@consulintel.es>
User-Agent: Mutt/1.4.1i
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/mIlwd-zPQ0ry5bcCpQJM_AFrlCc>
Cc: IETF discussion list <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: Fri, 15 Apr 2016 17:53:42 -0000

JORDI PALET MARTINEZ <jordi.palet@consulintel.es> wrote:
> 
> Again: I really think we must reject emails coming from DNS-BL
> black listed servers.

   In a word, No.

   I'm in a spamhaus blacklist right now (working on it!!!), and spamhaus
refuses to say why. These things happen!

   If we were seeing a higher volume of spam get through, I'd agree to
instituting a moderation-like process; but we're not, and I dislike
make-work for moderators.

   Perhaps somebody would like to work on a captca?

> Is up to each postmaster to make sure that the IP addresses of his/her
> servers are not listed in DNS-BL and his network free of malware that
> can create problems to others.

   Indeed, we try!

   But very few blacklist maintainers offer actually useful information
to help us do this.

   We _could_ in principle work up protocols to replace zero-maintenance
blacklists as "the solution" to spam. I tried, the last time the topic
was hot; but totally failed to get anything that wasn't trivial to bypass.

> May be some day, someone at the IAOC can take care of this ??? instead
> of ignoring our complains.

   How much are you contributing to the funding of that additional work?

--
John Leslie <john@jlc.net>


From nobody Fri Apr 15 11:05:13 2016
Return-Path: <paul.hoffman@vpnc.org>
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 2E40312D78F for <ietf@ietfa.amsl.com>; Fri, 15 Apr 2016 11:05:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 0uTMh4DY9ekH for <ietf@ietfa.amsl.com>; Fri, 15 Apr 2016 11:05:10 -0700 (PDT)
Received: from mail.proper.com (Opus1.Proper.COM [207.182.41.91]) (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 C744012D6F8 for <ietf@ietf.org>; Fri, 15 Apr 2016 11:05:10 -0700 (PDT)
Received: from [10.32.60.37] (142-254-101-173.dsl.dynamic.fusionbroadband.com [142.254.101.173]) (authenticated bits=0) by mail.proper.com (8.15.2/8.14.9) with ESMTPSA id u3FI592b067756 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Fri, 15 Apr 2016 11:05:10 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
X-Authentication-Warning: mail.proper.com: Host 142-254-101-173.dsl.dynamic.fusionbroadband.com [142.254.101.173] claimed to be [10.32.60.37]
From: "Paul Hoffman" <paul.hoffman@vpnc.org>
To: ietf@ietf.org
Subject: Re: Last Call: <draft-sheffer-rfc6982bis-00.txt> (Improving Awareness of Running Code: The Implementation Status Section) to Best Current Practice
Date: Fri, 15 Apr 2016 11:05:09 -0700
Message-ID: <AC22B3F8-9F5A-4380-8425-ADADCFD3C449@vpnc.org>
In-Reply-To: <20160415175943.17493.16979.idtracker@ietfa.amsl.com>
References: <20160415175943.17493.16979.idtracker@ietfa.amsl.com>
MIME-Version: 1.0
X-Mailer: MailMate (1.9.4r5234)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/XilG-RAS4_QzWczA_QUFxw_PdGM>
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: Fri, 15 Apr 2016 18:05:12 -0000

On 15 Apr 2016, at 10:59, The IESG wrote:

> The IESG has received a request from an individual submitter to consider
> the following document:
> - 'Improving Awareness of Running Code: The Implementation Status
> Section'
>   <draft-sheffer-rfc6982bis-00.txt> as Best Current Practice
>
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action. Please send substantive comments to the
> ietf@ietf.org mailing lists by 2016-05-13. Exceptionally, comments may be
> sent to iesg@ietf.org instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting.
>
> Abstract
>
>
>    This document describes a simple process that allows authors of
>    Internet-Drafts to record the status of known implementations by
>    including an Implementation Status section.  This will allow
>    reviewers and working groups to assign due consideration to documents
>    that have the benefit of running code, which may serve as evidence of
>    valuable experimentation and feedback that have made the implemented
>    protocols more mature.
>
>    This process is not mandatory.  Authors of Internet-Drafts are
>    encouraged to consider using the process for their documents, and
>    working groups are invited to think about applying the process to all
>    of their protocol specifications.  This document obsoletes RFC 6982,
>    advancing it to a Best Current Practice.

RFC 6982 seems to have worked well, and this should become a BCP.

--Paul Hoffman


From nobody Fri Apr 15 11:25:25 2016
Return-Path: <dwm@xpasc.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 A4EA512D612 for <ietf@ietfa.amsl.com>; Fri, 15 Apr 2016 11:25:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.921
X-Spam-Level: 
X-Spam-Status: No, score=-1.921 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] 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 6mIJZGoSmB-d for <ietf@ietfa.amsl.com>; Fri, 15 Apr 2016 11:25:21 -0700 (PDT)
Received: from dispatch1-us1.ppe-hosted.com (dispatch1-us1.ppe-hosted.com [67.231.154.164]) (using TLSv1.1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 366CE12D85C for <ietf@ietf.org>; Fri, 15 Apr 2016 11:25:21 -0700 (PDT)
Received: from mx1-us1.ppe-hosted.com (unknown [10.110.49.5]) by dispatch1-us1.ppe-hosted.com (Proofpoint Essentials ESMTP Server) with ESMTP id 95CFD6008F for <ietf@ietf.org>; Fri, 15 Apr 2016 18:25:20 +0000 (UTC)
X-Virus-Scanned: Proofpoint Essentials engine
Received: from xpasc.com (h-68-164-244-186.snva.ca.megapath.net [68.164.244.186]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by mx1-us1.ppe-hosted.com (Proofpoint Essentials ESMTP Server) with ESMTPS id 5C2BA8F for <ietf@ietf.org>; Fri, 15 Apr 2016 18:25:19 +0000 (UTC)
Received: from egate.xpasc.com (egate.xpasc.com [10.1.2.49]) by xpasc.com (8.13.8/8.13.8) with ESMTP id u3FIPHLe018181 for <ietf@ietf.org>; Fri, 15 Apr 2016 11:25:17 -0700
Date: Fri, 15 Apr 2016 11:25:16 -0700 (PDT)
From: David Morris <dwm@xpasc.com>
To: ietf@ietf.org
Subject: Re: spam on old lists - was [89attendees] Fw: new important message
In-Reply-To: <20160415175336.GU3997@verdi>
Message-ID: <alpine.LRH.2.01.1604151118350.13335@egate.xpasc.com>
References: <alpine.LRH.2.20.1604151309440.27222@ns0.nohats.ca> <00DFA933-A21B-4C0C-AFC8-319FF7AA1DFD@consulintel.es> <20160415175336.GU3997@verdi>
User-Agent: Alpine 2.01 (LRH 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-MDID: VaOmB7+1hZvI
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/fnQ_5P1PbicxA8dBmM3MphcmMGk>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: ietf@ietf.org
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: Fri, 15 Apr 2016 18:25:23 -0000

Having fought with DNSBL providers, I think the BLACK part of the name is
appropriate ... as in BLACK HOLE re. any hope of rational resolution. My
ISP at the time incorrectly categorized my static IP block as dynamic and
it proved impossible to get past that issue with the BL provider. It
happened at the time that it would be convenient to change ISPs and I did.
Then my email started using a hosted spam filter and my effective IPs were
kept clean by someone else. During the time I was wrangling with the BL, I
had a bounce from one ISP, but their message was complete enough
documenting their whitelist process that I think it took about 5 minutes
to fix.

On Fri, 15 Apr 2016, John Leslie wrote:

> JORDI PALET MARTINEZ <jordi.palet@consulintel.es> wrote:
> >
> > Again: I really think we must reject emails coming from DNS-BL
> > black listed servers.
>
>    In a word, No.
>
>    I'm in a spamhaus blacklist right now (working on it!!!), and spamhaus
> refuses to say why. These things happen!
>
>    If we were seeing a higher volume of spam get through, I'd agree to
> instituting a moderation-like process; but we're not, and I dislike
> make-work for moderators.
>
>    Perhaps somebody would like to work on a captca?
>
> > Is up to each postmaster to make sure that the IP addresses of his/her
> > servers are not listed in DNS-BL and his network free of malware that
> > can create problems to others.
>
>    Indeed, we try!
>
>    But very few blacklist maintainers offer actually useful information
> to help us do this.
>
>    We _could_ in principle work up protocols to replace zero-maintenance
> blacklists as "the solution" to spam. I tried, the last time the topic
> was hot; but totally failed to get anything that wasn't trivial to bypass.
>
> > May be some day, someone at the IAOC can take care of this ??? instead
> > of ignoring our complains.
>
>    How much are you contributing to the funding of that additional work?
>
> --
> John Leslie <john@jlc.net>
>
>
> ----------
>
> This email has been scanned for spam and viruses by Proofpoint Essentials. Visit the following link to report this email as spam:
> https://us1.proofpointessentials.com/index01.php?mod_id=11&mod_option=logitem&mail_id=m1w7uTVeX-2q&rid=113885848&report=1
>


From nobody Fri Apr 15 11:31:20 2016
Return-Path: <prvs=191307ffb3=jordi.palet@consulintel.es>
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 98ADE12E3FD for <ietf@ietfa.amsl.com>; Fri, 15 Apr 2016 11:31:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.899
X-Spam-Level: 
X-Spam-Status: No, score=-101.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_QP_LONG_LINE=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 Ga0v1ps4DGC5 for <ietf@ietfa.amsl.com>; Fri, 15 Apr 2016 11:31:18 -0700 (PDT)
Received: from mail.consulintel.com (mail.consulintel.com [213.0.69.132]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C7B2A12E3C3 for <ietf@ietf.org>; Fri, 15 Apr 2016 11:31:17 -0700 (PDT)
X-MDAV-Processed: mail.consulintel.com, Fri, 15 Apr 2016 20:31:14 +0200
Received: from [10.10.10.212] by mail.consulintel.com (MDaemon PRO v11.0.3) with ESMTP id md50000394147.msg for <ietf@ietf.org>; Fri, 15 Apr 2016 20:31:13 +0200
X-Spam-Processed: mail.consulintel.com, Fri, 15 Apr 2016 20:31:13 +0200 (not processed: spam filter heuristic analysis disabled)
X-MDOP-RefID: re=0.000,fgs=0 (_st=1 _vt=0 _iwf=0)
X-Return-Path: prvs=191307ffb3=jordi.palet@consulintel.es
X-Envelope-From: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: ietf@ietf.org
User-Agent: Microsoft-MacOutlook/0.0.0.160212
Date: Fri, 15 Apr 2016 20:31:10 +0200
Subject: Re: spam on old lists - was [89attendees] Fw: new important message
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: IETF discussion list <ietf@ietf.org>
Message-ID: <433046AF-64F4-486A-BBD0-251829CEEB5B@consulintel.es>
Thread-Topic: spam on old lists - was [89attendees] Fw: new important message
References: <alpine.LRH.2.20.1604151309440.27222@ns0.nohats.ca> <00DFA933-A21B-4C0C-AFC8-319FF7AA1DFD@consulintel.es> <20160415175336.GU3997@verdi>
In-Reply-To: <20160415175336.GU3997@verdi>
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/YlkA5l4K4fl065MSrK-V-_YPN0I>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: jordi.palet@consulintel.es
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: Fri, 15 Apr 2016 18:31:19 -0000

A few years ago, I=E2=80=99ve managed to get a customer out of spamhaus, despite =
having sent a SPAM because a bot, etc. I was able to find all the info about=
 how to proceed in their web site, apply to clean, etc.

Same with other similar DNS-BLs

I think if you=E2=80=99re =E2=80=9Cclean=E2=80=9D you should have not problem, and we can cho=
ose which DNS-BL to apply. If we have from the community negative reports ab=
out bad-behaviours from any of those DNS-BLs for example.

Regards,
Jordi









-----Mensaje original-----
De: ietf <ietf-bounces@ietf.org> en nombre de John Leslie <john@jlc.net>
Responder a: <john@jlc.net>
Fecha: viernes, 15 de abril de 2016, 19:53
Para: Jordi Palet Martinez <jordi.palet@consulintel.es>
CC: IETF discussion list <ietf@ietf.org>
Asunto: Re: spam on old lists - was [89attendees] Fw: new important message

>JORDI PALET MARTINEZ <jordi.palet@consulintel.es> wrote:
>>=20
>> Again: I really think we must reject emails coming from DNS-BL
>> black listed servers.
>
>   In a word, No.
>
>   I'm in a spamhaus blacklist right now (working on it!!!), and spamhaus
>refuses to say why. These things happen!
>
>   If we were seeing a higher volume of spam get through, I'd agree to
>instituting a moderation-like process; but we're not, and I dislike
>make-work for moderators.
>
>   Perhaps somebody would like to work on a captca?
>
>> Is up to each postmaster to make sure that the IP addresses of his/her
>> servers are not listed in DNS-BL and his network free of malware that
>> can create problems to others.
>
>   Indeed, we try!
>
>   But very few blacklist maintainers offer actually useful information
>to help us do this.
>
>   We _could_ in principle work up protocols to replace zero-maintenance
>blacklists as "the solution" to spam. I tried, the last time the topic
>was hot; but totally failed to get anything that wasn't trivial to bypass.
>
>> May be some day, someone at the IAOC can take care of this ??? instead
>> of ignoring our complains.
>
>   How much are you contributing to the funding of that additional work?
>
>--
>John Leslie <john@jlc.net>
>
>



From nobody Fri Apr 15 11:53:04 2016
Return-Path: <ietf@johnlevine.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 81A4512DDFF for <ietf@ietfa.amsl.com>; Fri, 15 Apr 2016 11:53:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] 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 k4juyWl9LWVu for <ietf@ietfa.amsl.com>; Fri, 15 Apr 2016 11:53:02 -0700 (PDT)
Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 045E112DDC4 for <ietf@ietf.org>; Fri, 15 Apr 2016 11:53:01 -0700 (PDT)
Received: (qmail 10058 invoked from network); 15 Apr 2016 18:53:00 -0000
Received: from unknown (64.57.183.18) by mail1.iecc.com with QMQP; 15 Apr 2016 18:53:00 -0000
Date: 15 Apr 2016 18:52:38 -0000
Message-ID: <20160415185238.6233.qmail@ary.lan>
From: ietf@johnlevine.com
To: 89attendees@ietf.org
Subject: Re: spam on old lists - was [89attendees] Fw: new important message
In-Reply-To: <alpine.LRH.2.01.1604151118350.13335@egate.xpasc.com>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/ZKWkWrhaUCM_TqUhSfUP55isL3o>
Cc: 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: Fri, 15 Apr 2016 18:53:03 -0000

>Having fought with DNSBL providers, I think the BLACK part of the name is
>appropriate ... as in BLACK HOLE re. any hope of rational resolution.

There are hundreds of DNSBL providers, most of whom are incompentent,
but nobody uses their lists so it doesn't matter.  There are a few
that are competent and have very low error rates.  They, not
surprisingly, are the ones everyone uses.  When I say everyone, I mean
it -- every mail system of any size uses them as part of their spam
filtering because they have to. They're awful but less awful than the
alternatives.

In this particular case, filtering by From: address on mailing lists
still works well enough, particularly here where the participants tend
to be technically sophisticated and so are somewhat less likely to get
their accounts p3ned than average users.  So I agree that we might as
well turn off useless old meeting lists, but I don't see any need to
twiddle things beyond that.

R's,
John

PS:

>>    We _could_ in principle work up protocols to replace zero-maintenance
>> blacklists as "the solution" to spam. I tried, the last time the topic
>> was hot; but totally failed to get anything that wasn't trivial to bypass.

I don't think that's a failure of imagination, it's in the nature of
systems with malicious participants.  It's not unrelated to the
observation that you wouldn't want to join a club that would have you
as a member.


From nobody Fri Apr 15 11:56:03 2016
Return-Path: <carlos@lacnic.net>
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 A4CED12D571; Fri, 15 Apr 2016 11:56:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] 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 Ezd9-0cJ919v; Fri, 15 Apr 2016 11:55:57 -0700 (PDT)
Received: from mail.lacnic.net.uy (hermes.lacnic.net.uy [IPv6:2001:13c7:7001:4000::8]) by ietfa.amsl.com (Postfix) with ESMTP id 0F3AE12D7E1; Fri, 15 Apr 2016 11:55:57 -0700 (PDT)
Received: from hermes.lacnic.net.uy (localhost [127.0.0.1]) by mail.lacnic.net.uy (Postfix) with ESMTP id CACAD16B40F5D; Fri, 15 Apr 2016 15:47:55 -0300 (UYT)
X-Virus-Scanned: amavisd-new at lacnic.net.uy
Received: from mail.lacnic.net.uy ([127.0.0.1]) by hermes.lacnic.net.uy (mail.lacnic.net.uy [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id l1UwrNSkk5AU; Fri, 15 Apr 2016 15:47:54 -0300 (UYT)
Received: from [IPv6:2001:13c7:7001:2128:5006:52b0:f2fc:e8fc] (unknown [IPv6:2001:13c7:7001:2128:5006:52b0:f2fc:e8fc]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mail.lacnic.net.uy (Postfix) with ESMTPSA id D90B616B400E2; Fri, 15 Apr 2016 15:47:54 -0300 (UYT)
Subject: Re: [89attendees] spam on old lists - was Fw: new important message
To: ietf@johnlevine.com, 89attendees@ietf.org
References: <20160415185238.6233.qmail@ary.lan>
From: "Carlos M. Martinez" <carlos@lacnic.net>
Message-ID: <57113939.80102@lacnic.net>
Date: Fri, 15 Apr 2016 15:55:53 -0300
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:38.0) Gecko/20100101 Thunderbird/38.7.2
MIME-Version: 1.0
In-Reply-To: <20160415185238.6233.qmail@ary.lan>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/pHPZjbyAJ1yMB7m8o4VW9O8_n78>
Cc: 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: Fri, 15 Apr 2016 18:56:01 -0000

Aren´t old XXattendees MLs suspended/default moderated ? i would have
thought so. At least it's what we do with old lacnicXX-attendees

-Carlos

On 4/15/16 3:52 PM, ietf@johnlevine.com wrote:
>> Having fought with DNSBL providers, I think the BLACK part of the name is
>> appropriate ... as in BLACK HOLE re. any hope of rational resolution.
> There are hundreds of DNSBL providers, most of whom are incompentent,
> but nobody uses their lists so it doesn't matter.  There are a few
> that are competent and have very low error rates.  They, not
> surprisingly, are the ones everyone uses.  When I say everyone, I mean
> it -- every mail system of any size uses them as part of their spam
> filtering because they have to. They're awful but less awful than the
> alternatives.
>
> In this particular case, filtering by From: address on mailing lists
> still works well enough, particularly here where the participants tend
> to be technically sophisticated and so are somewhat less likely to get
> their accounts p3ned than average users.  So I agree that we might as
> well turn off useless old meeting lists, but I don't see any need to
> twiddle things beyond that.
>
> R's,
> John
>
> PS:
>
>>>    We _could_ in principle work up protocols to replace zero-maintenance
>>> blacklists as "the solution" to spam. I tried, the last time the topic
>>> was hot; but totally failed to get anything that wasn't trivial to bypass.
> I don't think that's a failure of imagination, it's in the nature of
> systems with malicious participants.  It's not unrelated to the
> observation that you wouldn't want to join a club that would have you
> as a member.
>
> _______________________________________________
> 89attendees mailing list
> 89attendees@ietf.org
> https://www.ietf.org/mailman/listinfo/89attendees


From nobody Fri Apr 15 11:57:03 2016
Return-Path: <john@jlc.net>
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 CC54A12D8F3 for <ietf@ietfa.amsl.com>; Fri, 15 Apr 2016 11:57:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.196
X-Spam-Level: 
X-Spam-Status: No, score=-5.196 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.996] 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 Jr0P57s5-RJ4 for <ietf@ietfa.amsl.com>; Fri, 15 Apr 2016 11:56:58 -0700 (PDT)
Received: from mailhost.jlc.net (mailhost.jlc.net [199.201.159.4]) by ietfa.amsl.com (Postfix) with ESMTP id 3E1F712DB71 for <ietf@ietf.org>; Fri, 15 Apr 2016 11:56:52 -0700 (PDT)
Received: by mailhost.jlc.net (Postfix, from userid 104) id 14B8EC9414; Fri, 15 Apr 2016 14:56:47 -0400 (EDT)
Date: Fri, 15 Apr 2016 14:56:47 -0400
From: John Leslie <john@jlc.net>
To: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
Subject: Re: spam on old lists - was [89attendees] Fw: new important message
Message-ID: <20160415185647.GV3997@verdi>
References: <alpine.LRH.2.20.1604151309440.27222@ns0.nohats.ca> <00DFA933-A21B-4C0C-AFC8-319FF7AA1DFD@consulintel.es> <20160415175336.GU3997@verdi> <433046AF-64F4-486A-BBD0-251829CEEB5B@consulintel.es>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <433046AF-64F4-486A-BBD0-251829CEEB5B@consulintel.es>
User-Agent: Mutt/1.4.1i
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/MjtbY_qfNJihUGNY47Za8jawmKU>
Cc: IETF discussion list <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: Fri, 15 Apr 2016 18:57:02 -0000

JORDI PALET MARTINEZ <jordi.palet@consulintel.es> wrote:
> 
> A few years ago,

   Thank you for stipulating "a few years ago". Spammers have learned
a lot in the last few years.

> I???ve managed to get a customer out of spamhaus, despite having sent
> a SPAM because a bot, etc.

   In this case, there is _no_ evidence of a bot among my users.

> I was able to find all the info about how to proceed in their web
> site, apply to clean, etc.

   When is the last time you tried?

   Spamhaus has become more paranoid; and several features of their
website aren't functioning well right now. (Not to mention their preference
for users blindly enabling all javascript...)

> Same with other similar DNS-BLs

   Actually spamhaus has a better-than-average reputation. It is _not_
the "same" with the average DNSBLs.

> I think if you???re ???clean??? you should have not problem,

   "clean" by whose definition?

   Nowadays, it's not even a publicly-available definition!

> and we can choose which DNS-BL to apply.

   I refuse to feed a flame-war here; except to say we _won't_ reach
a useful rough-consensus without excluding too many contributors (and
probably won't reach rough-consensus at all).

> If we have from the community negative reports about bad-behaviours
> from any of those DNS-BLs for example.

   Again, how much are you contributing to the costs of what you ask?

--
John Leslie <john@jlc.net>


From nobody Fri Apr 15 12:45:45 2016
Return-Path: <prvs=191307ffb3=jordi.palet@consulintel.es>
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 5BBFF12D6BB for <ietf@ietfa.amsl.com>; Fri, 15 Apr 2016 12:45:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.899
X-Spam-Level: 
X-Spam-Status: No, score=-101.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_QP_LONG_LINE=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 BpefNYTcUaTK for <ietf@ietfa.amsl.com>; Fri, 15 Apr 2016 12:45:42 -0700 (PDT)
Received: from mail.consulintel.com (mail.consulintel.com [213.0.69.132]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 52D4C12D6FC for <ietf@ietf.org>; Fri, 15 Apr 2016 12:45:42 -0700 (PDT)
X-MDAV-Processed: mail.consulintel.com, Fri, 15 Apr 2016 21:45:39 +0200
Received: from [10.10.10.212] by mail.consulintel.com (MDaemon PRO v11.0.3) with ESMTP id md50000394188.msg for <ietf@ietf.org>; Fri, 15 Apr 2016 21:45:38 +0200
X-Spam-Processed: mail.consulintel.com, Fri, 15 Apr 2016 21:45:38 +0200 (not processed: spam filter heuristic analysis disabled)
X-MDOP-RefID: re=0.000,fgs=0 (_st=1 _vt=0 _iwf=0)
X-Return-Path: prvs=191307ffb3=jordi.palet@consulintel.es
X-Envelope-From: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: ietf@ietf.org
User-Agent: Microsoft-MacOutlook/0.0.0.160212
Date: Fri, 15 Apr 2016 21:45:37 +0200
Subject: Re: spam on old lists - was [89attendees] Fw: new important message
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: IETF discussion list <ietf@ietf.org>
Message-ID: <8673E574-B04F-4F09-8934-A386521C2029@consulintel.es>
Thread-Topic: spam on old lists - was [89attendees] Fw: new important message
References: <alpine.LRH.2.20.1604151309440.27222@ns0.nohats.ca> <00DFA933-A21B-4C0C-AFC8-319FF7AA1DFD@consulintel.es> <20160415175336.GU3997@verdi> <433046AF-64F4-486A-BBD0-251829CEEB5B@consulintel.es> <20160415185647.GV3997@verdi>
In-Reply-To: <20160415185647.GV3997@verdi>
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/rTabAvfWRfKjMjAUK7DZ25TXnIk>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: jordi.palet@consulintel.es
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: Fri, 15 Apr 2016 19:45:44 -0000

I=E2=80=99ve cleaned up bad customer records at several DNS-BL last july, and it =
worked.

I=E2=80=99m not sure to catch your question about the cost: I think the cost of t=
housands of IETF subscribers time to get SPAM from IETF exploders is much hi=
gher that the cost of using DNS-BL to reject posters that have been black li=
sted.

Saludos,
Jordi









-----Mensaje original-----
De: John Leslie <john@jlc.net>
Responder a: <john@jlc.net>
Fecha: viernes, 15 de abril de 2016, 20:56
Para: Jordi Palet Martinez <jordi.palet@consulintel.es>
CC: IETF discussion list <ietf@ietf.org>
Asunto: Re: spam on old lists - was [89attendees] Fw: new important message

>JORDI PALET MARTINEZ <jordi.palet@consulintel.es> wrote:
>>=20
>> A few years ago,
>
>   Thank you for stipulating "a few years ago". Spammers have learned
>a lot in the last few years.
>
>> I???ve managed to get a customer out of spamhaus, despite having sent
>> a SPAM because a bot, etc.
>
>   In this case, there is _no_ evidence of a bot among my users.
>
>> I was able to find all the info about how to proceed in their web
>> site, apply to clean, etc.
>
>   When is the last time you tried?
>
>   Spamhaus has become more paranoid; and several features of their
>website aren't functioning well right now. (Not to mention their preferenc=
e
>for users blindly enabling all javascript...)
>
>> Same with other similar DNS-BLs
>
>   Actually spamhaus has a better-than-average reputation. It is _not_
>the "same" with the average DNSBLs.
>
>> I think if you???re ???clean??? you should have not problem,
>
>   "clean" by whose definition?
>
>   Nowadays, it's not even a publicly-available definition!
>
>> and we can choose which DNS-BL to apply.
>
>   I refuse to feed a flame-war here; except to say we _won't_ reach
>a useful rough-consensus without excluding too many contributors (and
>probably won't reach rough-consensus at all).
>
>> If we have from the community negative reports about bad-behaviours
>> from any of those DNS-BLs for example.
>
>   Again, how much are you contributing to the costs of what you ask?
>
>--
>John Leslie <john@jlc.net>
>



From nobody Fri Apr 15 12:54:21 2016
Return-Path: <stewart.bryant@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 7DDEB12D88B; Fri, 15 Apr 2016 12:54:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 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, RCVD_IN_DNSWL_LOW=-0.7, 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 nl9-XJalkYUQ; Fri, 15 Apr 2016 12:54:17 -0700 (PDT)
Received: from mail-wm0-x230.google.com (mail-wm0-x230.google.com [IPv6:2a00:1450:400c:c09::230]) (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 8F69012D83B; Fri, 15 Apr 2016 12:54:17 -0700 (PDT)
Received: by mail-wm0-x230.google.com with SMTP id n3so46835434wmn.0; Fri, 15 Apr 2016 12:54:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=NxyIVGnqfth1f1CLACv1hHk2mOCEeBU+Up23/Np61QY=; b=fkxNms+ThcsZYH1QUhVEPm19bV3qMn5ZnlRzth6TFUhnW7GwxE9OjKFUmOLUjG/U+I TsINRSSHuXqXPYvz2JG/ZJvhZmfpK/DYkEwm2J/whcMap2arBZj3tHvJChd6rBhDwtrL 2ob/wChv70GoG4j4dJ0OfZqsH2na05p5L57E1UtZ3SbFI4exd0pNE9OTkk4Nq4l9xure nNB1SgYpnwGYeQy8bQTswUeSijka4zYwHmKck6CR8nL6b80KmaqvE74coJGDfashmpU5 WDJ7TDY7KOtSNVbh0IzEdatU8Wo/u1dnwvX266vAdnSx8Byy+z4PsXwMxP0sGBkWyofH jaAA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=NxyIVGnqfth1f1CLACv1hHk2mOCEeBU+Up23/Np61QY=; b=SFPgvHsF65u2999X77EaA71OZHmG1PKMgwXEcrMky6pggUtRkhEmYzKdNBhx8vYZRR SD+3tbGELTxxRxwCw/Beo7rTqVqY0bXlEJ1Ipa1cB07Nl12PyOIAL4IZL47TLlbopeQm bfEGauNYNSnMePkGI+DsNB6fDX6zJK3kbPYa/TOYgACbR4OebF7LRFAIwofr2N93Ipim tBH5rsOg/xn5Cv1ly5MlfxTqdS8IfERZkvuRF7uyT7XqKlw7m45202ce/EpC6FVAyd4b KcTy5Un6R7ztwMQ3LZDrg4KUjNKEQal7pNu9oFrFLGf4bfnWO+8ONH4vS3Az1YrhYNnk frLA==
X-Gm-Message-State: AOPr4FVLMeXl/v/JMv8Ct+09/McsvkeYT3Cqi/ozjTJhhXmScXPALb4vC5oxgCbViWANZg==
X-Received: by 10.28.55.139 with SMTP id e133mr6275048wma.98.1460750056091; Fri, 15 Apr 2016 12:54:16 -0700 (PDT)
Received: from [192.168.2.126] (host213-123-124-182.in-addr.btopenworld.com. [213.123.124.182]) by smtp.gmail.com with ESMTPSA id m6sm50323401wje.21.2016.04.15.12.54.14 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 15 Apr 2016 12:54:15 -0700 (PDT)
Subject: Re: IETF95 remote attendance
To: Meetecho IETF support <ietf@meetecho.com>, Joseph Lorenzo Hall <joe@cdt.org>
References: <5710CA7F.3050207@meetecho.com> <5710CE07.9090104@gmail.com> <CABtrr-W4bmaG2vEEokbwCLED2P9_eiEgmeM2zHO8-RQUt7BZ0Q@mail.gmail.com> <5710D983.5040006@meetecho.com>
From: Stewart Bryant <stewart.bryant@gmail.com>
Message-ID: <571146E5.9090901@gmail.com>
Date: Fri, 15 Apr 2016 20:54:13 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.7.0
MIME-Version: 1.0
In-Reply-To: <5710D983.5040006@meetecho.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/mFVpDjnQg5Y75-N99pPyOPCoJpk>
Cc: IETF Discussion Mailing List <ietf@ietf.org>, vmeet@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: Fri, 15 Apr 2016 19:54:19 -0000

On 15/04/2016 13:07, Meetecho IETF support wrote:
> Il 15/04/2016 13:56, Joseph Lorenzo Hall ha scritto:
>> On Fri, Apr 15, 2016 at 7:18 AM, Stewart Bryant
>> <stewart.bryant@gmail.com> wrote:
>>>
>>>
>>> On 15/04/2016 12:03, Meetecho IETF support wrote:
>>>>
>>>> - 712 unique remote participants joined Meetecho through the week; 
>>>> among
>>>> these, 282 opted to also put their Registration ID.
>>>
>>>
>>> There was something odd about the registration number system.
>>>
>>> I tried to enter my registration number a few times but it rejected 
>>> it every
>>> time.
>>>
>>> Since it did not REQUIRE(sic)  the registration number  I just used the
>>> option not to enter it.
>>
>> I had to enter "Joseph Hall" instead of "Joe Hall" to get it to take 
>> my Reg. ID.
>>
>
> Your first and last name must be identical to the name used to register.

I am sure that in both cases I used "Stewart Bryant".

Stewart


From nobody Fri Apr 15 12:56:07 2016
Return-Path: <hallam@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 D91D412DB89 for <ietf@ietfa.amsl.com>; Fri, 15 Apr 2016 12:56:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.4
X-Spam-Level: 
X-Spam-Status: No, score=-2.4 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.199, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 nWcfG6-kk38H for <ietf@ietfa.amsl.com>; Fri, 15 Apr 2016 12:56:03 -0700 (PDT)
Received: from mail-lf0-x234.google.com (mail-lf0-x234.google.com [IPv6:2a00:1450:4010:c07::234]) (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 CFF8412DA21 for <ietf@ietf.org>; Fri, 15 Apr 2016 12:56:02 -0700 (PDT)
Received: by mail-lf0-x234.google.com with SMTP id j11so157438551lfb.1 for <ietf@ietf.org>; Fri, 15 Apr 2016 12:56:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc; bh=uEx9AT+ZILr8qY9K9O9wvyV8QhoSA8ThHxrT0HkP1r4=; b=FMtz2+56opSdVyhaO6TtsfVLioGbW1jTZoR9P87oZTDufHpk/sBM9FohQ7rGUQd7WQ ibrn+LjWqJ7vot++FBwEO5XKVsTpOcLfdfEIDI2s2dkJjQfUwyMxwQ9xx+iPLR3zOZqj XJjqViExN5P7y+/Ii6sjwMOYvpQI9FFHRrhcouiizcoUOgUoF16DxsWonYiwLDIYWgFl XhAW2cVAda4WKxUOR/hauzR9lNGmXhgsp3CoaGBGz5A9welI9M7DAmL9q48vM9X8ROwO aL8QIrZfJtqHfwlT8T8OKw+SrgCm27eVnIsB45zYJP31ghuVzartbT7ENz3rOKBQVLxt 9X6w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:date :message-id:subject:from:to:cc; bh=uEx9AT+ZILr8qY9K9O9wvyV8QhoSA8ThHxrT0HkP1r4=; b=TmnWnFIhZktvW3Vuw+oFalG3I71/HA89r7XgE66nR5Ve8pffecfWBAV46Sc87k/r+Z 2OE5kGOUWCBTVcxHEe7Fga0fBQAEFerNySBJzxSc4qYyseSOpjnHd9pCPwe8CtQNPiJE ksnkARkDRI2f8gI+0IXA5uNNbAkh64Y5KHjVn5VhDtWwx1D5FByl4DLemsSGAwYequ1S jeZHBMFQSzRADpweQwk/d4DAKQLyq1Zj2NM2NSiNm87GFWiyPs8UpvzgmxMW5jxUxv4L tg1H1ZfRO+Bzk1KDRBeCNYkrUcgYVwEStXm42Fek9zZyEtOYEG+ncWEKeANQRE9LIfGa tdiA==
X-Gm-Message-State: AOPr4FXehNWV/39UxtC9t/qOLy0qkWOGJLymp3KGNWd997z/hbgenxtEQa3UgUM1NuHRpiaToLgernEXqaeq5A==
MIME-Version: 1.0
X-Received: by 10.25.162.20 with SMTP id l20mr8057509lfe.43.1460750160953; Fri, 15 Apr 2016 12:56:00 -0700 (PDT)
Sender: hallam@gmail.com
Received: by 10.112.3.102 with HTTP; Fri, 15 Apr 2016 12:56:00 -0700 (PDT)
In-Reply-To: <CAPt1N1kNAU+iKhFycE2mO3gjOh-43pRRxA3NpTyi3+A=x-85QQ@mail.gmail.com>
References: <CAMm+Lwg-HTYCv2pGt=SP2+Xjoko6GcJ73kVzqXC1LBTOMDKV_A@mail.gmail.com> <CB8FC0F5-DD04-4478-AC41-09B4F8BA583B@asgard.org> <CAMm+LwiymMc=mqqdj9hupG7AoJMCxxJY7oz7DAX6K1zJ6H3g9g@mail.gmail.com> <CAPt1N1kNAU+iKhFycE2mO3gjOh-43pRRxA3NpTyi3+A=x-85QQ@mail.gmail.com>
Date: Fri, 15 Apr 2016 15:56:00 -0400
X-Google-Sender-Auth: QUt3QdjtdTaKD_dZ9klSAifjG9U
Message-ID: <CAMm+LwihFcmjEGCtALQmyUVXxKfbo-0CJYAbhNjMJ4To60Ab3w@mail.gmail.com>
Subject: Re: Time to kill layer 2
From: Phillip Hallam-Baker <phill@hallambaker.com>
To: Ted Lemon <mellon@fugue.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/Ri6NCXtp9FQBIg8Qxtx86fhuCR0>
Cc: IETF Discussion Mailing List <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: Fri, 15 Apr 2016 19:56:05 -0000

Any time you eliminate use of ASN.1, it is a win.

On Fri, Apr 15, 2016 at 11:36 AM, Ted Lemon <mellon@fugue.com> wrote:
> There's a very interesting discussion about NetJSON as a management strategy
> for homenets going on on the babel mailing list right now.   There is a very
> cool but not very informative demo here:
> http://ninux-graph.netjson.org/topology/e384464c-d1d2-4af3-aae1-4e852a28d956/
>
> The thread is here:
> https://mailarchive.ietf.org/arch/search/?email_list=babel&gbt=1&index=MSVfepqNBnEahhioJocbbCqHODg
>
> (Subject line: NetJSON outreach)
>
>
> On Fri, Apr 15, 2016 at 11:29 AM, Phillip Hallam-Baker
> <phill@hallambaker.com> wrote:
>>
>> On Fri, Apr 15, 2016 at 11:07 AM, Time Warner Cable <Lee@asgard.org>
>> wrote:
>>
>> > On 4/14/16, 8:59 AM, "ietf on behalf of Phillip Hallam-Baker"
>> > <ietf-bounces@ietf.org on behalf of phill@hallambaker.com> wrote:
>>
>> >>All this networking gear is presented to me as black boxes over which
>> >>I have absolutely no control (which is fine-ish) and no visibility.
>> >
>> > What visibility do you want? Error messages on the printer's console?
>> > Syslog messages?
>> > SNMP traps? Oh, apparently not, since "SNMP isn't available most
>> > ordinary people."
>>
>> What I would like is something like a WiFi certification scheme that
>> means 'there is a collection of technology here that is sufficient and
>> complete'.
>>
>> Right now I would have to pay a ridiculous amount of money to get SNMP
>> support because it is positioned as a differentiator between SOHO and
>> 'enterprise' class devices.
>>
>> Getting the feedback necessary to make it work should not be an
>> 'enterprise' feature.
>>
>>
>> >>What should have happened many moons ago was that DHCP should have
>> >>become a bidirectional protocol or a bootstrap to a bidirectional
>> >>protocol. So when a printer joins the network, it authenticates and
>> >>tells the network what it is. And this is all defined in one set of
>> >>specifications from one organization, none of which assumes that
>> >>security is an 'advanced', 'optional' or 'enterprise' feature.
>> >
>> > See Homenet.
>>
>> That seems to be premised on the assumption that the home network will
>> be a simplified version of today's enterprise network rather than
>> having far more moving parts.
>>
>


From nobody Fri Apr 15 14:04:33 2016
Return-Path: <bensons@queuefull.net>
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 4A39612E371 for <ietf@ietfa.amsl.com>; Fri, 15 Apr 2016 14:04:30 -0700 (PDT)
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, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=queuefull.net
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 CnFd9D5-WY6l for <ietf@ietfa.amsl.com>; Fri, 15 Apr 2016 14:04:28 -0700 (PDT)
Received: from mail-ig0-x22d.google.com (mail-ig0-x22d.google.com [IPv6:2607:f8b0:4001:c05::22d]) (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 2BBEA12DC91 for <ietf@ietf.org>; Fri, 15 Apr 2016 14:04:28 -0700 (PDT)
Received: by mail-ig0-x22d.google.com with SMTP id f1so29932480igr.1 for <ietf@ietf.org>; Fri, 15 Apr 2016 14:04:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=queuefull.net; s=google; h=mime-version:subject:from:fcc:date:in-reply-to :content-transfer-encoding:message-id:user-agent:references:to; bh=FyeSA5JI2QzjLbH4OeH9e8le+4O/tBfJiByOEqbYBIw=; b=MQb62tkj9GkBA67h16Uxj4mKbqUpWrWYRb/L6IocNfgRsdwLAUcYce6H6I95onGMWu ZQaF/HBp5q9mNMP4y6Ey8uqUPi8YKQsFUqx4RA8YRR2rvGd48HWqoL286hc5haN6PUcQ e4Vr/gKn2G+z7pnYccwqgOIts0Ls5Mdkzkf3s=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:subject:from:fcc:date:in-reply-to :content-transfer-encoding:message-id:user-agent:references:to; bh=FyeSA5JI2QzjLbH4OeH9e8le+4O/tBfJiByOEqbYBIw=; b=j01dg+WbcsZdGbyrotRex/ap7n0wIdm293N52y3SkZiC4iakY8412IvJ2c2BNkaeNc X+BzclaWu5hVr3U1Dsq9du8HZO1azXpM70OJi46VASlsoiein5ZLsPNGLbMn8UT0pS5f b/xA9kMlerd0L7JmGHtu0Afmlwa01gabjSEpF/C2PFKGNZdfCbUXUjhMYEhXA89WKpq9 EN+L4SXDM0Pr3VDq2EiF3r906mJKnLpmFySw8ngEDwvznj0bGmegk9J06qGBDyvc8Wzt APQubedOHJvkPxoDQMeE0gHet0ijkd+0i6XHQt72pqZ0+INGCqrME8mXhRn1qsQ49Q0/ Zq5g==
X-Gm-Message-State: AOPr4FXrtqHDSe+43NQxVirFCkgiQ2aSRpR0mGDQCFuTr46ZX93BDKCepgh9hJq/usVWcw==
X-Received: by 10.50.79.167 with SMTP id k7mr7138730igx.27.1460754267320; Fri, 15 Apr 2016 14:04:27 -0700 (PDT)
Received: from [100.88.111.90] (186.sub-70-197-161.myvzw.com. [70.197.161.186]) by smtp.gmail.com with ESMTPSA id q198sm29376486iod.6.2016.04.15.14.04.25 for <ietf@ietf.org> (version=TLSv1/SSLv3 cipher=OTHER); Fri, 15 Apr 2016 14:04:26 -0700 (PDT)
Content-Type: multipart/signed; boundary=Apple-Mail-435F839C-3CCD-4863-9D2C-4C08F841E798; protocol="application/pkcs7-signature"; micalg=sha1
Mime-Version: 1.0
Subject: Re: spam on old lists - was [89attendees] Fw: new important message
From: Benson Schliesser <bensons@queuefull.net>
X-Mailer: iPhone Mail (13E238)
Fcc: imap://bensons%40queuefull.net@imap.gmail.com/[Gmail]/Sent Mail
X-Enigmail-Version: 1.2.3
X-Identity-Key: id1
Date: Fri, 15 Apr 2016 17:04:24 -0400
In-Reply-To: <20160415185238.6233.qmail@ary.lan>
Content-Transfer-Encoding: 7bit
X-Mozilla-Draft-Info: internal/draft; vcard=0; receipt=0; DSN=0; uuencode=0
Message-Id: <FBEF78BA-A260-4460-9090-F159D957531D@queuefull.net>
User-Agent: Postbox 4.0.8 (Macintosh/20151105)
References: <20160415185238.6233.qmail@ary.lan>
To: ietf@ietf.org
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/I8xDuyxyl_57JHzj3GixpkhTvNI>
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: Fri, 15 Apr 2016 21:04:30 -0000

--Apple-Mail-435F839C-3CCD-4863-9D2C-4C08F841E798
Content-Type: multipart/alternative;
	boundary=Apple-Mail-9DCBA347-CA26-46C2-AC01-47C965E99A10
Content-Transfer-Encoding: 7bit


--Apple-Mail-9DCBA347-CA26-46C2-AC01-47C965E99A10
Content-Type: text/plain;
	charset=us-ascii
Content-Transfer-Encoding: quoted-printable

ietf@johnlevine.com wrote:
> In this particular case, filtering by From: address on mailing lists
> still works well enough,=20

First, let me say that I agree with the above statement inasmuch as it conce=
rns external blacklists for filtering IETF mailing lists. But I'm not so sur=
e that I agree with it in a broader sense. I'm saying this as the person who=
se email address is in the =46rom header of the spam email that started this=
 thread.  :(

The spam message in this case did not originate from any client or host unde=
r my control. It did not transit via any of my mail relays. It was a forgery=
 - it spoofed my email address in the =46rom header, and unfortunately happe=
ned to match it up with a To header addressing an IETF mailing list to which=
 I'm subscribed.=20

For whatever it's worth, this has been going on for a while. I've been getti=
ng bounces, moderation notices, etc, for people and lists I never even knew e=
xisted. I'm not sure how the originating software harvested my email address=
, how it's controlled, etc, but it does seem to be some kind of distributed m=
alware or botnet that takes advantage of a specific mail client. (I have fur=
ther speculation about this, but I'll save that for another venue.)

In an effort to do something about this (in addition to fruitless attempts a=
t getting help from various abuse@ teams) I've tried to configure DMARC, DKI=
M, and SPF for my sending domain. Unfortunately the IETF mail servers don't s=
eem to pay attention to this, and spoofed messages still get relayed. Furthe=
r, because the IETF mailing lists don't perform sender rewriting, legitimate=
 messages were being thrown away by list members' mail servers that do respe=
ct SPF. The (hopefully temporary) fix has been to add the IETF mail servers t=
o my domain's SPF record - which results in false negatives instead of false=
 positives.=20

If any experts have advice on how to fix this better, please teach me. I'll b=
uy you many drinks, chocolates, or whatever makes you happy!=20

Otherwise the only fix that I can imagine is for the IETF to start opportuni=
stically filtering list message submissions based on DMARC, SPF, and DKIM, a=
s well as performing sender rewriting in the list software. Like most things=
, I imagine the subscribers on this list have opinions about this - and I'd b=
e glad to hear them.=20

Thanks,
-Benson


--Apple-Mail-9DCBA347-CA26-46C2-AC01-47C965E99A10
Content-Type: text/html;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable

<html><head><meta http-equiv=3D"content-type" content=3D"text/html; charset=3D=
utf-8"></head><body dir=3D"auto"><div><span></span></div><div>
<meta content=3D"text/html; charset=3DUTF-8" http-equiv=3D"Content-Type">
<span><a class=3D"moz-txt-link-abbreviated" href=3D"mailto:ietf@johnlevine.c=
om">ietf@johnlevine.com</a>=20
wrote:</span><br>
<blockquote cite=3D"mid:20160415185238.6233.qmail@ary.lan" type=3D"cite">
  <pre wrap=3D"">In this particular case, filtering by From: address on mail=
ing lists
still works well enough, </pre>
</blockquote>
<br>
First, let me say that I agree with the above statement inasmuch as it=20
concerns external blacklists for filtering IETF mailing lists.&nbsp;But I'm n=
ot so sure that I agree with it in a broader sense. I'm saying=20
this as the person whose email address is in the =46rom header of the spam
 email that started this thread.&nbsp; :(<br>
<br>
The spam message in this case did not originate from any client or host unde=
r my=20
control. It did not transit via any of my mail relays. It was a forgery - it=
 spoofed my email address in the =46rom header, and unfortunately happened t=
o match it up with a To header addressing an IETF mailing list to which I'm s=
ubscribed.&nbsp;<br>

</div><div><br></div><div>For whatever it's worth, this has been going on fo=
r a while. I've been getting bounces, moderation notices, etc, for people an=
d lists I never even knew existed. I'm not sure how the originating software=
 harvested my email address, how it's controlled, etc, but it does seem to b=
e some kind of distributed malware or botnet that takes advantage of a speci=
fic mail client. (I have further speculation about this, but I'll save that f=
or another venue.)</div><div><br></div><div>In an effort to do something abo=
ut this (in addition to fruitless attempts at getting help from various abus=
e@ teams) I've tried to configure DMARC, DKIM, and SPF for my sending domain=
. Unfortunately the IETF mail servers don't seem to pay attention to this, a=
nd spoofed messages still get relayed. Further, because the IETF mailing lis=
ts don't perform sender rewriting, legitimate messages were being thrown awa=
y by list members' mail servers that do respect SPF. The (hopefully temporar=
y) fix has been to add the IETF mail servers to my domain's SPF record - whi=
ch results in&nbsp;false negatives instead of false positives.&nbsp;</div><d=
iv><br></div><div>If any experts have advice on how to fix this better, plea=
se teach me. I'll buy you many drinks, chocolates, or whatever makes you hap=
py!&nbsp;</div><div><br></div><div>Otherwise the only fix that I can imagine=
 is for the IETF to start opportunistically filtering list message submissio=
ns based on DMARC, SPF, and DKIM, as well as performing sender rewriting in t=
he list software. Like most things, I imagine the subscribers on this list h=
ave opinions about this - and I'd be glad to hear them.&nbsp;</div><div><br>=
</div><div>Thanks,</div><div>-Benson</div><div><br></div></body></html>=

--Apple-Mail-9DCBA347-CA26-46C2-AC01-47C965E99A10--

--Apple-Mail-435F839C-3CCD-4863-9D2C-4C08F841E798
Content-Type: application/pkcs7-signature;
	name=smime.p7s
Content-Disposition: attachment;
	filename=smime.p7s
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIStjCCBP8w
ggPnoAMCAQICEDP/yhCwoPBv2h2BqmbbJtkwDQYJKoZIhvcNAQELBQAwdTELMAkGA1UEBhMCSUwx
FjAUBgNVBAoTDVN0YXJ0Q29tIEx0ZC4xKTAnBgNVBAsTIFN0YXJ0Q29tIENlcnRpZmljYXRpb24g
QXV0aG9yaXR5MSMwIQYDVQQDExpTdGFydENvbSBDbGFzcyAxIENsaWVudCBDQTAeFw0xNjAyMjEy
MTQ2MDNaFw0xNzAyMjEyMTQ2MDNaMEYxHjAcBgNVBAMMFWJlbnNvbnNAcXVldWVmdWxsLm5ldDEk
MCIGCSqGSIb3DQEJARYVYmVuc29uc0BxdWV1ZWZ1bGwubmV0MIIBIjANBgkqhkiG9w0BAQEFAAOC
AQ8AMIIBCgKCAQEAyWok/RG/EDaSfKy2h8PDqCKdSQQsh93FKUIvbFcq2c+JTyunQ0wm2UI888R4
rOfjBHwruPMp/jHm76JwCYyBasqBN6GOLJef2iRx/gekAZNd99MIXAXOhibWNI+pjCx2NWNd0yax
zeb6dIXQI5EIurkvt0kSl3VYdKGzeyZPQFybXuM9ABrjeLmIHY49VeJfGEly1zelhjUn4LkBX2lT
19Z98KxuYbPSIk+imPOyD2FEV0aT2r5AMueG9LpzV17vd2AMtTolvQ1gLOfHUn/1IdOwQtndbXJF
usT9Vpp9vxNIjZtkxt6WZi/tVIATzMU4tGdkHVqxws0KY1QXfpFAeQIDAQABo4IBuDCCAbQwDgYD
VR0PAQH/BAQDAgSwMB0GA1UdJQQWMBQGCCsGAQUFBwMCBggrBgEFBQcDBDAJBgNVHRMEAjAAMB0G
A1UdDgQWBBSP+2xt7XsDxn0mwV0GcdEsmQle6jAfBgNVHSMEGDAWgBQkgWw5Yb5JD4+3G0YrySi1
J0htaDBvBggrBgEFBQcBAQRjMGEwJAYIKwYBBQUHMAGGGGh0dHA6Ly9vY3NwLnN0YXJ0c3NsLmNv
bTA5BggrBgEFBQcwAoYtaHR0cDovL2FpYS5zdGFydHNzbC5jb20vY2VydHMvc2NhLmNsaWVudDEu
Y3J0MDgGA1UdHwQxMC8wLaAroCmGJ2h0dHA6Ly9jcmwuc3RhcnRzc2wuY29tL3NjYS1jbGllbnQx
LmNybDAgBgNVHREEGTAXgRViZW5zb25zQHF1ZXVlZnVsbC5uZXQwIwYDVR0SBBwwGoYYaHR0cDov
L3d3dy5zdGFydHNzbC5jb20vMEYGA1UdIAQ/MD0wOwYLKwYBBAGBtTcBAgQwLDAqBggrBgEFBQcC
ARYeaHR0cDovL3d3dy5zdGFydHNzbC5jb20vcG9saWN5MA0GCSqGSIb3DQEBCwUAA4IBAQCm7aO4
78JqMUzcTNkj4+FVcz9/es23IZ4l55gwlxTGsXG4r5Ks72dB6VnWr60nLN0Oya6VEX9FtDTzyD3M
n+pze45tkXoLSajTnSyHnO6tAtrjZt5/Txb3til1xo3gug9peUkyQOjqhF/khigvQHIdfm3lxwov
thJAqY0zml8yXIDSs/pjdH1THfFKNRN4wHTOh2QaAfE4j24ibaUVlo6CRGZbya/RxqGZagvSx2u4
Mt+ZwqsYf36rFiVV+ur19L/soXmV4Y3JcLjmohYb9Mv/lNLoVJHPPh+CRv1PSv37fYEfGbE2FFvG
YAsMJ6cPS2HtlK/qVmt/dtQtsQ/TAHPCMIIF4jCCA8qgAwIBAgIQa6eKfQrXiNZRCvlZ5Oe04TAN
BgkqhkiG9w0BAQsFADB9MQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRDb20gTHRkLjErMCkG
A1UECxMiU2VjdXJlIERpZ2l0YWwgQ2VydGlmaWNhdGUgU2lnbmluZzEpMCcGA1UEAxMgU3RhcnRD
b20gQ2VydGlmaWNhdGlvbiBBdXRob3JpdHkwHhcNMTUxMjE2MDEwMDA1WhcNMzAxMjE2MDEwMDA1
WjB1MQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRDb20gTHRkLjEpMCcGA1UECxMgU3RhcnRD
b20gQ2VydGlmaWNhdGlvbiBBdXRob3JpdHkxIzAhBgNVBAMTGlN0YXJ0Q29tIENsYXNzIDEgQ2xp
ZW50IENBMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAvX3a98OifYP2W4L921tfrh4b
dcC1Ga+YJKy7V3nYNewJHnzMlBsK0Hb8Dm4Wo3FZpylcYa1MJGT10QMGWaLER3xCIuRR+8eklf/E
qeZWRLojJ7zBRtjMywPOCelrOU+DX12dKp+Ez4J6919rz1UudTO1GvZyCYJ/I7062uHsskM8b7gP
xmcCoO1UHwwpgkvpCArJWGFoFzjLdsZbErJcS3HtAhlkbE/BKTMrdYg35Uo12SLBO5tbk8h2imbK
TC8iMs+pskrvI/AVlh6QoTTXk6xboVX6zgMgzxSVVLymQiygYYm0y5aMsvi2raFhC643SOGvErWW
PPnSEfbeAD1xswIDAQABo4IBZDCCAWAwDgYDVR0PAQH/BAQDAgEGMB0GA1UdJQQWMBQGCCsGAQUF
BwMCBggrBgEFBQcDBDASBgNVHRMBAf8ECDAGAQH/AgEAMDIGA1UdHwQrMCkwJ6AloCOGIWh0dHA6
Ly9jcmwuc3RhcnRzc2wuY29tL3Nmc2NhLmNybDBmBggrBgEFBQcBAQRaMFgwJAYIKwYBBQUHMAGG
GGh0dHA6Ly9vY3NwLnN0YXJ0c3NsLmNvbTAwBggrBgEFBQcwAoYkaHR0cDovL2FpYS5zdGFydHNz
bC5jb20vY2VydHMvY2EuY3J0MB0GA1UdDgQWBBQkgWw5Yb5JD4+3G0YrySi1J0htaDAfBgNVHSME
GDAWgBROC+8apEBbpRdphzDKNGhD0EGu8jA/BgNVHSAEODA2MDQGBFUdIAAwLDAqBggrBgEFBQcC
ARYeaHR0cDovL3d3dy5zdGFydHNzbC5jb20vcG9saWN5MA0GCSqGSIb3DQEBCwUAA4ICAQCL4/eH
7AGLhK0PAQJbnOEjJyMEvTTwcAJuUh/bodjQl06u4putYOxdSyIjSP/sKt+31LmjG8+IO1WqykE4
H/Lm7NKezWVnCHuwb3ptgFmlwbMbGkU2MOZBtwzfKXdYUhFLhaE2uw5jXhXvLYitQay962wP5uPI
6eAIhV4L8aaya1u4s7MnrTq0Rz25FuGNO79vTHYWj797tSRC8rM16js4yGKOLFpQvIg0F8IElv57
b1stp+C7omqM5Qn15dePbSnqr8Jb65WtmJJbnv6rlqfY/aLuE/zmNAlzLmPgfMDStKIXdg+EoYBZ
TEo8wBUaBxihfNbJ069ndQOxMNNqBelEMgpAtmjTbCuXFjqIwWq+XOx6ZV/Wh2FAmaLsSHlNvEjj
SQMZwE4EeHCdo66ZmEs/5JYlCeOkulKVQ6P3m5/XOj2jP17Q2AgmjP+11+sHN7PvrG0OwrQp9QMe
3X+rn0G8MjtFfqBWvR9CgLIxzM3MJNxFdgdjS2rYnShP5uxvqwfZvhZVYCIkqdJhpYON0DvSodfi
ar0wiM79mySZJjzC0CTbiisBzS/BeBhqeo2wFfli/iw3hn1XKvAx0ty6w/scmBF0AYqmRHYj1TjM
Sw0lAl7AztLglqWjUPI+sukvadMRPxmtKXlS2nVR4an/Z16imsZ69+fFYH68c1CK7zmjozCCB8kw
ggWxoAMCAQICAQEwDQYJKoZIhvcNAQEFBQAwfTELMAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0
Q29tIEx0ZC4xKzApBgNVBAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNpZ25pbmcxKTAn
BgNVBAMTIFN0YXJ0Q29tIENlcnRpZmljYXRpb24gQXV0aG9yaXR5MB4XDTA2MDkxNzE5NDYzNloX
DTM2MDkxNzE5NDYzNlowfTELMAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0Q29tIEx0ZC4xKzAp
BgNVBAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNpZ25pbmcxKTAnBgNVBAMTIFN0YXJ0
Q29tIENlcnRpZmljYXRpb24gQXV0aG9yaXR5MIICIjANBgkqhkiG9w0BAQEFAAOCAg8AMIICCgKC
AgEAwYjbCbxsRnx4n5V7tTOQ8nJi1sE2ICIkXs7pd/JDCqIGZKTMjjb4OOYj8G5tsTzdcqOFHKHT
PbQzK9Mvr/7qsEFZZ7bEBn0KnnSF1nlMgDd63zkFUln39BtGQ6TShYXSw3HzdWI0uiyKfx6P7u00
0BHHls1SPboz1t1N3gs7SkufwiYv+rUWHHI1d8o8XebK4SaLGjZ2XAHbdBQl/u21oIgP3XjKLR8H
lzABLXJ5+kbWEyqouaarg0kd5fLv3eQBjhgKj2NTFoViqQ4ZOsy1ZqbCa3QH5Cvhdj60bdj2ROFz
Yh87xL6gU1YlbFEJ96qryr92/W2b853bvz1mvAxWqq+YSJU6S9+nWFDZOHWpW+pDDAL/mevobE1w
WyllnN2qXcyvATHsDOvSjejqnHvmbvcnZgwaSNduQuM/3iE+e+ENcPtjqqhsGlS0XCV6yaLJixam
uyx+F14FTVhuEh0B7hIQDcYyfxj//PT6zW6R6DZJvhpIaYvClk0aErJpF8EKkNb6eSJIv7p7afhw
x/p6N9jYDdJ2T1f/kLfjkdLd78Jgt2c63f6qnPDUi39yIs7Gn5e2+K+KoBCo2fsYxra1XFI8ibYZ
KnMBCg8DsxJg8novgdujbv8mMJf1i92JV7atPbOvK8W3dgLwpdYrmoYUKnL24zOMXQlLE9+7jHQT
UksCAwEAAaOCAlIwggJOMAwGA1UdEwQFMAMBAf8wCwYDVR0PBAQDAgGuMB0GA1UdDgQWBBROC+8a
pEBbpRdphzDKNGhD0EGu8jBkBgNVHR8EXTBbMCygKqAohiZodHRwOi8vY2VydC5zdGFydGNvbS5v
cmcvc2ZzY2EtY3JsLmNybDAroCmgJ4YlaHR0cDovL2NybC5zdGFydGNvbS5vcmcvc2ZzY2EtY3Js
LmNybDCCAV0GA1UdIASCAVQwggFQMIIBTAYLKwYBBAGBtTcBAQEwggE7MC8GCCsGAQUFBwIBFiNo
dHRwOi8vY2VydC5zdGFydGNvbS5vcmcvcG9saWN5LnBkZjA1BggrBgEFBQcCARYpaHR0cDovL2Nl
cnQuc3RhcnRjb20ub3JnL2ludGVybWVkaWF0ZS5wZGYwgdAGCCsGAQUFBwICMIHDMCcWIFN0YXJ0
IENvbW1lcmNpYWwgKFN0YXJ0Q29tKSBMdGQuMAMCAQEagZdMaW1pdGVkIExpYWJpbGl0eSwgcmVh
ZCB0aGUgc2VjdGlvbiAqTGVnYWwgTGltaXRhdGlvbnMqIG9mIHRoZSBTdGFydENvbSBDZXJ0aWZp
Y2F0aW9uIEF1dGhvcml0eSBQb2xpY3kgYXZhaWxhYmxlIGF0IGh0dHA6Ly9jZXJ0LnN0YXJ0Y29t
Lm9yZy9wb2xpY3kucGRmMBEGCWCGSAGG+EIBAQQEAwIABzA4BglghkgBhvhCAQ0EKxYpU3RhcnRD
b20gRnJlZSBTU0wgQ2VydGlmaWNhdGlvbiBBdXRob3JpdHkwDQYJKoZIhvcNAQEFBQADggIBABZs
mfRmDDT10IVefQrs2hBOOBxe36YlBUuRMsHoO/E93UQJWwdJiinLZgK3sZr3JZgJPI4b4d02hytL
u2jTOWY9oCbH8jmRHVGrgnt+1c5a5OIDV3Bplwj5XlimCt+MBppFFhY4Cl5X9mLHegIF5rwetfKe
9Kkpg/iyFONuKIdEw5Aa3jipPKxDTWRFzt0oqVzyc3sE+Bfoq7HzLlxkbnMxOhK4vLMR5H2PgVGa
O42J9E2TZns8A+3Tmh2a82VQ9aDQdZ8vr/DqgkOY+GmciXnEQ45GcuNkNhKv9yUeOImQd37Da2q5
w8tES6x4kIvnxyweSxFEyDRSJ80KXZ+FwYnVGnjylRBTMt2AhGZ12bVoKPthLr6EqDjAmRKGpR5n
ZK0GLi+pcIXHlg98iWX1jkNUDqvdpYA5lGDANMmWcCyjEvUfSHu9HH5rt52Q9CI7rvj8Ksr6glKg
769LVZPrwbXwIousNE4mIgShhyx1SrflfRPXuAxkwDbSyS+GEowjCcEbgjtzSaNqV4eU5dZ4xZlD
Y+NN4Hct4WWZcmkEGkcJ5g8BViT7H78OealYLrnECQF+lbptAAY+supKEDnY0Cv1v+x1v5cCxQkb
CNxVN+KB+zeEQ2IgyudWS2Xq/mzBJJMkoTTrBf+aIq6bfT/xZVEKpjBqs/SIHIAN/HKK6INeMYID
TjCCA0oCAQEwgYkwdTELMAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0Q29tIEx0ZC4xKTAnBgNV
BAsTIFN0YXJ0Q29tIENlcnRpZmljYXRpb24gQXV0aG9yaXR5MSMwIQYDVQQDExpTdGFydENvbSBD
bGFzcyAxIENsaWVudCBDQQIQM//KELCg8G/aHYGqZtsm2TAJBgUrDgMCGgUAoIIBmTAYBgkqhkiG
9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0xNjA0MTUyMTA0MjRaMCMGCSqGSIb3
DQEJBDEWBBRl9FccrLcCeX1Lcem0O2ZINP55VjCBmgYJKwYBBAGCNxAEMYGMMIGJMHUxCzAJBgNV
BAYTAklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSkwJwYDVQQLEyBTdGFydENvbSBDZXJ0aWZp
Y2F0aW9uIEF1dGhvcml0eTEjMCEGA1UEAxMaU3RhcnRDb20gQ2xhc3MgMSBDbGllbnQgQ0ECEDP/
yhCwoPBv2h2BqmbbJtkwgZwGCyqGSIb3DQEJEAILMYGMoIGJMHUxCzAJBgNVBAYTAklMMRYwFAYD
VQQKEw1TdGFydENvbSBMdGQuMSkwJwYDVQQLEyBTdGFydENvbSBDZXJ0aWZpY2F0aW9uIEF1dGhv
cml0eTEjMCEGA1UEAxMaU3RhcnRDb20gQ2xhc3MgMSBDbGllbnQgQ0ECEDP/yhCwoPBv2h2Bqmbb
JtkwDQYJKoZIhvcNAQEBBQAEggEADZHNi0HNO/2r2HMNKdp324bzhEpFOCathLMt6NOseGnPrEEm
c70ywa/vcpb8hSJG22wKEaFFxGPzJOZrto0KtGA5RrsEVUtY5BVrpoxujzl1CqymmipSmBIllr8r
8ZkUD4COI0w78Lpl6gjOqcv1NvkJUT+mam3gGmsY9fOMagJksPtEZA8+aTamdDGMMVeyuO5JCPxu
L0F54p05g89iVzWQ8S+VjhWXEz8cclR9qTdNnt6x79XZhfYf0XTC8IrpCzBt6xcdNIfS1bDoP4ah
yuynw7U9ZEsjxb4fULDIm1ESlvSgWHFrBmIiO0AbOpQpMAtOXC6gXP8avUJzBy2EqAAAAAAAAA==

--Apple-Mail-435F839C-3CCD-4863-9D2C-4C08F841E798--


From nobody Fri Apr 15 15:23:30 2016
Return-Path: <rwfranks@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 70EA612E0DB; Fri, 15 Apr 2016 15:23:28 -0700 (PDT)
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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 KrTYIuFBSoeF; Fri, 15 Apr 2016 15:23:27 -0700 (PDT)
Received: from mail-ob0-x236.google.com (mail-ob0-x236.google.com [IPv6:2607:f8b0:4003:c01::236]) (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 CD55B12E123; Fri, 15 Apr 2016 15:23:26 -0700 (PDT)
Received: by mail-ob0-x236.google.com with SMTP id bg3so71550202obb.1; Fri, 15 Apr 2016 15:23:26 -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=ibnTvl10asQ94XwXFIREg4h8y0xdeFsNiFEjCM55oys=; b=MRqp2YPs0oBT2Spypedq0/cBCCBxLzitiGy1Z8RlzBwnDYKdE3jTx9LvsY5qQDo2/8 7xoLr7gK/MCdE0JzYa1zbeaMM38K1UJzUkzMFPGPkAPat0isxM1Sk3EA76QbtYyQ8dNb JuE7/8HHJD/fF2XVFDmzcqb+dBO7iFRsYPedeo/8SfJ+wNNnlrR+mSZIw6AF8AL1h2u7 eZrPQDQo6QjAXdYON73kCcXyAuq/RD85HPZ6JzdRLoDxniFwna84YTgetHF+v3r+bBjm Z4h+iMNlobi44UcXx1tpobndKEDqHxD1qgstdwFiQOjfZ22SVwtKtJf5hBVsZrmzz7/Z PdcQ==
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=ibnTvl10asQ94XwXFIREg4h8y0xdeFsNiFEjCM55oys=; b=iAF+hXsjMtqFZS90qTR1qDAgB1I3SqNKAHElt0V7h4xijqHuo/N1NbxZt5YsyoL7Dl ZjFEcgMp84yv1hPVal08wXuJQqgUCcDl7p2uTFjrdugjKjyNjc28iisfq3XdxKo1Ggod 8gA70m34BVzBz2cI2TWlfjt3aPfvEb4vuwGu9UjSbMrT2qXk86bvTa7uQ1jt75+hl4CZ dcDAMTk1BBbOm/kOGPMRpwQE65CZ4TuC4u4o6RuWdw6CVym1EMgppVixqgXLrSLQ65/f lUsLJW8ZMD5JrTG02S8qydVWhcWnGyecZxds+tcnt+cBkORJa4CwV52Rt34hsD+5spCS wuLQ==
X-Gm-Message-State: AOPr4FWnrPejPXS9gniO5n0magrkYssWfml+kDgkLS7avYQYfumAcORuGAW6BFtVZCw9anwiSrR4m8GGikGbpg==
X-Received: by 10.182.98.167 with SMTP id ej7mr12429275obb.46.1460759006197; Fri, 15 Apr 2016 15:23:26 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.182.114.136 with HTTP; Fri, 15 Apr 2016 15:22:46 -0700 (PDT)
In-Reply-To: <20160415185238.6233.qmail@ary.lan>
References: <alpine.LRH.2.01.1604151118350.13335@egate.xpasc.com> <20160415185238.6233.qmail@ary.lan>
From: Dick Franks <rwfranks@gmail.com>
Date: Fri, 15 Apr 2016 23:22:46 +0100
Message-ID: <CAKW6Ri6NSrsTw=LV_eErvjPQgW5QW_0EM0xJCsff_p9Eh2vk3g@mail.gmail.com>
Subject: Re: [89attendees] spam on old lists - was Fw: new important message
To: ietf@johnlevine.com
Content-Type: multipart/alternative; boundary=047d7b2e41ecaac38e05308d7517
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/A6QxkE-1P8uyy-7Ysthag25VgnQ>
Cc: IETF Discussion <ietf@ietf.org>, 89attendees@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: Fri, 15 Apr 2016 22:23:28 -0000

--047d7b2e41ecaac38e05308d7517
Content-Type: text/plain; charset=UTF-8

On 15 April 2016 at 19:52, <ietf@johnlevine.com> wrote:
[snip]

> In this particular case, filtering by From: address on mailing lists
> still works well enough, particularly here where the participants tend
> to be technically sophisticated and so are somewhat less likely to get
> their accounts p3ned than average users.  So I agree that we might as
> well turn off useless old meeting lists, but I don't see any need to
> twiddle things beyond that.
>

So what needs to be done to make it happen?

--047d7b2e41ecaac38e05308d7517
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra">
<br><div class=3D"gmail_quote">On 15 April 2016 at 19:52,  <span dir=3D"ltr=
">&lt;<a href=3D"mailto:ietf@johnlevine.com" target=3D"_blank">ietf@johnlev=
ine.com</a>&gt;</span> wrote:<br><div>[snip] <br></div><blockquote class=3D=
"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding=
-left:1ex">
In this particular case, filtering by From: address on mailing lists<br>
still works well enough, particularly here where the participants tend<br>
to be technically sophisticated and so are somewhat less likely to get<br>
their accounts p3ned than average users.=C2=A0 So I agree that we might as<=
br>
well turn off useless old meeting lists, but I don&#39;t see any need to<br=
>
twiddle things beyond that.<br></blockquote><div><br></div><div>So what nee=
ds to be done to make it happen?<br></div><div><br><br>=C2=A0</div></div></=
div></div>

--047d7b2e41ecaac38e05308d7517--


From nobody Fri Apr 15 15:33:37 2016
Return-Path: <jared@puck.nether.net>
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 27F5712E0B7 for <ietf@ietfa.amsl.com>; Fri, 15 Apr 2016 15:33:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.198
X-Spam-Level: 
X-Spam-Status: No, score=-5.198 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.996, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] 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 ydf4ZK5VL7RK for <ietf@ietfa.amsl.com>; Fri, 15 Apr 2016 15:33:33 -0700 (PDT)
Received: from puck.nether.net (puck.nether.net [204.42.254.5]) by ietfa.amsl.com (Postfix) with ESMTP id 2E5EB12D0B0 for <ietf@ietf.org>; Fri, 15 Apr 2016 15:33:32 -0700 (PDT)
Received: from [IPv6:2601:401:4:3000:206b:5db8:4177:73ca] (unknown [IPv6:2601:401:4:3000:206b:5db8:4177:73ca]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by puck.nether.net (Postfix) with ESMTPSA id 9E05B5409B1; Fri, 15 Apr 2016 18:33:30 -0400 (EDT)
Subject: Re: spam on old lists - was [89attendees]
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Content-Type: text/plain; charset=utf-8
From: Jared Mauch <jared@puck.nether.net>
In-Reply-To: <20160415185647.GV3997@verdi>
Date: Fri, 15 Apr 2016 18:33:30 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <BA94C5C3-1B4D-455A-92C1-68C7DFCDD3DD@puck.nether.net>
References: <alpine.LRH.2.20.1604151309440.27222@ns0.nohats.ca> <00DFA933-A21B-4C0C-AFC8-319FF7AA1DFD@consulintel.es> <20160415175336.GU3997@verdi> <433046AF-64F4-486A-BBD0-251829CEEB5B@consulintel.es> <20160415185647.GV3997@verdi>
To: John Leslie <john@jlc.net>
X-Mailer: Apple Mail (2.3124)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/YUJQ30e_2WqQD20K-6L-M_5ouQk>
Cc: IETF discussion list <ietf@ietf.org>, JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
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: Fri, 15 Apr 2016 22:33:36 -0000

> On Apr 15, 2016, at 2:56 PM, John Leslie <john@jlc.net> wrote:
>=20
>> If we have from the community negative reports about bad-behaviours
>> from any of those DNS-BLs for example.
>=20
>   Again, how much are you contributing to the costs of what you ask?

I=E2=80=99m reminded of a recent discussion on another list about how to =
turn off
IPv6 but just for google because the users were infected with malware =
and
got CAPTCHAs. The abuse in v4 is quiet, but when the hosts moved to =
dual-stack
and IPv6 capable it became obvious.

The provider blamed google and wanted to know how to disable IPv6 for =
google=20
only.

DNSBL/RBL are a part of life on the internet in the past 20 years.  You =
don=E2=80=99t
deal with abuse at your own peril, as once you=E2=80=99re the noisiest =
abuser and added
you generally have a *lot* of work to clean up.

Having worked at places that got corporate mail servers added to DNSBL =
as a
business response to not terminating people for AUP violations before, =
this is
hard to explain and deal with.

I likely didn=E2=80=99t see the messages on the old list due to it =
matching a known
message pattern that is blocked.  I know everyone wants @ietf lists to =
be
sufficiently promiscuous to have a low barrier to participating, but=20
we must perform some basic security operations to block them.

Regarding locking the lists?  I=E2=80=99m all for that after IETF closes
out the venue contract/payments.  It should be a mechanical operation
that coincides.  This way if there is a venue problem or something =
specific
those at the meeting can discuss, otherwise the general public doesn=E2=80=
=99t get
spammed with details.

- Jared


From nobody Fri Apr 15 16:46:44 2016
Return-Path: <johnl@taugh.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 B250512DDA7 for <ietf@ietfa.amsl.com>; Fri, 15 Apr 2016 16:46:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1536-bit key) header.d=iecc.com header.b=U57qqwz4; dkim=pass (1536-bit key) header.d=taugh.com header.b=USKwCx/w
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 0Bz2TNadXMRr for <ietf@ietfa.amsl.com>; Fri, 15 Apr 2016 16:46:42 -0700 (PDT)
Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EA53712DD89 for <ietf@ietf.org>; Fri, 15 Apr 2016 16:46:41 -0700 (PDT)
Received: (qmail 35643 invoked from network); 15 Apr 2016 23:46:39 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent; s=8b3a.57117d5f.k1604; bh=rrJQrmxwLX3EFj8qE/2STxsjpwQKdCnrUmFOl/TmZ5E=; b=U57qqwz4e8McaM18CSdxHqYn1yVO+x+rYdNxIpFjVF62gxd3dG1T7gl/9P0MOHbzs2jPhuUU+mvtPCCOgueTPBbuzqOxZrJMOidHgRirfYsD0S0CUvxBhlEg2vbfIomn9iLK6/29ANNbuy39xu/ZR8w8ZpIDY1a9Ap/zkXH23bH743Og/dKBa3WTz1p7hc0W/z3l7Icb+2OVEQPLiwOHc7w6Hj1ro7liJCtxt1EN3Y6dEoYaCg+9FXMVVlC/7wuY
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent; s=8b3a.57117d5f.k1604; bh=rrJQrmxwLX3EFj8qE/2STxsjpwQKdCnrUmFOl/TmZ5E=; b=USKwCx/w7P2b4e+ITpU7flYM9m2pcmEJ1Odc3/4kNjygpuu+8wDM/sBBB4e9uYZyixvbl7EroG2KgFuNr0sNbL8c333CI271+TN+I1GTog/9f3Xw3zoWgacKpE1Oq+F7oKkUfixgtL10E8b4nyzogAXbw4oGYfdXYU1sl6azmBz4mU9dwXQhnt+fI4gCnUTVGCnOROuIImQaLcfOeLgi1dWq6tDFBneL2CdSuYPPFSt5hJBShExpPLeSLtuWAHe6
Received: from localhost ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.0/X.509/SHA1) via TCP6; 15 Apr 2016 23:46:39 -0000
Date: 15 Apr 2016 19:46:38 -0400
Message-ID: <alpine.OSX.2.11.1604151938430.32352@ary.lan>
From: "John R Levine" <johnl@taugh.com>
To: "Benson Schliesser" <bensons@queuefull.net>
Subject: Re: spam on old lists - was [89attendees] Fw: new important message
In-Reply-To: <FBEF78BA-A260-4460-9090-F159D957531D@queuefull.net>
References: <20160415185238.6233.qmail@ary.lan> <FBEF78BA-A260-4460-9090-F159D957531D@queuefull.net>
User-Agent: Alpine 2.11 (OSX 23 2013-08-11)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/TQ9SqShPEbAGwA_iiuFhOHIRa2w>
Cc: 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: Fri, 15 Apr 2016 23:46:43 -0000

> The spam message in this case did not originate from any client or host under my control. It did not transit via any of my mail relays. It was a forgery - it spoofed my email address in the From header, and unfortunately happened to match it up with a To header addressing an IETF mailing list to which I'm subscribed.

Yeah, this is a new trend, crooks harvest address books and then do 
(from,to) pairwise spamming to take advantage of the common trick of 
whitelisting addresses in the recipient's address book.

If you're seeing a lot of forgery, SPF, DKIM, and DMARC will help 
somewhat, but since DMARC famously can't tell the difference between 
forged spam and mailing lists, I wouldn't turn on any DMARC policies. 
History suggests that in a while the bad guys will buy a new spam list and 
your bounces will drop back to normal.  FWIW I've been using my iecc.com 
address since 1993 and my taugh.com address since 2002, both have been 
scraped out the wazoo but with normal filtering both remain quite usable.

> Otherwise the only fix that I can imagine is for the IETF to start 
> opportunistically filtering list message submissions based on DMARC, 
> SPF, and DKIM, as well as performing sender rewriting in the list 
> software. Like most things, I imagine the subscribers on this list have 
> opinions about this - and I'd be glad to hear them.

Given that we've seen only one or two spams of this sort leak through, I'm 
not inclined to do anything about it.  An interesting thing to do would be 
to instrument the mail, do the various DNSBL, SPF, DKIM, and DMARC checks 
on incoming mail and log the results in the message headers.  Then we can 
gather data to tell us what would happen if we used them to filter.

On my smallish system, I use a few conservative DNSBLs to block mail, 
which knocks out about 2/3 of it, then SPF and DKIM as part of the 
spamassassin score.  I check DMARC but don't do anything beyond logging it 
except for a handful of high risk domains like paypal.com where DMARC 
failure almost always means phish.

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
Please consider the environment before reading this e-mail.


From nobody Sun Apr 17 08:33:24 2016
Return-Path: <llynch@civil-tongue.net>
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 6286612D93E for <ietf@ietfa.amsl.com>; Sun, 17 Apr 2016 08:33:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.901
X-Spam-Level: 
X-Spam-Status: No, score=-6.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001] 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 Ufy7DJKqpfsM for <ietf@ietfa.amsl.com>; Sun, 17 Apr 2016 08:33:22 -0700 (PDT)
Received: from hans.rg.net (hans.rg.net [IPv6:2001:418:1::42]) by ietfa.amsl.com (Postfix) with ESMTP id 2E34612D899 for <ietf@ietf.org>; Sun, 17 Apr 2016 08:33:22 -0700 (PDT)
Received: from hans.rg.net (hans.rg.net [IPv6:2001:418:1:0:0:0:0:42]) (authenticated bits=0) by hans.rg.net (8.15.2/8.14.9) with ESMTPSA id u3HFXKmt068329 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Sun, 17 Apr 2016 15:33:21 GMT (envelope-from llynch@civil-tongue.net)
Date: Sun, 17 Apr 2016 15:33:19 +0000 (UTC)
From: Lucy Lynch <llynch@civil-tongue.net>
X-X-Sender: llynch@hans.rg.net
To: carlos@lacnic.net
Subject: Re: thank you
In-Reply-To: <570D4A4C.5050406@gmail.com>
Message-ID: <alpine.BSF.2.20.1604171532040.42389@hans.rg.net>
References: <m24mb76cns.wl%randy@psg.com> <570D4A4C.5050406@gmail.com>
User-Agent: Alpine 2.20 (BSF 67 2015-01-07)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII; format=flowed
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/SfI29id61W1zaugVv4bPqtVQhwE>
Cc: IETF Disgust List <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: Sun, 17 Apr 2016 15:33:23 -0000

On Tue, 12 Apr 2016, Carlos M. Martinez wrote:

> Thank you Randy. I'm extremely happy that the meeting went well, and
> that, except for a few glitches here and there, every one had a good and
> productive time in BA.

and some of us got to tango - and eat ice cream! Lovely city, lovely 
people, and a good meeting. I'll be back.

- Lucy

> On 4/11/16 6:47 PM, Randy Bush wrote:
>> buenos aires is a beautiful latin american city, hospitable, and with
>> great folk.  kudos for such a great meeting go to many people and
>> organizations that i will not enumerate for fear of missing one.  thank
>> you.
>>
>> randy
>>
>
>


From nobody Sun Apr 17 13:10:29 2016
Return-Path: <peter@akayla.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 700CF12DE12; Sun, 17 Apr 2016 13:10:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_NONE=-0.0001] 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 taz873cNHEaI; Sun, 17 Apr 2016 13:10:25 -0700 (PDT)
Received: from p3plsmtpa11-03.prod.phx3.secureserver.net (p3plsmtpa11-03.prod.phx3.secureserver.net [68.178.252.104]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C4C2912DE77; Sun, 17 Apr 2016 13:10:25 -0700 (PDT)
Received: from [10.10.0.32] ([181.110.255.3]) by p3plsmtpa11-03.prod.phx3.secureserver.net with  id jYAK1s00505AX1901YANUq; Sun, 17 Apr 2016 13:10:25 -0700
User-Agent: Microsoft-MacOutlook/14.6.2.160219
Date: Sun, 17 Apr 2016 13:10:17 -0700
Subject: Gen-ART LC/Telechat review of draft-ietf-pce-iro-update-06
From: Peter Yee <peter@akayla.com>
To: <draft-ietf-pce-iro-update.all@ietf.org>
Message-ID: <D3393302.16A48%peter@akayla.com>
Thread-Topic: Gen-ART LC/Telechat review of draft-ietf-pce-iro-update-06
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/wE0AaY7H8zQzD4r1nrlGgjud3mg>
Cc: gen-art@ietf.org, IETF <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: Sun, 17 Apr 2016 20:10:27 -0000

I am the assigned Gen-ART reviewer for this draft. The General Area Review
Team (Gen-ART) reviews all IETF documents being processed by the IESG for
the IETF Chair. Please wait for direction from your document shepherd or
AD before posting a new version of the draft.

For more information, please see the FAQ at
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Document: draft-ietf-pce-iro-update-06
Reviewer: Peter Yee
Review Date: Apr-17-2016
IETF LC End Date: Mar-29-2016
IESG Telechat date: Apr-21-2016

Summary: This draft is basically ready for publication as a Standards
Track RFC, but has some nits that should be fixed before publication.
[Ready with nits]

This specification documents the results of a survey regarding
implementation of the Include Route Object for PCEP and uses those results
to clarify the meaning of section 7.12 of RFC 5440 with updated text.

Major issues: None

Minor issues: None really

Page 5, Section 4, 1st paragraph, 2nd sentence: Are you sure that
confusing interpretation of the IRO ordering or the L bit doesn=E2=80=99t cause
any security issues?  I=E2=80=99m not PCEP savvy enough to know if mistakenly
sending information that should have gone strictly through a loose node
would disclose anything that the originator didn=E2=80=99t really wish any nodes
outside of the strict list to see.


Nits:

Page 3, first full paragraph: insert =E2=80=9Can=E2=80=9D before =E2=80=9CIRO=E2=80=9D.

Page 3, Section 2 title: insert =E2=80=9Cthe=E2=80=9D before =E2=80=9CIRO=E2=80=9D.

Page 3, Section 2, 3rd paragraph, 2nd sentence: insert =E2=80=9Cthem=E2=80=9D before th=
e
second =E2=80=9Cas=E2=80=9D.

Page 4, Section 2, 1st paragraph: append a colon to the end of the
paragraph.

Page 4, Section 2, indented bullet item: remove the hyphen and put the
remainder between double quotes, not single quotes.

Page 4, Section 2, 1st major bullet item, 1st sentence: insert =E2=80=9Can=E2=80=9D bef=
ore
=E2=80=9CIRO=E2=80=9D. =20

Page 4, Section 2, 1st major bullet item, 2nd sentence: change
=E2=80=9Ccomprising=E2=80=9D to =E2=80=9Ccomprised=E2=80=9D.  Insert =E2=80=9Cto=E2=80=9D before =E2=80=9Csection=E2=80=9D.

Page 4, Section 2, 2nd major bullet item, 1st sentence: insert =E2=80=9Can=E2=80=9D bef=
ore
=E2=80=9CIRO=E2=80=9D.  Change the comma to a semicolon.

Page 4, Section 2, 2nd major bullet item, 3rd sentence: insert =E2=80=9Cthe=E2=80=9D
before =E2=80=9CLoose=E2=80=9D.

Page 4, Section 3, 2nd paragraph, 1st sentence: delete comma.

Page 4, Section 3, 2nd paragraph, 2nd sentence: change trailing space and
hyphen to a colon.

Page 4, Section 3, 1st bullet item: delete comma after =E2=80=9CIRO=E2=80=9D.  Insert
=E2=80=9Cthe=E2=80=9D before the last =E2=80=9CIRO=E2=80=9D.

Page 5, Section 3, 1st paragraph: insert =E2=80=9Cthe=E2=80=9D before =E2=80=9CIRO=E2=80=9D.

Page 5, Section 4, 1st paragraph, 1st sentence: insert =E2=80=9Cthe=E2=80=9D before =E2=80=9C=
IRO=E2=80=9D.








From nobody Sun Apr 17 13:18:44 2016
Return-Path: <peter@akayla.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 5103D12D65D; Sun, 17 Apr 2016 13:18:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001] 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 x-PJbatr3Bau; Sun, 17 Apr 2016 13:18:41 -0700 (PDT)
Received: from p3plsmtpa11-04.prod.phx3.secureserver.net (p3plsmtpa11-04.prod.phx3.secureserver.net [68.178.252.105]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BEEE612D57D; Sun, 17 Apr 2016 13:18:41 -0700 (PDT)
Received: from [10.10.0.32] ([181.110.255.3]) by p3plsmtpa11-04.prod.phx3.secureserver.net with  id jYJc1s00505AX1901YJfXP; Sun, 17 Apr 2016 13:18:41 -0700
User-Agent: Microsoft-MacOutlook/14.6.2.160219
Date: Sun, 17 Apr 2016 13:18:35 -0700
Subject: Gen-ART Telechat review of draft-ietf-tictoc-ptp-mib-08
From: Peter Yee <peter@akayla.com>
To: <draft-ietf-tictoc-ptp-mib.all@ietf.org>
Message-ID: <D3393DAB.16AA3%peter@akayla.com>
Thread-Topic: Gen-ART Telechat review of draft-ietf-tictoc-ptp-mib-08
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/y1r4rfWEkMemvNh-RWGIsWyvzN0>
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, IETF <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: Sun, 17 Apr 2016 20:18:43 -0000

I am the assigned Gen-ART reviewer for this draft. The General Area Review
Team (Gen-ART) reviews all IETF documents being processed by the IESG for
the IETF Chair. Please wait for direction from your document shepherd or
AD before posting a new version of the draft.

For more information, please see the FAQ at
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.


Document: draft-ietf-tictoc-ptp-mib-08
Reviewer: Peter Yee
Review Date: March 8, 2016
IETF LC End Date: March 8, 2016
IESG Telechat date: April 21, 2016

Summary: This draft is basically ready for publication as a Standards
Track RFC, but has nits and a couple of minor issues that should be
fixed/considered before publication. [Ready with issues]

This draft defines an SMIv2 MIB for use with the Precision Time Protocol
v2 (IEEE Std. 1588-2008).  I do not have access to this standard, so my
review primarily addresses nits within the module and not whether the
module itself is a fair representation of a MIB suitable for use with PTP
v2.

The following review was originally submitted for the LC (see
http://www.ietf.org/mail-archive/web/gen-art/current/msg13014.html).  As
no update has been issued for the draft, the content of that review is
copied below.

Major issues: None

Minor issues:

Given that the draft seems to quote a fair amount of text (at least 5
pages) from IEEE Std. 1588-2008 in the definitions section if not
elsewhere, it might be good to make sure that there are no copyright
issues.

Many of the object descriptions use identical text.  While that's helpful
from the direct lookup point of view, it doesn't help to distinguish these
items from others of their ilk.  I'm not sure if this matters, but perhaps
enhancing the descriptions in their contexts might make them more useful.

Nits:

General:

Replace all occurrences of "create logical group" with "create a logical
group".

Watch the case and spacing of object names in their descriptions.
Sometime there's a space between two words, sometimes not.  Some words are
capitalized in one place and not another.  Use of camel case conventions
comes and goes.  It's probably best to treat the object names as English
words in the descriptions, separating words with spaces and generally
writing them in lower case.  Sure, the inconsistency doesn't hurt a lot,
but it ends up looking a wee bit sloppy.  The RFC Editor may not be sure
how to handle the inconsistency as some word combinations might appear to
be technical MIB terms that should be left as is.

Drop the draft name from the center, top header.  Generally a shortened
form of the draft title is placed here.  Perhaps you could use "PTPv2 MIB"?

I'll leave the serial comma be.  It appears in some places and not others.
I like them, but there are enough missing ones that I'm just going to let
it slide. ;-)

When citing the official name of IEEE 1588-2008, use a lower case "a=E2=80=9D
before "Precision".  That aligns with IEEE's title.

The authors' addresses in Section 9 have way too many punctuation marks in
them.  A few less commas would go a long way.  Maybe change some into
serial commas for sprinkling elsewhere in the document? ;-)

Specific:

Page 2, Section 1, 1st paragraph, 2nd sentence: delete "the=E2=80=9D before
"ordinary".  Make "ordinary clock" and "transparent clock" plural.  Insert
a comma and "and" after "transparent clocks".

Page 3, Section 1.1, 1st paragraph, 2nd sentence: append a comma after
"e.g.".

Page 5, 1st bullet item: delete the comma after "STD 62".

Page 5, 2nd bullet item, 2nd sentence: insert "is" before "described".

Page 5, 3rd bullet item, 2nd sentence: insert "is" before "described".

Page 5, 3rd bullet item, last sentence: insert "is" before "described".

Page 7, MIB Description, 1st paragraph, 1st sentence: change "MIB is to
support" to "MIB supports".

Page 8, Acronyms, EUI: delete the period after the acronym expansion.

Page 12, PTP node definition: insert "A" before the sentence.

Page 16, ClockIdentity description: the term "MAC-48" has not been defined
or previously referenced in the draft.  It's also not quite an exact
synonym for EUI-48, so perhaps it should be defined.

Page 17, ClockMechanismType description: replace "End to End=E2=80=9D with
"end-to-end".  Replace "peer to peer" with "peer-to-peer".

Page 19, ClockPortTransportTypeAddress description, 2nd sentence: change
"Transport" to "transport".

Page 19, ClockPortTransportTypeAddress description, 4th sentence: insert
"an" before "address".  Change "and" to "or".

Page 20, ClockQualityAccuracyType description: change "section=E2=80=9D to
"sections".  Insert "of" before "RFC 2578", which should be placed in
square brackets.  Change "to start with" to "starting at".

Page 23, ClockStateType description: insert "a" before "PTP".

Page 24, Holdover state text: change "ptp" to "PTP.  Change "FREERUN=E2=80=9D to
"Freerun".

Page 25, ClockTimeSourceType description: change "section" to "sections=E2=80=9D.
Insert "of" before "RFC 2578", which should be placed in square brackets.
Change "to start with" to "starting at".

Page 26, ClockTimeSourceType reference: change "Section" to "Sections".

Page 32, ptpbaseClockCurrentDSOffsetFromMaster and
ptpbaseClockCurrentDSMeanPathDelay references: the indentation looks a bit
off here.

Page 32, ptpbaseClockCurrentDSMeanPathDelay description: change "measure=E2=80=9D
to "measured".

Page 35, ptpbaseClockParentDSOffset description (near top of page): change
"clocks" to "clock's".

Page 35, ptpbaseClockParentDSClockPhChRate description: change "clocks=E2=80=9D t=
o
"clock's".

Page 41, ptpbaseClockRunningState description: insert "a" before "PTP=E2=80=9D.
Append a comma after "engine".

Page 42, top: Rather than duplicate the state descriptions information
here, why not merely point back to ClockStateType?  Btw, PTP engine hasn't
been defined.

Page 42, Holdover state, 1st sentence: if you do not remove this paragraph
as suggested in the previous comment, change "ptp" to "PTP".

Page 42, ptpbaseClockRunningPacketsSent description: replace "packet
Unicast and multicast" with "unicast and multicast packets".

Page 42, ptpbaseClockRunningPacketsReceived description: replace =E2=80=9Cpacket
Unicast and multicast" with "unicast and multicast packets".

Page 44, ptpbaseClockTimePropertiesDSCurrentUTCOffsetValid description:
insert "the" before "UTC".

Page 45, ptpbaseClockTimePropertiesDSCurrentUTCOffset description (at top
of page): insert "the" before "UTC".

Page 49, ptpbaseClockTransDefaultDSDelay description (at top of page):
change "shall be" to "of".  Change "If" to "if".

Page 56, ptpbaseClockPortRunningTable description: should that be =E2=80=9Ca
dataset" or "datasets".  Plain "dataset" doesn't work.

Page 57, ptpbaseClockPortRunningEntry description: change "runing=E2=80=9D to
"running" unless Viking writing is involved.

Page 58, ptpbaseClockPortRunningState description: you probably don't need
to include the states here since they are already found in the definition
of ClockPortState.

Page 60, ptpbaseClockPortRunningEncapsulationType description: change
"eg.=E2=80=9D to "e.g.,".

Page 60, ptpbaseClockPortRunningRxMode description: change "specifie=E2=80=9D to
"specifies".

Page 63, ptpbaseClockPortTransDSPeerMeanPathDelay description: delete the
parentheses and append a comma after PTP.  On the following page, change
"value is" to "value of".

Page 64, ptpbaseClockPortAssociateTable description: change "which=E2=80=9D to
"that".

Page 75, ptpbaseMIBClockPortTransDSGroup description: does =E2=80=9C TransparentD=
S
Dataset" contain a redundancy?

Page 76, 4th paragraph, 1st sentence: delete "the" before "implementers=E2=80=9D.
Delete "as".

Page 76, 5th paragraph, 1st sentence: change "Further" to "Furthermore". =20



From nobody Mon Apr 18 06:05:23 2016
Return-Path: <david.black@emc.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 2477F12D5D7; Mon, 18 Apr 2016 06:05:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.317
X-Spam-Level: 
X-Spam-Status: No, score=-5.317 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.996, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=emc.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 pJAXAN0rYD1f; Mon, 18 Apr 2016 06:05:15 -0700 (PDT)
Received: from mailuogwdur.emc.com (mailuogwdur.emc.com [128.221.224.79]) (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 9805B12D60F; Mon, 18 Apr 2016 06:05:15 -0700 (PDT)
Received: from maildlpprd53.lss.emc.com (maildlpprd53.lss.emc.com [10.106.48.157]) by mailuogwprd51.lss.emc.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.0) with ESMTP id u3ID58ZA010541 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 18 Apr 2016 09:05:09 -0400
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd51.lss.emc.com u3ID58ZA010541
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=emc.com; s=jan2013; t=1460984709; bh=hBMeVa+zh9In9/S5DCDKI4HW7RY=; h=From:To:CC:Subject:Date:Message-ID:References:In-Reply-To: Content-Type:Content-Transfer-Encoding:MIME-Version; b=riy6hRjooHfNi10zHttjD3l6DurcbCQSAjtqNL6ExhKYIfwddcirU4OzyGgtuFrH7 aJY2gZH5jjTqj47rjpu9uL4TeHN1u4AmKfNSFQleIF0mHskUmUHRwWfa7hTrwYMtCL RseHbZ7+Isj6Z6gn2kW9M9U87yfyG05EuDUQ+L6M=
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd51.lss.emc.com u3ID58ZA010541
Received: from mailusrhubprd01.lss.emc.com (mailusrhubprd01.lss.emc.com [10.253.24.19]) by maildlpprd53.lss.emc.com (RSA Interceptor); Mon, 18 Apr 2016 09:04:30 -0400
Received: from MXHUB106.corp.emc.com (MXHUB106.corp.emc.com [10.253.58.23]) by mailusrhubprd01.lss.emc.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.0) with ESMTP id u3ID4rjo018392 (version=TLSv1 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 18 Apr 2016 09:04:53 -0400
Received: from MX104CL02.corp.emc.com ([169.254.8.9]) by MXHUB106.corp.emc.com ([10.253.58.23]) with mapi id 14.03.0266.001; Mon, 18 Apr 2016 09:04:52 -0400
From: "Black, David" <david.black@emc.com>
To: Cullen Jennings <fluffy@iii.ca>
Subject: RE: [tsvwg] Last Call: <draft-ietf-tsvwg-rtcweb-qos-15.txt> (DSCP and other packet markings for WebRTC QoS) to Proposed Standard
Thread-Topic: [tsvwg] Last Call: <draft-ietf-tsvwg-rtcweb-qos-15.txt> (DSCP and other packet markings for WebRTC QoS) to Proposed Standard
Thread-Index: AQHRg5nK94t/8iR5sU+B/9y+8LxFIp9nE2eAgADT/gCACkcQgIAGp9UQgBKxIQCABFTqQA==
Date: Mon, 18 Apr 2016 13:04:52 +0000
Message-ID: <CE03DB3D7B45C245BCA0D243277949362E96B03B@MX104CL02.corp.emc.com>
References: <20160321174750.31944.71903.idtracker@ietfa.amsl.com> <56F26AD3.3010403@ericsson.com> <5BB71158-3530-47A2-9A33-811F65B2F677@iii.ca> <56FBBBC1.5060902@ericsson.com> <CE03DB3D7B45C245BCA0D243277949362E92B245@MX104CL02.corp.emc.com> <D12A5B0E-EF12-4BC8-999B-6ED50029C95A@iii.ca>
In-Reply-To: <D12A5B0E-EF12-4BC8-999B-6ED50029C95A@iii.ca>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.239.240.141]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Sentrion-Hostname: mailusrhubprd01.lss.emc.com
X-RSA-Classifications: public
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/yPJT_gV656_ddI99RoPUXA8J_Xk>
Cc: Magnus Westerlund <magnus.westerlund@ericsson.com>, "draft-ietf-tsvwg-rtcweb-qos@ietf.org" <draft-ietf-tsvwg-rtcweb-qos@ietf.org>, "tsvwg@ietf.org" <tsvwg@ietf.org>, "Black, David" <david.black@emc.com>, "tsvwg-chairs@ietf.org" <tsvwg-chairs@ietf.org>, "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: Mon, 18 Apr 2016 13:05:17 -0000

So, summarizing Magnus's concerns with proposals:

> > [1] Flow Type in application-facing browser API:

> > Propose an additional sentence:
> > OLD
> >   o  Flow Type: The browser provides this input as it knows if the flow
> >      is audio, interactive video with or without audio, non-interactive
> >      video with or without audio, or data.
> > NEW
> >   o  Flow Type: The browser provides this input as it knows if the flow
> >      is audio, interactive video with or without audio, non-interactive
> >      video with or without audio, or data.  For audio that is associate=
d
> >      with a video flow, the flow type of the associated video MAY
> >      be used instead of the associated audio type.

Magnus - does that new text suffice?

> > [2] What does "interactive" mean in an implementation?:
>=20
> We could add something along lines of ..... Currently in WebRTC, media se=
nt over
> RTP is assumed to be interactive while media streamed over HTTP is assume=
d not
> to be. Future WebRTC extensions could allow streamed media over RTP.

I believe the proposed additional sentence addresses the question of how a =
browser
determines whether a video flow is interactive.  This proposed sentence wil=
l need to
cite a WebRTC document that contains a statement to that effect, as I don't=
 think this
draft is the right place to be the primary reference for that statement.

Magnus - would this approach be ok?

Thanks, --David

> -----Original Message-----
> From: Cullen Jennings [mailto:fluffy@iii.ca]
> Sent: Friday, April 15, 2016 10:48 AM
> To: Black, David
> Cc: Magnus Westerlund; ietf@ietf.org; tsvwg-chairs@ietf.org; draft-ietf-t=
svwg-
> rtcweb-qos@ietf.org; tsvwg@ietf.org
> Subject: Re: [tsvwg] Last Call: <draft-ietf-tsvwg-rtcweb-qos-15.txt> (DSC=
P and
> other packet markings for WebRTC QoS) to Proposed Standard
>=20
>=20
> > On Apr 3, 2016, at 3:37 PM, Black, David <david.black@emc.com> wrote:
> >
> > I see a couple of Magnus's points that appear to need additional text
> > in the draft:
> >
> > [1] Flow Type in application-facing browser API:
> >
> >>>>>> o Flow Type: The browser provides this input as it knows if
> >>>>>> the flow is audio, interactive video with or without audio,
> >>>>>> non-interactive video with or without audio, or data.
> >
> > [... snip ...]
> >
> >> The main issue here is that to me it was not clear that "Interactive
> >> Video with or without audio" allows for setting these DSCP values also
> >> for the RTP stream containing audio also. This, I do see a need for
> >> clarification on.
> >
> > Propose an additional sentence:
> > OLD
> >   o  Flow Type: The browser provides this input as it knows if the flow
> >      is audio, interactive video with or without audio, non-interactive
> >      video with or without audio, or data.
> > NEW
> >   o  Flow Type: The browser provides this input as it knows if the flow
> >      is audio, interactive video with or without audio, non-interactive
> >      video with or without audio, or data.  For audio that is associate=
d
> >      with a video flow, the flow type of the associated video MAY
> >      be used instead of the associated audio type.
> >
> > I hesitate to say anything stronger than "MAY" here.
>=20
> Looks good.
>=20
> >
> > [2] What does "interactive" mean in an implementation?:
>=20
> We could add something along lines of ..... Currently in WebRTC, media se=
nt over
> RTP is assumed to be interactive while media streamed over HTTP is assume=
d not
> to be. Future WebRTC extensions could allow streamed media over RTP.
>=20
>=20
> >
> >> The issue is that this document is called: DSCP and other packet
> >> markings for WebRTC QoS. Then this document define something that is n=
ot
> >> immediately mappable onto what is being defined in the other WebRTC
> >> specifications. That is why I am raising that there need to be more
> >> clear coupling. If that coupling is to mostly happen in another
> >> document, can we at least then have a proposal on the table for that
> >> change to ensure that the result is understandable.
> >
> > Well, this TSVWG draft is definitely not the right place for a discussi=
on of
> > when a video flow is interactive or non-interactive - I hope we can agr=
ee
> > on that.
> >
> > Beyond that, as Cullen (Jennings) is both an author of this document an=
d
> > one of the chairs of the rtcweb WG, I'd suggest that he and/or the rtcw=
eb
> > WG propose an appropriate location for discussion of when a video flow
> > is interactive or non-interactive.  This TSVWG draft would then have an
> > additional sentence added, e.g.,
> >
> > 	See [TBD] for further discussion of how to determine
> > 	whether a video flow is interactive vs. non-interactive.
> >
> > I believe that the added reference here ([TBD] above) would be normativ=
e.
> >
> > Cullen?
>=20
> That discussion happened long ago for WebRTC and we decided we did not ne=
ed
> a JavaScript controls point in the WebRTC API to indicate if RTP was inte=
ractive or
> not. If people start doing streaming video over RTP we can come back and =
revisit
> this and trivially add an API to indicate that in the W3C WebRTC API. Par=
t of what
> drove this decision is the likes of Netflix / ITunes / Youtube are not as=
king the
> browser vendors for streaming media over RTSP or RTP. They think HTTP wor=
ks
> much better for this. Thus the browser vendors see no need for non intera=
ctive
> video over RTP. I agree with Magnus that this might change some day in th=
e
> future but right now, I think it's close enough that everyone can live wi=
th it.
>=20
> I'm not OK in treating it like some open issue that is still in discussio=
n that
> somehow holds up this spec - it's not.
>=20
> >
> > Thanks, --David (as document  shepherd)
> >


From nobody Mon Apr 18 08:24:37 2016
Return-Path: <iad@ietf.org>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 1E62D12D956; Sun, 17 Apr 2016 11:36:29 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: IETF Administrative Director <iad@ietf.org>
To: "IETF Announcement List" <ietf-announce@ietf.org>
Subject: Nominations sought: Jonathan B. Postel Service Award 2016
X-Test-IDTracker: no
X-IETF-IDTracker: 6.19.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20160417183629.28764.73327.idtracker@ietfa.amsl.com>
Date: Sun, 17 Apr 2016 11:36:29 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/ZnA4NZMIiLbqRZh7-cPWSERz1fI>
X-Mailman-Approved-At: Mon, 18 Apr 2016 08:24:35 -0700
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Reply-To: ietf@ietf.org
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: Sun, 17 Apr 2016 18:36:29 -0000

Greetings on behalf of the Internet Society,

We are pleased to announce that candidate nominations for the 2016
Jonathan B. Postel Service Award are now open.

This prestigious annual award is presented to an individual or
organization that has made outstanding contributions in service to
the data communications community.

The signature crystal globe and a USD 20,000 prize will be presented
at the 96th Internet Engineering Task Force (IETF) meeting in
Berlin, Germany (17 -22 July 2016) to the chosen candidate.

Nominations are encouraged for individuals or teams of individuals
from across the data communications industry around the world,
either by self-nomination or by third party.

Please submit your nominations using this web form and do not
hesitate to share this information with your networks:
https://www.internetsociety.org/form/postel-nominations

The deadline for nominations is 1700 UTC, 18 May 2016.

***

More About the Award ===========

The Jonathan B. Postel Service Award was established by the Internet
Society to honor a person who has made outstanding contributions in
service to the data communications community.

The award is focused on sustained and substantial technical
contributions, service to the community, and leadership. With
respect to leadership, the award committee places particular
emphasis on candidates who have supported and enabled others in
addition to their own specific actions.

The award is named for Dr. Jonathan B. Postel to recognize and
commemorate the extraordinary stewardship exercised by Jon Postel
over the course of a thirty-year career in networking.

Jon Postel served as the editor of the RFC series of notes from its
inception in 1969 until 1998. He also served as the ARPANET â€śnumbers
Czarâ€ť and Internet Assigned Numbers Authority over the same period
of time. He was a founding member of the Internet Architecture (nee
Activities) Board and the first individual member of the Internet
Society, which he also served as a Trustee.

Find out more ===========

Find the out more on the award, nomination procedures, and online
submission forms. https://www.internetsociety.org/postel

Learn more about Jon Postelâ€™s life and contributions.
https://www.internetsociety.org/what-we-do/grants-and-awards/awards/
postel-service-award/ten-year-tribute-jon-postel

I'm ready to nominate someone!
https://www.internetsociety.org/what-we-do/grants-and-awards/awards/
postel-service-award/procedures

For any questions please contact postel@isoc.org

Best Regards,

The Internet Society Team


From nobody Mon Apr 18 09:16:01 2016
Return-Path: <iaoc-chair@ietf.org>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id AD62512E1E6; Mon, 18 Apr 2016 09:15:52 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: The IAOC <iaoc-chair@ietf.org>
To: "IETF Announcement List" <ietf-announce@ietf.org>
Subject: =?utf-8?q?Interim_step_on_meetings_site_feedback_=E2=80=94_for_sit?= =?utf-8?q?es_currently_under_active_consideration?=
X-Test-IDTracker: no
X-IETF-IDTracker: 6.19.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20160418161552.9368.65562.idtracker@ietfa.amsl.com>
Date: Mon, 18 Apr 2016 09:15:52 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/-VFeYZIfbTcOt3EdCKlV50coBpI>
Cc: recentattendees@ietf.org, ietf@ietf.org, 95all@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Reply-To: ietf@ietf.org
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: Mon, 18 Apr 2016 16:15:52 -0000

All,

The IAOC and its meetings committee are continuing to review the situation with respect to meeting in Singapore.  As I noted about a week ago [1],  we are reviewing our meeting planning procedures to ensure that we have input at appropriate points to ensure issues are identified and addressed before contracts are signed and announcements made.  This will mean more transparency, including sharing the list of cities under consideration when we have a workable way to handle and hear the feedback.  We will make concrete progress on that at our retreat in a few weeks time.

In the meantime, we do have active site discussions and negotiations ready to close for meetings that are coming up.  In addition to reaching out to groups or agencies that have specific knowledge about travel for diverse groups including religious, ethnical and LGBTQ people, we are reaching out to the IETF community as a whole with this note.

In order to make sure we havenâ€™t overlooked something else that should have been properly considered for sites under consideration, as well as to gather some running code on how a feedback process might work, we would like to hear from anyone who is aware of reasons we could not have a successful meeting in any of the following cities, or of any limits to attendee accessibility or inclusiveness that should be considered:

	Paris
	Montreal
	Copenhagen

Please send your input to venue-selection@ietf.org.  It will help the review process if the Subject line had the name of the city first, Subject: <city>.

In order not miss the contract opportunities, city-specific input would be most helpful if received by the end of May 2, 2016.

Other input on the process will be best received in e-mail at venue-selection@ietf.org with the Subject line: Process.  As we iterate the process we will continue to seek input to fashion a meeting planning process that works.


Leslie,
for the IAOC.

[1] https://mailarchive.ietf.org/arch/msg/ietf/hKwBYOwPkE6VTA4mxxf00NTLLF0

-- 

-------------------------------------------------------------------
Leslie Daigle
Principal, ThinkingCat Enterprises LLC
ldaigle@thinkingcat.com
-------------------------------------------------------------------


From nobody Mon Apr 18 10:09:15 2016
Return-Path: <dharkins@lounge.org>
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 F3C0712E175; Mon, 18 Apr 2016 10:09:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_PASS=-0.001] 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 5HQov-aP2S96; Mon, 18 Apr 2016 10:09:12 -0700 (PDT)
Received: from colo.trepanning.net (colo.trepanning.net [69.55.226.174]) by ietfa.amsl.com (Postfix) with ESMTP id A3C3412E145; Mon, 18 Apr 2016 10:09:12 -0700 (PDT)
Received: from www.trepanning.net (localhost [127.0.0.1]) by colo.trepanning.net (Postfix) with ESMTP id 7F54B10224008; Mon, 18 Apr 2016 10:09:11 -0700 (PDT)
Received: from 69.12.173.8 (SquirrelMail authenticated user dharkins@lounge.org) by www.trepanning.net with HTTP; Mon, 18 Apr 2016 10:09:12 -0700 (PDT)
Message-ID: <8fb376e11631f9ddf73f9385ec5472c3.squirrel@www.trepanning.net>
In-Reply-To: <20160418161552.9368.65562.idtracker@ietfa.amsl.com>
References: <20160418161552.9368.65562.idtracker@ietfa.amsl.com>
Date: Mon, 18 Apr 2016 10:09:12 -0700 (PDT)
Subject: Re: Interim step on meetings site feedback  =?iso-8859-1?Q?=E2=80=94_for_sites_currently_under_active_consideration?=
From: "Dan Harkins" <dharkins@lounge.org>
To: venue-selection@ietf.org
User-Agent: SquirrelMail/1.4.14 [SVN]
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/IIeshiYALJV_w0eB8xaMf21pzhI>
Cc: 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: Mon, 18 Apr 2016 17:09:14 -0000

  First off, Oxford comma. Next, what's an "ethnical" person? And
third, as I observed at the plenary, bringing in a very diverse
opinion set on inclusiveness and accessibility will make us only
meet in Western Europe, North America, and Japan. And what's in the
queue for consideration? Western Europe and North America. Sigh.

  There are plenty of reasons to not meet in Singapore and it's a
shame that some members of the IETF community cannot bring their
family and/or be open and honest about their relationships. But
I think these issues should be balanced with the overall benefit
that the IETF World Tour provides. We are a diverse group and I
think we leave each city a little better off after we depart
because of it. Embargoes seldom have the desired effect.

  regards,

  Dan.

On Mon, April 18, 2016 9:15 am, The IAOC wrote:
> All,
>
> The IAOC and its meetings committee are continuing to review the situation
> with respect to meeting in Singapore.  As I noted about a week ago [1],
> we are reviewing our meeting planning procedures to ensure that we have
> input at appropriate points to ensure issues are identified and addressed
> before contracts are signed and announcements made.  This will mean more
> transparency, including sharing the list of cities under consideration
> when we have a workable way to handle and hear the feedback.  We will make
> concrete progress on that at our retreat in a few weeks time.
>
> In the meantime, we do have active site discussions and negotiations ready
> to close for meetings that are coming up.  In addition to reaching out to
> groups or agencies that have specific knowledge about travel for diverse
> groups including religious, ethnical and LGBTQ people, we are reaching out
> to the IETF community as a whole with this note.
>
> In order to make sure we havenâ€™t overlooked something else that should
> have been properly considered for sites under consideration, as well as to
> gather some running code on how a feedback process might work, we would
> like to hear from anyone who is aware of reasons we could not have a
> successful meeting in any of the following cities, or of any limits to
> attendee accessibility or inclusiveness that should be considered:
>
> 	Paris
> 	Montreal
> 	Copenhagen
>
> Please send your input to venue-selection@ietf.org.  It will help the
> review process if the Subject line had the name of the city first,
> Subject: <city>.
>
> In order not miss the contract opportunities, city-specific input would be
> most helpful if received by the end of May 2, 2016.
>
> Other input on the process will be best received in e-mail at
> venue-selection@ietf.org with the Subject line: Process.  As we iterate
> the process we will continue to seek input to fashion a meeting planning
> process that works.
>
>
> Leslie,
> for the IAOC.
>
> [1] https://mailarchive.ietf.org/arch/msg/ietf/hKwBYOwPkE6VTA4mxxf00NTLLF0
>
> --
>
> -------------------------------------------------------------------
> Leslie Daigle
> Principal, ThinkingCat Enterprises LLC
> ldaigle@thinkingcat.com
> -------------------------------------------------------------------
>
>



From nobody Mon Apr 18 10:38:39 2016
Return-Path: <melinda.shore@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 22D8512D7A0 for <ietf@ietfa.amsl.com>; Mon, 18 Apr 2016 10:38:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 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, RCVD_IN_DNSWL_LOW=-0.7, 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 HITfsy4KNPcm for <ietf@ietfa.amsl.com>; Mon, 18 Apr 2016 10:38:37 -0700 (PDT)
Received: from mail-pa0-x234.google.com (mail-pa0-x234.google.com [IPv6:2607:f8b0:400e:c03::234]) (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 F097612E30B for <ietf@ietf.org>; Mon, 18 Apr 2016 10:38:28 -0700 (PDT)
Received: by mail-pa0-x234.google.com with SMTP id r5so24654937pag.1 for <ietf@ietf.org>; Mon, 18 Apr 2016 10:38:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding; bh=5DpeVs9TkDJaOe8s+Rl3wA5/YjynCLr1i8OmuVqzfJ4=; b=Yyq83K07/1ZITX7lJUaK87ibPyH4S6qOah6da+15hC4BtGY7HMm2nPY3xlQ0tk2/fA hGcOshTLElrtf2ROFG4TETqKEmE0Iw1tTrX9La6tiCtWj7/dZ4SI7uW5I4PjLqHZX4Os q9SRqNPhbZJ6rSABULVMVW1IsIVy9NlCnZu2oiW4s3IKSaN5N2O+ZzWyeBIH/b8XglEL rPtYMZbW1AOK+IrgdvU+OSjYJ3Mma2o5vKWX0bwVzll1Qh/EcKamo+uTn6V85Ksy+OWX scMUrFQ2eQzOyOkDrGpMkXZQ+lcdd5G3PcdmwgXglbp5Aw0wIkpCBaPM3JLsa9IsHUz/ RzOA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=5DpeVs9TkDJaOe8s+Rl3wA5/YjynCLr1i8OmuVqzfJ4=; b=fhg0KTNMm0Bf1YeL47aZqgYl/Yr/YHOf4Af8oZJHPz9TRggWs/ZKx+V4yZzF0wqzof 157dw/DhvCv8/JgRnejYau2Mgjxeum8o1Y0W4XmBzSeoGUe8zFQTE7aeMzfQ4w5K1Eqm HUwyrBVSaeSSBrhgZp2Zto528mnXs1n98t4K1NxVD6iFYGvU/b2JPvM5irZ/1RNUXeH5 iZWErjQrWMcMCpfqSsyZaJI22ulgMxdSKlxlA9PIOfi9U30oykAFvFFxYKsXoWs3Zf3B E/bmFO+TnaOgZn/3qyJhx2v8/FDXebZWGZh9EFhNiMyMZBB+sgCT0BhtHghuikLlM/J4 WZDw==
X-Gm-Message-State: AOPr4FVkfZgWMz9tiQwcblg3foVTyCW8aVzkuejSDX7Vm0f/GvMK3az7A2iGfRKwtmgNpw==
X-Received: by 10.66.229.33 with SMTP id sn1mr24143780pac.49.1461001108334; Mon, 18 Apr 2016 10:38:28 -0700 (PDT)
Received: from Melindas-MacBook-Pro.local (216-67-27-17-radius.dynamic.acsalaska.net. [216.67.27.17]) by smtp.googlemail.com with ESMTPSA id ff2sm61539387pac.15.2016.04.18.10.38.27 for <ietf@ietf.org> (version=TLSv1/SSLv3 cipher=OTHER); Mon, 18 Apr 2016 10:38:27 -0700 (PDT)
Subject: Re: Interim step on meetings site feedback for sites currently under active consideration
To: ietf@ietf.org
References: <20160418161552.9368.65562.idtracker@ietfa.amsl.com> <8fb376e11631f9ddf73f9385ec5472c3.squirrel@www.trepanning.net>
From: Melinda Shore <melinda.shore@gmail.com>
Message-ID: <57151C55.30206@gmail.com>
Date: Mon, 18 Apr 2016 09:41:41 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:38.0) Gecko/20100101 Thunderbird/38.6.0
MIME-Version: 1.0
In-Reply-To: <8fb376e11631f9ddf73f9385ec5472c3.squirrel@www.trepanning.net>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/d2wfCddjTKgyAFZC3XCLYvI3VFc>
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: Mon, 18 Apr 2016 17:38:38 -0000

On 4/18/16 9:09 AM, Dan Harkins wrote:
>But
> I think these issues should be balanced with the overall benefit
> that the IETF World Tour provides.

As I've said repeatedly, I don't think the world tour actually
does bring much benefit.  I'm very hopeful that some of the
South Americans who attended their first IETF meeting because
it was held in Buenos Aires will continue to participate (as in:
bring in work and participate in ongoing work, and not as in: sit
in meetings) but historically that has not been the case.  I also
think that the world tour tends to have the unintended side-effect
of overemphasizing the importance of meetings to our process.

Also, note that a large number of regulars opted to skip the meeting
in Buenos Aires.  Granted, there are those who might see that as
a benefit.

Melinda


From nobody Mon Apr 18 10:45:19 2016
Return-Path: <aallen@blackberry.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 C7A2912E3DC; Mon, 18 Apr 2016 10:45:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.597
X-Spam-Level: 
X-Spam-Status: No, score=-3.597 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.996, SPF_PASS=-0.001] 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 sBqvyxNJgMcz; Mon, 18 Apr 2016 10:45:14 -0700 (PDT)
Received: from smtp-p01.blackberry.com (smtp-p01.blackberry.com [208.65.78.88]) by ietfa.amsl.com (Postfix) with ESMTP id 6C82012E3D9; Mon, 18 Apr 2016 10:45:05 -0700 (PDT)
Received: from xct101cnc.rim.net ([10.65.161.201]) by mhs210cnc.rim.net with ESMTP/TLS/AES256-SHA; 18 Apr 2016 14:11:44 -0400
Received: from XMB121CNC.rim.net ([fe80::49cb:316:205b:d7d9]) by XCT101CNC.rim.net ([fe80::9c22:d9c:c906:c488%16]) with mapi id 14.03.0210.002; Mon, 18 Apr 2016 13:44:58 -0400
From: Andrew Allen <aallen@blackberry.com>
To: Dan Harkins <dharkins@lounge.org>, "venue-selection@ietf.org" <venue-selection@ietf.org>
Subject: =?utf-8?B?UkU6IEludGVyaW0gc3RlcCBvbiBtZWV0aW5ncyBzaXRlIGZlZWRiYWNrICA=?= =?utf-8?B?w6LigqzigJ0gZm9yIHNpdGVzIGN1cnJlbnRseSB1bmRlciBhY3RpdmUgY29u?= =?utf-8?Q?sideration?=
Thread-Topic: =?utf-8?B?SW50ZXJpbSBzdGVwIG9uIG1lZXRpbmdzIHNpdGUgZmVlZGJhY2sgIMOi4oKs?= =?utf-8?B?4oCdIGZvciBzaXRlcyBjdXJyZW50bHkgdW5kZXIgYWN0aXZlIGNvbnNpZGVy?= =?utf-8?Q?ation?=
Thread-Index: AQHRmZUXZalLvaOsekqhC8vL4c6/N5+P/6iQ
Date: Mon, 18 Apr 2016 17:44:57 +0000
Message-ID: <BBF5DDFE515C3946BC18D733B20DAD233A63D2A9@XMB121CNC.rim.net>
References: <20160418161552.9368.65562.idtracker@ietfa.amsl.com> <8fb376e11631f9ddf73f9385ec5472c3.squirrel@www.trepanning.net>
In-Reply-To: <8fb376e11631f9ddf73f9385ec5472c3.squirrel@www.trepanning.net>
Accept-Language: en-CA, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.65.160.247]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/mvVDn7b2ARU4mdK_aWrqHtpXmQU>
Cc: "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: Mon, 18 Apr 2016 17:45:17 -0000

SSBoYXZlIGEgKzEgZm9yIHRoZSBnZW5lcmFsIHNlbnRpbWVudCBidXQgc29tZSBkaXNhZ3JlZW1l
bnQgd2l0aCB0aGUgc3RhdGVtZW50ICJpdCdzIGEgc2hhbWUgdGhhdCBzb21lIG1lbWJlcnMgb2Yg
dGhlIElFVEYgY29tbXVuaXR5IGNhbm5vdCBicmluZyB0aGVpciBmYW1pbHkgYW5kL29yIGJlIG9w
ZW4gYW5kIGhvbmVzdCBhYm91dCB0aGVpciByZWxhdGlvbnNoaXBzIi4gVG8gbXkgdW5kZXJzdGFu
ZGluZyB0aGF0IGlzIG5vdCBjbGVhcmx5IHRoZSBjYXNlIGFuZCBuZWVkcyBzb21lIGZ1cnRoZXIg
aW52ZXN0aWdhdGlvbiB0byBkZXRlcm1pbmUgd2hhdCB0aGUgcHJlY2lzZSBsZWdhbCBzaXR1YXRp
b24gaXMgYW5kIGhvdyBpdCBhcHBsaWVzIHBhcnRpY3VsYXJseSB3aXRoIHJlZ2FyZCB0byBpbmRp
dmlkdWFscyBjb21pbmcgZnJvbSBjb3VudHJpZXMgd2hlcmUgdGhlaXIgc3RhdHVzIGlzIHBlcmZl
Y3RseSBsZWdhbC4NCg0KLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCkZyb206IGlldGYgW21h
aWx0bzppZXRmLWJvdW5jZXNAaWV0Zi5vcmddIE9uIEJlaGFsZiBPZiBEYW4gSGFya2lucw0KU2Vu
dDogTW9uZGF5LCBBcHJpbCAxOCwgMjAxNiAxOjA5IFBNDQpUbzogdmVudWUtc2VsZWN0aW9uQGll
dGYub3JnDQpDYzogaWV0ZkBpZXRmLm9yZw0KU3ViamVjdDogUmU6IEludGVyaW0gc3RlcCBvbiBt
ZWV0aW5ncyBzaXRlIGZlZWRiYWNrIMOi4oKs4oCdIGZvciBzaXRlcyBjdXJyZW50bHkgdW5kZXIg
YWN0aXZlIGNvbnNpZGVyYXRpb24NCg0KDQogIEZpcnN0IG9mZiwgT3hmb3JkIGNvbW1hLiBOZXh0
LCB3aGF0J3MgYW4gImV0aG5pY2FsIiBwZXJzb24/IEFuZCB0aGlyZCwgYXMgSSBvYnNlcnZlZCBh
dCB0aGUgcGxlbmFyeSwgYnJpbmdpbmcgaW4gYSB2ZXJ5IGRpdmVyc2Ugb3BpbmlvbiBzZXQgb24g
aW5jbHVzaXZlbmVzcyBhbmQgYWNjZXNzaWJpbGl0eSB3aWxsIG1ha2UgdXMgb25seSBtZWV0IGlu
IFdlc3Rlcm4gRXVyb3BlLCBOb3J0aCBBbWVyaWNhLCBhbmQgSmFwYW4uIEFuZCB3aGF0J3MgaW4g
dGhlIHF1ZXVlIGZvciBjb25zaWRlcmF0aW9uPyBXZXN0ZXJuIEV1cm9wZSBhbmQgTm9ydGggQW1l
cmljYS4gU2lnaC4NCg0KICBUaGVyZSBhcmUgcGxlbnR5IG9mIHJlYXNvbnMgdG8gbm90IG1lZXQg
aW4gU2luZ2Fwb3JlIGFuZCBpdCdzIGEgc2hhbWUgdGhhdCBzb21lIG1lbWJlcnMgb2YgdGhlIElF
VEYgY29tbXVuaXR5IGNhbm5vdCBicmluZyB0aGVpciBmYW1pbHkgYW5kL29yIGJlIG9wZW4gYW5k
IGhvbmVzdCBhYm91dCB0aGVpciByZWxhdGlvbnNoaXBzLiBCdXQgSSB0aGluayB0aGVzZSBpc3N1
ZXMgc2hvdWxkIGJlIGJhbGFuY2VkIHdpdGggdGhlIG92ZXJhbGwgYmVuZWZpdCB0aGF0IHRoZSBJ
RVRGIFdvcmxkIFRvdXIgcHJvdmlkZXMuIFdlIGFyZSBhIGRpdmVyc2UgZ3JvdXAgYW5kIEkgdGhp
bmsgd2UgbGVhdmUgZWFjaCBjaXR5IGEgbGl0dGxlIGJldHRlciBvZmYgYWZ0ZXIgd2UgZGVwYXJ0
IGJlY2F1c2Ugb2YgaXQuIEVtYmFyZ29lcyBzZWxkb20gaGF2ZSB0aGUgZGVzaXJlZCBlZmZlY3Qu
DQoNCiAgcmVnYXJkcywNCg0KICBEYW4uDQoNCk9uIE1vbiwgQXByaWwgMTgsIDIwMTYgOToxNSBh
bSwgVGhlIElBT0Mgd3JvdGU6DQo+IEFsbCwNCj4NCj4gVGhlIElBT0MgYW5kIGl0cyBtZWV0aW5n
cyBjb21taXR0ZWUgYXJlIGNvbnRpbnVpbmcgdG8gcmV2aWV3IHRoZSANCj4gc2l0dWF0aW9uIHdp
dGggcmVzcGVjdCB0byBtZWV0aW5nIGluIFNpbmdhcG9yZS4gIEFzIEkgbm90ZWQgYWJvdXQgYSAN
Cj4gd2VlayBhZ28gWzFdLCB3ZSBhcmUgcmV2aWV3aW5nIG91ciBtZWV0aW5nIHBsYW5uaW5nIHBy
b2NlZHVyZXMgdG8gDQo+IGVuc3VyZSB0aGF0IHdlIGhhdmUgaW5wdXQgYXQgYXBwcm9wcmlhdGUg
cG9pbnRzIHRvIGVuc3VyZSBpc3N1ZXMgYXJlIA0KPiBpZGVudGlmaWVkIGFuZCBhZGRyZXNzZWQg
YmVmb3JlIGNvbnRyYWN0cyBhcmUgc2lnbmVkIGFuZCBhbm5vdW5jZW1lbnRzIA0KPiBtYWRlLiAg
VGhpcyB3aWxsIG1lYW4gbW9yZSB0cmFuc3BhcmVuY3ksIGluY2x1ZGluZyBzaGFyaW5nIHRoZSBs
aXN0IG9mIA0KPiBjaXRpZXMgdW5kZXIgY29uc2lkZXJhdGlvbiB3aGVuIHdlIGhhdmUgYSB3b3Jr
YWJsZSB3YXkgdG8gaGFuZGxlIGFuZCANCj4gaGVhciB0aGUgZmVlZGJhY2suICBXZSB3aWxsIG1h
a2UgY29uY3JldGUgcHJvZ3Jlc3Mgb24gdGhhdCBhdCBvdXIgcmV0cmVhdCBpbiBhIGZldyB3ZWVr
cyB0aW1lLg0KPg0KPiBJbiB0aGUgbWVhbnRpbWUsIHdlIGRvIGhhdmUgYWN0aXZlIHNpdGUgZGlz
Y3Vzc2lvbnMgYW5kIG5lZ290aWF0aW9ucyANCj4gcmVhZHkgdG8gY2xvc2UgZm9yIG1lZXRpbmdz
IHRoYXQgYXJlIGNvbWluZyB1cC4gIEluIGFkZGl0aW9uIHRvIA0KPiByZWFjaGluZyBvdXQgdG8g
Z3JvdXBzIG9yIGFnZW5jaWVzIHRoYXQgaGF2ZSBzcGVjaWZpYyBrbm93bGVkZ2UgYWJvdXQgDQo+
IHRyYXZlbCBmb3IgZGl2ZXJzZSBncm91cHMgaW5jbHVkaW5nIHJlbGlnaW91cywgZXRobmljYWwg
YW5kIExHQlRRIA0KPiBwZW9wbGUsIHdlIGFyZSByZWFjaGluZyBvdXQgdG8gdGhlIElFVEYgY29t
bXVuaXR5IGFzIGEgd2hvbGUgd2l0aCB0aGlzIG5vdGUuDQo+DQo+IEluIG9yZGVyIHRvIG1ha2Ug
c3VyZSB3ZSBoYXZlbsOi4oKs4oSidCBvdmVybG9va2VkIHNvbWV0aGluZyBlbHNlIHRoYXQgDQo+
IHNob3VsZCBoYXZlIGJlZW4gcHJvcGVybHkgY29uc2lkZXJlZCBmb3Igc2l0ZXMgdW5kZXIgY29u
c2lkZXJhdGlvbiwgYXMgDQo+IHdlbGwgYXMgdG8gZ2F0aGVyIHNvbWUgcnVubmluZyBjb2RlIG9u
IGhvdyBhIGZlZWRiYWNrIHByb2Nlc3MgbWlnaHQgDQo+IHdvcmssIHdlIHdvdWxkIGxpa2UgdG8g
aGVhciBmcm9tIGFueW9uZSB3aG8gaXMgYXdhcmUgb2YgcmVhc29ucyB3ZSANCj4gY291bGQgbm90
IGhhdmUgYSBzdWNjZXNzZnVsIG1lZXRpbmcgaW4gYW55IG9mIHRoZSBmb2xsb3dpbmcgY2l0aWVz
LCBvciANCj4gb2YgYW55IGxpbWl0cyB0byBhdHRlbmRlZSBhY2Nlc3NpYmlsaXR5IG9yIGluY2x1
c2l2ZW5lc3MgdGhhdCBzaG91bGQgYmUgY29uc2lkZXJlZDoNCj4NCj4gCVBhcmlzDQo+IAlNb250
cmVhbA0KPiAJQ29wZW5oYWdlbg0KPg0KPiBQbGVhc2Ugc2VuZCB5b3VyIGlucHV0IHRvIHZlbnVl
LXNlbGVjdGlvbkBpZXRmLm9yZy4gIEl0IHdpbGwgaGVscCB0aGUgDQo+IHJldmlldyBwcm9jZXNz
IGlmIHRoZSBTdWJqZWN0IGxpbmUgaGFkIHRoZSBuYW1lIG9mIHRoZSBjaXR5IGZpcnN0LA0KPiBT
dWJqZWN0OiA8Y2l0eT4uDQo+DQo+IEluIG9yZGVyIG5vdCBtaXNzIHRoZSBjb250cmFjdCBvcHBv
cnR1bml0aWVzLCBjaXR5LXNwZWNpZmljIGlucHV0IA0KPiB3b3VsZCBiZSBtb3N0IGhlbHBmdWwg
aWYgcmVjZWl2ZWQgYnkgdGhlIGVuZCBvZiBNYXkgMiwgMjAxNi4NCj4NCj4gT3RoZXIgaW5wdXQg
b24gdGhlIHByb2Nlc3Mgd2lsbCBiZSBiZXN0IHJlY2VpdmVkIGluIGUtbWFpbCBhdCANCj4gdmVu
dWUtc2VsZWN0aW9uQGlldGYub3JnIHdpdGggdGhlIFN1YmplY3QgbGluZTogUHJvY2Vzcy4gIEFz
IHdlIA0KPiBpdGVyYXRlIHRoZSBwcm9jZXNzIHdlIHdpbGwgY29udGludWUgdG8gc2VlayBpbnB1
dCB0byBmYXNoaW9uIGEgDQo+IG1lZXRpbmcgcGxhbm5pbmcgcHJvY2VzcyB0aGF0IHdvcmtzLg0K
Pg0KPg0KPiBMZXNsaWUsDQo+IGZvciB0aGUgSUFPQy4NCj4NCj4gWzFdIA0KPiBodHRwczovL21h
aWxhcmNoaXZlLmlldGYub3JnL2FyY2gvbXNnL2lldGYvaEt3QllPd1BrRTZWVEE0bXh4ZjAwTlRM
TEYwDQo+DQo+IC0tDQo+DQo+IC0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0NCj4gTGVzbGllIERhaWdsZQ0KPiBQcmluY2lw
YWwsIFRoaW5raW5nQ2F0IEVudGVycHJpc2VzIExMQyBsZGFpZ2xlQHRoaW5raW5nY2F0LmNvbQ0K
PiAtLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tDQo+DQo+DQoNCg0K


From nobody Mon Apr 18 10:54:32 2016
Return-Path: <dhruv.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 351B612D6D9; Mon, 18 Apr 2016 10:54:30 -0700 (PDT)
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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 SaRkfRyKaVAG; Mon, 18 Apr 2016 10:54:28 -0700 (PDT)
Received: from mail-io0-x234.google.com (mail-io0-x234.google.com [IPv6:2607:f8b0:4001:c06::234]) (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 E796512E412; Mon, 18 Apr 2016 10:54:25 -0700 (PDT)
Received: by mail-io0-x234.google.com with SMTP id g185so202313557ioa.2; Mon, 18 Apr 2016 10:54:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc; bh=ryi7ZzozPzb2HzAuTVsk1QshxBDox8dMrlZf6+HuPUU=; b=x4Yr/6Lo4Dvl1PMoFg//b0/+LYuTpVX3Lme5SZevTExoIbTM5NYiMlFF18D5Kt7VSp n+n+12FgW/G4zJR1+HPiWgRcI5RGk0BRoO+1GXihZbrBRD24S1ujXo91e8JI75fViWMW HLbFvMo4rWSHHYQNIcc9tjRAiTFCiV6F3jjFVVMyikCVdI87nUo8DYA4iltxT003qIK0 /8Ft5SeDXmJSPiYSle5GZHkyLWmnxpuQJe8S7LLTicBeQ+3B2CUTeonAM0SYJYw91gei ygwjtF3ZPCQteIoJvycuezt8ZPiyWVzc7MB5puShreV6mp9hemN2+ynRuLFK03Lxw9Gk GDDA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:date :message-id:subject:from:to:cc; bh=ryi7ZzozPzb2HzAuTVsk1QshxBDox8dMrlZf6+HuPUU=; b=ktagB6So+QORGL6aqxOvvZYugejoliHk4a3n3EAZz/Uh/rDRdPs0GBShfF3EIKlQMz PjY/+WSHxQmzGX0S5v9J8n0+utXatNrhUg63swuEKhIfsfL8LWzi1YJT7d9C+pG/U1R3 Ig59G6gYiZWrE5j+NOeo+XAyi9khyA8pR81TGxjojzn5SHSwNuySeya6ZxxhXdUG9UwE feaDCwlgcjp8LqEXLHyXaRttaS9yJddJy6KhUwJmdN3debJGL2mV8hXRMNQ42xRloLX0 T1idjFi3wsGbPw3GzurWXcL9b7q8qSyXU0LpqiTJqYEXKD7ZVg6A7edf945VBFB8w5Xn zBoQ==
X-Gm-Message-State: AOPr4FVtgk/pXaOVc/Fb9eqbDC97v8rbOP+P4oDMrB8TWMOwq1LJECN9Qj8sKVOrECxXqE984vSl63LMazLO5A==
MIME-Version: 1.0
X-Received: by 10.107.10.206 with SMTP id 75mr38015336iok.155.1461002065242; Mon, 18 Apr 2016 10:54:25 -0700 (PDT)
Sender: dhruvdhody@gmail.com
X-Google-Sender-Delegation: dhruvdhody@gmail.com
Received: by 10.50.222.71 with HTTP; Mon, 18 Apr 2016 10:54:25 -0700 (PDT)
In-Reply-To: <D3393302.16A48%peter@akayla.com>
References: <D3393302.16A48%peter@akayla.com>
Date: Mon, 18 Apr 2016 23:24:25 +0530
X-Google-Sender-Auth: G739O0TRgYMAYLZqpToplkU6wHM
Message-ID: <CAB75xn41Uq-0vTYJZLKF+01peE8TJuLb1TG3tgd3bCTgW2WWBQ@mail.gmail.com>
Subject: Re: Gen-ART LC/Telechat review of draft-ietf-pce-iro-update-06
From: Dhruv Dhody <dhruv.ietf@gmail.com>
To: Peter Yee <peter@akayla.com>
Content-Type: multipart/alternative; boundary=001a113f89b41d79c10530c60dd1
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/3otR_ZGaaTViXn82gcj97oSpVQg>
Cc: General Area Review Team <gen-art@ietf.org>, draft-ietf-pce-iro-update.all@ietf.org, IETF <ietf@ietf.org>, "dhruv.dhody@huawei.com" <dhruv.dhody@huawei.com>
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: Mon, 18 Apr 2016 17:54:30 -0000

--001a113f89b41d79c10530c60dd1
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi Peter,

Thanks for the diligent review! See Inline...

On Mon, Apr 18, 2016 at 1:40 AM, Peter Yee <peter@akayla.com> wrote:

> I am the assigned Gen-ART reviewer for this draft. The General Area Revie=
w
> Team (Gen-ART) reviews all IETF documents being processed by the IESG for
> the IETF Chair. Please wait for direction from your document shepherd or
> AD before posting a new version of the draft.
>
> For more information, please see the FAQ at
> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>
> Document: draft-ietf-pce-iro-update-06
> Reviewer: Peter Yee
> Review Date: Apr-17-2016
> IETF LC End Date: Mar-29-2016
> IESG Telechat date: Apr-21-2016
>
> Summary: This draft is basically ready for publication as a Standards
> Track RFC, but has some nits that should be fixed before publication.
> [Ready with nits]
>
> This specification documents the results of a survey regarding
> implementation of the Include Route Object for PCEP and uses those result=
s
> to clarify the meaning of section 7.12 of RFC 5440 with updated text.
>
> Major issues: None
>
> Minor issues: None really
>
> Page 5, Section 4, 1st paragraph, 2nd sentence: Are you sure that
> confusing interpretation of the IRO ordering or the L bit doesn=E2=80=99t=
 cause
> any security issues?  I=E2=80=99m not PCEP savvy enough to know if mistak=
enly
> sending information that should have gone strictly through a loose node
> would disclose anything that the originator didn=E2=80=99t really wish an=
y nodes
> outside of the strict list to see.
>
>
=E2=80=8B[Dhruv]: My first instinct is to say that this isn't an issue, as =
PCEP
speaker are expected to know about the nodes (via TED) irrespective of
strict and loose interpretation of that node. I will discuss this again
with the our shepherd.
=E2=80=8B


>
> Nits:
>
> Page 3, first full paragraph: insert =E2=80=9Can=E2=80=9D before =E2=80=
=9CIRO=E2=80=9D.
>
> Page 3, Section 2 title: insert =E2=80=9Cthe=E2=80=9D before =E2=80=9CIRO=
=E2=80=9D.
>
> Page 3, Section 2, 3rd paragraph, 2nd sentence: insert =E2=80=9Cthem=E2=
=80=9D before the
> second =E2=80=9Cas=E2=80=9D.
>
> Page 4, Section 2, 1st paragraph: append a colon to the end of the
> paragraph.
>
> Page 4, Section 2, indented bullet item: remove the hyphen and put the
> remainder between double quotes, not single quotes.
>
> Page 4, Section 2, 1st major bullet item, 1st sentence: insert =E2=80=9Ca=
n=E2=80=9D before
> =E2=80=9CIRO=E2=80=9D.
>
> Page 4, Section 2, 1st major bullet item, 2nd sentence: change
> =E2=80=9Ccomprising=E2=80=9D to =E2=80=9Ccomprised=E2=80=9D.  Insert =E2=
=80=9Cto=E2=80=9D before =E2=80=9Csection=E2=80=9D.
>
> Page 4, Section 2, 2nd major bullet item, 1st sentence: insert =E2=80=9Ca=
n=E2=80=9D before
> =E2=80=9CIRO=E2=80=9D.  Change the comma to a semicolon.
>
> Page 4, Section 2, 2nd major bullet item, 3rd sentence: insert =E2=80=9Ct=
he=E2=80=9D
> before =E2=80=9CLoose=E2=80=9D.
>
> Page 4, Section 3, 2nd paragraph, 1st sentence: delete comma.
>
> Page 4, Section 3, 2nd paragraph, 2nd sentence: change trailing space and
> hyphen to a colon.
>
> Page 4, Section 3, 1st bullet item: delete comma after =E2=80=9CIRO=E2=80=
=9D.  Insert
> =E2=80=9Cthe=E2=80=9D before the last =E2=80=9CIRO=E2=80=9D.
>
> Page 5, Section 3, 1st paragraph: insert =E2=80=9Cthe=E2=80=9D before =E2=
=80=9CIRO=E2=80=9D.
>
> Page 5, Section 4, 1st paragraph, 1st sentence: insert =E2=80=9Cthe=E2=80=
=9D before =E2=80=9CIRO=E2=80=9D.
>
>
>
> =E2=80=8B[Dhruv]: Thanks! Will Update!

Regards,
Dhruv=E2=80=8B

--001a113f89b41d79c10530c60dd1
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-family:trebuche=
t ms,sans-serif;color:#4c1130">Hi Peter,=C2=A0</div><div class=3D"gmail_def=
ault" style=3D"font-family:trebuchet ms,sans-serif;color:#4c1130"><br></div=
><div class=3D"gmail_default" style=3D"font-family:trebuchet ms,sans-serif;=
color:#4c1130">Thanks for the diligent review! See Inline...</div><div clas=
s=3D"gmail_default" style=3D"font-family:trebuchet ms,sans-serif;color:#4c1=
130"><br></div><div class=3D"gmail_extra"><div class=3D"gmail_quote">On Mon=
, Apr 18, 2016 at 1:40 AM, Peter Yee <span dir=3D"ltr">&lt;<a href=3D"mailt=
o:peter@akayla.com" target=3D"_blank">peter@akayla.com</a>&gt;</span> wrote=
:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-le=
ft:1px #ccc solid;padding-left:1ex">I am the assigned Gen-ART reviewer for =
this draft. The General Area Review<br>
Team (Gen-ART) reviews all IETF documents being processed by the IESG for<b=
r>
the IETF Chair. Please wait for direction from your document shepherd or<br=
>
AD before posting a new version of the draft.<br>
<br>
For more information, please see the FAQ at<br>
&lt;<a href=3D"http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq" rel=
=3D"noreferrer" target=3D"_blank">http://wiki.tools.ietf.org/area/gen/trac/=
wiki/GenArtfaq</a>&gt;.<br>
<br>
Document: draft-ietf-pce-iro-update-06<br>
Reviewer: Peter Yee<br>
Review Date: Apr-17-2016<br>
IETF LC End Date: Mar-29-2016<br>
IESG Telechat date: Apr-21-2016<br>
<br>
Summary: This draft is basically ready for publication as a Standards<br>
Track RFC, but has some nits that should be fixed before publication.<br>
[Ready with nits]<br>
<br>
This specification documents the results of a survey regarding<br>
implementation of the Include Route Object for PCEP and uses those results<=
br>
to clarify the meaning of section 7.12 of RFC 5440 with updated text.<br>
<br>
Major issues: None<br>
<br>
Minor issues: None really<br>
<br>
Page 5, Section 4, 1st paragraph, 2nd sentence: Are you sure that<br>
confusing interpretation of the IRO ordering or the L bit doesn=E2=80=99t c=
ause<br>
any security issues?=C2=A0 I=E2=80=99m not PCEP savvy enough to know if mis=
takenly<br>
sending information that should have gone strictly through a loose node<br>
would disclose anything that the originator didn=E2=80=99t really wish any =
nodes<br>
outside of the strict list to see.<br>
<br></blockquote><div><br></div><div><div class=3D"gmail_default" style=3D"=
font-family:&quot;trebuchet ms&quot;,sans-serif;color:rgb(76,17,48);display=
:inline">=E2=80=8B[Dhruv]: My first instinct is to say that this isn&#39;t =
an issue, as PCEP speaker are expected to know about the nodes (via TED) ir=
respective of strict and loose interpretation of that node. I will discuss =
this again with the our shepherd. =C2=A0</div></div><div><div class=3D"gmai=
l_default" style=3D"font-family:&quot;trebuchet ms&quot;,sans-serif;color:r=
gb(76,17,48);display:inline">=E2=80=8B</div>=C2=A0</div><blockquote class=
=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padd=
ing-left:1ex">
<br>
Nits:<br>
<br>
Page 3, first full paragraph: insert =E2=80=9Can=E2=80=9D before =E2=80=9CI=
RO=E2=80=9D.<br>
<br>
Page 3, Section 2 title: insert =E2=80=9Cthe=E2=80=9D before =E2=80=9CIRO=
=E2=80=9D.<br>
<br>
Page 3, Section 2, 3rd paragraph, 2nd sentence: insert =E2=80=9Cthem=E2=80=
=9D before the<br>
second =E2=80=9Cas=E2=80=9D.<br>
<br>
Page 4, Section 2, 1st paragraph: append a colon to the end of the<br>
paragraph.<br>
<br>
Page 4, Section 2, indented bullet item: remove the hyphen and put the<br>
remainder between double quotes, not single quotes.<br>
<br>
Page 4, Section 2, 1st major bullet item, 1st sentence: insert =E2=80=9Can=
=E2=80=9D before<br>
=E2=80=9CIRO=E2=80=9D.<br>
<br>
Page 4, Section 2, 1st major bullet item, 2nd sentence: change<br>
=E2=80=9Ccomprising=E2=80=9D to =E2=80=9Ccomprised=E2=80=9D.=C2=A0 Insert =
=E2=80=9Cto=E2=80=9D before =E2=80=9Csection=E2=80=9D.<br>
<br>
Page 4, Section 2, 2nd major bullet item, 1st sentence: insert =E2=80=9Can=
=E2=80=9D before<br>
=E2=80=9CIRO=E2=80=9D.=C2=A0 Change the comma to a semicolon.<br>
<br>
Page 4, Section 2, 2nd major bullet item, 3rd sentence: insert =E2=80=9Cthe=
=E2=80=9D<br>
before =E2=80=9CLoose=E2=80=9D.<br>
<br>
Page 4, Section 3, 2nd paragraph, 1st sentence: delete comma.<br>
<br>
Page 4, Section 3, 2nd paragraph, 2nd sentence: change trailing space and<b=
r>
hyphen to a colon.<br>
<br>
Page 4, Section 3, 1st bullet item: delete comma after =E2=80=9CIRO=E2=80=
=9D.=C2=A0 Insert<br>
=E2=80=9Cthe=E2=80=9D before the last =E2=80=9CIRO=E2=80=9D.<br>
<br>
Page 5, Section 3, 1st paragraph: insert =E2=80=9Cthe=E2=80=9D before =E2=
=80=9CIRO=E2=80=9D.<br>
<br>
Page 5, Section 4, 1st paragraph, 1st sentence: insert =E2=80=9Cthe=E2=80=
=9D before =E2=80=9CIRO=E2=80=9D.<br>
<br>
<br>
<br></blockquote><div><div class=3D"gmail_default" style=3D"font-family:&qu=
ot;trebuchet ms&quot;,sans-serif;color:rgb(76,17,48);display:inline">=E2=80=
=8B[Dhruv]: Thanks! Will Update!=C2=A0</div></div><div><div class=3D"gmail_=
default" style=3D"font-family:&quot;trebuchet ms&quot;,sans-serif;color:rgb=
(76,17,48);display:inline"><br></div></div><div><div class=3D"gmail_default=
" style=3D"font-family:&quot;trebuchet ms&quot;,sans-serif;color:rgb(76,17,=
48);display:inline">Regards,</div></div><div><div class=3D"gmail_default" s=
tyle=3D"font-family:&quot;trebuchet ms&quot;,sans-serif;color:rgb(76,17,48)=
;display:inline">Dhruv=E2=80=8B</div>=C2=A0</div></div><br></div></div>

--001a113f89b41d79c10530c60dd1--


From nobody Mon Apr 18 11:53:49 2016
Return-Path: <dharkins@lounge.org>
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 533A012D80B for <ietf@ietfa.amsl.com>; Mon, 18 Apr 2016 11:53:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_PASS=-0.001] 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 PQK7DDUmYzY6 for <ietf@ietfa.amsl.com>; Mon, 18 Apr 2016 11:53:45 -0700 (PDT)
Received: from colo.trepanning.net (colo.trepanning.net [69.55.226.174]) by ietfa.amsl.com (Postfix) with ESMTP id CD38512D0E7 for <ietf@ietf.org>; Mon, 18 Apr 2016 11:53:45 -0700 (PDT)
Received: from www.trepanning.net (localhost [127.0.0.1]) by colo.trepanning.net (Postfix) with ESMTP id C998510224008; Mon, 18 Apr 2016 11:53:44 -0700 (PDT)
Received: from 69.12.173.8 (SquirrelMail authenticated user dharkins@lounge.org) by www.trepanning.net with HTTP; Mon, 18 Apr 2016 11:53:45 -0700 (PDT)
Message-ID: <7c39e37d84d42b48e493be2217ba3c76.squirrel@www.trepanning.net>
In-Reply-To: <57151C55.30206@gmail.com>
References: <20160418161552.9368.65562.idtracker@ietfa.amsl.com> <8fb376e11631f9ddf73f9385ec5472c3.squirrel@www.trepanning.net> <57151C55.30206@gmail.com>
Date: Mon, 18 Apr 2016 11:53:45 -0700 (PDT)
Subject: Re: Interim step on meetings site feedback for sites currently  under active consideration
From: "Dan Harkins" <dharkins@lounge.org>
To: "Melinda Shore" <melinda.shore@gmail.com>
User-Agent: SquirrelMail/1.4.14 [SVN]
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/rYv3GV5xRNGFqYpOr6d8NcGgM48>
Cc: 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: Mon, 18 Apr 2016 18:53:47 -0000

On Mon, April 18, 2016 10:41 am, Melinda Shore wrote:
> On 4/18/16 9:09 AM, Dan Harkins wrote:
>>But
>> I think these issues should be balanced with the overall benefit
>> that the IETF World Tour provides.
>
> As I've said repeatedly, I don't think the world tour actually
> does bring much benefit.  I'm very hopeful that some of the
> South Americans who attended their first IETF meeting because
> it was held in Buenos Aires will continue to participate (as in:
> bring in work and participate in ongoing work, and not as in: sit
> in meetings) but historically that has not been the case.  I also
> think that the world tour tends to have the unintended side-effect
> of overemphasizing the importance of meetings to our process.

  Perhaps, but the idea that bringing one's family along for a
vacation should have any bearing on venue selection seems to
distort the whole reason we have meetings in the first place.

  Let's not go to places that throw gay people off of tall buildings,
and chops the heads of atheists off. Singapore, for all its faults
and petty totalitarianism, is not that place. On the other hand,
if we're gonna go full Social Justice Warrior, let's not go to
Copenhagen because the Danes take all the money and jewelry of
refugees fleeing war and oppression that try to resetting in Denmark.

  Dan.



From nobody Mon Apr 18 11:57:56 2016
Return-Path: <gorry@erg.abdn.ac.uk>
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 8551F12E5A7; Mon, 18 Apr 2016 11:57:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.896
X-Spam-Level: 
X-Spam-Status: No, score=-2.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.996] 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 KIUF471tE0K2; Mon, 18 Apr 2016 11:57:49 -0700 (PDT)
Received: from pegasus.erg.abdn.ac.uk (pegasus.erg.abdn.ac.uk [IPv6:2001:630:241:204::f0f0]) by ietfa.amsl.com (Postfix) with ESMTP id EC61012E5A4; Mon, 18 Apr 2016 11:57:48 -0700 (PDT)
Received: from erg.abdn.ac.uk (galactica.erg.abdn.ac.uk [139.133.210.32]) by pegasus.erg.abdn.ac.uk (Postfix) with ESMTPA id C68F31B00055; Mon, 18 Apr 2016 20:09:55 +0100 (BST)
Received: from 212.159.18.54 (SquirrelMail authenticated user gorry) by erg.abdn.ac.uk with HTTP; Mon, 18 Apr 2016 19:57:47 +0100
Message-ID: <f956489e391d767784e6c8ab7479d0e3.squirrel@erg.abdn.ac.uk>
In-Reply-To: <CE03DB3D7B45C245BCA0D243277949362E96B03B@MX104CL02.corp.emc.com>
References: <20160321174750.31944.71903.idtracker@ietfa.amsl.com> <56F26AD3.3010403@ericsson.com> <5BB71158-3530-47A2-9A33-811F65B2F677@iii.ca> <56FBBBC1.5060902@ericsson.com> <CE03DB3D7B45C245BCA0D243277949362E92B245@MX104CL02.corp.emc.com> <D12A5B0E-EF12-4BC8-999B-6ED50029C95A@iii.ca> <CE03DB3D7B45C245BCA0D243277949362E96B03B@MX104CL02.corp.emc.com>
Date: Mon, 18 Apr 2016 19:57:47 +0100
Subject: Re: [tsvwg] Last Call: <draft-ietf-tsvwg-rtcweb-qos-15.txt> (DSCP and other packet markings for WebRTC QoS) to Proposed Standard
From: gorry@erg.abdn.ac.uk
To: "Black, David" <david.black@emc.com>
User-Agent: SquirrelMail/1.4.23 [SVN]
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/d7jiGOhXH7FGiOf5lRiStvtoumM>
Cc: Magnus Westerlund <magnus.westerlund@ericsson.com>, "draft-ietf-tsvwg-rtcweb-qos@ietf.org" <draft-ietf-tsvwg-rtcweb-qos@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "tsvwg-chairs@ietf.org" <tsvwg-chairs@ietf.org>, Cullen Jennings <fluffy@iii.ca>, "tsvwg@ietf.org" <tsvwg@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: Mon, 18 Apr 2016 18:57:52 -0000

Looks good to me, but I'd prefer /as/because/

Gorry

> So, summarizing Magnus's concerns with proposals:
>
>> > [1] Flow Type in application-facing browser API:
>
>> > Propose an additional sentence:
>> > OLD
>> >   o  Flow Type: The browser provides this input as it knows if the
>> flow
>> >      is audio, interactive video with or without audio,
>> non-interactive
>> >      video with or without audio, or data.
>> > NEW
>> >   o  Flow Type: The browser provides this input as it knows if the
>> flow
>> >      is audio, interactive video with or without audio,
>> non-interactive
>> >      video with or without audio, or data.  For audio that is
>> associated
>> >      with a video flow, the flow type of the associated video MAY
>> >      be used instead of the associated audio type.
>
> Magnus - does that new text suffice?
>
>> > [2] What does "interactive" mean in an implementation?:
>>
>> We could add something along lines of ..... Currently in WebRTC, media
>> sent over
>> RTP is assumed to be interactive while media streamed over HTTP is
>> assumed not
>> to be. Future WebRTC extensions could allow streamed media over RTP.
>
> I believe the proposed additional sentence addresses the question of how a
> browser
> determines whether a video flow is interactive.  This proposed sentence
> will need to
> cite a WebRTC document that contains a statement to that effect, as I
> don't think this
> draft is the right place to be the primary reference for that statement.
>
> Magnus - would this approach be ok?
>
> Thanks, --David
>
>> -----Original Message-----
>> From: Cullen Jennings [mailto:fluffy@iii.ca]
>> Sent: Friday, April 15, 2016 10:48 AM
>> To: Black, David
>> Cc: Magnus Westerlund; ietf@ietf.org; tsvwg-chairs@ietf.org;
>> draft-ietf-tsvwg-
>> rtcweb-qos@ietf.org; tsvwg@ietf.org
>> Subject: Re: [tsvwg] Last Call: <draft-ietf-tsvwg-rtcweb-qos-15.txt>
>> (DSCP and
>> other packet markings for WebRTC QoS) to Proposed Standard
>>
>>
>> > On Apr 3, 2016, at 3:37 PM, Black, David <david.black@emc.com> wrote:
>> >
>> > I see a couple of Magnus's points that appear to need additional text
>> > in the draft:
>> >
>> > [1] Flow Type in application-facing browser API:
>> >
>> >>>>>> o Flow Type: The browser provides this input as it knows if
>> >>>>>> the flow is audio, interactive video with or without audio,
>> >>>>>> non-interactive video with or without audio, or data.
>> >
>> > [... snip ...]
>> >
>> >> The main issue here is that to me it was not clear that "Interactive
>> >> Video with or without audio" allows for setting these DSCP values
>> also
>> >> for the RTP stream containing audio also. This, I do see a need for
>> >> clarification on.
>> >
>> > Propose an additional sentence:
>> > OLD
>> >   o  Flow Type: The browser provides this input as it knows if the
>> flow
>> >      is audio, interactive video with or without audio,
>> non-interactive
>> >      video with or without audio, or data.
>> > NEW
>> >   o  Flow Type: The browser provides this input as it knows if the
>> flow
>> >      is audio, interactive video with or without audio,
>> non-interactive
>> >      video with or without audio, or data.  For audio that is
>> associated
>> >      with a video flow, the flow type of the associated video MAY
>> >      be used instead of the associated audio type.
>> >
>> > I hesitate to say anything stronger than "MAY" here.
>>
>> Looks good.
>>
>> >
>> > [2] What does "interactive" mean in an implementation?:
>>
>> We could add something along lines of ..... Currently in WebRTC, media
>> sent over
>> RTP is assumed to be interactive while media streamed over HTTP is
>> assumed not
>> to be. Future WebRTC extensions could allow streamed media over RTP.
>>
>>
>> >
>> >> The issue is that this document is called: DSCP and other packet
>> >> markings for WebRTC QoS. Then this document define something that is
>> not
>> >> immediately mappable onto what is being defined in the other WebRTC
>> >> specifications. That is why I am raising that there need to be more
>> >> clear coupling. If that coupling is to mostly happen in another
>> >> document, can we at least then have a proposal on the table for that
>> >> change to ensure that the result is understandable.
>> >
>> > Well, this TSVWG draft is definitely not the right place for a
>> discussion of
>> > when a video flow is interactive or non-interactive - I hope we can
>> agree
>> > on that.
>> >
>> > Beyond that, as Cullen (Jennings) is both an author of this document
>> and
>> > one of the chairs of the rtcweb WG, I'd suggest that he and/or the
>> rtcweb
>> > WG propose an appropriate location for discussion of when a video flow
>> > is interactive or non-interactive.  This TSVWG draft would then have
>> an
>> > additional sentence added, e.g.,
>> >
>> > 	See [TBD] for further discussion of how to determine
>> > 	whether a video flow is interactive vs. non-interactive.
>> >
>> > I believe that the added reference here ([TBD] above) would be
>> normative.
>> >
>> > Cullen?
>>
>> That discussion happened long ago for WebRTC and we decided we did not
>> need
>> a JavaScript controls point in the WebRTC API to indicate if RTP was
>> interactive or
>> not. If people start doing streaming video over RTP we can come back and
>> revisit
>> this and trivially add an API to indicate that in the W3C WebRTC API.
>> Part of what
>> drove this decision is the likes of Netflix / ITunes / Youtube are not
>> asking the
>> browser vendors for streaming media over RTSP or RTP. They think HTTP
>> works
>> much better for this. Thus the browser vendors see no need for non
>> interactive
>> video over RTP. I agree with Magnus that this might change some day in
>> the
>> future but right now, I think it's close enough that everyone can live
>> with it.
>>
>> I'm not OK in treating it like some open issue that is still in
>> discussion that
>> somehow holds up this spec - it's not.
>>
>> >
>> > Thanks, --David (as document  shepherd)
>> >
>



From nobody Mon Apr 18 12:05:04 2016
Return-Path: <ldaigle@thinkingcat.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 DC1F812E5C1 for <ietf@ietfa.amsl.com>; Mon, 18 Apr 2016 12:05:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.491
X-Spam-Level: 
X-Spam-Status: No, score=-2.491 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001, T_DKIM_INVALID=0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=neutral reason="invalid (public key: not available)" header.d=thinkingcat.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 a4BRyPiNoF8D for <ietf@ietfa.amsl.com>; Mon, 18 Apr 2016 12:04:59 -0700 (PDT)
Received: from homiemail-a112.g.dreamhost.com (sub4.mail.dreamhost.com [69.163.253.135]) (using TLSv1.1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D7EE112E5BC for <ietf@ietf.org>; Mon, 18 Apr 2016 12:04:58 -0700 (PDT)
Received: from homiemail-a112.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a112.g.dreamhost.com (Postfix) with ESMTP id 19CEB2004EE1D; Mon, 18 Apr 2016 12:04:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=thinkingcat.com; h=from:to :subject:date:message-id:mime-version:content-type :content-transfer-encoding; s=thinkingcat.com; bh=2CFVTokj+u8WAN f8erG0AHKlwg4=; b=AU5DzD/VH6zcQOIZbiVZsrX3FJBuuMDoxppHvsrJAhdIfB gFKkDeuJjFAVxTjsYmCph2lfEG4/qPYmeOX6J0NOwp1p5I8iYBOe3WC8IugcdoN/ 77qgPr8dU/7qAE1v5SH+JOJ864AczkI6KlGNfzdqup3t9FgDQlaQQo7Zx4l40=
Received: from [192.168.1.5] (pool-72-86-47-69.clppva.fios.verizon.net [72.86.47.69]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: leslie@oceanpurl.net) by homiemail-a112.g.dreamhost.com (Postfix) with ESMTPSA id 960BF2004C42C; Mon, 18 Apr 2016 12:04:51 -0700 (PDT)
From: "Leslie Daigle" <ldaigle@thinkingcat.com>
To: ietf@ietf.org
Subject: A word about mailing lists Re: Interim step on meetings site feedback =?utf-8?q?=E2=80=94?= for sites currently under active consideration
Date: Mon, 18 Apr 2016 15:04:39 -0400
Message-ID: <BC1E4FDD-B320-4FB1-BB89-4C3617D1F869@thinkingcat.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
X-Mailer: MailMate (1.9.4r5234)
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/uCJf5HNUS3IJB4Oyfeh-wgiRMPw>
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: Mon, 18 Apr 2016 19:05:02 -0000

FYI =E2=80=94 venue-selection@ietf.org is publicly archived, at least unt=
il it=20
becomes clear why it shouldn=E2=80=99t be :^) .

It is, however, not a discussion list:  it=E2=80=99s intended to be a=20
recipient of information from people who wish to provide input.

Luckily, if you do want to discuss, there is a discussion list!  Started=20
for the BoF of the same name, general discussions around the=20
requirements for meeting venues are being undertaken at=20
mtgvenue@ietf.org  =E2=80=94 see =20
https://www.ietf.org/mailman/listinfo/mtgvenue .

Leslie.

--=20

-------------------------------------------------------------------
Leslie Daigle
Principal, ThinkingCat Enterprises LLC
ldaigle@thinkingcat.com
-------------------------------------------------------------------
On 18 Apr 2016, at 12:15, The IAOC wrote:

> All,
>
> The IAOC and its meetings committee are continuing to review the=20
> situation with respect to meeting in Singapore.  As I noted about a=20
> week ago [1],  we are reviewing our meeting planning procedures to=20
> ensure that we have input at appropriate points to ensure issues are=20
> identified and addressed before contracts are signed and announcements=20
> made.  This will mean more transparency, including sharing the list of=20
> cities under consideration when we have a workable way to handle and=20
> hear the feedback.  We will make concrete progress on that at our=20
> retreat in a few weeks time.
>
> In the meantime, we do have active site discussions and negotiations=20
> ready to close for meetings that are coming up.  In addition to=20
> reaching out to groups or agencies that have specific knowledge about=20
> travel for diverse groups including religious, ethnical and LGBTQ=20
> people, we are reaching out to the IETF community as a whole with this=20
> note.
>
> In order to make sure we haven=E2=80=99t overlooked something else that=
=20
> should have been properly considered for sites under consideration, as=20
> well as to gather some running code on how a feedback process might=20
> work, we would like to hear from anyone who is aware of reasons we=20
> could not have a successful meeting in any of the following cities, or=20
> of any limits to attendee accessibility or inclusiveness that should=20
> be considered:
>
> 	Paris
> 	Montreal
> 	Copenhagen
>
> Please send your input to venue-selection@ietf.org.  It will help the=20
> review process if the Subject line had the name of the city first,=20
> Subject: <city>.
>
> In order not miss the contract opportunities, city-specific input=20
> would be most helpful if received by the end of May 2, 2016.
>
> Other input on the process will be best received in e-mail at=20
> venue-selection@ietf.org with the Subject line: Process.  As we=20
> iterate the process we will continue to seek input to fashion a=20
> meeting planning process that works.
>
>
> Leslie,
> for the IAOC.
>
> [1]=20
> https://mailarchive.ietf.org/arch/msg/ietf/hKwBYOwPkE6VTA4mxxf00NTLLF0
>
> --=20
>
> -------------------------------------------------------------------
> Leslie Daigle
> Principal, ThinkingCat Enterprises LLC
> ldaigle@thinkingcat.com
> -------------------------------------------------------------------


From nobody Mon Apr 18 12:39:14 2016
Return-Path: <housley@vigilsec.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 23B7C12DAE1; Mon, 18 Apr 2016 12:39:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.9
X-Spam-Level: 
X-Spam-Status: No, score=-101.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 kePOVvubPnOz; Mon, 18 Apr 2016 12:39:10 -0700 (PDT)
Received: from odin.smetech.net (x-bolt-wan.smeinc.net [209.135.219.146]) by ietfa.amsl.com (Postfix) with ESMTP id 4453F12D615; Mon, 18 Apr 2016 12:39:10 -0700 (PDT)
Received: from localhost (ronin.smetech.net [209.135.209.5]) by odin.smetech.net (Postfix) with ESMTP id 9B465F2404B; Mon, 18 Apr 2016 15:39:09 -0400 (EDT)
X-Virus-Scanned: amavisd-new at smetech.net
Received: from odin.smetech.net ([209.135.209.4]) by localhost (ronin.smeinc.net [209.135.209.5]) (amavisd-new, port 10024) with ESMTP id OOX9o7yqYHVl; Mon, 18 Apr 2016 15:23:38 -0400 (EDT)
Received: from [192.168.2.100] (pool-108-51-128-219.washdc.fios.verizon.net [108.51.128.219]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id D5740F2401F; Mon, 18 Apr 2016 15:38:57 -0400 (EDT)
From: Russ Housley <housley@vigilsec.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Subject: Gen-ART review ofdraft-ietf-rtcweb-alpn-03
Date: Mon, 18 Apr 2016 15:35:57 -0400
Message-Id: <D8017772-5403-4C20-B69A-D6BB841A26E2@vigilsec.com>
To: draft-ietf-rtcweb-alpn.all@ietf.org
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/IsuuWpK7SG8k34BEzUQGT22Z99M>
Cc: IETF Gen-ART <gen-art@ietf.org>, IETF <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: Mon, 18 Apr 2016 19:39:12 -0000

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair. Please wait for direction from your
document shepherd or AD before posting a new version of the draft.

For more information, please see the FAQ at
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Document: draft-ietf-rtcweb-alpn-03
Reviewer: Russ Housley
Review Date: 2016-04-18
IETF LC End Date: 2016-04-21
IESG Telechat date: unknown

Summary:  Almost Ready

Major Concerns:  None


Minor Concerns:

In several places, the document says: "These confidentiality protections
do not apply to data that is sent using data channels."  It took me a
moment to figure out what was being said.  I think it would really help
the reader to say at the beginning something like: "The confidentiality
protections ensure that media is protected from other applications, but
the confidentiality protections do not extend to traffic on the data
channels."

Section 3 includes this paragraph:

   Generally speaking, ensuring confidentiality depends on
   authenticating the communications peer.  This mechanism explicitly
   does not define a specific authentication method; a WebRTC endpoint
   that accepts a session with this ALPN identifier MUST respect
   confidentiality no matter what identity is attributed to a peer.

I understand why authentication and confidentiality are often used
together.  However, it is very unclear to me why there ought to be a
linkage between c-webrtc and authentication since this service really
is only a promise to not share media with other applications.

A similar discussion in the security considerations talks about
assurance that the "media was delivered to the user that was
authenticated."  Again, if there is no authentication, I do not see
how the assurance associated with this mechanism changes.


Nits:

After reading the whole document, I went back and read the Abstract
again.  I do not think it captures the real intent of the document.
I have tried to provide an alternative, but it probably needs further
work:

   This document specifies two Application Layer Protocol Negotiation
   (ALPN) labels for use with Datagram Transport Layer Security (DTLS)
   and Web Real-Time Communications (WebRTC).  With the first label, a
   DTLS session is used to establish keys for Secure Real-time Transport
   Protocol (SRTP), known as DTLS-SRTP.  The second label also uses
   DTLS-SRTP, but the peers also agree to maintain the confidentiality
   of the media by not sharing it with other applications.


From nobody Mon Apr 18 12:40:10 2016
Return-Path: <johnl@taugh.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 03B4712E67B for <ietf@ietfa.amsl.com>; Mon, 18 Apr 2016 12:40:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] 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 bHu-QpdtX0e2 for <ietf@ietfa.amsl.com>; Mon, 18 Apr 2016 12:40:07 -0700 (PDT)
Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9835012E67A for <ietf@ietf.org>; Mon, 18 Apr 2016 12:40:07 -0700 (PDT)
Received: (qmail 6202 invoked from network); 18 Apr 2016 19:40:06 -0000
Received: from unknown (64.57.183.18) by mail1.iecc.com with QMQP; 18 Apr 2016 19:40:06 -0000
Date: 18 Apr 2016 19:39:44 -0000
Message-ID: <20160418193944.9357.qmail@ary.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: Interim step on meetings site feedback for sites currently under active consideration
In-Reply-To: <57151C55.30206@gmail.com>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/pH_S4aGeR7huGkTb2BDgRtVZt8w>
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: Mon, 18 Apr 2016 19:40:09 -0000

>As I've said repeatedly, I don't think the world tour actually
>does bring much benefit.  I'm very hopeful that some of the
>South Americans who attended their first IETF meeting because
>it was held in Buenos Aires will continue to participate (as in:
>bring in work and participate in ongoing work, and not as in: sit
>in meetings) but historically that has not been the case.

I was surprised both at how well the BA meeting went, and the
number of new people from the region.  But as you say, the
proof will be if they join the mailing lists and write
drafts.

R's,
John


From nobody Mon Apr 18 12:50:36 2016
Return-Path: <nalini.elkins@insidethestack.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 53B2C12E6AA for <ietf@ietfa.amsl.com>; Mon, 18 Apr 2016 12:50:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.619
X-Spam-Level: 
X-Spam-Status: No, score=-2.619 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=yahoo.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 LCtE8eWClzpr for <ietf@ietfa.amsl.com>; Mon, 18 Apr 2016 12:50:34 -0700 (PDT)
Received: from nm12-vm4.bullet.mail.ne1.yahoo.com (nm12-vm4.bullet.mail.ne1.yahoo.com [98.138.91.172]) (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 404CF12E6A3 for <ietf@ietf.org>; Mon, 18 Apr 2016 12:50:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1461009033; bh=NDkohFaD65ue5F8vVLhFXtfqhVbWHJBxpPwyDPqVIMM=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:From:Subject; b=Zk1L0f8H7B9Q7Df5f/i+Aoix0IFVI2N3aa95NweYFdqzuNnTIbbFIuINVsxdMXDmoUjEXqSulhs97Ea+8588XJAWQ96Y6cH9rBOpeQW2yJBrstiVNbw4Ydvk3ef/87WzkBrhUymtACF9leDZrHTnursG6VRoV57zdMslFoFyRSQdu5+70+VhtCtE3mnOyINW2QzwAobWJuW8K2hA9ohdX34HglOWhzBnwaIUrYQ/pDZgRtVadq5IHbeDDJmwRwoE9YlE/j09SqujJAQrWbOBx8jfFgWteEdt9gV/mXGGMedS7L1UX49ucMgwhC7a6QWoeFNyOZ+Aah2UZ1Oil0irHw==
Received: from [98.138.100.112] by nm12.bullet.mail.ne1.yahoo.com with NNFMP;  18 Apr 2016 19:50:33 -0000
Received: from [98.138.89.248] by tm103.bullet.mail.ne1.yahoo.com with NNFMP;  18 Apr 2016 19:50:33 -0000
Received: from [127.0.0.1] by omp1040.mail.ne1.yahoo.com with NNFMP; 18 Apr 2016 19:50:33 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 488657.45482.bm@omp1040.mail.ne1.yahoo.com
X-YMail-OSG: ZmJKaggVM1mx.Jf7z8wNs9S1ZHLs_SYZxE0E9ZldqU6GnY.pnRG.fwBP9Imd2ZC ERsIl7.gIXx5jfSwFRcE8LSTvmb3zarekiIP_SDOXoKbuvdeoAc0im2LD1qdpHxeRr8vqS6orMSU NDu.hI4omPU_ErqO5QjdzqT7LlSj5EJOAxYmXfdnxDM6ld_mPFO.OWBi7UeI9xGKwSElINBpyntn 2sfz0q_dkK6fAk8611PxWmr8s.rmKyIb0XG8C7AKOfmacVNXyjR9rG3ryvjhaUBxWlElkUqj6vbQ SpIB4wO6Ev1AldbSKzySGED6uZS9CgU67SqokQMvMGyWRbH8upliNFeJnQ3WiR1KuteYQl.Q8qv1 fJd3OUfsX94aPvKq8hn9.U1v.iy6Q_LB7go10Ub6r5_nr4.KZIrPVh8BAugoqzkK5JnA15Roowbc LJMVh0Ktay8P8s_KSVB1_6fVSDG6.WOqAK4HtWB6yOK107jIih87FC9_guvGFZTELfDRYVRDMqzz nKPulGqY5psieeXLzC4fJLY6xo1799SJYC6miw6zoFrfG4.iKK8EJfA--
Received: by 98.138.101.171; Mon, 18 Apr 2016 19:50:32 +0000 
Date: Mon, 18 Apr 2016 19:50:32 +0000 (UTC)
From: <nalini.elkins@insidethestack.com>
To: Melinda Shore <melinda.shore@gmail.com>, "ietf@ietf.org" <ietf@ietf.org>,  "mtgvenue@ietf.org" <mtgvenue@ietf.org>
Message-ID: <746128222.2295531.1461009032633.JavaMail.yahoo@mail.yahoo.com>
In-Reply-To: <57151C55.30206@gmail.com>
References: <57151C55.30206@gmail.com>
Subject: Re: Interim step on meetings site feedback for sites currently under active consideration
MIME-Version: 1.0
Content-Type: multipart/alternative;  boundary="----=_Part_2295530_681012570.1461009032630"
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/oJb8sdXQwUM1BB5HN4rgQWHeJU0>
Cc: "Carlos M. Martinez" <carlos@lacnic.net>, Christian O'Flaherty <oflaherty@isoc.org>, Juliao Braga <juliao@braga.net.br>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: nalini.elkins@insidethestack.com
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: Mon, 18 Apr 2016 19:50:36 -0000

------=_Part_2295530_681012570.1461009032630
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable




>>But
>> I think these issues should be balanced with the overall benefit
>> that the IETF World Tour provides.

>As I've said repeatedly, I don't think the world tour actually
>does bring much benefit.=C2=A0 I'm very hopeful that some of the
>South Americans who attended their first IETF meeting because
>it was held in Buenos Aires will continue to participate (as in:
>bring in work and participate in ongoing work, and not as in: sit
>in meetings) but historically that has not been the case.=C2=A0
=C2=A0
Just to put some numbers into this conversation, we have 8 people from Lati=
n America who have signed up to be a part of the Internet Draft Review team=
s. =C2=A0 The first review team to form will likely be the Spanish-speaking=
 DNSOP review team.
This is one week after IETF 95 and after 3 days of soliciting review teams =
and basically zero publicity.
I wonder if there has not been more participation in active IETF work befor=
e from other regions because there was no structured way to start participa=
ting and language insensitivity. =C2=A0(BTW, there is a new member of the M=
entoring Team from Latin America, that I met in Buenos Aires who will trans=
late the Mentoring emails into Spanish.)
But the effort of the Mentoring Team is standing on the shoulders of giants=
. =C2=A0People such as Carlos Martinez, Christian O'Flaherty, Alvaro Retana=
, Dr. Juliao Braga, and many others who have done such a tremendous job of =
outreach to their community in Latin America.
So, let's do some changing of history.
Nalini



  
------=_Part_2295530_681012570.1461009032630
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<html><head></head><body><div style=3D"color:#000; background-color:#fff; f=
ont-family:HelveticaNeue-Light, Helvetica Neue Light, Helvetica Neue, Helve=
tica, Arial, Lucida Grande, sans-serif;font-size:16px"><div id=3D"yui_3_16_=
0_ym19_1_1460996044645_65196"><br></div><div class=3D"qtdSeparateBR"><br><b=
r></div><div class=3D"yahoo_quoted" id=3D"yui_3_16_0_ym19_1_1460996044645_6=
5201" style=3D"display: block;"><div style=3D"font-family: HelveticaNeue-Li=
ght, Helvetica Neue Light, Helvetica Neue, Helvetica, Arial, Lucida Grande,=
 sans-serif; font-size: 16px;" id=3D"yui_3_16_0_ym19_1_1460996044645_65200"=
><div style=3D"font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial=
, Lucida Grande, sans-serif; font-size: 16px;" id=3D"yui_3_16_0_ym19_1_1460=
996044645_65199"><div class=3D"y_msg_container" id=3D"yui_3_16_0_ym19_1_146=
0996044645_65205"><div class=3D"yqt1428991998" id=3D"yqtfd56344">&gt;&gt;Bu=
t<br clear=3D"none">&gt;&gt; I think these issues should be balanced with t=
he overall benefit<br clear=3D"none">&gt;&gt; that the IETF World Tour prov=
ides.</div><br clear=3D"none"><br clear=3D"none">&gt;As I've said repeatedl=
y, I don't think the world tour actually<br clear=3D"none">&gt;does bring m=
uch benefit.&nbsp; I'm very hopeful that some of the<br clear=3D"none">&gt;=
South Americans who attended their first IETF meeting because<br clear=3D"n=
one">&gt;it was held in Buenos Aires will continue to participate (as in:<b=
r clear=3D"none">&gt;bring in work and participate in ongoing work, and not=
 as in: sit<br clear=3D"none">&gt;in meetings) but historically that has no=
t been the case.&nbsp;<br clear=3D"none"><div class=3D"yqt1428991998" id=3D=
"yqtfd62356">&nbsp;<br clear=3D"none">Just to put some numbers into this co=
nversation, we have 8 people from Latin America who have signed up to be a =
part of the Internet Draft Review teams. &nbsp; The first review team to fo=
rm will likely be the Spanish-speaking DNSOP review team.</div><div class=
=3D"yqt1428991998" id=3D"yqtfd62356"><br></div><div class=3D"yqt1428991998"=
 id=3D"yqtfd62356" dir=3D"ltr">This is one week after IETF 95 and after 3 d=
ays of soliciting review teams and basically zero publicity.</div><div clas=
s=3D"yqt1428991998" id=3D"yqtfd62356"><br></div><div class=3D"yqt1428991998=
" id=3D"yqtfd62356" dir=3D"ltr">I wonder if there has not been more partici=
pation in active IETF work before from other regions because there was no s=
tructured way to start participating and language insensitivity. &nbsp;(BTW=
, there is a new member of the Mentoring Team from Latin America, that I me=
t in Buenos Aires who will translate the Mentoring emails into Spanish.)</d=
iv><div class=3D"yqt1428991998" id=3D"yqtfd62356" dir=3D"ltr"><br></div><di=
v class=3D"yqt1428991998" id=3D"yqtfd62356" dir=3D"ltr">But the effort of t=
he Mentoring Team is standing on the shoulders of giants. &nbsp;People such=
 as Carlos Martinez, Christian O'Flaherty, Alvaro Retana, Dr. Juliao Braga,=
 and many others who have done such a tremendous job of outreach to their c=
ommunity in Latin America.</div><div class=3D"yqt1428991998" id=3D"yqtfd623=
56" dir=3D"ltr"><br></div><div class=3D"yqt1428991998" id=3D"yqtfd62356" di=
r=3D"ltr">So, let's do some changing of history.</div><div class=3D"yqt1428=
991998" id=3D"yqtfd62356" dir=3D"ltr"><br></div><div class=3D"yqt1428991998=
" id=3D"yqtfd62356" dir=3D"ltr">Nalini</div><div class=3D"yqt1428991998" id=
=3D"yqtfd62356" dir=3D"ltr"><br></div><div class=3D"yqt1428991998" id=3D"yq=
tfd62356" dir=3D"ltr"><br></div><br><br></div> </div> </div>  </div></div><=
/body></html>
------=_Part_2295530_681012570.1461009032630--


From nobody Mon Apr 18 13:16:14 2016
Return-Path: <fred.clark@sit.gob.gt>
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 8C07612E713 for <ietf@ietfa.amsl.com>; Mon, 18 Apr 2016 13:16:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.895
X-Spam-Level: 
X-Spam-Status: No, score=-2.895 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MSGID_FROM_MTA_HEADER=0.001, RP_MATCHES_RCVD=-0.996] 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 nbu-Tbbn0o9e for <ietf@ietfa.amsl.com>; Mon, 18 Apr 2016 13:16:11 -0700 (PDT)
Received: from sit.gob.gt (mail.sit.gob.gt [200.35.162.180]) by ietfa.amsl.com (Postfix) with ESMTP id 468AD12E712 for <ietf@ietf.org>; Mon, 18 Apr 2016 13:16:10 -0700 (PDT)
To: <ietf@ietf.org>
Date: Mon, 18 Apr 2016 14:15:20 -0600
Subject: =?utf-8?Q?RE:_=5BRecentattendees=5D_Interim_st?=	=?utf-8?Q?ep_on_meetings_site_feedback_=E2=80=94_f?=	=?utf-8?Q?or_sites_currently_under_active_?=	=?utf-8?Q?consideration?=
References: <20160418161552.9368.65562.idtracker@ietfa.amsl.com>
Message-ID: <000001d199af$08090370$181b0a50$@sit.gob.gt>
From: "fred.clark" <fred.clark@sit.gob.gt>
Received: from SITTELGRT (192.168.10.228 [192.168.10.228]) by sit.gob.gt; Sun, 17 Apr 2016 19:40:05 -0600
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 15.0
Thread-Index: AQI7wOa3/DPbBCXeyZwtwRUcqCTbWZ672xtQ
Content-Language: es-gt
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/1F66kBzMqTYiODF04yWiSe6gvUE>
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: Mon, 18 Apr 2016 20:16:13 -0000

Leslie,

I think all the cities provide all the facilities and conforts needed =
for an IETF meeting. I think it may depend on the time of the year. =
During the period of May to September the weather will allow the =
attendees to walk at lunch time. I have not been at other times of the =
year, but my feeling is tht after September the weather gets colder and =
may not be as pleasant.

Cordially

-------------------------------------------------------

Fred L. Clark, M. Sc.
Gerente de Regulaci=C3=B3n de Telefon=C3=ADa
Superintendencia de Telecomunicaciones
Correo electr=C3=B3nico:  fred.clark@sit.gob.gt
4=C2=AA avenida 15-51 zona 10
Ciudad de Guatemala, Guatemala 01010
Tel=C3=A9fono: +502.2321.1000
M=C3=B3vil: +502.5651.8133

No imprima este correo electr=C3=B3nico a menos que sea absolutamente =
necesario.=20
Do not print this electronic mail message unless it is absolutely =
necesary.

-----Mensaje original-----
De: Recentattendees [mailto:recentattendees-bounces@ietf.org] En nombre =
de The IAOC
Enviado el: lunes, 18 de abril de 2016 10:16
Para: IETF Announcement List <ietf-announce@ietf.org>
CC: recentattendees@ietf.org; ietf@ietf.org; 95all@ietf.org
Asunto: [Recentattendees] Interim step on meetings site feedback =
=E2=80=94 for sites currently under active consideration

All,

The IAOC and its meetings committee are continuing to review the =
situation with respect to meeting in Singapore.  As I noted about a week =
ago [1],  we are reviewing our meeting planning procedures to ensure =
that we have input at appropriate points to ensure issues are identified =
and addressed before contracts are signed and announcements made.  This =
will mean more transparency, including sharing the list of cities under =
consideration when we have a workable way to handle and hear the =
feedback.  We will make concrete progress on that at our retreat in a =
few weeks time.

In the meantime, we do have active site discussions and negotiations =
ready to close for meetings that are coming up.  In addition to reaching =
out to groups or agencies that have specific knowledge about travel for =
diverse groups including religious, ethnical and LGBTQ people, we are =
reaching out to the IETF community as a whole with this note.

In order to make sure we haven=E2=80=99t overlooked something else that =
should have been properly considered for sites under consideration, as =
well as to gather some running code on how a feedback process might =
work, we would like to hear from anyone who is aware of reasons we could =
not have a successful meeting in any of the following cities, or of any =
limits to attendee accessibility or inclusiveness that should be =
considered:

	Paris
	Montreal
	Copenhagen

Please send your input to venue-selection@ietf.org.  It will help the =
review process if the Subject line had the name of the city first, =
Subject: <city>.

In order not miss the contract opportunities, city-specific input would =
be most helpful if received by the end of May 2, 2016.

Other input on the process will be best received in e-mail at =
venue-selection@ietf.org with the Subject line: Process.  As we iterate =
the process we will continue to seek input to fashion a meeting planning =
process that works.


Leslie,
for the IAOC.

[1] =
https://mailarchive.ietf.org/arch/msg/ietf/hKwBYOwPkE6VTA4mxxf00NTLLF0

--=20

-------------------------------------------------------------------
Leslie Daigle
Principal, ThinkingCat Enterprises LLC
ldaigle@thinkingcat.com
-------------------------------------------------------------------

_______________________________________________
Recentattendees mailing list
Recentattendees@ietf.org
https://www.ietf.org/mailman/listinfo/recentattendees


From nobody Tue Apr 19 01:47:01 2016
Return-Path: <magnus.westerlund@ericsson.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 4DC0512E0D8; Tue, 19 Apr 2016 01:47:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] 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 s083o6D4L6op; Tue, 19 Apr 2016 01:46:58 -0700 (PDT)
Received: from sesbmg23.ericsson.net (sesbmg23.ericsson.net [193.180.251.37]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9427512DF4F; Tue, 19 Apr 2016 01:46:57 -0700 (PDT)
X-AuditID: c1b4fb25-f79f26d00000327e-57-5715f07fa2af
Received: from ESESSHC021.ericsson.se (Unknown_Domain [153.88.183.81]) by sesbmg23.ericsson.net (Symantec Mail Security) with SMTP id E6.DA.12926.F70F5175; Tue, 19 Apr 2016 10:46:55 +0200 (CEST)
Received: from [127.0.0.1] (153.88.183.153) by smtp.internal.ericsson.com (153.88.183.83) with Microsoft SMTP Server id 14.3.248.2; Tue, 19 Apr 2016 10:46:54 +0200
Subject: Re: [tsvwg] Last Call: <draft-ietf-tsvwg-rtcweb-qos-15.txt> (DSCP and other packet markings for WebRTC QoS) to Proposed Standard
To: "Black, David" <david.black@emc.com>, Cullen Jennings <fluffy@iii.ca>
References: <20160321174750.31944.71903.idtracker@ietfa.amsl.com> <56F26AD3.3010403@ericsson.com> <5BB71158-3530-47A2-9A33-811F65B2F677@iii.ca> <56FBBBC1.5060902@ericsson.com> <CE03DB3D7B45C245BCA0D243277949362E92B245@MX104CL02.corp.emc.com> <D12A5B0E-EF12-4BC8-999B-6ED50029C95A@iii.ca> <CE03DB3D7B45C245BCA0D243277949362E96B03B@MX104CL02.corp.emc.com>
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
Message-ID: <5715F07D.1050502@ericsson.com>
Date: Tue, 19 Apr 2016 10:46:53 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2
MIME-Version: 1.0
In-Reply-To: <CE03DB3D7B45C245BCA0D243277949362E96B03B@MX104CL02.corp.emc.com>
Content-Type: text/plain; charset="windows-1252"; format=flowed
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrFLMWRmVeSWpSXmKPExsUyM2J7oG79B9Fwgw2nlSy2Hl7LbvHnyj0W iw/rfzBaPNs4n8Wioe8uq8WxN3fZHNg8jhyZzeKxZMlPJo/L5z8yBjBHcdmkpOZklqUW6dsl cGVcvTGJpeCgUcWcB1PZGhgbNLoYOTkkBEwkWvbNYIKwxSQu3FvP1sXIxSEkcIRRYtHCRYwQ znJGic2r3jCBOMIC3YwSc850gbWICHhKbDw+nxnEFhJ4zSTxZV0+SBGzwClGiY5d88GK2AQs JG7+aGQDsXkFtCXWPXrGAmKzCKhKbFy7BcwWFYiRaHxwigmiRlDi5MwnYHFOAT+JHf1rWLsY OYCG2ks82FoGEmYWkJdo3jobaq+2RENTB+sERsFZSLpnIXTMQtKxgJF5FaNocWpxUm66kbFe alFmcnFxfp5eXmrJJkZgiB/c8lt1B+PlN46HGAU4GJV4eBUmioYLsSaWFVfmHmKU4GBWEuE9 +AYoxJuSWFmVWpQfX1Sak1p8iFGag0VJnDc78l+YkEB6YklqdmpqQWoRTJaJg1OqgTErfJdd YVP6r/P3Zj2cIGzxeqLFX1fbwsxZD+ddXDCv2OnIq8O6ixKrKn/d/PAhRmr9RzP5U1K9gfqC /CayO+Jiu08a5Dc4a+puPrD3lKHPpU6d7cx75yWzbni25du0mI9zSmqlA97ZhsSduV6dXCL4 zMyWW2mhULy6yd9eU5EPFy6tnDZ3+V8lluKMREMt5qLiRAAGxxHDbQIAAA==
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/DiLvtdzSH5I1YVfNlfnfJq65saE>
Cc: "tsvwg@ietf.org" <tsvwg@ietf.org>, "draft-ietf-tsvwg-rtcweb-qos@ietf.org" <draft-ietf-tsvwg-rtcweb-qos@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "tsvwg-chairs@ietf.org" <tsvwg-chairs@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: Tue, 19 Apr 2016 08:47:00 -0000

Den 2016-04-18 kl. 15:04, skrev Black, David:
> So, summarizing Magnus's concerns with proposals:
>
>>> [1] Flow Type in application-facing browser API:
>
>>> Propose an additional sentence:
>>> OLD
>>>    o  Flow Type: The browser provides this input as it knows if the flow
>>>       is audio, interactive video with or without audio, non-interactive
>>>       video with or without audio, or data.
>>> NEW
>>>    o  Flow Type: The browser provides this input as it knows if the flow
>>>       is audio, interactive video with or without audio, non-interactive
>>>       video with or without audio, or data.  For audio that is associated
>>>       with a video flow, the flow type of the associated video MAY
>>>       be used instead of the associated audio type.
>
> Magnus - does that new text suffice?

Yes.

>
>>> [2] What does "interactive" mean in an implementation?:
>>
>> We could add something along lines of ..... Currently in WebRTC, media sent over
>> RTP is assumed to be interactive while media streamed over HTTP is assumed not
>> to be. Future WebRTC extensions could allow streamed media over RTP.
>
> I believe the proposed additional sentence addresses the question of how a browser
> determines whether a video flow is interactive.  This proposed sentence will need to
> cite a WebRTC document that contains a statement to that effect, as I don't think this
> draft is the right place to be the primary reference for that statement.
>
> Magnus - would this approach be ok?

Yes.

/Magnus

>
> Thanks, --David
>
>> -----Original Message-----
>> From: Cullen Jennings [mailto:fluffy@iii.ca]
>> Sent: Friday, April 15, 2016 10:48 AM
>> To: Black, David
>> Cc: Magnus Westerlund; ietf@ietf.org; tsvwg-chairs@ietf.org; draft-ietf-tsvwg-
>> rtcweb-qos@ietf.org; tsvwg@ietf.org
>> Subject: Re: [tsvwg] Last Call: <draft-ietf-tsvwg-rtcweb-qos-15.txt> (DSCP and
>> other packet markings for WebRTC QoS) to Proposed Standard
>>
>>
>>> On Apr 3, 2016, at 3:37 PM, Black, David <david.black@emc.com> wrote:
>>>
>>> I see a couple of Magnus's points that appear to need additional text
>>> in the draft:
>>>
>>> [1] Flow Type in application-facing browser API:
>>>
>>>>>>>> o Flow Type: The browser provides this input as it knows if
>>>>>>>> the flow is audio, interactive video with or without audio,
>>>>>>>> non-interactive video with or without audio, or data.
>>>
>>> [... snip ...]
>>>
>>>> The main issue here is that to me it was not clear that "Interactive
>>>> Video with or without audio" allows for setting these DSCP values also
>>>> for the RTP stream containing audio also. This, I do see a need for
>>>> clarification on.
>>>
>>> Propose an additional sentence:
>>> OLD
>>>    o  Flow Type: The browser provides this input as it knows if the flow
>>>       is audio, interactive video with or without audio, non-interactive
>>>       video with or without audio, or data.
>>> NEW
>>>    o  Flow Type: The browser provides this input as it knows if the flow
>>>       is audio, interactive video with or without audio, non-interactive
>>>       video with or without audio, or data.  For audio that is associated
>>>       with a video flow, the flow type of the associated video MAY
>>>       be used instead of the associated audio type.
>>>
>>> I hesitate to say anything stronger than "MAY" here.
>>
>> Looks good.
>>
>>>
>>> [2] What does "interactive" mean in an implementation?:
>>
>> We could add something along lines of ..... Currently in WebRTC, media sent over
>> RTP is assumed to be interactive while media streamed over HTTP is assumed not
>> to be. Future WebRTC extensions could allow streamed media over RTP.
>>
>>
>>>
>>>> The issue is that this document is called: DSCP and other packet
>>>> markings for WebRTC QoS. Then this document define something that is not
>>>> immediately mappable onto what is being defined in the other WebRTC
>>>> specifications. That is why I am raising that there need to be more
>>>> clear coupling. If that coupling is to mostly happen in another
>>>> document, can we at least then have a proposal on the table for that
>>>> change to ensure that the result is understandable.
>>>
>>> Well, this TSVWG draft is definitely not the right place for a discussion of
>>> when a video flow is interactive or non-interactive - I hope we can agree
>>> on that.
>>>
>>> Beyond that, as Cullen (Jennings) is both an author of this document and
>>> one of the chairs of the rtcweb WG, I'd suggest that he and/or the rtcweb
>>> WG propose an appropriate location for discussion of when a video flow
>>> is interactive or non-interactive.  This TSVWG draft would then have an
>>> additional sentence added, e.g.,
>>>
>>> 	See [TBD] for further discussion of how to determine
>>> 	whether a video flow is interactive vs. non-interactive.
>>>
>>> I believe that the added reference here ([TBD] above) would be normative.
>>>
>>> Cullen?
>>
>> That discussion happened long ago for WebRTC and we decided we did not need
>> a JavaScript controls point in the WebRTC API to indicate if RTP was interactive or
>> not. If people start doing streaming video over RTP we can come back and revisit
>> this and trivially add an API to indicate that in the W3C WebRTC API. Part of what
>> drove this decision is the likes of Netflix / ITunes / Youtube are not asking the
>> browser vendors for streaming media over RTSP or RTP. They think HTTP works
>> much better for this. Thus the browser vendors see no need for non interactive
>> video over RTP. I agree with Magnus that this might change some day in the
>> future but right now, I think it's close enough that everyone can live with it.
>>
>> I'm not OK in treating it like some open issue that is still in discussion that
>> somehow holds up this spec - it's not.
>>
>>>
>>> Thanks, --David (as document  shepherd)
>>>
>
>


-- 

Magnus Westerlund

----------------------------------------------------------------------
Services, Media and Network features, Ericsson Research EAB/TXM
----------------------------------------------------------------------
Ericsson AB                 | Phone  +46 10 7148287
Färögatan 6                 | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------


From nobody Tue Apr 19 01:48:49 2016
Return-Path: <cattekwaad@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 92E4612DA8C; Tue, 19 Apr 2016 01:48:45 -0700 (PDT)
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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 FYM5wScgTdu7; Tue, 19 Apr 2016 01:48:43 -0700 (PDT)
Received: from mail-wm0-x22e.google.com (mail-wm0-x22e.google.com [IPv6:2a00:1450:400c:c09::22e]) (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 61CA412D568; Tue, 19 Apr 2016 01:48:43 -0700 (PDT)
Received: by mail-wm0-x22e.google.com with SMTP id e201so5165638wme.0; Tue, 19 Apr 2016 01:48:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc; bh=ynhMBoWnUfh/Xw9lTNKsGJVIb/eUJ4Ia/WmZzUPOj90=; b=k6gDm8mmC4qexto5K6alQXqM2udY/wNfd74tbiGpc1cg+eBJXzCNE6J0cW+FZKObqd ZCmWyLKlKz74mApOImeCIFYGgO0HRUc9AeBAiaVvoY2T3l71Sz3UBBLfQl35o2XiUtUK 39lS24BRVSnKwgaRcyhzjcxxHmNJx1eN1QtXAxNP57YAdDTA8RG4URg6NL4dF3VK/Dha t3h8qwNF64y/TgaQEZXsXs4QbOuFeYrERWz6mKeqgGyOu1ORm84M0buWRrFcukt+EH6G 9V3D/Zkgbkcc9Z09169Ci0lgRxkl9PYibyAM3G+t547vNP8HnAIo6N7sZiXC1Gv8Hcxw +D7w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:date :message-id:subject:from:to:cc; bh=ynhMBoWnUfh/Xw9lTNKsGJVIb/eUJ4Ia/WmZzUPOj90=; b=XiL0pwNap84k16AgYITC55JYvLOR5ZNifUf0IvsVph2mb/1xN2s52VwN/67PmwFkEJ KcN3LicN/OsPtmHIkBgL5Zp7R2AGveGj/x/sKqIdu44Sd0YL6FOFdIutrT4/4ogOEeqD 5oSeqtx7768UDjTFBE4NbG9WaqYlto5JKwDlibqS2+05S1XOdHTb4lUOzkPH8RvAD/wC GarYW52N3BN3e495DgOC3u6hxyFlaxwI4HFDIpr0AmMWlY+eTg6kvPgsMvhJl3e8JGeE 1ZCSn/l1us9JT+u6AidL1NBsan7bf37cQHKD2kv8nEeV8sXch7SpLjI/s8nGwnx8H+hV vEEw==
X-Gm-Message-State: AOPr4FW1fFSkRwaGrsEOfp1zvgky6AVxEF/Z4BrFZK73Yq7/+s26wNLUnBcVSyrXc/yISoY9nvFJ9Yw5ymoIoQ==
MIME-Version: 1.0
X-Received: by 10.28.153.203 with SMTP id b194mr23987137wme.3.1461055721869; Tue, 19 Apr 2016 01:48:41 -0700 (PDT)
Sender: cattekwaad@gmail.com
Received: by 10.194.190.71 with HTTP; Tue, 19 Apr 2016 01:48:41 -0700 (PDT)
In-Reply-To: <746128222.2295531.1461009032633.JavaMail.yahoo@mail.yahoo.com>
References: <57151C55.30206@gmail.com> <746128222.2295531.1461009032633.JavaMail.yahoo@mail.yahoo.com>
Date: Tue, 19 Apr 2016 09:48:41 +0100
X-Google-Sender-Auth: nPu0DFq-ehO1UOTKEugExq946fA
Message-ID: <CAD499eLvW0KFToSHLb4faMHk2c5ad+HAPEwumaq48QaUbh2n2A@mail.gmail.com>
Subject: Re: [Mtgvenue] Interim step on meetings site feedback for sites currently under active consideration
From: Corinne Cath <corinnecath@gmail.com>
To: Nalini Elkins <nalini.elkins@insidethestack.com>
Content-Type: multipart/alternative; boundary=001a114b38de4cb90c0530d28bc6
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/8p96oDclo_yVz2bXqCEAGLrvuYY>
Cc: "ietf@ietf.org" <ietf@ietf.org>, Juliao Braga <juliao@braga.net.br>, "mtgvenue@ietf.org" <mtgvenue@ietf.org>, "Carlos M. Martinez" <carlos@lacnic.net>, Christian O'Flaherty <oflaherty@isoc.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: Tue, 19 Apr 2016 08:48:45 -0000

--001a114b38de4cb90c0530d28bc6
Content-Type: text/plain; charset=UTF-8

Dear all,

Just a quick question: are you intending on providing feedback to the IAOC?
If so, maybe it makes sense to coordinate a bit in order to prevent a
duplication of entries? Or will it be useful if multiple people point out
the same themes?

Best,

Corinne

On Mon, Apr 18, 2016 at 8:50 PM, <nalini.elkins@insidethestack.com> wrote:

>
>
>
> >>But
> >> I think these issues should be balanced with the overall benefit
> >> that the IETF World Tour provides.
>
>
> >As I've said repeatedly, I don't think the world tour actually
> >does bring much benefit.  I'm very hopeful that some of the
> >South Americans who attended their first IETF meeting because
> >it was held in Buenos Aires will continue to participate (as in:
> >bring in work and participate in ongoing work, and not as in: sit
> >in meetings) but historically that has not been the case.
>
> Just to put some numbers into this conversation, we have 8 people from
> Latin America who have signed up to be a part of the Internet Draft Review
> teams.   The first review team to form will likely be the Spanish-speaking
> DNSOP review team.
>
> This is one week after IETF 95 and after 3 days of soliciting review teams
> and basically zero publicity.
>
> I wonder if there has not been more participation in active IETF work
> before from other regions because there was no structured way to start
> participating and language insensitivity.  (BTW, there is a new member of
> the Mentoring Team from Latin America, that I met in Buenos Aires who will
> translate the Mentoring emails into Spanish.)
>
> But the effort of the Mentoring Team is standing on the shoulders of
> giants.  People such as Carlos Martinez, Christian O'Flaherty, Alvaro
> Retana, Dr. Juliao Braga, and many others who have done such a tremendous
> job of outreach to their community in Latin America.
>
> So, let's do some changing of history.
>
> Nalini
>
>
>
>
>
> _______________________________________________
> Mtgvenue mailing list
> Mtgvenue@ietf.org
> https://www.ietf.org/mailman/listinfo/mtgvenue
>
>

--001a114b38de4cb90c0530d28bc6
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-family:georgia,=
serif">Dear all,<br><br></div><div class=3D"gmail_default" style=3D"font-fa=
mily:georgia,serif">Just a quick question: are you intending on providing f=
eedback to the IAOC? If so, maybe it makes sense to coordinate a bit in ord=
er to prevent a duplication of entries? Or will it be useful if multiple pe=
ople point out the same themes?<br><br></div><div class=3D"gmail_default" s=
tyle=3D"font-family:georgia,serif">Best,<br><br></div><div class=3D"gmail_d=
efault" style=3D"font-family:georgia,serif">Corinne <br></div></div><div cl=
ass=3D"gmail_extra"><br><div class=3D"gmail_quote">On Mon, Apr 18, 2016 at =
8:50 PM,  <span dir=3D"ltr">&lt;<a href=3D"mailto:nalini.elkins@insidethest=
ack.com" target=3D"_blank">nalini.elkins@insidethestack.com</a>&gt;</span> =
wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bord=
er-left:1px #ccc solid;padding-left:1ex"><div><div style=3D"color:#000;back=
ground-color:#fff;font-family:HelveticaNeue-Light,Helvetica Neue Light,Helv=
etica Neue,Helvetica,Arial,Lucida Grande,sans-serif;font-size:16px"><div><b=
r></div><div><br><br></div><div style=3D"display:block"><div style=3D"font-=
family:HelveticaNeue-Light,Helvetica Neue Light,Helvetica Neue,Helvetica,Ar=
ial,Lucida Grande,sans-serif;font-size:16px"><div style=3D"font-family:Helv=
eticaNeue,Helvetica Neue,Helvetica,Arial,Lucida Grande,sans-serif;font-size=
:16px"><div><div>&gt;&gt;But<br clear=3D"none">&gt;&gt; I think these issue=
s should be balanced with the overall benefit<br clear=3D"none">&gt;&gt; th=
at the IETF World Tour provides.</div><br clear=3D"none"><br clear=3D"none"=
>&gt;As I&#39;ve said repeatedly, I don&#39;t think the world tour actually=
<br clear=3D"none">&gt;does bring much benefit.=C2=A0 I&#39;m very hopeful =
that some of the<br clear=3D"none">&gt;South Americans who attended their f=
irst IETF meeting because<br clear=3D"none">&gt;it was held in Buenos Aires=
 will continue to participate (as in:<br clear=3D"none">&gt;bring in work a=
nd participate in ongoing work, and not as in: sit<br clear=3D"none">&gt;in=
 meetings) but historically that has not been the case.=C2=A0<br clear=3D"n=
one"><div>=C2=A0<br clear=3D"none">Just to put some numbers into this conve=
rsation, we have 8 people from Latin America who have signed up to be a par=
t of the Internet Draft Review teams. =C2=A0 The first review team to form =
will likely be the Spanish-speaking DNSOP review team.</div><div><br></div>=
<div dir=3D"ltr">This is one week after IETF 95 and after 3 days of solicit=
ing review teams and basically zero publicity.</div><div><br></div><div dir=
=3D"ltr">I wonder if there has not been more participation in active IETF w=
ork before from other regions because there was no structured way to start =
participating and language insensitivity. =C2=A0(BTW, there is a new member=
 of the Mentoring Team from Latin America, that I met in Buenos Aires who w=
ill translate the Mentoring emails into Spanish.)</div><div dir=3D"ltr"><br=
></div><div dir=3D"ltr">But the effort of the Mentoring Team is standing on=
 the shoulders of giants.=C2=A0 People such as Carlos Martinez, Christian O=
&#39;Flaherty, Alvaro Retana, Dr. Juliao Braga, and many others who have do=
ne such a tremendous job of outreach to their community in Latin America.</=
div><div dir=3D"ltr"><br></div><div dir=3D"ltr">So, let&#39;s do some chang=
ing of history.</div><div dir=3D"ltr"><br></div><div dir=3D"ltr">Nalini</di=
v><div dir=3D"ltr"><br></div><div dir=3D"ltr"><br></div><br><br></div> </di=
v> </div>  </div></div></div><br>__________________________________________=
_____<br>
Mtgvenue mailing list<br>
<a href=3D"mailto:Mtgvenue@ietf.org">Mtgvenue@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/mtgvenue" rel=3D"noreferre=
r" target=3D"_blank">https://www.ietf.org/mailman/listinfo/mtgvenue</a><br>
<br></blockquote></div><br></div>

--001a114b38de4cb90c0530d28bc6--


From nobody Tue Apr 19 05:03:12 2016
Return-Path: <mellon@fugue.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 A812D12D656 for <ietf@ietfa.amsl.com>; Tue, 19 Apr 2016 05:03:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.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 8KE39E0wqPAw for <ietf@ietfa.amsl.com>; Tue, 19 Apr 2016 05:03:08 -0700 (PDT)
Received: from mail-lf0-x234.google.com (mail-lf0-x234.google.com [IPv6:2a00:1450:4010:c07::234]) (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 F0EC412DD59 for <ietf@ietf.org>; Tue, 19 Apr 2016 05:02:53 -0700 (PDT)
Received: by mail-lf0-x234.google.com with SMTP id g184so15917078lfb.3 for <ietf@ietf.org>; Tue, 19 Apr 2016 05:02:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=bkw17dICZlyzCbYHiq9dIhnaZq1I0yg/GLFlXICHkHs=; b=n+gkBTlEISuAwieXO1ONvSXRwDKqatZfpsSqctzGQ9MwgZJN+jQTjao3cVaIR9ShOH Ds5l0SbZ08/0AAl1t/aYPlegL/W7zpBZjPig+aiBEPIr5HsXReiRfDuSRID+F84o7EqM 5GkT+uucxvV2rz4FBExhytuyf9lgIYJXgbwBziHtX48w28ipFhRwUIAH2vJT058YWk1+ zG/+wh6kAbLciMC83igLnEpPCLQltMKZ+s7D5gXRHX8MIKKbRORbDcIWQSgCidq4Jm9C oSBJdtV4vNawx4Y8lv0HXdiRNyI1eRiBds1YGkOHsnmQ3hDtWanSBjX1Zwgqjs5t4Tpj e69A==
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=bkw17dICZlyzCbYHiq9dIhnaZq1I0yg/GLFlXICHkHs=; b=QWLWC78ZJNm3DDou1d3c8MX90DfMvl6ep82sC1QRfgMApLLFY/pNMXw8y/FNuAuUPJ 9kK0wX/l66UJkMOtplihMPM2Cr5ABxDwmih6LYnnahagGQBgWdCzhOuGUNwd/UVzO48W wEnedk5wUSsav79yq2cQKnmy9W2TkwcKEpyMgUZqm0TjlKY/X9dy5GuTcsUvSqfK5pRo tR6Y6STjPVxoB/AEyaq0KMKLr+pouDFTMdBOYjjv5EwFS3lr3ys+ef54/hwLcDxEKIgz FlyIAJ9tBh2v9RK0Ez5lbBVjbkSO3rjeuRF+cKLNbcYL6Vf4qAJux9funtdbf5AOxOGo ZA7Q==
X-Gm-Message-State: AOPr4FVJ8MLu4kUw+jZ0N9TP+mb/EFJ5B3CO8Tbz6uQsvYdAzD4e54ajGRnMTWDdvuTHcvdeWvGuwQLFcevPqw==
X-Received: by 10.112.169.105 with SMTP id ad9mr1188697lbc.135.1461067371695;  Tue, 19 Apr 2016 05:02:51 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.25.213.19 with HTTP; Tue, 19 Apr 2016 05:02:12 -0700 (PDT)
X-Originating-IP: [71.233.41.235]
In-Reply-To: <CAD499eLvW0KFToSHLb4faMHk2c5ad+HAPEwumaq48QaUbh2n2A@mail.gmail.com>
References: <57151C55.30206@gmail.com> <746128222.2295531.1461009032633.JavaMail.yahoo@mail.yahoo.com> <CAD499eLvW0KFToSHLb4faMHk2c5ad+HAPEwumaq48QaUbh2n2A@mail.gmail.com>
From: Ted Lemon <mellon@fugue.com>
Date: Tue, 19 Apr 2016 08:02:12 -0400
Message-ID: <CAPt1N1kFgReUFy-RC9ovMUN9LqnBVRCconku4gyqow0sN_0Y9g@mail.gmail.com>
Subject: Re: [Mtgvenue] Interim step on meetings site feedback for sites currently under active consideration
To: Corinne Cath <corinnecath@gmail.com>
Content-Type: multipart/alternative; boundary=001a11c38c08aee1580530d5410f
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/mY74pia1MJ0_6TUbfhbOfgWUgpw>
Cc: "ietf@ietf.org" <ietf@ietf.org>, "mtgvenue@ietf.org" <mtgvenue@ietf.org>, Juliao Braga <juliao@braga.net.br>, "Carlos M. Martinez" <carlos@lacnic.net>, Christian O'Flaherty <oflaherty@isoc.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: Tue, 19 Apr 2016 12:03:10 -0000

--001a11c38c08aee1580530d5410f
Content-Type: text/plain; charset=UTF-8

The IETF has a very strong tradition of commenting at length on the topic
at hand and hoping either that IETF leadership will spend the time to
review the whole thread and extract the salient points from it, or give up
in despair.   So what you are seeing here is very much the IETF tradition.
  Asking people to do better probably won't work, although it never hurts
to try.

I personally see this as a tools problem, more than a communications
problem--we need better tools to track the points being made in discussions
so that either the people discussing can see that they don't need to make a
particular point again, or at least that the people tracking the discussion
can see that the point has already been made.

On Tue, Apr 19, 2016 at 4:48 AM, Corinne Cath <corinnecath@gmail.com> wrote:

> Dear all,
>
> Just a quick question: are you intending on providing feedback to the
> IAOC? If so, maybe it makes sense to coordinate a bit in order to prevent a
> duplication of entries? Or will it be useful if multiple people point out
> the same themes?
>
> Best,
>
> Corinne
>
> On Mon, Apr 18, 2016 at 8:50 PM, <nalini.elkins@insidethestack.com> wrote:
>
>>
>>
>>
>> >>But
>> >> I think these issues should be balanced with the overall benefit
>> >> that the IETF World Tour provides.
>>
>>
>> >As I've said repeatedly, I don't think the world tour actually
>> >does bring much benefit.  I'm very hopeful that some of the
>> >South Americans who attended their first IETF meeting because
>> >it was held in Buenos Aires will continue to participate (as in:
>> >bring in work and participate in ongoing work, and not as in: sit
>> >in meetings) but historically that has not been the case.
>>
>> Just to put some numbers into this conversation, we have 8 people from
>> Latin America who have signed up to be a part of the Internet Draft Review
>> teams.   The first review team to form will likely be the Spanish-speaking
>> DNSOP review team.
>>
>> This is one week after IETF 95 and after 3 days of soliciting review
>> teams and basically zero publicity.
>>
>> I wonder if there has not been more participation in active IETF work
>> before from other regions because there was no structured way to start
>> participating and language insensitivity.  (BTW, there is a new member of
>> the Mentoring Team from Latin America, that I met in Buenos Aires who will
>> translate the Mentoring emails into Spanish.)
>>
>> But the effort of the Mentoring Team is standing on the shoulders of
>> giants.  People such as Carlos Martinez, Christian O'Flaherty, Alvaro
>> Retana, Dr. Juliao Braga, and many others who have done such a tremendous
>> job of outreach to their community in Latin America.
>>
>> So, let's do some changing of history.
>>
>> Nalini
>>
>>
>>
>>
>>
>> _______________________________________________
>> Mtgvenue mailing list
>> Mtgvenue@ietf.org
>> https://www.ietf.org/mailman/listinfo/mtgvenue
>>
>>
>
> _______________________________________________
> Mtgvenue mailing list
> Mtgvenue@ietf.org
> https://www.ietf.org/mailman/listinfo/mtgvenue
>
>

--001a11c38c08aee1580530d5410f
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">The IETF has a very strong tradition of commenting at leng=
th on the topic at hand and hoping either that IETF leadership will spend t=
he time to review the whole thread and extract the salient points from it, =
or give up in despair. =C2=A0 So what you are seeing here is very much the =
IETF tradition. =C2=A0 Asking people to do better probably won&#39;t work, =
although it never hurts to try.=C2=A0<div><br></div><div>I personally see t=
his as a tools problem, more than a communications problem--we need better =
tools to track the points being made in discussions so that either the peop=
le discussing can see that they don&#39;t need to make a particular point a=
gain, or at least that the people tracking the discussion can see that the =
point has already been made.</div></div><div class=3D"gmail_extra"><br><div=
 class=3D"gmail_quote">On Tue, Apr 19, 2016 at 4:48 AM, Corinne Cath <span =
dir=3D"ltr">&lt;<a href=3D"mailto:corinnecath@gmail.com" target=3D"_blank">=
corinnecath@gmail.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_q=
uote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1e=
x"><div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-family:georg=
ia,serif">Dear all,<br><br></div><div class=3D"gmail_default" style=3D"font=
-family:georgia,serif">Just a quick question: are you intending on providin=
g feedback to the IAOC? If so, maybe it makes sense to coordinate a bit in =
order to prevent a duplication of entries? Or will it be useful if multiple=
 people point out the same themes?<br><br></div><div class=3D"gmail_default=
" style=3D"font-family:georgia,serif">Best,<br><br></div><div class=3D"gmai=
l_default" style=3D"font-family:georgia,serif">Corinne <br></div></div><div=
 class=3D"gmail_extra"><br><div class=3D"gmail_quote"><div><div class=3D"h5=
">On Mon, Apr 18, 2016 at 8:50 PM,  <span dir=3D"ltr">&lt;<a href=3D"mailto=
:nalini.elkins@insidethestack.com" target=3D"_blank">nalini.elkins@insideth=
estack.com</a>&gt;</span> wrote:<br></div></div><blockquote class=3D"gmail_=
quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1=
ex"><div><div class=3D"h5"><div><div style=3D"color:#000;background-color:#=
fff;font-family:HelveticaNeue-Light,Helvetica Neue Light,Helvetica Neue,Hel=
vetica,Arial,Lucida Grande,sans-serif;font-size:16px"><div><br></div><div><=
br><br></div><div style=3D"display:block"><div style=3D"font-family:Helveti=
caNeue-Light,Helvetica Neue Light,Helvetica Neue,Helvetica,Arial,Lucida Gra=
nde,sans-serif;font-size:16px"><div style=3D"font-family:HelveticaNeue,Helv=
etica Neue,Helvetica,Arial,Lucida Grande,sans-serif;font-size:16px"><div><d=
iv>&gt;&gt;But<br clear=3D"none">&gt;&gt; I think these issues should be ba=
lanced with the overall benefit<br clear=3D"none">&gt;&gt; that the IETF Wo=
rld Tour provides.</div><br clear=3D"none"><br clear=3D"none">&gt;As I&#39;=
ve said repeatedly, I don&#39;t think the world tour actually<br clear=3D"n=
one">&gt;does bring much benefit.=C2=A0 I&#39;m very hopeful that some of t=
he<br clear=3D"none">&gt;South Americans who attended their first IETF meet=
ing because<br clear=3D"none">&gt;it was held in Buenos Aires will continue=
 to participate (as in:<br clear=3D"none">&gt;bring in work and participate=
 in ongoing work, and not as in: sit<br clear=3D"none">&gt;in meetings) but=
 historically that has not been the case.=C2=A0<br clear=3D"none"><div>=C2=
=A0<br clear=3D"none">Just to put some numbers into this conversation, we h=
ave 8 people from Latin America who have signed up to be a part of the Inte=
rnet Draft Review teams. =C2=A0 The first review team to form will likely b=
e the Spanish-speaking DNSOP review team.</div><div><br></div><div dir=3D"l=
tr">This is one week after IETF 95 and after 3 days of soliciting review te=
ams and basically zero publicity.</div><div><br></div><div dir=3D"ltr">I wo=
nder if there has not been more participation in active IETF work before fr=
om other regions because there was no structured way to start participating=
 and language insensitivity. =C2=A0(BTW, there is a new member of the Mento=
ring Team from Latin America, that I met in Buenos Aires who will translate=
 the Mentoring emails into Spanish.)</div><div dir=3D"ltr"><br></div><div d=
ir=3D"ltr">But the effort of the Mentoring Team is standing on the shoulder=
s of giants.=C2=A0 People such as Carlos Martinez, Christian O&#39;Flaherty=
, Alvaro Retana, Dr. Juliao Braga, and many others who have done such a tre=
mendous job of outreach to their community in Latin America.</div><div dir=
=3D"ltr"><br></div><div dir=3D"ltr">So, let&#39;s do some changing of histo=
ry.</div><div dir=3D"ltr"><br></div><div dir=3D"ltr">Nalini</div><div dir=
=3D"ltr"><br></div><div dir=3D"ltr"><br></div><br><br></div> </div> </div> =
 </div></div></div><br></div></div>________________________________________=
_______<br>
Mtgvenue mailing list<br>
<a href=3D"mailto:Mtgvenue@ietf.org" target=3D"_blank">Mtgvenue@ietf.org</a=
><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/mtgvenue" rel=3D"noreferre=
r" target=3D"_blank">https://www.ietf.org/mailman/listinfo/mtgvenue</a><br>
<br></blockquote></div><br></div>
<br>_______________________________________________<br>
Mtgvenue mailing list<br>
<a href=3D"mailto:Mtgvenue@ietf.org">Mtgvenue@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/mtgvenue" rel=3D"noreferre=
r" target=3D"_blank">https://www.ietf.org/mailman/listinfo/mtgvenue</a><br>
<br></blockquote></div><br></div>

--001a11c38c08aee1580530d5410f--


From nobody Tue Apr 19 10:37:50 2016
Return-Path: <christian.oflaherty@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 2342A12EE1C for <ietf@ietfa.amsl.com>; Tue, 19 Apr 2016 10:37:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 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, 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 FQ1E0GlN9Mes for <ietf@ietfa.amsl.com>; Tue, 19 Apr 2016 10:37:02 -0700 (PDT)
Received: from mail-vk0-x229.google.com (mail-vk0-x229.google.com [IPv6:2607:f8b0:400c:c05::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 AC53A12EE0F for <ietf@ietf.org>; Tue, 19 Apr 2016 10:37:02 -0700 (PDT)
Received: by mail-vk0-x229.google.com with SMTP id e185so28413260vkb.1 for <ietf@ietf.org>; Tue, 19 Apr 2016 10:37:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=subject:mime-version:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=fAW9BU/1k00L4Bz5hm5qhLvIPA4pJjhjTG9k5/OOiXs=; b=cK4a90Ub09YMM2t+afFSn5YXhHdwYgD1Dxj3dxmcpqJtgOntlTtPADVKtYPJVhkoXU RKf8uSIzhOo6MEblfAegTt04RvTOR88ObGuG3KpUFAgDQVkVeiZcM5S1AULCwrmuBxib q+fJr0q59Z5Xlvb5iY03Po+zghXAuBsfM5dTmoXpsjtE0fgM68uwiQlQF7rrPvJj1Zlq 1Q0+69uPBMDkg8Dhy7npNX4zIJ6np1N5SrJUcvMQcRNWwOM3fj7r9WQFs35yt1LTWju+ NlgKFTegp5bpGkxuInVk/MW0a//fCP81IrkE2BJ/XwtFqseOasRGpuwrqP+W88DU+hdD zANQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:mime-version:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=fAW9BU/1k00L4Bz5hm5qhLvIPA4pJjhjTG9k5/OOiXs=; b=U3+bDQXOLbsYCkXG+hBjZJMSnItPYkecp359/B6tcujt+2Jss9mertOdP5MaFEqEW5 ha8Guo2aMDkm29WX5uw4xIda0JZVGkzpWJRx3DLeXmEMStfFkIR9wBkA6b66RQENkwoB Mvk/26n4yRHo0F7GzWArHAjj0+aYTGR4E4SvW6jXhNRy+Uq6zhsa3aCmd4umdiMvE75m pAVu1z641GueApKRdTvLVqeJX0QuEinbvscVtnyaSZpsxPyaZWCuPrdxbMFs2Zo9bSPP 8LbDFgAbOmrYweeJXtv5RKMFV/PhQ1GYcibFG8dch7ndHODHh06dlbdJF97y5pL0H38t NdIw==
X-Gm-Message-State: AOPr4FX7h+rjib02+UHQzx66N+LrYn47PS2DLck+x8EXXZQQSIul+Uw+zw4NeU5mnAFZ8A==
X-Received: by 10.159.36.15 with SMTP id 15mr2356819uaq.48.1461087421867; Tue, 19 Apr 2016 10:37:01 -0700 (PDT)
Received: from [10.0.1.13] (r167-61-127-90.dialup.adsl.anteldata.net.uy. [167.61.127.90]) by smtp.gmail.com with ESMTPSA id n78sm8648181vkf.7.2016.04.19.10.36.59 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Tue, 19 Apr 2016 10:37:00 -0700 (PDT)
Subject: Re: Interim step on meetings site feedback for sites currently under active consideration
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Content-Type: text/plain; charset=windows-1252
From: Christian O'Flaherty <christian.oflaherty@gmail.com>
In-Reply-To: <57151C55.30206@gmail.com>
Date: Tue, 19 Apr 2016 14:36:56 -0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <54D9A539-6409-4692-85F6-E4837E823AAE@gmail.com>
References: <20160418161552.9368.65562.idtracker@ietfa.amsl.com> <8fb376e11631f9ddf73f9385ec5472c3.squirrel@www.trepanning.net> <57151C55.30206@gmail.com>
To: Melinda Shore <melinda.shore@gmail.com>
X-Mailer: Apple Mail (2.3124)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/pRihFBvvLfE58LxWvJfAktLRTLs>
Cc: 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: Tue, 19 Apr 2016 17:37:12 -0000

> On Apr 18, 2016, at 2:41 PM, Melinda Shore <melinda.shore@gmail.com> =
wrote:
>=20
> On 4/18/16 9:09 AM, Dan Harkins wrote:
>> But
>> I think these issues should be balanced with the overall benefit
>> that the IETF World Tour provides.
>=20
> As I've said repeatedly, I don't think the world tour actually
> does bring much benefit.  I'm very hopeful that some of the
> South Americans who attended their first IETF meeting because
> it was held in Buenos Aires will continue to participate (as in:
> bring in work and participate in ongoing work, and not as in: sit
> in meetings) but historically that has not been the case. =20


BTW=85 if there=92s a way to keep track and measure that additional =
active participation from Latin America I=92ll be happy to do it.

I=92m open to suggestions on how it can be than.

Christian =20




> I also
> think that the world tour tends to have the unintended side-effect
> of overemphasizing the importance of meetings to our process.
>=20
> Also, note that a large number of regulars opted to skip the meeting
> in Buenos Aires.  Granted, there are those who might see that as
> a benefit.
>=20
> Melinda
>=20


From nobody Tue Apr 19 10:56:18 2016
Return-Path: <mellon@fugue.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 2BEC612E3F2 for <ietf@ietfa.amsl.com>; Tue, 19 Apr 2016 10:56:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.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 MgqW0Cd11bq1 for <ietf@ietfa.amsl.com>; Tue, 19 Apr 2016 10:56:15 -0700 (PDT)
Received: from mail-ig0-x22d.google.com (mail-ig0-x22d.google.com [IPv6:2607:f8b0:4001:c05::22d]) (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 DF23812E3EE for <ietf@ietf.org>; Tue, 19 Apr 2016 10:56:14 -0700 (PDT)
Received: by mail-ig0-x22d.google.com with SMTP id gy3so106699713igb.0 for <ietf@ietf.org>; Tue, 19 Apr 2016 10:56:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=460pdcRKhcivvMLf/kD3S4mE+ZEIY7A0md639HrLzMU=; b=ApN2Wp3uuf6EWT4s7hT2/SmFHOd3xSCOrV2sG9n2ZSO6sCBJie12UEiAw/mt9pRjnk 6JyZocozD977+u/fBnYdZcmxkjpr4Kwh06ulHAXdV2c/3G+SM6XcI1QqfgC0KZwGvp2T 9BinyhK5Cr7ishEzX8V/wBqGXA2zU+Aa5zAvz0A/RwCuowm0i6nnWjYiEjKAg0LjYoSx +/+cZqycVCk1m1PARnpkGMchHIgmk1l8O6pyl/g44c/01/Xe1xOfuJBoWkA+Bxv0coE1 HXCvo6lTEa2lOEpMurHH1p9bG8h/0EBX1fOKZLaVDg9wVPQwe1yCn28e6uMj4qeXVkpu Ybfw==
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=460pdcRKhcivvMLf/kD3S4mE+ZEIY7A0md639HrLzMU=; b=S3O1XzMmw73OU494N8nbCYoNaVLIyTpgHcwSa7/sRMmv0QtsUgU4coKmh0p+KzSUk2 C74DHDqjokDgwtbPjmIm+Eg+dGFdyCVS5xV0nmRyQ3lIG1cciTergUsSuwY8j5m39VnE jutyH4p1Jj4T+R7gzijCIoLurCkrkiY8BudVFTS3+aXeJnj8SMGGLMoWLuPyYzpxMTph XC2PdOPbRWCewcc74Kvi1bnEgcz8KjZFMtqO/Z0YNGLYz23rPSkzVOyKSoQWQmGJD6F1 3Hj1YP4QICLkb5mHQYcCI/f51L/3/qIuTOKkxe0+wZaGBm4AtK0Lb8giV2yfZBGIYt9x bs+w==
X-Gm-Message-State: AOPr4FX9+yQEu3iPsbm+aOoJua8Xz5fAuntLDq2P5DBwVgDfu0bFg3exdzhIwbvpKEm3/6R8dr3RlxJgyWaPWQ==
X-Received: by 10.50.59.211 with SMTP id b19mr5399664igr.58.1461088573921; Tue, 19 Apr 2016 10:56:13 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.64.144.225 with HTTP; Tue, 19 Apr 2016 10:55:34 -0700 (PDT)
X-Originating-IP: [71.233.41.235]
In-Reply-To: <54D9A539-6409-4692-85F6-E4837E823AAE@gmail.com>
References: <20160418161552.9368.65562.idtracker@ietfa.amsl.com> <8fb376e11631f9ddf73f9385ec5472c3.squirrel@www.trepanning.net> <57151C55.30206@gmail.com> <54D9A539-6409-4692-85F6-E4837E823AAE@gmail.com>
From: Ted Lemon <mellon@fugue.com>
Date: Tue, 19 Apr 2016 13:55:34 -0400
Message-ID: <CAPt1N1n+676sAWFLee3oUGUgnTNHh95yFgrsmyjB5VbSmF-=XQ@mail.gmail.com>
Subject: Re: Interim step on meetings site feedback for sites currently under active consideration
To: "Christian O'Flaherty" <christian.oflaherty@gmail.com>
Content-Type: multipart/alternative; boundary=047d7bd757586f37730530da31d5
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/x4VTiQ5FieVkNkoVLxYPAMBZ8RI>
Cc: ietf <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: Tue, 19 Apr 2016 17:56:17 -0000

--047d7bd757586f37730530da31d5
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

It should be pretty easy for the IAD to measure this by comparing the list
of newcomers in Argentina to the list of participants in Berlin, for
example.   I am fairly sure that they already do this, and possibly may
even have made presentations about it from time to time at the plenary... :=
)

On Tue, Apr 19, 2016 at 1:36 PM, Christian O'Flaherty <
christian.oflaherty@gmail.com> wrote:

>
> > On Apr 18, 2016, at 2:41 PM, Melinda Shore <melinda.shore@gmail.com>
> wrote:
> >
> > On 4/18/16 9:09 AM, Dan Harkins wrote:
> >> But
> >> I think these issues should be balanced with the overall benefit
> >> that the IETF World Tour provides.
> >
> > As I've said repeatedly, I don't think the world tour actually
> > does bring much benefit.  I'm very hopeful that some of the
> > South Americans who attended their first IETF meeting because
> > it was held in Buenos Aires will continue to participate (as in:
> > bring in work and participate in ongoing work, and not as in: sit
> > in meetings) but historically that has not been the case.
>
>
> BTW=E2=80=A6 if there=E2=80=99s a way to keep track and measure that addi=
tional active
> participation from Latin America I=E2=80=99ll be happy to do it.
>
> I=E2=80=99m open to suggestions on how it can be than.
>
> Christian
>
>
>
>
> > I also
> > think that the world tour tends to have the unintended side-effect
> > of overemphasizing the importance of meetings to our process.
> >
> > Also, note that a large number of regulars opted to skip the meeting
> > in Buenos Aires.  Granted, there are those who might see that as
> > a benefit.
> >
> > Melinda
> >
>
>

--047d7bd757586f37730530da31d5
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">It should be pretty easy for the IAD to measure this by co=
mparing the list of newcomers in Argentina to the list of participants in B=
erlin, for example. =C2=A0 I am fairly sure that they already do this, and =
possibly may even have made presentations about it from time to time at the=
 plenary... :)</div><div class=3D"gmail_extra"><br><div class=3D"gmail_quot=
e">On Tue, Apr 19, 2016 at 1:36 PM, Christian O&#39;Flaherty <span dir=3D"l=
tr">&lt;<a href=3D"mailto:christian.oflaherty@gmail.com" target=3D"_blank">=
christian.oflaherty@gmail.com</a>&gt;</span> wrote:<br><blockquote class=3D=
"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding=
-left:1ex"><br>
&gt; On Apr 18, 2016, at 2:41 PM, Melinda Shore &lt;<a href=3D"mailto:melin=
da.shore@gmail.com">melinda.shore@gmail.com</a>&gt; wrote:<br>
<span class=3D"">&gt;<br>
&gt; On 4/18/16 9:09 AM, Dan Harkins wrote:<br>
&gt;&gt; But<br>
&gt;&gt; I think these issues should be balanced with the overall benefit<b=
r>
&gt;&gt; that the IETF World Tour provides.<br>
&gt;<br>
&gt; As I&#39;ve said repeatedly, I don&#39;t think the world tour actually=
<br>
&gt; does bring much benefit.=C2=A0 I&#39;m very hopeful that some of the<b=
r>
&gt; South Americans who attended their first IETF meeting because<br>
&gt; it was held in Buenos Aires will continue to participate (as in:<br>
&gt; bring in work and participate in ongoing work, and not as in: sit<br>
&gt; in meetings) but historically that has not been the case.<br>
<br>
<br>
</span>BTW=E2=80=A6 if there=E2=80=99s a way to keep track and measure that=
 additional active participation from Latin America I=E2=80=99ll be happy t=
o do it.<br>
<br>
I=E2=80=99m open to suggestions on how it can be than.<br>
<br>
Christian<br>
<br>
<br>
<br>
<br>
&gt; I also<br>
&gt; think that the world tour tends to have the unintended side-effect<br>
&gt; of overemphasizing the importance of meetings to our process.<br>
&gt;<br>
&gt; Also, note that a large number of regulars opted to skip the meeting<b=
r>
&gt; in Buenos Aires.=C2=A0 Granted, there are those who might see that as<=
br>
&gt; a benefit.<br>
&gt;<br>
&gt; Melinda<br>
&gt;<br>
<br>
</blockquote></div><br></div>

--047d7bd757586f37730530da31d5--


From nobody Tue Apr 19 11:03:28 2016
Return-Path: <nalini.elkins@insidethestack.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 BBC3712E430 for <ietf@ietfa.amsl.com>; Tue, 19 Apr 2016 11:03:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.619
X-Spam-Level: 
X-Spam-Status: No, score=-2.619 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=yahoo.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 qefmdNoyviwe for <ietf@ietfa.amsl.com>; Tue, 19 Apr 2016 11:03:23 -0700 (PDT)
Received: from nm3-vm5.bullet.mail.ne1.yahoo.com (nm3-vm5.bullet.mail.ne1.yahoo.com [98.138.91.225]) (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 437B412E377 for <ietf@ietf.org>; Tue, 19 Apr 2016 11:03:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1461089001; bh=LrbRg1xY9es0zrTFO0ms8Tdz/grtgmfyPEQbutStXX0=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:From:Subject; b=G21naYYldlNT5/pI6/qU7oQv8ZazBYjiQbK1oO/kaPbNluyZxViEmTYQNu1Ue8PQpNbGKGSvYozyNWx7YgcJYxbsVGaTcrEwu11Cpkv1dFXvqQiUSgojdaN/SBgcvbv22VLL2sWZCMXW53xWUjtl3cNRPszfo63WW8ivhN/dkZRgLlpDnLvby3AXIZjpYckUhUlXikEkQyeNzbrh7XEq/lrnt1/i6GsSwfrgvzo1VVgBkTORhPpM8PPWCO3O7dNxfRT/FQZoAaptzhrRstPw28FaLV1yPCw6NKd356nFb4S+oSCFUdw8GV5qiiyDps1Sqs8axu+pMIuL9mig8hVtGg==
Received: from [98.138.100.115] by nm3.bullet.mail.ne1.yahoo.com with NNFMP; 19 Apr 2016 18:03:21 -0000
Received: from [98.138.89.245] by tm106.bullet.mail.ne1.yahoo.com with NNFMP;  19 Apr 2016 18:03:21 -0000
Received: from [127.0.0.1] by omp1059.mail.ne1.yahoo.com with NNFMP; 19 Apr 2016 18:03:21 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 746909.76215.bm@omp1059.mail.ne1.yahoo.com
X-YMail-OSG: 2HEBzvcVM1mpJWiW1zjMBnCRqosXv6QoXJV74uptXz.obKbluFLMSeF.UqrQK4n uRMvlfjZKfxrmGkrrsc4Kfh5Pwbwf2B6WWQNHauraZG5giUPpuHKiJC0M_a9B0co5QzdPV61mxTS DeY7gQ4FP7MDJ8HYYrl_2dCNcrm6JClxa0e8SegblNjQlS0O_a7aU1e6ESZU9hp5ioh1UogO_jPt 1EYO7fogH2.RP_pG.yL1XCIN5k2m_Hi2BcDwWZdDT6hVFUnc_liElDQrbzmDch8NfSYRgelNLnsN _4RCkvN8x95EQXAcWDx3j_bTuo8dA8NMP6bNeh89iYezf3CRkASYrHt_tpm7O_CkPFqummxGmPm7 M1QvdbK4SgkmHyE2Q5hKbWgh102x3jH8ZHjACMfHAgHl49OOmwK01KtmpA8XcXKk0imp8P0QeLWt 41kHZbZQj8YD5iqVT1Ic.nNhwJyruwmtbDMY7Lj5ewhmp0LwiERKj7ZbxSbjAU5y_mPfRXkqA6jV gRskn6Wp.lvrSaO8JGsdn0jXCjYDFBi7OmLZOGtA-
Received: by 98.138.105.216; Tue, 19 Apr 2016 18:03:21 +0000 
Date: Tue, 19 Apr 2016 18:03:06 +0000 (UTC)
From: <nalini.elkins@insidethestack.com>
To: Ted Lemon <mellon@fugue.com>,  Christian O'Flaherty <christian.oflaherty@gmail.com>
Message-ID: <876171588.2793946.1461088986149.JavaMail.yahoo@mail.yahoo.com>
In-Reply-To: <CAPt1N1n+676sAWFLee3oUGUgnTNHh95yFgrsmyjB5VbSmF-=XQ@mail.gmail.com>
References: <CAPt1N1n+676sAWFLee3oUGUgnTNHh95yFgrsmyjB5VbSmF-=XQ@mail.gmail.com>
Subject: Re: Interim step on meetings site feedback for sites currently under active consideration
MIME-Version: 1.0
Content-Type: multipart/alternative;  boundary="----=_Part_2793945_1897585121.1461088986144"
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/R2JEeMd26tG4Fs9w-9FGTZ__2GE>
Cc: "diversity@ietf.org" <diversity@ietf.org>, ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: nalini.elkins@insidethestack.com
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: Tue, 19 Apr 2016 18:03:26 -0000

------=_Part_2793945_1897585121.1461088986144
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

=C2=A0

>It should be pretty easy for the IAD to measure this by comparing the list=
 of newcomers in Argentina to the list of participants in Berlin, for examp=
le. =C2=A0 I am fairly sure that they already do >this, and possibly may ev=
en have made presentations about it from time to time at the plenary... :)
We have been having a discussion in the Diversity about this. =C2=A0=C2=A0
Some stats that I have for Latin America:
8 newcomers signed up for Internet Draft Review teams
1 newcomer participating in IPPM
But, that is only what I know via personal information. =C2=A0I don't know =
how to do this automatically. =C2=A0 I suspect that these newcomers are not=
 likely to get funding to participate in Berlin. =C2=A0But, we can get them=
 to be active on email lists (as a start).
Nalini

On Tue, Apr 19, 2016 at 1:36 PM, Christian O'Flaherty <christian.oflaherty@=
gmail.com> wrote:


> On Apr 18, 2016, at 2:41 PM, Melinda Shore <melinda.shore@gmail.com> wrot=
e:
>
> On 4/18/16 9:09 AM, Dan Harkins wrote:
>> But
>> I think these issues should be balanced with the overall benefit
>> that the IETF World Tour provides.
>
> As I've said repeatedly, I don't think the world tour actually
> does bring much benefit.=C2=A0 I'm very hopeful that some of the
> South Americans who attended their first IETF meeting because
> it was held in Buenos Aires will continue to participate (as in:
> bring in work and participate in ongoing work, and not as in: sit
> in meetings) but historically that has not been the case.


BTW=E2=80=A6 if there=E2=80=99s a way to keep track and measure that additi=
onal active participation from Latin America I=E2=80=99ll be happy to do it=
.

I=E2=80=99m open to suggestions on how it can be than.

Christian




> I also
> think that the world tour tends to have the unintended side-effect
> of overemphasizing the importance of meetings to our process.
>
> Also, note that a large number of regulars opted to skip the meeting
> in Buenos Aires.=C2=A0 Granted, there are those who might see that as
> a benefit.
>
> Melinda
>





  
------=_Part_2793945_1897585121.1461088986144
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<html><head></head><body><div style=3D"color:#000; background-color:#fff; f=
ont-family:HelveticaNeue-Light, Helvetica Neue Light, Helvetica Neue, Helve=
tica, Arial, Lucida Grande, sans-serif;font-size:16px"><div id=3D"yui_3_16_=
0_ym19_1_1461087890052_20096">&nbsp;</div><div class=3D"qtdSeparateBR"><br>=
<br></div><div class=3D"yahoo_quoted" id=3D"yui_3_16_0_ym19_1_1461087890052=
_20100" style=3D"display: block;"><div style=3D"font-family: HelveticaNeue-=
Light, Helvetica Neue Light, Helvetica Neue, Helvetica, Arial, Lucida Grand=
e, sans-serif; font-size: 16px;" id=3D"yui_3_16_0_ym19_1_1461087890052_2009=
9"><div style=3D"font-family: HelveticaNeue, Helvetica Neue, Helvetica, Ari=
al, Lucida Grande, sans-serif; font-size: 16px;" id=3D"yui_3_16_0_ym19_1_14=
61087890052_20098"><div class=3D"y_msg_container" id=3D"yui_3_16_0_ym19_1_1=
461087890052_20118"><div id=3D"yiv1261521057"><div id=3D"yui_3_16_0_ym19_1_=
1461087890052_20117"><div dir=3D"ltr" id=3D"yui_3_16_0_ym19_1_1461087890052=
_20120">&gt;It should be pretty easy for the IAD to measure this by compari=
ng the list of newcomers in Argentina to the list of participants in Berlin=
, for example. &nbsp; I am fairly sure that they already do &gt;this, and p=
ossibly may even have made presentations about it from time to time at the =
plenary... :)</div><div dir=3D"ltr" id=3D"yui_3_16_0_ym19_1_1461087890052_2=
0120"><br></div><div dir=3D"ltr" id=3D"yui_3_16_0_ym19_1_1461087890052_2012=
0">We have been having a discussion in the Diversity about this. &nbsp;&nbs=
p;</div><div dir=3D"ltr" id=3D"yui_3_16_0_ym19_1_1461087890052_20120"><br><=
/div><div dir=3D"ltr" id=3D"yui_3_16_0_ym19_1_1461087890052_20120">Some sta=
ts that I have for Latin America:</div><div dir=3D"ltr" id=3D"yui_3_16_0_ym=
19_1_1461087890052_20120"><br></div><div dir=3D"ltr" id=3D"yui_3_16_0_ym19_=
1_1461087890052_20120">8 newcomers signed up for Internet Draft Review team=
s</div><div dir=3D"ltr" id=3D"yui_3_16_0_ym19_1_1461087890052_20120"><br></=
div><div dir=3D"ltr" id=3D"yui_3_16_0_ym19_1_1461087890052_20120">1 newcome=
r participating in IPPM</div><div dir=3D"ltr" id=3D"yui_3_16_0_ym19_1_14610=
87890052_20120"><br></div><div dir=3D"ltr" id=3D"yui_3_16_0_ym19_1_14610878=
90052_20120">But, that is only what I know via personal information. &nbsp;=
I don't know how to do this automatically. &nbsp; I suspect that these newc=
omers are not likely to get funding to participate in Berlin. &nbsp;But, we=
 can get them to be active on email lists (as a start).</div><div dir=3D"lt=
r" id=3D"yui_3_16_0_ym19_1_1461087890052_20120"><br></div><div dir=3D"ltr" =
id=3D"yui_3_16_0_ym19_1_1461087890052_20120">Nalini</div><div dir=3D"ltr" i=
d=3D"yui_3_16_0_ym19_1_1461087890052_20120"><br></div><div class=3D"yiv1261=
521057yqt6596304951" id=3D"yiv1261521057yqt27617"><div class=3D"yiv12615210=
57gmail_extra" id=3D"yui_3_16_0_ym19_1_1461087890052_20116"><br clear=3D"no=
ne"><div class=3D"yiv1261521057gmail_quote" id=3D"yui_3_16_0_ym19_1_1461087=
890052_20115">On Tue, Apr 19, 2016 at 1:36 PM, Christian O'Flaherty <span d=
ir=3D"ltr" id=3D"yui_3_16_0_ym19_1_1461087890052_20129">&lt;<a rel=3D"nofol=
low" shape=3D"rect" ymailto=3D"mailto:christian.oflaherty@gmail.com" target=
=3D"_blank" href=3D"mailto:christian.oflaherty@gmail.com" id=3D"yui_3_16_0_=
ym19_1_1461087890052_20128">christian.oflaherty@gmail.com</a>&gt;</span> wr=
ote:<br clear=3D"none"><blockquote class=3D"yiv1261521057gmail_quote" style=
=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;" id=3D"y=
ui_3_16_0_ym19_1_1461087890052_20114"><br clear=3D"none">
&gt; On Apr 18, 2016, at 2:41 PM, Melinda Shore &lt;<a rel=3D"nofollow" sha=
pe=3D"rect" ymailto=3D"mailto:melinda.shore@gmail.com" target=3D"_blank" hr=
ef=3D"mailto:melinda.shore@gmail.com">melinda.shore@gmail.com</a>&gt; wrote=
:<br clear=3D"none">
<span class=3D"yiv1261521057" id=3D"yui_3_16_0_ym19_1_1461087890052_20119">=
&gt;<br clear=3D"none">
&gt; On 4/18/16 9:09 AM, Dan Harkins wrote:<br clear=3D"none">
&gt;&gt; But<br clear=3D"none">
&gt;&gt; I think these issues should be balanced with the overall benefit<b=
r clear=3D"none">
&gt;&gt; that the IETF World Tour provides.<br clear=3D"none">
&gt;<br clear=3D"none">
&gt; As I've said repeatedly, I don't think the world tour actually<br clea=
r=3D"none">
&gt; does bring much benefit.&nbsp; I'm very hopeful that some of the<br cl=
ear=3D"none">
&gt; South Americans who attended their first IETF meeting because<br clear=
=3D"none">
&gt; it was held in Buenos Aires will continue to participate (as in:<br cl=
ear=3D"none">
&gt; bring in work and participate in ongoing work, and not as in: sit<br c=
lear=3D"none">
&gt; in meetings) but historically that has not been the case.<br clear=3D"=
none">
<br clear=3D"none">
<br clear=3D"none">
</span>BTW=E2=80=A6 if there=E2=80=99s a way to keep track and measure that=
 additional active participation from Latin America I=E2=80=99ll be happy t=
o do it.<br clear=3D"none">
<br clear=3D"none">
I=E2=80=99m open to suggestions on how it can be than.<br clear=3D"none">
<br clear=3D"none">
Christian<br clear=3D"none">
<br clear=3D"none">
<br clear=3D"none">
<br clear=3D"none">
<br clear=3D"none">
&gt; I also<br clear=3D"none">
&gt; think that the world tour tends to have the unintended side-effect<br =
clear=3D"none">
&gt; of overemphasizing the importance of meetings to our process.<br clear=
=3D"none">
&gt;<br clear=3D"none">
&gt; Also, note that a large number of regulars opted to skip the meeting<b=
r clear=3D"none">
&gt; in Buenos Aires.&nbsp; Granted, there are those who might see that as<=
br clear=3D"none">
&gt; a benefit.<br clear=3D"none">
&gt;<br clear=3D"none">
&gt; Melinda<br clear=3D"none">
&gt;<br clear=3D"none">
<br clear=3D"none">
</blockquote></div><br clear=3D"none"></div></div></div></div><br><br></div=
> </div> </div>  </div></div></body></html>
------=_Part_2793945_1897585121.1461088986144--


From nobody Tue Apr 19 11:44:02 2016
Return-Path: <melinda.shore@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 8CB2A12D935 for <ietf@ietfa.amsl.com>; Tue, 19 Apr 2016 11:44:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 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, RCVD_IN_DNSWL_LOW=-0.7, 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 afhJb0HtvZPU for <ietf@ietfa.amsl.com>; Tue, 19 Apr 2016 11:43:57 -0700 (PDT)
Received: from mail-pa0-x236.google.com (mail-pa0-x236.google.com [IPv6:2607:f8b0:400e:c03::236]) (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 CEDC512D820 for <ietf@ietf.org>; Tue, 19 Apr 2016 11:43:57 -0700 (PDT)
Received: by mail-pa0-x236.google.com with SMTP id er2so9181068pad.3 for <ietf@ietf.org>; Tue, 19 Apr 2016 11:43:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding; bh=fbc4IR76lCnh5jVlzHV9+PiNI76yxkJB7j+xhVuKKUI=; b=Zk+DNMorFpkn3dIexW2VwR3546OfJHGtEDBdnG9blulgSres4AnuKi8/fvwcQ/ERkY dbderkJ0eD48fPYVF0VVuv4H2+olZ+atztxI0ZWNucjxjeBwBtmvioEJW6IGt0BIolKZ YoqdJGC1fbYseBd0GId2ya/8wYnDikmpvDBHRp5PzjG4lZUAYMcScgQL1SG3Whpnbw87 mt4QTs16BnA7+gjsBE9t6EZfdXBbcF1W28MY3IJ3F3ZL/DPBF+siK5LC+6Kpyp8jl55n anO70WkzE0q/WSBduBBhzru73VKAc+po8GHuHoHRPdEqF3D2sKO4WAG2GyFEWD1+/inB OZnQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=fbc4IR76lCnh5jVlzHV9+PiNI76yxkJB7j+xhVuKKUI=; b=FBllp+y9hhg0dbWuN+Q9Bmoec1EF6PYWeD8FUuJFlLaZpLnn0zUbKsFW/osR3mW3QU qNCodYWwBhNLaUs9FxHEwjvXKWRU/xHTt4dB7OAwSi+1Lq/5iTR0VIvHSFQ4BI8Pg9cU cqY6AwfGlzglGRwwXykfecM9LGBgUKt6aZAzYhRNtUERePP4+WYpav342UDMHzfblTrf +ig10vcADgTBBEYEetoZ0FhslyiWpylBXbQAL/MIIjGwhBtsazUL0W6gBf0wJX5Nxz0q 2cfB2+Gm97MYbPnGDQTVZOEH8NwuBl2Aj+E7D2ubVi4EEQDBnjHN/AoXPLb7aZMylYIz CQ/w==
X-Gm-Message-State: AOPr4FV+PH0OJX4JhUDLrtsow7u8J9z9Bdj4QDxczFEwYhzM2G2StZtzi8UV4H6NPlgUBQ==
X-Received: by 10.66.75.97 with SMTP id b1mr6183268paw.54.1461091437424; Tue, 19 Apr 2016 11:43:57 -0700 (PDT)
Received: from Melindas-MacBook-Pro.local (74-124-100-170-radius.dynamic.acsalaska.net. [74.124.100.170]) by smtp.googlemail.com with ESMTPSA id r191sm92567283pfr.36.2016.04.19.11.43.56 for <ietf@ietf.org> (version=TLSv1/SSLv3 cipher=OTHER); Tue, 19 Apr 2016 11:43:56 -0700 (PDT)
Subject: Re: Interim step on meetings site feedback for sites currently under active consideration
To: ietf@ietf.org
References: <CAPt1N1n+676sAWFLee3oUGUgnTNHh95yFgrsmyjB5VbSmF-=XQ@mail.gmail.com> <876171588.2793946.1461088986149.JavaMail.yahoo@mail.yahoo.com>
From: Melinda Shore <melinda.shore@gmail.com>
Message-ID: <57167C6C.50104@gmail.com>
Date: Tue, 19 Apr 2016 10:43:56 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:38.0) Gecko/20100101 Thunderbird/38.6.0
MIME-Version: 1.0
In-Reply-To: <876171588.2793946.1461088986149.JavaMail.yahoo@mail.yahoo.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/HOsQH9oTV3E-NpcD-0b4G81UjnA>
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: Tue, 19 Apr 2016 18:44:01 -0000

On 4/19/16 10:03 AM, nalini.elkins@insidethestack.com wrote:
> But, that is only what I know via personal information.  I don't know
> how to do this automatically.   I suspect that these newcomers are not
> likely to get funding to participate in Berlin.  But, we can get them to
> be active on email lists (as a start).

Either we are doing a terrible, terrible job making it
clear that you do not need to attend a meeting in person
to make meaningful contributions to the IETF's work, or
we're doing a fine job and for most part those who want
to be active participants already are and those who aren't
aren't interested.  I tend to think it's the former but that's
just a guess.

At any rate, inability to travel to Berlin should not in
any way be seen as a barrier to participation.

Melinda



From nobody Tue Apr 19 11:57:00 2016
Return-Path: <vinayakh@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 B28E912E48D for <ietf@ietfa.amsl.com>; Tue, 19 Apr 2016 11:56:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 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, RCVD_IN_DNSWL_LOW=-0.7, 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 oF4pZ8jNPyEv for <ietf@ietfa.amsl.com>; Tue, 19 Apr 2016 11:56:57 -0700 (PDT)
Received: from mail-wm0-x22f.google.com (mail-wm0-x22f.google.com [IPv6:2a00:1450:400c:c09::22f]) (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 E02BC12E48B for <ietf@ietf.org>; Tue, 19 Apr 2016 11:56:56 -0700 (PDT)
Received: by mail-wm0-x22f.google.com with SMTP id u206so45387540wme.1 for <ietf@ietf.org>; Tue, 19 Apr 2016 11:56:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=6gthE+LhrO//QSmvJkmW0RkVDE6m45DirPtlpLas35s=; b=gOE87Y7JBuQHvCi7WQlUjYUYSrGfGsOwCeXXSj4HyxAe7CHJg9mDOfZeoroyviqOBP WLpH78p7HVx21YCp9Dw4MMbPuOvcnFgkMZz6ukdsxm8QazszmOVtawM1xBz/fE8cR/t6 fCMcrccaGskkwixvX6MoRm2f+cutjqi0BYc7ta3DLq3GP6wb5WhhuNh04mAoi7AxlDkM gmK5cI9tVtuzNdB/p+v70fT7fyCEQjAeQfCu/U68eAZPgIvlR/61hW6W/gueVMnS/2nh Fb4zeTP7BwRTG1tcg5zlresd/9wZB1eBVzu3/igSGl51GPrEAVnPOiEjmv02591a1yJX 79uA==
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:date :message-id:subject:from:to:cc; bh=6gthE+LhrO//QSmvJkmW0RkVDE6m45DirPtlpLas35s=; b=RTq5Pjf7DQhQf3bmegSPnbCQ2Al4aoqXV6NsM4OoLqsCf3WgmhWOJruXLm3VFl4S2B A2B9EzwnsPTRCqScgXN7uEtiDFa4dxVLzr23nj5u+huTrAZL0cRdODnPvdd85IiPt9YV ekvI9I75Y88jlB9ZokvKWAJulqSkU5BVYWbYl82+vhAAajEm6zkxszI4Ra4XA0tJrUp+ QG8LDVP/crWw1ubWo6lV4Kd4EmrS7Co9zot6T8jl0t8dNVI9KA2eQK6SWBb2xPiTi5KR 7G9ZpCrZ9FeKaGB7TdUZD4wiTFnQP/e/lVOQfOMwd0ScyfSxZ1GOB0Naj8qP2cv9NrRT hp1w==
X-Gm-Message-State: AOPr4FXUaH0nqumz+MhJM9evXD4CAW8ED7kfAaRkArwaw6OOcvEF9I5SQvckw/CV3BESm0uwQDKzwv48qFWzKQ==
MIME-Version: 1.0
X-Received: by 10.28.107.13 with SMTP id g13mr5462095wmc.62.1461092215463; Tue, 19 Apr 2016 11:56:55 -0700 (PDT)
Received: by 10.194.133.99 with HTTP; Tue, 19 Apr 2016 11:56:55 -0700 (PDT)
In-Reply-To: <CAPt1N1n+676sAWFLee3oUGUgnTNHh95yFgrsmyjB5VbSmF-=XQ@mail.gmail.com>
References: <20160418161552.9368.65562.idtracker@ietfa.amsl.com> <8fb376e11631f9ddf73f9385ec5472c3.squirrel@www.trepanning.net> <57151C55.30206@gmail.com> <54D9A539-6409-4692-85F6-E4837E823AAE@gmail.com> <CAPt1N1n+676sAWFLee3oUGUgnTNHh95yFgrsmyjB5VbSmF-=XQ@mail.gmail.com>
Date: Wed, 20 Apr 2016 00:26:55 +0530
Message-ID: <CAKe6YvPGufULDN=SLbR8YZ-7-tUj-H18U4h4JTH7_S3UJKvRbw@mail.gmail.com>
Subject: Re: Interim step on meetings site feedback for sites currently under active consideration
From: Vinayak Hegde <vinayakh@gmail.com>
To: Ted Lemon <mellon@fugue.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/3FeN_rcyqO6udfyC2t1YuavD1oQ>
Cc: ietf <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: Tue, 19 Apr 2016 18:56:58 -0000

On Tue, Apr 19, 2016 at 11:25 PM, Ted Lemon <mellon@fugue.com> wrote:
> It should be pretty easy for the IAD to measure this by comparing the list
> of newcomers in Argentina to the list of participants in Berlin, for
> example.   I am fairly sure that they already do this, and possibly may even
> have made presentations about it from time to time at the plenary... :)

Hi Ted,

I am not picking on you but this idea is flawed at many levels.
Fundamentally we need to answer
1. What does a (meaningful ?) contribution mean ?
2. How does that relate to active participation ? Are there thresholds
or is it a continuum ? Does I mean writing a draft or is reviewing
drafts, taking minutes and hacking on code to check real world
implementation good enough.

The answers are more nuanced and varied than one might guess at first
glance. At IETF 95 in BA several long-time contributors participated
remotely. I am sure that they would take offense to this idea if they
have contributed remotely and on the mailing lists.

Just to emphasize, several WG chairs also do not attend every meeting.
Are they active ? I think there needs to be less emphasis on physical
meetings overall (FWIW I think we are already moving in that direction
quite rapidly. But at the same time F2F interaction cannot be done
away with completely IMHO and is also not going away.)

-- Vinayak


From nobody Tue Apr 19 11:59:33 2016
Return-Path: <mellon@fugue.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 232BA12D647 for <ietf@ietfa.amsl.com>; Tue, 19 Apr 2016 11:59:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.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 lK8SwC_hQ58v for <ietf@ietfa.amsl.com>; Tue, 19 Apr 2016 11:59:30 -0700 (PDT)
Received: from mail-ig0-x236.google.com (mail-ig0-x236.google.com [IPv6:2607:f8b0:4001:c05::236]) (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 259E312D173 for <ietf@ietf.org>; Tue, 19 Apr 2016 11:59:30 -0700 (PDT)
Received: by mail-ig0-x236.google.com with SMTP id g8so26368191igr.0 for <ietf@ietf.org>; Tue, 19 Apr 2016 11:59:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=ykNI5ejZah+aruDn+SGohxE9fKAwhtaY3pxkaeprbB4=; b=R6LqXWAZPKC2mvjrtJn6TmHF3IOB1ILnVujrIDZFqJxA8iMobd1W3klxsxnork5qPg uXl6kZQW3k7+KuJoPibPlkZFkyVQE32buMKyFLQnCGvaGoXUcOgCCJPDjN7cC8OsuVbi BrFT3YgIgD32OW+SEzgL8iFmKJeAP7/VRcP0Q4R63Mb/XAeCsK6spd1yPpRPtz2utdRz QMdW8pvYzrBBdviU2vp+YseDD1pDW4HgD/lvdMpSMIYpZNIdBSssI68DopXZ6Tgbk3d1 NDszVb71vCvBga7lPOBsdk6eWZDcJTIZZHbEh6IBjnw47zOQO53gRm/Twvtp3wZWfJDM 57iw==
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=ykNI5ejZah+aruDn+SGohxE9fKAwhtaY3pxkaeprbB4=; b=Ce6uq6rnZs6J1+P+J0kWS/GJ8Eyj4r6qasvw4FtZhkPmNR/Ir7RDxameMlQ5ACA68x a4vLwwEpnbKEUj7y1N5BV1SagTbPA//tYi6N9YEGAnhTILGJscIuYWu13EWbukA2bAGx QAC+5dV2cFe+RmWNKMRzstKOJTjSmWd4rFUksQdeCXSyrNAzur3o96eSTW3Satbc1LF/ 4lh0/bipR6hH6yhMdIB53T1VVPP+JLD/CJz63VSZbNED1dMiaNd85ZInlqPymmSfs2wd dMx7wver2j4A8SBfXSaOPcJinEbGnYN+tLv8IAsCMjRNgDCUGJBsW6UfLGFru0LP8fZJ yOWQ==
X-Gm-Message-State: AOPr4FW1192hndHkKzuPDu64/6tknDgDiRvrz7DQWo7oeLZHhg09WJW6Zm56mPDhrvRbgq3u8L4BwkoNlVnyAg==
X-Received: by 10.50.30.101 with SMTP id r5mr27107851igh.2.1461092369461; Tue, 19 Apr 2016 11:59:29 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.64.144.225 with HTTP; Tue, 19 Apr 2016 11:58:50 -0700 (PDT)
X-Originating-IP: [71.233.41.235]
In-Reply-To: <CAKe6YvPGufULDN=SLbR8YZ-7-tUj-H18U4h4JTH7_S3UJKvRbw@mail.gmail.com>
References: <20160418161552.9368.65562.idtracker@ietfa.amsl.com> <8fb376e11631f9ddf73f9385ec5472c3.squirrel@www.trepanning.net> <57151C55.30206@gmail.com> <54D9A539-6409-4692-85F6-E4837E823AAE@gmail.com> <CAPt1N1n+676sAWFLee3oUGUgnTNHh95yFgrsmyjB5VbSmF-=XQ@mail.gmail.com> <CAKe6YvPGufULDN=SLbR8YZ-7-tUj-H18U4h4JTH7_S3UJKvRbw@mail.gmail.com>
From: Ted Lemon <mellon@fugue.com>
Date: Tue, 19 Apr 2016 14:58:50 -0400
Message-ID: <CAPt1N1k+tbGBg=Pz1EikFzG6ArpXhi5=dnc+NkpprWX==UnF2A@mail.gmail.com>
Subject: Re: Interim step on meetings site feedback for sites currently under active consideration
To: Vinayak Hegde <vinayakh@gmail.com>
Content-Type: multipart/alternative; boundary=047d7bdca97eab07f10530db1329
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/5SK5ApQCwT7bkBUfdrmv_G485QM>
Cc: ietf <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: Tue, 19 Apr 2016 18:59:32 -0000

--047d7bdca97eab07f10530db1329
Content-Type: text/plain; charset=UTF-8

You're right, I failed to account for remote participation.   In principal,
however, the IAD can account for this too, both by looking at remote
attendance, assuming that we start collecting better statistics, and by
looking at participation on mailing lists and in the writing and reviewing
of drafts.   All of this data is available.

On Tue, Apr 19, 2016 at 2:56 PM, Vinayak Hegde <vinayakh@gmail.com> wrote:

> On Tue, Apr 19, 2016 at 11:25 PM, Ted Lemon <mellon@fugue.com> wrote:
> > It should be pretty easy for the IAD to measure this by comparing the
> list
> > of newcomers in Argentina to the list of participants in Berlin, for
> > example.   I am fairly sure that they already do this, and possibly may
> even
> > have made presentations about it from time to time at the plenary... :)
>
> Hi Ted,
>
> I am not picking on you but this idea is flawed at many levels.
> Fundamentally we need to answer
> 1. What does a (meaningful ?) contribution mean ?
> 2. How does that relate to active participation ? Are there thresholds
> or is it a continuum ? Does I mean writing a draft or is reviewing
> drafts, taking minutes and hacking on code to check real world
> implementation good enough.
>
> The answers are more nuanced and varied than one might guess at first
> glance. At IETF 95 in BA several long-time contributors participated
> remotely. I am sure that they would take offense to this idea if they
> have contributed remotely and on the mailing lists.
>
> Just to emphasize, several WG chairs also do not attend every meeting.
> Are they active ? I think there needs to be less emphasis on physical
> meetings overall (FWIW I think we are already moving in that direction
> quite rapidly. But at the same time F2F interaction cannot be done
> away with completely IMHO and is also not going away.)
>
> -- Vinayak
>

--047d7bdca97eab07f10530db1329
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">You&#39;re right, I failed to account for remote participa=
tion. =C2=A0 In principal, however, the IAD can account for this too, both =
by looking at remote attendance, assuming that we start collecting better s=
tatistics, and by looking at participation on mailing lists and in the writ=
ing and reviewing of drafts. =C2=A0 All of this data is available.</div><di=
v class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Tue, Apr 19, 2016=
 at 2:56 PM, Vinayak Hegde <span dir=3D"ltr">&lt;<a href=3D"mailto:vinayakh=
@gmail.com" target=3D"_blank">vinayakh@gmail.com</a>&gt;</span> wrote:<br><=
blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px=
 #ccc solid;padding-left:1ex"><span class=3D"">On Tue, Apr 19, 2016 at 11:2=
5 PM, Ted Lemon &lt;<a href=3D"mailto:mellon@fugue.com">mellon@fugue.com</a=
>&gt; wrote:<br>
&gt; It should be pretty easy for the IAD to measure this by comparing the =
list<br>
&gt; of newcomers in Argentina to the list of participants in Berlin, for<b=
r>
&gt; example.=C2=A0 =C2=A0I am fairly sure that they already do this, and p=
ossibly may even<br>
&gt; have made presentations about it from time to time at the plenary... :=
)<br>
<br>
</span>Hi Ted,<br>
<br>
I am not picking on you but this idea is flawed at many levels.<br>
Fundamentally we need to answer<br>
1. What does a (meaningful ?) contribution mean ?<br>
2. How does that relate to active participation ? Are there thresholds<br>
or is it a continuum ? Does I mean writing a draft or is reviewing<br>
drafts, taking minutes and hacking on code to check real world<br>
implementation good enough.<br>
<br>
The answers are more nuanced and varied than one might guess at first<br>
glance. At IETF 95 in BA several long-time contributors participated<br>
remotely. I am sure that they would take offense to this idea if they<br>
have contributed remotely and on the mailing lists.<br>
<br>
Just to emphasize, several WG chairs also do not attend every meeting.<br>
Are they active ? I think there needs to be less emphasis on physical<br>
meetings overall (FWIW I think we are already moving in that direction<br>
quite rapidly. But at the same time F2F interaction cannot be done<br>
away with completely IMHO and is also not going away.)<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
-- Vinayak<br>
</font></span></blockquote></div><br></div>

--047d7bdca97eab07f10530db1329--


From nobody Tue Apr 19 12:08:12 2016
Return-Path: <stephen.farrell@cs.tcd.ie>
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 BF86B12E4B8 for <ietf@ietfa.amsl.com>; Tue, 19 Apr 2016 12:08:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.297
X-Spam-Level: 
X-Spam-Status: No, score=-5.297 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.996, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cs.tcd.ie
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 4n72D11U1phz for <ietf@ietfa.amsl.com>; Tue, 19 Apr 2016 12:08:09 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6298A12E4B9 for <ietf@ietf.org>; Tue, 19 Apr 2016 12:08:09 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 29416BE54; Tue, 19 Apr 2016 20:08:08 +0100 (IST)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id waN5RjvvZASO; Tue, 19 Apr 2016 20:08:06 +0100 (IST)
Received: from [10.87.49.100] (unknown [86.46.28.69]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 147CEBE49; Tue, 19 Apr 2016 20:08:06 +0100 (IST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; s=mail; t=1461092886; bh=4ZofM/6yXxYemYcK8v1ATY4CG2I3kN5hcDFBRv00VLo=; h=Subject:To:References:From:Date:In-Reply-To:From; b=FC174FZTCmmU0zw1IrFRUTodnJVwa7nN+KA8u7Hn2teCmVpyt54Fdjrsx4A8G7LrJ uZZ+WWQqwI/4A2LUnNtpMdsDSvNziZ4bWOD2s+Wdwbd7xaLQyM+jXmZ4JQWi0pHDfT 1NwSJpOsK4DQmWGgAtQfqJCRUxnCHNS1XyWT7qUc=
Subject: f2f and mailing list participation - a question for "newer" participants (Was: Re: Interim step on meetings site feedback for sites currently under active consideration)
To: Melinda Shore <melinda.shore@gmail.com>, ietf@ietf.org
References: <CAPt1N1n+676sAWFLee3oUGUgnTNHh95yFgrsmyjB5VbSmF-=XQ@mail.gmail.com> <876171588.2793946.1461088986149.JavaMail.yahoo@mail.yahoo.com> <57167C6C.50104@gmail.com>
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Openpgp: id=D66EA7906F0B897FB2E97D582F3C8736805F8DA2; url=
Message-ID: <57168215.4080107@cs.tcd.ie>
Date: Tue, 19 Apr 2016 20:08:05 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0
MIME-Version: 1.0
In-Reply-To: <57167C6C.50104@gmail.com>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha-256; boundary="------------ms020509040800030600060608"
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/TkGNfLZ80xFN25LUuFRfGfs6UwY>
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: Tue, 19 Apr 2016 19:08:11 -0000

This is a cryptographically signed message in MIME format.

--------------ms020509040800030600060608
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


(The topic seems to have wandered enough to warrant a change of
subject, and apologies for extending what has become a frequently
replayed thread but I've a question at the end aimed at some folks
who maybe don't post here so much...)

On 19/04/16 19:43, Melinda Shore wrote:
>=20
>=20
> At any rate, inability to travel to Berlin should not in
> any way be seen as a barrier to participation.

I don't think we ought pretend that mailing list participation
isn't inevitably enhanced via in-person connections.

Yes, we can participate via mailing lists. And we need to do
better in encouraging folks to do that. And we need to do that
over and over so that newer and older participants really get it.

But having been to a few f2f meetings IMO really does make
it far easier to get stuff done via mailing lists and otherwise,
e.g. on jabber or audio calls. I further figure that's not
down to how the IETF works, but is because we're talking about
humans.

So I can fully understand how folks who've not (yet:-) been
participating for that long would find attending a f2f meeting
makes a HUGE difference to them.

I can also see how the same sets of folks might have different
views on our current remote access setup - when I had to be
remote for a meeting (Hawaii) I really found it much better than
I had expected, really only the TZ was a killer. But, and it's
a big BUT, I recognised loads of voices in audio and could
IM people in the room to ask stuff, so I suspect the experience
is nowhere near as satisfactory for newer participants.

So, I'd be really interested in hearing from people who've
been participating a bit for a while and who'd consider themselves
as "newer participants" (define that yourself however you want)...

If you've been to a f2f meeting what difference did that make
to how you participate via mailing lists and remote tools?

or

If you've not been to a f2f meeting, what's your experience of
participation via mailing lists and (especially) remote tools?

Cheers,
S.

PS: If folks prefer to answer offlist feel free to do that and
I'll summarise back to the list with whatever level of nymity
you say you want.

PPS: This isn't meant to be scientific nor a good survey, I'm
just interested:-) If there's some or no reaction that might
help with some proper survey stuff in future.





--------------ms020509040800030600060608
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIAGCSqGSIb3DQEHAqCAMIACAQExDzANBglghkgBZQMEAgEFADCABgkqhkiG9w0BBwEAAKCC
CvIwggUIMIID8KADAgECAhBPzaE7pzYviUJyhmHTFBdnMA0GCSqGSIb3DQEBCwUAMHUxCzAJ
BgNVBAYTAklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSkwJwYDVQQLEyBTdGFydENvbSBD
ZXJ0aWZpY2F0aW9uIEF1dGhvcml0eTEjMCEGA1UEAxMaU3RhcnRDb20gQ2xhc3MgMSBDbGll
bnQgQ0EwHhcNMTYwMjA5MDkyODE1WhcNMTcwMjA5MDkyODE1WjBOMSIwIAYDVQQDDBlzdGVw
aGVuLmZhcnJlbGxAY3MudGNkLmllMSgwJgYJKoZIhvcNAQkBFhlzdGVwaGVuLmZhcnJlbGxA
Y3MudGNkLmllMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAtuC0rYze/2JinSra
C9F2RjGdQZjNALLcW9C3WKTwYII3wBslobmHuPEYE5JaGItmzuKnAW619R1rD/kfoNWC19N3
rBZ6UX9Cmb9D9exCwYIwVuSwjrCQWGxgCtNQTrwKzCCpI790GRiMTvxvO7UmzmBrCaBLiZW5
R0fBjK5Yn6hUhAzGBkNbkIEL28cLJqH0yVz7Kl92OlzrQqTPEts5m6cDnNdY/ADfeAX18c1r
dxZqcAxhLotrCqgsVA4ilbQDMMXGTLlB5TP35HeWZuGBU7xu003rLcFLdOkD8xvpJoYZy9Kt
3oABXPS5yqtMK+XCNdqmMn+4mOtLwQSMmPCSiQIDAQABo4IBuTCCAbUwCwYDVR0PBAQDAgSw
MB0GA1UdJQQWMBQGCCsGAQUFBwMCBggrBgEFBQcDBDAJBgNVHRMEAjAAMB0GA1UdDgQWBBQJ
QhvwQ5Fl372Z6xqo6fdn8XejTTAfBgNVHSMEGDAWgBQkgWw5Yb5JD4+3G0YrySi1J0htaDBv
BggrBgEFBQcBAQRjMGEwJAYIKwYBBQUHMAGGGGh0dHA6Ly9vY3NwLnN0YXJ0c3NsLmNvbTA5
BggrBgEFBQcwAoYtaHR0cDovL2FpYS5zdGFydHNzbC5jb20vY2VydHMvc2NhLmNsaWVudDEu
Y3J0MDgGA1UdHwQxMC8wLaAroCmGJ2h0dHA6Ly9jcmwuc3RhcnRzc2wuY29tL3NjYS1jbGll
bnQxLmNybDAkBgNVHREEHTAbgRlzdGVwaGVuLmZhcnJlbGxAY3MudGNkLmllMCMGA1UdEgQc
MBqGGGh0dHA6Ly93d3cuc3RhcnRzc2wuY29tLzBGBgNVHSAEPzA9MDsGCysGAQQBgbU3AQIE
MCwwKgYIKwYBBQUHAgEWHmh0dHA6Ly93d3cuc3RhcnRzc2wuY29tL3BvbGljeTANBgkqhkiG
9w0BAQsFAAOCAQEArzrSv2C8PlBBmGuiGrzm2Wma46/KHtXmZYS0bsd43pM66Pc/MsqPE0HD
C1GzMFfwB6BfkJn8ijNSIhlgj898WzjvnpM/SO8KStjlB8719ig/xKISrOl5mX55XbFlQtX9
U6MrqRgbDIATxhD9IDr+ryvovDzChqgQj7mt2jYr4mdlRjsjod3H1VY6XglRmaaNGZfsCARM
aE/TU5SXIiqauwt5KxNGYAY67QkOBs7O1FkSXpTk7+1MmzJMF4nP8QQ5n8vhVNseF+/Wm7ai
9mtnrkLbaznMsy/ULo/C2yuLUWTbZZbf4EKNmVdme6tUDgYkFjAFOblfA7W1fSPiQGagYzCC
BeIwggPKoAMCAQICEGunin0K14jWUQr5WeTntOEwDQYJKoZIhvcNAQELBQAwfTELMAkGA1UE
BhMCSUwxFjAUBgNVBAoTDVN0YXJ0Q29tIEx0ZC4xKzApBgNVBAsTIlNlY3VyZSBEaWdpdGFs
IENlcnRpZmljYXRlIFNpZ25pbmcxKTAnBgNVBAMTIFN0YXJ0Q29tIENlcnRpZmljYXRpb24g
QXV0aG9yaXR5MB4XDTE1MTIxNjAxMDAwNVoXDTMwMTIxNjAxMDAwNVowdTELMAkGA1UEBhMC
SUwxFjAUBgNVBAoTDVN0YXJ0Q29tIEx0ZC4xKTAnBgNVBAsTIFN0YXJ0Q29tIENlcnRpZmlj
YXRpb24gQXV0aG9yaXR5MSMwIQYDVQQDExpTdGFydENvbSBDbGFzcyAxIENsaWVudCBDQTCC
ASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAL192vfDon2D9luC/dtbX64eG3XAtRmv
mCSsu1d52DXsCR58zJQbCtB2/A5uFqNxWacpXGGtTCRk9dEDBlmixEd8QiLkUfvHpJX/xKnm
VkS6Iye8wUbYzMsDzgnpazlPg19dnSqfhM+Cevdfa89VLnUztRr2cgmCfyO9Otrh7LJDPG+4
D8ZnAqDtVB8MKYJL6QgKyVhhaBc4y3bGWxKyXEtx7QIZZGxPwSkzK3WIN+VKNdkiwTubW5PI
dopmykwvIjLPqbJK7yPwFZYekKE015OsW6FV+s4DIM8UlVS8pkIsoGGJtMuWjLL4tq2hYQuu
N0jhrxK1ljz50hH23gA9cbMCAwEAAaOCAWQwggFgMA4GA1UdDwEB/wQEAwIBBjAdBgNVHSUE
FjAUBggrBgEFBQcDAgYIKwYBBQUHAwQwEgYDVR0TAQH/BAgwBgEB/wIBADAyBgNVHR8EKzAp
MCegJaAjhiFodHRwOi8vY3JsLnN0YXJ0c3NsLmNvbS9zZnNjYS5jcmwwZgYIKwYBBQUHAQEE
WjBYMCQGCCsGAQUFBzABhhhodHRwOi8vb2NzcC5zdGFydHNzbC5jb20wMAYIKwYBBQUHMAKG
JGh0dHA6Ly9haWEuc3RhcnRzc2wuY29tL2NlcnRzL2NhLmNydDAdBgNVHQ4EFgQUJIFsOWG+
SQ+PtxtGK8kotSdIbWgwHwYDVR0jBBgwFoAUTgvvGqRAW6UXaYcwyjRoQ9BBrvIwPwYDVR0g
BDgwNjA0BgRVHSAAMCwwKgYIKwYBBQUHAgEWHmh0dHA6Ly93d3cuc3RhcnRzc2wuY29tL3Bv
bGljeTANBgkqhkiG9w0BAQsFAAOCAgEAi+P3h+wBi4StDwECW5zhIycjBL008HACblIf26HY
0JdOruKbrWDsXUsiI0j/7Crft9S5oxvPiDtVqspBOB/y5uzSns1lZwh7sG96bYBZpcGzGxpF
NjDmQbcM3yl3WFIRS4WhNrsOY14V7y2IrUGsvetsD+bjyOngCIVeC/GmsmtbuLOzJ606tEc9
uRbhjTu/b0x2Fo+/e7UkQvKzNeo7OMhijixaULyINBfCBJb+e29bLafgu6JqjOUJ9eXXj20p
6q/CW+uVrZiSW57+q5an2P2i7hP85jQJcy5j4HzA0rSiF3YPhKGAWUxKPMAVGgcYoXzWydOv
Z3UDsTDTagXpRDIKQLZo02wrlxY6iMFqvlzsemVf1odhQJmi7Eh5TbxI40kDGcBOBHhwnaOu
mZhLP+SWJQnjpLpSlUOj95uf1zo9oz9e0NgIJoz/tdfrBzez76xtDsK0KfUDHt1/q59BvDI7
RX6gVr0fQoCyMczNzCTcRXYHY0tq2J0oT+bsb6sH2b4WVWAiJKnSYaWDjdA70qHX4mq9MIjO
/ZskmSY8wtAk24orAc0vwXgYanqNsBX5Yv4sN4Z9VyrwMdLcusP7HJgRdAGKpkR2I9U4zEsN
JQJewM7S4Jalo1DyPrLpL2nTET8ZrSl5Utp1UeGp/2deoprGevfnxWB+vHNQiu85o6MxggPM
MIIDyAIBATCBiTB1MQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRDb20gTHRkLjEpMCcG
A1UECxMgU3RhcnRDb20gQ2VydGlmaWNhdGlvbiBBdXRob3JpdHkxIzAhBgNVBAMTGlN0YXJ0
Q29tIENsYXNzIDEgQ2xpZW50IENBAhBPzaE7pzYviUJyhmHTFBdnMA0GCWCGSAFlAwQCAQUA
oIICEzAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0xNjA0MTkx
OTA4MDVaMC8GCSqGSIb3DQEJBDEiBCD2fG14RLNRBEqpgZ4yaXCUBXtp41sS9bVMMg6IdkLr
dTBsBgkqhkiG9w0BCQ8xXzBdMAsGCWCGSAFlAwQBKjALBglghkgBZQMEAQIwCgYIKoZIhvcN
AwcwDgYIKoZIhvcNAwICAgCAMA0GCCqGSIb3DQMCAgFAMAcGBSsOAwIHMA0GCCqGSIb3DQMC
AgEoMIGaBgkrBgEEAYI3EAQxgYwwgYkwdTELMAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0
Q29tIEx0ZC4xKTAnBgNVBAsTIFN0YXJ0Q29tIENlcnRpZmljYXRpb24gQXV0aG9yaXR5MSMw
IQYDVQQDExpTdGFydENvbSBDbGFzcyAxIENsaWVudCBDQQIQT82hO6c2L4lCcoZh0xQXZzCB
nAYLKoZIhvcNAQkQAgsxgYyggYkwdTELMAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0Q29t
IEx0ZC4xKTAnBgNVBAsTIFN0YXJ0Q29tIENlcnRpZmljYXRpb24gQXV0aG9yaXR5MSMwIQYD
VQQDExpTdGFydENvbSBDbGFzcyAxIENsaWVudCBDQQIQT82hO6c2L4lCcoZh0xQXZzANBgkq
hkiG9w0BAQEFAASCAQCJEj8JzGVMwYsob3b8sZRlNjrznXGNPtz0f6TuSZCfQyqYHo4rsown
NulqjWriTjop78sXFZzTtSDigqTxgkHCEFZhpJECSwqBsl6MPDFu8YZz3Zeb32TH8X8km29t
Q7cVROJz0LPQn5INvP+569BQEq8qPkeX4xot/9yPDiWGhBYIzlsQEeZ3l/Q0gbD506O3SPEs
xIQ+ZWWplmiBbA4AmvLL4tGiJKR+h/mp3epJAuIrWUsAX+Yo8MdbhSIEHoPs5hk7DTN+uTJn
sX98lP4a2vNZ55SOO9oh3yU+U39EK2wXJTSrMUSFK+dAwws2QifzwEoSVwhOF4vnrM3OmV+G
AAAAAAAA
--------------ms020509040800030600060608--


From nobody Tue Apr 19 12:35:43 2016
Return-Path: <christian.oflaherty@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 6815412E635 for <ietf@ietfa.amsl.com>; Tue, 19 Apr 2016 12:35:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.699
X-Spam-Level: 
X-Spam-Status: No, score=-1.699 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, FREEMAIL_REPLY=1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=no 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 C6XDBlEHK_Ss for <ietf@ietfa.amsl.com>; Tue, 19 Apr 2016 12:35:38 -0700 (PDT)
Received: from mail-vk0-x22d.google.com (mail-vk0-x22d.google.com [IPv6:2607:f8b0:400c:c05::22d]) (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 72A2E12E596 for <ietf@ietf.org>; Tue, 19 Apr 2016 12:35:38 -0700 (PDT)
Received: by mail-vk0-x22d.google.com with SMTP id t129so32631701vkg.2 for <ietf@ietf.org>; Tue, 19 Apr 2016 12:35:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=subject:mime-version:from:in-reply-to:date:cc:message-id:references :to; bh=yQ7EBdKP+S4xMBAnHV9gC9RhdiihiL+PdLuVmit7HTs=; b=zCyf6uSiuZTVuGYYv1Xh8Sxaq66Eqnf5Uip+8Dnt+Whxdsec/AcHj3Uumx3UTX8je0 pNIV3UCX1KzvEBgDL3kRi1E21vwJTKtzyEEOswEyztZ+RLk2ibLdny32nrLvY5dQFHDU S/KaDBc4GsA8mM0v1RyuQiN2YgfGQphurHyDIJcPLWMIK1RFbJnsmUp/kDxG0U/9LoEt OuNOfnheWOgt4R2qhm0ld/XWjF+LPo8NkaR2XOoGmrOvJykDOuMfbomVYOX89ruQ5PPq TVH4KYOsQ6/cmXYbIqlqT6x+yM4OcdK9KFt58lYQBQYiA5xEYG4Z1Z4x7HLhr5cKPga+ +bWA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:mime-version:from:in-reply-to:date:cc :message-id:references:to; bh=yQ7EBdKP+S4xMBAnHV9gC9RhdiihiL+PdLuVmit7HTs=; b=dpQyD5SPSnkEYxTVSNjUaQ0hkkYJLx2Fwuofa8gdf2rcEwmgPXWkrMqweThhFrMehh 2pWmliCX86JSdn8JyP5F7helbJD6UFwKCAJwiwU8f4DUV6EzbweRZQ1LtcDMCCMvu7/J 2YEhJ2jaTUPSWGMTGtLoMu8T8oUDD3WHODNDNdbWFOxwQmZ1WdwylflB4SesR5ImkhMN HjQX7K1rZLWSNn84H5ENyyyt3pI3Q5Hl+iI+I9EWUtzf6hZcKQHYbZbiw37KLipEVDig NBgUKZk8j4h5YPr4NCIOA1joh0/+MlgV8gNtnUXeGR8YBCj6NxXDU4mVWc3h3lyKwgsL gHFg==
X-Gm-Message-State: AOPr4FU962OkS5FLIbaDjFR/At4dn4DjCgFTuABFdTXICmms4hDeTsMPVA5nort0QQrh+Q==
X-Received: by 10.176.1.5 with SMTP id 5mr2602613uak.72.1461094537556; Tue, 19 Apr 2016 12:35:37 -0700 (PDT)
Received: from [10.0.1.13] (r167-61-127-90.dialup.adsl.anteldata.net.uy. [167.61.127.90]) by smtp.gmail.com with ESMTPSA id 37sm11215460ual.21.2016.04.19.12.35.28 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Tue, 19 Apr 2016 12:35:36 -0700 (PDT)
Subject: Re: Interim step on meetings site feedback for sites currently under active consideration
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Content-Type: multipart/alternative; boundary="Apple-Mail=_9E4F89C6-07A7-467C-BB13-66FDE59055A0"
From: Christian O'Flaherty <christian.oflaherty@gmail.com>
In-Reply-To: <CAPt1N1n+676sAWFLee3oUGUgnTNHh95yFgrsmyjB5VbSmF-=XQ@mail.gmail.com>
Date: Tue, 19 Apr 2016 16:35:15 -0300
Message-Id: <9BC149F0-83E7-44A8-AE04-89C3FDC15693@gmail.com>
References: <20160418161552.9368.65562.idtracker@ietfa.amsl.com> <8fb376e11631f9ddf73f9385ec5472c3.squirrel@www.trepanning.net> <57151C55.30206@gmail.com> <54D9A539-6409-4692-85F6-E4837E823AAE@gmail.com> <CAPt1N1n+676sAWFLee3oUGUgnTNHh95yFgrsmyjB5VbSmF-=XQ@mail.gmail.com>
To: Ted Lemon <mellon@fugue.com>
X-Mailer: Apple Mail (2.3124)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/y_pZHjIiIc9Z908uTQIyqO5cdKE>
Cc: ietf <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: Tue, 19 Apr 2016 19:35:42 -0000

--Apple-Mail=_9E4F89C6-07A7-467C-BB13-66FDE59055A0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8


> On Apr 19, 2016, at 2:55 PM, Ted Lemon <mellon@fugue.com> wrote:
>=20
> It should be pretty easy for the IAD to measure this by comparing the =
list of newcomers in Argentina to the list of participants in Berlin, =
for example. =20

But I was interested in addressing this part:

>  I'm very hopeful that some of the
> > South Americans who attended their first IETF meeting because
> > it was held in Buenos Aires will continue to participate (as in:
> > bring in work and participate in ongoing work, and not as in: sit
> > in meetings)


that would be, for example, WG mailing list contributions from Latin =
America (or at least subscriptions since IETF95) .

it=E2=80=99s very difficult to measure=E2=80=A6 but I=E2=80=99m open to =
suggestions.=20

Christian


> I am fairly sure that they already do this, and possibly may even have =
made presentations about it from time to time at the plenary... :)
>=20
> On Tue, Apr 19, 2016 at 1:36 PM, Christian O'Flaherty =
<christian.oflaherty@gmail.com <mailto:christian.oflaherty@gmail.com>> =
wrote:
>=20
> > On Apr 18, 2016, at 2:41 PM, Melinda Shore <melinda.shore@gmail.com =
<mailto:melinda.shore@gmail.com>> wrote:
> >
> > On 4/18/16 9:09 AM, Dan Harkins wrote:
> >> But
> >> I think these issues should be balanced with the overall benefit
> >> that the IETF World Tour provides.
> >
> > As I've said repeatedly, I don't think the world tour actually
> > does bring much benefit.  I'm very hopeful that some of the
> > South Americans who attended their first IETF meeting because
> > it was held in Buenos Aires will continue to participate (as in:
> > bring in work and participate in ongoing work, and not as in: sit
> > in meetings) but historically that has not been the case.
>=20
>=20
> BTW=E2=80=A6 if there=E2=80=99s a way to keep track and measure that =
additional active participation from Latin America I=E2=80=99ll be happy =
to do it.
>=20
> I=E2=80=99m open to suggestions on how it can be than.
>=20
> Christian
>=20
>=20
>=20
>=20
> > I also
> > think that the world tour tends to have the unintended side-effect
> > of overemphasizing the importance of meetings to our process.
> >
> > Also, note that a large number of regulars opted to skip the meeting
> > in Buenos Aires.  Granted, there are those who might see that as
> > a benefit.
> >
> > Melinda
> >
>=20
>=20


--Apple-Mail=_9E4F89C6-07A7-467C-BB13-66FDE59055A0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D""><br class=3D""><div><blockquote type=3D"cite" class=3D""><div =
class=3D"">On Apr 19, 2016, at 2:55 PM, Ted Lemon &lt;<a =
href=3D"mailto:mellon@fugue.com" class=3D"">mellon@fugue.com</a>&gt; =
wrote:</div><br class=3D"Apple-interchange-newline"><div class=3D""><div =
dir=3D"ltr" class=3D"">It should be pretty easy for the IAD to measure =
this by comparing the list of newcomers in Argentina to the list of =
participants in Berlin, for example. =
&nbsp;</div></div></blockquote><div><br class=3D""></div><div>But I was =
interested in addressing this part:</div><div><br =
class=3D""></div><div><blockquote type=3D"cite" class=3D""><div =
class=3D"gmail_extra"><div class=3D"gmail_quote"><blockquote =
class=3D"gmail_quote" style=3D"margin: 0px 0px 0px 0.8ex; =
border-left-width: 1px; border-left-color: rgb(204, 204, 204); =
border-left-style: solid; padding-left: 1ex;"><span class=3D"">&nbsp;I'm =
very hopeful that some of the<br class=3D"">&gt; South Americans who =
attended their first IETF meeting because<br class=3D"">&gt; it was held =
in Buenos Aires will continue to participate (as in:<br class=3D"">&gt; =
bring in work and participate in ongoing work, and not as in: sit<br =
class=3D"">&gt; in =
meetings)</span></blockquote></div></div></blockquote></div><div><br =
class=3D""></div><div>that would be, for example, WG mailing list =
contributions from Latin America (or at least subscriptions since =
IETF95) .</div><div><br class=3D""></div><div>it=E2=80=99s very =
difficult to measure=E2=80=A6 but I=E2=80=99m open to =
suggestions.&nbsp;</div><div><br =
class=3D""></div><div>Christian</div><div><br class=3D""></div><br =
class=3D""><blockquote type=3D"cite" class=3D""><div class=3D""><div =
dir=3D"ltr" class=3D""> I am fairly sure that they already do this, and =
possibly may even have made presentations about it from time to time at =
the plenary... :)</div><div class=3D"gmail_extra"><br class=3D""><div =
class=3D"gmail_quote">On Tue, Apr 19, 2016 at 1:36 PM, Christian =
O'Flaherty <span dir=3D"ltr" class=3D"">&lt;<a =
href=3D"mailto:christian.oflaherty@gmail.com" target=3D"_blank" =
class=3D"">christian.oflaherty@gmail.com</a>&gt;</span> wrote:<br =
class=3D""><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 =
.8ex;border-left:1px #ccc solid;padding-left:1ex"><br class=3D"">
&gt; On Apr 18, 2016, at 2:41 PM, Melinda Shore &lt;<a =
href=3D"mailto:melinda.shore@gmail.com" =
class=3D"">melinda.shore@gmail.com</a>&gt; wrote:<br class=3D"">
<span class=3D"">&gt;<br class=3D"">
&gt; On 4/18/16 9:09 AM, Dan Harkins wrote:<br class=3D"">
&gt;&gt; But<br class=3D"">
&gt;&gt; I think these issues should be balanced with the overall =
benefit<br class=3D"">
&gt;&gt; that the IETF World Tour provides.<br class=3D"">
&gt;<br class=3D"">
&gt; As I've said repeatedly, I don't think the world tour actually<br =
class=3D"">
&gt; does bring much benefit.&nbsp; I'm very hopeful that some of the<br =
class=3D"">
&gt; South Americans who attended their first IETF meeting because<br =
class=3D"">
&gt; it was held in Buenos Aires will continue to participate (as in:<br =
class=3D"">
&gt; bring in work and participate in ongoing work, and not as in: =
sit<br class=3D"">
&gt; in meetings) but historically that has not been the case.<br =
class=3D"">
<br class=3D"">
<br class=3D"">
</span>BTW=E2=80=A6 if there=E2=80=99s a way to keep track and measure =
that additional active participation from Latin America I=E2=80=99ll be =
happy to do it.<br class=3D"">
<br class=3D"">
I=E2=80=99m open to suggestions on how it can be than.<br class=3D"">
<br class=3D"">
Christian<br class=3D"">
<br class=3D"">
<br class=3D"">
<br class=3D"">
<br class=3D"">
&gt; I also<br class=3D"">
&gt; think that the world tour tends to have the unintended =
side-effect<br class=3D"">
&gt; of overemphasizing the importance of meetings to our process.<br =
class=3D"">
&gt;<br class=3D"">
&gt; Also, note that a large number of regulars opted to skip the =
meeting<br class=3D"">
&gt; in Buenos Aires.&nbsp; Granted, there are those who might see that =
as<br class=3D"">
&gt; a benefit.<br class=3D"">
&gt;<br class=3D"">
&gt; Melinda<br class=3D"">
&gt;<br class=3D"">
<br class=3D"">
</blockquote></div><br class=3D""></div>
</div></blockquote></div><br class=3D""></body></html>=

--Apple-Mail=_9E4F89C6-07A7-467C-BB13-66FDE59055A0--


From nobody Tue Apr 19 12:54:26 2016
Return-Path: <jhall@cdt.org>
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 D47A812DB5E for <ietf@ietfa.amsl.com>; Tue, 19 Apr 2016 12:54:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cdt.org
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 j3zeEne2oU2k for <ietf@ietfa.amsl.com>; Tue, 19 Apr 2016 12:54:24 -0700 (PDT)
Received: from mail-vk0-x236.google.com (mail-vk0-x236.google.com [IPv6:2607:f8b0:400c:c05::236]) (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 34BB612E276 for <ietf@ietf.org>; Tue, 19 Apr 2016 12:54:24 -0700 (PDT)
Received: by mail-vk0-x236.google.com with SMTP id n67so29263216vkf.3 for <ietf@ietf.org>; Tue, 19 Apr 2016 12:54:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cdt.org; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=/6ZwA8LcXHDIjZC1O9vnE6X6NgBLRWVlthOe2GQuo9I=; b=I96xUZnrTTxyfiwoOXzlVaeuKdDlcMMBXbeUHen9GhYDzG3s3FF4Y3c8qn90EPebIV E+erXEXyZni2FK3Tq2dJTvRyaIrmeIycIpjctk3vOb5Wejl5KIOFjrizAl6+dZTEu7Tf o/6McOZUZ78n0S7Ic7Vc7t0k4QNkZyI3S1WFE=
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=/6ZwA8LcXHDIjZC1O9vnE6X6NgBLRWVlthOe2GQuo9I=; b=dIu1B0gYi0Sp9giZFfK1k9mPeAbTqoA6q28QKRAStwXt+P9Zo4TRfpG+nV7Fl95NYH fgEGjUpagQoRaqEJqpxmsRXtFaiCi+TS+aHglLwOnvSYW5xZ+rr/r4RHE9KblCgrTxNY XJjtIEAu2+jTBuH7QjV0iQzJXlR84e6gDZZ9GcZUcmtXMKxWu4KWp8jbs0RQ6xycFetI E8u9w3r9PuUzhra8OLkLY7H+fllWxxav/OO+dCLT6jSm5S+ixJ1i+YdPPCChdVI1rRIc N6vqwINJxP7sWovye2dRhPnFVixeHbyIBYP2fcecgxAuCo8DILnK+BCSLqmPJlVR+pyb VZLA==
X-Gm-Message-State: AOPr4FUPdKJ3H7jeTBRQ/8C2+7T7hw0SrvZLDh5Y0ASW/jo8yZR2opLiREf9+/OU6JvKGh1zzkMIdsBv1mDoW9Pt
X-Received: by 10.159.33.181 with SMTP id 50mr2362306uac.114.1461095663166; Tue, 19 Apr 2016 12:54:23 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.103.94.3 with HTTP; Tue, 19 Apr 2016 12:54:03 -0700 (PDT)
In-Reply-To: <57168215.4080107@cs.tcd.ie>
References: <CAPt1N1n+676sAWFLee3oUGUgnTNHh95yFgrsmyjB5VbSmF-=XQ@mail.gmail.com> <876171588.2793946.1461088986149.JavaMail.yahoo@mail.yahoo.com> <57167C6C.50104@gmail.com> <57168215.4080107@cs.tcd.ie>
From: Joseph Lorenzo Hall <joe@cdt.org>
Date: Tue, 19 Apr 2016 15:54:03 -0400
Message-ID: <CABtrr-URsEfgjPFArerBU4cO04xFy9NWFz05iEe=_kDw3LK3ww@mail.gmail.com>
Subject: Re: f2f and mailing list participation - a question for "newer" participants (Was: Re: Interim step on meetings site feedback for sites currently under active consideration)
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/KVJd-asrmsFbKr7nWIwqSki2s3I>
Cc: IETF Discussion Mailing List <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: Tue, 19 Apr 2016 19:54:26 -0000

On Tue, Apr 19, 2016 at 3:08 PM, Stephen Farrell
<stephen.farrell@cs.tcd.ie> wrote:
> So, I'd be really interested in hearing from people who've
> been participating a bit for a while and who'd consider themselves
> as "newer participants" (define that yourself however you want)...
>
> If you've been to a f2f meeting what difference did that make
> to how you participate via mailing lists and remote tools?
>
> or
>
> If you've not been to a f2f meeting, what's your experience of
> participation via mailing lists and (especially) remote tools?

My new participant response:

1. It's made a big big difference being able to attend f2f meetings.
2. Remote participation works very well for consumers.

While CDT has been participating at IETF (with some gaps) for many
years, I definitely consider myself personally to be a newer
participant, with my first IETF being 89 in London but having missed
90 (Vancouver) and 95 (BA).

We've gone so far as sought funding from grantmaking philanthropic
organizations (as have others like Article 19 and the ACLU) to support
our IETF work, and a very important part of that support is being able
to ensure we can attend IETF in person. Not only do you get to know
peoples' voices and such, but the "hallway track" is in essence "many
fine lunches and dinners" (although for IESG, etc. that must be
brutal!) that inevitably involves a lot of technical discussion (and
policy discussion, oh my!).

I found the remote participation at IETF 95 to be amazing (sure, there
were hiccups, but we troubleshoot and make it better)... but it is
definitely focused (rightly so) on good transmission of WG meeting
goings-on and remote presentations (e.g., participating in a
non-meetecho meeting is rough).

I can imagine remote participation is different for a "consumer" like
me (tend to comment on documents more than author or implement, heh)
than very active roles like IESG member, WG chair or editor.

best, Joe

-- 
Joseph Lorenzo Hall
Chief Technologist, Center for Democracy & Technology [https://www.cdt.org]
1401 K ST NW STE 200, Washington DC 20005-3497
e: joe@cdt.org, p: 202.407.8825, pgp: https://josephhall.org/gpg-key
Fingerprint: 3CA2 8D7B 9F6D DBD3 4B10  1607 5F86 6987 40A9 A871


From nobody Tue Apr 19 13:34:53 2016
Return-Path: <jari.arkko@piuha.net>
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 1B4D612E1A2 for <ietf@ietfa.amsl.com>; Tue, 19 Apr 2016 13:34:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.896
X-Spam-Level: 
X-Spam-Status: No, score=-2.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.996] 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 F0y9cWIbWvkM for <ietf@ietfa.amsl.com>; Tue, 19 Apr 2016 13:34:40 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 5DABE12DC2F for <ietf@ietf.org>; Tue, 19 Apr 2016 13:34:39 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 809CC2CC9A for <ietf@ietf.org>; Tue, 19 Apr 2016 23:34:37 +0300 (EEST) (envelope-from jari.arkko@piuha.net)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ik_UeIXClljV for <ietf@ietf.org>; Tue, 19 Apr 2016 23:34:36 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id B86BF2CC95 for <ietf@ietf.org>; Tue, 19 Apr 2016 23:34:35 +0300 (EEST) (envelope-from jari.arkko@piuha.net)
Subject: =?windows-1252?Q?Re=3A_Interim_step_on_meetings_site_feedback__?= =?windows-1252?Q?=E2=80=94_for_sites_currently_under_active_cons?= =?windows-1252?Q?ideration?=
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Content-Type: multipart/signed; boundary="Apple-Mail=_4CD72D15-6A3E-4C65-86FB-BE8653BAE4B7"; protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail 2.5.2
From: Jari Arkko <jari.arkko@piuha.net>
X-Priority: 3 (Normal)
In-Reply-To: <8fb376e11631f9ddf73f9385ec5472c3.squirrel@www.trepanning.net>
Date: Tue, 19 Apr 2016 22:34:33 +0200
Message-Id: <50AB4BF1-8634-4A59-9DEA-2BA14947D0C4@piuha.net>
References: <20160418161552.9368.65562.idtracker@ietfa.amsl.com> <8fb376e11631f9ddf73f9385ec5472c3.squirrel@www.trepanning.net>
To: "ietf@ietf.org Discussion" <ietf@ietf.org>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/uERjCprRUVttlrcyaJg80h32v4c>
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: Tue, 19 Apr 2016 20:34:52 -0000

--Apple-Mail=_4CD72D15-6A3E-4C65-86FB-BE8653BAE4B7
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252

I wanted to thank for the feedback we=92ve already gotten to =
venue-selection on the three future meeting locations. Keep the feedback =
coming!

I also wanted to briefly comment on the discussion here on ietf@ietf.org =
list. First off, the term =93world tour=94 can be understood in =
different ways, and it may not be the best term to use. We are a =
technology collaboration forum, not a tour operator :-) =46rom my =
perspective it is important that the IETF meetings happen where the =
IETFers are, maybe with occasional preference to emerging groups of =
IETFers. Hence 1-1-1*. Exactly where on the continents we meet is =
subject to detailed planning, but my understanding of the community=92s =
wishes has been that we=92d like to see more repeats of successful =
meeting sites, and I think that is what I=92m seeing in the future =
meeting calendar. Even so, some variation should probably be left, given =
that where we meet exactly does affect who comes to the meetings. If the =
IETF ever came to Finland I would guarantee that there=92d be more =
people than the usual participants, and those people would have =
something to say about our topics :-)

Secondly, when we talk about participation in IETF work, it should =
defined broadly. Meetings are far from the only way to introduce people =
to the IETF, and far from the only measure of a person=92s involvement =
in the IETF. In the years prior to our meeting in BA, there was a lot of =
interaction and activity in the region, I=92m sure there will be in the =
coming years as well.

Thirdly, outside that specific action, I think our organisation is also =
otherwise experiencing changes in participation styles, e.g., remote =
participation and remote presentations are growing. And I think even the =
concept of an IETF participant perhaps should evolve. For instance, I =
would love to see a mode of operation where it is possible to =
participate in significant ways with differing levels of investment. =
Somebody can attend all meetings and put in a significant fraction of =
their time, and be involved in many activities. That is perhaps the =
group of people that finds it easiest to work at the IETF, currently. =
But someone else may only be able to drive a particular issue, or =
perhaps just be able to check in to fix a bug that he or she has =
identified. Granted, we=92ve always been able to do this, but I think =
there=92s room for improvement. Can an open source project member with =
no ability to travel drive a spec from 00 to RFC? There are some obvious =
challenges, but I think it would be a good thing for the IETF if the =
answer was yes. Similarly, could an experienced technology developer =
participate in the IETF to drive an effort that he or she is interested =
in, for the duration of the effort, and become a chair of that working =
group? Again, I=92d argue it would be a good thing that the answer was =
yes.

Jari


--Apple-Mail=_4CD72D15-6A3E-4C65-86FB-BE8653BAE4B7
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQIcBAEBCgAGBQJXFpZZAAoJEM80gCTQU46q5MsP/j04BITa8Y3Mb2TzYk7uZ1X3
wZdLTuGAZ45xgJmYcbZg+YewNehhnqz3bmA0azAgKctsPstty0JTHG3UmlaAwf8R
ceDkj3EnWLhI1O8Mikbt8GBMbmwG1Hysz0hEM9sC0q0WLy2YCGs9H5a3EGJHQnjC
U8f6I/VrVubvW1tMoqCrUXCiF7wHWS8nPEhTBCN9t2KII1uCo/MrG4tR2ydnlw9o
BxaQ1M3bwLdmOVTaI6WC6iK+OdrZxXPZV7z0hvqQ1KEfijRGexYYmwU71p2stcIF
IBdf8ULLuQAAI5LjDBa+gPRhrz1BUMCFJp23Q7Zpb6vBLEA8n3oSdCWc/FoP6PB8
7Dhtl6xKXanIEqvjVK7DVnLTSdLGUbkv2VbFtqAUP1GC9S9wEDSMXUFY5/zjdzrw
D4AbhX3ABoqKjG0GyqdtaqAxvgmHSZb+zn2b8md6PV06lXqA9ffw6MKjhvfattl4
kbGY/+x8jy0z8koLMzWGMctKFzr+Dvum8e+qefagTbn+sKsbrAYLpoiD0KNNB+1s
f+d2aSbjrQSYxL6Aqrpvg2rcpma44vpQjaA7M2ueWxicjBoit32HCUTuUDrzMX0O
8Jy4kjzPE35HVDfM+gUPiVItce6pGPPD4RorsP9hU8JQ3Je9TK08le7qMJzHRuhZ
sCWsj62K/KDu+gZ0t/zz
=xcTj
-----END PGP SIGNATURE-----

--Apple-Mail=_4CD72D15-6A3E-4C65-86FB-BE8653BAE4B7--


From nobody Wed Apr 20 03:48:44 2016
Return-Path: <harald@alvestrand.no>
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 A312812DF49 for <ietf@ietfa.amsl.com>; Wed, 20 Apr 2016 03:48:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.196
X-Spam-Level: 
X-Spam-Status: No, score=-5.196 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.996] 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 42lk36axSuqd for <ietf@ietfa.amsl.com>; Wed, 20 Apr 2016 03:48:41 -0700 (PDT)
Received: from mork.alvestrand.no (mork.alvestrand.no [158.38.152.117]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6C45412DDA2 for <ietf@ietf.org>; Wed, 20 Apr 2016 03:48:41 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mork.alvestrand.no (Postfix) with ESMTP id 870177C7DD2 for <ietf@ietf.org>; Wed, 20 Apr 2016 12:48:39 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at alvestrand.no
Received: from mork.alvestrand.no ([127.0.0.1]) by localhost (mork.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ompjcMFkbBT7 for <ietf@ietf.org>; Wed, 20 Apr 2016 12:48:38 +0200 (CEST)
Received: from hta-hippo.lul.corp.google.com (unknown [IPv6:2620:0:1043:12:a180:7eff:b055:c675]) by mork.alvestrand.no (Postfix) with ESMTPSA id 1AC457C7DCF for <ietf@ietf.org>; Wed, 20 Apr 2016 12:48:38 +0200 (CEST)
Subject: Re: Interim step on meetings site feedback for sites currently under active consideration
To: ietf@ietf.org
References: <20160418161552.9368.65562.idtracker@ietfa.amsl.com> <8fb376e11631f9ddf73f9385ec5472c3.squirrel@www.trepanning.net> <57151C55.30206@gmail.com> <54D9A539-6409-4692-85F6-E4837E823AAE@gmail.com> <CAPt1N1n+676sAWFLee3oUGUgnTNHh95yFgrsmyjB5VbSmF-=XQ@mail.gmail.com> <CAKe6YvPGufULDN=SLbR8YZ-7-tUj-H18U4h4JTH7_S3UJKvRbw@mail.gmail.com>
From: Harald Alvestrand <harald@alvestrand.no>
Message-ID: <57175E85.2030804@alvestrand.no>
Date: Wed, 20 Apr 2016 12:48:37 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0
MIME-Version: 1.0
In-Reply-To: <CAKe6YvPGufULDN=SLbR8YZ-7-tUj-H18U4h4JTH7_S3UJKvRbw@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/I_lHiDvKlsWtMPV7KNPEZPD4Hmo>
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, 20 Apr 2016 10:48:43 -0000

I think we should not let the perfect become the enemy of the good with
regard to measuring impact.

If we see a large cohort of first-time Buenos Aires attendees show up at
later meetings (Berlin being the first chance for them to show), we have
a strong signal that they thought it was worth it, and likely that
having the meeting in BA helped the community by helping recruit them.
Case closed (apart from some corner case possibilities I'm sure we,
being engineers, can all imagine).

If we don't see such a cohort, we need to dig deeper.

Let's do the obvious measurements. They're not useless just because they
don't show everything.

On 04/19/2016 08:56 PM, Vinayak Hegde wrote:
> On Tue, Apr 19, 2016 at 11:25 PM, Ted Lemon <mellon@fugue.com> wrote:
>> It should be pretty easy for the IAD to measure this by comparing the list
>> of newcomers in Argentina to the list of participants in Berlin, for
>> example.   I am fairly sure that they already do this, and possibly may even
>> have made presentations about it from time to time at the plenary... :)
> Hi Ted,
>
> I am not picking on you but this idea is flawed at many levels.
> Fundamentally we need to answer
> 1. What does a (meaningful ?) contribution mean ?
> 2. How does that relate to active participation ? Are there thresholds
> or is it a continuum ? Does I mean writing a draft or is reviewing
> drafts, taking minutes and hacking on code to check real world
> implementation good enough.
>
> The answers are more nuanced and varied than one might guess at first
> glance. At IETF 95 in BA several long-time contributors participated
> remotely. I am sure that they would take offense to this idea if they
> have contributed remotely and on the mailing lists.
>
> Just to emphasize, several WG chairs also do not attend every meeting.
> Are they active ? I think there needs to be less emphasis on physical
> meetings overall (FWIW I think we are already moving in that direction
> quite rapidly. But at the same time F2F interaction cannot be done
> away with completely IMHO and is also not going away.)
>
> -- Vinayak
>


From nobody Wed Apr 20 06:26:52 2016
Return-Path: <tnadeau@lucidvision.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 C23D612E5A1 for <ietf@ietfa.amsl.com>; Wed, 20 Apr 2016 06:26:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.998
X-Spam-Level: 
X-Spam-Status: No, score=-2.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.996, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=lucidvision.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 SGlH5LgsIuap for <ietf@ietfa.amsl.com>; Wed, 20 Apr 2016 06:26:48 -0700 (PDT)
Received: from lucidvision.com (lucidvision.com [64.71.170.115]) (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 8676112E52B for <ietf@ietf.org>; Wed, 20 Apr 2016 06:26:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=lucidvision.com; s=default; t=1461158782; bh=Zi23TLr+tFi2OFIHap0zY/BR7mb4L682apjMyzLCscc=; h=Subject:From:In-Reply-To:Date:Cc:References:To; b=ySNSo5Www0km0EclIHb1Xz95p3s0K097MZhiFjSrL8Hh/CREnABqIL02W5M6GA2n8 4zuGklP0jm4lcbbEFZvtijCY8bQQrW8gP1MKo69R2/H7cFa8w8dem9n1fXeWmVTYTE T6le9phWmpJIK/doAUNXXmu+qmyIO+mcL/Z0FYgI=
X-Default-Received-SPF: pass (skip=loggedin (res=PASS)) x-ip-name=23.25.240.189; 
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (1.0)
Subject: Re: Interim step on meetings site feedback for sites currently under active consideration
From: thomas nadeau <tnadeau@lucidvision.com>
X-Mailer: iPhone Mail (13E238)
In-Reply-To: <57175E85.2030804@alvestrand.no>
Date: Wed, 20 Apr 2016 09:26:18 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <60F23053-67F2-4A6E-A9C8-4E9681585BBD@lucidvision.com>
References: <20160418161552.9368.65562.idtracker@ietfa.amsl.com> <8fb376e11631f9ddf73f9385ec5472c3.squirrel@www.trepanning.net> <57151C55.30206@gmail.com> <54D9A539-6409-4692-85F6-E4837E823AAE@gmail.com> <CAPt1N1n+676sAWFLee3oUGUgnTNHh95yFgrsmyjB5VbSmF-=XQ@mail.gmail.com> <CAKe6YvPGufULDN=SLbR8YZ-7-tUj-H18U4h4JTH7_S3UJKvRbw@mail.gmail.com> <57175E85.2030804@alvestrand.no>
To: Harald Alvestrand <harald@alvestrand.no>
X-Authenticated-User: tnadeau@lucidvision.com 
X-Info: aspam skipped due to (g_smite_skip_relay)
X-Encryption: SSL encrypted
X-MyRbl: Color=Unknown ip=23.25.240.189
X-IP-stats: Notspam Incoming Last 9, First 288, in=19, out=0, spam=0 Known=true ip=23.25.240.189
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/vqBCay-5DcZvH3jlA7SgvgFw9nM>
Cc: 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, 20 Apr 2016 13:26:52 -0000

> On Apr 20, 2016, at 6:48 AM, Harald Alvestrand <harald@alvestrand.no> wrot=
e:
>=20
> I think we should not let the perfect become the enemy of the good with
> regard to measuring impact.
>=20
> If we see a large cohort of first-time Buenos Aires attendees show up at
> later meetings (Berlin being the first chance for them to show), we have
> a strong signal that they thought it was worth it, and likely that
> having the meeting in BA helped the community by helping recruit them.
> Case closed (apart from some corner case possibilities I'm sure we,
> being engineers, can all imagine).
>=20
> If we don't see such a cohort, we need to dig deeper.

Or perhaps wonder why we should concern ourselves with this at all?

tom

>=20
> Let's do the obvious measurements. They're not useless just because they
> don't show everything.
>=20
>> On 04/19/2016 08:56 PM, Vinayak Hegde wrote:
>>> On Tue, Apr 19, 2016 at 11:25 PM, Ted Lemon <mellon@fugue.com> wrote:
>>> It should be pretty easy for the IAD to measure this by comparing the li=
st
>>> of newcomers in Argentina to the list of participants in Berlin, for
>>> example.   I am fairly sure that they already do this, and possibly may e=
ven
>>> have made presentations about it from time to time at the plenary... :)
>> Hi Ted,
>>=20
>> I am not picking on you but this idea is flawed at many levels.
>> Fundamentally we need to answer
>> 1. What does a (meaningful ?) contribution mean ?
>> 2. How does that relate to active participation ? Are there thresholds
>> or is it a continuum ? Does I mean writing a draft or is reviewing
>> drafts, taking minutes and hacking on code to check real world
>> implementation good enough.
>>=20
>> The answers are more nuanced and varied than one might guess at first
>> glance. At IETF 95 in BA several long-time contributors participated
>> remotely. I am sure that they would take offense to this idea if they
>> have contributed remotely and on the mailing lists.
>>=20
>> Just to emphasize, several WG chairs also do not attend every meeting.
>> Are they active ? I think there needs to be less emphasis on physical
>> meetings overall (FWIW I think we are already moving in that direction
>> quite rapidly. But at the same time F2F interaction cannot be done
>> away with completely IMHO and is also not going away.)
>>=20
>> -- Vinayak
>=20


From nobody Wed Apr 20 08:02:52 2016
Return-Path: <johnl@taugh.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 7BFA312D6CF for <ietf@ietfa.amsl.com>; Wed, 20 Apr 2016 08:02:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] 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 NpYratn_iYni for <ietf@ietfa.amsl.com>; Wed, 20 Apr 2016 08:02:50 -0700 (PDT)
Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 212EF12D0D3 for <ietf@ietf.org>; Wed, 20 Apr 2016 08:02:50 -0700 (PDT)
Received: (qmail 20709 invoked from network); 20 Apr 2016 15:02:48 -0000
Received: from unknown (64.57.183.18) by mail1.iecc.com with QMQP; 20 Apr 2016 15:02:48 -0000
Date: 20 Apr 2016 15:02:26 -0000
Message-ID: <20160420150226.17377.qmail@ary.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: Interim step on meetings site feedback for sites currently under active consideration
In-Reply-To: <57175E85.2030804@alvestrand.no>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/QfQyCGK2QwBs2JPW2IOQUJKWBI4>
Cc: harald@alvestrand.no
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, 20 Apr 2016 15:02:51 -0000

>I think we should not let the perfect become the enemy of the good with
>regard to measuring impact.
>
>If we see a large cohort of first-time Buenos Aires attendees show up at
>later meetings (Berlin being the first chance for them to show), we have
>a strong signal that they thought it was worth it, and likely that
>having the meeting in BA helped the community by helping recruit them.

Personally, I don't care whether they show up in Berlin, I care
whether they show up on mailing lists writing drafts and editing and
reviewing them.

I'd be rather surprised if a lot of new participants from Argentina
showed up in Berlin, because if you live in, say, Mendoza, it's orders
of magnitude more expensive to get to Berlin than to B.A.

R's,
John


From nobody Wed Apr 20 08:08:42 2016
Return-Path: <abdussalambaryun@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 A2B6512D659; Wed, 20 Apr 2016 08:08:40 -0700 (PDT)
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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 KuESVhSEW0aO; Wed, 20 Apr 2016 08:08:38 -0700 (PDT)
Received: from mail-qg0-x22b.google.com (mail-qg0-x22b.google.com [IPv6:2607:f8b0:400d:c04::22b]) (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 5550612D64F; Wed, 20 Apr 2016 08:08:38 -0700 (PDT)
Received: by mail-qg0-x22b.google.com with SMTP id d90so229330qgd.3; Wed, 20 Apr 2016 08:08:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=Fbk/4fNgt/rW0j9XlYKkQ1n/WWU9fdOW8h5oq3KFhBs=; b=oMBOg5MryBtYdGMEaU6SeY48dOBGqZAE8X/QXLXAHMvD0GYDv+1t5rlQhn1Yrz8iYa w/qIolBCthGncc+aASTh0ybbbPFxoD+C8tDfqhuTB/+d7ps7O3Yce2jAmKb4JbtPOjH+ panvNJ5e/2lx05rGqhV6ITPpvkpuH+HXGN/J/FIjd7XYzHwGvX72oQpwVWTkJw85NNz9 ZKt+nmR2r0bB9Mk3Tq64oCN92UBxbPsCJNRnq58WHw2NpEKDqiCNHsm7udWV21kwQZQZ l70cAPLGlw6V4/bK8YoiOUi/cvhaTTGsS38AtOYu/q2L5S1OCvs54StDkBa/O2S4hUlY udFg==
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:date :message-id:subject:from:to:cc; bh=Fbk/4fNgt/rW0j9XlYKkQ1n/WWU9fdOW8h5oq3KFhBs=; b=NoYstGXO7UxQhUYjkfhji+U1TTx/QkV0EhghYgEdz+FgPfDC6xkbstDl769YHaK3b+ gcCBaHGXiDckCVV3MsV8XYz+7RZ8WE9aqFvmomI1xPXpB2ukl+/Tx+N+/JsEs5wlV9SW WyEq6Xzz1160fn3MF4KVGLm0P3BaVYxmzy6lVJLM3uGva+pWOat1QpnV2Zhl6BTAJ8x2 OOfOYw1QjIFR4RoxlgNP/oVJmsztittP1w9eKJqYwiQp06/wWjuZ3EcdMV0Ae0vVCR8k 2Pw9g/BQOLfjYwhnNr/Mx8uNWAYHxaPbLsQ1P7/MMIeN/hMvJ+OPAK2x71fQ4dTUWEgJ 8Pdw==
X-Gm-Message-State: AOPr4FUsu5ibxoNYbyqJWj064Rpz4yva3OYbFeUgx+ayDRQ5qaVRreY5TuaNQTo+1AxEnb9FOvukJrPSlMSnbw==
MIME-Version: 1.0
X-Received: by 10.140.169.132 with SMTP id p126mr12113327qhp.71.1461164917426;  Wed, 20 Apr 2016 08:08:37 -0700 (PDT)
Received: by 10.140.43.131 with HTTP; Wed, 20 Apr 2016 08:08:37 -0700 (PDT)
In-Reply-To: <CAPt1N1kFgReUFy-RC9ovMUN9LqnBVRCconku4gyqow0sN_0Y9g@mail.gmail.com>
References: <57151C55.30206@gmail.com> <746128222.2295531.1461009032633.JavaMail.yahoo@mail.yahoo.com> <CAD499eLvW0KFToSHLb4faMHk2c5ad+HAPEwumaq48QaUbh2n2A@mail.gmail.com> <CAPt1N1kFgReUFy-RC9ovMUN9LqnBVRCconku4gyqow0sN_0Y9g@mail.gmail.com>
Date: Wed, 20 Apr 2016 17:08:37 +0200
Message-ID: <CADnDZ8-4_Me2C+2Pi_QXEW7N0Z5h6g2Ys4cEH0jpcyrDM+aeRg@mail.gmail.com>
Subject: Re: [Mtgvenue] Interim step on meetings site feedback for sites currently under active consideration
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: Ted Lemon <mellon@fugue.com>
Content-Type: multipart/alternative; boundary=001a113b31b2dc8fc70530ebf721
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/QikAgquoZDA-k6pxm_a_rCkEREg>
Cc: "ietf@ietf.org" <ietf@ietf.org>, Corinne Cath <corinnecath@gmail.com>, "mtgvenue@ietf.org" <mtgvenue@ietf.org>, Juliao Braga <juliao@braga.net.br>, "Carlos M. Martinez" <carlos@lacnic.net>, Christian O'Flaherty <oflaherty@isoc.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, 20 Apr 2016 15:08:40 -0000

--001a113b31b2dc8fc70530ebf721
Content-Type: text/plain; charset=UTF-8

I think the tool is that each discussion needs a chair and each chair is
responsible for getting value from any discussion/list/meeting. IETF needs
to look into our chairs or create more.

AB

On Tue, Apr 19, 2016 at 2:02 PM, Ted Lemon <mellon@fugue.com> wrote:

> The IETF has a very strong tradition of commenting at length on the topic
> at hand and hoping either that IETF leadership will spend the time to
> review the whole thread and extract the salient points from it, or give up
> in despair.   So what you are seeing here is very much the IETF tradition.
>   Asking people to do better probably won't work, although it never hurts
> to try.
>
> I personally see this as a tools problem, more than a communications
> problem--we need better tools to track the points being made in discussions
> so that either the people discussing can see that they don't need to make a
> particular point again, or at least that the people tracking the discussion
> can see that the point has already been made.
>
> On Tue, Apr 19, 2016 at 4:48 AM, Corinne Cath <corinnecath@gmail.com>
> wrote:
>
>> Dear all,
>>
>> Just a quick question: are you intending on providing feedback to the
>> IAOC? If so, maybe it makes sense to coordinate a bit in order to prevent a
>> duplication of entries? Or will it be useful if multiple people point out
>> the same themes?
>>
>> Best,
>>
>> Corinne
>>
>> On Mon, Apr 18, 2016 at 8:50 PM, <nalini.elkins@insidethestack.com>
>> wrote:
>>
>>>
>>>
>>>
>>> >>But
>>> >> I think these issues should be balanced with the overall benefit
>>> >> that the IETF World Tour provides.
>>>
>>>
>>> >As I've said repeatedly, I don't think the world tour actually
>>> >does bring much benefit.  I'm very hopeful that some of the
>>> >South Americans who attended their first IETF meeting because
>>> >it was held in Buenos Aires will continue to participate (as in:
>>> >bring in work and participate in ongoing work, and not as in: sit
>>> >in meetings) but historically that has not been the case.
>>>
>>> Just to put some numbers into this conversation, we have 8 people from
>>> Latin America who have signed up to be a part of the Internet Draft Review
>>> teams.   The first review team to form will likely be the Spanish-speaking
>>> DNSOP review team.
>>>
>>> This is one week after IETF 95 and after 3 days of soliciting review
>>> teams and basically zero publicity.
>>>
>>> I wonder if there has not been more participation in active IETF work
>>> before from other regions because there was no structured way to start
>>> participating and language insensitivity.  (BTW, there is a new member of
>>> the Mentoring Team from Latin America, that I met in Buenos Aires who will
>>> translate the Mentoring emails into Spanish.)
>>>
>>> But the effort of the Mentoring Team is standing on the shoulders of
>>> giants.  People such as Carlos Martinez, Christian O'Flaherty, Alvaro
>>> Retana, Dr. Juliao Braga, and many others who have done such a tremendous
>>> job of outreach to their community in Latin America.
>>>
>>> So, let's do some changing of history.
>>>
>>> Nalini
>>>
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> Mtgvenue mailing list
>>> Mtgvenue@ietf.org
>>> https://www.ietf.org/mailman/listinfo/mtgvenue
>>>
>>>
>>
>> _______________________________________________
>> Mtgvenue mailing list
>> Mtgvenue@ietf.org
>> https://www.ietf.org/mailman/listinfo/mtgvenue
>>
>>
>

--001a113b31b2dc8fc70530ebf721
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>I think the tool is that each discussion needs a chai=
r and each chair is responsible for getting value from any discussion/list/=
meeting. IETF needs to look into our chairs or create more.<br><br></div>AB=
 <br></div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Tue=
, Apr 19, 2016 at 2:02 PM, Ted Lemon <span dir=3D"ltr">&lt;<a href=3D"mailt=
o:mellon@fugue.com" target=3D"_blank">mellon@fugue.com</a>&gt;</span> wrote=
:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-le=
ft:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr">The IETF has a very st=
rong tradition of commenting at length on the topic at hand and hoping eith=
er that IETF leadership will spend the time to review the whole thread and =
extract the salient points from it, or give up in despair. =C2=A0 So what y=
ou are seeing here is very much the IETF tradition. =C2=A0 Asking people to=
 do better probably won&#39;t work, although it never hurts to try.=C2=A0<d=
iv><br></div><div>I personally see this as a tools problem, more than a com=
munications problem--we need better tools to track the points being made in=
 discussions so that either the people discussing can see that they don&#39=
;t need to make a particular point again, or at least that the people track=
ing the discussion can see that the point has already been made.</div></div=
><div class=3D"HOEnZb"><div class=3D"h5"><div class=3D"gmail_extra"><br><di=
v class=3D"gmail_quote">On Tue, Apr 19, 2016 at 4:48 AM, Corinne Cath <span=
 dir=3D"ltr">&lt;<a href=3D"mailto:corinnecath@gmail.com" target=3D"_blank"=
>corinnecath@gmail.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_=
quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1=
ex"><div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-family:geor=
gia,serif">Dear all,<br><br></div><div class=3D"gmail_default" style=3D"fon=
t-family:georgia,serif">Just a quick question: are you intending on providi=
ng feedback to the IAOC? If so, maybe it makes sense to coordinate a bit in=
 order to prevent a duplication of entries? Or will it be useful if multipl=
e people point out the same themes?<br><br></div><div class=3D"gmail_defaul=
t" style=3D"font-family:georgia,serif">Best,<br><br></div><div class=3D"gma=
il_default" style=3D"font-family:georgia,serif">Corinne <br></div></div><di=
v class=3D"gmail_extra"><br><div class=3D"gmail_quote"><div><div>On Mon, Ap=
r 18, 2016 at 8:50 PM,  <span dir=3D"ltr">&lt;<a href=3D"mailto:nalini.elki=
ns@insidethestack.com" target=3D"_blank">nalini.elkins@insidethestack.com</=
a>&gt;</span> wrote:<br></div></div><blockquote class=3D"gmail_quote" style=
=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><di=
v><div><div style=3D"color:#000;background-color:#fff;font-family:Helvetica=
Neue-Light,Helvetica Neue Light,Helvetica Neue,Helvetica,Arial,Lucida Grand=
e,sans-serif;font-size:16px"><div><br></div><div><br><br></div><div style=
=3D"display:block"><div style=3D"font-family:HelveticaNeue-Light,Helvetica =
Neue Light,Helvetica Neue,Helvetica,Arial,Lucida Grande,sans-serif;font-siz=
e:16px"><div style=3D"font-family:HelveticaNeue,Helvetica Neue,Helvetica,Ar=
ial,Lucida Grande,sans-serif;font-size:16px"><div><div>&gt;&gt;But<br clear=
=3D"none">&gt;&gt; I think these issues should be balanced with the overall=
 benefit<br clear=3D"none">&gt;&gt; that the IETF World Tour provides.</div=
><br clear=3D"none"><br clear=3D"none">&gt;As I&#39;ve said repeatedly, I d=
on&#39;t think the world tour actually<br clear=3D"none">&gt;does bring muc=
h benefit.=C2=A0 I&#39;m very hopeful that some of the<br clear=3D"none">&g=
t;South Americans who attended their first IETF meeting because<br clear=3D=
"none">&gt;it was held in Buenos Aires will continue to participate (as in:=
<br clear=3D"none">&gt;bring in work and participate in ongoing work, and n=
ot as in: sit<br clear=3D"none">&gt;in meetings) but historically that has =
not been the case.=C2=A0<br clear=3D"none"><div>=C2=A0<br clear=3D"none">Ju=
st to put some numbers into this conversation, we have 8 people from Latin =
America who have signed up to be a part of the Internet Draft Review teams.=
 =C2=A0 The first review team to form will likely be the Spanish-speaking D=
NSOP review team.</div><div><br></div><div dir=3D"ltr">This is one week aft=
er IETF 95 and after 3 days of soliciting review teams and basically zero p=
ublicity.</div><div><br></div><div dir=3D"ltr">I wonder if there has not be=
en more participation in active IETF work before from other regions because=
 there was no structured way to start participating and language insensitiv=
ity. =C2=A0(BTW, there is a new member of the Mentoring Team from Latin Ame=
rica, that I met in Buenos Aires who will translate the Mentoring emails in=
to Spanish.)</div><div dir=3D"ltr"><br></div><div dir=3D"ltr">But the effor=
t of the Mentoring Team is standing on the shoulders of giants.=C2=A0 Peopl=
e such as Carlos Martinez, Christian O&#39;Flaherty, Alvaro Retana, Dr. Jul=
iao Braga, and many others who have done such a tremendous job of outreach =
to their community in Latin America.</div><div dir=3D"ltr"><br></div><div d=
ir=3D"ltr">So, let&#39;s do some changing of history.</div><div dir=3D"ltr"=
><br></div><div dir=3D"ltr">Nalini</div><div dir=3D"ltr"><br></div><div dir=
=3D"ltr"><br></div><br><br></div> </div> </div>  </div></div></div><br></di=
v></div>_______________________________________________<br>
Mtgvenue mailing list<br>
<a href=3D"mailto:Mtgvenue@ietf.org" target=3D"_blank">Mtgvenue@ietf.org</a=
><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/mtgvenue" rel=3D"noreferre=
r" target=3D"_blank">https://www.ietf.org/mailman/listinfo/mtgvenue</a><br>
<br></blockquote></div><br></div>
<br>_______________________________________________<br>
Mtgvenue mailing list<br>
<a href=3D"mailto:Mtgvenue@ietf.org" target=3D"_blank">Mtgvenue@ietf.org</a=
><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/mtgvenue" rel=3D"noreferre=
r" target=3D"_blank">https://www.ietf.org/mailman/listinfo/mtgvenue</a><br>
<br></blockquote></div><br></div>
</div></div></blockquote></div><br></div>

--001a113b31b2dc8fc70530ebf721--


From nobody Wed Apr 20 08:10:55 2016
Return-Path: <melinda.shore@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 298DA12E0E7 for <ietf@ietfa.amsl.com>; Wed, 20 Apr 2016 08:10:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 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, RCVD_IN_DNSWL_LOW=-0.7, 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 ue0MkxEOR0p1 for <ietf@ietfa.amsl.com>; Wed, 20 Apr 2016 08:10:52 -0700 (PDT)
Received: from mail-pa0-x235.google.com (mail-pa0-x235.google.com [IPv6:2607:f8b0:400e:c03::235]) (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 DDE4412DD1B for <ietf@ietf.org>; Wed, 20 Apr 2016 08:10:51 -0700 (PDT)
Received: by mail-pa0-x235.google.com with SMTP id zm5so18746785pac.0 for <ietf@ietf.org>; Wed, 20 Apr 2016 08:10:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding; bh=owZZrsVDUmAN1Kxj2Zss0Ecw2BEzzFAyRkfs/c+qNxc=; b=hlqpMdIuRafXfn38EZ+oUiOzDgpl0Z/TuG4KiudL0TJoAKE4Dfcd4b72v7wgn4athw a1CvsWtyr/O+U20Yy/hFr9wRmI+cxHr57gjZ3d0sxU/XNA+YN7VfGqd/79b/DtwKtKmE YPvG0AWsFYiIpAkBliBjYweq805veH2brGk/nha5GNYoE45vYa2TECs0vDvGSXd1s8f3 TS943W2azrXB52zklrN2HUJHm+HePYk9NT9htiUm3K6WrJyHBD4P8H8SOjyDhRTuy+YK we3LFHA460eCKOEbv9ycCe+Z6gIaP+xsv86+Q1PhoISDbQBfoPYqnq5Pqs0UD+3E6/wL 3bYg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=owZZrsVDUmAN1Kxj2Zss0Ecw2BEzzFAyRkfs/c+qNxc=; b=D+RIimAONzekQvTLGODYeimOn+YNngEV1vEvE5CFUkVuk7mVaSnIF5TEYS6VxDpKZZ b0NXEEAu7oLdceqp9eKJows5j7q2hbHf5Y+JjmJXduIoeDER7RSY8IQcfrijB655xK95 nunANm+SFRME7J2Z4ItBSsesBroCc8538Dbbivc61ZRUDmG4MRAX3i3QtjoZZJjyff2l mUcl9iQGw/XHpipRm6VysBIVRN6xfQqjIyC4PlgDNl7WzehqPyLZBGqPdsKRPWHaRx23 Q+YrEWhFgyV9bM8/TSGtHJnPolXgDT6AouMWy+byTjzW6HOXOsOBgmJj6bUh10VsMXtL dMRA==
X-Gm-Message-State: AOPr4FU6gj+K7ETgDQROzbdOG5He45l1uMrg1FQg8LPgWLyAzU0bYgIY7Ge0OPc+EC3enw==
X-Received: by 10.66.118.106 with SMTP id kl10mr12907358pab.78.1461165051436;  Wed, 20 Apr 2016 08:10:51 -0700 (PDT)
Received: from Melindas-MacBook-Pro.local (216-67-58-191-radius.dynamic.acsalaska.net. [216.67.58.191]) by smtp.googlemail.com with ESMTPSA id y128sm3257736pfb.13.2016.04.20.08.10.50 for <ietf@ietf.org> (version=TLSv1/SSLv3 cipher=OTHER); Wed, 20 Apr 2016 08:10:50 -0700 (PDT)
Subject: Re: Interim step on meetings site feedback for sites currently under active consideration
To: ietf@ietf.org
References: <20160420150226.17377.qmail@ary.lan>
From: Melinda Shore <melinda.shore@gmail.com>
Message-ID: <57179C0E.4000605@gmail.com>
Date: Wed, 20 Apr 2016 07:11:10 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:38.0) Gecko/20100101 Thunderbird/38.6.0
MIME-Version: 1.0
In-Reply-To: <20160420150226.17377.qmail@ary.lan>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/qoNOyx0swSlE91eEe8ajtN-gewY>
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, 20 Apr 2016 15:10:53 -0000

On 4/20/16 7:02 AM, John Levine wrote:
> Personally, I don't care whether they show up in Berlin, I care
> whether they show up on mailing lists writing drafts and editing and
> reviewing them.

Exactly.

Melinda



From nobody Wed Apr 20 08:36:32 2016
Return-Path: <abdussalambaryun@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 9B52B12D54F for <ietf@ietfa.amsl.com>; Wed, 20 Apr 2016 08:36:30 -0700 (PDT)
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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 aecikYSoDmGP for <ietf@ietfa.amsl.com>; Wed, 20 Apr 2016 08:36:28 -0700 (PDT)
Received: from mail-qg0-x230.google.com (mail-qg0-x230.google.com [IPv6:2607:f8b0:400d:c04::230]) (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 D755F12DC07 for <ietf@ietf.org>; Wed, 20 Apr 2016 08:23:23 -0700 (PDT)
Received: by mail-qg0-x230.google.com with SMTP id v14so30684719qge.0 for <ietf@ietf.org>; Wed, 20 Apr 2016 08:23:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=OMSSjPLqMGUTmnJ8pOJGPQg0BngFMr6zfgg6Ob6EVDk=; b=nzOkDmOvQw+Lhnw9RpqIppkqvhsEYek3Z1jeDFqX6FDdIUGT+f3w1ne3ATFk7VbIUa WtOL+X6bMVGjt3ryyW8RGJHAGLGsu4AYubzXcXj3IwyOFofysjq8NyMCHNxeNtDNwyPd +MyWXkyuwrJK6vP7rq9Ie2QTdaLGWrsyBm3V51fJkLxI5QuG1hn161HcmxCnwKcE/2zh qm8Z8HsorIhUCUESGKYtJaIpJDPigWk3JeI62uKMGocvAzwPk1/rzZTGOp+s9BF33UHS 7KoXFXGseKaoiEebXWqc3Q72b35rCNdioCLq9HF5NVIUPAM3VrxpEPKTFuKknClX/UgZ Fgmg==
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:date :message-id:subject:from:to:cc; bh=OMSSjPLqMGUTmnJ8pOJGPQg0BngFMr6zfgg6Ob6EVDk=; b=btH+i9qFYJN/dpI4vMwIhOtqvhfs0O3lQaeFORxohBsLvln8K5590v84d45pMdFzp7 /f63C4jh7WHpf/bV3td4teTORG3uaq5+WwUBuKaB2rBABOzSnTrG/gT32qEy4tIzIRNm EpyRHKDhYlnXbjWkkR1zCsddXLYFL4RSgF9VeB4qZgMXgNfxrHgY+oxp07AXq22u2kVJ GOdnoX+gg8U1x5KZUFJTixsKj0OeWpdrxVQC5miP+/+7Kc1UOnANqkNzXl5VQe5ooGoN 48AsQP44kbPT0dxcTg3sEfKh6Vpul75Wt9EFRXQ1kSSfA59KNqlmIHjcESXTB0amDfAf CEZQ==
X-Gm-Message-State: AOPr4FWpUjjFiQPC8OtvNT93WCdki/+aetZhaqfIKr0egCycLnMfTB1uJMriRKWYE0q5xwBTFYASQKOvpX3/2w==
MIME-Version: 1.0
X-Received: by 10.140.130.14 with SMTP id 14mr12177989qhc.85.1461165803025; Wed, 20 Apr 2016 08:23:23 -0700 (PDT)
Received: by 10.140.43.131 with HTTP; Wed, 20 Apr 2016 08:23:22 -0700 (PDT)
In-Reply-To: <57179C0E.4000605@gmail.com>
References: <20160420150226.17377.qmail@ary.lan> <57179C0E.4000605@gmail.com>
Date: Wed, 20 Apr 2016 17:23:22 +0200
Message-ID: <CADnDZ8-sRdqQp9rFn-7DiTmdBA-Qw91XcsizQ8ufb-fok=siZQ@mail.gmail.com>
Subject: Re: Interim step on meetings site feedback for sites currently under active consideration
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: Melinda Shore <melinda.shore@gmail.com>
Content-Type: multipart/alternative; boundary=001a1134f182a5be3a0530ec2cf6
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/Admum3-vWMe72mWuocPIeZs51aA>
Cc: ietf <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, 20 Apr 2016 15:36:30 -0000

--001a1134f182a5be3a0530ec2cf6
Content-Type: text/plain; charset=UTF-8

On Wed, Apr 20, 2016 at 5:11 PM, Melinda Shore <melinda.shore@gmail.com>
wrote:

> On 4/20/16 7:02 AM, John Levine wrote:
>
>> Personally, I don't care whether they show up in Berlin, I care
>> whether they show up on mailing lists writing drafts and editing and
>> reviewing them.
>>
>
> Exactly.
>
>
If IETF cares about reviews/discussions then it needs to continue
acknowledging their participants that discussed and reviewed. People with
different culture work for free when they are welcomed and treated well. So
we need to care when we find  people are not reviewing per WG, or need to
care when a WG has less reviews per draft.

AB

--001a1134f182a5be3a0530ec2cf6
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><div class=3D"gmail_quo=
te">On Wed, Apr 20, 2016 at 5:11 PM, Melinda Shore <span dir=3D"ltr">&lt;<a=
 href=3D"mailto:melinda.shore@gmail.com" target=3D"_blank">melinda.shore@gm=
ail.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D=
"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=
=3D"">On 4/20/16 7:02 AM, John Levine wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
Personally, I don&#39;t care whether they show up in Berlin, I care<br>
whether they show up on mailing lists writing drafts and editing and<br>
reviewing them.<br>
</blockquote>
<br></span>
Exactly.<span class=3D"HOEnZb"><font color=3D"#888888"><br>
<br></font></span></blockquote><div><br></div><div>If IETF cares about revi=
ews/discussions then it needs to continue acknowledging their participants =
that discussed and reviewed. People with different culture work for free wh=
en they are welcomed and treated well. So we need to care when we find=C2=
=A0 people are not reviewing per WG, or need to care when a WG has less rev=
iews per draft.<br><br></div><div>AB<br></div></div><br></div></div>

--001a1134f182a5be3a0530ec2cf6--


From nobody Wed Apr 20 08:37:15 2016
Return-Path: <stewe@stewe.org>
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 CAC1512DBAD for <ietf@ietfa.amsl.com>; Wed, 20 Apr 2016 08:37:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, LOTS_OF_MONEY=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] 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 uDlnxhaQHG3t for <ietf@ietfa.amsl.com>; Wed, 20 Apr 2016 08:37:11 -0700 (PDT)
Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1on0773.outbound.protection.outlook.com [IPv6:2a01:111:f400:fc10::773]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 75ED612F058 for <ietf@ietf.org>; Wed, 20 Apr 2016 08:25:23 -0700 (PDT)
Received: from BLUPR17MB0275.namprd17.prod.outlook.com (10.162.235.146) by BLUPR17MB0276.namprd17.prod.outlook.com (10.162.235.147) with Microsoft SMTP Server (TLS) id 15.1.466.19; Wed, 20 Apr 2016 15:25:05 +0000
Received: from BLUPR17MB0275.namprd17.prod.outlook.com ([10.162.235.146]) by BLUPR17MB0275.namprd17.prod.outlook.com ([10.162.235.146]) with mapi id 15.01.0466.023; Wed, 20 Apr 2016 15:25:05 +0000
From: Stephan Wenger <stewe@stewe.org>
To: John Levine <johnl@taugh.com>, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: Interim step on meetings site feedback for sites currently under active consideration
Thread-Topic: Interim step on meetings site feedback for sites currently under active consideration
Thread-Index: AQHRmZkrWzuQ7z3ff0uTs2gzx/aGyJ+RkPAAgAAFNQCAABEkgIABCeeAgABG6gD//5D5gA==
Date: Wed, 20 Apr 2016 15:25:05 +0000
Message-ID: <159A682B-3124-4ABC-9108-B7A6F9B49C52@stewe.org>
References: <57175E85.2030804@alvestrand.no> <20160420150226.17377.qmail@ary.lan>
In-Reply-To: <20160420150226.17377.qmail@ary.lan>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: taugh.com; dkim=none (message not signed) header.d=none;taugh.com; dmarc=none action=none header.from=stewe.org;
x-ms-exchange-messagesentrepresentingtype: 1
x-originating-ip: [50.174.30.183]
x-ms-office365-filtering-correlation-id: ff338331-66a4-470f-51ee-08d3692ff346
x-microsoft-exchange-diagnostics: 1; BLUPR17MB0276; 5:IMHWaaMulpHgw2JQHKrWw1JQcNuKWN3ASsHyCOWv5R17AAxsnIlBoqed1S2XAel0RKowfDvYK67I4knMlExJbaater3T0MTTa2J97jNKWLYrzZa8cWwILDesjAuCbqj3egO1Efo255WBa2sloky58M9zE77V1Z7BOs0T1S30NcvboQCOi4hS+WxuF2ZTA5hw; 24:96LS4GSVa1KxtaMoaSdMjvwvPeB6WwkYEvTSgSORHJOss03bq6t4XpKMlnu0cx6WDLFzuoYaQa72QXWaDy/9c6r3G+Ueft4gf/5sCjOPfBE=; 7:a3dU+AmVAUuRsHSHFb3+z03azvOX/PSad6sBVEH2lOIXfhWWMHje7KDkUbuhwDgiEIDX1WJfKGqVXvNzsmDqo3vT2JDld/Dqst4/HXX+KU/q+1RZWgHZUhy+TfWKwR3rnQq1nmfVTb3WsVt8rEZEArBcZhxXnD4kkGAluSmc7RqrIvH3xBI9WkgZPxrIRWO5m2NWKzEj0o4eRTDO4kDYoONFJY5sxtpC/A7AxL7UBFg=
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:BLUPR17MB0276;
x-microsoft-antispam-prvs: <BLUPR17MB027659009020E87F793D1431AE6D0@BLUPR17MB0276.namprd17.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(9101521026)(6040130)(601004)(2401047)(5005006)(8121501046)(3002001)(10201501046)(6041046)(6043046); SRVR:BLUPR17MB0276; BCL:0; PCL:0; RULEID:; SRVR:BLUPR17MB0276; 
x-forefront-prvs: 0918748D70
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(24454002)(66066001)(36756003)(99286002)(87936001)(5001770100001)(4326007)(586003)(2906002)(3280700002)(10400500002)(2501003)(81166005)(102836003)(6116002)(76176999)(54356999)(50986999)(189998001)(3660700001)(1096002)(1220700001)(3846002)(122556002)(77096005)(2950100001)(2900100001)(19580405001)(5004730100002)(19580395003)(33656002)(82746002)(92566002)(11100500001)(106116001)(86362001)(5002640100001)(5008740100001)(83716003)(42262002); DIR:OUT; SFP:1102; SCL:1; SRVR:BLUPR17MB0276; H:BLUPR17MB0275.namprd17.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en; 
spamdiagnosticoutput: 1:23
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
Content-ID: <C3112D80A819B04A80EC5864C9C32C0C@namprd17.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: stewe.org
X-MS-Exchange-CrossTenant-originalarrivaltime: 20 Apr 2016 15:25:05.1629 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 865fc51c-5fae-4322-98ef-0121a85df0b6
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BLUPR17MB0276
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/MldMNEtohzgKKT4H3nJM7Rxucg4>
Cc: "harald@alvestrand.no" <harald@alvestrand.no>
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, 20 Apr 2016 15:37:13 -0000

T24gNC8yMC8xNiwgMDg6MDIsICJpZXRmIG9uIGJlaGFsZiBvZiBKb2huIExldmluZSIgPGlldGYt
Ym91bmNlc0BpZXRmLm9yZyBvbiBiZWhhbGYgb2Ygam9obmxAdGF1Z2guY29tPiB3cm90ZToNCg0K
DQoNCj4NCj4NCj5JJ2QgYmUgcmF0aGVyIHN1cnByaXNlZCBpZiBhIGxvdCBvZiBuZXcgcGFydGlj
aXBhbnRzIGZyb20gQXJnZW50aW5hDQo+c2hvd2VkIHVwIGluIEJlcmxpbiwgYmVjYXVzZSBpZiB5
b3UgbGl2ZSBpbiwgc2F5LCBNZW5kb3phLCBpdCdzIG9yZGVycw0KPm9mIG1hZ25pdHVkZSBtb3Jl
IGV4cGVuc2l2ZSB0byBnZXQgdG8gQmVybGluIHRoYW4gdG8gQi5BLg0KDQpSaWdodC4NCg0KQWNj
b3JkaW5nIHRvIHBheXNjYWxlLmNvbSwgdGhlIG1lZGlhbiBzYWxhcnkgZm9yIGEgc29mdHdhcmUg
ZW5naW5lZXIgaW4gQnVlbm9zIEFpcmVzIGlzIEFSUyAxNzAsMDAwLCB3aGljaCBjdXJyZW50bHkg
dHJhbnNsYXRlcyB0byAkMTIsMDAwLiAgUGVyIHllYXIuICBJIGRvdWJ0IHRoYXQgdHJhdmVsbGlu
ZyBmcm9tIEJBIG9yIE1lbmRvemEgdG8gQmVybGluIGZvciBhIHdlZWsgY2FuIGJlIGRvbmUgYmVs
b3cgJDMwMDAsIHdoaWNoIHdvdWxkIGJlIGEgcXVhcnRlciBvZiB0aGVpciBhbm51YWwgaW5jb21l
LiAgVG8gbWUsIHRoYXQgc291bmRzIGxpa2Ugc2VsZi1zcG9uc29yZWQgdHJpcHMgYXJlIHByb2Jh
Ymx5IG91dCBvZiBxdWVzdGlvbiBldmVuIHRvIHRoZSBtb3N0IGVudGh1c2lhc3RpYywgdW5sZXNz
IHRoZXkgaGF2ZSBwZXJzb25hbCB3ZWFsdGggd2VsbCBhYm92ZSBhdmVyYWdlLiAgQW5kIEkgc29t
ZXdoYXQgZG91YnQgdGhhdCBsb2NhbCBjb21wYW5pZXMgc3dpbSBpbiBtb25leSBlaXRoZXIuICAN
Cg0KR2VuZXJhbGl6aW5nIHRoYXQ6IGV4cGVjdGluZyBsYXJnZSBzY2FsZSBwaHlzaWNhbCBwYXJ0
aWNpcGF0aW9uIGZyb20gZm9sa3MgaW4gZGV2ZWxvcGluZyBjb3VudHJpZXMgaXMgbmHDr3ZlLCBJ
TU8sIGV4Y2VwdCB3aGVuIHlvdSBtZWV0IGluIHRoYXQgcmVnaW9uLiAgVGhlIHJldHVybiBmb3Ig
b3VyIGludmVzdG1lbnQgaW4gdHJhdmVsaW5nIHRvIEJBIGhhcyB0byBiZSBtZWFzdXJlZCBvbiBv
dGhlciBzY2FsZXMuICBUaGUgZmFjdCB0aGF0IHNvIG1hbnkgbG9jYWxzIHNob3dlZCB1cCBwaHlz
aWNhbGx5IGF0IHRoZSBtZWV0aW5nIGFscmVhZHkgc3BlYWtzIGluIGZhdm9yLiAgSWYgdGhhdCBp
cyBmb2xsb3dlZCB1cCBieSByZW1vdGUvbWFpbGluZyBsaXN0IHBhcnRpY2lwYXRpb24gb3ZlciB0
aGUgbmV4dCBmZXcgeWVhcnMsIHRoYXQgd291bGQgYmUgZW5vdWdoIGZvciBtZS4NCg0KU3RlcGhh
bg0KDQo+DQo+UidzLA0KPkpvaG4NCj4NCg==


From nobody Wed Apr 20 11:18:59 2016
Return-Path: <housley@vigilsec.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 39A9E12DF7D; Wed, 20 Apr 2016 11:18:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.9
X-Spam-Level: 
X-Spam-Status: No, score=-101.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 NqQujU6OETuO; Wed, 20 Apr 2016 11:18:53 -0700 (PDT)
Received: from odin.smetech.net (x-bolt-wan.smeinc.net [209.135.219.146]) by ietfa.amsl.com (Postfix) with ESMTP id 75BDB12E2FC; Wed, 20 Apr 2016 11:18:42 -0700 (PDT)
Received: from localhost (ronin.smetech.net [209.135.209.5]) by odin.smetech.net (Postfix) with ESMTP id 27E2EF2402A; Wed, 20 Apr 2016 14:18:42 -0400 (EDT)
X-Virus-Scanned: amavisd-new at smetech.net
Received: from odin.smetech.net ([209.135.209.4]) by localhost (ronin.smeinc.net [209.135.209.5]) (amavisd-new, port 10024) with ESMTP id doprNttL2y6a; Wed, 20 Apr 2016 14:03:14 -0400 (EDT)
Received: from [192.168.2.100] (pool-108-51-128-219.washdc.fios.verizon.net [108.51.128.219]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 72E2D9A4001; Wed, 20 Apr 2016 14:18:41 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Subject: Re: [IAB] Call for Comment: <draft-iab-rfc3677bis> (IETF ISOC Board of Trustee Appointment Procedures)
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <6EC360A9-BE71-4EFF-A4DF-9D9F8CD0614F@harvard.edu>
Date: Wed, 20 Apr 2016 14:18:40 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <2BF65369-2400-46DC-88A4-5159A3B8FBAB@vigilsec.com>
References: <20160224175935.21103.69618.idtracker@ietfa.amsl.com> <6EC360A9-BE71-4EFF-A4DF-9D9F8CD0614F@harvard.edu>
To: Scott Bradner <sob@harvard.edu>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/EgkhvCkza3516ObFDkneTowEHY4>
Cc: IAB <iab@iab.org>, IETF <ietf@ietf.org>, "architecture-discuss@ietf.org" <architecture-discuss@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, 20 Apr 2016 18:18:55 -0000

Scott:

I cannot see how the change that you are proposing to the ISOC Bylaws =
has any impact on the content of rfc3677bis.  What am I missing?

If I am not missing anything, then it seems to me that waiting to move =
forward on this is counter to may of the other comments that we got =
about acting promptly to keep our document in sync with the current =
bylaws.

Russ

On Feb 25, 2016, at 7:27 AM, Bradner, Scott <sob@harvard.edu> wrote:

> re section 3.5 mid-term vacancies
>=20
> please hold off on this particular section for a bit - I am in the =
middle of proposing some changes=20
> to the ISOC bylaws - mostly to clear up some confusions - and one of =
these changes concerns IETF vacancy appointments
>=20
> the current bylaws do not limit when the IETF can appoint someone to =
fill a vacancy but do limit when such an
> appointment can take office to the start of the ISOC mid year meeting, =
when all new trustees take office - which might
> be a bit frustrating to the appointee
>=20
> I am proposing a bylaws update that will put the IETF appointment t =
fill a vacancy to be the same
> as it is for the chapters & org members - with until the next =
appointment cycle (to do otherwise
> provided unequal treatment for the IETF)
>=20
> in any case some change is needed to clarify the existing situation
>=20
> Scott
>=20
>> On Feb 24, 2016, at 12:59 PM, IAB Executive Administrative Manager =
<execd@iab.org> wrote:
>>=20
>> This is an announcement of an IETF-wide Call for Comment on
>> draft-iab-rfc3677bis-00.
>>=20
>> The document is being considered for publication as a Best Current=20
>> Practice RFC within the IAB stream, and is available for inspection=20=

>> here: https://datatracker.ietf.org/doc/draft-iab-rfc3677bis/
>>=20
>> The Call for Comment will last until 2016-03-23. Please send comments =
to
>> architecture-discuss@ietf.org and iab@iab.org.
>>=20
>>=20
>> Abstract
>>=20
>>  This memo, which obsoletes RFC3677, outlines the process by which =
the
>>  IETF makes a selection of an Internet Society (ISOC) Board of
>>  Trustees appointment.
>>=20
>=20


From nobody Wed Apr 20 11:41:28 2016
Return-Path: <sob@sobco.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 4AE4E12EBD0; Wed, 20 Apr 2016 11:41:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.109
X-Spam-Level: 
X-Spam-Status: No, score=-1.109 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RDNS_NONE=0.793, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=no 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 6qrqFfRDcU7I; Wed, 20 Apr 2016 11:41:23 -0700 (PDT)
Received: from sobco.sobco.com (unknown [136.248.127.164]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0B27912EE0D; Wed, 20 Apr 2016 11:41:19 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by sobco.sobco.com (Postfix) with ESMTP id 1FC5F1C6E1D9; Wed, 20 Apr 2016 14:41:18 -0400 (EDT)
X-Virus-Scanned: amavisd-new at sobco.com
Received: from sobco.sobco.com ([127.0.0.1]) by localhost (sobco.sobco.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eZwFmklsdskD; Wed, 20 Apr 2016 14:41:15 -0400 (EDT)
Received: from [10.251.213.164] (unknown [65.112.10.217]) by sobco.sobco.com (Postfix) with ESMTPSA id B228B1C6E1CE; Wed, 20 Apr 2016 14:41:15 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (1.0)
Subject: Re: [IAB] Call for Comment: <draft-iab-rfc3677bis> (IETF ISOC Board of Trustee Appointment Procedures)
From: "Scott O. Bradner" <sob@sobco.com>
X-Mailer: iPhone Mail (13E238)
In-Reply-To: <2BF65369-2400-46DC-88A4-5159A3B8FBAB@vigilsec.com>
Date: Wed, 20 Apr 2016 14:41:14 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <1606171A-73E6-4553-AFB4-9C5AE2C6B7DE@sobco.com>
References: <20160224175935.21103.69618.idtracker@ietfa.amsl.com> <6EC360A9-BE71-4EFF-A4DF-9D9F8CD0614F@harvard.edu> <2BF65369-2400-46DC-88A4-5159A3B8FBAB@vigilsec.com>
To: Russ Housley <housley@vigilsec.com>
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/bskkrYVE-ftwknZVabkTpctD7UI>
Cc: "architecture-discuss@ietf.org" <architecture-discuss@ietf.org>, IAB <iab@iab.org>, Scott Bradner <sob@harvard.edu>, IETF <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, 20 Apr 2016 18:41:24 -0000

My quick read of the vacancy process assumed an approach that made an appoin=
tment when a vacancy occurs and the  proposal is to have the IETF follow the=
 same process as the other groups that select trustees and add the seat to t=
he next selection cycle

I may have misread the 3677bis proposal
If so please correct me=20

Scott


Sent from my iPhone

> On Apr 20, 2016, at 2:18 PM, Russ Housley <housley@vigilsec.com> wrote:
>=20
> Scott:
>=20
> I cannot see how the change that you are proposing to the ISOC Bylaws has a=
ny impact on the content of rfc3677bis.  What am I missing?
>=20
> If I am not missing anything, then it seems to me that waiting to move for=
ward on this is counter to may of the other comments that we got about actin=
g promptly to keep our document in sync with the current bylaws.
>=20
> Russ
>=20
>> On Feb 25, 2016, at 7:27 AM, Bradner, Scott <sob@harvard.edu> wrote:
>>=20
>> re section 3.5 mid-term vacancies
>>=20
>> please hold off on this particular section for a bit - I am in the middle=
 of proposing some changes=20
>> to the ISOC bylaws - mostly to clear up some confusions - and one of thes=
e changes concerns IETF vacancy appointments
>>=20
>> the current bylaws do not limit when the IETF can appoint someone to fill=
 a vacancy but do limit when such an
>> appointment can take office to the start of the ISOC mid year meeting, wh=
en all new trustees take office - which might
>> be a bit frustrating to the appointee
>>=20
>> I am proposing a bylaws update that will put the IETF appointment t fill a=
 vacancy to be the same
>> as it is for the chapters & org members - with until the next appointment=
 cycle (to do otherwise
>> provided unequal treatment for the IETF)
>>=20
>> in any case some change is needed to clarify the existing situation
>>=20
>> Scott
>>=20
>>> On Feb 24, 2016, at 12:59 PM, IAB Executive Administrative Manager <exec=
d@iab.org> wrote:
>>>=20
>>> This is an announcement of an IETF-wide Call for Comment on
>>> draft-iab-rfc3677bis-00.
>>>=20
>>> The document is being considered for publication as a Best Current=20
>>> Practice RFC within the IAB stream, and is available for inspection=20
>>> here: https://datatracker.ietf.org/doc/draft-iab-rfc3677bis/
>>>=20
>>> The Call for Comment will last until 2016-03-23. Please send comments to=

>>> architecture-discuss@ietf.org and iab@iab.org.
>>>=20
>>>=20
>>> Abstract
>>>=20
>>> This memo, which obsoletes RFC3677, outlines the process by which the
>>> IETF makes a selection of an Internet Society (ISOC) Board of
>>> Trustees appointment.
>>>=20
>>=20
>=20


From nobody Wed Apr 20 11:43:35 2016
Return-Path: <sob@sobco.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 1054D12D82E; Wed, 20 Apr 2016 11:43:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.109
X-Spam-Level: 
X-Spam-Status: No, score=-1.109 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RDNS_NONE=0.793, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=no 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 575fIr6Y8nnO; Wed, 20 Apr 2016 11:43:26 -0700 (PDT)
Received: from sobco.sobco.com (unknown [136.248.127.164]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2735A12DB98; Wed, 20 Apr 2016 11:43:25 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by sobco.sobco.com (Postfix) with ESMTP id 55C141C6E297; Wed, 20 Apr 2016 14:43:24 -0400 (EDT)
X-Virus-Scanned: amavisd-new at sobco.com
Received: from sobco.sobco.com ([127.0.0.1]) by localhost (sobco.sobco.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0k1gU3t02IrQ; Wed, 20 Apr 2016 14:43:23 -0400 (EDT)
Received: from [10.251.213.164] (unknown [65.112.10.217]) by sobco.sobco.com (Postfix) with ESMTPSA id 0FDDA1C6E286; Wed, 20 Apr 2016 14:43:23 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (1.0)
Subject: Re: [IAB] Call for Comment: <draft-iab-rfc3677bis> (IETF ISOC Board of Trustee Appointment Procedures)
From: "Scott O. Bradner" <sob@sobco.com>
X-Mailer: iPhone Mail (13E238)
In-Reply-To: <2BF65369-2400-46DC-88A4-5159A3B8FBAB@vigilsec.com>
Date: Wed, 20 Apr 2016 14:43:22 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <4F6B020D-E3B7-48BE-9BD1-77D814D25F2E@sobco.com>
References: <20160224175935.21103.69618.idtracker@ietfa.amsl.com> <6EC360A9-BE71-4EFF-A4DF-9D9F8CD0614F@harvard.edu> <2BF65369-2400-46DC-88A4-5159A3B8FBAB@vigilsec.com>
To: Russ Housley <housley@vigilsec.com>
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/WLij-rETQqfVNt8fkYiR-USSvoA>
Cc: "architecture-discuss@ietf.org" <architecture-discuss@ietf.org>, IAB <iab@iab.org>, Scott Bradner <sob@harvard.edu>, IETF <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, 20 Apr 2016 18:43:32 -0000

Ps the trustees approved sending the by laws proposals out for comment and t=
hat will happen in the next few days

Scott


Sent from my iPhone

> On Apr 20, 2016, at 2:18 PM, Russ Housley <housley@vigilsec.com> wrote:
>=20
> Scott:
>=20
> I cannot see how the change that you are proposing to the ISOC Bylaws has a=
ny impact on the content of rfc3677bis.  What am I missing?
>=20
> If I am not missing anything, then it seems to me that waiting to move for=
ward on this is counter to may of the other comments that we got about actin=
g promptly to keep our document in sync with the current bylaws.
>=20
> Russ
>=20
>> On Feb 25, 2016, at 7:27 AM, Bradner, Scott <sob@harvard.edu> wrote:
>>=20
>> re section 3.5 mid-term vacancies
>>=20
>> please hold off on this particular section for a bit - I am in the middle=
 of proposing some changes=20
>> to the ISOC bylaws - mostly to clear up some confusions - and one of thes=
e changes concerns IETF vacancy appointments
>>=20
>> the current bylaws do not limit when the IETF can appoint someone to fill=
 a vacancy but do limit when such an
>> appointment can take office to the start of the ISOC mid year meeting, wh=
en all new trustees take office - which might
>> be a bit frustrating to the appointee
>>=20
>> I am proposing a bylaws update that will put the IETF appointment t fill a=
 vacancy to be the same
>> as it is for the chapters & org members - with until the next appointment=
 cycle (to do otherwise
>> provided unequal treatment for the IETF)
>>=20
>> in any case some change is needed to clarify the existing situation
>>=20
>> Scott
>>=20
>>> On Feb 24, 2016, at 12:59 PM, IAB Executive Administrative Manager <exec=
d@iab.org> wrote:
>>>=20
>>> This is an announcement of an IETF-wide Call for Comment on
>>> draft-iab-rfc3677bis-00.
>>>=20
>>> The document is being considered for publication as a Best Current=20
>>> Practice RFC within the IAB stream, and is available for inspection=20
>>> here: https://datatracker.ietf.org/doc/draft-iab-rfc3677bis/
>>>=20
>>> The Call for Comment will last until 2016-03-23. Please send comments to=

>>> architecture-discuss@ietf.org and iab@iab.org.
>>>=20
>>>=20
>>> Abstract
>>>=20
>>> This memo, which obsoletes RFC3677, outlines the process by which the
>>> IETF makes a selection of an Internet Society (ISOC) Board of
>>> Trustees appointment.
>>>=20
>>=20
>=20


From nobody Wed Apr 20 12:30:42 2016
Return-Path: <housley@vigilsec.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 2C74B12E4BF; Wed, 20 Apr 2016 12:30:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.9
X-Spam-Level: 
X-Spam-Status: No, score=-101.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 jZoFqpkyKN6Q; Wed, 20 Apr 2016 12:30:32 -0700 (PDT)
Received: from odin.smetech.net (x-bolt-wan.smeinc.net [209.135.219.146]) by ietfa.amsl.com (Postfix) with ESMTP id 10F7712E49C; Wed, 20 Apr 2016 12:30:32 -0700 (PDT)
Received: from localhost (ronin.smetech.net [209.135.209.5]) by odin.smetech.net (Postfix) with ESMTP id BB9DE9A4001; Wed, 20 Apr 2016 15:30:31 -0400 (EDT)
X-Virus-Scanned: amavisd-new at smetech.net
Received: from odin.smetech.net ([209.135.209.4]) by localhost (ronin.smeinc.net [209.135.209.5]) (amavisd-new, port 10024) with ESMTP id JX9z7OxTBewb; Wed, 20 Apr 2016 15:15:03 -0400 (EDT)
Received: from [192.168.2.100] (pool-108-51-128-219.washdc.fios.verizon.net [108.51.128.219]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id D0B95F2402A; Wed, 20 Apr 2016 15:30:30 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Subject: Re: [IAB] Call for Comment: <draft-iab-rfc3677bis> (IETF ISOC Board of Trustee Appointment Procedures)
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <1606171A-73E6-4553-AFB4-9C5AE2C6B7DE@sobco.com>
Date: Wed, 20 Apr 2016 15:30:30 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <6F1589B6-8408-4533-BBBF-5BFD7BE36756@vigilsec.com>
References: <20160224175935.21103.69618.idtracker@ietfa.amsl.com> <6EC360A9-BE71-4EFF-A4DF-9D9F8CD0614F@harvard.edu> <2BF65369-2400-46DC-88A4-5159A3B8FBAB@vigilsec.com> <1606171A-73E6-4553-AFB4-9C5AE2C6B7DE@sobco.com>
To: Scott Bradner <sob@sobco.com>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/aWgIp4uJz1q0L1cgoRNJb9wWGvI>
Cc: "architecture-discuss@ietf.org" <architecture-discuss@ietf.org>, IAB <iab@iab.org>, Scott Bradner <sob@harvard.edu>, IETF <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, 20 Apr 2016 19:30:35 -0000

Scott:

I think that the language can be aligned with very minimal changes.

If I have understood the potential change to the ISOC Bylaws, this
will work with the current bylaws and the poposed ones, if they are
approved.

OLD:

   This document describes the process for the general, annual
   appointment of ISOC Trustees to fill the seats of Trustees whose
   terms are ending.  However, if an IETF-appointed Trustee is unable to
   serve his or her full term, the IAB may, at its discretion,
   immediately select a replacement to serve the remainder of the term
   using the interim process defined in Section 3.5.1.  If the IAB does
   not invoke the interim process, the next annual selection process
   will fill the vacancy (if the vacant term does not end at that point)
   as well as the regular appointment for that selection cycle.

NEW:

   This document describes the process for the general, annual
   appointment of ISOC Trustees to fill the seats of Trustees whose
   terms are ending.  However, if an IETF-appointed Trustee is unable to
   serve his or her full term, the IAB may, at its discretion, select a
   replacement to serve the remainder of the term using the interim
   process defined in Section 3.5.1, with a start date consistent
   with the [ISOC-By-Laws].  If the IAB does not invoke the interim
   process, the next annual selection process will fill the vacancy
   (if the vacant term does not end at that point) as well as the
   regular appointment for that selection cycle.

Russ


On Apr 20, 2016, at 2:41 PM, Scott O. Bradner <sob@sobco.com> wrote:

> My quick read of the vacancy process assumed an approach that made an =
appointment when a vacancy occurs and the  proposal is to have the IETF =
follow the same process as the other groups that select trustees and add =
the seat to the next selection cycle
>=20
> I may have misread the 3677bis proposal
> If so please correct me=20
>=20
> Scott
>=20
>=20
> Sent from my iPhone
>=20
>> On Apr 20, 2016, at 2:18 PM, Russ Housley <housley@vigilsec.com> =
wrote:
>>=20
>> Scott:
>>=20
>> I cannot see how the change that you are proposing to the ISOC Bylaws =
has any impact on the content of rfc3677bis.  What am I missing?
>>=20
>> If I am not missing anything, then it seems to me that waiting to =
move forward on this is counter to may of the other comments that we got =
about acting promptly to keep our document in sync with the current =
bylaws.
>>=20
>> Russ
>>=20
>>> On Feb 25, 2016, at 7:27 AM, Bradner, Scott <sob@harvard.edu> wrote:
>>>=20
>>> re section 3.5 mid-term vacancies
>>>=20
>>> please hold off on this particular section for a bit - I am in the =
middle of proposing some changes=20
>>> to the ISOC bylaws - mostly to clear up some confusions - and one of =
these changes concerns IETF vacancy appointments
>>>=20
>>> the current bylaws do not limit when the IETF can appoint someone to =
fill a vacancy but do limit when such an
>>> appointment can take office to the start of the ISOC mid year =
meeting, when all new trustees take office - which might
>>> be a bit frustrating to the appointee
>>>=20
>>> I am proposing a bylaws update that will put the IETF appointment t =
fill a vacancy to be the same
>>> as it is for the chapters & org members - with until the next =
appointment cycle (to do otherwise
>>> provided unequal treatment for the IETF)
>>>=20
>>> in any case some change is needed to clarify the existing situation
>>>=20
>>> Scott
>>>=20
>>>> On Feb 24, 2016, at 12:59 PM, IAB Executive Administrative Manager =
<execd@iab.org> wrote:
>>>>=20
>>>> This is an announcement of an IETF-wide Call for Comment on
>>>> draft-iab-rfc3677bis-00.
>>>>=20
>>>> The document is being considered for publication as a Best Current=20=

>>>> Practice RFC within the IAB stream, and is available for inspection=20=

>>>> here: https://datatracker.ietf.org/doc/draft-iab-rfc3677bis/
>>>>=20
>>>> The Call for Comment will last until 2016-03-23. Please send =
comments to
>>>> architecture-discuss@ietf.org and iab@iab.org.
>>>>=20
>>>>=20
>>>> Abstract
>>>>=20
>>>> This memo, which obsoletes RFC3677, outlines the process by which =
the
>>>> IETF makes a selection of an Internet Society (ISOC) Board of
>>>> Trustees appointment.
>>>>=20
>>>=20
>>=20


From nobody Wed Apr 20 12:41:15 2016
Return-Path: <sob@sobco.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 8451912E61C; Wed, 20 Apr 2016 12:41:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.109
X-Spam-Level: 
X-Spam-Status: No, score=-1.109 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RDNS_NONE=0.793, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=no 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 4ano4xVxGIrt; Wed, 20 Apr 2016 12:41:12 -0700 (PDT)
Received: from sobco.sobco.com (unknown [136.248.127.164]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 581BE12E52A; Wed, 20 Apr 2016 12:41:06 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by sobco.sobco.com (Postfix) with ESMTP id 7B5851C6F25C; Wed, 20 Apr 2016 15:41:05 -0400 (EDT)
X-Virus-Scanned: amavisd-new at sobco.com
Received: from sobco.sobco.com ([127.0.0.1]) by localhost (sobco.sobco.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0mvJhl_VEONP; Wed, 20 Apr 2016 15:41:04 -0400 (EDT)
Received: from golem.sobco.com (golem.sobco.com [136.248.127.162]) by sobco.sobco.com (Postfix) with ESMTPSA id 3F5211C6F245; Wed, 20 Apr 2016 15:41:04 -0400 (EDT)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Subject: Re: [IAB] Call for Comment: <draft-iab-rfc3677bis> (IETF ISOC Board of Trustee Appointment Procedures)
From: "Scott O. Bradner" <sob@sobco.com>
In-Reply-To: <6F1589B6-8408-4533-BBBF-5BFD7BE36756@vigilsec.com>
Date: Wed, 20 Apr 2016 15:41:04 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <7D1073A2-E7F5-4B0B-A70D-5F5218F4CB09@sobco.com>
References: <20160224175935.21103.69618.idtracker@ietfa.amsl.com> <6EC360A9-BE71-4EFF-A4DF-9D9F8CD0614F@harvard.edu> <2BF65369-2400-46DC-88A4-5159A3B8FBAB@vigilsec.com> <1606171A-73E6-4553-AFB4-9C5AE2C6B7DE@sobco.com> <6F1589B6-8408-4533-BBBF-5BFD7BE36756@vigilsec.com>
To: Russ Housley <housley@vigilsec.com>
X-Mailer: Apple Mail (2.3124)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/xLEPfyL7TsSNXEkt5pc59KtWHh4>
Cc: IAB <iab@iab.org>, IETF <ietf@ietf.org>, "architecture-discuss@ietf.org" <architecture-discuss@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, 20 Apr 2016 19:41:13 -0000

that is not actually consistent

the proposed bylaws change says that the seat is added to the next =
selection cycle
not that someone gets picked outside of the cycle and only gets seated =
when the=20
people seated by the next selection cycle get seated

it would seem to be more straightforward to just say =E2=80=9Cadded to =
the next selection cycle=E2=80=9D and
I think it would be easier on the IETF to not run multiple selection =
processes (perhaps overlapping)=20
in a year

Scott

> On Apr 20, 2016, at 3:30 PM, Russ Housley <housley@vigilsec.com> =
wrote:
>=20
> Scott:
>=20
> I think that the language can be aligned with very minimal changes.
>=20
> If I have understood the potential change to the ISOC Bylaws, this
> will work with the current bylaws and the poposed ones, if they are
> approved.
>=20
> OLD:
>=20
>   This document describes the process for the general, annual
>   appointment of ISOC Trustees to fill the seats of Trustees whose
>   terms are ending.  However, if an IETF-appointed Trustee is unable =
to
>   serve his or her full term, the IAB may, at its discretion,
>   immediately select a replacement to serve the remainder of the term
>   using the interim process defined in Section 3.5.1.  If the IAB does
>   not invoke the interim process, the next annual selection process
>   will fill the vacancy (if the vacant term does not end at that =
point)
>   as well as the regular appointment for that selection cycle.
>=20
> NEW:
>=20
>   This document describes the process for the general, annual
>   appointment of ISOC Trustees to fill the seats of Trustees whose
>   terms are ending.  However, if an IETF-appointed Trustee is unable =
to
>   serve his or her full term, the IAB may, at its discretion, select a
>   replacement to serve the remainder of the term using the interim
>   process defined in Section 3.5.1, with a start date consistent
>   with the [ISOC-By-Laws].  If the IAB does not invoke the interim
>   process, the next annual selection process will fill the vacancy
>   (if the vacant term does not end at that point) as well as the
>   regular appointment for that selection cycle.
>=20
> Russ
>=20
>=20
> On Apr 20, 2016, at 2:41 PM, Scott O. Bradner <sob@sobco.com> wrote:
>=20
>> My quick read of the vacancy process assumed an approach that made an =
appointment when a vacancy occurs and the  proposal is to have the IETF =
follow the same process as the other groups that select trustees and add =
the seat to the next selection cycle
>>=20
>> I may have misread the 3677bis proposal
>> If so please correct me=20
>>=20
>> Scott
>>=20
>>=20
>> Sent from my iPhone
>>=20
>>> On Apr 20, 2016, at 2:18 PM, Russ Housley <housley@vigilsec.com> =
wrote:
>>>=20
>>> Scott:
>>>=20
>>> I cannot see how the change that you are proposing to the ISOC =
Bylaws has any impact on the content of rfc3677bis.  What am I missing?
>>>=20
>>> If I am not missing anything, then it seems to me that waiting to =
move forward on this is counter to may of the other comments that we got =
about acting promptly to keep our document in sync with the current =
bylaws.
>>>=20
>>> Russ
>>>=20
>>>> On Feb 25, 2016, at 7:27 AM, Bradner, Scott <sob@harvard.edu> =
wrote:
>>>>=20
>>>> re section 3.5 mid-term vacancies
>>>>=20
>>>> please hold off on this particular section for a bit - I am in the =
middle of proposing some changes=20
>>>> to the ISOC bylaws - mostly to clear up some confusions - and one =
of these changes concerns IETF vacancy appointments
>>>>=20
>>>> the current bylaws do not limit when the IETF can appoint someone =
to fill a vacancy but do limit when such an
>>>> appointment can take office to the start of the ISOC mid year =
meeting, when all new trustees take office - which might
>>>> be a bit frustrating to the appointee
>>>>=20
>>>> I am proposing a bylaws update that will put the IETF appointment t =
fill a vacancy to be the same
>>>> as it is for the chapters & org members - with until the next =
appointment cycle (to do otherwise
>>>> provided unequal treatment for the IETF)
>>>>=20
>>>> in any case some change is needed to clarify the existing situation
>>>>=20
>>>> Scott
>>>>=20
>>>>> On Feb 24, 2016, at 12:59 PM, IAB Executive Administrative Manager =
<execd@iab.org> wrote:
>>>>>=20
>>>>> This is an announcement of an IETF-wide Call for Comment on
>>>>> draft-iab-rfc3677bis-00.
>>>>>=20
>>>>> The document is being considered for publication as a Best Current=20=

>>>>> Practice RFC within the IAB stream, and is available for =
inspection=20
>>>>> here: https://datatracker.ietf.org/doc/draft-iab-rfc3677bis/
>>>>>=20
>>>>> The Call for Comment will last until 2016-03-23. Please send =
comments to
>>>>> architecture-discuss@ietf.org and iab@iab.org.
>>>>>=20
>>>>>=20
>>>>> Abstract
>>>>>=20
>>>>> This memo, which obsoletes RFC3677, outlines the process by which =
the
>>>>> IETF makes a selection of an Internet Society (ISOC) Board of
>>>>> Trustees appointment.
>>>>>=20
>>>>=20
>>>=20
>=20


From nobody Wed Apr 20 12:51:33 2016
Return-Path: <sob@sobco.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 F140212E4B9; Wed, 20 Apr 2016 12:51:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.109
X-Spam-Level: 
X-Spam-Status: No, score=-1.109 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RDNS_NONE=0.793, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=no 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 Ajutoqm9PwRD; Wed, 20 Apr 2016 12:51:29 -0700 (PDT)
Received: from sobco.sobco.com (unknown [136.248.127.164]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8B1BB12E4C7; Wed, 20 Apr 2016 12:51:28 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by sobco.sobco.com (Postfix) with ESMTP id C5EB01C6F6D3; Wed, 20 Apr 2016 15:51:27 -0400 (EDT)
X-Virus-Scanned: amavisd-new at sobco.com
Received: from sobco.sobco.com ([127.0.0.1]) by localhost (sobco.sobco.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QssQqqeWbcuq; Wed, 20 Apr 2016 15:51:27 -0400 (EDT)
Received: from golem.sobco.com (golem.sobco.com [136.248.127.162]) by sobco.sobco.com (Postfix) with ESMTPSA id 42D151C6F6C5; Wed, 20 Apr 2016 15:51:27 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Subject: Re: [IAB] Call for Comment: <draft-iab-rfc3677bis> (IETF ISOC Board of Trustee Appointment Procedures)
From: "Scott O. Bradner" <sob@sobco.com>
In-Reply-To: <6F1589B6-8408-4533-BBBF-5BFD7BE36756@vigilsec.com>
Date: Wed, 20 Apr 2016 15:51:27 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <E6209F2D-39BE-4CF3-B023-E3A8DDBF0603@sobco.com>
References: <20160224175935.21103.69618.idtracker@ietfa.amsl.com> <6EC360A9-BE71-4EFF-A4DF-9D9F8CD0614F@harvard.edu> <2BF65369-2400-46DC-88A4-5159A3B8FBAB@vigilsec.com> <1606171A-73E6-4553-AFB4-9C5AE2C6B7DE@sobco.com> <6F1589B6-8408-4533-BBBF-5BFD7BE36756@vigilsec.com>
To: Russ Housley <housley@vigilsec.com>
X-Mailer: Apple Mail (2.3124)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/bVk1hPK3z4aOcFhUoyRgVkroKjc>
Cc: IAB <iab@iab.org>, IETF <ietf@ietf.org>, "architecture-discuss@ietf.org" <architecture-discuss@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, 20 Apr 2016 19:51:30 -0000

since we are talking about it - here is the proposal - it would have =
come out in the next few days anyway

Current bylaws text in Article II section 3:
=
--------------------------------------------------------------------------=
----------------------------------------------------------------------
Any vacancy for a Board seat filled by election shall be filled by =
including the open seat in the next regular election or selection =
process for that seat after the vacancy occurs so long as a call for =
nominations has not been announced. If an election includes seats with =
terms or remaining terms that are unequal in length, then the seat with =
the longest term shall be filled by the candidate receiving the most =
votes, the seat with the next longest term shall be filled by the =
candidate receiving the next most votes, and so on.
=20
Any vacancy for a board seat filled by the Internet Engineering Task =
Force shall be filled by the Internet Engineering Task Force using a =
process of their own choosing.
=20
Any Trustee elected or appointed by the above processes to fill a =
vacancy will hold office commencing at the start of the Annual General =
Meeting (AGM) following their election or appointment.


Proposal:
=
--------------------------------------------------------------------------=
----------------------------------------------------------------------
remove "or selection" from the first sentence of the first paragraph.
Reason:

to be consistent with proposed change to Article 2 section 1.


Proposal: replace 2nd paragraph with the following:
=
--------------------------------------------------------------------------=
----------------------------------------------------------------------
Any vacancy for a Board seat filled by the Internet Engineering Task =
Force shall be filled by including the open seat in the next regular =
appointment process for that seat after the vacancy occurs so long as a =
call for candidates has not been announced. If an appointment process =
includes seats with terms or remaining terms that are unequal in length, =
then Internet Engineering Task Force shall decide which appointment is =
to receive which term though a mechanism of its own choosing.


Reason:
=
--------------------------------------------------------------------------=
----------------------------------------------------------------------
to remove the confusion that would result if the IETF were to fill a =
vacancy and the selection would not be able to be seated until the next =
AGM and to make the vacancy processes consistent for all trustees=


From nobody Wed Apr 20 13:14:18 2016
Return-Path: <sob@sobco.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 A883112DC75; Wed, 20 Apr 2016 13:14:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.109
X-Spam-Level: 
X-Spam-Status: No, score=-1.109 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RDNS_NONE=0.793, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=no 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 ep-wP-7fD-3g; Wed, 20 Apr 2016 13:14:13 -0700 (PDT)
Received: from sobco.sobco.com (unknown [136.248.127.164]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A0FFA12DB4B; Wed, 20 Apr 2016 13:14:12 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by sobco.sobco.com (Postfix) with ESMTP id A4D9B1C700A7; Wed, 20 Apr 2016 16:14:11 -0400 (EDT)
X-Virus-Scanned: amavisd-new at sobco.com
Received: from sobco.sobco.com ([127.0.0.1]) by localhost (sobco.sobco.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eN6oWI2ArKwq; Wed, 20 Apr 2016 16:14:10 -0400 (EDT)
Received: from [10.0.1.16] (173-166-5-69-newengland.hfc.comcastbusiness.net [173.166.5.69]) by sobco.sobco.com (Postfix) with ESMTPSA id 1F5EB1C70096; Wed, 20 Apr 2016 16:14:10 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Subject: Re: [IAB] Call for Comment: <draft-iab-rfc3677bis> (IETF ISOC Board of Trustee Appointment Procedures)
From: "Scott O. Bradner" <sob@sobco.com>
In-Reply-To: <E6209F2D-39BE-4CF3-B023-E3A8DDBF0603@sobco.com>
Date: Wed, 20 Apr 2016 16:14:26 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <AA188E12-DC0C-48B2-A5E9-8106686B5457@sobco.com>
References: <20160224175935.21103.69618.idtracker@ietfa.amsl.com> <6EC360A9-BE71-4EFF-A4DF-9D9F8CD0614F@harvard.edu> <2BF65369-2400-46DC-88A4-5159A3B8FBAB@vigilsec.com> <1606171A-73E6-4553-AFB4-9C5AE2C6B7DE@sobco.com> <6F1589B6-8408-4533-BBBF-5BFD7BE36756@vigilsec.com> <E6209F2D-39BE-4CF3-B023-E3A8DDBF0603@sobco.com>
To: Russ Housley <housley@vigilsec.com>
X-Mailer: Apple Mail (2.3124)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/mFcJs0AdtlnrDeR_FPdiFXCQPpk>
Cc: IAB <iab@iab.org>, IETF <ietf@ietf.org>, "architecture-discuss@ietf.org" <architecture-discuss@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, 20 Apr 2016 20:14:14 -0000

one other thing I should make clear - this is a proposal and the ISOC =
Board will be asking for input on it
it should not be seen as a fait accompli  - a special address is being =
setup for the comments & the request will
be sent out in the next few days

Scott



> On Apr 20, 2016, at 3:51 PM, Scott O. Bradner <sob@sobco.com> wrote:
>=20
> since we are talking about it - here is the proposal - it would have =
come out in the next few days anyway
>=20
> Current bylaws text in Article II section 3:
> =
--------------------------------------------------------------------------=
----------------------------------------------------------------------
> Any vacancy for a Board seat filled by election shall be filled by =
including the open seat in the next regular election or selection =
process for that seat after the vacancy occurs so long as a call for =
nominations has not been announced. If an election includes seats with =
terms or remaining terms that are unequal in length, then the seat with =
the longest term shall be filled by the candidate receiving the most =
votes, the seat with the next longest term shall be filled by the =
candidate receiving the next most votes, and so on.
>=20
> Any vacancy for a board seat filled by the Internet Engineering Task =
Force shall be filled by the Internet Engineering Task Force using a =
process of their own choosing.
>=20
> Any Trustee elected or appointed by the above processes to fill a =
vacancy will hold office commencing at the start of the Annual General =
Meeting (AGM) following their election or appointment.
>=20
>=20
> Proposal:
> =
--------------------------------------------------------------------------=
----------------------------------------------------------------------
> remove "or selection" from the first sentence of the first paragraph.
> Reason:
>=20
> to be consistent with proposed change to Article 2 section 1.
>=20
>=20
> Proposal: replace 2nd paragraph with the following:
> =
--------------------------------------------------------------------------=
----------------------------------------------------------------------
> Any vacancy for a Board seat filled by the Internet Engineering Task =
Force shall be filled by including the open seat in the next regular =
appointment process for that seat after the vacancy occurs so long as a =
call for candidates has not been announced. If an appointment process =
includes seats with terms or remaining terms that are unequal in length, =
then Internet Engineering Task Force shall decide which appointment is =
to receive which term though a mechanism of its own choosing.
>=20
>=20
> Reason:
> =
--------------------------------------------------------------------------=
----------------------------------------------------------------------
> to remove the confusion that would result if the IETF were to fill a =
vacancy and the selection would not be able to be seated until the next =
AGM and to make the vacancy processes consistent for all trustees


From nobody Wed Apr 20 13:26:42 2016
Return-Path: <dave@taht.net>
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 44CC712E6B4 for <ietf@ietfa.amsl.com>; Wed, 20 Apr 2016 13:26:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.897
X-Spam-Level: 
X-Spam-Status: No, score=-2.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.996, SPF_PASS=-0.001] 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 CUWUjdbJXxVL for <ietf@ietfa.amsl.com>; Wed, 20 Apr 2016 13:26:36 -0700 (PDT)
Received: from mail.taht.net (mail.taht.net [176.58.107.8]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 399B912E6AC for <ietf@ietf.org>; Wed, 20 Apr 2016 13:26:36 -0700 (PDT)
Received: from dair-1972.gw.taht.net (c-73-252-201-217.hsd1.ca.comcast.net [73.252.201.217]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.taht.net (Postfix) with ESMTPSA id 38C8C21312 for <ietf@ietf.org>; Wed, 20 Apr 2016 20:26:34 +0000 (UTC)
Subject: Re: [aqm] Last Call: <draft-ietf-aqm-eval-guidelines-11.txt> (AQM Characterization Guidelines) to Informational RFC
References: <20160420124713.32376.24588.idtracker@ietfa.amsl.com>
To: IETF discussion list <ietf@ietf.org>
From: =?UTF-8?Q?Dave_T=c3=a4ht?= <dave@taht.net>
Message-ID: <5717E73E.9030501@taht.net>
Date: Wed, 20 Apr 2016 13:31:58 -0700
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:38.0) Gecko/20100101 Thunderbird/38.7.0
MIME-Version: 1.0
In-Reply-To: <20160420124713.32376.24588.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/NzxZhMvP2JGurCRa6gEOusW-Az0>
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, 20 Apr 2016 20:26:38 -0000

My basic objection to this entire draft is that it needs to be made
executable in some benchmarking suite before being considered as a
standard.

While it has many seemingly desirable stats and figures
few have been demonstrated as useful or used in the real world, nor have
any of the aqms under evaluation already been tested under it.

This has been my steady objection to it from day one, and as a
co-developer of a benchmark suite (flent.org) that *does* rigorously
explore some of the complexities aqm and fq technologies introduce,
with suitably complex tests, topologies, and graphs, I have long been
doubtful that the simple metrics and models used here were useful or
sufficient.

I have given detailed critiques of each metric to the wg before, and
could again, but my main point remained:

Rough consensus *and* Running Code is needed here.

And with that, I'd stopped paying attention to it, until code materialized.

On 4/20/16 5:47 AM, The IESG wrote:
> 
> The IESG has received a request from the Active Queue Management and
> Packet Scheduling WG (aqm) to consider the following document:
> - 'AQM Characterization Guidelines'
>   <draft-ietf-aqm-eval-guidelines-11.txt> as Informational RFC
> 
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action. Please send substantive comments to the
> ietf@ietf.org mailing lists by 2016-05-04. Exceptionally, comments may be
> sent to iesg@ietf.org instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting.
> 
> Abstract
> 
> 
>    Unmanaged large buffers in today's networks have given rise to a slew
>    of performance issues.  These performance issues can be addressed by
>    some form of Active Queue Management (AQM) mechanism, optionally in
>    combination with a packet scheduling scheme such as fair queuing.
>    This document describes various criteria for performing precautionary
>    characterizations of AQM schemes.
> 
> 
> 
> 
> The file can be obtained via
> https://datatracker.ietf.org/doc/draft-ietf-aqm-eval-guidelines/
> 
> IESG discussion can be tracked via
> https://datatracker.ietf.org/doc/draft-ietf-aqm-eval-guidelines/ballot/
> 
> 
> No IPR declarations have been submitted directly on this I-D.
> 
> 
> _______________________________________________
> aqm mailing list
> aqm@ietf.org
> https://www.ietf.org/mailman/listinfo/aqm
> 


From nobody Wed Apr 20 18:08:00 2016
Return-Path: <adam@nostrum.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 D797312E55C for <ietf@ietfa.amsl.com>; Wed, 20 Apr 2016 18:07:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.896
X-Spam-Level: 
X-Spam-Status: No, score=-2.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.996] 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 AfDLsTrzlUaB for <ietf@ietfa.amsl.com>; Wed, 20 Apr 2016 18:07:57 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (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 9C38512E555 for <ietf@ietf.org>; Wed, 20 Apr 2016 18:07:57 -0700 (PDT)
Received: from Orochi.local (99-152-145-110.lightspeed.dllstx.sbcglobal.net [99.152.145.110]) (authenticated bits=0) by nostrum.com (8.15.2/8.14.9) with ESMTPSA id u3L17otY035293 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Wed, 20 Apr 2016 20:07:51 -0500 (CDT) (envelope-from adam@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host 99-152-145-110.lightspeed.dllstx.sbcglobal.net [99.152.145.110] claimed to be Orochi.local
Subject: Re: Interim step on meetings site feedback for sites currently under active consideration
To: thomas nadeau <tnadeau@lucidvision.com>, Harald Alvestrand <harald@alvestrand.no>
References: <20160418161552.9368.65562.idtracker@ietfa.amsl.com> <8fb376e11631f9ddf73f9385ec5472c3.squirrel@www.trepanning.net> <57151C55.30206@gmail.com> <54D9A539-6409-4692-85F6-E4837E823AAE@gmail.com> <CAPt1N1n+676sAWFLee3oUGUgnTNHh95yFgrsmyjB5VbSmF-=XQ@mail.gmail.com> <CAKe6YvPGufULDN=SLbR8YZ-7-tUj-H18U4h4JTH7_S3UJKvRbw@mail.gmail.com> <57175E85.2030804@alvestrand.no> <60F23053-67F2-4A6E-A9C8-4E9681585BBD@lucidvision.com>
From: Adam Roach <adam@nostrum.com>
Message-ID: <571827E6.9090307@nostrum.com>
Date: Wed, 20 Apr 2016 20:07:50 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:38.0) Gecko/20100101 Thunderbird/38.7.2
MIME-Version: 1.0
In-Reply-To: <60F23053-67F2-4A6E-A9C8-4E9681585BBD@lucidvision.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/CKYNzk7bOEPCCz8dwwy5eCDH5ms>
Cc: 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, 21 Apr 2016 01:07:59 -0000

On 4/20/16 08:26, thomas nadeau wrote:
>
>> On Apr 20, 2016, at 6:48 AM, Harald Alvestrand <harald@alvestrand.no> wrote:
>>
>> ...
>> If we see a large cohort of first-time Buenos Aires attendees show up at
>> later meetings (Berlin being the first chance for them to show), we have
>> a strong signal that they thought it was worth it, and likely that
>> having the meeting in BA helped the community by helping recruit them.
>> Case closed (apart from some corner case possibilities I'm sure we,
>> being engineers, can all imagine).
>>
>> If we don't see such a cohort, we need to dig deeper.
> Or perhaps wonder why we should concern ourselves with this at all?
>

Because it's their Internet, too.

/a


From nobody Wed Apr 20 19:09:45 2016
Return-Path: <melinda.shore@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 13ECA12DD55 for <ietf@ietfa.amsl.com>; Wed, 20 Apr 2016 19:09:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 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, RCVD_IN_DNSWL_LOW=-0.7, 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 HedmH-xKelgT for <ietf@ietfa.amsl.com>; Wed, 20 Apr 2016 19:09:42 -0700 (PDT)
Received: from mail-pf0-x234.google.com (mail-pf0-x234.google.com [IPv6:2607:f8b0:400e:c00::234]) (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 85BBE12DD23 for <ietf@ietf.org>; Wed, 20 Apr 2016 19:09:42 -0700 (PDT)
Received: by mail-pf0-x234.google.com with SMTP id 184so24538383pff.0 for <ietf@ietf.org>; Wed, 20 Apr 2016 19:09:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=subject:references:to:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding; bh=uiibO/QpKOPm+vFdqAjU0xJdipfmtalYGDqo9i2GShs=; b=Pk5w+YafWXCssA+MDlf+B0u4wuKXr+9SB+13Be4tLn62VpOCguiKAlOTbRTXdeOkzK jC0lIS9DI+mdGrhvuV+nB5p2t1ArzQLd9m5IoF4ev/Gh8pmgY+aa2JVIhYu8U8Xoeh6I nLAspKzWnG22TtDkuWvSWUqmU2sAwROt2VE4Cgkr67WGCeODK7IVYwA6rfI5qhSN3PeE jB0KldjjHwlZSCDsOGNiSq6H209FXJgY7fB6ezgnym/pvjwYaxojxtJa5XkyWdJfjA/s So+CULd6QLNkFE2bhEU3CEubK9XQ3l4ObpIoIHFcXkge8pvpd3xkTvV6P7H0N1fPxJrG zK9A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:references:to:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=uiibO/QpKOPm+vFdqAjU0xJdipfmtalYGDqo9i2GShs=; b=fM4/kUZLemlPVFj8rTMDVoZ5li3ahJ3D7gjnWAKD9sVE3jtwbFwKmMDl7M+Ncp7oDu 39gqt4CtbLrGiwwouvVgXSEIlcQ+F64uQKP76dHF0LgqhePg8O0pIWyrz6Jk3rvxfNp2 JLS5vN4Z51oISinZDRubH+feVRdk78j8px1w0RFZtkNQEyRyniSdZN06f+l0Ymv8ip80 lBINzM/LcjLlLdf1m+0QSlm6yBueXY3qA+84tVxCL7hp3elwFAa62yKj1g+pRPugtkOA A2k6tIOYneonmYHMfv6w1cqH9L1qnJ2Dae37eOfF7c9vmC54Xh8+MVg1EyUP8gYxCt8K Sz3w==
X-Gm-Message-State: AOPr4FWkrIjvUF9gzdkE5E96Jgrcmbj8CMwgSS2jlX3Cxdav45YHH+6vXn/n1DrwiOjSPw==
X-Received: by 10.98.89.22 with SMTP id n22mr17001385pfb.55.1461204582021; Wed, 20 Apr 2016 19:09:42 -0700 (PDT)
Received: from Melindas-MacBook-Pro.local (216-67-58-191-radius.dynamic.acsalaska.net. [216.67.58.191]) by smtp.googlemail.com with ESMTPSA id uw2sm310926pac.10.2016.04.20.19.09.40 for <ietf@ietf.org> (version=TLSv1/SSLv3 cipher=OTHER); Wed, 20 Apr 2016 19:09:41 -0700 (PDT)
Subject: Re: Interim step on meetings site feedback for sites currently under active consideration
References: <57183308.7090108@gmail.com>
To: ietf <ietf@ietf.org>
From: Melinda Shore <melinda.shore@gmail.com>
X-Forwarded-Message-Id: <57183308.7090108@gmail.com>
Message-ID: <57183686.8000307@gmail.com>
Date: Wed, 20 Apr 2016 18:10:14 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:38.0) Gecko/20100101 Thunderbird/38.6.0
MIME-Version: 1.0
In-Reply-To: <57183308.7090108@gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/YuFzMWtg-2D7SptP8bub5_dYMWw>
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, 21 Apr 2016 02:09:44 -0000

On 4/20/16 5:07 PM, Adam Roach wrote:
> On 4/20/16 08:26, thomas nadeau wrote:
>>
>>> On Apr 20, 2016, at 6:48 AM, Harald Alvestrand <harald@alvestrand.no>
>>> wrote:
>>> If we don't see such a cohort, we need to dig deeper.
>> Or perhaps wonder why we should concern ourselves with this at all?
> Because it's their Internet, too.

I'm not sure that's actually responsive.  The internet "belongs
to" uncountable numbers of people who will never, ever participate
in making protocol standards.

If people are not participating in mailing lists, reviewing
documents, and so on, it's not at all clear to me why meeting
in their corner of the world is going to change anything.
Historically it does not seem to have been very effective.
I do think that what Nalini is doing (putting together
document review teams/study groups for new participants)
seems likely to be more effective than changing meeting
venues, and I'm very curious to see how that works out.

Personally, I'm completely unfunded and geographically
remote but still chair a working group, belong to directorates,
author drafts, and so on.  For me, the expectation that we
will attend meetings in person every single time is a
much bigger barrier to participation than having the meetings
someplace inconvenient (i.e. having to travel at all is far
more onerous than having to spend two days in transit if I do
travel), and I'd really like to see us let go of expectations
that IETF participation means going to meetings (particularly
since it's not how we're *supposed* to work, according to
our own process documents).

I expect that this discussion, coupled with the repeat-ad-
infinitum discussion of what's required of IETF leadership
positions makes it how clear just how deeply into the pockets
of the big network gizmo manufacturers the IETF really is.

Melinda




From nobody Wed Apr 20 19:41:46 2016
Return-Path: <vinays@cisco.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 1BE7D12E8C1; Wed, 20 Apr 2016 19:41:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.517
X-Spam-Level: 
X-Spam-Status: No, score=-15.517 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.996, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 ZKYzJrCrWORr; Wed, 20 Apr 2016 19:41:37 -0700 (PDT)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4686A12E89F; Wed, 20 Apr 2016 19:41:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=8613; q=dns/txt; s=iport; t=1461206497; x=1462416097; h=subject:to:references:cc:from:message-id:date: mime-version:in-reply-to:content-transfer-encoding; bh=jL/v91HQ5BkL79NxegKdIs2EPo/E9T7mLI6NOo3oPcs=; b=bHxQBDPdfWCa6FphAPpqbwB5OgvD5rYOeL9+tsnEIjZZVbhJ+YRY7W0E tdwi2Vm5dc9IhyLQlV5HSvV1pHcMa18X168VT4KI+Ba3qFYSLLgCphH4i 8RnaZICfLH4v82lzn/MuRhVWcM1dzDjPwfSTposL7oIGZT8qtF46oRreW k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AeAgDFPBhX/4gNJK1egzhTfblxAQ2Bc?= =?us-ascii?q?iKFbAKBRTgUAQEBAQEBAWUnhEEBAQEDASMPAQVAAQULCwkLBAICBRYLAgIJAwI?= =?us-ascii?q?BAgFFBgEMCAEBBYgZCA6tU5EQAQEBAQEBAQECAQEBAQEBAQEYfIUkhEyEIAEBg?= =?us-ascii?q?x2CVgEEjVOFS4RxghqDYYgZgWZOg3+DBoVXhiOJCh4BAUKEBCAwAYcSgTQBAQE?=
X-IronPort-AV: E=Sophos;i="5.24,512,1454976000"; d="scan'208";a="94149703"
Received: from alln-core-3.cisco.com ([173.36.13.136]) by rcdn-iport-8.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 21 Apr 2016 02:41:35 +0000
Received: from [10.82.241.140] (rtp-vpn2-396.cisco.com [10.82.241.140]) (authenticated bits=0) by alln-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id u3L2fY4D031637 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Thu, 21 Apr 2016 02:41:35 GMT
Subject: Re: Gen-ART Telechat review of draft-ietf-tictoc-ptp-mib-08
To: Peter Yee <peter@akayla.com>, draft-ietf-tictoc-ptp-mib.all@ietf.org
References: <D3393DAB.16AA3%peter@akayla.com>
From: vinays <vinays@cisco.com>
Message-ID: <57183DDE.5040309@cisco.com>
Date: Wed, 20 Apr 2016 22:41:34 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:38.0) Gecko/20100101 Thunderbird/38.7.2
MIME-Version: 1.0
In-Reply-To: <D3393DAB.16AA3%peter@akayla.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
X-Authenticated-User: vinays
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/XglFMt_IDpgXWxBo2ZnkpgNPlZo>
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, IETF <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, 21 Apr 2016 02:41:40 -0000

Have addressed the MIB related comments below. The remaining will be 
addressed
by Tim in the latest revision to be submitted tomorrow morning UK time.

Please see inline at VC.


On 4/17/16 4:18 PM, Peter Yee wrote:
> I am the assigned Gen-ART reviewer for this draft. The General Area Review
> Team (Gen-ART) reviews all IETF documents being processed by the IESG for
> the IETF Chair. Please wait for direction from your document shepherd or
> AD before posting a new version of the draft.
>
> For more information, please see the FAQ at
> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>
>
> Document: draft-ietf-tictoc-ptp-mib-08
> Reviewer: Peter Yee
> Review Date: March 8, 2016
> IETF LC End Date: March 8, 2016
> IESG Telechat date: April 21, 2016
>
> Summary: This draft is basically ready for publication as a Standards
> Track RFC, but has nits and a couple of minor issues that should be
> fixed/considered before publication. [Ready with issues]
>
> This draft defines an SMIv2 MIB for use with the Precision Time Protocol
> v2 (IEEE Std. 1588-2008).  I do not have access to this standard, so my
> review primarily addresses nits within the module and not whether the
> module itself is a fair representation of a MIB suitable for use with PTP
> v2.
>
> The following review was originally submitted for the LC (see
> http://www.ietf.org/mail-archive/web/gen-art/current/msg13014.html).  As
> no update has been issued for the draft, the content of that review is
> copied below.
>
> Major issues: None
>
> Minor issues:
>
> Given that the draft seems to quote a fair amount of text (at least 5
> pages) from IEEE Std. 1588-2008 in the definitions section if not
> elsewhere, it might be good to make sure that there are no copyright
> issues.
>
> Many of the object descriptions use identical text.  While that's helpful
> from the direct lookup point of view, it doesn't help to distinguish these
> items from others of their ilk.  I'm not sure if this matters, but perhaps
> enhancing the descriptions in their contexts might make them more useful.
>
> Nits:
>
> General:
>
> Replace all occurrences of "create logical group" with "create a logical
> group".

VC: done.

>
> Watch the case and spacing of object names in their descriptions.
> Sometime there's a space between two words, sometimes not.  Some words are
> capitalized in one place and not another.  Use of camel case conventions
> comes and goes.  It's probably best to treat the object names as English
> words in the descriptions, separating words with spaces and generally
> writing them in lower case.  Sure, the inconsistency doesn't hurt a lot,
> but it ends up looking a wee bit sloppy.  The RFC Editor may not be sure
> how to handle the inconsistency as some word combinations might appear to
> be technical MIB terms that should be left as is.
>
> Drop the draft name from the center, top header.  Generally a shortened
> form of the draft title is placed here.  Perhaps you could use "PTPv2 MIB"?
>
> I'll leave the serial comma be.  It appears in some places and not others.
> I like them, but there are enough missing ones that I'm just going to let
> it slide. ;-)
>
> When citing the official name of IEEE 1588-2008, use a lower case "aâ€ť
> before "Precision".  That aligns with IEEE's title.
>
> The authors' addresses in Section 9 have way too many punctuation marks in
> them.  A few less commas would go a long way.  Maybe change some into
> serial commas for sprinkling elsewhere in the document? ;-)
>
> Specific:
>
> Page 2, Section 1, 1st paragraph, 2nd sentence: delete "theâ€ť before
> "ordinary".  Make "ordinary clock" and "transparent clock" plural.  Insert
> a comma and "and" after "transparent clocks".
>
> Page 3, Section 1.1, 1st paragraph, 2nd sentence: append a comma after
> "e.g.".
>
> Page 5, 1st bullet item: delete the comma after "STD 62".
>
> Page 5, 2nd bullet item, 2nd sentence: insert "is" before "described".
>
> Page 5, 3rd bullet item, 2nd sentence: insert "is" before "described".
>
> Page 5, 3rd bullet item, last sentence: insert "is" before "described".
>
> Page 7, MIB Description, 1st paragraph, 1st sentence: change "MIB is to
> support" to "MIB supports".
VC: done.

> Page 8, Acronyms, EUI: delete the period after the acronym expansion.

VC: done.


>
> Page 12, PTP node definition: insert "A" before the sentence.

VC: done.

>
> Page 16, ClockIdentity description: the term "MAC-48" has not been defined
> or previously referenced in the draft.  It's also not quite an exact
> synonym for EUI-48, so perhaps it should be defined.

VC: done. Have added MAC-48 in the acronym section.

>
> Page 17, ClockMechanismType description: replace "End to Endâ€ť with
> "end-to-end".  Replace "peer to peer" with "peer-to-peer".

VC: done.


>
> Page 19, ClockPortTransportTypeAddress description, 2nd sentence: change
> "Transport" to "transport".

VC: done.


>
> Page 19, ClockPortTransportTypeAddress description, 4th sentence: insert
> "an" before "address".  Change "and" to "or".

VC: done.


>
> Page 20, ClockQualityAccuracyType description: change "sectionâ€ť to
> "sections".  Insert "of" before "RFC 2578", which should be placed in
> square brackets.  Change "to start with" to "starting at".

VC: done.

>
> Page 23, ClockStateType description: insert "a" before "PTP".

VC: done.
>
> Page 24, Holdover state text: change "ptp" to "PTP.  Change "FREERUNâ€ť to
> "Freerun".
>
> Page 25, ClockTimeSourceType description: change "section" to "sectionsâ€ť.
> Insert "of" before "RFC 2578", which should be placed in square brackets.
> Change "to start with" to "starting at".
>
> Page 26, ClockTimeSourceType reference: change "Section" to "Sections".
>
> Page 32, ptpbaseClockCurrentDSOffsetFromMaster and
> ptpbaseClockCurrentDSMeanPathDelay references: the indentation looks a bit
> off here.
>
> Page 32, ptpbaseClockCurrentDSMeanPathDelay description: change "measureâ€ť
> to "measured".
>
> Page 35, ptpbaseClockParentDSOffset description (near top of page): change
> "clocks" to "clock's".
>
> Page 35, ptpbaseClockParentDSClockPhChRate description: change "clocksâ€ť to
> "clock's".
>
> Page 41, ptpbaseClockRunningState description: insert "a" before "PTPâ€ť.
> Append a comma after "engine".
>
> Page 42, top: Rather than duplicate the state descriptions information
> here, why not merely point back to ClockStateType?  Btw, PTP engine hasn't
> been defined.
>
> Page 42, Holdover state, 1st sentence: if you do not remove this paragraph
> as suggested in the previous comment, change "ptp" to "PTP".
>
> Page 42, ptpbaseClockRunningPacketsSent description: replace "packet
> Unicast and multicast" with "unicast and multicast packets".
>
> Page 42, ptpbaseClockRunningPacketsReceived description: replace â€śpacket
> Unicast and multicast" with "unicast and multicast packets".
>
> Page 44, ptpbaseClockTimePropertiesDSCurrentUTCOffsetValid description:
> insert "the" before "UTC".
>
> Page 45, ptpbaseClockTimePropertiesDSCurrentUTCOffset description (at top
> of page): insert "the" before "UTC".
>
> Page 49, ptpbaseClockTransDefaultDSDelay description (at top of page):
> change "shall be" to "of".  Change "If" to "if".
>
> Page 56, ptpbaseClockPortRunningTable description: should that be â€śa
> dataset" or "datasets".  Plain "dataset" doesn't work.
>
> Page 57, ptpbaseClockPortRunningEntry description: change "runingâ€ť to
> "running" unless Viking writing is involved.
>
> Page 58, ptpbaseClockPortRunningState description: you probably don't need
> to include the states here since they are already found in the definition
> of ClockPortState.
>
> Page 60, ptpbaseClockPortRunningEncapsulationType description: change
> "eg.â€ť to "e.g.,".
>
> Page 60, ptpbaseClockPortRunningRxMode description: change "specifieâ€ť to
> "specifies".
>
> Page 63, ptpbaseClockPortTransDSPeerMeanPathDelay description: delete the
> parentheses and append a comma after PTP.  On the following page, change
> "value is" to "value of".
>
> Page 64, ptpbaseClockPortAssociateTable description: change "whichâ€ť to
> "that".
>
> Page 75, ptpbaseMIBClockPortTransDSGroup description: does â€ś TransparentDS
> Dataset" contain a redundancy?
>
> Page 76, 4th paragraph, 1st sentence: delete "the" before "implementersâ€ť.
> Delete "as".
>
> Page 76, 5th paragraph, 1st sentence: change "Further" to "Furthermore".
>
>


From nobody Wed Apr 20 19:44:10 2016
Return-Path: <vinays@cisco.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 B18DB12D96B; Wed, 20 Apr 2016 19:44:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.517
X-Spam-Level: 
X-Spam-Status: No, score=-15.517 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.996, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 wLf1uyqAtsNs; Wed, 20 Apr 2016 19:44:03 -0700 (PDT)
Received: from alln-iport-1.cisco.com (alln-iport-1.cisco.com [173.37.142.88]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1331D12DAB5; Wed, 20 Apr 2016 19:44:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=9336; q=dns/txt; s=iport; t=1461206643; x=1462416243; h=subject:to:references:cc:from:message-id:date: mime-version:in-reply-to:content-transfer-encoding; bh=BkycmUlt3l8gCf/LIBeBQza7pVKBClpgk3HUXymLL5s=; b=Nq2s/d2xCvmIWoL18YAqC/2qc5xT+RToNsUd+6iZIVJnvo9dgEJX8Ja2 65094+lxW4Y1Ub2jezssR1jPhrwD6u8tQueHm3sO9ovRkp8lPfGw9t1kK X/dSQFrshWQ6eivmMb19fIbcnGErIjINFAsB0x9FwntiPv2ho5TMtw3Tj 0=;
X-IronPort-AV: E=Sophos;i="5.24,512,1454976000"; d="scan'208";a="264215075"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by alln-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 21 Apr 2016 02:44:02 +0000
Received: from [10.82.241.140] (rtp-vpn2-396.cisco.com [10.82.241.140]) (authenticated bits=0) by rcdn-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id u3L2i1j7008169 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Thu, 21 Apr 2016 02:44:01 GMT
Subject: Re: Gen-ART Telechat review of draft-ietf-tictoc-ptp-mib-08
To: Peter Yee <peter@akayla.com>, draft-ietf-tictoc-ptp-mib.all@ietf.org
References: <D3393DAB.16AA3%peter@akayla.com> <57183DDE.5040309@cisco.com>
From: vinays <vinays@cisco.com>
Message-ID: <57183E70.6070806@cisco.com>
Date: Wed, 20 Apr 2016 22:44:00 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:38.0) Gecko/20100101 Thunderbird/38.7.2
MIME-Version: 1.0
In-Reply-To: <57183DDE.5040309@cisco.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
X-Authenticated-User: vinays
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/lyfVr2hozl0dWXivyG9sJl1HfCE>
Cc: Tim Frost <tim.frost@calnexsol.com>, IETF <ietf@ietf.org>, Vinay Shankarkumar <vinays@cisco.com>, "gen-art@ietf.org" <gen-art@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, 21 Apr 2016 02:44:06 -0000

Sent too soon. Please see inline at VC2.

Thanks,
-Vinay.


On 4/20/16 10:41 PM, vinays wrote:
>
>
> Have addressed the MIB related comments below. The remaining will be 
> addressed
> by Tim in the latest revision to be submitted tomorrow morning UK time.
>
> Please see inline at VC.
>
>
> On 4/17/16 4:18 PM, Peter Yee wrote:
>> I am the assigned Gen-ART reviewer for this draft. The General Area 
>> Review
>> Team (Gen-ART) reviews all IETF documents being processed by the IESG 
>> for
>> the IETF Chair. Please wait for direction from your document shepherd or
>> AD before posting a new version of the draft.
>>
>> For more information, please see the FAQ at
>> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>>
>>
>> Document: draft-ietf-tictoc-ptp-mib-08
>> Reviewer: Peter Yee
>> Review Date: March 8, 2016
>> IETF LC End Date: March 8, 2016
>> IESG Telechat date: April 21, 2016
>>
>> Summary: This draft is basically ready for publication as a Standards
>> Track RFC, but has nits and a couple of minor issues that should be
>> fixed/considered before publication. [Ready with issues]
>>
>> This draft defines an SMIv2 MIB for use with the Precision Time Protocol
>> v2 (IEEE Std. 1588-2008).  I do not have access to this standard, so my
>> review primarily addresses nits within the module and not whether the
>> module itself is a fair representation of a MIB suitable for use with 
>> PTP
>> v2.
>>
>> The following review was originally submitted for the LC (see
>> http://www.ietf.org/mail-archive/web/gen-art/current/msg13014.html). As
>> no update has been issued for the draft, the content of that review is
>> copied below.
>>
>> Major issues: None
>>
>> Minor issues:
>>
>> Given that the draft seems to quote a fair amount of text (at least 5
>> pages) from IEEE Std. 1588-2008 in the definitions section if not
>> elsewhere, it might be good to make sure that there are no copyright
>> issues.
>>
>> Many of the object descriptions use identical text.  While that's 
>> helpful
>> from the direct lookup point of view, it doesn't help to distinguish 
>> these
>> items from others of their ilk.  I'm not sure if this matters, but 
>> perhaps
>> enhancing the descriptions in their contexts might make them more 
>> useful.
>>
>> Nits:
>>
>> General:
>>
>> Replace all occurrences of "create logical group" with "create a logical
>> group".
>
> VC: done.
>
>>
>> Watch the case and spacing of object names in their descriptions.
>> Sometime there's a space between two words, sometimes not.  Some 
>> words are
>> capitalized in one place and not another.  Use of camel case conventions
>> comes and goes.  It's probably best to treat the object names as English
>> words in the descriptions, separating words with spaces and generally
>> writing them in lower case.  Sure, the inconsistency doesn't hurt a lot,
>> but it ends up looking a wee bit sloppy.  The RFC Editor may not be sure
>> how to handle the inconsistency as some word combinations might 
>> appear to
>> be technical MIB terms that should be left as is.
>>
>> Drop the draft name from the center, top header.  Generally a shortened
>> form of the draft title is placed here.  Perhaps you could use "PTPv2 
>> MIB"?
>>
>> I'll leave the serial comma be.  It appears in some places and not 
>> others.
>> I like them, but there are enough missing ones that I'm just going to 
>> let
>> it slide. ;-)
>>
>> When citing the official name of IEEE 1588-2008, use a lower case "aâ€ť
>> before "Precision".  That aligns with IEEE's title.
>>
>> The authors' addresses in Section 9 have way too many punctuation 
>> marks in
>> them.  A few less commas would go a long way.  Maybe change some into
>> serial commas for sprinkling elsewhere in the document? ;-)
>>
>> Specific:
>>
>> Page 2, Section 1, 1st paragraph, 2nd sentence: delete "theâ€ť before
>> "ordinary".  Make "ordinary clock" and "transparent clock" plural.  
>> Insert
>> a comma and "and" after "transparent clocks".
>>
>> Page 3, Section 1.1, 1st paragraph, 2nd sentence: append a comma after
>> "e.g.".
>>
>> Page 5, 1st bullet item: delete the comma after "STD 62".
>>
>> Page 5, 2nd bullet item, 2nd sentence: insert "is" before "described".
>>
>> Page 5, 3rd bullet item, 2nd sentence: insert "is" before "described".
>>
>> Page 5, 3rd bullet item, last sentence: insert "is" before "described".
>>
>> Page 7, MIB Description, 1st paragraph, 1st sentence: change "MIB is to
>> support" to "MIB supports".
> VC: done.
>
>> Page 8, Acronyms, EUI: delete the period after the acronym expansion.
>
> VC: done.
>
>
>>
>> Page 12, PTP node definition: insert "A" before the sentence.
>
> VC: done.
>
>>
>> Page 16, ClockIdentity description: the term "MAC-48" has not been 
>> defined
>> or previously referenced in the draft.  It's also not quite an exact
>> synonym for EUI-48, so perhaps it should be defined.
>
> VC: done. Have added MAC-48 in the acronym section.
>
>>
>> Page 17, ClockMechanismType description: replace "End to Endâ€ť with
>> "end-to-end".  Replace "peer to peer" with "peer-to-peer".
>
> VC: done.
>
>
>>
>> Page 19, ClockPortTransportTypeAddress description, 2nd sentence: change
>> "Transport" to "transport".
>
> VC: done.
>
>
>>
>> Page 19, ClockPortTransportTypeAddress description, 4th sentence: insert
>> "an" before "address".  Change "and" to "or".
>
> VC: done.
>
>
>>
>> Page 20, ClockQualityAccuracyType description: change "sectionâ€ť to
>> "sections".  Insert "of" before "RFC 2578", which should be placed in
>> square brackets.  Change "to start with" to "starting at".
>
> VC: done.
>
>>
>> Page 23, ClockStateType description: insert "a" before "PTP".
>
> VC: done.
>>
>> Page 24, Holdover state text: change "ptp" to "PTP.  Change "FREERUNâ€ť to
>> "Freerun".
>>

VC2: done.


>> Page 25, ClockTimeSourceType description: change "section" to 
>> "sectionsâ€ť.
>> Insert "of" before "RFC 2578", which should be placed in square 
>> brackets.
>> Change "to start with" to "starting at".

VC2: done.

>>
>> Page 26, ClockTimeSourceType reference: change "Section" to "Sections".

VC2: done.


>>
>> Page 32, ptpbaseClockCurrentDSOffsetFromMaster and
>> ptpbaseClockCurrentDSMeanPathDelay references: the indentation looks 
>> a bit
>> off here.

VC2: done.


>>
>> Page 32, ptpbaseClockCurrentDSMeanPathDelay description: change 
>> "measureâ€ť
>> to "measured".

VC2: done.


>>
>> Page 35, ptpbaseClockParentDSOffset description (near top of page): 
>> change
>> "clocks" to "clock's".
VC2: done.

>>
>> Page 35, ptpbaseClockParentDSClockPhChRate description: change 
>> "clocksâ€ť to
>> "clock's".

VC2: done.


>>
>> Page 41, ptpbaseClockRunningState description: insert "a" before "PTPâ€ť.
>> Append a comma after "engine".

VC2: done.


>>
>> Page 42, top: Rather than duplicate the state descriptions information
>> here, why not merely point back to ClockStateType?  Btw, PTP engine 
>> hasn't
>> been defined.

VC2: done.

>>
>> Page 42, Holdover state, 1st sentence: if you do not remove this 
>> paragraph
>> as suggested in the previous comment, change "ptp" to "PTP".
>>
>> Page 42, ptpbaseClockRunningPacketsSent description: replace "packet
>> Unicast and multicast" with "unicast and multicast packets".
>>
>> Page 42, ptpbaseClockRunningPacketsReceived description: replace â€śpacket
>> Unicast and multicast" with "unicast and multicast packets".
>>
>> Page 44, ptpbaseClockTimePropertiesDSCurrentUTCOffsetValid description:
>> insert "the" before "UTC".
>>
>> Page 45, ptpbaseClockTimePropertiesDSCurrentUTCOffset description (at 
>> top
>> of page): insert "the" before "UTC".
>>
>> Page 49, ptpbaseClockTransDefaultDSDelay description (at top of page):
>> change "shall be" to "of".  Change "If" to "if".
>>
>> Page 56, ptpbaseClockPortRunningTable description: should that be â€śa
>> dataset" or "datasets".  Plain "dataset" doesn't work.
>>
>> Page 57, ptpbaseClockPortRunningEntry description: change "runingâ€ť to
>> "running" unless Viking writing is involved.
>>
>> Page 58, ptpbaseClockPortRunningState description: you probably don't 
>> need
>> to include the states here since they are already found in the 
>> definition
>> of ClockPortState.
>>
>> Page 60, ptpbaseClockPortRunningEncapsulationType description: change
>> "eg.â€ť to "e.g.,".
>>
>> Page 60, ptpbaseClockPortRunningRxMode description: change "specifieâ€ť to
>> "specifies".
>>
>> Page 63, ptpbaseClockPortTransDSPeerMeanPathDelay description: delete 
>> the
>> parentheses and append a comma after PTP.  On the following page, change
>> "value is" to "value of".
>>
>> Page 64, ptpbaseClockPortAssociateTable description: change "whichâ€ť to
>> "that".
>>
>> Page 75, ptpbaseMIBClockPortTransDSGroup description: does â€ś 
>> TransparentDS
>> Dataset" contain a redundancy?

VC2: All the above are done as well. Thanks,
-Vinay.



>>
>> Page 76, 4th paragraph, 1st sentence: delete "the" before 
>> "implementersâ€ť.
>> Delete "as".
>>
>> Page 76, 5th paragraph, 1st sentence: change "Further" to "Furthermore".
>>
>>
>


From nobody Wed Apr 20 22:04:07 2016
Return-Path: <jari.arkko@piuha.net>
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 7256E12D8ED; Wed, 20 Apr 2016 22:04:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.896
X-Spam-Level: 
X-Spam-Status: No, score=-2.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.996] 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 FLqjCYQpr8dY; Wed, 20 Apr 2016 22:03:58 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 5897712E994; Wed, 20 Apr 2016 22:03:57 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id A7A0D2CCAE; Thu, 21 Apr 2016 08:03:55 +0300 (EEST) (envelope-from jari.arkko@piuha.net)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dDWVC5EdgubR; Thu, 21 Apr 2016 08:03:54 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 061442CC6F; Thu, 21 Apr 2016 08:03:53 +0300 (EEST) (envelope-from jari.arkko@piuha.net)
Subject: Re: [Gen-art] Gen-ART Telechat review of draft-ietf-tictoc-ptp-mib-08
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Content-Type: multipart/signed; boundary="Apple-Mail=_76A4A5CA-8DA9-41B8-9038-5542F9E69D64"; protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail 2.5.2
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <57183E70.6070806@cisco.com>
Date: Thu, 21 Apr 2016 07:03:52 +0200
Message-Id: <E441CD5C-1285-46AB-9624-DC41041E60D0@piuha.net>
References: <D3393DAB.16AA3%peter@akayla.com> <57183DDE.5040309@cisco.com> <57183E70.6070806@cisco.com>
To: vinays <vinays@cisco.com>, Peter Yee <peter@akayla.com>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/9bj209EQYFQUVtoVPDiFArFP66k>
Cc: Tim Frost <tim.frost@calnexsol.com>, "gen-art@ietf.org" <gen-art@ietf.org>, draft-ietf-tictoc-ptp-mib.all@ietf.org, IETF <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, 21 Apr 2016 05:04:05 -0000

--Apple-Mail=_76A4A5CA-8DA9-41B8-9038-5542F9E69D64
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252

Thanks for the review Peter, and for the updates, Vinay!

I do have a remaining question about the copyright. Do we have an =
answer?

Jari

On 21 Apr 2016, at 04:44, vinays <vinays@cisco.com> wrote:

>=20
>=20
> Sent too soon. Please see inline at VC2.
>=20
> Thanks,
> -Vinay.
>=20
>=20
> On 4/20/16 10:41 PM, vinays wrote:
>>=20
>>=20
>> Have addressed the MIB related comments below. The remaining will be =
addressed
>> by Tim in the latest revision to be submitted tomorrow morning UK =
time.
>>=20
>> Please see inline at VC.
>>=20
>>=20
>> On 4/17/16 4:18 PM, Peter Yee wrote:
>>> I am the assigned Gen-ART reviewer for this draft. The General Area =
Review
>>> Team (Gen-ART) reviews all IETF documents being processed by the =
IESG for
>>> the IETF Chair. Please wait for direction from your document =
shepherd or
>>> AD before posting a new version of the draft.
>>>=20
>>> For more information, please see the FAQ at
>>> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>>>=20
>>>=20
>>> Document: draft-ietf-tictoc-ptp-mib-08
>>> Reviewer: Peter Yee
>>> Review Date: March 8, 2016
>>> IETF LC End Date: March 8, 2016
>>> IESG Telechat date: April 21, 2016
>>>=20
>>> Summary: This draft is basically ready for publication as a =
Standards
>>> Track RFC, but has nits and a couple of minor issues that should be
>>> fixed/considered before publication. [Ready with issues]
>>>=20
>>> This draft defines an SMIv2 MIB for use with the Precision Time =
Protocol
>>> v2 (IEEE Std. 1588-2008).  I do not have access to this standard, so =
my
>>> review primarily addresses nits within the module and not whether =
the
>>> module itself is a fair representation of a MIB suitable for use =
with PTP
>>> v2.
>>>=20
>>> The following review was originally submitted for the LC (see
>>> http://www.ietf.org/mail-archive/web/gen-art/current/msg13014.html). =
As
>>> no update has been issued for the draft, the content of that review =
is
>>> copied below.
>>>=20
>>> Major issues: None
>>>=20
>>> Minor issues:
>>>=20
>>> Given that the draft seems to quote a fair amount of text (at least =
5
>>> pages) from IEEE Std. 1588-2008 in the definitions section if not
>>> elsewhere, it might be good to make sure that there are no copyright
>>> issues.
>>>=20
>>> Many of the object descriptions use identical text.  While that's =
helpful
>>> from the direct lookup point of view, it doesn't help to distinguish =
these
>>> items from others of their ilk.  I'm not sure if this matters, but =
perhaps
>>> enhancing the descriptions in their contexts might make them more =
useful.
>>>=20
>>> Nits:
>>>=20
>>> General:
>>>=20
>>> Replace all occurrences of "create logical group" with "create a =
logical
>>> group".
>>=20
>> VC: done.
>>=20
>>>=20
>>> Watch the case and spacing of object names in their descriptions.
>>> Sometime there's a space between two words, sometimes not.  Some =
words are
>>> capitalized in one place and not another.  Use of camel case =
conventions
>>> comes and goes.  It's probably best to treat the object names as =
English
>>> words in the descriptions, separating words with spaces and =
generally
>>> writing them in lower case.  Sure, the inconsistency doesn't hurt a =
lot,
>>> but it ends up looking a wee bit sloppy.  The RFC Editor may not be =
sure
>>> how to handle the inconsistency as some word combinations might =
appear to
>>> be technical MIB terms that should be left as is.
>>>=20
>>> Drop the draft name from the center, top header.  Generally a =
shortened
>>> form of the draft title is placed here.  Perhaps you could use =
"PTPv2 MIB"?
>>>=20
>>> I'll leave the serial comma be.  It appears in some places and not =
others.
>>> I like them, but there are enough missing ones that I'm just going =
to let
>>> it slide. ;-)
>>>=20
>>> When citing the official name of IEEE 1588-2008, use a lower case =
"a=94
>>> before "Precision".  That aligns with IEEE's title.
>>>=20
>>> The authors' addresses in Section 9 have way too many punctuation =
marks in
>>> them.  A few less commas would go a long way.  Maybe change some =
into
>>> serial commas for sprinkling elsewhere in the document? ;-)
>>>=20
>>> Specific:
>>>=20
>>> Page 2, Section 1, 1st paragraph, 2nd sentence: delete "the=94 =
before
>>> "ordinary".  Make "ordinary clock" and "transparent clock" plural.  =
Insert
>>> a comma and "and" after "transparent clocks".
>>>=20
>>> Page 3, Section 1.1, 1st paragraph, 2nd sentence: append a comma =
after
>>> "e.g.".
>>>=20
>>> Page 5, 1st bullet item: delete the comma after "STD 62".
>>>=20
>>> Page 5, 2nd bullet item, 2nd sentence: insert "is" before =
"described".
>>>=20
>>> Page 5, 3rd bullet item, 2nd sentence: insert "is" before =
"described".
>>>=20
>>> Page 5, 3rd bullet item, last sentence: insert "is" before =
"described".
>>>=20
>>> Page 7, MIB Description, 1st paragraph, 1st sentence: change "MIB is =
to
>>> support" to "MIB supports".
>> VC: done.
>>=20
>>> Page 8, Acronyms, EUI: delete the period after the acronym =
expansion.
>>=20
>> VC: done.
>>=20
>>=20
>>>=20
>>> Page 12, PTP node definition: insert "A" before the sentence.
>>=20
>> VC: done.
>>=20
>>>=20
>>> Page 16, ClockIdentity description: the term "MAC-48" has not been =
defined
>>> or previously referenced in the draft.  It's also not quite an exact
>>> synonym for EUI-48, so perhaps it should be defined.
>>=20
>> VC: done. Have added MAC-48 in the acronym section.
>>=20
>>>=20
>>> Page 17, ClockMechanismType description: replace "End to End=94 with
>>> "end-to-end".  Replace "peer to peer" with "peer-to-peer".
>>=20
>> VC: done.
>>=20
>>=20
>>>=20
>>> Page 19, ClockPortTransportTypeAddress description, 2nd sentence: =
change
>>> "Transport" to "transport".
>>=20
>> VC: done.
>>=20
>>=20
>>>=20
>>> Page 19, ClockPortTransportTypeAddress description, 4th sentence: =
insert
>>> "an" before "address".  Change "and" to "or".
>>=20
>> VC: done.
>>=20
>>=20
>>>=20
>>> Page 20, ClockQualityAccuracyType description: change "section=94 to
>>> "sections".  Insert "of" before "RFC 2578", which should be placed =
in
>>> square brackets.  Change "to start with" to "starting at".
>>=20
>> VC: done.
>>=20
>>>=20
>>> Page 23, ClockStateType description: insert "a" before "PTP".
>>=20
>> VC: done.
>>>=20
>>> Page 24, Holdover state text: change "ptp" to "PTP.  Change =
"FREERUN=94 to
>>> "Freerun".
>>>=20
>=20
> VC2: done.
>=20
>=20
>>> Page 25, ClockTimeSourceType description: change "section" to =
"sections=94.
>>> Insert "of" before "RFC 2578", which should be placed in square =
brackets.
>>> Change "to start with" to "starting at".
>=20
> VC2: done.
>=20
>>>=20
>>> Page 26, ClockTimeSourceType reference: change "Section" to =
"Sections".
>=20
> VC2: done.
>=20
>=20
>>>=20
>>> Page 32, ptpbaseClockCurrentDSOffsetFromMaster and
>>> ptpbaseClockCurrentDSMeanPathDelay references: the indentation looks =
a bit
>>> off here.
>=20
> VC2: done.
>=20
>=20
>>>=20
>>> Page 32, ptpbaseClockCurrentDSMeanPathDelay description: change =
"measure=94
>>> to "measured".
>=20
> VC2: done.
>=20
>=20
>>>=20
>>> Page 35, ptpbaseClockParentDSOffset description (near top of page): =
change
>>> "clocks" to "clock's".
> VC2: done.
>=20
>>>=20
>>> Page 35, ptpbaseClockParentDSClockPhChRate description: change =
"clocks=94 to
>>> "clock's".
>=20
> VC2: done.
>=20
>=20
>>>=20
>>> Page 41, ptpbaseClockRunningState description: insert "a" before =
"PTP=94.
>>> Append a comma after "engine".
>=20
> VC2: done.
>=20
>=20
>>>=20
>>> Page 42, top: Rather than duplicate the state descriptions =
information
>>> here, why not merely point back to ClockStateType?  Btw, PTP engine =
hasn't
>>> been defined.
>=20
> VC2: done.
>=20
>>>=20
>>> Page 42, Holdover state, 1st sentence: if you do not remove this =
paragraph
>>> as suggested in the previous comment, change "ptp" to "PTP".
>>>=20
>>> Page 42, ptpbaseClockRunningPacketsSent description: replace "packet
>>> Unicast and multicast" with "unicast and multicast packets".
>>>=20
>>> Page 42, ptpbaseClockRunningPacketsReceived description: replace =
=93packet
>>> Unicast and multicast" with "unicast and multicast packets".
>>>=20
>>> Page 44, ptpbaseClockTimePropertiesDSCurrentUTCOffsetValid =
description:
>>> insert "the" before "UTC".
>>>=20
>>> Page 45, ptpbaseClockTimePropertiesDSCurrentUTCOffset description =
(at top
>>> of page): insert "the" before "UTC".
>>>=20
>>> Page 49, ptpbaseClockTransDefaultDSDelay description (at top of =
page):
>>> change "shall be" to "of".  Change "If" to "if".
>>>=20
>>> Page 56, ptpbaseClockPortRunningTable description: should that be =93a=

>>> dataset" or "datasets".  Plain "dataset" doesn't work.
>>>=20
>>> Page 57, ptpbaseClockPortRunningEntry description: change "runing=94 =
to
>>> "running" unless Viking writing is involved.
>>>=20
>>> Page 58, ptpbaseClockPortRunningState description: you probably =
don't need
>>> to include the states here since they are already found in the =
definition
>>> of ClockPortState.
>>>=20
>>> Page 60, ptpbaseClockPortRunningEncapsulationType description: =
change
>>> "eg.=94 to "e.g.,".
>>>=20
>>> Page 60, ptpbaseClockPortRunningRxMode description: change =
"specifie=94 to
>>> "specifies".
>>>=20
>>> Page 63, ptpbaseClockPortTransDSPeerMeanPathDelay description: =
delete the
>>> parentheses and append a comma after PTP.  On the following page, =
change
>>> "value is" to "value of".
>>>=20
>>> Page 64, ptpbaseClockPortAssociateTable description: change "which=94 =
to
>>> "that".
>>>=20
>>> Page 75, ptpbaseMIBClockPortTransDSGroup description: does =93 =
TransparentDS
>>> Dataset" contain a redundancy?
>=20
> VC2: All the above are done as well. Thanks,
> -Vinay.
>=20
>=20
>=20
>>>=20
>>> Page 76, 4th paragraph, 1st sentence: delete "the" before =
"implementers=94.
>>> Delete "as".
>>>=20
>>> Page 76, 5th paragraph, 1st sentence: change "Further" to =
"Furthermore".
>>>=20
>>>=20
>>=20
>=20
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


--Apple-Mail=_76A4A5CA-8DA9-41B8-9038-5542F9E69D64
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQIcBAEBCgAGBQJXGF85AAoJEM80gCTQU46qvOgP/3UnMl5M7kaDSKgoIfKGZ3MJ
gaLNpa5Qm5Juvl3lxwcydBdulSZVqj5PwMp+d1qh8nfaVy/ZBAw1XDV6Ayr5nxUZ
7QdwW/REhcBskuJSLGXVHIvEiMrKIFYi/KCYF/SfDqH1yJOvOtclLDS+EBJXnDlI
bN7ETgABC/kYh+Vyea9sX78wjINkwB09Y7JQqzjOY/2euXB5H8F4TemPd0ndPWwR
rYizd6BT9v/MhiZqbxaIvPHC98O98SY/7KWonp6Jc3pLIm0jxpzaOJ9BlMc+ZRd0
RWDsmt7eog8cCdoBL4+tQF4gpvnVLVkmvn3wFiEh18X9wT8I1ArOnDoe0l8stQ1E
zXnYOeu6uiUP3z9ovSAca54Z1UV2JLpAXWXlA3ZodEL7aEA4E4rEDX5qmCgLAed/
MY4R9w5hG3meum+vLo7+wOo4ruXNTkzFRAHIPgw5oHbuUJ5HZqb2dQUOvvKaKQK+
mgIu+9/S6dNVIoWOMGfI1ZrznKpDlZue2CezY/dhx0+wL2JhbmTGB7VDquMxcJC5
CzJ3BP1PcrJVEoLE0Fxt2NJ8dm1BlpxoJS2SwYw5PVmphc6Cpop3G2HmUdR7kPii
n9bkdcnVscEs5uLaj/N2b1mTsdD0QSQ4ZvZJXj1gAzQjr6sbJ8miUzqYlBSPTgd3
8IUcInZfHMA/vO6rfgkA
=QiMp
-----END PGP SIGNATURE-----

--Apple-Mail=_76A4A5CA-8DA9-41B8-9038-5542F9E69D64--


From nobody Wed Apr 20 22:10:36 2016
Return-Path: <jari.arkko@piuha.net>
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 441BE12DEC2; Wed, 20 Apr 2016 22:10:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.896
X-Spam-Level: 
X-Spam-Status: No, score=-2.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.996] 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 OLufj4BrQeUu; Wed, 20 Apr 2016 22:10:32 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [IPv6:2a00:1d50:2::130]) by ietfa.amsl.com (Postfix) with ESMTP id 08ABB12DD42; Wed, 20 Apr 2016 22:10:32 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id C64E62CCAE; Thu, 21 Apr 2016 08:10:30 +0300 (EEST) (envelope-from jari.arkko@piuha.net)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Qs3lWhv99e4i; Thu, 21 Apr 2016 08:10:30 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 200082CC6F; Thu, 21 Apr 2016 08:10:30 +0300 (EEST) (envelope-from jari.arkko@piuha.net)
Subject: Re: [Gen-art] Gen-ART LC/Telechat review of draft-ietf-pce-iro-update-06
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Content-Type: multipart/signed; boundary="Apple-Mail=_2BA35696-248D-4B6C-97E9-FEA1B4BF7175"; protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail 2.5.2
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <CAB75xn41Uq-0vTYJZLKF+01peE8TJuLb1TG3tgd3bCTgW2WWBQ@mail.gmail.com>
Date: Thu, 21 Apr 2016 07:10:28 +0200
Message-Id: <74F52701-20C9-4C3D-8731-157F08441038@piuha.net>
References: <D3393302.16A48%peter@akayla.com> <CAB75xn41Uq-0vTYJZLKF+01peE8TJuLb1TG3tgd3bCTgW2WWBQ@mail.gmail.com>
To: Dhruv Dhody <dhruv.ietf@gmail.com>, Peter Yee <peter@akayla.com>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/FYcDtEU7s2XtC6IY5IFC1hG8_Tc>
Cc: General Area Review Team <gen-art@ietf.org>, draft-ietf-pce-iro-update.all@ietf.org, IETF <ietf@ietf.org>, "dhruv.dhody@huawei.com" <dhruv.dhody@huawei.com>
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, 21 Apr 2016 05:10:33 -0000

--Apple-Mail=_2BA35696-248D-4B6C-97E9-FEA1B4BF7175
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=us-ascii

Thanks again for your careful review, Peter!

And thank you Dhruv for looking into the one question.

Jari



--Apple-Mail=_2BA35696-248D-4B6C-97E9-FEA1B4BF7175
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQIcBAEBCgAGBQJXGGDEAAoJEM80gCTQU46qEDcQAJ2aZCmhtqKly9yBMIzXvylp
PZvFQlIDp3beVynZMBIOMOB3AWp3Jfeoso1YrtX+b8kQjP6SR1QFM9wc7VaH9avh
ZCHyCgPwNdNM6Fm2dNWQha8XWf9JK+GhoiB0nbQz8E+esFcBnXtl1vzXmvGZ1fUc
NOqvuHb/Amq4wQLfMbqpeoULJqBfBH6N0aocmcuh8CdfFwYSbxql0un9ck8cxptb
2GAR+PmnctNUJwmZWUkrkoeKR1rnCEUM8MQ3czWXH6d3rmgVRMfTPqo5mVhoI7P1
V/ctaVStzCuQsVSBPfTjtZsSkJhF5no8jU20JANIsak87Tkzj5PLK1L9In6hwX6e
GI7/rK+kX/y2GuQSTYcfkIF/4FldllzmOWo9hoOneP1iz2zWOpZQquPuBtRujWj2
LHmpaycBxTSSBgbGSyNPH1pcXx6CiBPl4sR5DUoRektv0foqmX8nyUV28W0V9SoW
FeipGC3UPYTmD9rU/6O65zpmHHHgD4Ly69whOdZr29mVW5vcMRnJmWuvEsvEZsVV
n/i3xQgQcjeBRWyJ6LaDhC3AUQ4KHuK+sUGf21tkgLFaxxKrNgTTkPOjzZFGgx+l
Ryy21RVQry6aYXjV/Su1l2PoSyt+NBs778RPV2njTHfD1WOz+ECbWjAxAoIe/H2A
IYmfDfUainkQG4s+Z4RT
=ItaC
-----END PGP SIGNATURE-----

--Apple-Mail=_2BA35696-248D-4B6C-97E9-FEA1B4BF7175--


From nobody Thu Apr 21 05:07:50 2016
Return-Path: <mary.h.barnes@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 4171B12DC59 for <ietf@ietfa.amsl.com>; Thu, 21 Apr 2016 05:07:49 -0700 (PDT)
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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 iwE4YRaCSZp7 for <ietf@ietfa.amsl.com>; Thu, 21 Apr 2016 05:07:47 -0700 (PDT)
Received: from mail-yw0-x235.google.com (mail-yw0-x235.google.com [IPv6:2607:f8b0:4002:c05::235]) (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 B3A4812D901 for <ietf@ietf.org>; Thu, 21 Apr 2016 05:07:47 -0700 (PDT)
Received: by mail-yw0-x235.google.com with SMTP id g133so76097789ywb.2 for <ietf@ietf.org>; Thu, 21 Apr 2016 05:07:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=8x23dHGohAYzVx8uLUhQ0t3PqA0PG4MvQeTZcH2j6sw=; b=jtusTtHfFxWFKPKykofhv+1V1h7fpZuLo7bcx4LN5wBb8yynIPWLnBbDmfSk/6r3gt q5zDAJVDlcxwy28T04aS9aksU+1hD/3aX5xX8FXlBbRVzTNm22BQ08xNIQKcmvVG3EdM DEeEUsz9ZaYZDlfJE7dHDNkwLfv282q3z620TXWZEV79piMW8tRJZkPuKlasmGt+lXCs mwUD0uSb6wrPl9Dq/PUv/8dwiC6Q6nWsnP7o+hg99j6jbwyUU57i6b9iCh0qqSzsE1S7 YuIqDdBg88++3FRvkY3V0ie/Y6SzNsI5yBoEqSNsSTzh3amLcrLRivscJ7s5uD9q5OJB vBgA==
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:date :message-id:subject:from:to:cc; bh=8x23dHGohAYzVx8uLUhQ0t3PqA0PG4MvQeTZcH2j6sw=; b=W1gIFPMjcJgTDGSw4CuQawzTsRCkmOgz+8VjX9I1/oh6dDoJhQ53ZxZC+1mB//djod 0phmL8TGHn74juOL1FwepsyYXOcRB0ODXYRNgG9NuopvfagYKjn2IGIoHjhoOk9Za168 hc1ocqo2K0L6E5YWKOOjeNMEwLid5kjewYdiVwHe/JGLNsKV+KgoHZtpla5/b4vtiRmV r84mhZgTWLQKV27z4Tz/sgWIQvgHG0/I2uSxwYYpAhtbujkSEaoMb/yMPS2m176boJYt 4ZSP2qMHVidT1RQxOZaMCJyaIrLGOo3D6EL2mBn2WCgT+2hHohSKuNNmAi+jEldDsxh2 QBYQ==
X-Gm-Message-State: AOPr4FUvvlAuWxpQPLSmWSpX8+qif/PpS/suOEVNgSddDmLZZmGFxIc+TgNgEBIf8uGPqo/dIToz4D9QmbAdAg==
MIME-Version: 1.0
X-Received: by 10.129.134.133 with SMTP id w127mr8251620ywf.252.1461240466955;  Thu, 21 Apr 2016 05:07:46 -0700 (PDT)
Received: by 10.37.63.197 with HTTP; Thu, 21 Apr 2016 05:07:46 -0700 (PDT)
In-Reply-To: <57183686.8000307@gmail.com>
References: <57183308.7090108@gmail.com> <57183686.8000307@gmail.com>
Date: Thu, 21 Apr 2016 07:07:46 -0500
Message-ID: <CABmDk8kf-fXzxYxExNf2zc5W113-Tun0fx3s19mJBqJ=y5h5WA@mail.gmail.com>
Subject: Re: Interim step on meetings site feedback for sites currently under active consideration
From: Mary Barnes <mary.h.barnes@gmail.com>
To: Melinda Shore <melinda.shore@gmail.com>
Content-Type: multipart/alternative; boundary=001a114f2250f6e62c0530fd8ef3
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/sAcQ3Cih5K6xBuKmxXffVj8ztk4>
Cc: ietf <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, 21 Apr 2016 12:07:49 -0000

--001a114f2250f6e62c0530fd8ef3
Content-Type: text/plain; charset=UTF-8

I agree 100% with what Melinda says.

Regards,
Mary.

On Wed, Apr 20, 2016 at 9:10 PM, Melinda Shore <melinda.shore@gmail.com>
wrote:

> On 4/20/16 5:07 PM, Adam Roach wrote:
>
>> On 4/20/16 08:26, thomas nadeau wrote:
>>
>>>
>>> On Apr 20, 2016, at 6:48 AM, Harald Alvestrand <harald@alvestrand.no>
>>>> wrote:
>>>> If we don't see such a cohort, we need to dig deeper.
>>>>
>>> Or perhaps wonder why we should concern ourselves with this at all?
>>>
>> Because it's their Internet, too.
>>
>
> I'm not sure that's actually responsive.  The internet "belongs
> to" uncountable numbers of people who will never, ever participate
> in making protocol standards.
>
> If people are not participating in mailing lists, reviewing
> documents, and so on, it's not at all clear to me why meeting
> in their corner of the world is going to change anything.
> Historically it does not seem to have been very effective.
> I do think that what Nalini is doing (putting together
> document review teams/study groups for new participants)
> seems likely to be more effective than changing meeting
> venues, and I'm very curious to see how that works out.
>
> Personally, I'm completely unfunded and geographically
> remote but still chair a working group, belong to directorates,
> author drafts, and so on.  For me, the expectation that we
> will attend meetings in person every single time is a
> much bigger barrier to participation than having the meetings
> someplace inconvenient (i.e. having to travel at all is far
> more onerous than having to spend two days in transit if I do
> travel), and I'd really like to see us let go of expectations
> that IETF participation means going to meetings (particularly
> since it's not how we're *supposed* to work, according to
> our own process documents).
>
> I expect that this discussion, coupled with the repeat-ad-
> infinitum discussion of what's required of IETF leadership
> positions makes it how clear just how deeply into the pockets
> of the big network gizmo manufacturers the IETF really is.
>
> Melinda
>
>
>
>

--001a114f2250f6e62c0530fd8ef3
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">I agree 100% with what Melinda says.<div><br></div><div>Re=
gards,</div><div>Mary.=C2=A0</div></div><div class=3D"gmail_extra"><br><div=
 class=3D"gmail_quote">On Wed, Apr 20, 2016 at 9:10 PM, Melinda Shore <span=
 dir=3D"ltr">&lt;<a href=3D"mailto:melinda.shore@gmail.com" target=3D"_blan=
k">melinda.shore@gmail.com</a>&gt;</span> wrote:<br><blockquote class=3D"gm=
ail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-le=
ft:1ex"><span class=3D"">On 4/20/16 5:07 PM, Adam Roach wrote:<br>
</span><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-=
left:1px #ccc solid;padding-left:1ex"><span class=3D"">
On 4/20/16 08:26, thomas nadeau wrote:<br>
</span><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-=
left:1px #ccc solid;padding-left:1ex">
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><span class=3D"">
On Apr 20, 2016, at 6:48 AM, Harald Alvestrand &lt;<a href=3D"mailto:harald=
@alvestrand.no" target=3D"_blank">harald@alvestrand.no</a>&gt;<br>
wrote:<br></span><span class=3D"">
If we don&#39;t see such a cohort, we need to dig deeper.<br>
</span></blockquote><span class=3D"">
Or perhaps wonder why we should concern ourselves with this at all?<br>
</span></blockquote><span class=3D"">
Because it&#39;s their Internet, too.<br>
</span></blockquote>
<br>
I&#39;m not sure that&#39;s actually responsive.=C2=A0 The internet &quot;b=
elongs<br>
to&quot; uncountable numbers of people who will never, ever participate<br>
in making protocol standards.<br>
<br>
If people are not participating in mailing lists, reviewing<br>
documents, and so on, it&#39;s not at all clear to me why meeting<br>
in their corner of the world is going to change anything.<br>
Historically it does not seem to have been very effective.<br>
I do think that what Nalini is doing (putting together<br>
document review teams/study groups for new participants)<br>
seems likely to be more effective than changing meeting<br>
venues, and I&#39;m very curious to see how that works out.<br>
<br>
Personally, I&#39;m completely unfunded and geographically<br>
remote but still chair a working group, belong to directorates,<br>
author drafts, and so on.=C2=A0 For me, the expectation that we<br>
will attend meetings in person every single time is a<br>
much bigger barrier to participation than having the meetings<br>
someplace inconvenient (i.e. having to travel at all is far<br>
more onerous than having to spend two days in transit if I do<br>
travel), and I&#39;d really like to see us let go of expectations<br>
that IETF participation means going to meetings (particularly<br>
since it&#39;s not how we&#39;re *supposed* to work, according to<br>
our own process documents).<br>
<br>
I expect that this discussion, coupled with the repeat-ad-<br>
infinitum discussion of what&#39;s required of IETF leadership<br>
positions makes it how clear just how deeply into the pockets<br>
of the big network gizmo manufacturers the IETF really is.<span class=3D"HO=
EnZb"><font color=3D"#888888"><br>
<br>
Melinda<br>
<br>
<br>
<br>
</font></span></blockquote></div><br></div>

--001a114f2250f6e62c0530fd8ef3--


From nobody Thu Apr 21 07:51:23 2016
Return-Path: <hallam@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 7F37112E952 for <ietf@ietfa.amsl.com>; Thu, 21 Apr 2016 07:51:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.4
X-Spam-Level: 
X-Spam-Status: No, score=-2.4 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.199, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 73KRy2ZLRf1t for <ietf@ietfa.amsl.com>; Thu, 21 Apr 2016 07:51:15 -0700 (PDT)
Received: from mail-lb0-x231.google.com (mail-lb0-x231.google.com [IPv6:2a00:1450:4010:c04::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 C6B8F12E597 for <ietf@ietf.org>; Thu, 21 Apr 2016 07:50:57 -0700 (PDT)
Received: by mail-lb0-x231.google.com with SMTP id u8so28432743lbk.0 for <ietf@ietf.org>; Thu, 21 Apr 2016 07:50:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc; bh=rCuKHDcXJtfmzf3x1hccj7IX8S9PqOf5/Civj3BFLRs=; b=sk1ZUngUUXL5WBBM++b31xAi4nwyHzTG0tJiPR5SvglA4KZpe8PVEIa79i7XsINsVs Qq/g2nb2EI77HjTWvd7f7HTOJJKm251+xT8SAZwBP5R2CZOExe/6jJNHICmYu1cKsjRl iiyGN+r9F6FJm7QlxvsJLAbRX1hl3sSSaLGXBsoLUDnqveBdgc89ki2SIXyXv2FWlLo+ Mo9MoDYEVwV+Gkfrw7678rpY2aX1rIpltOmtOqf5WNGxqWhRB61Xr8HeQUFVqHAGtXJS j5Y9lQve3YR/5UszJELOWchG0XoeMlCWor7KmFDRgEQZaQoMXWLipJIo1D5LMSpz7xTQ KNUA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:date :message-id:subject:from:to:cc; bh=rCuKHDcXJtfmzf3x1hccj7IX8S9PqOf5/Civj3BFLRs=; b=ijWREY7AsGFetpSg8tsN63ScGawjJhcjUsqg1UDk7coSgbRFioshat631NZPvrozZ7 mRi9XOiybifyRLlGTfPXAEyCSyI7hUHO3aPSlNOZb39IUzc5Ecq+l3Dv19xSZzVfr6Ez wc3Kz1M1qUwn7N0YRAKa6qvUYHawmGQ8l+09uGEzDE1JJaUBuDmhnka+BbOjLYMhCOb1 SX7Flze2pdS9PsFfB/RhrH93rPOD+EznB6PZ/6N1HwZrAKsa2qIV5IG9qn3Q4ExKN7g+ m1E3D/q9474Jf99kk5AElrsDBuWiQw2O3zLDXrbzdnA/XUCEoop0U20YJnbcxyNoe6M0 Gwbg==
X-Gm-Message-State: AOPr4FX495Qhd14Vehny5rmn6fcY2CET+DuNickFQSSbxcHEUZdgmyl25vm6ZTMJVq+ZeqhXakxY0DbOIpzPdw==
MIME-Version: 1.0
X-Received: by 10.112.135.4 with SMTP id po4mr6609656lbb.112.1461250255990; Thu, 21 Apr 2016 07:50:55 -0700 (PDT)
Sender: hallam@gmail.com
Received: by 10.112.3.102 with HTTP; Thu, 21 Apr 2016 07:50:55 -0700 (PDT)
In-Reply-To: <57151C55.30206@gmail.com>
References: <20160418161552.9368.65562.idtracker@ietfa.amsl.com> <8fb376e11631f9ddf73f9385ec5472c3.squirrel@www.trepanning.net> <57151C55.30206@gmail.com>
Date: Thu, 21 Apr 2016 10:50:55 -0400
X-Google-Sender-Auth: G6vZDphk8F7odZO_b0phbc4_8ko
Message-ID: <CAMm+LwjW9+Y6E=t7oNjFcviQoXLESS-C-bn+W9rymjaHXUJskQ@mail.gmail.com>
Subject: Re: Interim step on meetings site feedback for sites currently under active consideration
From: Phillip Hallam-Baker <phill@hallambaker.com>
To: Melinda Shore <melinda.shore@gmail.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/Bb4de_PSfJymT7tunZltPSV8NJE>
Cc: IETF Discussion Mailing List <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, 21 Apr 2016 14:51:17 -0000

I think people are missing the point of the 'world tour'. It is not
just what happens inside the IETF that is important, it is the
perception of the IETF in other forums. In particular government
forums.

The politics of communication systems sit in the top tier in
international diplomacy. Only actual military conflict outranks them.
One thing that every successful politician understands is the impact
of communication infrastructures on their position.

The Clinton Gore online campaign set up a Web server in 1992. That is
before Mosaic came out. The BA location was being decided round about
the time that the Arab Spring was occurring. How quickly people
forget.

As far as travel goes, BA was less inconvenient for me than Hawaii.
And dramatically less difficult than Japan or South Korea.

But what we are up to is causing vastly more inconvenience to a lot
more people than a few long distance plane rides. The Internet isn't
just cat pictures and a mountain of porn. The Internet is the pulse of
freedom.


From nobody Thu Apr 21 07:55:30 2016
Return-Path: <mellon@fugue.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 DBF9D12D71D for <ietf@ietfa.amsl.com>; Thu, 21 Apr 2016 07:55:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.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 RjFDlhvs93b2 for <ietf@ietfa.amsl.com>; Thu, 21 Apr 2016 07:55:25 -0700 (PDT)
Received: from mail-lf0-x22f.google.com (mail-lf0-x22f.google.com [IPv6:2a00:1450:4010:c07::22f]) (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 B7E4312D10F for <ietf@ietf.org>; Thu, 21 Apr 2016 07:55:24 -0700 (PDT)
Received: by mail-lf0-x22f.google.com with SMTP id j11so62276580lfb.1 for <ietf@ietf.org>; Thu, 21 Apr 2016 07:55:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=U2MxC2GHE18wUNcjWy7nHER02fDqSf9tXz/qUhIYxeE=; b=o0GoJn8uskbIw2vZP9iM+Y6VtVObrPas7fhLfLbPq/tqgLmDJsWB+KTzPg21EZPbRh CUDOtepLblmLn5nB8lLkqegOmW3odYKdOdLd1ViUS2QA4tr2hB8ZYKahivATJvIp0eNN w2CFIf5u7S8UHXeVOwOR4nYCXsgHJJcjT0Kwg9UkF38MYykLZxAtok9AOi/b9sve9iWf sgYx994L4iTyIqTfWr2kg2hDtF9r2/phSP9OlBGoyKAYUkr0yC4ycpsH4jSlFrDkh8wm QflOBRyh00At9a99PCFjDK7gVwuiIukmpsBV8iCf99Th+ycKX8WPFeaN3u67EKC0GLti fWDA==
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=U2MxC2GHE18wUNcjWy7nHER02fDqSf9tXz/qUhIYxeE=; b=jZFCwxXiXjrMehQ6ghoy8dqJ/Sgi23OC8FtBw2RqVvvjNOr8qAj//erRnUoe6Nvr8S cORv4bl/wV92GcZOqo1ZowVCZMtztygivB5r+AuyZJq8qohQqISROoqg5r+xOwI15hsZ q2CU+udA6D6UAjG8TU5L7VCL2LtNaBoJ+e9tg0lpJrou7QMuQyjtM8kb/M51GUopeRTN 0eqMHDGxXmCgtVYHh5NnTqSYBBvj93WV7JHaMHgAjhiypi1yA2vgSKhXoHXEOCLQQBGk l0u/oIh0aZ9Dwoon8wBzR3l+nqxkAXn+Pcie+41ZWUj8u9ssaMrsde2LzmZ0UHB+GFln 3NIQ==
X-Gm-Message-State: AOPr4FW0SkHuv5zvo6P1JuM5dcH+ryKPCoa5dS0gCgqFQsGoW95DSxlW+39oOuBUSmL2MRbHqqrQhbyhYlnfrQ==
X-Received: by 10.25.153.136 with SMTP id b130mr6502577lfe.53.1461250522912; Thu, 21 Apr 2016 07:55:22 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.25.213.19 with HTTP; Thu, 21 Apr 2016 07:54:43 -0700 (PDT)
X-Originating-IP: [71.233.41.235]
In-Reply-To: <CAMm+LwjW9+Y6E=t7oNjFcviQoXLESS-C-bn+W9rymjaHXUJskQ@mail.gmail.com>
References: <20160418161552.9368.65562.idtracker@ietfa.amsl.com> <8fb376e11631f9ddf73f9385ec5472c3.squirrel@www.trepanning.net> <57151C55.30206@gmail.com> <CAMm+LwjW9+Y6E=t7oNjFcviQoXLESS-C-bn+W9rymjaHXUJskQ@mail.gmail.com>
From: Ted Lemon <mellon@fugue.com>
Date: Thu, 21 Apr 2016 10:54:43 -0400
Message-ID: <CAPt1N1=KeDCOg4XpGxaCuP5EDmgFARgYxBhvg3E386=dBFkbxQ@mail.gmail.com>
Subject: Re: Interim step on meetings site feedback for sites currently under active consideration
To: Phillip Hallam-Baker <phill@hallambaker.com>
Content-Type: multipart/alternative; boundary=001a1140392658b1e20530ffe68f
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/nVAhHS_okqN1TuFP7fmmnfmznE4>
Cc: IETF Discussion Mailing List <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, 21 Apr 2016 14:55:29 -0000

--001a1140392658b1e20530ffe68f
Content-Type: text/plain; charset=UTF-8

On Thu, Apr 21, 2016 at 10:50 AM, Phillip Hallam-Baker <
phill@hallambaker.com> wrote:

> I think people are missing the point of the 'world tour'. It is not
> just what happens inside the IETF that is important, it is the
> perception of the IETF in other forums. In particular government
> forums.
>

+1

However, I think what Melinda is saying and what you are saying are not in
conflict.   We have a problem in the IETF that in-person attendance counts
for too much.   This is a real problem.   We should do something about it.
  Then the question of whether to do world tours becomes more of a
logistical/financial issue, which is really what it should be.   And like
you, I found this trip much easier than going to Asia, although I know our
colleagues from Asia found it just the opposite. :)

--001a1140392658b1e20530ffe68f
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On T=
hu, Apr 21, 2016 at 10:50 AM, Phillip Hallam-Baker <span dir=3D"ltr">&lt;<a=
 href=3D"mailto:phill@hallambaker.com" target=3D"_blank">phill@hallambaker.=
com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"mar=
gin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I think people =
are missing the point of the &#39;world tour&#39;. It is not<br>
just what happens inside the IETF that is important, it is the<br>
perception of the IETF in other forums. In particular government<br>
forums.<br></blockquote><div><br></div><div>+1</div><div><br></div><div>How=
ever, I think what Melinda is saying and what you are saying are not in con=
flict. =C2=A0 We have a problem in the IETF that in-person attendance count=
s for too much. =C2=A0 This is a real problem. =C2=A0 We should do somethin=
g about it. =C2=A0 Then the question of whether to do world tours becomes m=
ore of a logistical/financial issue, which is really what it should be. =C2=
=A0 And like you, I found this trip much easier than going to Asia, althoug=
h I know our colleagues from Asia found it just the opposite. :)=C2=A0</div=
></div></div></div>

--001a1140392658b1e20530ffe68f--


From nobody Thu Apr 21 08:11:28 2016
Return-Path: <adrian@olddog.co.uk>
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 4737F12DE7B; Thu, 21 Apr 2016 08:11:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7] 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 NSOy-vKmho35; Thu, 21 Apr 2016 08:11:23 -0700 (PDT)
Received: from asmtp2.iomartmail.com (asmtp2.iomartmail.com [62.128.201.249]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CCCB712E436; Thu, 21 Apr 2016 08:11:19 -0700 (PDT)
Received: from asmtp2.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp2.iomartmail.com (8.13.8/8.13.8) with ESMTP id u3LF95tG009304; Thu, 21 Apr 2016 16:09:05 +0100
Received: from 950129200 ([213.5.92.177]) (authenticated bits=0) by asmtp2.iomartmail.com (8.13.8/8.13.8) with ESMTP id u3LF93K5009266 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO); Thu, 21 Apr 2016 16:09:04 +0100
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: <ietf@ietf.org>
References: <20160419141640.31545.54742.idtracker@ietfa.amsl.com>
In-Reply-To: <20160419141640.31545.54742.idtracker@ietfa.amsl.com>
Subject: RE: Last Call: <draft-leiba-cotton-iana-5226bis-12.txt> (Guidelines for Writing an IANA Considerations Section in RFCs) to Best Current Practice
Date: Thu, 21 Apr 2016 16:09:05 +0100
Message-ID: <06b601d19bdf$bf725b10$3e571130$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQD6sjSRIIB+2MCyMyZ0rhhMk0byWqFCSc7A
Content-Language: en-gb
X-TM-AS-MML: disable
X-TM-AS-Product-Ver: IMSS-7.1.0.1679-8.0.0.1202-22274.006
X-TM-AS-Result: No--12.327-10.0-31-10
X-imss-scan-details: No--12.327-10.0-31-10
X-TMASE-MatchedRID: gjZGo2H/wj9fsB4HYR80ZggKAWhuC2ojb6bRSg4rpzuo+b+yOP0oGOhu cPsHg+lUVou3tdUwrwv+5Sngvyncm4XVLLOFXneznVTWWiNp+v+sBP5mv7DuayG8WMGwsRk0+6X wUEj2jUrctUcKuR6f5ATqfG8+r3FKZFRqrQuuReFdIpzA9POr8uBgp+G3IXxrIfg3G4Q08Gj+tn MvnQl+U/AFbtEwRr9cvMCF9IKt8R4BDyUlObljv691/YHX0i1lu1b0t4ooa9vROhK+RFWo5hzll v0af4rKafcnFY/rkJAAzLwZoZKu8lDAEECFhQnKeUyVZX4ivrtzd7C7BtJobusoDDE6CvPdPlF5 N5t2gL/us5Y6tXWJTG2+sEpeMprvCEMM7muZaodMkJTSstTiqM/rSr8VfmGwRoS5c9eVHmoDdbq f2nbl9FXEvU+FtIj3eAZCO3WnFdSL3nwNzypZrJgGnz93PV93s+SyIdviDnyhUoducQu06XkvYG lzSDgV2TaDGX0BbTtIcWiYbodCz2bRarzMLj8yngIgpj8eDcC063Wh9WVqghziNLWewPgd+gtHj 7OwNO3Ix3Icp6zuW/KlLG2J0ZSz489InB5iHeKtG/HGcy1UeOmAfNw/VyJk
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/8FJpn9ZKOBz6Kn4MOnwDWtlVLiE>
Cc: draft-leiba-cotton-iana-5226bis@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: adrian@olddog.co.uk
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, 21 Apr 2016 15:11:27 -0000

Thanks to the authors for resurrecting this work, and thanks also for addressing
comments from the previous review cycle. I went back and read the review
comments I entered back in 2014 when the document was last up before the IESG
(https://datatracker.ietf.org/doc/draft-leiba-cotton-iana-5226bis/ballot/#adrian
-farrel) before I did this review and I feel that the general point still
applies that it is really hard for a document author to extract a simple
"cookbook for an IANA considerations section". [I'm afraid I can no longer swap
in the context of any email threads that happened at that time.] Maybe this is
intended to be covered at the URL mentioned in 1.2 - that would be good, but had
I held my breath back in 2014 and waited for this URL to receive some content, I
would not now be bothering you with this email!  (All the detailed nits I raised
back then seem to have been addressed, however, so very many thanks!)

I think this document is ready for publication, but I wonder whether some
further emphasis for clarity might be added to section 4.4. The point I would
like to labor is that the assignment is made for a specific use not for a
specific person, organization, company, etc. You do already state that changes
to the registration of a First Come First Served code point retain compatibility
with the current usage of that code point, and this is exactly the right
message. But I have recently heard several cases of a code point that was
assigned using FCFS as "Foo Corp's BLEAGH protocol" being completely repurposed
by Foo Corp as "Foo Corp's YUCK protocol". You appear to be saying that "this
should not happen" and I largely agree (modulo - we really know this is not in
the field), but how is IANA to interpret this text and how do you expect them to
act if Foo Corp sends them mail to say what they have done? Maybe also a forward
pointer to 9.4 and 9.5?

In 4.9 you have
   For the Standards Action policy, values are assigned only through
   Standards Track or Best Current Practice RFCs approved by the IESG.
Do you want to harmonize this with language in other sections by saying "IETF
Stream" not "approved by the IESG"?

15.1 has a dated title.

Cheers,
Adrian

> The IESG has received a request from an individual submitter to consider
> the following document:
> - 'Guidelines for Writing an IANA Considerations Section in RFCs'
>   <draft-leiba-cotton-iana-5226bis-12.txt> as Best Current Practice


From nobody Thu Apr 21 09:40:53 2016
Return-Path: <nalini.elkins@insidethestack.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 B006612E13B for <ietf@ietfa.amsl.com>; Thu, 21 Apr 2016 09:40:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.619
X-Spam-Level: 
X-Spam-Status: No, score=-2.619 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=yahoo.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 dQgPMvAxY9Yu for <ietf@ietfa.amsl.com>; Thu, 21 Apr 2016 09:40:50 -0700 (PDT)
Received: from nm24-vm4.bullet.mail.ne1.yahoo.com (nm24-vm4.bullet.mail.ne1.yahoo.com [98.138.91.184]) (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 BAE4212E070 for <ietf@ietf.org>; Thu, 21 Apr 2016 09:40:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1461256850; bh=8OUAeLvOsEoC3jOMTbw3TYHo3j9/xReRlRp2vIdKGO0=; h=Date:From:Reply-To:To:In-Reply-To:References:Subject:From:Subject; b=mOA6x8cSCYrkaTgGzhmMjiSycnvdWpuiPe/jDwttdeuptD0SHcrV5buyf+0gA9T1dxclPTIagPL60l8cNUCIb/agaJ07WicF7sYtSRw2j+IpRT6ddWTiuHLRLt0R5IAiqCpyrAkSurgTTmBXYknmQyJtxXABkx/nAb94et0EwXYW/rmSLuLVhE/+qYUKgJ3PecxUNC3ZUULHtpQMGcwWFM2A5B2JhIFvX1L1Gv457H5wR2q1JwN72SYhqTm3BDK3i5fbtu7g3nDYEzlObtgOFVHhEqrcvQFPD4sJQpMOZ/oq5MZsKC8EoxDxdOJERQvK/23Z6gmkwUKqn7WdQCovmw==
Received: from [98.138.101.129] by nm24.bullet.mail.ne1.yahoo.com with NNFMP;  21 Apr 2016 16:40:50 -0000
Received: from [98.138.87.5] by tm17.bullet.mail.ne1.yahoo.com with NNFMP; 21 Apr 2016 16:40:49 -0000
Received: from [127.0.0.1] by omp1005.mail.ne1.yahoo.com with NNFMP; 21 Apr 2016 16:40:49 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 938008.60112.bm@omp1005.mail.ne1.yahoo.com
X-YMail-OSG: NBxI_UIVM1nSl2aSJsk51E3OexR0QqI0vE21Xtl2B9JXCVG7jVGLa8Pb5NGL2xG YLVKPAzKmZ4WNnj_iMLoSG16UXrHrzUt2eqnEjH.KhvED.BRz.ylQFRlUgu5ZSEk1jPh46EOHe1g .ayCDB1L2nVdTBlilcnfMW7bXAaAH0KHpPzccTAKJKMM5bSqzPVKCekBzZ0M0kbd09ZExa4i6HNL ipAU6TDTIOmG_oD3d8FrtziAZEjw3lw1db6TeX7yp.PgXKKfVF7jQ_CJtxtszxj4jq0eVi73cZ9V NhPv0Qzw7soL6qIbI4aL60GulgoFdspAkZFiEBomwWAxxEWu2hxp9zeQ2ygBBVdf7QswUiAZwlrv 7fKKBPlYnl_5uoL2jCBp_B4Nn5Hl9emqr2tFW0HH538mOVbjqDAQzfG5Ry02eY8b9_SCMF7NFxNz cMXSE5r0DFFiMQGQQbH1xF3wkhma3Z7inXY6IWRWAF0pGKteFAvbarXKkkh556_XuIUsYlYihdUN X1WpSz4f4c60nVc7y
Received: by 98.138.105.240; Thu, 21 Apr 2016 16:40:49 +0000 
Date: Thu, 21 Apr 2016 16:40:33 +0000 (UTC)
From: <nalini.elkins@insidethestack.com>
To: Melinda Shore <melinda.shore@gmail.com>, ietf <ietf@ietf.org>
Message-ID: <425793799.4005281.1461256833680.JavaMail.yahoo@mail.yahoo.com>
In-Reply-To: <57183686.8000307@gmail.com>
References: <57183686.8000307@gmail.com>
Subject: Re: Interim step on meetings site feedback for sites currently under active consideration
MIME-Version: 1.0
Content-Type: multipart/alternative;  boundary="----=_Part_4005280_399053617.1461256833675"
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/WNHMfqirFh8v7vtx1xEVUO1YWCY>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: nalini.elkins@insidethestack.com
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, 21 Apr 2016 16:40:52 -0000

------=_Part_4005280_399053617.1461256833675
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

=C2=A0

 =20
On 4/20/16 5:07 PM, Adam Roach wrote:
> On 4/20/16 08:26, thomas nadeau wrote:
>>
>>>> On Apr 20, 2016, at 6:48 AM, Harald Alvestrand <harald@alvestrand.no>
>>>> wrote:
>>>> If we don't see such a cohort, we need to dig deeper.
>>> Or perhaps wonder why we should concern ourselves with this at all?
>>> Because it's their Internet, too.

>>I'm not sure that's actually responsive.=C2=A0 The internet "belongs
>>to" uncountable numbers of people who will never, ever participate
>>in making protocol standards.

>>If people are not participating in mailing lists, reviewing
>>documents, and so on, it's not at all clear to me why meeting
>>in their corner of the world is going to change anything.
>>Historically it does not seem to have been very effective.
>>I do think that what Nalini is doing (putting together
>>document review teams/study groups for new participants)
>>seems likely to be more effective than changing meeting
>>venues, and I'm very curious to see how that works out.
Melinda, thank you for your support. =C2=A0It means a lot to me.
Having said that, with this initiative (as with any new project!), there wi=
ll be false starts, miscommunication, scalability issues, etc. =C2=A0But, (=
obviously) I think this is, at least, one of the right things to do and we =
will figure it out.
As a status: we have 43 people signed up so far for Internet Draft review t=
eams and 3 teams starting (Spanish: DNSOP, =C2=A0Spanish: v6ops/ 6man / sun=
set4, and English: 6lo, 6tisch).
I have heard from the Indian community that they will be publicizing in Ind=
ia, so in the next couple of weeks hope to get quite a few more in that reg=
ion.
So, speaking of that - if this initiative is successful, it is because it i=
s building on the efforts of the people in the various geographic regions. =
=C2=A0As I have said before - standing on the shoulders of giants. =C2=A0 A=
 huge effort has been and continues to be made in a number of geographic ar=
eas to increase awareness of the IETF and increase participation.
The way I have gotten people to sign up for our initiative is by talking to=
 the people leading the remote hubs and posting to their email lists. =C2=
=A0In local language, if necessary. =C2=A0Including the delightful Boston h=
ub! =C2=A0(BTW, anyone interested in starting a SF Bay Area / Silicon Valle=
y Hub, please contact me unicast. =C2=A0Why not us?)
I am also hearing from the Chinese community that they are exploring remote=
 hubs. =C2=A0Do not know if any of them are ready to comment.
But, IMHO, I think a fruitful discussion might be: where do we see all this=
 going? =C2=A0That is, what do we think the IETF will look like in 3 years,=
 5 years, 10 years? =C2=A0The reason I say this is because I believe that i=
nforms our thinking. =C2=A0 Any business plans for (at least) 3 - 5 years d=
own the road, why don't we at the IETF talk about it?
I, personally, think that the winds are shifting. =C2=A0 The world is getti=
ng smaller and smaller. =C2=A0In particular, for the kinds of people who ar=
e "crazy" enough to be finding their energy in writing new protocols and li=
ving and breathing networks. =C2=A0These people come from all corners of th=
e globe and this will become only more so.
I also, personally, am very much for face-to-face. =C2=A0 We cannot ignore =
that we are, after all, human.
Having an IETF in different parts of the world, to me, also validates the e=
fforts of the local community who has worked so hard to get contributors.
I live in California, it is a state where there is no majority ethnic or so=
cial group. =C2=A0IMHO, that is where the IETF is going.
Nalini
=C2=A0  
------=_Part_4005280_399053617.1461256833675
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<html><head></head><body><div style=3D"color:#000; background-color:#fff; f=
ont-family:HelveticaNeue-Light, Helvetica Neue Light, Helvetica Neue, Helve=
tica, Arial, Lucida Grande, sans-serif;font-size:16px"><div id=3D"yui_3_16_=
0_ym19_1_1461254264833_16981">&nbsp;</div><div class=3D"qtdSeparateBR"><br>=
<br></div><div class=3D"yahoo_quoted" id=3D"yui_3_16_0_ym19_1_1461254264833=
_16989" style=3D"display: block;"><div style=3D"font-family: HelveticaNeue-=
Light, Helvetica Neue Light, Helvetica Neue, Helvetica, Arial, Lucida Grand=
e, sans-serif; font-size: 16px;" id=3D"yui_3_16_0_ym19_1_1461254264833_1698=
8"><div style=3D"font-family: HelveticaNeue, Helvetica Neue, Helvetica, Ari=
al, Lucida Grande, sans-serif; font-size: 16px;" id=3D"yui_3_16_0_ym19_1_14=
61254264833_16987"><div dir=3D"ltr" id=3D"yui_3_16_0_ym19_1_1461254264833_1=
6986"> </div> <div class=3D"y_msg_container" id=3D"yui_3_16_0_ym19_1_146125=
4264833_17000"><br>On 4/20/16 5:07 PM, Adam Roach wrote:<br>&gt; On 4/20/16=
 08:26, thomas nadeau wrote:<br>&gt;&gt;<br>&gt;&gt;&gt;&gt; On Apr 20, 201=
6, at 6:48 AM, Harald Alvestrand &lt;<a ymailto=3D"mailto:harald@alvestrand=
.no" href=3D"mailto:harald@alvestrand.no">harald@alvestrand.no</a>&gt;<br>&=
gt;&gt;&gt;&gt; wrote:<br>&gt;&gt;&gt;&gt; If we don't see such a cohort, w=
e need to dig deeper.<br>&gt;&gt;&gt; Or perhaps wonder why we should conce=
rn ourselves with this at all?</div><div class=3D"y_msg_container" id=3D"yu=
i_3_16_0_ym19_1_1461254264833_17000"><br>&gt;&gt;&gt; Because it's their In=
ternet, too.<br><br>&gt;&gt;I'm not sure that's actually responsive.&nbsp; =
The internet "belongs<br>&gt;&gt;to" uncountable numbers of people who will=
 never, ever participate<br>&gt;&gt;in making protocol standards.<br><br>&g=
t;&gt;If people are not participating in mailing lists, reviewing<br>&gt;&g=
t;documents, and so on, it's not at all clear to me why meeting<br>&gt;&gt;=
in their corner of the world is going to change anything.<br>&gt;&gt;Histor=
ically it does not seem to have been very effective.<br>&gt;&gt;I do think =
that what Nalini is doing (putting together<br>&gt;&gt;document review team=
s/study groups for new participants)<br>&gt;&gt;seems likely to be more eff=
ective than changing meeting<br>&gt;&gt;venues, and I'm very curious to see=
 how that works out.</div><div class=3D"y_msg_container" id=3D"yui_3_16_0_y=
m19_1_1461254264833_17000"><br></div><div class=3D"y_msg_container" id=3D"y=
ui_3_16_0_ym19_1_1461254264833_17000">Melinda, thank you for your support. =
&nbsp;It means a lot to me.</div><div class=3D"y_msg_container" id=3D"yui_3=
_16_0_ym19_1_1461254264833_17000"><br></div><div class=3D"y_msg_container" =
id=3D"yui_3_16_0_ym19_1_1461254264833_17000">Having said that, with this in=
itiative (as with any new project!), there will be false starts, miscommuni=
cation, scalability issues, etc. &nbsp;But, (obviously) I think this is, at=
 least, one of the right things to do and we will figure it out.</div><div =
class=3D"y_msg_container" id=3D"yui_3_16_0_ym19_1_1461254264833_17000"><br>=
</div><div class=3D"y_msg_container" id=3D"yui_3_16_0_ym19_1_1461254264833_=
17000" dir=3D"ltr">As a status: we have 43 people signed up so far for Inte=
rnet Draft review teams and 3 teams starting (Spanish: DNSOP, &nbsp;Spanish=
: v6ops/ 6man / sunset4, and English: 6lo, 6tisch).</div><div class=3D"y_ms=
g_container" id=3D"yui_3_16_0_ym19_1_1461254264833_17000" dir=3D"ltr"><br><=
/div><div class=3D"y_msg_container" id=3D"yui_3_16_0_ym19_1_1461254264833_1=
7000" dir=3D"ltr">I have heard from the Indian community that they will be =
publicizing in India, so in the next couple of weeks hope to get quite a fe=
w more in that region.</div><div class=3D"y_msg_container" id=3D"yui_3_16_0=
_ym19_1_1461254264833_17000" dir=3D"ltr"><br></div><div class=3D"y_msg_cont=
ainer" id=3D"yui_3_16_0_ym19_1_1461254264833_17000" dir=3D"ltr">So, speakin=
g of that - if this initiative is successful, it is because it is building =
on the efforts of the people in the various geographic regions. &nbsp;As I =
have said before - standing on the shoulders of giants. &nbsp; A huge effor=
t has been and continues to be made in a number of geographic areas to incr=
ease awareness of the IETF and increase participation.</div><div class=3D"y=
_msg_container" id=3D"yui_3_16_0_ym19_1_1461254264833_17000" dir=3D"ltr"><b=
r></div><div class=3D"y_msg_container" id=3D"yui_3_16_0_ym19_1_146125426483=
3_17000" dir=3D"ltr">The way I have gotten people to sign up for our initia=
tive is by talking to the people leading the remote hubs and posting to the=
ir email lists. &nbsp;In local language, if necessary. &nbsp;Including the =
delightful Boston hub! &nbsp;(BTW, anyone interested in starting a SF Bay A=
rea / Silicon Valley Hub, please contact me unicast. &nbsp;Why not us?)</di=
v><div class=3D"y_msg_container" id=3D"yui_3_16_0_ym19_1_1461254264833_1700=
0"><br></div><div class=3D"y_msg_container" id=3D"yui_3_16_0_ym19_1_1461254=
264833_17000">I am also hearing from the Chinese community that they are ex=
ploring remote hubs. &nbsp;Do not know if any of them are ready to comment.=
</div><div class=3D"y_msg_container" id=3D"yui_3_16_0_ym19_1_1461254264833_=
17000"><br></div><div class=3D"y_msg_container" id=3D"yui_3_16_0_ym19_1_146=
1254264833_17000">But, IMHO, I think a fruitful discussion might be: where =
do we see all this going? &nbsp;That is, what do we think the IETF will loo=
k like in 3 years, 5 years, 10 years? &nbsp;The reason I say this is becaus=
e I believe that informs our thinking. &nbsp; Any business plans for (at le=
ast) 3 - 5 years down the road, why don't we at the IETF talk about it?</di=
v><div class=3D"y_msg_container" id=3D"yui_3_16_0_ym19_1_1461254264833_1700=
0"><br></div><div class=3D"y_msg_container" id=3D"yui_3_16_0_ym19_1_1461254=
264833_17000" dir=3D"ltr">I, personally, think that the winds are shifting.=
 &nbsp; The world is getting smaller and smaller. &nbsp;In particular, for =
the kinds of people who are "crazy" enough to be finding their energy in wr=
iting new protocols and living and breathing networks. &nbsp;These people c=
ome from all corners of the globe and this will become only more so.</div><=
div class=3D"y_msg_container" id=3D"yui_3_16_0_ym19_1_1461254264833_17000" =
dir=3D"ltr"><br></div><div class=3D"y_msg_container" id=3D"yui_3_16_0_ym19_=
1_1461254264833_17000" dir=3D"ltr">I also, personally, am very much for fac=
e-to-face. &nbsp; We cannot ignore that we are, after all, human.</div><div=
 class=3D"y_msg_container" id=3D"yui_3_16_0_ym19_1_1461254264833_17000" dir=
=3D"ltr"><br></div><div class=3D"y_msg_container" id=3D"yui_3_16_0_ym19_1_1=
461254264833_17000" dir=3D"ltr">Having an IETF in different parts of the wo=
rld, to me, also validates the efforts of the local community who has worke=
d so hard to get contributors.</div><div class=3D"y_msg_container" id=3D"yu=
i_3_16_0_ym19_1_1461254264833_17000" dir=3D"ltr"><br></div><div class=3D"y_=
msg_container" id=3D"yui_3_16_0_ym19_1_1461254264833_17000" dir=3D"ltr">I l=
ive in California, it is a state where there is no majority ethnic or socia=
l group. &nbsp;IMHO, that is where the IETF is going.</div><div class=3D"y_=
msg_container" id=3D"yui_3_16_0_ym19_1_1461254264833_17000"><br></div><div =
class=3D"y_msg_container" id=3D"yui_3_16_0_ym19_1_1461254264833_17000">Nali=
ni</div><div class=3D"y_msg_container" id=3D"yui_3_16_0_ym19_1_146125426483=
3_17000"><br></div><div class=3D"y_msg_container" id=3D"yui_3_16_0_ym19_1_1=
461254264833_17000">&nbsp;</div> </div> </div>  </div></div></body></html>
------=_Part_4005280_399053617.1461256833675--


From nobody Thu Apr 21 10:12:05 2016
Return-Path: <adam@nostrum.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 B337212E731 for <ietf@ietfa.amsl.com>; Thu, 21 Apr 2016 10:12:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.895
X-Spam-Level: 
X-Spam-Status: No, score=-2.895 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.996] 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 ao7EKP62GOXb for <ietf@ietfa.amsl.com>; Thu, 21 Apr 2016 10:12:00 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (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 D702712E6FF for <ietf@ietf.org>; Thu, 21 Apr 2016 10:12:00 -0700 (PDT)
Received: from Orochi.local (99-152-145-110.lightspeed.dllstx.sbcglobal.net [99.152.145.110]) (authenticated bits=0) by nostrum.com (8.15.2/8.14.9) with ESMTPSA id u3LHBqK5045441 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Thu, 21 Apr 2016 12:11:52 -0500 (CDT) (envelope-from adam@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host 99-152-145-110.lightspeed.dllstx.sbcglobal.net [99.152.145.110] claimed to be Orochi.local
Subject: Re: Interim step on meetings site feedback for sites currently under active consideration
To: Ted Lemon <mellon@fugue.com>, Phillip Hallam-Baker <phill@hallambaker.com>
References: <20160418161552.9368.65562.idtracker@ietfa.amsl.com> <8fb376e11631f9ddf73f9385ec5472c3.squirrel@www.trepanning.net> <57151C55.30206@gmail.com> <CAMm+LwjW9+Y6E=t7oNjFcviQoXLESS-C-bn+W9rymjaHXUJskQ@mail.gmail.com> <CAPt1N1=KeDCOg4XpGxaCuP5EDmgFARgYxBhvg3E386=dBFkbxQ@mail.gmail.com>
From: Adam Roach <adam@nostrum.com>
Message-ID: <571909D7.5050300@nostrum.com>
Date: Thu, 21 Apr 2016 12:11:51 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:38.0) Gecko/20100101 Thunderbird/38.7.2
MIME-Version: 1.0
In-Reply-To: <CAPt1N1=KeDCOg4XpGxaCuP5EDmgFARgYxBhvg3E386=dBFkbxQ@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------050807030607020601030709"
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/clwwq-PAf3p-7DU8GjDmzHUpAPI>
Cc: IETF Discussion Mailing List <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, 21 Apr 2016 17:12:04 -0000

This is a multi-part message in MIME format.
--------------050807030607020601030709
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit

On 4/21/16 09:54, Ted Lemon wrote:
> On Thu, Apr 21, 2016 at 10:50 AM, Phillip Hallam-Baker 
> <phill@hallambaker.com <mailto:phill@hallambaker.com>> wrote:
>
>     I think people are missing the point of the 'world tour'. It is not
>     just what happens inside the IETF that is important, it is the
>     perception of the IETF in other forums. In particular government
>     forums.
>
>
> +1
>
> However, I think what Melinda is saying and what you are saying are 
> not in conflict.   We have a problem in the IETF that in-person 
> attendance counts for too much.   This is a real problem.   We should 
> do something about it.

I agree with you to this point. I've seen the importance of the 
in-person meetings gradually increase over the past 18 years, and I 
think it would be great if we could reverse the trend. That's going to 
require a cultural shift, and those are notoriously difficult to effect. 
So if you want this to change, focus on changing the participant 
culture. It's going to be long, and it's going to be hard.

> Then the question of whether to do world tours becomes more of a 
> logistical/financial issue, which is really what it should be.

Sure. For any single, established bit of work, this is largely true 
(given sufficiently rich tools to interact and sufficient will to make 
concessions to time zones), and we can work to make this more true than 
it is today.

What the in-person meetings provide is cross-pollination, in the form of 
hallway conversations and attendees sitting in on working groups that 
operate on the periphery of their area of interest. It allows people to 
identify similarities and trends that would be difficult or impossible 
to spot with simple mailing list participation. I'm not claiming that 
people who participate remotely are necessarily less effective. However, 
the IETF needs a critical mass of these pollinators to spread ideas around.

It's also pretty evident that these cross-pollinators are going to get 
value from the experience of conversing with people on the edges of 
their area of work, both in the form of intel and in the form of 
bringing their own interests and needs into the synthesis of the ideas 
they're coming across. This lets them propose new areas of work that 
benefit groups they care about.

My earlier point was mostly that the trip to BA provided an entirely new 
set of people -- people with as much of a stake in the Internet as 
anyone else -- the opportunity to be these pollinators, both providing 
and generating the benefits I describe above. And that's something we 
should care about. Even if the basic tenets of fairness don't compel 
some people, at least the selfish interest of bringing fresh ideas -- 
and fresh syntheses of ideas -- into the IETF should have clear value.

There's also clear growing interest on behalf of South Americans to get 
involved: it is the only continent that has shown a steady 
meeting-over-meeting increase in attendance over the past seven meetings 
(as measured by percentage of attendees) [1].

Perhaps the right metric is not whether these same people attend 
subsequent meetings in destinations that are remote from their home 
territory, but whether they continue their involvement by participating 
remotely and (to a lesser degree) whether they return to the next 
face-to-face meeting held on their home continent.

Based on the foregoing, I assert that putting effort into observing the 
impact of this kind of excursion from our normal travel pattern has 
value, and that it should inform future venue selection discussions.

/a

____
[1] See 
https://www.dropbox.com/s/fosw7dcwih0dqvz/attendance-by-continent.png?dl=0

--------------050807030607020601030709
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta content="text/html; charset=utf-8" http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">On 4/21/16 09:54, Ted Lemon wrote:<br>
    </div>
    <blockquote
cite="mid:CAPt1N1=KeDCOg4XpGxaCuP5EDmgFARgYxBhvg3E386=dBFkbxQ@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div class="gmail_extra">
          <div class="gmail_quote">On Thu, Apr 21, 2016 at 10:50 AM,
            Phillip Hallam-Baker <span dir="ltr">&lt;<a
                moz-do-not-send="true"
                href="mailto:phill@hallambaker.com" target="_blank"><a class="moz-txt-link-abbreviated" href="mailto:phill@hallambaker.com">phill@hallambaker.com</a></a>&gt;</span>
            wrote:<br>
            <blockquote class="gmail_quote" style="margin:0 0 0
              .8ex;border-left:1px #ccc solid;padding-left:1ex">I think
              people are missing the point of the 'world tour'. It is
              not<br>
              just what happens inside the IETF that is important, it is
              the<br>
              perception of the IETF in other forums. In particular
              government<br>
              forums.<br>
            </blockquote>
            <div><br>
            </div>
            <div>+1</div>
            <div><br>
            </div>
            <div>However, I think what Melinda is saying and what you
              are saying are not in conflict. Â  We have a problem in the
              IETF that in-person attendance counts for too much. Â  This
              is a real problem. Â  We should do something about it.</div>
          </div>
        </div>
      </div>
    </blockquote>
    <br>
    I agree with you to this point. I've seen the importance of the
    in-person meetings gradually increase over the past 18 years, and I
    think it would be great if we could reverse the trend. That's going
    to require a cultural shift, and those are notoriously difficult to
    effect. So if you want this to change, focus on changing the
    participant culture. It's going to be long, and it's going to be
    hard.<br>
    <br>
    <blockquote
cite="mid:CAPt1N1=KeDCOg4XpGxaCuP5EDmgFARgYxBhvg3E386=dBFkbxQ@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div class="gmail_extra">
          <div class="gmail_quote">
            <div>Then the question of whether to do world tours becomes
              more of a logistical/financial issue, which is really what
              it should be.<br>
            </div>
          </div>
        </div>
      </div>
    </blockquote>
    <br>
    Sure. For any single, established bit of work, this is largely true
    (given sufficiently rich tools to interact and sufficient will to
    make concessions to time zones), and we can work to make this more
    true than it is today.<br>
    <br>
    What the in-person meetings provide is cross-pollination, in the
    form of hallway conversations and attendees sitting in on working
    groups that operate on the periphery of their area of interest. It
    allows people to identify similarities and trends that would be
    difficult or impossible to spot with simple mailing list
    participation. I'm not claiming that people who participate remotely
    are necessarily less effective. However, the IETF needs a critical
    mass of these pollinators to spread ideas around.<br>
    <br>
    It's also pretty evident that these cross-pollinators are going to
    get value from the experience of conversing with people on the edges
    of their area of work, both in the form of intel and in the form of
    bringing their own interests and needs into the synthesis of the
    ideas they're coming across. This lets them propose new areas of
    work that benefit groups they care about. <br>
    <br>
    My earlier point was mostly that the trip to BA provided an entirely
    new set of people -- people with as much of a stake in the Internet
    as anyone else -- the opportunity to be these pollinators, both
    providing and generating the benefits I describe above. And that's
    something we should care about. Even if the basic tenets of fairness
    don't compel some people, at least the selfish interest of bringing
    fresh ideas -- and fresh syntheses of ideas -- into the IETF should
    have clear value.<br>
    <br>
    There's also clear growing interest on behalf of South Americans to
    get involved: it is the only continent that has shown a steady
    meeting-over-meeting increase in attendance over the past seven
    meetings (as measured by percentage of attendees) [1].<br>
    <br>
    Perhaps the right metric is not whether these same people attend
    subsequent meetings in destinations that are remote from their home
    territory, but whether they continue their involvement by
    participating remotely and (to a lesser degree) whether they return
    to the next face-to-face meeting held on their home continent.<br>
    <br>
    Based on the foregoing, I assert that putting effort into observing
    the impact of this kind of excursion from our normal travel pattern
    has value, and that it should inform future venue selection
    discussions.<br>
    <br>
    /a<br>
    <br>
    ____<br>
    [1] See
<a class="moz-txt-link-freetext" href="https://www.dropbox.com/s/fosw7dcwih0dqvz/attendance-by-continent.png?dl=0">https://www.dropbox.com/s/fosw7dcwih0dqvz/attendance-by-continent.png?dl=0</a><br>
  </body>
</html>

--------------050807030607020601030709--


From nobody Thu Apr 21 10:31:42 2016
Return-Path: <spencerdawkins.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 90C6612E079 for <ietf@ietfa.amsl.com>; Thu, 21 Apr 2016 10:31:40 -0700 (PDT)
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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 HF13ZslAsvzf for <ietf@ietfa.amsl.com>; Thu, 21 Apr 2016 10:31:38 -0700 (PDT)
Received: from mail-yw0-x22b.google.com (mail-yw0-x22b.google.com [IPv6:2607:f8b0:4002:c05::22b]) (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 AB4F212DD13 for <ietf@ietf.org>; Thu, 21 Apr 2016 10:31:38 -0700 (PDT)
Received: by mail-yw0-x22b.google.com with SMTP id t10so96981665ywa.0 for <ietf@ietf.org>; Thu, 21 Apr 2016 10:31:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=eblaV7g9iQ+3wTSzYkHO8iVm8+QwoQxZN4DJ6AlVM0Y=; b=idAncoYZ/ivoznuKodaCVw8i0ChPC94Q6XiIx15P9Ksb2fe6paIn42z1BfDg/EaGPb xq3PtBSl75L7gVvCmw0uu7yk82/FPX6XuNSdSvr1XrkJnDvBSRGJJfUDZumYwcvFQHuF CYKd+Z9mL9kFMnPgKwteesVGNwfjDyHYXJt578R7Cdv1bjh+U8/T9QXuxT9bjgi11Pc7 /xwtvxpxKqtGdtv7Q/y4jx/ySV69vc5LJ6wROIuAoekK8RtFuFv+5XlGGes0dt48wIzs P5fd7gxiQ1wl8TlmQasWg0RwR/ZcLoXrCJoar+g6gKVEtnOD4PSZt/z3VQ6CekjCiuuF LvVQ==
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:date :message-id:subject:from:to:cc; bh=eblaV7g9iQ+3wTSzYkHO8iVm8+QwoQxZN4DJ6AlVM0Y=; b=RzpRVmX4k3fREwZO3+43b7mblNZgiJw3UgkJKUm+OVLnA8YCx5xWzJAvn00pkBwMCP cQ7jNOc2birH++qbLBJKmifoNH8PCBUmFVXUjhtDX1XqgviP6O3ilGHfHWPbZ8W0fZ1u o4d8EQhBzMB0EsEF0HDd4mOClJdFcAmh4tRdbnygS4jEwQxTf6Wu9v0JFk6DvoHb26EB RB+cwHjYj0UK0fdZ/ZhHPfSMlEEJUdRbsvEhNoTk4ej5SGoet32/WuIoOH17qDU67H1H w52WMW8cJuweIE5sqcHVx7HM8qH3JoBIqXf7evSyZ2UeDozAKykqvsWMwjBgTMHyeF/x Y+gA==
X-Gm-Message-State: AOPr4FX0IZxUHmClCmbRzQp4WmrbsU+fBFhXdQMtwyQ20KaBB2dRs4WJqtUIv5VLCMeG9cBUQkLQfJS8Hb4Ohg==
MIME-Version: 1.0
X-Received: by 10.129.152.8 with SMTP id p8mr9947344ywg.157.1461259897885; Thu, 21 Apr 2016 10:31:37 -0700 (PDT)
Received: by 10.37.224.212 with HTTP; Thu, 21 Apr 2016 10:31:37 -0700 (PDT)
In-Reply-To: <425793799.4005281.1461256833680.JavaMail.yahoo@mail.yahoo.com>
References: <57183686.8000307@gmail.com> <425793799.4005281.1461256833680.JavaMail.yahoo@mail.yahoo.com>
Date: Thu, 21 Apr 2016 12:31:37 -0500
Message-ID: <CAKKJt-cOFT-97UFF4ESES7VXk9WxB-8q5vZKGSqsG0VBPwsysA@mail.gmail.com>
Subject: Re: Interim step on meetings site feedback for sites currently under active consideration
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
To: Nalini Elkins <nalini.elkins@insidethestack.com>
Content-Type: multipart/alternative; boundary=94eb2c0bc490235b28053102154a
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/0lD_wJM54FyaRl1Hy57PmIbTddo>
Cc: ietf <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, 21 Apr 2016 17:31:40 -0000

--94eb2c0bc490235b28053102154a
Content-Type: text/plain; charset=UTF-8

Hi, Nalini,

On Thu, Apr 21, 2016 at 11:40 AM, <nalini.elkins@insidethestack.com> wrote:

>
> But, IMHO, I think a fruitful discussion might be: where do we see all
> this going?  That is, what do we think the IETF will look like in 3 years,
> 5 years, 10 years?  The reason I say this is because I believe that informs
> our thinking.   Any business plans for (at least) 3 - 5 years down the
> road, why don't we at the IETF talk about it?
>

I don't know who noticed, or did not notice,
https://datatracker.ietf.org/doc/draft-arkko-ietf-trends-and-observations/
(people who didn't notice it were probably preparing for IETF 95, which is
a reasonable alibi).

That draft is input to - not output from - people at the IETF talking about
this, and it steers comments and feedback to the IETF mailing list, so I'd
encourage people to comment and provide feedback.

Further, Jari has discussion of the feedback we've seen thus far on the
agenda for the IESG retreat next month, and Stephen and I have the
semi-related "all decisions are/are not on mailing lists" and "people do/do
not need to attend IETF face-to-face meetings to participate effectively"
threads also on the agenda.

I don't know/don't remember what gets published after IESG retreats (when I
was IESG scribe, Russ as IETF chair published summary minutes, but that was
years ago), but anyone could ask for an update before, or during, the IETF
96 plenary open mike session ... including remote participants, of course
:-) ...

More broadly, I don't know what's on the IAB and IAOC retreat agendas (all
of these are still being put together now), but they may also be discussing
relevant aspects of a "business plan".

Thanks,

Spencer, as 1/15th of the IESG, but only 1/15th

>

--94eb2c0bc490235b28053102154a
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi, Nalini,<div class=3D"gmail_extra"><br><div class=3D"gm=
ail_quote">On Thu, Apr 21, 2016 at 11:40 AM,  <span dir=3D"ltr">&lt;<a href=
=3D"mailto:nalini.elkins@insidethestack.com" target=3D"_blank">nalini.elkin=
s@insidethestack.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_qu=
ote" style=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-co=
lor:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div style=
=3D"color:rgb(0,0,0);font-family:HelveticaNeue-Light,&#39;Helvetica Neue Li=
ght&#39;,&#39;Helvetica Neue&#39;,Helvetica,Arial,&#39;Lucida Grande&#39;,s=
ans-serif;font-size:16px;background-color:rgb(255,255,255)"><div>=C2=A0</di=
v><div><span style=3D"font-family:HelveticaNeue,&#39;Helvetica Neue&#39;,He=
lvetica,Arial,&#39;Lucida Grande&#39;,sans-serif">But, IMHO, I think a frui=
tful discussion might be: where do we see all this going?=C2=A0 That is, wh=
at do we think the IETF will look like in 3 years, 5 years, 10 years?=C2=A0=
 The reason I say this is because I believe that informs our thinking. =C2=
=A0 Any business plans for (at least) 3 - 5 years down the road, why don&#3=
9;t we at the IETF talk about it?</span><br></div></div></blockquote><div><=
br></div><div>I don&#39;t know who noticed, or did not notice,=C2=A0<a href=
=3D"https://datatracker.ietf.org/doc/draft-arkko-ietf-trends-and-observatio=
ns/" target=3D"_blank">https://datatracker.ietf.org/doc/draft-arkko-ietf-tr=
ends-and-observations/</a> (people who didn&#39;t notice it were probably p=
reparing for IETF 95, which is a reasonable alibi).</div><div><br></div><di=
v>That draft is input to - not output from - people at the IETF talking abo=
ut this, and it steers comments and feedback to the IETF mailing list, so I=
&#39;d encourage people to comment and provide feedback.</div><div><br></di=
v><div>Further, Jari has discussion of the feedback we&#39;ve seen thus far=
 on the agenda for the IESG retreat next month, and Stephen and I have the =
semi-related &quot;all decisions are/are not on mailing lists&quot; and &qu=
ot;people do/do not need to attend IETF face-to-face meetings to participat=
e effectively&quot; threads also on the agenda.</div><div><br></div><div>I =
don&#39;t know/don&#39;t remember what gets published after IESG retreats (=
when I was IESG scribe, Russ as IETF chair published summary minutes, but t=
hat was years ago), but anyone could ask for an update before, or during, t=
he IETF 96 plenary open mike session ... including remote participants, of =
course :-) ...</div><div><br></div><div>More broadly, I don&#39;t know what=
&#39;s on the IAB and IAOC retreat agendas (all of these are still being pu=
t together now), but they may also be discussing relevant aspects of a &quo=
t;business plan&quot;.</div><div><br></div><div>Thanks,</div><div><br></div=
><div>Spencer, as 1/15th of the IESG, but only 1/15th</div><blockquote clas=
s=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;b=
order-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"=
><div><div style=3D"color:rgb(0,0,0);font-family:HelveticaNeue-Light,&#39;H=
elvetica Neue Light&#39;,&#39;Helvetica Neue&#39;,Helvetica,Arial,&#39;Luci=
da Grande&#39;,sans-serif;font-size:16px;background-color:rgb(255,255,255)"=
><div style=3D"display:block"><div style=3D"font-family:HelveticaNeue-Light=
,&#39;Helvetica Neue Light&#39;,&#39;Helvetica Neue&#39;,Helvetica,Arial,&#=
39;Lucida Grande&#39;,sans-serif;font-size:16px"><div style=3D"font-family:=
HelveticaNeue,&#39;Helvetica Neue&#39;,Helvetica,Arial,&#39;Lucida Grande&#=
39;,sans-serif;font-size:16px"><span><font color=3D"#888888"> </font></span=
></div> </div>  </div></div></div></blockquote></div><br></div></div>

--94eb2c0bc490235b28053102154a--


From nobody Thu Apr 21 12:13:30 2016
Return-Path: <ynir.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 C5FA012DF66 for <ietf@ietfa.amsl.com>; Thu, 21 Apr 2016 12:13:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 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, RCVD_IN_DNSWL_LOW=-0.7, 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 xCdFb5SOg4L6 for <ietf@ietfa.amsl.com>; Thu, 21 Apr 2016 12:13:26 -0700 (PDT)
Received: from mail-wm0-x235.google.com (mail-wm0-x235.google.com [IPv6:2a00:1450:400c:c09::235]) (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 D30B912DF1D for <ietf@ietf.org>; Thu, 21 Apr 2016 12:13:25 -0700 (PDT)
Received: by mail-wm0-x235.google.com with SMTP id n3so148444689wmn.0 for <ietf@ietf.org>; Thu, 21 Apr 2016 12:13:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=q9xdu/RJc2s97OxObB2GzdSjnewNbvChTZgtSM7aSpE=; b=LMnM/HAh1WZSmulTr/CnLTzpbuWX1yzAVr4nTa1YKZr8qhvuO0gp/80l3P2ctITfFM 2bTtIQ4OZwsHRYiUs+G8WP4EMcUrv/7Ec0wFvyQXcJK3eIx22Elm9IkZPkl0bPCj6AZv AIbPHOL2zKCrkPD+wVg4nQMeXs/fnl5TzydGyrI6U7HIDGhJR3pZEYs2DL5kIlj5dd+E DuPOyo0/yzs6d4aBW2xrcaIKSR9IB2BkvGFZUeJ+fSIF4WwOeNuLInaFoETKhJpLPeq0 OrEpbWxybKdYAC0V2Pd36xGniZrGS1bWGrVpxzkuY1XyerwcUxNLr3x1/Mcpse3OkQ6x hDUg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=q9xdu/RJc2s97OxObB2GzdSjnewNbvChTZgtSM7aSpE=; b=TnWxLXlzbDOIeEOaenh1O2GW1giMRsSoMFGhYNkUrDSDGDfE31C1JxolleVXgPTp/O qpHFrc2yDRRqKPzeEApAeRrZHrFPNYLqGGeOmw1Wb8an4BfTcU2yskORtshl1ijJt2L7 lfHcjur52A4p774bCOYYI+wvz1G2zqpx1ivAjSYmTlde26fVZZS29U1hpjNqJ8ZxmC1n I5LEVnMLy2p+yNwzuHczcKtqFuNGrsF+7UK4wdN9d0mpCsEI+YZN4QrkNMHoOeldjNPm 4XTv5A0BPGyiSTrLN5KCAn3UCZKNAfiBVoH1+qVvzBndj9ckzAWlcWtpfOw6NCt2D5At vZEw==
X-Gm-Message-State: AOPr4FUoyXP+zSXa+dCbYR5zmTAmak+KG9wqv5+S7uY2HA/h8N3SDHvEUVR23b8LwQldow==
X-Received: by 10.194.89.38 with SMTP id bl6mr15710424wjb.44.1461266004297; Thu, 21 Apr 2016 12:13:24 -0700 (PDT)
Received: from yoavs-mbp-2.lan (85-10-244-169.clients.your-server.de. [85.10.244.169]) by smtp.gmail.com with ESMTPSA id a16sm16314620wme.22.2016.04.21.12.13.22 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 21 Apr 2016 12:13:23 -0700 (PDT)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Subject: Re: Interim step on meetings site feedback for sites currently under active consideration
From: Yoav Nir <ynir.ietf@gmail.com>
In-Reply-To: <CAPt1N1=KeDCOg4XpGxaCuP5EDmgFARgYxBhvg3E386=dBFkbxQ@mail.gmail.com>
Date: Thu, 21 Apr 2016 21:13:08 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <D923AD0E-53E9-4B25-9319-BE698BC903B9@gmail.com>
References: <20160418161552.9368.65562.idtracker@ietfa.amsl.com> <8fb376e11631f9ddf73f9385ec5472c3.squirrel@www.trepanning.net> <57151C55.30206@gmail.com> <CAMm+LwjW9+Y6E=t7oNjFcviQoXLESS-C-bn+W9rymjaHXUJskQ@mail.gmail.com> <CAPt1N1=KeDCOg4XpGxaCuP5EDmgFARgYxBhvg3E386=dBFkbxQ@mail.gmail.com>
To: Ted Lemon <mellon@fugue.com>
X-Mailer: Apple Mail (2.3124)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/Dd42Alk60SYdA39_aQ2usR2h21c>
Cc: Phillip Hallam-Baker <phill@hallambaker.com>, IETF Discussion Mailing List <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, 21 Apr 2016 19:13:28 -0000

On 21 Apr 2016, at 4:54 PM, Ted Lemon <mellon@fugue.com> wrote:

>    And like you, I found this trip much easier than going to Asia, =
although I know our colleagues from Asia found it just the opposite. :)=20=


Not necessarily. Asia=E2=80=99s a big place. Travel to Japan and Taipei =
was for me more difficult than Buenos Aires, and significantly more =
difficult than anywhere in North America.=20

Yoav



From nobody Thu Apr 21 12:42:18 2016
Return-Path: <nalini.elkins@insidethestack.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 DF84A12E5BB for <ietf@ietfa.amsl.com>; Thu, 21 Apr 2016 12:42:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.619
X-Spam-Level: 
X-Spam-Status: No, score=-2.619 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=yahoo.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 G7SIqL_NsV1w for <ietf@ietfa.amsl.com>; Thu, 21 Apr 2016 12:42:15 -0700 (PDT)
Received: from nm15-vm6.bullet.mail.ne1.yahoo.com (nm15-vm6.bullet.mail.ne1.yahoo.com [98.138.91.108]) (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 16B7512E571 for <ietf@ietf.org>; Thu, 21 Apr 2016 12:42:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1461267758; bh=yqoNYxZn+T/qYRlnKIXyR2gYT30zFXuHNWUlcJxof2g=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:From:Subject; b=T/+YyhTdpdXBNDLpFmSwH1J10dHhGAxAIDIfzpiCGKL30zH27CPrZbE5iuloUpGZAQszabvJjXtnoe4r+aZlpVnErBIcbA6CcSKRgT3UIPZT7mCfnZE6GZeGtuoTp6azotw2sNi4ZfNeSeQjlOSv3+jc4BGE3cnepAMH2NDEe1nZdYfoJxzTs33OwyOXXI6h9Ubm493wDwMXZzAK8uHGrpge/jp0hFJHsg8z+rE/JEntjt0tr5HpkskHaR6kEOx8miEmyJ1NOQJ6l8y6Xcu6hN1L1AFHaaUpp2g9w9FPmC980b8yyDY+upRMEUNmbFKW0ARaX19TjyH+XXp9DtY4xA==
Received: from [98.138.100.112] by nm15.bullet.mail.ne1.yahoo.com with NNFMP;  21 Apr 2016 19:42:38 -0000
Received: from [98.138.226.166] by tm103.bullet.mail.ne1.yahoo.com with NNFMP;  21 Apr 2016 19:42:14 -0000
Received: from [127.0.0.1] by omp1067.mail.ne1.yahoo.com with NNFMP; 21 Apr 2016 19:42:14 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 491915.43619.bm@omp1067.mail.ne1.yahoo.com
X-YMail-OSG: n_HRSrgVM1lYPlr1TZQMXpmRkIBF9ntlIBuglPJkNXXLZX.t5_QBAM.FdNYSfbb RGz85fhUGHfw2kQgjoPXNbLv1vg6NUlVbbKxOraGX074kudgodjjlGFh32xMnXCW3YNaAkk5LHNI pHJF7rQvpVVjy7MoN8yjAKIaw0oY2cuvEwKSc58D5FYtbHDBKdxuo6KO2ZbzG2M8TRzMF0KpkFiU gP.FwA8TEf5COKwLpy08tv3ihV_ogaKKIbXehPWwLVWPoZtg7BljNHkfid5jnWYBnnPLdB.X8HFh LLscv1.TysYaOzFe9zZTQOqXrxftNooUlpRg7Pfb0smITo5Z0Y6B3OAktcv31Ehr22NbBm.cH7HA FstkMyqej2QfrCiKdh2UjO774zimEhdDFg2yNBHoy1yxbUG4TUsZ1gsocmYPRh8MjbE..ds1cTcz OHmqzKb8_qWBaT6zKeI6EueyX4DFAA2iCooAg.shpEu3Z8IajFZp0HCYaiMmB5bvl2zCGS2FBykh u2NMbX46WquIYt7izrg.31QS.tJMfhUudcoH22Uyov4srtYNaqH.BtiaAhpf.PqpnAzJNXrqUBUB o85X_tpN7rMLYtrkPduR81A--
Received: by 98.138.105.254; Thu, 21 Apr 2016 19:42:14 +0000 
Date: Thu, 21 Apr 2016 19:41:59 +0000 (UTC)
From: <nalini.elkins@insidethestack.com>
To: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Message-ID: <2022071530.3940564.1461267719714.JavaMail.yahoo@mail.yahoo.com>
In-Reply-To: <CAKKJt-cOFT-97UFF4ESES7VXk9WxB-8q5vZKGSqsG0VBPwsysA@mail.gmail.com>
References: <CAKKJt-cOFT-97UFF4ESES7VXk9WxB-8q5vZKGSqsG0VBPwsysA@mail.gmail.com>
Subject: Re: Interim step on meetings site feedback for sites currently under active consideration
MIME-Version: 1.0
Content-Type: multipart/alternative;  boundary="----=_Part_3940563_785281348.1461267719709"
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/NvJZX0r9o4MBKcP6eHeRBowwxow>
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: nalini.elkins@insidethestack.com
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, 21 Apr 2016 19:42:17 -0000

------=_Part_3940563_785281348.1461267719709
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

=C2=A0Thanks, Spencer


On Thu, Apr 21, 2016 at 11:40 AM, <nalini.elkins@insidethestack.com> wrote:

=C2=A0But, IMHO, I think a fruitful discussion might be: where do we see al=
l this going?=C2=A0 That is, what do we think the IETF will look like in 3 =
years, 5 years, 10 years?=C2=A0 The reason I say this is because I believe =
that informs our thinking. =C2=A0 Any business plans for (at least) 3 - 5 y=
ears down the road, why don't we at the IETF talk about it?


>I don't know who noticed, or did not notice,=C2=A0https://datatracker.ietf=
.org/doc/draft-arkko-ietf-trends-and-observations/ (people who didn't notic=
e it were probably preparing for IETF 95, which is >a reasonable alibi).
>That draft is input to - not output from - people at the IETF talking abou=
t this, and it steers comments and feedback to the IETF mailing list, so I'=
d encourage people to comment and provide >feedback.

I took a quick look at that draft but then had a ton of other work to do. =
=C2=A0 I will re-read over the weekend and comment.
Thanks for pointing that out.
Nalini
=C2=A0  
------=_Part_3940563_785281348.1461267719709
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<html><head></head><body><div style=3D"color:#000; background-color:#fff; f=
ont-family:HelveticaNeue-Light, Helvetica Neue Light, Helvetica Neue, Helve=
tica, Arial, Lucida Grande, sans-serif;font-size:16px"><div id=3D"yui_3_16_=
0_ym19_1_1461267446848_9672">&nbsp;Thanks, Spencer</div><div class=3D"qtdSe=
parateBR"><br><br></div><div class=3D"yahoo_quoted" id=3D"yui_3_16_0_ym19_1=
_1461267446848_9701" style=3D"display: block;"><div style=3D"font-family: H=
elveticaNeue-Light, Helvetica Neue Light, Helvetica Neue, Helvetica, Arial,=
 Lucida Grande, sans-serif; font-size: 16px;" id=3D"yui_3_16_0_ym19_1_14612=
67446848_9700"><div style=3D"font-family: HelveticaNeue, Helvetica Neue, He=
lvetica, Arial, Lucida Grande, sans-serif; font-size: 16px;" id=3D"yui_3_16=
_0_ym19_1_1461267446848_9699"><div class=3D"y_msg_container" id=3D"yui_3_16=
_0_ym19_1_1461267446848_9722"><div id=3D"yiv8109647910"><div id=3D"yui_3_16=
_0_ym19_1_1461267446848_9740"><div dir=3D"ltr" id=3D"yui_3_16_0_ym19_1_1461=
267446848_9739"><div class=3D"yiv8109647910gmail_extra" id=3D"yui_3_16_0_ym=
19_1_1461267446848_9742"><br clear=3D"none"><div class=3D"yiv8109647910yqt5=
464656972" id=3D"yiv8109647910yqtfd52689"><div class=3D"yiv8109647910gmail_=
quote" id=3D"yui_3_16_0_ym19_1_1461267446848_9744">On Thu, Apr 21, 2016 at =
11:40 AM,  <span dir=3D"ltr">&lt;<a rel=3D"nofollow" shape=3D"rect" ymailto=
=3D"mailto:nalini.elkins@insidethestack.com" target=3D"_blank" href=3D"mail=
to:nalini.elkins@insidethestack.com">nalini.elkins@insidethestack.com</a>&g=
t;</span> wrote:<br clear=3D"none"><blockquote class=3D"yiv8109647910gmail_=
quote" style=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-=
color:rgb(204,204,204);border-left-style:solid;padding-left:1ex;" id=3D"yui=
_3_16_0_ym19_1_1461267446848_9809"><div style=3D"color:rgb(0,0,0);font-fami=
ly:HelveticaNeue-Light, 'Helvetica Neue Light', 'Helvetica Neue', Helvetica=
, Arial, 'Lucida Grande', sans-serif;font-size:16px;background-color:rgb(25=
5,255,255);" id=3D"yui_3_16_0_ym19_1_1461267446848_9808"><div>&nbsp;</div><=
div id=3D"yui_3_16_0_ym19_1_1461267446848_9807"><span style=3D"font-family:=
HelveticaNeue, 'Helvetica Neue', Helvetica, Arial, 'Lucida Grande', sans-se=
rif;" id=3D"yui_3_16_0_ym19_1_1461267446848_9864">But, IMHO, I think a frui=
tful discussion might be: where do we see all this going?&nbsp; That is, wh=
at do we think the IETF will look like in 3 years, 5 years, 10 years?&nbsp;=
 The reason I say this is because I believe that informs our thinking. &nbs=
p; Any business plans for (at least) 3 - 5 years down the road, why don't w=
e at the IETF talk about it?</span><br clear=3D"none"></div></div></blockqu=
ote><div id=3D"yui_3_16_0_ym19_1_1461267446848_9862"><br clear=3D"none"></d=
iv><div id=3D"yui_3_16_0_ym19_1_1461267446848_9860">&gt;I don't know who no=
ticed, or did not notice,&nbsp;<a rel=3D"nofollow" shape=3D"rect" target=3D=
"_blank" href=3D"https://datatracker.ietf.org/doc/draft-arkko-ietf-trends-a=
nd-observations/">https://datatracker.ietf.org/doc/draft-arkko-ietf-trends-=
and-observations/</a> (people who didn't notice it were probably preparing =
for IETF 95, which is &gt;a reasonable alibi).</div><div id=3D"yui_3_16_0_y=
m19_1_1461267446848_9858"><br clear=3D"none"></div><div id=3D"yui_3_16_0_ym=
19_1_1461267446848_9856">&gt;That draft is input to - not output from - peo=
ple at the IETF talking about this, and it steers comments and feedback to =
the IETF mailing list, so I'd encourage people to comment and provide &gt;f=
eedback.</div><div id=3D"yui_3_16_0_ym19_1_1461267446848_9856"><br></div><d=
iv id=3D"yui_3_16_0_ym19_1_1461267446848_9856"><br></div><div id=3D"yui_3_1=
6_0_ym19_1_1461267446848_9856" dir=3D"ltr">I took a quick look at that draf=
t but then had a ton of other work to do. &nbsp; I will re-read over the we=
ekend and comment.</div><div id=3D"yui_3_16_0_ym19_1_1461267446848_9856" di=
r=3D"ltr"><br></div><div id=3D"yui_3_16_0_ym19_1_1461267446848_9856" dir=3D=
"ltr">Thanks for pointing that out.</div><div id=3D"yui_3_16_0_ym19_1_14612=
67446848_9856" dir=3D"ltr"><br></div><div id=3D"yui_3_16_0_ym19_1_146126744=
6848_9856" dir=3D"ltr">Nalini</div><div id=3D"yui_3_16_0_ym19_1_14612674468=
48_9846"><br clear=3D"none"></div><div id=3D"yui_3_16_0_ym19_1_146126744684=
8_9805">&nbsp;</div></div></div></div></div></div></div></div> </div> </div=
>  </div></div></body></html>
------=_Part_3940563_785281348.1461267719709--


From nobody Thu Apr 21 15:08:58 2016
Return-Path: <hallam@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 47F2512DC70 for <ietf@ietfa.amsl.com>; Thu, 21 Apr 2016 15:08:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.4
X-Spam-Level: 
X-Spam-Status: No, score=-2.4 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.199, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 nezhnRQx2gOk for <ietf@ietfa.amsl.com>; Thu, 21 Apr 2016 15:08:56 -0700 (PDT)
Received: from mail-lb0-x236.google.com (mail-lb0-x236.google.com [IPv6:2a00:1450:4010:c04::236]) (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 D5F6D12D0F5 for <ietf@ietf.org>; Thu, 21 Apr 2016 15:08:55 -0700 (PDT)
Received: by mail-lb0-x236.google.com with SMTP id b1so30403882lbi.1 for <ietf@ietf.org>; Thu, 21 Apr 2016 15:08:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-transfer-encoding; bh=n76iaJQhH8e8EQpNmVPRvthByu6t3Mk7J1P0iVgSzSE=; b=EVFqbfXkHMXIIMAv/W5Pzlizc7evMN/sZN2lDMOYJZ+AxLOyYXfkK+DnKCsXqWd4K5 2PmdcTPnP/pmy7g5EuxiwAA33AcnG/pCizjI8Zqm9amJ/ftCDKOLPLs/ySWxddYwRCia G0dDBmZauZ1Owi6cUoctTof0mvOPP1CoU9Q2S/wE8JCEhF2Th7yVNrV22/LCttHJdrBd pchQHtvNbpur2WWTPPR6hcAeNr1QrFaZPOr7MPkJSFynsRqiSCCxrjgmJK2klvFUHDkU ypXGR7rjJIDOq5QpTdghLZtatx55LSIljUGWqJGJFock9ZyOcfWDnyO3BoGisEfBXSe+ NGkg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:date :message-id:subject:from:to:cc:content-transfer-encoding; bh=n76iaJQhH8e8EQpNmVPRvthByu6t3Mk7J1P0iVgSzSE=; b=SV5h7DtZe4WO6LVcwqme3VV41NIF30HcyhxR6PCPCdEaeY1C21mbR/2r7nOV8Ftbmw vCS7N9pyRkYfStiXvsebsQTAS1UubgAwgOSPxtbkhGrRwFhnvB3TgWB0eoGTFw2NMVmR rt75kRke6lwC4iziLGTGfD6llBIJKk2JpnFumbosYJfCQGuELjrNYmGhm8wIfW3rUqn+ OoYQqXJqAMHuwvLjSqSe6Hci8TbRcsSJuJDIEW8F3qzgHIlEZ+NbfV3Sn2hSy5DJa0nY A8EFHxRSRRHum75cu1WItrqGu9hVOV2+2RUgVy13u+Q/3j4K5rXhPC832QbpRQvmq0FW /X3Q==
X-Gm-Message-State: AOPr4FUjc5GKVRaqAv1YJJ2svqS0OsL0SNVe39D2qMlCJSxbdyvcvtrIqQNPm5802GkjUFWq96dkYYDSRL886Q==
MIME-Version: 1.0
X-Received: by 10.112.95.20 with SMTP id dg20mr7277306lbb.58.1461276534017; Thu, 21 Apr 2016 15:08:54 -0700 (PDT)
Sender: hallam@gmail.com
Received: by 10.112.3.102 with HTTP; Thu, 21 Apr 2016 15:08:53 -0700 (PDT)
In-Reply-To: <D923AD0E-53E9-4B25-9319-BE698BC903B9@gmail.com>
References: <20160418161552.9368.65562.idtracker@ietfa.amsl.com> <8fb376e11631f9ddf73f9385ec5472c3.squirrel@www.trepanning.net> <57151C55.30206@gmail.com> <CAMm+LwjW9+Y6E=t7oNjFcviQoXLESS-C-bn+W9rymjaHXUJskQ@mail.gmail.com> <CAPt1N1=KeDCOg4XpGxaCuP5EDmgFARgYxBhvg3E386=dBFkbxQ@mail.gmail.com> <D923AD0E-53E9-4B25-9319-BE698BC903B9@gmail.com>
Date: Thu, 21 Apr 2016 18:08:53 -0400
X-Google-Sender-Auth: SQeaKff1OlbEFHQsTKxc9-CW1uE
Message-ID: <CAMm+LwjvZwC9Uhf460_xV9y5uWZ=cp75CDATOQ4RU-n-0FyS-g@mail.gmail.com>
Subject: Re: Interim step on meetings site feedback for sites currently under active consideration
From: Phillip Hallam-Baker <phill@hallambaker.com>
To: Yoav Nir <ynir.ietf@gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/ydu8SmuvEuq5SHoBBMR9SJSqDRo>
Cc: IETF Discussion Mailing List <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, 21 Apr 2016 22:08:57 -0000

On Thu, Apr 21, 2016 at 3:13 PM, Yoav Nir <ynir.ietf@gmail.com> wrote:
>
> On 21 Apr 2016, at 4:54 PM, Ted Lemon <mellon@fugue.com> wrote:
>
>>    And like you, I found this trip much easier than going to Asia, altho=
ugh I know our colleagues from Asia found it just the opposite. :)
>
> Not necessarily. Asia=E2=80=99s a big place. Travel to Japan and Taipei w=
as for me more difficult than Buenos Aires, and significantly more difficul=
t than anywhere in North America.
>
> Yoav

In which we discover the importance of 'great circle routes'.

And the fact that 'Asia' crosses almost 180 degrees of longitude
making it not very useful as a geographical locale.


From nobody Thu Apr 21 16:11:47 2016
Return-Path: <finlayson@live555.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 2157D12DCAD for <ietf@ietfa.amsl.com>; Thu, 21 Apr 2016 16:11:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level: 
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.996, TVD_FROM_1=0.999] 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 txo5j8UhT2Uk for <ietf@ietfa.amsl.com>; Thu, 21 Apr 2016 16:11:43 -0700 (PDT)
Received: from ns.live555.com (ns.live555.com [4.79.217.242]) (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 35FFA12DC37 for <ietf@ietf.org>; Thu, 21 Apr 2016 16:11:43 -0700 (PDT)
Received: from [127.0.0.1] (localhost.live555.com [127.0.0.1]) by ns.live555.com (8.15.2/8.14.9) with ESMTP id u3LNBUCQ044391 for <ietf@ietf.org>; Thu, 21 Apr 2016 16:11:32 -0700 (PDT) (envelope-from finlayson@live555.com)
X-Authentication-Warning: ns.live555.com: Host localhost.live555.com [127.0.0.1] claimed to be [127.0.0.1]
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Subject: Re: Interim step on meetings site feedback for sites currently under active consideration
From: Ross Finlayson <finlayson@live555.com>
In-Reply-To: <CAMm+LwjW9+Y6E=t7oNjFcviQoXLESS-C-bn+W9rymjaHXUJskQ@mail.gmail.com>
Date: Thu, 21 Apr 2016 16:11:30 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <3C99A58B-847B-424F-8682-5036C75EB735@live555.com>
References: <20160418161552.9368.65562.idtracker@ietfa.amsl.com> <8fb376e11631f9ddf73f9385ec5472c3.squirrel@www.trepanning.net> <57151C55.30206@gmail.com> <CAMm+LwjW9+Y6E=t7oNjFcviQoXLESS-C-bn+W9rymjaHXUJskQ@mail.gmail.com>
To: IETF Discussion Mailing List <ietf@ietf.org>
X-Mailer: Apple Mail (2.3124)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/0cOkUMvkuaaRO7YPmNcz80fAwOs>
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, 21 Apr 2016 23:11:46 -0000

> On Apr 21, 2016, at 7:50 AM, Phillip Hallam-Baker =
<phill@hallambaker.com> wrote:
>=20
> I think people are missing the point of the 'world tour'. It is not
> just what happens inside the IETF that is important, it is the
> perception of the IETF in other forums. In particular government
> forums.
>=20
> The politics of communication systems sit in the top tier in
> international diplomacy. Only actual military conflict outranks them.
> One thing that every successful politician understands is the impact
> of communication infrastructures on their position.

The point=E2=80=99s well taken - but perhaps you=E2=80=99re conflating =
the role of the IETF with that of the Internet Society (ISOC)?

	Ross.


From nobody Thu Apr 21 16:51:37 2016
Return-Path: <hallam@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 7346812E987 for <ietf@ietfa.amsl.com>; Thu, 21 Apr 2016 16:51:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.4
X-Spam-Level: 
X-Spam-Status: No, score=-2.4 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.199, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 lC-sJS89ao39 for <ietf@ietfa.amsl.com>; Thu, 21 Apr 2016 16:51:34 -0700 (PDT)
Received: from mail-lf0-x234.google.com (mail-lf0-x234.google.com [IPv6:2a00:1450:4010:c07::234]) (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 73C7612E972 for <ietf@ietf.org>; Thu, 21 Apr 2016 16:51:34 -0700 (PDT)
Received: by mail-lf0-x234.google.com with SMTP id e190so70025351lfe.0 for <ietf@ietf.org>; Thu, 21 Apr 2016 16:51:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-transfer-encoding; bh=a3HEnZjA1+quei69+mc4ivgGRBQTlOOWsA4kFB1ej0Y=; b=BBY+Ouk33f8wd/NquRchiDnvsxf4VjwFZ7JJVwURXOYIxCVCtqVY9B7uS2wqi1ylMj dbDFyUJlvGCMQXTpNIvPT5TzdaJV6uYuIUWZzz17fYuP2ke3JjLHBtsMuHLYFft5p5Bh JZftrty7iqtTw2tQWvVFcZtPsgNdlF7fRgYtXy7SByuvlpsVjqXpMPrKa8ZaAgXoVZn9 KHtPCbxybAR2FoSp2EpAqGmjBSxx02tBUvx/OsUilpoYFg82OlFafOVM7yV6pnHmlcwW i70SfIPgdYZyTnsjWtj5fUL8V79eBT5VbEBHO7pdK1HDFERjWlRM+dx1TsS/tRKd3t8Z Avcg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:date :message-id:subject:from:to:cc:content-transfer-encoding; bh=a3HEnZjA1+quei69+mc4ivgGRBQTlOOWsA4kFB1ej0Y=; b=KnDpem/sOuylg8Fg5SoTYUOHJvDU9l51ZSDeY7NreNawNLi82VVxD+cA1439TVdnwu VYHDN7fRhnYj2fw+AyewoXBUaj15o4l+5aR+cla3tXnnqA62i0Ird542cAlMixwIbc3x cfwvV8+L6/8Umu5aZ1nQQRWhT3KORY0I94EuivqLudlH2+yvq5uqTEZdPDND6dUmBjtg EYztbcVoWESXFxf2cc5c55u8CHiR5exAXkJZ6Iml10v/jgV7oyau2putD7ggFEmL3OFj paO8j9OptC84duNyQgJufp1g3OiTm0MsHK2JVa9GI8bxm00ZBjp8as9v7VbKw+5tCfi6 HGgQ==
X-Gm-Message-State: AOPr4FXUJrzIHvDWaSNTCV3K18UqifpP91QUuT/WLEvZtSxIP55hpOiwh45FiD3rWZXeuSXzNWM2Ap9A2Qpgxw==
MIME-Version: 1.0
X-Received: by 10.25.4.202 with SMTP id 193mr7673589lfe.49.1461282692684; Thu, 21 Apr 2016 16:51:32 -0700 (PDT)
Sender: hallam@gmail.com
Received: by 10.112.163.99 with HTTP; Thu, 21 Apr 2016 16:51:32 -0700 (PDT)
In-Reply-To: <3C99A58B-847B-424F-8682-5036C75EB735@live555.com>
References: <20160418161552.9368.65562.idtracker@ietfa.amsl.com> <8fb376e11631f9ddf73f9385ec5472c3.squirrel@www.trepanning.net> <57151C55.30206@gmail.com> <CAMm+LwjW9+Y6E=t7oNjFcviQoXLESS-C-bn+W9rymjaHXUJskQ@mail.gmail.com> <3C99A58B-847B-424F-8682-5036C75EB735@live555.com>
Date: Thu, 21 Apr 2016 19:51:32 -0400
X-Google-Sender-Auth: ZO4iGB3YR93TqAZIJz0ZMxZsN0c
Message-ID: <CAMm+Lwiii4bN0_F2=-NutCjqJdrjNZaThRmJo08q7JXe-i8YhA@mail.gmail.com>
Subject: Re: Interim step on meetings site feedback for sites currently under active consideration
From: Phillip Hallam-Baker <phill@hallambaker.com>
To: Ross Finlayson <finlayson@live555.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/uMJQKlVhrpasAbNX7SFD3ri35ac>
Cc: IETF Discussion Mailing List <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, 21 Apr 2016 23:51:36 -0000

On Thu, Apr 21, 2016 at 7:11 PM, Ross Finlayson <finlayson@live555.com> wro=
te:
>
>> On Apr 21, 2016, at 7:50 AM, Phillip Hallam-Baker <phill@hallambaker.com=
> wrote:
>>
>> I think people are missing the point of the 'world tour'. It is not
>> just what happens inside the IETF that is important, it is the
>> perception of the IETF in other forums. In particular government
>> forums.
>>
>> The politics of communication systems sit in the top tier in
>> international diplomacy. Only actual military conflict outranks them.
>> One thing that every successful politician understands is the impact
>> of communication infrastructures on their position.
>
> The point=E2=80=99s well taken - but perhaps you=E2=80=99re conflating th=
e role of the IETF with that of the Internet Society (ISOC)?

IETF is an organized activity of ISOC. The government types do not see
a difference and it is not something I would spend time attempting to
explain.


From nobody Thu Apr 21 21:53:14 2016
Return-Path: <narten@us.ibm.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 AD9D712E7CD for <ietf@ietfa.amsl.com>; Thu, 21 Apr 2016 21:53:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.217
X-Spam-Level: 
X-Spam-Status: No, score=-5.217 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.996, SPF_PASS=-0.001] 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 Cc2pjzfDACqV for <ietf@ietfa.amsl.com>; Thu, 21 Apr 2016 21:53:08 -0700 (PDT)
Received: from e18.ny.us.ibm.com (e18.ny.us.ibm.com [129.33.205.208]) (using TLSv1.2 with cipher CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ADA5512E7BB for <ietf@ietf.org>; Thu, 21 Apr 2016 21:53:08 -0700 (PDT)
Received: from localhost by e18.ny.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for <ietf@ietf.org> from <narten@us.ibm.com>; Fri, 22 Apr 2016 00:53:07 -0400
Received: from d01dlp02.pok.ibm.com (9.56.250.167) by e18.ny.us.ibm.com (146.89.104.205) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Fri, 22 Apr 2016 00:53:04 -0400
X-IBM-Helo: d01dlp02.pok.ibm.com
X-IBM-MailFrom: narten@us.ibm.com
X-IBM-RcptTo: ietf@ietf.org
Received: from b01cxnp22034.gho.pok.ibm.com (b01cxnp22034.gho.pok.ibm.com [9.57.198.24]) by d01dlp02.pok.ibm.com (Postfix) with ESMTP id 568EB6E8041 for <ietf@ietf.org>; Fri, 22 Apr 2016 00:52:49 -0400 (EDT)
Received: from d01av02.pok.ibm.com (d01av02.pok.ibm.com [9.56.224.216]) by b01cxnp22034.gho.pok.ibm.com (8.14.9/8.14.9/NCO v10.0) with ESMTP id u3M4r4MC36372526 for <ietf@ietf.org>; Fri, 22 Apr 2016 04:53:04 GMT
Received: from d01av02.pok.ibm.com (localhost [127.0.0.1]) by d01av02.pok.ibm.com (8.14.4/8.14.4/NCO v10.0 AVout) with ESMTP id u3M4r31a022623 for <ietf@ietf.org>; Fri, 22 Apr 2016 00:53:04 -0400
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com [9.27.222.27]) by d01av02.pok.ibm.com (8.14.4/8.14.4/NCO v10.0 AVin) with ESMTP id u3M4r3Ig022577 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for <ietf@ietf.org>; Fri, 22 Apr 2016 00:53:03 -0400
Received: from rotala.raleigh.ibm.com (localhost [127.0.0.1]) by rotala.raleigh.ibm.com (8.15.2/8.12.5) with ESMTP id u3M4r2QD004602 for <ietf@ietf.org>; Fri, 22 Apr 2016 00:53:03 -0400
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.15.2/8.15.2/Submit) id u3M4r11N004516 for ietf@ietf.org; Fri, 22 Apr 2016 00:53:01 -0400
From: narten@us.ibm.com
Message-Id: <201604220453.u3M4r11N004516@rotala.raleigh.ibm.com>
Date: Fri, 22 Apr 2016 00:53:01 -0400
To: ietf@ietf.org
Subject: Weekly posting summary for ietf@ietf.org
User-Agent: Heirloom mailx 12.5 7/5/10
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-TM-AS-MML: disable
X-Content-Scanned: Fidelis XPS MAILER
x-cbid: 16042204-0045-0000-0000-000003FAFFBF
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/ic3m539OC7W05Yqvjd9exq_rj-U>
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: Fri, 22 Apr 2016 04:53:11 -0000

Total of 101 messages in the last 7 days.
 
script run at: Fri Apr 22 00:53:01 EDT 2016
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
  4.95% |    5 |  6.81% |    67361 | nalini.elkins@insidethestack.com
  4.95% |    5 |  6.07% |    60101 | mellon@fugue.com
  4.95% |    5 |  4.44% |    43920 | sob@sobco.com
  4.95% |    5 |  4.20% |    41516 | phill@hallambaker.com
  4.95% |    5 |  3.07% |    30385 | ietf@meetecho.com
  1.98% |    2 |  5.50% |    54388 | dimitri.staessens@intec.ugent.be
  3.96% |    4 |  3.19% |    31595 | melinda.shore@gmail.com
  2.97% |    3 |  3.44% |    34010 | jari.arkko@piuha.net
  2.97% |    3 |  2.58% |    25564 | housley@vigilsec.com
  2.97% |    3 |  2.38% |    23599 | jordi.palet@consulintel.es
  1.98% |    2 |  3.04% |    30122 | vinays@cisco.com
  2.97% |    3 |  2.02% |    19947 | johnl@taugh.com
  1.98% |    2 |  2.60% |    25719 | abdussalambaryun@gmail.com
  1.98% |    2 |  2.30% |    22734 | christian.oflaherty@gmail.com
  1.98% |    2 |  2.22% |    21931 | adam@nostrum.com
  1.98% |    2 |  2.07% |    20495 | peter@akayla.com
  1.98% |    2 |  1.62% |    16071 | joe@cdt.org
  1.98% |    2 |  1.54% |    15246 | stewart.bryant@gmail.com
  1.98% |    2 |  1.51% |    14909 | dharkins@lounge.org
  1.98% |    2 |  1.29% |    12725 | john@jlc.net
  1.98% |    2 |  1.25% |    12331 | swmike@swm.pp.se
  0.99% |    1 |  2.12% |    20958 | bensons@queuefull.net
  0.99% |    1 |  1.75% |    17341 | spromano@unina.it
  0.99% |    1 |  1.64% |    16263 | dhruv.ietf@gmail.com
  0.99% |    1 |  1.44% |    14210 | stephen.farrell@cs.tcd.ie
  0.99% |    1 |  1.35% |    13312 | david.black@emc.com
  0.99% |    1 |  1.34% |    13268 | corinnecath@gmail.com
  0.99% |    1 |  1.32% |    13112 | magnus.westerlund@ericsson.com
  0.99% |    1 |  1.27% |    12532 | spencerdawkins.ietf@gmail.com
  0.99% |    1 |  1.22% |    12100 | mary.h.barnes@gmail.com
  0.99% |    1 |  1.18% |    11711 | narten@us.ibm.com
  0.99% |    1 |  1.17% |    11627 | gorry@erg.abdn.ac.uk
  0.99% |    1 |  1.00% |     9913 | fluffy@iii.ca
  0.99% |    1 |  0.98% |     9682 | aallen@blackberry.com
  0.99% |    1 |  0.97% |     9604 | stewe@stewe.org
  0.99% |    1 |  0.93% |     9177 | ldaigle@thinkingcat.com
  0.99% |    1 |  0.87% |     8604 | fred.clark@sit.gob.gt
  0.99% |    1 |  0.87% |     8589 | tnadeau@lucidvision.com
  0.99% |    1 |  0.84% |     8323 | rwfranks@gmail.com
  0.99% |    1 |  0.84% |     8285 | vinayakh@gmail.com
  0.99% |    1 |  0.83% |     8176 | rwfranks@acm.org
  0.99% |    1 |  0.81% |     8019 | dwm@xpasc.com
  0.99% |    1 |  0.80% |     7963 | harald@alvestrand.no
  0.99% |    1 |  0.80% |     7883 | adrian@olddog.co.uk
  0.99% |    1 |  0.79% |     7783 | ynir.ietf@gmail.com
  0.99% |    1 |  0.78% |     7726 | dave@taht.net
  0.99% |    1 |  0.78% |     7707 | tony@att.com
  0.99% |    1 |  0.77% |     7637 | sm+ietf@elandsys.com
  0.99% |    1 |  0.75% |     7387 | lee@asgard.org
  0.99% |    1 |  0.74% |     7313 | carlos@lacnic.net
  0.99% |    1 |  0.71% |     7062 | jared@puck.nether.net
  0.99% |    1 |  0.70% |     6929 | mcr+ietf@sandelman.ca
  0.99% |    1 |  0.68% |     6740 | paul@nohats.ca
  0.99% |    1 |  0.68% |     6734 | paul.hoffman@vpnc.org
  0.99% |    1 |  0.68% |     6680 | iad@ietf.org
  0.99% |    1 |  0.64% |     6370 | iaoc-chair@ietf.org
  0.99% |    1 |  0.64% |     6294 | finlayson@live555.com
  0.99% |    1 |  0.63% |     6276 | ietf@johnlevine.com
  0.99% |    1 |  0.57% |     5669 | llynch@civil-tongue.net
--------+------+--------+----------+------------------------
100.00% |  101 |100.00% |   989628 | Total


From nobody Thu Apr 21 23:46:17 2016
Return-Path: <lloyd.wood@yahoo.co.uk>
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 C3E2D12E8F4 for <ietf@ietfa.amsl.com>; Thu, 21 Apr 2016 23:46:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level: 
X-Spam-Status: No, score=-2.701 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, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-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=yahoo.co.uk
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 fmVvJ8hbyCfX for <ietf@ietfa.amsl.com>; Thu, 21 Apr 2016 23:46:15 -0700 (PDT)
Received: from nm42-vm8.bullet.mail.ne1.yahoo.com (nm42-vm8.bullet.mail.ne1.yahoo.com [98.138.120.214]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 26BB812E8E7 for <ietf@ietf.org>; Thu, 21 Apr 2016 23:46:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.co.uk; s=s2048;  t=1461307574; bh=ySWpvH4MoipMVrGFWc0fhbAczuHKywL7d2euK2jJNhI=;  h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:From:Subject;  b=tWzzAYZmMkgquRkwTqUQFZ+Bmm/LTt/vGqYzv2Y5wGw4+uAlvtFtihQG2hczgPfjRAiOhKmaY2YsuKnV7WX4XaVsqqLhAcRZb48GEBRIoJpldi3FNe3kcGAadqXLi1PceykYdytnVf6YaCDNPI593bOMVVRkEp1+rfSzEJRCmunRaBrcfBfc3EU4Wrwyucqk6tIe53aB96PnEpJ6jpz8LPYBVtCxaLStRA/Ad1VlzSKSjALFsmsLceMinY3j82s4RHejY9BuUFanGg2eABHsHFWHIdeaRH/JvwSovvXuvPoQmdMqNJ0OJrr/fs9PA381Yg9r7GRSP1NHFd0X077Nnw==
Received: from [127.0.0.1] by nm42.bullet.mail.ne1.yahoo.com with NNFMP; 22 Apr 2016 06:46:14 -0000
Received: from [98.138.101.129] by nm42.bullet.mail.ne1.yahoo.com with NNFMP;  22 Apr 2016 06:43:23 -0000
Received: from [212.82.98.58] by tm17.bullet.mail.ne1.yahoo.com with NNFMP; 22 Apr 2016 06:43:23 -0000
Received: from [212.82.98.79] by tm11.bullet.mail.ir2.yahoo.com with NNFMP; 22 Apr 2016 06:43:23 -0000
Received: from [127.0.0.1] by omp1016.mail.ir2.yahoo.com with NNFMP; 22 Apr 2016 06:43:23 -0000
X-Yahoo-Newman-Property: ymail-4
X-Yahoo-Newman-Id: 699927.82643.bm@omp1016.mail.ir2.yahoo.com
X-YMail-OSG: l.rptjQVM1lRzeLiQRz8YkqZ4CRr7DRT.aEcqZ7ELY6SzUuW2k_eSCYrksHt8Uz 5WfhUt4vZT0YT.EDtbe.qV_sxIE_LR1y3cUrUSoZPCZQ978Yb1zztk2ZRDNOPWM3uegAhIOC0lE7 LCb8kmqwXvhmwIVE28PSifciBcidZvspzQ7FuMS.dp5Ae7atu8lnBIpEkOkN6AdGyewXrLv7Jcfo WwtKd.NLsQGOU3CWZRxizwj01rnM0MiMmHsPYsbyN2vbuw4yGAENmq.QGnQe35Scl6yVxAgLfU7M wIwtAc.qcv6jzGKMcYv7siJJLONoa9IPzCslS58AVWR0m6ICMDXRd5h_iQKfTGr.Fo.b3gKmkVN_ eHvcxOD_ypWQ3XWoxc5RJjwrGkh8UM6vmmBfSOErnnsnYeg8RfKb_nC2SumzI0F8ELeSb4HsMuBN fe0f36KHsxcVQvtR8Je_fz9T2cSokPXf1_2FFiT1FOdhLC58G4Xh.HlvK1dp..WwHZjVZBKE2hlQ MeaEhBfqcfZ5zLFz5ETR_ZJmXcNyH
Received: by 212.82.98.121; Fri, 22 Apr 2016 06:43:23 +0000 
Date: Fri, 22 Apr 2016 06:43:17 +0000 (UTC)
From: <lloyd.wood@yahoo.co.uk>
To: Phillip Hallam-Baker <phill@hallambaker.com>,  Ross Finlayson <finlayson@live555.com>
Message-ID: <612808179.92739.1461307397364.JavaMail.yahoo@mail.yahoo.com>
In-Reply-To: <CAMm+Lwiii4bN0_F2=-NutCjqJdrjNZaThRmJo08q7JXe-i8YhA@mail.gmail.com>
References: <CAMm+Lwiii4bN0_F2=-NutCjqJdrjNZaThRmJo08q7JXe-i8YhA@mail.gmail.com>
Subject: Re: Interim step on meetings site feedback for sites currently under active consideration
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/vbun5eEM01LtYW3u1FURuzCXgc8>
Cc: IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: lloyd.wood@yahoo.co.uk
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: Fri, 22 Apr 2016 06:46:17 -0000

>> The politics of communication systems sit in the top tier in=20
>> international diplomacy. Only actual military conflict outranks them.=20


How truly fortunate that no-one views energy, oil or trade as that importan=
t.

 Lloyd Wood lloyd.wood@yahoo.co.uk http://about.me/lloydwood=20


----- Original Message -----
From: Phillip Hallam-Baker <phill@hallambaker.com>
To: Ross Finlayson <finlayson@live555.com>
Cc: IETF Discussion Mailing List <ietf@ietf.org>
Sent: Friday, 22 April 2016, 9:51
Subject: Re: Interim step on meetings site feedback for sites currently und=
er active consideration

On Thu, Apr 21, 2016 at 7:11 PM, Ross Finlayson <finlayson@live555.com> wro=
te:

>
>> On Apr 21, 2016, at 7:50 AM, Phillip Hallam-Baker <phill@hallambaker.com=
> wrote:
>>
>> I think people are missing the point of the 'world tour'. It is not
>> just what happens inside the IETF that is important, it is the
>> perception of the IETF in other forums. In particular government
>> forums.
>>
>> The politics of communication systems sit in the top tier in
>> international diplomacy. Only actual military conflict outranks them.
>> One thing that every successful politician understands is the impact
>> of communication infrastructures on their position.
>
> The point=E2=80=99s well taken - but perhaps you=E2=80=99re conflating th=
e role of the IETF with that of the Internet Society (ISOC)?

IETF is an organized activity of ISOC. The government types do not see
a difference and it is not something I would spend time attempting to
explain.


From nobody Fri Apr 22 02:46:24 2016
Return-Path: <sm@elandsys.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 473FC12ECB7 for <ietf@ietfa.amsl.com>; Fri, 22 Apr 2016 02:46:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.786
X-Spam-Level: 
X-Spam-Status: No, score=-2.786 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.996, T_DKIM_INVALID=0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=opendkim.org header.b=DHEf5ndx; dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=elandsys.com header.b=n/aMBrVM
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 45Q0szDFIGgx for <ietf@ietfa.amsl.com>; Fri, 22 Apr 2016 02:46:21 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id E224A12ECB2 for <ietf@ietf.org>; Fri, 22 Apr 2016 02:46:20 -0700 (PDT)
Received: from SUBMAN.elandsys.com (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id u3M9k8fO002043 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 22 Apr 2016 02:46:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1461318380; x=1461404780; bh=A6ZH1qpZUZrp1rqQmocSxCPFevugbnax/MFNk/KMnEk=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=DHEf5ndxOnTiqC6ofdoC5TEK5megKBpBdx60ucJw9+KdB7Gwl2syWTUbbGa9WiOwK +xGqK+jdHzvhYHG0NGYcDilHWqqDGtOceCsnUUl77izR8j0Wa+cfLk4xq17tUG6Eb6 Cf5Efoqt7ufsQelzrm6VBrnY1e9Rln9nrBqN1vhk=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1461318380; x=1461404780; i=@elandsys.com; bh=A6ZH1qpZUZrp1rqQmocSxCPFevugbnax/MFNk/KMnEk=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=n/aMBrVMIUARAjkOtc/++YclKV83BEHsgiNHOAVrdRphEs7EfSKkCIC0sSBK/bLFw sq2iFnNghhA3mKxm13x5C7KziZctmCCbQRxyBeEL3EtcM++SQXyhcHBQMxgNCcCsU1 yCda7VOBvM9qT6O9wBOKJP/V7S9wCC92OHOnv+xo=
Message-Id: <6.2.5.6.2.20160422005428.110b3f28@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Fri, 22 Apr 2016 02:44:10 -0700
To: Corinne Cath <corinnecath@gmail.com>, Ted Lemon <mellon@fugue.com>, ietf@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: Interim step on meetings site feedback for sites currently under active consideration (off-topic)
In-Reply-To: <CAD499eLvW0KFToSHLb4faMHk2c5ad+HAPEwumaq48QaUbh2n2A@mail.g mail.com>
References: <57151C55.30206@gmail.com> <746128222.2295531.1461009032633.JavaMail.yahoo@mail.yahoo.com> <CAD499eLvW0KFToSHLb4faMHk2c5ad+HAPEwumaq48QaUbh2n2A@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/BJba0sAoa15u6LJtF3U4dND-HeA>
Cc: Juliao Braga <juliao@braga.net.br>, "Carlos M. Martinez" <carlos@lacnic.net>, Christian O'Flaherty <oflaherty@isoc.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: Fri, 22 Apr 2016 09:46:23 -0000

Hi Corinne, Ted,
At 01:48 19-04-2016, Corinne Cath wrote:
>Just a quick question: are you intending on providing feedback to 
>the IAOC? If so, maybe it makes sense to coordinate a bit in order 
>to prevent a duplication of entries? Or will it be useful if 
>multiple people point out the same themes?

The IAOC Chair requested comments about a future IETF meeting in 
Paris (France),
Montreal (Canada) or Copenhagen (Denmark) as the IAOC is considering 
whether the IETF can have a meeting in any of those countries.  It 
probably doesn't make much of a difference whether there is 
duplication of entries except to the person(s) who will be reading 
the messages to venue-selection@ietf.org to extract the points of concern.

At 05:02 19-04-2016, Ted Lemon wrote:
>The IETF has a very strong tradition of commenting at length on the 
>topic at hand and hoping either that IETF leadership will spend the 
>time to review the whole thread and extract the salient points from 
>it, or give up in despair.   So what you are seeing here is very 
>much the IETF tradition.   Asking people to do better probably won't 
>work, although it never hurts to try.

I read the 36 messages in this thread.  Although some of the content 
is interesting, it does not look like the messages are directly 
related to the subject line.  Even though two Area Directors read 
some of the messages, the discussion is on an unmanaged thread.  It 
is more of an effort instead of a problem to extract the arguments 
made on this thread.  The problem is what to suggest given that they 
may be related to multiple IETF policies.

Regards,
S. Moonesamy  


From howahong37@yahoo.com  Fri Apr 22 02:44:57 2016
Return-Path: <howahong37@yahoo.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 A83BA12DE9B for <ietf@ietfa.amsl.com>; Fri, 22 Apr 2016 02:44:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.515
X-Spam-Level: 
X-Spam-Status: No, score=-0.515 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, FREEMAIL_REPLYTO_END_DIGIT=0.25, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.996, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=yahoo.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 YAwm61MM2HFJ for <ietf@ietfa.amsl.com>; Fri, 22 Apr 2016 02:44:56 -0700 (PDT)
Received: from nm19-vm1.bullet.mail.ne1.yahoo.com (nm19-vm1.bullet.mail.ne1.yahoo.com [98.138.91.56]) (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 8B9E212D786 for <ietf@ietf.org>; Fri, 22 Apr 2016 02:44:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1461318295; bh=FSA28IS2VVReHZAaY1dgF77ZuD0Doc+mk4+Kz6fx7Iw=; h=Date:From:Reply-To:To:Subject:References:From:Subject; b=Ldz8S7a2Rn5uuqoHUR2pnUnq34CPCbuoGXgJv0q5CuvBsT3GyUzbie0rO4OoTpMYN8vDkPe/8TZg1/D+D4tA+uHkLIdbGgJwH7AH6F+u8bXmLKMDKIPfb0P8DwUXWBiHmnCrKEbaGDXNwFltJ/7pQndE2Kq7TOFDLIi+l1ocV2UOzVaT8wA5M9IGyLN1mnd3TmJrZLgg3bR4IWX0IOoWfdS7NMUB3lXC4vIOGiCGtzd5aLXEi5Mjj+QPLiLTuZPSxBsHXbRfY7TCHg6CxVxQGCl1BEwqmUOxLmCZTw9+NYvtoZFxXBt/DsyZSQ+aAnFVx2NJVDOZ/NSHcPeQZ18lEw==
Received: from [98.138.226.180] by nm19.bullet.mail.ne1.yahoo.com with NNFMP;  22 Apr 2016 09:44:55 -0000
Received: from [98.138.89.240] by tm15.bullet.mail.ne1.yahoo.com with NNFMP; 22 Apr 2016 09:44:55 -0000
Received: from [127.0.0.1] by omp1013.mail.ne1.yahoo.com with NNFMP; 22 Apr 2016 09:44:55 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 852433.61731.bm@omp1013.mail.ne1.yahoo.com
X-YMail-OSG: OCIAH3QVM1mGzUMutFNTl2qA0E6Sw044DIczQgXxBeYqgk22oUwDQMC8tbOcjUv RS45MYBvZ7uy3xRZ.wxWr3fJI197HADkHJoCT3egOU2ErhMWCWY_6SsVv66XLZGI6KpA.w0mMghV KlPo40RXrq_ZPOU7u6TeekZsRURosLLNvLyn2N4JQ.wki6OXhUIxPXc2UpgczxwUtdQO9nLuuNJW HtiVUK._OqhmeNOajJg10p1wVp1nOQBCpdZ3PsXPEVLT9eT86jMKGmw19mzFHKbfIIBescdvPBEA 1C7TrquVh_h2JFW5TL8AZbfM7IqcmJ8jhav5fSSsTfIrLmd6kJbdkB7UsBi5O4BrSIQYTM_koX6. xBOvYKr5udHgurMGHdgNDIgKRBOLhRZ5q6D0rLuDzNbXbxgOLDlDcC7CLwrFzBG8DGWOfZuqRn8U lZcIID9ay3B1fGKcfMUYA5GFLh6g4KdYcUpfualk9.dKLaP6HDiWU1g--
Received: by 98.138.105.211; Fri, 22 Apr 2016 09:44:55 +0000 
Date: Fri, 22 Apr 2016 09:44:55 +0000 (UTC)
From: Howard Hong <howahong37@yahoo.com>
To: "ietf@ietf.org" <ietf@ietf.org>
Message-ID: <94486323.183663.1461318295153.JavaMail.yahoo@mail.yahoo.com>
Subject: Spam catcher
MIME-Version: 1.0
Content-Type: multipart/alternative;  boundary="----=_Part_183662_1857624387.1461318295151"
References: <94486323.183663.1461318295153.JavaMail.yahoo.ref@mail.yahoo.com>
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/WTxG0zweWokGqYGex9FMJh3-FlM>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: Howard Hong <howahong37@yahoo.com>
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: Fri, 22 Apr 2016 09:48:43 -0000

------=_Part_183662_1857624387.1461318295151
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

Hello,
Would it help to stop spam by recording the IP address of the originating server when open SMTP relays collect mail? Record the IP address in the body of the e-mail, and record an IP address at each hop. Establish a chain of custody so I can track an e-mail back to the source IP address.
Thanks,Howard Hong

------=_Part_183662_1857624387.1461318295151
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 7bit

<html><head></head><body><div style="color:#000; background-color:#fff; font-family:HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif;font-size:16px"><div id="yui_3_16_0_ym19_1_1461317218372_7405">Hello,</div><div id="yui_3_16_0_ym19_1_1461317218372_7538"><br></div><div id="yui_3_16_0_ym19_1_1461317218372_7461">Would it help to stop spam by recording the IP address of the originating server when open SMTP relays collect mail? Record the IP address in the body of the e-mail, and record an IP address at each hop. Establish a chain of custody so I can track an e-mail back to the source IP address.</div><div id="yui_3_16_0_ym19_1_1461317218372_7547"><br></div><div>Thanks,</div><div id="yui_3_16_0_ym19_1_1461317218372_7548" dir="ltr">Howard Hong<br></div></div></body></html>
------=_Part_183662_1857624387.1461318295151--


From nobody Fri Apr 22 03:45:13 2016
Return-Path: <dave@cridland.net>
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 6CE8A12D6C1 for <ietf@ietfa.amsl.com>; Fri, 22 Apr 2016 03:45:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 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] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cridland.net
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 mY1Jb2LnJk9W for <ietf@ietfa.amsl.com>; Fri, 22 Apr 2016 03:45:10 -0700 (PDT)
Received: from mail-ob0-x232.google.com (mail-ob0-x232.google.com [IPv6:2607:f8b0:4003:c01::232]) (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 29E8212D1E0 for <ietf@ietf.org>; Fri, 22 Apr 2016 03:45:10 -0700 (PDT)
Received: by mail-ob0-x232.google.com with SMTP id n10so41171239obb.2 for <ietf@ietf.org>; Fri, 22 Apr 2016 03:45:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cridland.net; s=google; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=/1o/PAzmyWrkUvVmgubsP1kj0jx4o7rzdGqH8hgr1Ok=; b=AOfnEY539JzJ2OfDWgF5JaAPBG962YPWULZrGHxkCmIcICgst97npBSd8RsgrKACz1 FP8R2B2UFF0deKYzATwSGUx/0GGbge1+/28uBZvuCKUxN3pOkT8vg+g76IT7MlQv0Wi9 Mj5fqM4wxvSu5TbdY2XCTYwdI2UW5RQCtKY9o=
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:date :message-id:subject:from:to:cc; bh=/1o/PAzmyWrkUvVmgubsP1kj0jx4o7rzdGqH8hgr1Ok=; b=DVtHFETkrlcllNt4tyQn3xawkmZq9y/M2NHXHOmfJ3myVz4ikyBMpGD8IsXXqYrL2c hssh4ZfSyeMcfOYBgknnZIAbQaGBq6ecDh37yRWCd/cR3VpMGc0hZbh8uZ/Tlaab6tqU +sS/JU9UXpHWnXbA2NEJAuKq0igsej13Bj+rGzhcp6wNMOdxT7jpA9YB/jsPakMRFAdn jEVff+ljxvDrTpqr9W4zEXfrsBlcJdDge/8bGjXWWAo1sYY4FRi9XOhi6b6jJQcVK7Z4 VXDvPKCdFht/8yMsjKb53t7RfF9+1a3Qt7t09YJGGfnTQBSHsSz+K356yS6euPp0iKta Cfhg==
X-Gm-Message-State: AOPr4FVwiE5rzpSSsRM9+GED5W3nUpCtar45pdoFIQokIawvzjxRCK0swSfwPDR2sHxr/5U9QfoylCeX2BOPQcU2
MIME-Version: 1.0
X-Received: by 10.182.17.9 with SMTP id k9mr8250644obd.3.1461321909550; Fri, 22 Apr 2016 03:45:09 -0700 (PDT)
Received: by 10.157.8.46 with HTTP; Fri, 22 Apr 2016 03:45:09 -0700 (PDT)
In-Reply-To: <94486323.183663.1461318295153.JavaMail.yahoo@mail.yahoo.com>
References: <94486323.183663.1461318295153.JavaMail.yahoo.ref@mail.yahoo.com> <94486323.183663.1461318295153.JavaMail.yahoo@mail.yahoo.com>
Date: Fri, 22 Apr 2016 11:45:09 +0100
Message-ID: <CAKHUCzzzypTXDoDAHxFFhusRP-_K3r70juZzy3Xw9FUtPh0Mzg@mail.gmail.com>
Subject: Re: Spam catcher
From: Dave Cridland <dave@cridland.net>
To: Howard Hong <howahong37@yahoo.com>
Content-Type: multipart/alternative; boundary=f46d0444745b525ef50531108518
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/qYRgc3nsJb3FFmbTayjxL2oZWrg>
Cc: "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: Fri, 22 Apr 2016 10:45:11 -0000

--f46d0444745b525ef50531108518
Content-Type: text/plain; charset=UTF-8

Howard,

It would, and does, to some degree - the trace header fields (particularly
Received) specify exactly this in RFC 5321 and RFC 5322. The problem is
that these can be faked by various means.

DKIM extends this to provide cryptographic proof of the chain of custody,
too.

So while one cannot find the originating IP address, one can find the last
known good server in the presented custody chain with some effort and
reasonable reliability. This doesn't stop spam in its tracks, of course,
but as you note it does help.

Dave.

On 22 April 2016 at 10:44, Howard Hong <howahong37@yahoo.com> wrote:

> Hello,
>
> Would it help to stop spam by recording the IP address of the originating
> server when open SMTP relays collect mail? Record the IP address in the
> body of the e-mail, and record an IP address at each hop. Establish a chain
> of custody so I can track an e-mail back to the source IP address.
>
> Thanks,
> Howard Hong
>

--f46d0444745b525ef50531108518
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Howard,</div><div><br></div>It would, and does, to so=
me degree - the trace header fields (particularly Received) specify exactly=
 this in RFC 5321 and RFC 5322. The problem is that these can be faked by v=
arious means.<div><br></div><div>DKIM extends this to provide cryptographic=
 proof of the chain of custody, too.</div><div><br></div><div>So while one =
cannot find the originating IP address, one can find the last known good se=
rver in the presented custody chain with some effort and reasonable reliabi=
lity. This doesn&#39;t stop spam in its tracks, of course, but as you note =
it does help.</div><div><br></div><div>Dave.</div></div><div class=3D"gmail=
_extra"><br><div class=3D"gmail_quote">On 22 April 2016 at 10:44, Howard Ho=
ng <span dir=3D"ltr">&lt;<a href=3D"mailto:howahong37@yahoo.com" target=3D"=
_blank">howahong37@yahoo.com</a>&gt;</span> wrote:<br><blockquote class=3D"=
gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-=
left:1ex"><div><div style=3D"color:#000;background-color:#fff;font-family:H=
elveticaNeue,Helvetica Neue,Helvetica,Arial,Lucida Grande,sans-serif;font-s=
ize:16px"><div>Hello,</div><div><br></div><div>Would it help to stop spam b=
y recording the IP address of the originating server when open SMTP relays =
collect mail? Record the IP address in the body of the e-mail, and record a=
n IP address at each hop. Establish a chain of custody so I can track an e-=
mail back to the source IP address.</div><div><br></div><div>Thanks,</div><=
div dir=3D"ltr">Howard Hong<br></div></div></div></blockquote></div><br></d=
iv>

--f46d0444745b525ef50531108518--


From nobody Fri Apr 22 04:30:03 2016
Return-Path: <cattekwaad@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 4B17E12E3D8 for <ietf@ietfa.amsl.com>; Fri, 22 Apr 2016 04:30:01 -0700 (PDT)
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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 IUIHhs8rDTCu for <ietf@ietfa.amsl.com>; Fri, 22 Apr 2016 04:29:59 -0700 (PDT)
Received: from mail-wm0-x22e.google.com (mail-wm0-x22e.google.com [IPv6:2a00:1450:400c:c09::22e]) (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 44C8112D903 for <ietf@ietf.org>; Fri, 22 Apr 2016 04:29:59 -0700 (PDT)
Received: by mail-wm0-x22e.google.com with SMTP id v200so1896987wmv.1 for <ietf@ietf.org>; Fri, 22 Apr 2016 04:29:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc; bh=VQAqcOuulXPxkpZDjy2caQRlgvSw/NCCWQYeRd1fP3c=; b=nVCSbrhtt2szOnrtYE6C2/jCwmzCeistzfyWGCzNq8OKM2jhn3mS2JJOMVO8SrkplR DOpyAuV9hTFpFfVNoFJMaSZp+ksy7a+x1VjJxVQxihna4/MU3rV+PiwQSs8ihYIQxNxr DI+y8HCKlYXsziMHvinE+6K07166AEZX+BXBDzKByyM49BnqW0chG15f53N9eT8NAu4V Ftbm+ynoZyYQabnI/TxRuznmtVNZEgt6psVkvdA/KJBSEH9vel4+TPxgSijaMyGFKRMV fLXWvI9tOVXXnR5IF/Na4py/jNZTCuhYpUs9S3D7lJqhjPsVO310pz2pidWbf4nLnIT0 4DBg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:date :message-id:subject:from:to:cc; bh=VQAqcOuulXPxkpZDjy2caQRlgvSw/NCCWQYeRd1fP3c=; b=i0nQtTk17+nehB2KQvUFApQNRzpvVf+YjIqBPkZu+9XnvmI5FAadIbdEoQX9gXwA+j lDYONFWyWCLg0F1x4wmhBtRm0j+/xlamStmYKSvDw48oNYsR3KuIQ41+kh91bF0MhRdq m/cPT3UjjhzkZSRinGsb2YtWH7B6MsEo9ZK0K/KBWgIrSF1ZQITvkJVhXyaG//vx/pzq f/zdqPLlOK8CfUcdSvLCTMSRoWU+3RkJngJVLK3Pmyhls8rS17QcaoYqafghhcGc0oS4 tdZrn1lmUplT9eskHtsoDI+rbvrUIr5Gzz1l3uk11Zc/uvyadQcWYWMAU6n5ZG4iwwp1 MCHA==
X-Gm-Message-State: AOPr4FUsdQj5KNu3JT1vnEuuVCKKtf0zwOeMIkYdKBvrCtS/TOQo68ji/vF3i6DVuVr1+PmkmOSsVNVBFRaB2w==
MIME-Version: 1.0
X-Received: by 10.194.61.19 with SMTP id l19mr19435724wjr.4.1461324597885; Fri, 22 Apr 2016 04:29:57 -0700 (PDT)
Sender: cattekwaad@gmail.com
Received: by 10.194.190.71 with HTTP; Fri, 22 Apr 2016 04:29:57 -0700 (PDT)
In-Reply-To: <6.2.5.6.2.20160422005428.110b3f28@resistor.net>
References: <57151C55.30206@gmail.com> <746128222.2295531.1461009032633.JavaMail.yahoo@mail.yahoo.com> <CAD499eLvW0KFToSHLb4faMHk2c5ad+HAPEwumaq48QaUbh2n2A@mail.gmail.com> <6.2.5.6.2.20160422005428.110b3f28@resistor.net>
Date: Fri, 22 Apr 2016 12:29:57 +0100
X-Google-Sender-Auth: NHYTlsgjEj2qxYe9qxk3RBW5SBg
Message-ID: <CAD499eJWX8DU7iyvSxDtFWm+srpJWRMyLe+PZ7sL3+=hb6pibQ@mail.gmail.com>
Subject: Re: Interim step on meetings site feedback for sites currently under active consideration (off-topic)
From: Corinne Cath <corinnecath@gmail.com>
To: S Moonesamy <sm+ietf@elandsys.com>
Content-Type: multipart/alternative; boundary=047d7ba97bfe8f0c2d05311125ae
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/SIxnIcsa75bque01CiqPmjL_G7M>
Cc: ietf@ietf.org, Juliao Braga <juliao@braga.net.br>, "Carlos M. Martinez" <carlos@lacnic.net>, Christian O'Flaherty <oflaherty@isoc.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: Fri, 22 Apr 2016 11:30:01 -0000

--047d7ba97bfe8f0c2d05311125ae
Content-Type: text/plain; charset=UTF-8

excellent. thank you, best, corinne

On Fri, Apr 22, 2016 at 10:44 AM, S Moonesamy <sm+ietf@elandsys.com> wrote:

> Hi Corinne, Ted,
> At 01:48 19-04-2016, Corinne Cath wrote:
>
>> Just a quick question: are you intending on providing feedback to the
>> IAOC? If so, maybe it makes sense to coordinate a bit in order to prevent a
>> duplication of entries? Or will it be useful if multiple people point out
>> the same themes?
>>
>
> The IAOC Chair requested comments about a future IETF meeting in Paris
> (France),
> Montreal (Canada) or Copenhagen (Denmark) as the IAOC is considering
> whether the IETF can have a meeting in any of those countries.  It probably
> doesn't make much of a difference whether there is duplication of entries
> except to the person(s) who will be reading the messages to
> venue-selection@ietf.org to extract the points of concern.
>
> At 05:02 19-04-2016, Ted Lemon wrote:
>
>> The IETF has a very strong tradition of commenting at length on the topic
>> at hand and hoping either that IETF leadership will spend the time to
>> review the whole thread and extract the salient points from it, or give up
>> in despair.   So what you are seeing here is very much the IETF tradition.
>>  Asking people to do better probably won't work, although it never hurts to
>> try.
>>
>
> I read the 36 messages in this thread.  Although some of the content is
> interesting, it does not look like the messages are directly related to the
> subject line.  Even though two Area Directors read some of the messages,
> the discussion is on an unmanaged thread.  It is more of an effort instead
> of a problem to extract the arguments made on this thread.  The problem is
> what to suggest given that they may be related to multiple IETF policies.
>
> Regards,
> S. Moonesamy
>

--047d7ba97bfe8f0c2d05311125ae
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-family:georgia,=
serif">excellent. thank you, best, corinne <br></div></div><div class=3D"gm=
ail_extra"><br><div class=3D"gmail_quote">On Fri, Apr 22, 2016 at 10:44 AM,=
 S Moonesamy <span dir=3D"ltr">&lt;<a href=3D"mailto:sm+ietf@elandsys.com" =
target=3D"_blank">sm+ietf@elandsys.com</a>&gt;</span> wrote:<br><blockquote=
 class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc soli=
d;padding-left:1ex">Hi Corinne, Ted,<br>
At 01:48 19-04-2016, Corinne Cath wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
Just a quick question: are you intending on providing feedback to the IAOC?=
 If so, maybe it makes sense to coordinate a bit in order to prevent a dupl=
ication of entries? Or will it be useful if multiple people point out the s=
ame themes?<br>
</blockquote>
<br>
The IAOC Chair requested comments about a future IETF meeting in Paris (Fra=
nce),<br>
Montreal (Canada) or Copenhagen (Denmark) as the IAOC is considering whethe=
r the IETF can have a meeting in any of those countries.=C2=A0 It probably =
doesn&#39;t make much of a difference whether there is duplication of entri=
es except to the person(s) who will be reading the messages to <a href=3D"m=
ailto:venue-selection@ietf.org" target=3D"_blank">venue-selection@ietf.org<=
/a> to extract the points of concern.<br>
<br>
At 05:02 19-04-2016, Ted Lemon wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
The IETF has a very strong tradition of commenting at length on the topic a=
t hand and hoping either that IETF leadership will spend the time to review=
 the whole thread and extract the salient points from it, or give up in des=
pair.=C2=A0 =C2=A0So what you are seeing here is very much the IETF traditi=
on.=C2=A0 =C2=A0Asking people to do better probably won&#39;t work, althoug=
h it never hurts to try.<br>
</blockquote>
<br>
I read the 36 messages in this thread.=C2=A0 Although some of the content i=
s interesting, it does not look like the messages are directly related to t=
he subject line.=C2=A0 Even though two Area Directors read some of the mess=
ages, the discussion is on an unmanaged thread.=C2=A0 It is more of an effo=
rt instead of a problem to extract the arguments made on this thread.=C2=A0=
 The problem is what to suggest given that they may be related to multiple =
IETF policies.<br>
<br>
Regards,<br>
S. Moonesamy=C2=A0 <br>
</blockquote></div><br></div>

--047d7ba97bfe8f0c2d05311125ae--


From nobody Fri Apr 22 09:38:48 2016
Return-Path: <johnl@taugh.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 2D3D912DF86 for <ietf@ietfa.amsl.com>; Fri, 22 Apr 2016 09:38:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] 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 fIirTMMQyUio for <ietf@ietfa.amsl.com>; Fri, 22 Apr 2016 09:38:46 -0700 (PDT)
Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B102512D508 for <ietf@ietf.org>; Fri, 22 Apr 2016 09:38:45 -0700 (PDT)
Received: (qmail 88117 invoked from network); 22 Apr 2016 16:38:44 -0000
Received: from unknown (64.57.183.18) by mail1.iecc.com with QMQP; 22 Apr 2016 16:38:44 -0000
Date: 22 Apr 2016 16:38:22 -0000
Message-ID: <20160422163822.29642.qmail@ary.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: Spam catcher
In-Reply-To: <94486323.183663.1461318295153.JavaMail.yahoo@mail.yahoo.com>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/PLEIiHv1EmM0BqC9QqUMWBik_0o>
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: Fri, 22 Apr 2016 16:38:47 -0000

>Would it help to stop spam by recording the IP address of the originating server when open SMTP relays collect mail? Record
>the IP address in the body of the e-mail, and record an IP address at each hop. Establish a chain of custody so I can track
>an e-mail back to the source IP address.

Short answer: no.

Open SMTP relays disappeared a decade ago when spammers started
abusing them, and SMTP servers have always recorded the incoming IP
addresss in Received headers.

As someone else noted, once you get more than one hop, you have no
reason to believe the Received headers unless you know the relaying
host is reliable (in which case it's unlikely to have a spam problem.)

DKIM offers some help in identifying the originating, or at least the
signing server.  ARC is a work in progress to try to provide a signed
chain of DKIM like headers.

In my experience, other than a few narrow cases related to mailing
lists, trying to filter based on IPs beyond the immediately connecting
host isn't very effective.  The same IP could have a legit user
sending real mail and a botnet sending spam.

R's,
John


From nobody Fri Apr 22 13:07:27 2016
Return-Path: <nd@syndicat.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 A41CD12E6C4 for <ietf@ietfa.amsl.com>; Fri, 22 Apr 2016 13:07:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.298
X-Spam-Level: 
X-Spam-Status: No, score=-5.298 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.996, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=syndicat.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 6PvJG4Wk55zi for <ietf@ietfa.amsl.com>; Fri, 22 Apr 2016 13:07:24 -0700 (PDT)
Received: from mail.syndicat.com (mail.syndicat.com [62.146.89.62]) (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 EA96612E6CA for <ietf@ietf.org>; Fri, 22 Apr 2016 13:07:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=syndicat.com; s=x;  h=To:References:Message-Id:Cc:Date:In-Reply-To:From:Content-Type:Mime-Version:Subject; bh=VRwvDlI61j9rTBxGq0f8zEQTLY2x0FScD4Q1YQOwDwM=;  b=IIf2KEOeMjzuczeHXlkiZIBRCMvN2Hm/KFf6UVtyIGmtPAUPuCHvskYqheZKbs0BbmcoIx+1L32HB2S7Cgnya0zq4EXLASwZY/8o5HhaxZZjdAJyjIIb5zim4sA7W61w4LjJflesRT0N+9ftQqMBa5AA551csyCbUxhpoKjVKNQ=;
Received: from localhost.syndicat.com ([127.0.0.1] helo=localhost) by mail.syndicat.com with esmtp (Syndicat.com PostHamster 4.84) (envelope-from <nd@syndicat.com>) id 1athMG-0000D8-Fe; Fri, 22 Apr 2016 22:07:20 +0200
X-Virus-Scanned: amavisd-new at syndicat.com
Received: from mail.syndicat.com ([127.0.0.1]) by localhost (mail.syndicat.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ac3JP2ZHBKua; Fri, 22 Apr 2016 22:07:20 +0200 (CEST)
Received: from p5dd4b75f.dip0.t-ipconnect.de ([93.212.183.95] helo=[192.168.222.107]) by mail.syndicat.com with esmtpsa (TLSv1:DHE-RSA-AES256-SHA:256) (Syndicat.com PostHamster 4.84) (envelope-from <nd@syndicat.com>) id 1athMG-0003YQ-7e; Fri, 22 Apr 2016 22:07:20 +0200
Subject: Re: Spam catcher
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Content-Type: multipart/signed; boundary="Apple-Mail=_9921E731-48EA-4DAC-916A-E93F791C928C"; protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail 2.6b2
From: "Niels Dettenbach (Syndicat.com)" <nd@syndicat.com>
In-Reply-To: <20160422163822.29642.qmail@ary.lan>
Date: Fri, 22 Apr 2016 22:07:14 +0200
Message-Id: <42F47494-E066-4334-8057-6CD50AD5F733@syndicat.com>
References: <20160422163822.29642.qmail@ary.lan>
To: John Levine <johnl@taugh.com>
X-Mailer: Apple Mail (2.3124)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/ZKESpAsEgUNs66Bebiqi1Mwal6Y>
Cc: 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: Fri, 22 Apr 2016 20:07:26 -0000

--Apple-Mail=_9921E731-48EA-4DAC-916A-E93F791C928C
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8


> Am 22.04.2016 um 18:38 schrieb John Levine <johnl@taugh.com>:
>=20
> Open SMTP relays disappeared a decade ago when spammers started
> abusing them

This is nearly two decades the case (even if every days starts =
misconfigured - usually not really usuable - relays until today.)=E2=80=A6=


best regards,


Niels.
=E2=80=94
Niels Dettenbach.
Syndicat IT & Internet
http.//www.syndicat.com

--Apple-Mail=_9921E731-48EA-4DAC-916A-E93F791C928C
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: Syndicat GnuPG build

iQIcBAEBCgAGBQJXGoR3AAoJEA27WohFkipE0DkQAKV3opf0awJGWKhwNmaL+zVk
M/4MN9q3A9GaUpUXPC61JJvCzQ7DoAtZUPrNYSUHkr5PsYngq2vaZcXnTbh5LDHW
vLngSEGD9i+ORGu/cMF18jtNDV9lPzS8havBcOsN6hUrEK2cEckHW85IUsBgUQRr
XJGkmNFvVVugjrOdjSfBXlKzx2qtZ7qEvVkPLHyYcLcclA6w2eXLW8oZfF96xbWu
XPArULwDL9OevalWgJszR4SFhif7IvYViAnJDmdhnsUX7BdSLmgwufKz0zajU+UX
mBDBeU9py3fv1dO9S4uknvRWNUKtTrskWhh3uvtms9OPywTqQJPmrwaQUmYQDv94
cyE5nlQ+Qjo1d56k0pq8oHjzkiuUas0zEMBsl4JPxnSofNlW9TikObTWKDbIdf8O
oGkHceo/ls/fKHBNyVHj9XBMPfZUS08nzUaB6DO5MMMzvveK46ffS20l7QWM8LRn
a4wrArOuWeCKjIyrCtBw4DCZ+W8TZIpxc/NTAlqOc1fhFYkqceBkF6402k8JUTgM
E+YItWPzfy6hvkaweeXmPsKS9ddxueI9efwsglDCBMjj5YjEyAyXVEMPm+T6e+WO
MXXZ9bkI6Z+SFH/ljTa1HfsINBC1UCC3M1y3G14hcmuhajId6C5UgkXeNdUUsZvX
AjYZRzgjfLh8Vf41jV1O
=u8nK
-----END PGP SIGNATURE-----

--Apple-Mail=_9921E731-48EA-4DAC-916A-E93F791C928C--


From nobody Fri Apr 22 13:48:22 2016
Return-Path: <wes@mti-systems.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 98B5212E939 for <ietf@ietfa.amsl.com>; Fri, 22 Apr 2016 13:48:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001] 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 VItgwcuQAgHZ for <ietf@ietfa.amsl.com>; Fri, 22 Apr 2016 13:48:18 -0700 (PDT)
Received: from atl4mhob11.myregisteredsite.com (atl4mhob11.myregisteredsite.com [209.17.115.49]) by ietfa.amsl.com (Postfix) with ESMTP id B7EC112D815 for <ietf@ietf.org>; Fri, 22 Apr 2016 13:48:17 -0700 (PDT)
Received: from mailpod.hostingplatform.com ([10.30.71.211]) by atl4mhob11.myregisteredsite.com (8.14.4/8.14.4) with ESMTP id u3MKmFTW031260 for <ietf@ietf.org>; Fri, 22 Apr 2016 16:48:15 -0400
Received: (qmail 19036 invoked by uid 0); 22 Apr 2016 20:48:15 -0000
X-TCPREMOTEIP: 65.189.201.79
X-Authenticated-UID: wes@mti-systems.com
Received: from unknown (HELO ?192.168.1.104?) (wes@mti-systems.com@65.189.201.79) by 0 with ESMTPA; 22 Apr 2016 20:48:15 -0000
Subject: Re: [aqm] Last Call: <draft-ietf-aqm-eval-guidelines-11.txt> (AQM Characterization Guidelines) to Informational RFC
To: ietf@ietf.org
References: <20160420124713.32376.24588.idtracker@ietfa.amsl.com> <5717E73E.9030501@taht.net>
From: Wesley Eddy <wes@mti-systems.com>
Message-ID: <571A8E05.40308@mti-systems.com>
Date: Fri, 22 Apr 2016 16:48:05 -0400
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2
MIME-Version: 1.0
In-Reply-To: <5717E73E.9030501@taht.net>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/eNZcnu8kaihgIswfcrQ_C-jsH88>
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: Fri, 22 Apr 2016 20:48:20 -0000

Hi Dave, just to provide context for the IETF list, I wanted to say that 
I'm the document shepherd for this, and we had noted in the writeup in 
the tracker this lack of "running code" that you raised earlier in the 
working group, so I think it will be understood by the IESG.

As the shepherd, the reason I believe this is okay (though obviously 
code is always desirable) is that this is going to be Informational 
guidance (not a "standard", as you mentioned), and the hope is that it 
provides some helpful advice for someone wondering how to determine if 
an AQM will be appropriate for deployment in their operational 
environment, or otherwise evaluate AQMs.

So, it isn't really intended to describe how to write a piece of code, 
similar to many other Informational RFCs.



On 4/20/2016 4:31 PM, Dave Täht wrote:
> My basic objection to this entire draft is that it needs to be made
> executable in some benchmarking suite before being considered as a
> standard.
>
> While it has many seemingly desirable stats and figures
> few have been demonstrated as useful or used in the real world, nor have
> any of the aqms under evaluation already been tested under it.
>
> This has been my steady objection to it from day one, and as a
> co-developer of a benchmark suite (flent.org) that *does* rigorously
> explore some of the complexities aqm and fq technologies introduce,
> with suitably complex tests, topologies, and graphs, I have long been
> doubtful that the simple metrics and models used here were useful or
> sufficient.
>
> I have given detailed critiques of each metric to the wg before, and
> could again, but my main point remained:
>
> Rough consensus *and* Running Code is needed here.
>
> And with that, I'd stopped paying attention to it, until code materialized.
>
> On 4/20/16 5:47 AM, The IESG wrote:
>> The IESG has received a request from the Active Queue Management and
>> Packet Scheduling WG (aqm) to consider the following document:
>> - 'AQM Characterization Guidelines'
>>    <draft-ietf-aqm-eval-guidelines-11.txt> as Informational RFC
>>
>> The IESG plans to make a decision in the next few weeks, and solicits
>> final comments on this action. Please send substantive comments to the
>> ietf@ietf.org mailing lists by 2016-05-04. Exceptionally, comments may be
>> sent to iesg@ietf.org instead. In either case, please retain the
>> beginning of the Subject line to allow automated sorting.
>>
>> Abstract
>>
>>
>>     Unmanaged large buffers in today's networks have given rise to a slew
>>     of performance issues.  These performance issues can be addressed by
>>     some form of Active Queue Management (AQM) mechanism, optionally in
>>     combination with a packet scheduling scheme such as fair queuing.
>>     This document describes various criteria for performing precautionary
>>     characterizations of AQM schemes.
>>
>>
>>
>>
>> The file can be obtained via
>> https://datatracker.ietf.org/doc/draft-ietf-aqm-eval-guidelines/
>>
>> IESG discussion can be tracked via
>> https://datatracker.ietf.org/doc/draft-ietf-aqm-eval-guidelines/ballot/
>>
>>
>> No IPR declarations have been submitted directly on this I-D.
>>
>>
>> _______________________________________________
>> aqm mailing list
>> aqm@ietf.org
>> https://www.ietf.org/mailman/listinfo/aqm
>>
>
>


From nobody Sat Apr 23 08:57:26 2016
Return-Path: <nalini.elkins@insidethestack.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 8276612D181 for <ietf@ietfa.amsl.com>; Sat, 23 Apr 2016 08:57:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.72
X-Spam-Level: 
X-Spam-Status: No, score=-0.72 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=yahoo.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 07oOx3zjujVG for <ietf@ietfa.amsl.com>; Sat, 23 Apr 2016 08:57:22 -0700 (PDT)
Received: from nm9-vm6.bullet.mail.ne1.yahoo.com (nm9-vm6.bullet.mail.ne1.yahoo.com [98.138.91.102]) (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 98D7912D149 for <ietf@ietf.org>; Sat, 23 Apr 2016 08:57:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1461427042; bh=q7J0z6R+Qa1H2QauXufs6UdKC/7jkdQ+zUBUouhGuTE=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:From:Subject; b=CfCYwm0PHiyfxpd4bYtoJ84NVvxvqgB6URSSnj/uyRS4bolh6hzl6EVViyOeYAFEZcXxc+h/OaewLAiXorvcB+4J1UO9Dm0MgRnmshKKoF6m4SsHK86doyfuFn+MIdunAWNNST2/mSxIwmMDDkbDWYsJE1fO0jfKurBnDf4L35KKOiAPxAjYfea9gt5EE87BVjULP9NUWnSy1bp3oHC4mvaDdOmj0WzDkIiP3sOnf7xM6BlCuyHILBExmKBxtA000WKM9oOY7xDgPaZQ6nLN6a8cp9x6blSgOMdzJcob9DxR4TeeVewtw8YBuO2jRghUNtCoqrCB1UxTvOMTSqDWwQ==
Received: from [98.138.101.130] by nm9.bullet.mail.ne1.yahoo.com with NNFMP; 23 Apr 2016 15:57:22 -0000
Received: from [98.138.89.170] by tm18.bullet.mail.ne1.yahoo.com with NNFMP; 23 Apr 2016 15:57:21 -0000
Received: from [127.0.0.1] by omp1026.mail.ne1.yahoo.com with NNFMP; 23 Apr 2016 15:57:21 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 882844.97778.bm@omp1026.mail.ne1.yahoo.com
X-YMail-OSG: 9Z7l8aQVM1n9kTsP6Sz60OUToKoFShenhtRb7fZ.juTOSNvcfGK_22EvA1RHfw0 ZilwMXojSNk3hJPpOX2fBvRJaUykCC5cr4__bVTH5_2oLxIe8lB7C8Tanpd_CeLby9Li3zR0TN6S vJ1rrx1SXIOnqemgfBSlmEjjTlpeFWQWGj1lW3emA2wRPYLCxCApxMBrW6_mt40mGIz9TOBKBViy lC3i2YP.dez2cvnxe8FZwOIavwQ9RGjl.DmROkaflUEuQPLIkpQnYHGmM52ATHmHo1ugktZUCmDe xpuUNkqdx9ysaSh13_oTGerdqG1cRT.YQwQnQMt9mbnCszr.uwiZQBfHy1NrmQ0Hj2VkUomceDsC 9h0cijm7KS92I3zUDvZaUZy697OARcUBVlfNmXhqdzWNQqGTS1a.Ly9YWgVcvGdjI.SWFkMa2o4X YnowmCFsHKZ5.JvCPQXd6MMxT425RdIJX9lh0g3rBJrwfOE7_DYMWA3zYS8Y8MF9pEKq1UZu7mbz _a7r4KNGFNVTNph.6_6SKlbrzsAj_BLPSV8YHyHRTnNJAdc67Bg--
Received: by 98.138.101.164; Sat, 23 Apr 2016 15:57:21 +0000 
Date: Sat, 23 Apr 2016 15:57:20 +0000 (UTC)
From: <nalini.elkins@insidethestack.com>
To: IETF Discussion List <ietf@ietf.org>
Message-ID: <2003316287.716228.1461427040919.JavaMail.yahoo@mail.yahoo.com>
In-Reply-To: <1389181485.681559.1461426902202.JavaMail.yahoo@mail.yahoo.com>
References: <1389181485.681559.1461426902202.JavaMail.yahoo@mail.yahoo.com>
Subject: Re: draft-arkko-ietf-trends-and-observations-00
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/-P99VfIxxabysgFl58gATNFEQA0>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: nalini.elkins@insidethestack.com
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, 23 Apr 2016 15:57:24 -0000

All,

Great to have this document put out for community discussion.   After reading the document, I feel that there are a few additional things that we may want to discuss:


1.  In the Introduction, there is no discussion of globalization and the economic / political context.  I will give my thoughts below.

2.  The issues of "Culture" and "Renewal and Diversity" are discussed in Section 4.  I feel that these are some of the most important issues facing us today.  (My thoughts below)

3.  Section 3 discusses "Funding".  Again, IMHO, a core issue.  My thoughts below.



My thoughts:

1.  The changing financial balance in the world and how it impacts the IETF

2.  The impact of diversity and what it means to the IETF

3.  The increased importance and reliance of the world on the Internet

4.  The need to get and spend money wisely in a way that reflects the importance of the IETF to the continuing success of the Internet


Let me discuss each.

Changing Financial Balance
--------------------------
With money, comes power.  The unquestioned dominance of the West is declining.  It seems clear that other parts of the world: China, India, Latin (and South) America, and certain parts of Africa are developing rapidly and gaining technical sophistication.  The context we find ourselves in is that of fundamental transitions taking place in the world.  The IETF is not immune from the changes that it itself has helped to create: that is, the Internet and how it has exponentially increased the rate of change.

You may wish to read an interesting article from the World Bank which discusses what may be happening in 2025:
http://web.worldbank.org/WBSITE/EXTERNAL/EXTDEC/EXTDECPROSPECTS/EXTGDH/0,,contentMDK:22915409~menuPK:7935744~pagePK:64167689~piPK:64167673~theSitePK:7933464,00.html

If you look at the IETF Chair report for IETF95:  https://www.internetsociety.org/sites/default/files/IETF%20Chair's%20Report.pdf 

on page 3, you will see the attendee split for IETF95.  

This split does not match the population of the world.   If you assume that intelligence and technical talent is evenly distributed across cultures and ethnic groups, it is likely that over time, the makeup of IETF will also shift to more closely match that of the makeup of the world. Today, China and India both have about 1.3 billion people, the United States has about 320 million.  Today, the IETF is dominated by the United States and Western Europe.

Certainly, the problems which come with high population, entrenched poverty, political corruption, educational systems which need improvement, and so forth cannot be ignored.   Yet, the gains in economic power made by China, India, Latin (and South) America and so forth, also cannot be ignored.

So, what do we do?  If this indeed is the case, and we are looking, over time, at a very changed IETF attendee composition, how do we handle it gracefully?    What are the problems that may arise?


The Impact of Diversity
------------------------
Diversity and culture need much more discussion.  These are among the most important issues facing us if we want to navigate this transition gracefully.  I live in the United States in the State of California.  There is no racial group that has over 50% in California. 

http://kff.org/other/state-indicator/distribution-by-raceethnicity/

In California, we are all minorities.  This is likely to be where the IETF is going.

So, what does this mean?

The IETF has a culture, which IMHO, works quite well to support innovation.  Having said that, the IETF culture is redolent of the culture of Berkeley in the 1970s (with some of the political correctness of Northern California in 2016 thrown in for good measure!).   Some of us (esp. those of us who live in Northern California) find that familiar and feel quite comfortable in that culture.  Others, not so much.

We have much experience with issues of diversity in California.  Battles over what language(s) will be spoken in schools, dress codes and other issues are constantly on the ballots in local elections.  As is the inevitable backlash over the sharing of power that is entailed.  Hence, the Trump reality show disguised as a primary contest.

Obviously, this issue is not unique to California or the United States.   Consider Germany with their generosity and kindness in taking many, many refugees.   They are now dealing with the impacts of their generosity.

To truly deal with diversity, requires sensitivity and awareness as well as having the right people be a part of that conversation.  Moving forth, sensitivity about culture, language, food preferences, what is "affordable", venue, etc, will become more and more important.   I would submit that this actually requires a draft co-authored by a number of people on how best to navigate these waters.


Increased Importance of the Internet
------------------------------------
In a very few years, the Internet has become extraordinarily important to the world.  There is no reason to think that this will become less so.  If we did not have standards by which network equipment could interoperate, there would be no Internet.  Our role in creating these standards is critical to the successful operation of the Internet.

We need to have the best people available (whatever "available" means) to create the best standards possible.   This implies the best engineering talent, management, training programs, events, and so on.


The need for money
------------------
To support the best engineering talent needs money.   Serious money. Much more money than is budgeted today.

Having said that, most people have absolutely no idea what the IETF does and why they might want to pay more money to support it.  This needs to change.

This issue, along with diversity, IMHO, are THE issues that we need to be talking about.
  


Next Steps
----------
One thing that we do at my company retreat which helps us to think about where we might be going in the future and thus decide on which product lines and initiatives to support today (and what new ones to plan for) is to play a game called "Headlines".   The idea is that you put yourself 5 years into the future and write newspaper (or blog) headlines which affect your company.

Let's play this for the IETF.   Here are some of my headlines.

Headlines for IETF110 (July 2020)
---------------------------------------------

New Movie Announced: Godzilla vs. Mothra
Yet another Network Gizmo vendor, this time from country nnn, sends 200 attendees to IETF.   IETF now up to 3,000 attendees.


Two-Week IETF Announced for IETF110
With 300 concurrent WGs, a one week meeting, long found to be inadequate, has finally been increased to two weeks. 



Virtual Reality Meetups
Internet Draft review teams meet via holograms.  


Recap of IETF109: City vvv in Developing World Country nnn
109Attendees list flooded with comments about the shocking in-your-face poverty of City vvv.  Bird-poo scam of IETF95 recalled fondly by grey beards.  



IETF under Microscope
The major Internet outage caused by the cyberterrorist attack which took down the Internet in 5 countries for 3 days in December of 2019 highlighted the dependence that we have come to have on the Internet. The "I" agencies (ICANN, IETF, ISOC) are being examined for effectiveness by the US Congress and the European Duo (France and Germany).  You will recall that the European Union collapsed in early 2019.   The U.S. "60 Minutes" expose news show plans a series on "Who is the IETF and what does it do?"


Death Announcement: Sunset4 finally concluded
As IPv6 reaches 20% penetration globally, it is felt that the Sunset4 WG is no longer needed

I wonder if it might be a good exercise to have more "headlines" from the community.  Many a truth is spoken in jest.  It may help us to think out where we are going in a spirit of camaraderie and good will.


From nobody Sat Apr 23 11:50:43 2016
Return-Path: <lrg_pizza_xtra_chz_plz@aol.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 6396E12D556 for <ietf@ietfa.amsl.com>; Sat, 23 Apr 2016 11:50:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.894
X-Spam-Level: 
X-Spam-Status: No, score=-2.894 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, LOTS_OF_MONEY=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.996, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=mx.aol.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 v9e9uAsovAtz for <ietf@ietfa.amsl.com>; Sat, 23 Apr 2016 11:50:40 -0700 (PDT)
Received: from omr-a014e.mx.aol.com (omr-a014e.mx.aol.com [204.29.186.62]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E8BD212D11F for <ietf@ietf.org>; Sat, 23 Apr 2016 11:50:39 -0700 (PDT)
Received: from mtaomg-mbc02.mx.aol.com (mtaomg-mbc02.mx.aol.com [172.26.221.144]) by omr-a014e.mx.aol.com (Outbound Mail Relay) with ESMTP id 0E78A38000A2 for <ietf@ietf.org>; Sat, 23 Apr 2016 14:50:39 -0400 (EDT)
Received: from core-lea01f.mail.aol.com (core-lea01.mail.aol.com [10.76.11.1]) by mtaomg-mbc02.mx.aol.com (OMAG/Core Interface) with ESMTP id C25D038000082 for <ietf@ietf.org>; Sat, 23 Apr 2016 14:50:38 -0400 (EDT)
Received: from 128.218.39.180 by webprd-m54.mail.aol.com (10.74.5.47) with HTTP (WebMailUI); Sat, 23 Apr 2016 14:50:38 -0400
Date: Sat, 23 Apr 2016 14:50:38 -0400
From: Casey Farrell <lrg_pizza_xtra_chz_plz@aol.com>
To: ietf@ietf.org
Message-Id: <15444759a9f-839-3c9d@webprd-m54.mail.aol.com>
In-Reply-To: <CAND0zA0sp0FTWXea9wSoXYVqyJjnL5sZjs9Xi8CJhPtAJ7HgTQ@mail.gmail.com>
Subject: A kwik brcwn fcks jamps ovur ya leizi dcg ( Developer seeks FUNDING )
MIME-Version: 1.0
Content-Type: multipart/alternative;  boundary="----=_Part_19649_1822216745.1461437438621"
X-MB-Message-Source: WebUI
X-MB-Message-Type: User
X-Mailer: JAS STD
X-Originating-IP: [128.218.39.180]
x-aol-global-disposition: G
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mx.aol.com; s=20150623; t=1461437439; bh=BmehQ9BuUfJ6TGptpbrHgnti6LYC/Ipgy5/NlysS+Ik=; h=From:To:Subject:Message-Id:Date:MIME-Version:Content-Type; b=S319tmnCTkcTTW/AdEHAazgMZzKcvb/E8Bcc96JQqDWwKPQnl4YqmjiTvVg/z1+tg MsaoXwX8L7LA2lhrHrCLoRBlKwTkAJ0EIAswdKqIbBu37RY5/zAaN3SXm9VWLX/KCr gktPKL9LuAGvvhjUGApajd1KGrrNiZiIresa67TI=
x-aol-sid: 3039ac1add90571bc3fe40e0
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/EC7kTGl8nWseOu_Xnh-0wOy3Ap0>
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, 23 Apr 2016 18:50:41 -0000

------=_Part_19649_1822216745.1461437438621
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


 

 

Casey Farrell
lrg_pizza_xtra_chz_plz@aol.com

 

 

-----Original Message-----
From: Casey Farrell <caseyfarrell26@gmail.com>
To: Keisi Feral <lrg_pizza_xtra_chz_plz@aol.com>
Sent: Sat, Apr 23, 2016 11:44 am
Subject: Fwd: A kwik brcwn fcks jamps ovur ya leizi dcg ( Developer seeks FUNDING )





---------- Forwarded message ----------
From: Casey Farrell <caseyfarrell26@gmail.com>
Date: Sat, Apr 23, 2016 at 11:42 AM
Subject: Fwd: A kwik brcwn fcks jamps ovur ya leizi dcg ( Developer seeks FUNDING )
To: OP-ED Dept <oped@nytimes.com>






---------- Forwarded message ----------
From: Casey Farrell <caseyfarrell26@gmail.com>
Date: Sat, Apr 23, 2016 at 11:42 AM
Subject: A kwik brcwn fcks jamps ovur ya leizi dcg ( Developer seeks FUNDING )
To: info@waldenvc.com







RE: http://www.kulefornia.blogspot.com / http://www.kclefornia.blogspot.com 


   revised to KELUFORNIA ("Keh-'LOVE'-fornyuh") PHONETIC TRANSCRIPTION of ENGLISH


A veritable 'Morse Code' for ENGLISH LANGUAGE texting- WORLD's FASTEST WRITING SYSTEM


KELUFORNIA Copyright 2016 Casey Farrell
  

                ALL RIGHTS RESERVED 


The Author seeks venture capital funding in San Francisco, of $4.5M for development locally.


Thank you-


 Casey Farrell


tel: 415/690-9883 








------=_Part_19649_1822216745.1461437438621
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 7bit

<font color='black' size='2' face='arial'>

<div> <br>

</div>



<div> <br>

</div>



<div style="clear:both">Casey Farrell<br>

lrg_pizza_xtra_chz_plz@aol.com<br>

</div>



<div> <br>

</div>



<div> <br>

</div>



<div style="font-family:arial,helvetica;font-size:10pt;color:black">-----Original Message-----<br>

From: Casey Farrell &lt;caseyfarrell26@gmail.com&gt;<br>

To: Keisi Feral &lt;lrg_pizza_xtra_chz_plz@aol.com&gt;<br>

Sent: Sat, Apr 23, 2016 11:44 am<br>

Subject: Fwd: A kwik brcwn fcks jamps ovur ya leizi dcg ( Developer seeks FUNDING )<br>

<br>






<div id="AOLMsgPart_2_0afba701-9e43-4712-b529-e49fd7813bc4">


<div class="aolReplacedBody">

<div dir="ltr"><br>



<div class="gmail_quote">---------- Forwarded message ----------<br>

From: <b class="gmail_sendername">Casey Farrell</b> <span dir="ltr">&lt;<a target="_blank" href="mailto:caseyfarrell26@gmail.com">caseyfarrell26@gmail.com</a>&gt;</span><br>

Date: Sat, Apr 23, 2016 at 11:42 AM<br>

Subject: Fwd: A kwik brcwn fcks jamps ovur ya leizi dcg ( Developer seeks FUNDING )<br>

To: OP-ED Dept &lt;<a target="_blank" href="mailto:oped@nytimes.com">oped@nytimes.com</a>&gt;<br>

<br>

<br>



<div class="HOEnZb">

<div class="h5">

<div dir="ltr"><br>



<div class="gmail_quote">---------- Forwarded message ----------<br>

From: <b class="gmail_sendername">Casey Farrell</b> <span dir="ltr">&lt;<a target="_blank" href="mailto:caseyfarrell26@gmail.com">caseyfarrell26@gmail.com</a>&gt;</span><br>

Date: Sat, Apr 23, 2016 at 11:42 AM<br>

Subject: A kwik brcwn fcks jamps ovur ya leizi dcg ( Developer seeks FUNDING )<br>

To: <a target="_blank" href="mailto:info@waldenvc.com">info@waldenvc.com</a><br>

<br>

<br>



<div dir="ltr">

<div>

<div>

<div>

<div>

<div>

<div>

<div>

<div>RE: <a target="_blank" href="http://www.kulefornia.blogspot.com">http://www.kulefornia.blogspot.com</a> / <a target="_blank" href="http://www.kclefornia.blogspot.com">http://www.kclefornia.blogspot.com</a> <br>

<br>

</div>

&nbsp;&nbsp; revised to KELUFORNIA ("Keh-'LOVE'-fornyuh") PHONETIC TRANSCRIPTION of ENGLISH<br>

<br>

</div>

A veritable 'Morse Code' for ENGLISH LANGUAGE texting- WORLD's FASTEST WRITING SYSTEM<br>

<br>

</div>

KELUFORNIA Copyright 2016 Casey Farrell<br>

&nbsp; <br>

</div>

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ALL RIGHTS RESERVED <br>

<br>

</div>

The Author seeks venture capital funding in San Francisco, of $4.5M for development locally.<br>

<br>

</div>

Thank you-<br>

<br>

</div>

&nbsp;Casey Farrell<br>

<br>

</div>

tel: <a target="_blank" href="tel:415%2F690-9883">415/690-9883</a> <br>

</div>


</div>

<br>

</div>


</div>

</div>

</div>

<br>

</div>


</div>


</div>





</div>

</font>
------=_Part_19649_1822216745.1461437438621--


From nobody Mon Apr 25 13:15:34 2016
Return-Path: <jari.arkko@piuha.net>
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 6D70912D104 for <ietf@ietfa.amsl.com>; Mon, 25 Apr 2016 13:15:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.896
X-Spam-Level: 
X-Spam-Status: No, score=-2.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.996] 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 gUEtzsQq2UIh for <ietf@ietfa.amsl.com>; Mon, 25 Apr 2016 13:15:31 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [IPv6:2a00:1d50:2::130]) by ietfa.amsl.com (Postfix) with ESMTP id B54A7120727 for <ietf@ietf.org>; Mon, 25 Apr 2016 13:15:30 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 8BEF72CCAE; Mon, 25 Apr 2016 23:15:29 +0300 (EEST) (envelope-from jari.arkko@piuha.net)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id b5bpg191s3ZT; Mon, 25 Apr 2016 23:15:28 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id B1D032CC6F; Mon, 25 Apr 2016 23:15:28 +0300 (EEST) (envelope-from jari.arkko@piuha.net)
Subject: Re: Last Call on draft-bradner-rfc3979bis-08.txt ("Intellectual Property Rights in IETF Technology")
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Content-Type: multipart/signed; boundary="Apple-Mail=_341299A3-3E4C-4E5C-B36A-313694D24FA4"; protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail 2.5.2
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <E7E31E22-1C86-40C4-BC5B-F65132015EF5@qti.qualcomm.com>
Date: Mon, 25 Apr 2016 23:15:25 +0300
Message-Id: <6CA3C554-0FF6-4779-80B9-C75698FB61C1@piuha.net>
References: <0000431F-F977-4A24-BA4D-064F740977A0@piuha.net> <E7E31E22-1C86-40C4-BC5B-F65132015EF5@qti.qualcomm.com>
To: Pete Resnick <presnick@qti.qualcomm.com>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/BvD4tSwb67cESRGQIkKmfc4A4xs>
Cc: IETF <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: Mon, 25 Apr 2016 20:15:33 -0000

--Apple-Mail=_341299A3-3E4C-4E5C-B36A-313694D24FA4
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252

Thanks Pete.

I=92m working slowly through your comments, but wanted to agree on at =
least these from my personal perspective:

> A few editorial ones suggested by some lawyer friends. They all seem =
eminently sensible to me:
>=20
> - Section 5.5(A): s/i.e./e.g.
>=20
> - Section 5.5(B): s/royalty rates/royalties. I'm told that there are =
royalties that might not have "rates" associated with them.

yes

> - Section 5.5(C): Two things:
>=20
> OLD
>      and will attach to the associated IPR
> NEW
>      and will attach, to the extent permissible by law, to the =
associated IPR
> END
>=20
> I'm told that there are some jurisdictions where you may not be able =
to do that.

yep

> OLD
>      must ensure that such
>      commitments are binding on any subsequent transferee of the
>      relevant IPR.
> NEW
>      must ensure that such commitments are binding on a transferee of
>      the relevant IPR, and that such transferee will use reasonable
>      efforts to ensure that such commitments are binding on a
>      subsequent transferee of the relevant IPR, and so on.
> END
>=20
> The object of the "subsequent" wasn't clear, so this just spells it =
out. Wordy, but more precise.

right

> - Section 7, paragraph 6:
>=20
> The only change in this paragraph from 3979 was to add the word "all" =
in the second-to-last sentence. My lawyer friends tell me that this =
little change is opening a can of worms, having to do with licensing to =
makers of parts instead of implementers of the whole specification. I =
don't think we meant to change the meaning from the 3979 meaning, and I =
certainly don't think that we meant to change some implication about =
whether folks in general needed to license to people that make parts =
where they wouldn't have before. Was there something unclear about that =
sentence that needed the word "all" added to it? We aren't making a =
substantive change, are we? Can we just strike it? It seemed pretty =
clear to me before.

agree

> As far as the concern, the second part of the next sentence in =
5.4.2(A) is worrisome:
>=20
>                                                                    If =
a
>       patent has issued, then the new IPR disclosure must include the
>       patent number and, if the claims of the granted patent differ
>       from those of the application in manner material to the relevant
>       Contribution, the IPR disclosure must describe any differences =
in
>       applicability to the Contribution.
>=20
> The first part is fine, though it repeats what's in 5.4.1 already, so =
I think it can be dropped. But the second part is what I'm concerned =
about. We've never before required disclosures to determine and discuss =
the applicability of the disclosure to the Contribution, and nowhere =
else in this document is that mentioned. Indeed, we go to great lengths =
to say that the leadership of the IETF doesn't try to figure out =
applicability, and that even WGs or the IESG can only take into account =
their opinions of what the applicability is. As a general rule, I don't =
think we can ask people who disclose to do the analysis to determine =
what parts of the patent do or do not apply to a particular =
contribution. As we say elsewhere, that's really up to a court. So I =
think the above should just be dropped.

I agree, although I wonder if the intent was to cover a case where =97 =
given the changes in claims =97 the issued patent no longer covers the =
draft. But, even so, there=92s a practical concern: I=92m not sure it is =
easy to get lawyers to state that they have no claims on a particular =
topic.

Jari


--Apple-Mail=_341299A3-3E4C-4E5C-B36A-313694D24FA4
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQIcBAEBCgAGBQJXHnrdAAoJEM80gCTQU46qpuAQAIZy5vq45/SjyKoRE5Hz7PKC
X44N2iIqcjWPumDvu5xdesk3qxUc/47acUSZSvojcJNF1Ph5cvGZFLbgr7OBQLy3
oAjdT/8qg2czf4tqlORDL2Ek5U1yxioFKPL0o9uU8j9DMNM1GvyVq7G8zUcJbciS
F/8xUv2Jry2v9XJhzosLvzy6Pk+3DO/Slt/qQMLV5luXFUAvSE4wHecPexmjCbIh
eEJbxdw3OSqQEjzYxupcRN0w9xFSOZEYu6q/33/X4lV6zqWgehO5cDq0zY0NNQ58
o0NSkgNBd1kQbKSTIGxNg8PBLmT4u/NCRCr/fHdOr67R5EuGj5eWNMA1BHFFAF/m
SKWmvNnBMDc1oVgCKuhh/DKNZ6yt+9z8jL572awyqSKnBuu5Mba9DJj9eSkd33Ud
9dx1DR6ALESDm4Equ0y+G72SXqn6u0kroMP8m9ZglGOrs+99DYbrhlaBY/NL1Cfr
SJbPrqcE1D06nPIPf43P+98FfIrh1TH0XtH3b6wHuvDTRW0vT0Hhl65UxBYOtVkZ
HKQs9mpod7I7gBwN6Cy3ih0zKqI/RelATwSlaRHiiu2Eem5og/L9VIUI8sXTa2hT
MyPtwU7OzmsQRSwtVhscQqH+UmBrqfaLC+6zCduhQKpc9Mmy0ny3sZtK/GRtymq9
pmE1RvbBFGvbkW6obBHb
=rEH0
-----END PGP SIGNATURE-----

--Apple-Mail=_341299A3-3E4C-4E5C-B36A-313694D24FA4--


From nobody Mon Apr 25 14:32:05 2016
Return-Path: <stewe@stewe.org>
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 7FDAF12D0B0 for <ietf@ietfa.amsl.com>; Mon, 25 Apr 2016 14:32:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] 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 waQ9Au-KThWS for <ietf@ietfa.amsl.com>; Mon, 25 Apr 2016 14:32:01 -0700 (PDT)
Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1on0731.outbound.protection.outlook.com [IPv6:2a01:111:f400:fc10::731]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2AE3C12D149 for <ietf@ietf.org>; Mon, 25 Apr 2016 14:32:01 -0700 (PDT)
Received: from BLUPR17MB0275.namprd17.prod.outlook.com (10.162.235.146) by BLUPR17MB0273.namprd17.prod.outlook.com (10.162.235.144) with Microsoft SMTP Server (TLS) id 15.1.477.8; Mon, 25 Apr 2016 21:31:42 +0000
Received: from BLUPR17MB0275.namprd17.prod.outlook.com ([10.162.235.146]) by BLUPR17MB0275.namprd17.prod.outlook.com ([10.162.235.146]) with mapi id 15.01.0477.012; Mon, 25 Apr 2016 21:31:42 +0000
From: Stephan Wenger <stewe@stewe.org>
To: Jari Arkko <jari.arkko@piuha.net>, Pete Resnick <presnick@qti.qualcomm.com>
Subject: Re: Last Call on draft-bradner-rfc3979bis-08.txt ("Intellectual Property Rights in IETF Technology")
Thread-Topic: Last Call on draft-bradner-rfc3979bis-08.txt ("Intellectual Property Rights in IETF Technology")
Thread-Index: AQHRhDTbKR9yu1RueEWA9RrAiHSISp+FI5mAgBYyZID//5/2gA==
Date: Mon, 25 Apr 2016 21:31:42 +0000
Message-ID: <EC4CBF0D-1B7C-4FB5-85EA-E622B24E9B9A@stewe.org>
References: <0000431F-F977-4A24-BA4D-064F740977A0@piuha.net> <E7E31E22-1C86-40C4-BC5B-F65132015EF5@qti.qualcomm.com> <6CA3C554-0FF6-4779-80B9-C75698FB61C1@piuha.net>
In-Reply-To: <6CA3C554-0FF6-4779-80B9-C75698FB61C1@piuha.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: piuha.net; dkim=none (message not signed) header.d=none;piuha.net; dmarc=none action=none header.from=stewe.org;
x-ms-exchange-messagesentrepresentingtype: 1
x-originating-ip: [50.174.30.183]
x-ms-office365-filtering-correlation-id: f25eb691-dbb0-47d1-ebef-08d36d50fec2
x-microsoft-exchange-diagnostics: 1; BLUPR17MB0273; 5:hDa7O3G2g8Ybzrup2Sjz7m+vtKEPBsAK9tWcxKd/KPEcgjB/vf+sB7UQvol1d6cY9CwV+ezFUpWjd+JRrrj60u+4wbgC/fJ4v7R+pPdDw5xVyiTQdyvG572z7Oh88eak0r9YiG/u84yH4nBPrr4hFA==; 24:r2AAFNtzPgCL1IFyNYUUiZU+XCkuUY3PiRIey5lhdlrhWb3FkezeJmfWVLxL2rP4AO6qxbj/KE+sPK0iPQFNX0FVIFHowGkpGh191cd6wtA=; 7:m5sppoAqwXzwkmnIloIe+birerCo8spcuJIOrkurQG77o1s+yHIeQDeMC330PXxFFPk8qNQh+iluTzBZlumEf9ZRuOk2Ab5DSQ8BwnW6Mhv4Dvu7lqmo5SuYQE0uEE/ZZwKxMh67PWGNDaTqEgXPXHc3Aw1byNYuubdDrFyntgUD+b8RICM8dJfmvd7poGhv
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:BLUPR17MB0273;
x-microsoft-antispam-prvs: <BLUPR17MB027354C25F9CF5B6A7848C8CAE620@BLUPR17MB0273.namprd17.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(9101521072)(6040130)(601004)(2401047)(8121501046)(5005006)(10201501046)(3002001)(6041072)(6043046); SRVR:BLUPR17MB0273; BCL:0; PCL:0; RULEID:; SRVR:BLUPR17MB0273; 
x-forefront-prvs: 0923977CCA
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(24454002)(1220700001)(1096002)(4326007)(82746002)(5002640100001)(19580405001)(33656002)(19580395003)(36756003)(92566002)(76176999)(3280700002)(3660700001)(2906002)(54356999)(50986999)(3846002)(586003)(6116002)(102836003)(122556002)(5008740100001)(83716003)(86362001)(87936001)(99286002)(11100500001)(189998001)(106116001)(5004730100002)(10400500002)(230783001)(5001770100001)(2950100001)(66066001)(2900100001)(77096005)(81166005)(42262002)(104396002); DIR:OUT; SFP:1102; SCL:1; SRVR:BLUPR17MB0273; H:BLUPR17MB0275.namprd17.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en; 
spamdiagnosticoutput: 1:23
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
Content-ID: <1A63854213E6B648AF61BC6908D0C271@namprd17.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: stewe.org
X-MS-Exchange-CrossTenant-originalarrivaltime: 25 Apr 2016 21:31:42.4463 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 865fc51c-5fae-4322-98ef-0121a85df0b6
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BLUPR17MB0273
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/nOndVfUo6ORpFi42kT38HQYMW8Y>
Cc: IETF <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: Mon, 25 Apr 2016 21:32:03 -0000

SGksDQpQbGVhc2Ugc2VlIGlubGluZS4gIEV2ZXJ5dGhpbmcgSSBhZ3JlZSB3aXRoIChyZWx1Y3Rh
bnRseSBvciB3aG9sZWhlYXJ0ZWRseSkgaXMgZGVsZXRlZC4NClRoYW5rcywNClN0ZXBoYW4NCg0K
DQoNCg0KDQpPbiA0LzI1LzE2LCAxMzoxNSwgImlldGYgb24gYmVoYWxmIG9mIEphcmkgQXJra28i
IDxpZXRmLWJvdW5jZXNAaWV0Zi5vcmcgb24gYmVoYWxmIG9mIGphcmkuYXJra29AcGl1aGEubmV0
PiB3cm90ZToNCg0KPg0KPj4gLSBTZWN0aW9uIDUuNShDKTogVHdvIHRoaW5nczoNCj4+IA0KDQpb
Li4uXQ0KDQo+PiBPTEQNCj4+ICAgICAgbXVzdCBlbnN1cmUgdGhhdCBzdWNoDQo+PiAgICAgIGNv
bW1pdG1lbnRzIGFyZSBiaW5kaW5nIG9uIGFueSBzdWJzZXF1ZW50IHRyYW5zZmVyZWUgb2YgdGhl
DQo+PiAgICAgIHJlbGV2YW50IElQUi4NCj4+IE5FVw0KPj4gICAgICBtdXN0IGVuc3VyZSB0aGF0
IHN1Y2ggY29tbWl0bWVudHMgYXJlIGJpbmRpbmcgb24gYSB0cmFuc2ZlcmVlIG9mDQo+PiAgICAg
IHRoZSByZWxldmFudCBJUFIsIGFuZCB0aGF0IHN1Y2ggdHJhbnNmZXJlZSB3aWxsIHVzZSByZWFz
b25hYmxlDQo+PiAgICAgIGVmZm9ydHMgdG8gZW5zdXJlIHRoYXQgc3VjaCBjb21taXRtZW50cyBh
cmUgYmluZGluZyBvbiBhDQo+PiAgICAgIHN1YnNlcXVlbnQgdHJhbnNmZXJlZSBvZiB0aGUgcmVs
ZXZhbnQgSVBSLCBhbmQgc28gb24uDQo+PiBFTkQNCj4+IA0KPj4gVGhlIG9iamVjdCBvZiB0aGUg
InN1YnNlcXVlbnQiIHdhc24ndCBjbGVhciwgc28gdGhpcyBqdXN0IHNwZWxscyBpdCBvdXQuIFdv
cmR5LCBidXQgbW9yZSBwcmVjaXNlLg0KPg0KPlJpZ2h0DQoNCknigJltIG5vdCBzdXJlIEkgYWdy
ZWUgdGhhdCB0aGUgb2JqZWN0IG9mIOKAnHN1YnNlcXVlbnQgd2FzbuKAmXQgY2xlYXIgZnJvbSBj
b250ZXh0LiAgSG93ZXZlciwgSSBkb27igJl0IG1pbmQgdG8gc2VlIHRoYXQgZml4ZWQgaWYgb3Ro
ZXJzIGZlZWwgc28uICBIb3dldmVyLCB0aGUgZml4IGFzIHByb3Bvc2VkIHNldHMgYSB2ZXJ5IGxv
dyBzdGFuZGFyZCAocmVhc29uYWJsZSBlZmZvcnRzKSBmb3IgZW5zdXJpbmcgdGhhdCBzdWJzZXF1
ZW50IHRyYW5zZmVyZWVzIGFyZSBib3VuZC4gVGhhdCBhIHN1YnN0YW50aWFsIGNoYW5nZSBmcm9t
IHRoZSBXRyBjb25zZW5zdXMsIGFuZCBJTU8gaW4gdGhlIHdyb25nIGRpcmVjdGlvbi4NCg0KV2hh
dCB3ZSB3YW50IHRvIGFjaGlldmUgaXMgdGhhdCBpZiBBIGFzc2lnbnMgYSBwYXRlbnQgdG8gQiwg
QiBhbmQgYWxsIGZ1cnRoZXIgdHJhbnNmZXJlZXMgKEIgdG8gQywgQyB0byBELCBldGMuIGV0Yy4p
IGFyZSBzaW1pbGFybHkgYm91bmQuICBXZSB3YW50IHRvIG1ha2Ugc3VyZSBpZiBhbnkgb2YgdGhl
c2UgZW50aXRpZXMgZG9lc27igJl0IGZlZWwgYm91bmQgZm9yIHdoYXRldmVyIHJlYXNvbiwgdGhl
IHBhdGVudCBpcyBoZWxkIHVuZW5mb3JjaWJsZSBieSBhIHdlbGwtaW5mb3JtZWQgY291cnQuICBJ
dOKAmXMgY2xlYXIgdGhhdCB0aGlzIGlzIG11Y2ggbW9yZSBvbmVyb3VzIHRvIHRoZSByaWdodGhv
bGRlciwgYW5kIG1heSB3ZWxsIGxvd2VyIHRoZSB2YWx1ZSBvZiB0aGUgSVBSLiANCg0KSSB3b3Vs
ZCBiZSBmaW5lIGlmIHRoZSBORVcgcGFydCB3b3VsZCBiZSByZXdvcmRlZCBhcyBmb2xsb3dzOg0K
TkVXDQogICAgICBtdXN0IGVuc3VyZSB0aGF0IHN1Y2ggY29tbWl0bWVudHMgYXJlIGJpbmRpbmcg
b24gYSB0cmFuc2ZlcmVlIG9mDQogICAgICB0aGUgcmVsZXZhbnQgSVBSLCBhbmQgYWxzbyBiaW5k
aW5nIG9uIGFueSBzdWJzZXF1ZW50IHRyYW5zZmVyZWVzIA0Kb2YgdGhlIHJlbGV2YW50IElQUi4N
CkVORA0KDQoNCg0KDQoNCj4NCj4+IC0gU2VjdGlvbiA3LCBwYXJhZ3JhcGggNjoNCj4+IA0KPj4g
VGhlIG9ubHkgY2hhbmdlIGluIHRoaXMgcGFyYWdyYXBoIGZyb20gMzk3OSB3YXMgdG8gYWRkIHRo
ZSB3b3JkICJhbGwiIGluIHRoZSBzZWNvbmQtdG8tbGFzdCBzZW50ZW5jZS4gTXkgbGF3eWVyIGZy
aWVuZHMgdGVsbCBtZSB0aGF0IHRoaXMgbGl0dGxlIGNoYW5nZSBpcyBvcGVuaW5nIGEgY2FuIG9m
IHdvcm1zLCBoYXZpbmcgdG8gZG8gd2l0aCBsaWNlbnNpbmcgdG8gbWFrZXJzIG9mIHBhcnRzIGlu
c3RlYWQgb2YgaW1wbGVtZW50ZXJzIG9mIHRoZSB3aG9sZSBzcGVjaWZpY2F0aW9uLiBJIGRvbid0
IHRoaW5rIHdlIG1lYW50IHRvIGNoYW5nZSB0aGUgbWVhbmluZyBmcm9tIHRoZSAzOTc5IG1lYW5p
bmcsIGFuZCBJIGNlcnRhaW5seSBkb24ndCB0aGluayB0aGF0IHdlIG1lYW50IHRvIGNoYW5nZSBz
b21lIGltcGxpY2F0aW9uIGFib3V0IHdoZXRoZXIgZm9sa3MgaW4gZ2VuZXJhbCBuZWVkZWQgdG8g
bGljZW5zZSB0byBwZW9wbGUgdGhhdCBtYWtlIHBhcnRzIHdoZXJlIHRoZXkgd291bGRuJ3QgaGF2
ZSBiZWZvcmUuIFdhcyB0aGVyZSBzb21ldGhpbmcgdW5jbGVhciBhYm91dCB0aGF0IHNlbnRlbmNl
IHRoYXQgbmVlZGVkIHRoZSB3b3JkICJhbGwiIGFkZGVkIHRvIGl0PyBXZSBhcmVuJ3QgbWFraW5n
IGEgc3Vic3RhbnRpdmUgY2hhbmdlLCBhcmUgd2U/IENhbiB3ZSBqdXN0IHN0cmlrZSBpdD8gSXQg
c2VlbWVkIHByZXR0eSBjbGVhciB0byBtZSBiZWZvcmUuDQo+DQo+QWdyZWUNCg0KSeKAmW0gbm90
IHN1cmUgaGVyZS4NCkZvciBjb250ZXh0LCB0aGUgcGFyYWdyYXBoIGlzIGluIHNlY3Rpb24gNyBv
ZiBSRkMzOTc5YmlzICh3aGljaCB1c2VkIHRvIGJlIHRoZSBzZWNvbmQgcGFyYWdyYXBoIG9mIHNl
Y3Rpb24gOCBvZiBSRkMzOTc5KS4gIFRoZSBzZW50ZW5jZSBpbiBxdWVzdGlvbiBkZXNjcmliZXMg
YW4gcHVycG9ydGVkIElFVEYgY29uc2Vuc3VzIGVzdGFibGlzaGVkIGluIHByZS1SRkMzOTc5IHRp
bWVzLCBhcyBmb2xsb3dzICh0aGUgY3JpdGljYWwgYW5kIG5ldyDigJxBTEzigJ0gaXMgY2FwaXRh
bGl6ZWQpOg0KDQrigJwNCkFuIElFVEYgY29uc2Vuc3VzIGhhcyBkZXZlbG9wZWQgdGhhdCBubyBt
YW5kYXRvcnktdG8taW1wbGVtZW50IHNlY3VyaXR5IHRlY2hub2xvZ3kgY2FuIGJlIHNwZWNpZmll
ZCBpbiBhbiBJRVRGIHNwZWNpZmljYXRpb24gdW5sZXNzIGl0IGhhcyBubyBrbm93biBJUFIgY2xh
aW1zIGFnYWluc3QgaXQgb3IgYSByb3lhbHR5LWZyZWUgbGljZW5zZSBpcyBhdmFpbGFibGUgdG8g
QUxMIGltcGxlbWVudGVycyBvZiB0aGUgc3BlY2lmaWNhdGlvbiB1bmxlc3MgdGhlcmUgaXMgYSB2
ZXJ5IGdvb2QgcmVhc29uIHRvIGRvIHNvLiANCg0K4oCcDQoNCkkgYWdyZWUgdGhhdCB0aGUgdGln
aHRlbmVkIGxhbmd1YWdlIHJlbW92ZXMgYW4gYXJndWFibHkgdW5jbGVhciBsb29waG9sZSB0aGF0
IGhhcyBiZWVuIHByZXNlbnQgaW4gUkZDMzk3OSwgYW5kIHdoaWNoIFBldGXigJlzIGxhd3llci1m
cmllbmRzIHByb2JhYmx5IHdvdWxkIGxpa2UgdG8gcHJlc2VydmUuICBIb3dldmVyLCBnZW5lcmFs
bHkgc3BlYWtpbmcsIHJlbW92aW5nIGxvb3Bob2xlcyBsaWtlIHRoaXMgaXMgYSBHb29kIFRoaW5n
LCB1bmxlc3MgdGhlIGNvbnNlbnN1cyBhdCB0aGUgdGltZSB3YXMgc3VjaCB0aGF0IHRoZXJlIG91
Z2h0IHRvIGJlIGEgbG9vcGhvbGUuICBJIGRpZCBub3QgZm9sbG93IHRoZSBjb25zZW5zdXMgcHJv
Y2VzcyBpbiBzdWZmaWNpZW50IGRldGFpbCB0byBoYXZlIGFuIG9waW5pb24sIGJ1dCBwZXJoYXBz
IHNlY3VyaXR5IGFuZCBJUFIgY29uc2Npb3VzIGZvbGtzIGluIHRoZSBJRVRGIHJlbWVtYmVyPw0K
DQoNCg==


From nobody Tue Apr 26 08:19:54 2016
Return-Path: <iad@ietf.org>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 0B1CD12D5C0; Mon, 25 Apr 2016 09:02:29 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: IETF Administrative Director <iad@ietf.org>
To: "IETF Announcement List" <ietf-announce@ietf.org>
Subject: Community Input Requested on Update to Trust Records Retention Policy
X-Test-IDTracker: no
X-IETF-IDTracker: 6.19.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20160425160229.28320.45734.idtracker@ietfa.amsl.com>
Date: Mon, 25 Apr 2016 09:02:29 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/T1fB2JNHz80KLjmLeKswxAz82G8>
X-Mailman-Approved-At: Tue, 26 Apr 2016 08:19:53 -0700
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Reply-To: trustees@ietf.org
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: Mon, 25 Apr 2016 16:02:29 -0000

The Trustees of the IETF Trust are considering updating the IETF
Trust Records Retention and Management Policy that was adopted in
2007 and would like community input before making changes. 

The objectives of the Policy are:
  a.  Ensure compliance with legal and regulatory obligations;
  b.  Reduce storage costs and increasing efficiency;
  c.  Retrieve current information or important archives more easily and 
       reliably;
  d.  Minimize litigation costs; and
  e.   Provide a more accurate and reliable record of the IETF Trustâ€™s 
        actions and decisions.

The Policy addresses the following matters:	

  a.  Storage and access of physical records
  b.  Storage and access of electronic records
  c.  Access to historic electronic records
  d.  Records Destruction
  e.  Document Retention, if required, during Litigation and Other Proceedings

The Trustees would like to receive community input by 9 May for its
consideration.

The Draft policy dated 23 March 2016 is located here:
http://trustee.ietf.org/policies-and-procedures.html  

There is also a Diff file reflecting the proposed changes in 2016.

Comments should be sent to trustees@ietf.org.

Thanks

Ray
Trustee
IETF Administrative Director


From nobody Tue Apr 26 13:30:08 2016
Return-Path: <adrian@olddog.co.uk>
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 C27FB12D56C; Tue, 26 Apr 2016 13:30:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.62
X-Spam-Level: 
X-Spam-Status: No, score=-2.62 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01] 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 aW84XjF_vTJu; Tue, 26 Apr 2016 13:30:02 -0700 (PDT)
Received: from asmtp4.iomartmail.com (asmtp4.iomartmail.com [62.128.201.175]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0A6A712D0A6; Tue, 26 Apr 2016 13:30:01 -0700 (PDT)
Received: from asmtp4.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp4.iomartmail.com (8.13.8/8.13.8) with ESMTP id u3QKS4c9011010; Tue, 26 Apr 2016 21:28:04 +0100
Received: from 950129200 (jplon-nat14.juniper.net [193.110.55.14]) (authenticated bits=0) by asmtp4.iomartmail.com (8.13.8/8.13.8) with ESMTP id u3QKS302010990 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO); Tue, 26 Apr 2016 21:28:04 +0100
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: <ietf@ietf.org>
References: <20160419141640.31545.54742.idtracker@ietfa.amsl.com> 
In-Reply-To: 
Subject: RE: Last Call: <draft-leiba-cotton-iana-5226bis-12.txt> (Guidelines for Writing an IANA Considerations Section in RFCs) to Best Current Practice
Date: Tue, 26 Apr 2016 21:28:02 +0100
Message-ID: <057701d19ffa$2291b5b0$67b52110$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQD6sjSRIIB+2MCyMyZ0rhhMk0byWqFCSc7AgAhB+rA=
Content-Language: en-gb
X-TM-AS-MML: disable
X-TM-AS-Product-Ver: IMSS-7.1.0.1679-8.0.0.1202-22286.002
X-TM-AS-Result: No--11.377-10.0-31-10
X-imss-scan-details: No--11.377-10.0-31-10
X-TMASE-MatchedRID: 9zTThWtzImtfsB4HYR80ZggKAWhuC2ojb6bRSg4rpzvM7zpEspqG/yQK VkaL89O9Wvpt4uqyaUEcPMPBmVk68HmKI6b62ffnUSn3o+eoUmzDHSNFHFxB81vym/gvSH4iakc q2RAHKcqD67iPeqoD/gSmL1+CJjGb8P4Bf0DnMRuMVQb49Y23I4LsLasl5ROhxaQNbiRXdZoDkd 7WQNL44uLzNWBegCW2XC3N7C7YzrfkwjHXXC/4IzsAVzN+Ov/sBvOTRKyP23fRw3LGe3O6GsTsE Q2p7sMrzOcn9pmdN6KtnlQyvBfVYw==
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/MtU6cutG8UoAvVZeoft23pxtOGU>
Cc: draft-leiba-cotton-iana-5226bis@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: adrian@olddog.co.uk
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: Tue, 26 Apr 2016 20:30:07 -0000

Hi,

A couple of further thoughts arising from the discussions on the WG chairs'
mailing list (but not claiming the opinions as other than my own).

Section 4.4
Aim to set the expectations of consumers better (and fix the grammar) by...
OLD
 For numbers, the exact
 value is generally assigned by IANA; with names, specific text
   strings can usually be requested.
NEW:
 For numbers, IANA generally assigns the next in-sequence unallocated
 value, but other values may be requested and assigned if an extenuating
 circumstance exists.  With names, specific text strings can usually be
 requested.
END

Section 6
Include hint on best practice for top and bottom of ranges.
OLD
     Reserved: Not assigned and not available for assignment.  Reserved
           values are held for special uses, such as to extend the
           namespace when it becomes exhausted.  Note that this is
           distinctly different from "Unassigned".
NEW
     Reserved: Not assigned and not available for assignment.  Reserved
           values are held for special uses, such as to extend the
           namespace when it becomes exhausted.  Note that this is
           distinctly different from "Unassigned".

          It is common practice for documents that define numeric registries
          to mark the zero value as "Reserved" because this often aids protocol 
          implementations.  It is also common practice to mark the maximum
          value as "Reserved" so that it can be used as part of a strategy to
          extend the registry if the range proves too small in the future.
END

Thanks,
Adrian


From nobody Tue Apr 26 16:47:15 2016
Return-Path: <brian.e.carpenter@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 537DD12D1AE; Tue, 26 Apr 2016 16:47:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 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, RCVD_IN_DNSWL_LOW=-0.7, 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 nKw79ufzHNAV; Tue, 26 Apr 2016 16:47:13 -0700 (PDT)
Received: from mail-pf0-x22f.google.com (mail-pf0-x22f.google.com [IPv6:2607:f8b0:400e:c00::22f]) (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 0958B12D10D; Tue, 26 Apr 2016 16:47:13 -0700 (PDT)
Received: by mail-pf0-x22f.google.com with SMTP id y69so12906392pfb.1; Tue, 26 Apr 2016 16:47:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=subject:to:references:cc:from:organization:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=pKSwkUvG060MFRYWcvwSHpo+enBIr5nXY6ATGj/w+6k=; b=e4sLS0zobt4xCxaCqZSLM4niZF9JflZaFRY0Lj/edo5UigOPsuzZ8hnrWdv7MMv7sI YTpiIRoAV49A7WWZTRYfFTAWx3d9ERllBrUbB/sqAZJfXWkW5gRaIoq6VMydAYIrgmBZ gsY+gBTKf1fVvA64kDZ65cvQqKVknnT0LUYkOXFy2+6kiDvFeVWbLXBtpNE7gMlDzexI y7zuCZCTMjnn1Pxhq60EbRHpJOIGcGabEiDlZbwxCyQ+yJrRoh3FZm/nPIvEbbbVXAf2 YLpSm0MsOZ2mx5uLfxeLC7juNbAIMk28b82yjKRyMc5tk7TjomCI+YgK3/7w698q8xpT cOow==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:cc:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=pKSwkUvG060MFRYWcvwSHpo+enBIr5nXY6ATGj/w+6k=; b=RKVaJ84tE2iBGbsk6H4bi2U7d1j2QCv2Jfap269PF91oLtDmdZRKlWX+LS/4Hmv/Mx TFp4ipy+LEN82qvVE/JfEACvkjKfN9Zy34JI/hGjLpqvcf1gm8lmI9SagOQCK5pv9rRv x5B4OeEJGrKK78NgbvkKaVNN+yySuIfLrMWDliUYPKN/ZVAepRus7iyIfDHtzvkciFxW garHGU5GMCVWmJ1bmzbRk8lcd/GsTtRbpkJ+4uYfZs25UpGVLoUs8FAYY5t1nXaVITgU 3Ly7osLtH4SIRWtisVc5AijB+TIiqAW4YqAc3V6EROCzG/S892YAmsd13K9OT6RXD4u8 fXUg==
X-Gm-Message-State: AOPr4FVnFuF91pcVNiG20BSAjPqV3t8zqHYcc8VTwFOCi7FkTvcNZRKGDqY9gXtm6zE9fw==
X-Received: by 10.98.32.211 with SMTP id m80mr7532107pfj.3.1461714432610; Tue, 26 Apr 2016 16:47:12 -0700 (PDT)
Received: from ?IPv6:2406:e007:79e1:1:28cc:dc4c:9703:6781? ([2406:e007:79e1:1:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id q72sm998441pfa.70.2016.04.26.16.47.09 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 26 Apr 2016 16:47:11 -0700 (PDT)
Subject: Re: Last Call: <draft-leiba-cotton-iana-5226bis-12.txt> (Guidelines for Writing an IANA Considerations Section in RFCs) to Best Current Practice
To: adrian@olddog.co.uk, ietf@ietf.org
References: <20160419141640.31545.54742.idtracker@ietfa.amsl.com> <057701d19ffa$2291b5b0$67b52110$@olddog.co.uk>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <44038e4c-d177-3f06-7f40-dd82cbd86a99@gmail.com>
Date: Wed, 27 Apr 2016 11:47:14 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.0
MIME-Version: 1.0
In-Reply-To: <057701d19ffa$2291b5b0$67b52110$@olddog.co.uk>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/uYuA7DzmwdeOYxrRNvpm-_w2yKA>
Cc: draft-leiba-cotton-iana-5226bis@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: Tue, 26 Apr 2016 23:47:14 -0000

On 27/04/2016 08:28, Adrian Farrel wrote:
...
> Section 6
> Include hint on best practice for top and bottom of ranges.
> OLD
>      Reserved: Not assigned and not available for assignment.  Reserved
>            values are held for special uses, such as to extend the
>            namespace when it becomes exhausted.  Note that this is
>            distinctly different from "Unassigned".
> NEW
>      Reserved: Not assigned and not available for assignment.  Reserved
>            values are held for special uses, such as to extend the
>            namespace when it becomes exhausted.  Note that this is
>            distinctly different from "Unassigned".
> 
>           It is common practice for documents that define numeric registries
>           to mark the zero value as "Reserved" because this often aids protocol 
>           implementations.

I'm not sure about the "because" clause. It sounds a bit like an excuse for
sloppy coding. Defining it explicitly as a no-op would seem like better
practice in many cases.

   Brian

>           It is also common practice to mark the maximum
>           value as "Reserved" so that it can be used as part of a strategy to
>           extend the registry if the range proves too small in the future.
> END
> 
> Thanks,
> Adrian
> 
> 


From nobody Wed Apr 27 02:57:47 2016
Return-Path: <chair@ietf.org>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from [192.168.1.192] (37-219-219-243.nat.bb.dnainternet.fi [37.219.219.243]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPSA id 6E47112D643; Wed, 27 Apr 2016 02:57:40 -0700 (PDT)
Content-Type: text/plain; charset=windows-1252
Subject: IETF-95 summary articles
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: IETF Chair <chair@ietf.org>
Date: Wed, 27 Apr 2016 12:57:37 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <E2BDE0D2-05FB-4D27-8FEF-57CF27C03F37@ietf.org>
To: IETF Announcement List <ietf-announce@ietf.org>, 95all@ietf.org
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/MUTdgdDyhK0gDl-bFUQnX9lOW7o>
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: IETF <ietf@ietf.org>, chair@ietf.org
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, 27 Apr 2016 09:57:44 -0000

Thank you all for the meeting we had a couple of weeks ago in Buenos =
Aires! Here are some thoughts from me about the meeting and discussion =
topics:

   https://www.ietf.org/blog/2016/04/ietf-95-summary/

I have also included some pointers to other materials, including for =
instance: Un resumen de la reuni=F3n (Alvaro Retana): =
https://youtu.be/Yq6u1fc8VXo, Nick Sullivan=92s description of his =
team=92s work on TLS1.3 at the Hackathon: =
https://www.ietf.org/blog/2016/04/ietf-hackathon-getting-tls-1-3-working-i=
n-the-browser/ and others.

Jari Arkko
IETF Chair


From nobody Wed Apr 27 06:02:08 2016
Return-Path: <klieforth@isoc.org>
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 BDA8712D14B; Wed, 27 Apr 2016 06:02:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.903
X-Spam-Level: 
X-Spam-Status: No, score=-1.903 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=isoc.onmicrosoft.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 YaKzRgaRBZjo; Wed, 27 Apr 2016 06:02:05 -0700 (PDT)
Received: from na01-by2-obe.outbound.protection.outlook.com (mail-by2on0092.outbound.protection.outlook.com [207.46.100.92]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EA75C12D158; Wed, 27 Apr 2016 06:02:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=isoc.onmicrosoft.com;  s=selector1-isoc-org; h=From:To:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=tcO2QqplGMIZI9J0YjytHCWm5lZgXC4aj81Efw6SGtQ=; b=G0waWHEOB3+XFXc69qIqg5MJ0E9mRL/dplj4z4lX0DwhxY8QO8CiGyKJPXNeYhsMXUAOx/aIEjjRj9MP1RHLQo6fsCK1mPIUknoK6JeNqGYVRHcD0RPNtzb/0QSJ7T8i3o8c4ADEdDbE0kaEM8yQ5olw2GKC/D8FzcxGh9Cvy1I=
Received: from BLUPR06MB257.namprd06.prod.outlook.com (10.141.22.13) by BLUPR06MB260.namprd06.prod.outlook.com (10.141.22.27) with Microsoft SMTP Server (TLS) id 15.1.466.19; Wed, 27 Apr 2016 13:02:04 +0000
Received: from BLUPR06MB257.namprd06.prod.outlook.com ([169.254.13.88]) by BLUPR06MB257.namprd06.prod.outlook.com ([169.254.13.88]) with mapi id 15.01.0477.012; Wed, 27 Apr 2016 13:02:03 +0000
From: Linda Klieforth <klieforth@isoc.org>
To: IETF <ietf@ietf.org>, IETF Chair <chair@ietf.org>
Subject: Re: [95all] IETF-95 summary articles
Thread-Topic: [95all] IETF-95 summary articles
Thread-Index: AQHRoGuBSUFjfU/JOUmzoWaKGyHKjZ+dhhgA
Date: Wed, 27 Apr 2016 13:02:03 +0000
Message-ID: <7D4B83C8-742B-49EF-8710-4D8A614153EB@isoc.org>
References: <E2BDE0D2-05FB-4D27-8FEF-57CF27C03F37@ietf.org>
In-Reply-To: <E2BDE0D2-05FB-4D27-8FEF-57CF27C03F37@ietf.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=isoc.org;
x-ms-exchange-messagesentrepresentingtype: 1
x-originating-ip: [2001:4870:400e:402:ccfb:d814:3a42:6087]
x-ms-office365-filtering-correlation-id: 8c4f185b-cebc-464c-2331-08d36e9c2103
x-microsoft-exchange-diagnostics: 1; BLUPR06MB260; 5:t4AhnEC8l2P3TxOv7XyjZMj6daN5KnsHx6gyT6VdHPqi+ei5KEj0HwiyWE7FqkCFhalV7dvbjtBBzXXx1pg0+Lgw68MIvko+0LK3dkfynHJr2VbZmuHRWAbKqfowIRhNqpfAwXuLdqOqqsp903BcVdiffThRXPTn/4LJIFvyVzPsN7sjtDCPTPyB8Y1ph96I; 24:LBq7ATlqp0WYx4VUBs0Mzax5w9qB/o+UYLTzQ2t5acZWN/UtUDrUnWJFLbyq6fcvdKU2oV8ZRmqELg6Y/T3EAoAlgZVI5IlC6BwCKO2wRXA=; 7:Bowl6wGsXscy2nIkbdvx+M+xRPMNuBcgB2IFoB+soPfq1OZ9fxAXe5ukUv5y64zMAOYXc92H3coLUnciw0hn7dEANmiX7LiClmURY9MrPCNM5QTazwIAq01Wnt9Y4VEI65fcPzQo0QK1SMtKCy26ATMjz5nM74NNbqaCfZu+s87ZXFvxG0q2mlaiDk2ayVYjr5bOT2iw6XJZBEBXwZAdNv2pjOssRHgh8FNYybLepR0=
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:BLUPR06MB260;
x-ld-processed: 89f84dfb-7285-4810-bc4d-8b9b5794554f,ExtAddr
x-microsoft-antispam-prvs: <BLUPR06MB26066EEEA44D003B8ED82D1D4640@BLUPR06MB260.namprd06.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(601004)(2401047)(8121501046)(5005006)(3002001)(10201501046); SRVR:BLUPR06MB260; BCL:0; PCL:0; RULEID:; SRVR:BLUPR06MB260; 
x-forefront-prvs: 0925081676
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(6009001)(24454002)(377454003)(23363002)(107886002)(189998001)(5001770100001)(6116002)(586003)(102836003)(5002640100001)(2906002)(15975445007)(36756003)(106116001)(450100001)(33656002)(86362001)(1096002)(92566002)(1220700001)(122556002)(99286002)(19580405001)(3280700002)(87936001)(10400500002)(54356999)(76176999)(83716003)(5008740100001)(50986999)(19580395003)(5004730100002)(82746002)(2900100001)(2950100001)(81166005)(3660700001)(3826002)(104396002); DIR:OUT; SFP:1101; SCL:1; SRVR:BLUPR06MB260; H:BLUPR06MB257.namprd06.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en; 
spamdiagnosticoutput: 1:23
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
Content-ID: <5C21264032270149BEDE9DA75F3604C2@namprd06.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: isoc.org
X-MS-Exchange-CrossTenant-originalarrivaltime: 27 Apr 2016 13:02:03.5151 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 89f84dfb-7285-4810-bc4d-8b9b5794554f
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BLUPR06MB260
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/ZAsxsv7pEtachFh1_PiB4I0XYqI>
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, 27 Apr 2016 13:02:06 -0000

R3JlYXQsIHRoYW5rcw0KDQoNCg0KDQpPbiA0LzI3LzE2LCA1OjU3IEFNLCAiOTVhbGwgb24gYmVo
YWxmIG9mIElFVEYgQ2hhaXIiIDw5NWFsbC1ib3VuY2VzQGlldGYub3JnIG9uIGJlaGFsZiBvZiBj
aGFpckBpZXRmLm9yZz4gd3JvdGU6DQoNCj5UaGFuayB5b3UgYWxsIGZvciB0aGUgbWVldGluZyB3
ZSBoYWQgYSBjb3VwbGUgb2Ygd2Vla3MgYWdvIGluIEJ1ZW5vcyBBaXJlcyEgSGVyZSBhcmUgc29t
ZSB0aG91Z2h0cyBmcm9tIG1lIGFib3V0IHRoZSBtZWV0aW5nIGFuZCBkaXNjdXNzaW9uIHRvcGlj
czoNCj4NCj4gICBodHRwczovL3d3dy5pZXRmLm9yZy9ibG9nLzIwMTYvMDQvaWV0Zi05NS1zdW1t
YXJ5Lw0KPg0KPkkgaGF2ZSBhbHNvIGluY2x1ZGVkIHNvbWUgcG9pbnRlcnMgdG8gb3RoZXIgbWF0
ZXJpYWxzLCBpbmNsdWRpbmcgZm9yIGluc3RhbmNlOiBVbiByZXN1bWVuIGRlIGxhIHJldW5pw7Nu
IChBbHZhcm8gUmV0YW5hKTogaHR0cHM6Ly95b3V0dS5iZS9ZcTZ1MWZjOFZYbywgTmljayBTdWxs
aXZhbuKAmXMgZGVzY3JpcHRpb24gb2YgaGlzIHRlYW3igJlzIHdvcmsgb24gVExTMS4zIGF0IHRo
ZSBIYWNrYXRob246IGh0dHBzOi8vd3d3LmlldGYub3JnL2Jsb2cvMjAxNi8wNC9pZXRmLWhhY2th
dGhvbi1nZXR0aW5nLXRscy0xLTMtd29ya2luZy1pbi10aGUtYnJvd3Nlci8gYW5kIG90aGVycy4N
Cj4NCj5KYXJpIEFya2tvDQo+SUVURiBDaGFpcg0KPg0KPl9fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fDQo+OTVhbGwgbWFpbGluZyBsaXN0DQo+OTVhbGxAaWV0
Zi5vcmcNCj5odHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvLzk1YWxsDQo=


From nobody Wed Apr 27 06:02:31 2016
Return-Path: <klieforth@isoc.org>
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 DF9F912D168; Wed, 27 Apr 2016 06:02:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.903
X-Spam-Level: 
X-Spam-Status: No, score=-1.903 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=isoc.onmicrosoft.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 La0fBzUlwF67; Wed, 27 Apr 2016 06:02:26 -0700 (PDT)
Received: from na01-by2-obe.outbound.protection.outlook.com (mail-by2on0077.outbound.protection.outlook.com [207.46.100.77]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 63FF612D166; Wed, 27 Apr 2016 06:02:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=isoc.onmicrosoft.com;  s=selector1-isoc-org; h=From:To:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=vMmyS+JGJrlOn+YqKeKDK0Av996lnNaLTqpvZonFrV8=; b=J/vwQ0PRYDg9LuXmZw6GOoIdSMPKb5u5GxtCjlmamlR1jPdsw7oAkKkGxgueH9iepWkG7jd+nabXJDCdgjgPAANIo5Y6X68YXknuOGf/0aJlZ33Pudg1vMFzGORh/A6qlAarVydT6H6ilBa5ftl0Ak4sZnc+Fjy+5AMq407y1JA=
Received: from BLUPR06MB257.namprd06.prod.outlook.com (10.141.22.13) by BLUPR06MB260.namprd06.prod.outlook.com (10.141.22.27) with Microsoft SMTP Server (TLS) id 15.1.466.19; Wed, 27 Apr 2016 13:02:25 +0000
Received: from BLUPR06MB257.namprd06.prod.outlook.com ([169.254.13.88]) by BLUPR06MB257.namprd06.prod.outlook.com ([169.254.13.88]) with mapi id 15.01.0477.012; Wed, 27 Apr 2016 13:02:24 +0000
From: Linda Klieforth <klieforth@isoc.org>
To: IETF <ietf@ietf.org>, IETF Chair <chair@ietf.org>
Subject: Re: [95all] IETF-95 summary articles
Thread-Topic: [95all] IETF-95 summary articles
Thread-Index: AQHRoGuBSUFjfU/JOUmzoWaKGyHKjZ+dhjGA
Date: Wed, 27 Apr 2016 13:02:24 +0000
Message-ID: <C2BFFA65-F8A0-4AE5-8608-84290D0BD97B@isoc.org>
References: <E2BDE0D2-05FB-4D27-8FEF-57CF27C03F37@ietf.org>
In-Reply-To: <E2BDE0D2-05FB-4D27-8FEF-57CF27C03F37@ietf.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=isoc.org;
x-ms-exchange-messagesentrepresentingtype: 1
x-originating-ip: [2001:4870:400e:402:ccfb:d814:3a42:6087]
x-ms-office365-filtering-correlation-id: 13d5b804-134a-47e5-b20f-08d36e9c2d84
x-microsoft-exchange-diagnostics: 1; BLUPR06MB260; 5:tS45bCb818Q8OMcBflDHTYFKsI1MHdhnyj6tFAq+nZdRGYYu7dB7hltMyH7vXAD42DNt9qOzIYmZuMcQCTGgyfee2WRFVmQrAqZ0/w/RI4squsD1VhmN1QIaOqQoNjBI8fJwnA99fq6KZpoV9ULLh/0YYa+fyZmUbSdFWKllTjM1AYWBA5/QHvuYfNA0u4rR; 24:KO9NMLNmrxAE70ciL0f59L6kSU5INHzbqdIODXFZJydviHVF2zWRvpNh5rwk4TV1/o71Mzfb5Z1lDgaCaBCyOsJL+eVkDHaWA1jY/zqOklk=; 7:jV5QKqgbd8UDiTvK9mGqOmjkp8ngKUi2rveTRSIXuCGhXx/2JVY7mRE/f55en0M9tb89PxXQETaJfaaTDs6D7k9Tzy5cSn8uauPwtwOlTwPety2D9Vo53xQO+C8Xh0ioDfH0b3oQflJdre1pD+yVOwi8hsm2/sLkDFkmot57OeqaV4ianhP0tmq/s2ybkPlKkK+3CZw7RQhCCBih4Y3jO4FCM7lxDODg318+MSPDTF8=
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:BLUPR06MB260;
x-ld-processed: 89f84dfb-7285-4810-bc4d-8b9b5794554f,ExtAddr
x-microsoft-antispam-prvs: <BLUPR06MB2605FBD928C5EE89AC13576D4640@BLUPR06MB260.namprd06.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(601004)(2401047)(8121501046)(5005006)(3002001)(10201501046); SRVR:BLUPR06MB260; BCL:0; PCL:0; RULEID:; SRVR:BLUPR06MB260; 
x-forefront-prvs: 0925081676
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(6009001)(24454002)(377454003)(23363002)(107886002)(189998001)(5001770100001)(6116002)(586003)(102836003)(5002640100001)(2906002)(15975445007)(36756003)(106116001)(450100001)(33656002)(86362001)(1096002)(92566002)(1220700001)(122556002)(99286002)(19580405001)(3280700002)(87936001)(10400500002)(54356999)(76176999)(83716003)(5008740100001)(50986999)(19580395003)(5004730100002)(82746002)(2900100001)(2950100001)(81166005)(3660700001)(3826002)(104396002); DIR:OUT; SFP:1101; SCL:1; SRVR:BLUPR06MB260; H:BLUPR06MB257.namprd06.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en; 
spamdiagnosticoutput: 1:23
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
Content-ID: <5C67B81B93F9AD4CB66F2F6913B1FF2C@namprd06.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: isoc.org
X-MS-Exchange-CrossTenant-originalarrivaltime: 27 Apr 2016 13:02:24.4344 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 89f84dfb-7285-4810-bc4d-8b9b5794554f
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BLUPR06MB260
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/HGdErCai2kdM_W4b8yQanXVxYBM>
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, 27 Apr 2016 13:02:29 -0000

R3JlYXQsIHRoYW5rcy4NCg0KDQoNCg0KT24gNC8yNy8xNiwgNTo1NyBBTSwgIjk1YWxsIG9uIGJl
aGFsZiBvZiBJRVRGIENoYWlyIiA8OTVhbGwtYm91bmNlc0BpZXRmLm9yZyBvbiBiZWhhbGYgb2Yg
Y2hhaXJAaWV0Zi5vcmc+IHdyb3RlOg0KDQo+VGhhbmsgeW91IGFsbCBmb3IgdGhlIG1lZXRpbmcg
d2UgaGFkIGEgY291cGxlIG9mIHdlZWtzIGFnbyBpbiBCdWVub3MgQWlyZXMhIEhlcmUgYXJlIHNv
bWUgdGhvdWdodHMgZnJvbSBtZSBhYm91dCB0aGUgbWVldGluZyBhbmQgZGlzY3Vzc2lvbiB0b3Bp
Y3M6DQo+DQo+ICAgaHR0cHM6Ly93d3cuaWV0Zi5vcmcvYmxvZy8yMDE2LzA0L2lldGYtOTUtc3Vt
bWFyeS8NCj4NCj5JIGhhdmUgYWxzbyBpbmNsdWRlZCBzb21lIHBvaW50ZXJzIHRvIG90aGVyIG1h
dGVyaWFscywgaW5jbHVkaW5nIGZvciBpbnN0YW5jZTogVW4gcmVzdW1lbiBkZSBsYSByZXVuacOz
biAoQWx2YXJvIFJldGFuYSk6IGh0dHBzOi8veW91dHUuYmUvWXE2dTFmYzhWWG8sIE5pY2sgU3Vs
bGl2YW7igJlzIGRlc2NyaXB0aW9uIG9mIGhpcyB0ZWFt4oCZcyB3b3JrIG9uIFRMUzEuMyBhdCB0
aGUgSGFja2F0aG9uOiBodHRwczovL3d3dy5pZXRmLm9yZy9ibG9nLzIwMTYvMDQvaWV0Zi1oYWNr
YXRob24tZ2V0dGluZy10bHMtMS0zLXdvcmtpbmctaW4tdGhlLWJyb3dzZXIvIGFuZCBvdGhlcnMu
DQo+DQo+SmFyaSBBcmtrbw0KPklFVEYgQ2hhaXINCj4NCj5fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fXw0KPjk1YWxsIG1haWxpbmcgbGlzdA0KPjk1YWxsQGll
dGYub3JnDQo+aHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby85NWFsbA0K


From nobody Wed Apr 27 10:02:47 2016
Return-Path: <daedulus@btconnect.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 0114712D9CE; Wed, 27 Apr 2016 10:02:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=btconnect.onmicrosoft.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 XpVoZZxE-Hy0; Wed, 27 Apr 2016 10:02:43 -0700 (PDT)
Received: from emea01-db3-obe.outbound.protection.outlook.com (mail-db3on0781.outbound.protection.outlook.com [IPv6:2a01:111:f400:fe04::781]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 303EA12D973; Wed, 27 Apr 2016 10:02:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=btconnect.onmicrosoft.com; s=selector1-btconnect-com; h=From:To:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=TBmZvVehBz6wHNz1wPAudxdhrSjqjLmQmzDH115doXo=; b=RoLpv43kktmSShU8/GQOffigpUFZScCDQoIy8xPiSZdllHSacjJOHUMV/aLnP1uVO1emtYnVezuXqPEGE/U87Rvx81+r6XjLr5DjBekjIMUoz/+8lugeoGzT1czJyOi80DfEHsOUEqah+nKvYSC684SIEMsmnaXSVJWmNzu9BNQ=
Authentication-Results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=btconnect.com;
Received: from pc6 (81.159.99.181) by VI1PR07MB1567.eurprd07.prod.outlook.com (10.165.239.13) with Microsoft SMTP Server (TLS) id 15.1.477.8; Wed, 27 Apr 2016 17:02:16 +0000
Message-ID: <00a801d1a0a6$14f26420$4001a8c0@gateway.2wire.net>
From: tom p. <daedulus@btconnect.com>
To: <ietf@ietf.org>
References: <20160415175827.17486.53218.idtracker@ietfa.amsl.com>
Subject: Re: Last Call: <draft-ietf-i2rs-pub-sub-requirements-05.txt> (Requirements for Subscription to YANG Datastores) to Proposed Standard
Date: Wed, 27 Apr 2016 17:55:20 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Originating-IP: [81.159.99.181]
X-ClientProxiedBy: DB3PR08CA0031.eurprd08.prod.outlook.com (10.161.51.169) To VI1PR07MB1567.eurprd07.prod.outlook.com (10.165.239.13)
X-MS-Office365-Filtering-Correlation-Id: 61565faf-2e47-43c3-af88-08d36ebdb038
X-Microsoft-Exchange-Diagnostics: 1; VI1PR07MB1567; 2:EM1Q6lhNdDOn0EJ0RyfK7sgQ59pZ9RcGjptbqXy6qGSDWGCTyKrfTdxsVGBi4RUgLXTvTTjyPt9A+knKXMrnRHrxo3THQXsbhAGXvd1tyWRpAfMnVqPHtl6BFPg+a5/dbmRY2Z7xzH71kcAorTEoMynlZTsDsIBHnvskTTAj81gN9ljQgoWDEW2L+eihZ42a; 3:u0zLRfjg1M/smeTUqg9EaAM+/G/jTj9xWDG9z65ONP0xTSjKLLXe9dtet/LKdB7cjbbRWwz6EnTp9jpp3ax4AbWufcfntMPuaBsvJC+uwLMtyqeH2wfiZBO0gDby82u3
X-Microsoft-Antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:VI1PR07MB1567;
X-Microsoft-Exchange-Diagnostics: 1; VI1PR07MB1567; 25:KByqurePIGkGzqYv1ue10wMlPR8O8vW3dypEso1iO/ExppRjbiLVJbR2FDMh+2571Qkr4zasH6FlYZqcX9GMoEt4fxv7C0U+a6berH4Zci2eChp0qEuApFwFPu4GkteQ5NumFyQ1Oakh4ceSeGO2PA9lz99KQZ/MpGuI1D6eMdSUGhIEQ2tz9mAVsqBe1loGtGP+sUk9X77xM3AKwnrPfWGhZLG5qtHOx4HNAOob13OPKskxGgyn6KB7r9xcPf84dk7vNyUc56dzaGpcVQ5l24py52qONSDb0RIy1/iw/b0zgBpoWl2dZWErA/C40JN1z+LhVhlrRdtYTr32ipAYP2K3w94dwVMcseOPPU0ja4butAfkt2U6plR5i+eJB6DJslnup28xumK7HxnLAHLa2MVEUut85901vLsoUuSpn004rOjKTl7xABl5Ych9u61Vh4ZqcvEsZa218hp8K45efxUSA35RzYmOO9vJ0BrfrpBXEHB8KBSZef4KxfHWeCj9AGMJq5alaOofL16wRCEHfii5tCPiZkEa7630gA06cl07c+l3rcmqNfhAsSMHW2U5eH+tV0o4kk/RcvxC4DprhEfl5fB2PTqGOgfFwhz4w4QH4+DF8OH2NtxIjiqBJSHUJBR5Xkr5nR3casivVH5MaB4kIrtzNqB5PwMIWHfwu1OgJwMccfiakYLcTY994E4w5WWQKIMReMahNCqzQA+q9iC5tWsWEhX2IwhJhIKrrIOVlGKpLF9qz/Bc3vE4eaWm
X-Microsoft-Antispam-PRVS: <VI1PR07MB1567791BF156EC924B74260BC6640@VI1PR07MB1567.eurprd07.prod.outlook.com>
X-Exchange-Antispam-Report-Test: UriScan:;
X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(9101521072)(601004)(2401047)(5005006)(8121501046)(10201501046)(3002001); SRVR:VI1PR07MB1567; BCL:0; PCL:0; RULEID:; SRVR:VI1PR07MB1567; 
X-Microsoft-Exchange-Diagnostics: 1; VI1PR07MB1567; 4:bNnR27Wgbgpt1RpbUO2aGxmR+8pJGkfI7RqHDBg0zAqj8I9pSmMgwdjCd/MXKrEp398JczFUA7vYNXWpFk0b1hOQ9ErSyopCu1kEmfEZsw/+HOH1zencrzxI5JzKepWEN3J94RWtdRCUiU2RfSeU40oVKH8NfU2ZGRvo9NvmXGpHoYjOvpdJkhmcxiF7L5mUKdhb/MoVX5Ak8U6IeCRI3sYrdkZrhODYgKSgXJ/Q0dhfh3GYm2Fvlpg08VaVgoYfoy+DdIWZ2NCXo5nrWu3V2QT46X3SoESe1ObIdPv/blhaeIthr0PkS9IfGoEU8LNAU8poRiU/XlWHKr11hjZmFfofqW3xMcuxAvoeUBxuZ7z6AYtRSZ9EGdKvbOQxMSpMYFxhIC6zQs4sdpGtsGhZSw==
X-Forefront-PRVS: 0925081676
X-Forefront-Antispam-Report: SFV:NSPM; SFS:(10019020)(4630300001)(6009001)(13464003)(377454003)(15975445007)(33646002)(1096002)(1556002)(77096005)(62236002)(50226002)(5004730100002)(6116002)(230700001)(2351001)(9686002)(61296003)(14496001)(110136002)(230783001)(92566002)(50986999)(76176999)(42186005)(1456003)(189998001)(81816999)(81686999)(84392002)(66066001)(4326007)(50466002)(5008740100001)(3846002)(44716002)(19580405001)(19580395003)(586003)(2906002)(23756003)(47776003)(81166005)(4720700001); DIR:OUT; SFP:1102; SCL:1; SRVR:VI1PR07MB1567; H:pc6; FPR:; SPF:None; MLV:sfv;  LANG:en; 
X-Microsoft-Exchange-Diagnostics: =?iso-8859-1?Q?1; VI1PR07MB1567; 23:FNZursexetUT7kLmYjTc8/8qXLXRlnEp+wdBeQg?= =?iso-8859-1?Q?Pwk+wZhN5z9UL0YVHKexnMQl6szcVy2P0hxb8UtBNPzNnZJKem91ZbocsJ?= =?iso-8859-1?Q?1IAd/TfPmQeE+CPo1BpUqfrCODFgNDyYZSzTiyLPksVnh2fu583poPMHg7?= =?iso-8859-1?Q?+7MT/T3/TXfKn1xFE0vnMsoQaX96fJVVxzHtkKnm/Ju9Vndxw2hO1ku45a?= =?iso-8859-1?Q?h4VNvCRRYcdY3CYIIAAzCMlUA6a/8eMNKiUaBwEUyay1eVUENKznCNLynE?= =?iso-8859-1?Q?M1GBJcEBs4zZoGQPJ6dfuFDAtuE1MckEyGUDkEr+56p1aQQuO99dFLZ2N8?= =?iso-8859-1?Q?F+MD04r8WtgCyKx7C/m6oYaZaiR1x3RMh+d7GFm9JuusPoc4lWqB4kfJLl?= =?iso-8859-1?Q?RcLi8p8FxEsjLtUlECI+MMNCfDkp8xpAqBYprrdchwmibkfHASUF/9n+CD?= =?iso-8859-1?Q?sASGX4kJHHVlaNMDH7BcMXACcKD/MMt9NWWYBZq/DGIUDeMMz9oQQtV6Yi?= =?iso-8859-1?Q?E8FWU0r/EKuAJkAQByDy0x8OrWt83oEbd1ILc53GgWeShfjbcRyS55ptQ5?= =?iso-8859-1?Q?is95ArLwy13NXsbJ/8RaVazN3F7rmylbhRLA7yW4wher9FdAjA+l/vcdPD?= =?iso-8859-1?Q?vd+oI0JRu0LaJuMqp6qWcF6K0LAgJiKc6/NXBF7YN0ALBeiscpPXPxATsX?= =?iso-8859-1?Q?hY6sOwdPA1+3YyRgewVy7WtGJV8bQSU+4Su2StCQrr7uC+etSh08CrIpW3?= =?iso-8859-1?Q?BSFGIpanLAT93xeTF3MqywSKSGQz66OSmnw/7a9pSePwLUmQ2zcc/bxGWy?= =?iso-8859-1?Q?IZCRUxPhcRrnkpSZ/2QK7WAz87HZy5rCtr6FRO0XiunQ8IDM3PzHkvOFJR?= =?iso-8859-1?Q?hKzoVIN7CWk6J4OcStXEHfc3/sEJEb5dRzNMV7FtN8WgLPxzKJOF4zZBk/?= =?iso-8859-1?Q?mJ9XaRph9Gkv6dJ8TnxZB/K/FOF4t/9XG0wOy6OuArLNSuMVJuO00iK7vL?= =?iso-8859-1?Q?TGun3Az4QCuoU2gWP1Xn7wIGFtsWKxpAZBRCHQFBoqms9OGliSGSUDhFff?= =?iso-8859-1?Q?sD6zJtBbBh1kMMd/sYR0QCAiWfbESZSbuTNaB04yplA63FohXuZNNfPR5M?= =?iso-8859-1?Q?PLaYTsRerZU0AJ5MV0JVbNBoEqdPEYH4B/kkbBzcWr7sCVVo=3D?=
X-Microsoft-Exchange-Diagnostics: 1; VI1PR07MB1567; 5:h+xv5KQuVhQK1kNbh3sWeQJpnzGimaaGu4ZG0utJ4gCIw2ygR0WbvpVZtGJdr2mZsBf1ogVJvr2eB0GdCt/5TxVzwOntZ7AXTlgK+KuabNlmGrKVM8opjzAxzYFbP6+VwRFJ6nISpttDWOmTfsiB6Q==; 24:T3+vODn25TgiTPgX1loLw3G4aO32xCpK/4d6WyWkyK5DCu2i/gV4iae9Sy598UzHX6dc7HcKxgUJd24SBOEPXKbuLj/EpAT3makmuODbp+M=; 7:0xkoBqOcNNY9Urc9Y3ME3llpgFtA/WbcS3i7rnnig7Mnu3kDGfD4cmwoX0Jtbyw3N/Y+Z7NpFtVS8hFF43ofSucUP7znHE7IkmY6gPQNy3g5LDJU2JfjGrUjk+POt26KfDn9gBtY9YOKGXi86nDGR52UCoavHriArquAq945vFIdMXrldo/OU9nelv1dRes6
SpamDiagnosticOutput: 1:23
SpamDiagnosticMetadata: NSPM
X-OriginatorOrg: btconnect.com
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 27 Apr 2016 17:02:16.7813 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-Transport-CrossTenantHeadersStamped: VI1PR07MB1567
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/_G889XecGKgC-9SAF6ukoVP4VsE>
Cc: draft-ietf-i2rs-pub-sub-requirements@ietf.org, i2rs-chairs@ietf.org, shares@ndzh.com
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, 27 Apr 2016 17:02:46 -0000

This I-D gives a fresh definition of 'datastore' in s.3

   A YANG datastore is a conceptual datastore that contains hierarchical
   data defined in YANG data models.  It is what is referred in existing
   RFCs as "NETCONF datastore".  However, as the same datastore is no
   longer tied to NETCONF as a specific transport, the term "YANG
   datastore" is deemed more appropriate.

which I think unhelpful.  There is no such term as  'NETCONF datastore';
rather there is 'datastore' defined (in RFC6241) as

   o  datastore: A conceptual place to store and access information.  A
      datastore might be implemented, for example, using files, a
      database, flash memory locations, or combinations thereof.

and widely used now in OAM RFC and I-D.  It can be used with the NETCONF
protocol ( which is not just a transport), it can be used with RESTCONF
and could in future be used with other application protocols.

YANG 1.0 (RFC6020) could have, should have, imported that definition in
s.3 (as other RFC and I-D do); rather it uses the phrase 'NETCONF
datastore' which makes it clear where the definition comes from but that
does not tie it to a particular protocol nor does it qualify its
meaning.  In the context of YANG, it is the unit of constraint checking.

Although NETCONF and YANG have grown up in tandem, NETCONF could be used
with another DDL but with the same concept of datastore just as the
concept of datastore can be used with another prototocol, such as
RESTCONF.

So if this I-D wants to use 'datastore' as defined in RFC6241, then it
should import and use it; if it wants another concept, then it should
mint a fresh term and define that.  From reading the I-D, I suspect that
the latter is the case, that the concept is nothing to do with
'datastore' (as currently defined in the IETF) and is just configuration
and state data on a device modelled with YANG as a DDL.

(In passing, one of the work items that the netmod WG circles around,
and will I am sure one day take on and complete, is the removal of
NETCONF from the documentation of YANG so that YANG is a standalone
DDL - but still importing the concept of datastore).

Tom Petch

----- Original Message -----
From: "The IESG" <iesg-secretary@ietf.org>
To: "IETF-Announce" <ietf-announce@ietf.org>
Cc: <i2rs@ietf.org>; <draft-ietf-i2rs-pub-sub-requirements@ietf.org>;
<i2rs-chairs@ietf.org>; <shares@ndzh.com>; <akatlas@gmail.com>
Sent: Friday, April 15, 2016 6:58 PM
Subject: Last Call: <draft-ietf-i2rs-pub-sub-requirements-05.txt>
(Requirements for Subscription to YANG Datastores) to Proposed Standard


>
> The IESG has received a request from the Interface to the Routing
System
> WG (i2rs) to consider the following document:
> - 'Requirements for Subscription to YANG Datastores'
>   <draft-ietf-i2rs-pub-sub-requirements-05.txt> as Proposed Standard
>
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action. Please send substantive comments to the
> ietf@ietf.org mailing lists by 2016-04-29. Exceptionally, comments may
be
> sent to iesg@ietf.org instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting.
>
> Abstract
>
>
>    This document provides requirements for a service that allows
client
>    applications to subscribe to updates of a YANG datastore.  Based on
>    criteria negotiated as part of a subscription, updates will be
pushed
>    to targeted recipients.  Such a capability eliminates the need for
>    periodic polling of YANG datastores by applications and fills a
>    functional gap in existing YANG transports (i.e.  Netconf and
>    Restconf).  Such a service can be summarized as a "pub/sub" service
>    for YANG datastore updates.  Beyond a set of basic requirements for
>    the service, various refinements are addressed.  These refinements
>    include: periodicity of object updates, filtering out of objects
>    underneath a requested a subtree, and delivery QoS guarantees.
>
>
>
>
> The file can be obtained via
> https://datatracker.ietf.org/doc/draft-ietf-i2rs-pub-sub-requirements/
>
> IESG discussion can be tracked via
>
https://datatracker.ietf.org/doc/draft-ietf-i2rs-pub-sub-requirements/ba
llot/
>
>
> No IPR declarations have been submitted directly on this I-D.
>
>


From nobody Wed Apr 27 11:15:42 2016
Return-Path: <evoit@cisco.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 7C68F12DB8F; Wed, 27 Apr 2016 11:15:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.517
X-Spam-Level: 
X-Spam-Status: No, score=-15.517 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.996, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 qm3q8xrdSzbP; Wed, 27 Apr 2016 11:15:39 -0700 (PDT)
Received: from alln-iport-7.cisco.com (alln-iport-7.cisco.com [173.37.142.94]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6D18912DB90; Wed, 27 Apr 2016 11:15:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5339; q=dns/txt; s=iport; t=1461780938; x=1462990538; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=9zb8fqFdWasHXMPJNGg5i6lMOxQi+vSaCkoUz5BnaFA=; b=JpkrT1Tk/y0i+0jj6gCKGserKNSJr1UHV8qbfoCLnp4JUA+rUWm/zaL/ RLnuRxaCasMleOdteiW8+1+W/qnK8iVcLKf7pZvLIHGAGsYc0Fwa/n42x n2CmfMqfVLacFYCY1iH6OdWAK/uuD8yO0+e82+Y/b+Qu2s4UDFatLUEwX c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AQAgCqACFX/4UNJK1egzhTfQauCYlOg?= =?us-ascii?q?g8BDYF1JIVrAoEyOBQBAQEBAQEBZSeEQQEBAQMBOjQLBQcEAgEIEQQBAQ0BEQU?= =?us-ascii?q?LIREdCAIEAQ0FCIgNAwoIDr5MDYRhAQEBAQEBAQEBAQEBAQEBAQEBAQEBEQSGI?= =?us-ascii?q?YRLgkGHUgWXXzEBhXuGJYFvgW6ETYhdh1GHXgEeAQFCgjaBNWyIL38BAQE?=
X-IronPort-AV: E=Sophos;i="5.24,542,1454976000"; d="scan'208";a="266797425"
Received: from alln-core-11.cisco.com ([173.36.13.133]) by alln-iport-7.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 27 Apr 2016 18:15:37 +0000
Received: from XCH-RTP-015.cisco.com (xch-rtp-015.cisco.com [64.101.220.155]) by alln-core-11.cisco.com (8.14.5/8.14.5) with ESMTP id u3RIFaKu031494 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 27 Apr 2016 18:15:37 GMT
Received: from xch-rtp-013.cisco.com (64.101.220.153) by XCH-RTP-015.cisco.com (64.101.220.155) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Wed, 27 Apr 2016 14:15:36 -0400
Received: from xch-rtp-013.cisco.com ([64.101.220.153]) by XCH-RTP-013.cisco.com ([64.101.220.153]) with mapi id 15.00.1104.009; Wed, 27 Apr 2016 14:15:35 -0400
From: "Eric Voit (evoit)" <evoit@cisco.com>
To: "tom p." <daedulus@btconnect.com>, "ietf@ietf.org" <ietf@ietf.org>
Subject: RE: Last Call: <draft-ietf-i2rs-pub-sub-requirements-05.txt> (Requirements for Subscription to YANG Datastores) to Proposed Standard
Thread-Topic: Last Call: <draft-ietf-i2rs-pub-sub-requirements-05.txt> (Requirements for Subscription to YANG Datastores) to Proposed Standard
Thread-Index: AQHRoKaiXtqNqqZhJkGFNMmqCiiuUJ+eEi8A
Date: Wed, 27 Apr 2016 18:15:35 +0000
Message-ID: <5c171faaae4d4a5ebbcace548cd97a9a@XCH-RTP-013.cisco.com>
References: <20160415175827.17486.53218.idtracker@ietfa.amsl.com> <00a801d1a0a6$14f26420$4001a8c0@gateway.2wire.net>
In-Reply-To: <00a801d1a0a6$14f26420$4001a8c0@gateway.2wire.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.118.56.228]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/WWJp1MvxrLOdGKltIYnUQTqMc7w>
Cc: "draft-ietf-i2rs-pub-sub-requirements@ietf.org" <draft-ietf-i2rs-pub-sub-requirements@ietf.org>, "i2rs-chairs@ietf.org" <i2rs-chairs@ietf.org>, "shares@ndzh.com" <shares@ndzh.com>
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, 27 Apr 2016 18:15:41 -0000

Hi Tom,

> From: tom p., April 27, 2016 12:55 PM
>=20
> This I-D gives a fresh definition of 'datastore' in s.3
>=20
>    A YANG datastore is a conceptual datastore that contains hierarchical
>    data defined in YANG data models.  It is what is referred in existing
>    RFCs as "NETCONF datastore".  However, as the same datastore is no
>    longer tied to NETCONF as a specific transport, the term "YANG
>    datastore" is deemed more appropriate.
>=20
> which I think unhelpful.  There is no such term as  'NETCONF datastore'; =
rather
> there is 'datastore' defined (in RFC6241) as
>=20
>    o  datastore: A conceptual place to store and access information.  A
>       datastore might be implemented, for example, using files, a
>       database, flash memory locations, or combinations thereof.
>=20
> and widely used now in OAM RFC and I-D.  It can be used with the NETCONF
> protocol ( which is not just a transport), it can be used with RESTCONF a=
nd could
> in future be used with other application protocols.
>=20
> YANG 1.0 (RFC6020) could have, should have, imported that definition in
> s.3 (as other RFC and I-D do); rather it uses the phrase 'NETCONF datasto=
re'
> which makes it clear where the definition comes from but that does not ti=
e it to
> a particular protocol nor does it qualify its meaning.  In the context of=
 YANG, it is
> the unit of constraint checking.
>=20
> Although NETCONF and YANG have grown up in tandem, NETCONF could be
> used with another DDL but with the same concept of datastore just as the
> concept of datastore can be used with another prototocol, such as RESTCON=
F.
>=20
> So if this I-D wants to use 'datastore' as defined in RFC6241, then it sh=
ould
> import and use it; if it wants another concept, then it should mint a fre=
sh term
> and define that.  From reading the I-D, I suspect that the latter is the =
case, that
> the concept is nothing to do with 'datastore' (as currently defined in th=
e IETF)
> and is just configuration and state data on a device modelled with YANG a=
s a
> DDL.

Nice catch, I agree with your analysis above.  As an FYI references to 'NET=
CONF datastore' came from within RFCs 6020, 6022, and RFC 6536.  A re-readi=
ng shows that NETCONF 'datastore' would be closer to the originally defined=
 meaning.=20

I see no reason why draft-ietf-i2rs-pub-sub-requirements cannot import the =
definition of datastore from RFC 6241.  This would impact nothing in the dr=
aft except replacing the term definition of "YANG datastore" you reference =
above with the text: " The term  datastore is defined in [RFC6241] and is n=
ot redefined here".   Would that be a sufficient fix?

Eric

> (In passing, one of the work items that the netmod WG circles around, and=
 will I
> am sure one day take on and complete, is the removal of NETCONF from the
> documentation of YANG so that YANG is a standalone DDL - but still import=
ing
> the concept of datastore).


> Tom Petch
>=20
> ----- Original Message -----
> From: "The IESG" <iesg-secretary@ietf.org>
> To: "IETF-Announce" <ietf-announce@ietf.org>
> Cc: <i2rs@ietf.org>; <draft-ietf-i2rs-pub-sub-requirements@ietf.org>;
> <i2rs-chairs@ietf.org>; <shares@ndzh.com>; <akatlas@gmail.com>
> Sent: Friday, April 15, 2016 6:58 PM
> Subject: Last Call: <draft-ietf-i2rs-pub-sub-requirements-05.txt>
> (Requirements for Subscription to YANG Datastores) to Proposed Standard
>=20
>=20
> >
> > The IESG has received a request from the Interface to the Routing
> System
> > WG (i2rs) to consider the following document:
> > - 'Requirements for Subscription to YANG Datastores'
> >   <draft-ietf-i2rs-pub-sub-requirements-05.txt> as Proposed Standard
> >
> > The IESG plans to make a decision in the next few weeks, and solicits
> > final comments on this action. Please send substantive comments to the
> > ietf@ietf.org mailing lists by 2016-04-29. Exceptionally, comments may
> be
> > sent to iesg@ietf.org instead. In either case, please retain the
> > beginning of the Subject line to allow automated sorting.
> >
> > Abstract
> >
> >
> >    This document provides requirements for a service that allows
> client
> >    applications to subscribe to updates of a YANG datastore.  Based on
> >    criteria negotiated as part of a subscription, updates will be
> pushed
> >    to targeted recipients.  Such a capability eliminates the need for
> >    periodic polling of YANG datastores by applications and fills a
> >    functional gap in existing YANG transports (i.e.  Netconf and
> >    Restconf).  Such a service can be summarized as a "pub/sub" service
> >    for YANG datastore updates.  Beyond a set of basic requirements for
> >    the service, various refinements are addressed.  These refinements
> >    include: periodicity of object updates, filtering out of objects
> >    underneath a requested a subtree, and delivery QoS guarantees.
> >
> >
> >
> >
> > The file can be obtained via
> > https://datatracker.ietf.org/doc/draft-ietf-i2rs-pub-sub-requirements/
> >
> > IESG discussion can be tracked via
> >
> https://datatracker.ietf.org/doc/draft-ietf-i2rs-pub-sub-requirements/ba
> llot/
> >
> >
> > No IPR declarations have been submitted directly on this I-D.
> >
> >


From nobody Wed Apr 27 11:28:23 2016
Return-Path: <touch@isi.edu>
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 4138D12DBA1; Wed, 27 Apr 2016 11:28:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.896
X-Spam-Level: 
X-Spam-Status: No, score=-2.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.996] 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 E3Wyhs07q4Cy; Wed, 27 Apr 2016 11:28:19 -0700 (PDT)
Received: from nitro.isi.edu (nitro.isi.edu [128.9.208.207]) (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 C0D4412B067; Wed, 27 Apr 2016 11:28:19 -0700 (PDT)
Received: from [128.9.184.114] ([128.9.184.114]) (authenticated bits=0) by nitro.isi.edu (8.13.8/8.13.8) with ESMTP id u3RIRrFa009181 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Wed, 27 Apr 2016 11:27:54 -0700 (PDT)
Subject: Re: Last Call: <draft-leiba-cotton-iana-5226bis-12.txt> (Guidelines for Writing an IANA Considerations Section in RFCs) to Best Current Practice
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, adrian@olddog.co.uk, ietf@ietf.org
References: <20160419141640.31545.54742.idtracker@ietfa.amsl.com> <057701d19ffa$2291b5b0$67b52110$@olddog.co.uk> <44038e4c-d177-3f06-7f40-dd82cbd86a99@gmail.com>
From: Joe Touch <touch@isi.edu>
Message-ID: <572104A8.2070805@isi.edu>
Date: Wed, 27 Apr 2016 11:27:52 -0700
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2
MIME-Version: 1.0
In-Reply-To: <44038e4c-d177-3f06-7f40-dd82cbd86a99@gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-MailScanner-ID: u3RIRrFa009181
X-ISI-4-69-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/fd9FrGMn_wDuNVK56D2-Q1aKZEw>
Cc: draft-leiba-cotton-iana-5226bis@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, 27 Apr 2016 18:28:21 -0000

Hi, all,

Sorry, but this seems incorrect to me.

1. if you want to reserve codepoints for an API (e.g., so that "0" means
"let the OS decide" or "any"), then you don't "reserve" it; you remove
it from the namespace. I.e., instead of defining the namespace as 0-255,
you define the namespace as 1-255 and indicate that the value of 0 is
specifically excluded *FROM THE PROTOCOL*.

Otherwise, you end up with exactly the problem we have with things like
transport port numbers - where 0 is effectively excluded as a protocol
codepoint because no API can access it, but it's not technically
excluded from being used inside a packet.

I would absolutely advise against claiming that 0 is Reserved to assist
with protocol development unless that's indicated in the specification
itself to avoid this problem in the future.

2. there is absolutely no reason to reserve the maximum value for
codepoint space extension; ANY reserved codepoint can accomplish that.
It might be useful to indicate that at least one codepoints SHOULD be
reserved for such extension, and that this is typically the highest
value -- but if you need to list a reason, the only one that comes to
mind is convenience of list management. Having it at the end makes it
easy to see. But there's no algorithmic reason for suggesting this.

Some other comments for this version:

1.1 - it's useful to remind authors to use only symbolic names for
codepoints until assignments are completed by IANA. Those symbolic names
should be used throughout the document AND in the IANA considerations
section.

4.2 - experimental use codepoints should clearly indicate whether they
are allowed or prohibited in widescale deployments on the public
Internet; this is a good place to cite the methods described in RFC 6994
as potentially useful for other shared use of experimental codepoints.

4.3 - other guidance to expert reviewers appears in the BCP165 document
pair (RFC6335 and RFC7605).

4.5 - transport ports should be listed under the examples provided in
this section, as they are one of the most frequently assigned this way.

4.8 / 4.10 - Transport ports in the system range (0-1023) are assigned
based on *either* IETF approval or IESG review, i.e., there's a case
where either sections 4.8 or 4.10 apply. That might be a useful example.

4.11 - examples where IETF review or standards action are needed include
cases where a namespace involves privilege, i.e., where simply using
that space could provide increased access (e.g., transport ports in the
system range).

4.12 - another place where transport ports are a good example of using
multiple policies - both for different subsets of the namespace AND
within one of those subsets.

6. another term useful to include here is "known unauthorized use". It
is a flag that can accompany any of these registration status values
listed and indicates when a codepoint is known to be deployed in the
Internet in ways other than as indicated. That helps sysadmins
understand when they see the codepoint whether it is likely that the
assignee is involved or not. NOTE: I do not recommend indicating the
name or contact point of the squatter because that only helps validate
their squatting.

7. it's useful to note that documents in registries should be provided
by a relatively permanent reference; a URL alone is typically
insufficient (and dead within a few months).

9.3 - this section ought to explain the term "squatting" and its impact.
In particular, I would like to see the IETF assert the claim that "use
of a codepoint prior to its assignment should not influence a subsequent
consideration of assignment", and reiterate that Internet drafts, RFCs,
and other documentation must avoid using specific codepoints unless
assigned for that purpose (i.e., assigned for that use specifically or
consistent with generic assignments - the latter including experimental
codepoints when deployed in ways consistent with such experiments)

9.4 - this section ought to differentiate between IANA revocation,
assignee release, and transfer. I recommend seeing RFC6335 about
transfers - e.g., transfers ought to be prohibited in favor of
release/request where each of those two steps should need to pass the
same hurdles as if they were independent.

Speaking from experience, this section should also discuss what happens
to abandoned contacts, i.e., when a codepoint is assigned based on a
point of contact or assignee who no longer works at a company of whose
company no longer exists.

Joe

On 4/26/2016 4:47 PM, Brian E Carpenter wrote:
> On 27/04/2016 08:28, Adrian Farrel wrote:
> ...
>> Section 6
>> Include hint on best practice for top and bottom of ranges.
>> OLD
>>      Reserved: Not assigned and not available for assignment.  Reserved
>>            values are held for special uses, such as to extend the
>>            namespace when it becomes exhausted.  Note that this is
>>            distinctly different from "Unassigned".
>> NEW
>>      Reserved: Not assigned and not available for assignment.  Reserved
>>            values are held for special uses, such as to extend the
>>            namespace when it becomes exhausted.  Note that this is
>>            distinctly different from "Unassigned".
>>
>>           It is common practice for documents that define numeric registries
>>           to mark the zero value as "Reserved" because this often aids protocol 
>>           implementations.
> I'm not sure about the "because" clause. It sounds a bit like an excuse for
> sloppy coding. Defining it explicitly as a no-op would seem like better
> practice in many cases.
>
>    Brian
>
>>           It is also common practice to mark the maximum
>>           value as "Reserved" so that it can be used as part of a strategy to
>>           extend the registry if the range proves too small in the future.
>> END
>>
>> Thanks,
>> Adrian
>>
>>


From nobody Thu Apr 28 11:35:39 2016
Return-Path: <carlosm3011@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 EB18A12D7FD for <ietf@ietfa.amsl.com>; Thu, 28 Apr 2016 11:35:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.449
X-Spam-Level: 
X-Spam-Status: No, score=-2.449 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, LOTS_OF_MONEY=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 Sa2Dq1ZOIFu9 for <ietf@ietfa.amsl.com>; Thu, 28 Apr 2016 11:35:34 -0700 (PDT)
Received: from mail-yw0-x22a.google.com (mail-yw0-x22a.google.com [IPv6:2607:f8b0:4002:c05::22a]) (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 5359A12D51E for <ietf@ietf.org>; Thu, 28 Apr 2016 11:35:34 -0700 (PDT)
Received: by mail-yw0-x22a.google.com with SMTP id j74so120037606ywg.1 for <ietf@ietf.org>; Thu, 28 Apr 2016 11:35:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=reply-to:to:from:subject:message-id:date:user-agent:mime-version :content-transfer-encoding; bh=nGzK2Bcv794H6Qx9hrhgUysXh5o9X5KKNbhQTVZj7XA=; b=oGe0LekJ4MOYyZeDrWBI3rOyuH9qItKOOKbLKc2eaVjx9YyCaOXZ1eTDgYve+Z2GRH BSmSyftCuIeDHuQ3a9KIOEytIrl9hRiis4D2yoPCrEa8xI+Q4Xqw56ug4oYuMHGhgnZ7 V2HXnn3JLuiYcqrE2Onwdqu962+lUZJQzSiYs8SxDwBw0erKMJ6+cp6irFPHZerQDY61 LzuUPJ7qzyXfBexOdsGEujbZO2iWgCIC8SY0IRCJrZ6xrr3z6pdg3mx8/eo5qrxtbbBp 2a+84kRHu7jg1UpHOpcQ5y+a/zAbR1pfa/JCv7ynxVfy8AlNTydLgKjn3DM7X1zDLw5p JyLw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:reply-to:to:from:subject:message-id:date :user-agent:mime-version:content-transfer-encoding; bh=nGzK2Bcv794H6Qx9hrhgUysXh5o9X5KKNbhQTVZj7XA=; b=ZH8xVvTIywMiFzeitbpMfzHqSCECTAfH5MM3zMCEs487iJ+pHhSQbB4MH6UV81KnaH rhBNqxi14K07xeYct7vxWjyzexNVJPfm2ECKuU1XlS3oQi4ZHn6DESA2sbwNEe5MkcKJ ih1h422CJgv612sCsbD2bDm4D2JtmMZQ4nseG0W0I/QBcbULH8q2NNNPD4GezlQx6Fs7 LPx0YBqr6909nmlRkASskaUK9fLNW1GxkJnnqO6AGnwPkFHsAg4IDjK7HNbq7qsQBeFB yPmEhIKVDzdJqgHBdbP06xUykrtO9d9uuFj8nDIcdy+L0vtco4rxwEUsu6YwjoFnml0c duGg==
X-Gm-Message-State: AOPr4FUOuhOCcpqDFmbtkH2BTxf1ygH055TxkQ8+goUd3LnzdMOupSHiEU4YdU0Hxen92Q==
X-Received: by 10.159.37.72 with SMTP id 66mr8756570uaz.111.1461868533537; Thu, 28 Apr 2016 11:35:33 -0700 (PDT)
Received: from [200.7.87.117] ([200.7.87.117]) by smtp.googlemail.com with ESMTPSA id b36sm2479572uab.26.2016.04.28.11.35.32 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 28 Apr 2016 11:35:32 -0700 (PDT)
To: ietf@ietf.org
From: "Carlos M. Martinez" <carlosm3011@gmail.com>
Subject: Grants for Cybersecurity in Africa, LAC and AP regions
Message-ID: <572257F4.9060302@gmail.com>
Date: Thu, 28 Apr 2016 15:35:32 -0300
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:38.0) Gecko/20100101 Thunderbird/38.7.2
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/rtDI5wHi8NG-5LYiaH0fjSwC1K0>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: carlos@lacnic.net
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, 28 Apr 2016 18:35:38 -0000

Hello all,

I'm channeling my colleagues from APNIC, AfriNIC and LACNIC helping them
share some funding opportunities for projects involving IPv6 and
cybersecurity (RPKI included!)

----

This year the Seed Alliance <www.seedalliance.net> and its regional
members, FIRE, FRIDA and ISIF Asia will support technical projects
seeking to improve Internet security and stability in Africa, Latin
America and the Caribbean as well as the Asia Pacific region to allocate
US$150,000 in grants.Those interested in obtaining these grants must
submit their projects to the call for proposals launched by each
regional program.

1) Africa â€“ Deadline: 31 May 2016. Two grants of US$25,000 each for
project that focus on Internet Security and Collaborative Security, and
established projects that focus on improving access to Internet.
For more information contact FIRE coordinator Mwendwa Kivuva at
fireprogram@afrinic.net
The FIRE program is managed by AFRINIC. Details about how to apply
available at http://www.fireafrica.org

2) Latin America - Deadline: 13 May, 2016. Two grants on Cybersecurity
between USD 20,000 and USD 30,000. Additional funding is also available
for one grant on IPv6 Deployment in the LAC region for US$20,000.
For more information contact FRIDA Coordinator Carolina Caeiro at
carolina@lacnic.net.
The FRIDA Program is managed by LACNIC. Details about how to apply
available at http://www.programafrida.net

3) Asia Pacific â€“ Deadline: 31 May 2016. 1 grant on Cybersecurity for
AUD 56,000. Additional funding is also available for technical projects:
AUD 92,000 to support Research on Network Operations for grants from AUD
5,000 to AUD 45,000 and 2 grants on Technical Innovation, one for AUD
30,000 for prototypes and proof of concept development support and a AUD
50,000 grant for scale-up of existing solutions.
For more information contact ISIF Asia Coordinator Sylvia Cadena at
info@isif.asia
The ISIF Asia program is managed by APNIC. Details about how to apply
available at http://www.isif.asia/grant


From nobody Thu Apr 28 13:31:41 2016
Return-Path: <worley@alum.mit.edu>
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 79F4612D9E6 for <ietf@ietfa.amsl.com>; Thu, 28 Apr 2016 13:31:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.934
X-Spam-Level: 
X-Spam-Status: No, score=-1.934 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_SOFTFAIL=0.665] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=comcast.net
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 QlN3BpgkX93a for <ietf@ietfa.amsl.com>; Thu, 28 Apr 2016 13:31:38 -0700 (PDT)
Received: from resqmta-ch2-01v.sys.comcast.net (resqmta-ch2-01v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:33]) (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 C121912D575 for <ietf@ietf.org>; Thu, 28 Apr 2016 13:31:35 -0700 (PDT)
Received: from resomta-ch2-12v.sys.comcast.net ([69.252.207.108]) by comcast with SMTP id vsaaaFmslfr8Tvsb0aHkw4; Thu, 28 Apr 2016 20:31:34 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1461875494; bh=Y3O99cEnRxisuJO/nSCu6JSD25KarDQWoWsHatoEcL4=; h=Received:Received:Received:Received:From:To:Subject:Date: Message-ID; b=YvXkmrOrOUg684DLyHkRD4RSVXLcoa/6S5VVejBQRlIT3JJMUa3OBh+KNDh/NCbpy U+tlWkY2fcKGzO+tOqnX1bTI1DIwA3ZuxsyTiSMiYJ1Y+vAITlGZ1rdiKiORdF9yHt fsaEfxY/KRM7jeoSUkM669yT1sA+zSwibgGYyLHH40b7z8gcAtYT4OQUpQWygTwrK6 p/wn4jQy2PO/H9MP6tBK2opIqFRlxomaVQqu6Jz9lEqaQQdrAUu+9WEDn/vzAW1r3G AmvZL7GunLSmfnr02Q+9sfEUpG1WvL7LdwlQ1cMWr9OXLMs48Fjv3QKYbjKIczH1Fw p3kdCPLNxfSdw==
Received: from hobgoblin.ariadne.com ([73.143.237.82]) by resomta-ch2-12v.sys.comcast.net with comcast id nwXZ1s00b1nMCLR01wXakW; Thu, 28 Apr 2016 20:31:34 +0000
Received: from hobgoblin.ariadne.com (hobgoblin.ariadne.com [127.0.0.1]) by hobgoblin.ariadne.com (8.14.7/8.14.7) with ESMTP id u3SKVX5c002950; Thu, 28 Apr 2016 16:31:33 -0400
Received: (from worley@localhost) by hobgoblin.ariadne.com (8.14.7/8.14.7/Submit) id u3SKVWBD002947; Thu, 28 Apr 2016 16:31:32 -0400
X-Authentication-Warning: hobgoblin.ariadne.com: worley set sender to worley@alum.mit.edu using -f
From: worley@ariadne.com (Dale R. Worley)
To: gen-art@ietf.org, draft-ietf-bfd-seamless-use-case.all@ietf.org, ietf@ietf.org
Subject: Gen-ART Telechat review of draft-ietf-bfd-seamless-use-case-06
Sender: worley@ariadne.com (Dale R. Worley)
Date: Thu, 28 Apr 2016 16:31:32 -0400
Message-ID: <87wpnhzd97.fsf@hobgoblin.ariadne.com>
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/4I0Pp2f9Dd1stjnGgWxeZLO2Vuo>
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, 28 Apr 2016 20:31:39 -0000

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed by
the IESG for the IETF Chair. Please wait for direction from your
document shepherd or AD before posting a new version of the draft.

For more information, please see the FAQ at
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Document: draft-ietf-bfd-seamless-use-case-06
Reviewer: Dale R. Worley
Review Date: 2016-04-28
IESG Telechat date: 2016-05-05

Summary:  Ready.  Thanks for the thorough reworking of section 2,
which makes clear the way that SBFD is organized, and forms the
context within which the use cases are described.  Also, many nits
were fixed.  There are still some wording problems, but the RFC Editor
can help clean those up.

Dale


From nobody Thu Apr 28 15:55:01 2016
Return-Path: <tomh@apnic.net>
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 5BA6512D5A9 for <ietf@ietfa.amsl.com>; Thu, 28 Apr 2016 15:54:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.787
X-Spam-Level: 
X-Spam-Status: No, score=-7.787 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.996, SPF_PASS=-0.001, T_DKIM_INVALID=0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=apnic.net
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 ZneeGSBIPf_y for <ietf@ietfa.amsl.com>; Thu, 28 Apr 2016 15:54:57 -0700 (PDT)
Received: from ia-mailgw.apnic.net (ia-mailgw.apnic.net [IPv6:2001:dd8:a:851::25]) (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 D186612D5A4 for <ietf@ietf.org>; Thu, 28 Apr 2016 15:54:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=apnic.net; s=R2D2; h=received:received:received:date:from:to:cc:subject:message-id: mail-followup-to:references:mime-version:content-type:content-disposition: in-reply-to:user-agent:return-path; bh=PCi41aMzEmmnYsILpOAtVHMiBQ9VIeMJPm8dlTApRZc=; b=gmAP9VAzQKQx7NHNi2W2SlltwB2mvCJeVVUZ+koAOknfz/Z2/3NQe9vhUxjWh/a443I4VWEn7v7SE tBmceQChOZ2oEKazQpHK9JiU9FpwBoEKTZzBwVVqXjohVcPxKGUUCEXzogl+GTiQXDB5BYwCn5dphm Te1YGvPs3OsgxdSs=
Received: from iamda3.org.apnic.net (unknown [IPv6:2001:dd8:9:2::101:249]) by ia-mailgw.apnic.net (Halon Mail Gateway) with ESMTPS; Fri, 29 Apr 2016 08:59:59 +1000 (AEST)
Received: from main (203.119.101.249) by iamda3.org.apnic.net (203.119.111.31) with Microsoft SMTP Server (TLS) id 14.3.123.3; Fri, 29 Apr 2016 08:54:51 +1000
Received: from tomh by main with local (Exim 4.87)	(envelope-from <tomh@apnic.net>)	id 1avupf-0000OY-JP; Fri, 29 Apr 2016 08:54:51 +1000
Date: Fri, 29 Apr 2016 08:54:51 +1000
From: Tom Harrison <tomh@apnic.net>
To: <ietf@ietf.org>
Subject: Re: [sidr] Last Call: <draft-ietf-sidr-rpsl-sig-10.txt> (Securing RPSL Objects with RPKI Signatures) to Proposed Standard
Message-ID: <20160428225451.GE123284@main>
Mail-Followup-To: ietf@ietf.org, sidr-chairs@ietf.org, draft-ietf-sidr-rpsl-sig@ietf.org, sidr@ietf.org
References: <20160425184508.30206.46648.idtracker@ietfa.amsl.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <20160425184508.30206.46648.idtracker@ietfa.amsl.com>
User-Agent: Mutt/1.6.0 (2016-04-01)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/n4gPJc4vuhe445GAnqRYa9A242g>
Cc: sidr-chairs@ietf.org, draft-ietf-sidr-rpsl-sig@ietf.org, sidr@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, 28 Apr 2016 22:54:59 -0000

Section 5 requires that an EE certificate be used for the signing of
the RPSL object.  An EE certificate must contain an SIA extension that
points to an RPKI signed object (RFC 6487 [4.8.8.2]).  The draft does
not define a profile for a new type of object, or specify an existing
one that may be used instead.  There are a number of ways to deal with
this: for example, by defining a new profile and changing the
signature URL to suit, or by amending RFC 6487 such that object
pointers in EE certificates are optional.

Section 4 specifies sets of attributes that must be signed.  'org' is
included as one of these attributes for the as-block, inet[6]num, and
route[6] object types.  However, 'org' is not defined in either of the
principal RPSL RFCs (2622 and 4012), and there are current
implementations (e.g. APNIC's) that do not support it.  I think the
references to 'org' should be omitted.

Section 4 specifies 'signature' as an attribute that must be signed.
'signature' can appear multiple times in a single object, where e.g.
two different resource holders sign a route[6] object.  Given that the
text doesn't explicitly state that only the newest 'signature' must be
signed, it would appear to require that any extant 'signature'
attributes be signed as well.  That in turn would prevent previous
signers from re-signing the object independently of the subsequent
signers.  I think the text should be changed so that only the new
signature attribute need be signed.

Section 2.4 requires that "the Internet number resources present in
[RFC3779] extensions of the certificate referred to in the "c" field
of the signature must cover the resources in the primary key of the
object".  This means that it's not possible to sign a route[6] object
for a route where one resource holder has the ASN and another the
prefix.  In revision 8 (and earlier), the possibility of there being
multiple signatures, each with a certificate covering a subset of the
primary key resources, was explicitly permitted.  I think that the
previous text here should be restored.

(The above points were the product of much discussion of this draft
with Tim and Oleg from RIPE, not that I'm speaking for them.  We were
able to write interoperable prototype signer/validator
implementations, so the document is in pretty good shape on the
whole.)

-Tom


From nobody Thu Apr 28 21:53:17 2016
Return-Path: <narten@us.ibm.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 923D412B061 for <ietf@ietfa.amsl.com>; Thu, 28 Apr 2016 21:53:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.917
X-Spam-Level: 
X-Spam-Status: No, score=-7.917 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.996, SPF_PASS=-0.001] 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 G5ix6qKrovSn for <ietf@ietfa.amsl.com>; Thu, 28 Apr 2016 21:53:12 -0700 (PDT)
Received: from e38.co.us.ibm.com (e38.co.us.ibm.com [32.97.110.159]) (using TLSv1.2 with cipher CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0448D12B00A for <ietf@ietf.org>; Thu, 28 Apr 2016 21:53:08 -0700 (PDT)
Received: from localhost by e38.co.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for <ietf@ietf.org> from <narten@us.ibm.com>; Thu, 28 Apr 2016 22:53:08 -0600
Received: from d03dlp01.boulder.ibm.com (9.17.202.177) by e38.co.us.ibm.com (192.168.1.138) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Thu, 28 Apr 2016 22:53:05 -0600
X-IBM-Helo: d03dlp01.boulder.ibm.com
X-IBM-MailFrom: narten@us.ibm.com
X-IBM-RcptTo: ietf@ietf.org
Received: from b03cxnp07028.gho.boulder.ibm.com (b03cxnp07028.gho.boulder.ibm.com [9.17.130.15]) by d03dlp01.boulder.ibm.com (Postfix) with ESMTP id 60CE61FF001E for <ietf@ietf.org>; Thu, 28 Apr 2016 22:52:50 -0600 (MDT)
Received: from b03ledav006.gho.boulder.ibm.com (b03ledav006.gho.boulder.ibm.com [9.17.130.237]) by b03cxnp07028.gho.boulder.ibm.com (8.14.9/8.14.9/NCO v10.0) with ESMTP id u3T4r57O45875408 for <ietf@ietf.org>; Thu, 28 Apr 2016 21:53:05 -0700
Received: from b03ledav006.gho.boulder.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id DCB66C6037 for <ietf@ietf.org>; Thu, 28 Apr 2016 22:53:04 -0600 (MDT)
Received: from rotala.raleigh.ibm.com (unknown [9.27.222.27]) by b03ledav006.gho.boulder.ibm.com (Postfix) with ESMTPS id BE1E1C603E for <ietf@ietf.org>; Thu, 28 Apr 2016 22:53:04 -0600 (MDT)
Received: from rotala.raleigh.ibm.com (localhost [127.0.0.1]) by rotala.raleigh.ibm.com (8.15.2/8.12.5) with ESMTP id u3T4r3he023808 for <ietf@ietf.org>; Fri, 29 Apr 2016 00:53:03 -0400
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.15.2/8.15.2/Submit) id u3T4r2pJ023748 for ietf@ietf.org; Fri, 29 Apr 2016 00:53:02 -0400
From: narten@us.ibm.com
Message-Id: <201604290453.u3T4r2pJ023748@rotala.raleigh.ibm.com>
Date: Fri, 29 Apr 2016 00:53:02 -0400
To: ietf@ietf.org
Subject: Weekly posting summary for ietf@ietf.org
User-Agent: Heirloom mailx 12.5 7/5/10
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-TM-AS-GCONF: 00
X-Content-Scanned: Fidelis XPS MAILER
x-cbid: 16042904-0029-0000-0000-000027173BD2
X-IBM-AV-DETECTION: SAVI=unused REMOTE=unused XFE=unused
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/MIW6X4tLobgW_Ov0PIQKrh3Ncuw>
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: Fri, 29 Apr 2016 04:53:15 -0000

Total of 25 messages in the last 7 days.
 
script run at: Fri Apr 29 00:53:02 EDT 2016
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
  8.00% |    2 |  8.10% |    19090 | klieforth@isoc.org
  4.00% |    1 |  6.57% |    15487 | daedulus@btconnect.com
  4.00% |    1 |  6.21% |    14637 | nalini.elkins@insidethestack.com
  4.00% |    1 |  5.45% |    12855 | evoit@cisco.com
  4.00% |    1 |  5.01% |    11818 | stewe@stewe.org
  4.00% |    1 |  4.97% |    11720 | corinnecath@gmail.com
  4.00% |    1 |  4.86% |    11454 | touch@isi.edu
  4.00% |    1 |  4.54% |    10697 | jari.arkko@piuha.net
  4.00% |    1 |  4.40% |    10372 | lrg_pizza_xtra_chz_plz@aol.com
  4.00% |    1 |  4.35% |    10252 | narten@us.ibm.com
  4.00% |    1 |  3.97% |     9352 | dave@cridland.net
  4.00% |    1 |  3.80% |     8952 | carlosm3011@gmail.com
  4.00% |    1 |  3.71% |     8738 | lloyd.wood@yahoo.co.uk
  4.00% |    1 |  3.65% |     8598 | wes@mti-systems.com
  4.00% |    1 |  3.60% |     8492 | tomh@apnic.net
  4.00% |    1 |  3.57% |     8420 | brian.e.carpenter@gmail.com
  4.00% |    1 |  3.46% |     8157 | howahong37@yahoo.com
  4.00% |    1 |  3.42% |     8071 | sm+ietf@elandsys.com
  4.00% |    1 |  3.39% |     7994 | nd@syndicat.com
  4.00% |    1 |  3.09% |     7280 | adrian@olddog.co.uk
  4.00% |    1 |  3.05% |     7187 | worley@ariadne.com
  4.00% |    1 |  2.57% |     6059 | johnl@taugh.com
  4.00% |    1 |  2.26% |     5328 | iad@ietf.org
  4.00% |    1 |  2.01% |     4734 | chair@ietf.org
--------+------+--------+----------+------------------------
100.00% |   25 |100.00% |   235744 | Total


From nobody Fri Apr 29 12:59:07 2016
Return-Path: <presnick@qti.qualcomm.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 CBD3F12D10E for <ietf@ietfa.amsl.com>; Fri, 29 Apr 2016 12:59:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.017
X-Spam-Level: 
X-Spam-Status: No, score=-8.017 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.996, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=qti.qualcomm.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 KywKezwR7-3Y for <ietf@ietfa.amsl.com>; Fri, 29 Apr 2016 12:59:04 -0700 (PDT)
Received: from wolverine02.qualcomm.com (wolverine02.qualcomm.com [199.106.114.251]) (using TLSv1.2 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 10D5B12D0DF for <ietf@ietf.org>; Fri, 29 Apr 2016 12:59:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1461959940; x=1493495940; h=from:to:cc:subject:date:message-id:in-reply-to: references:mime-version:content-transfer-encoding; bh=YMC7RobgRNsW3CIYzuTx0t0FGFS8FNYSYdaH34W/O5o=; b=CnsBwE8yZA35JCw1T0ITfnizO6D3upFv6SxP+n/6cLGKwXtbSLuCZGUT kkCPzAOxJeeeMX4ZzWRLD5WTUktxOCTs1CxPyq5VO14AtV+u2to/mco3O BpdBFAr96LknM3Mbpmls0XFV9HeyFx8OTKWFM8FZDTDROvG/O85aLi8mZ U=;
X-IronPort-AV: E=Sophos;i="5.24,553,1455004800"; d="scan'208";a="284547520"
Received: from ironmsg02-l-new.qualcomm.com (HELO ironmsg02-L.qualcomm.com) ([10.53.140.109]) by wolverine02.qualcomm.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 29 Apr 2016 12:59:00 -0700
X-IronPort-AV: E=McAfee;i="5700,7163,8150"; a="687220188"
Received: from nasanexm01f.na.qualcomm.com ([10.85.0.32]) by ironmsg02-L.qualcomm.com with ESMTP/TLS/RC4-SHA; 29 Apr 2016 12:59:00 -0700
Received: from [10.64.161.242] (10.80.80.8) by NASANEXM01F.na.qualcomm.com (10.85.0.32) with Microsoft SMTP Server (TLS) id 15.0.1130.7; Fri, 29 Apr 2016 12:58:59 -0700
From: Pete Resnick <presnick@qti.qualcomm.com>
To: Stephan Wenger <stewe@stewe.org>
Subject: Re: Last Call on draft-bradner-rfc3979bis-08.txt ("Intellectual Property Rights in IETF Technology")
Date: Fri, 29 Apr 2016 14:58:58 -0500
Message-ID: <9AFC22D7-C509-4765-AAC9-3096F188C4C6@qti.qualcomm.com>
In-Reply-To: <EC4CBF0D-1B7C-4FB5-85EA-E622B24E9B9A@stewe.org>
References: <0000431F-F977-4A24-BA4D-064F740977A0@piuha.net> <E7E31E22-1C86-40C4-BC5B-F65132015EF5@qti.qualcomm.com> <6CA3C554-0FF6-4779-80B9-C75698FB61C1@piuha.net> <EC4CBF0D-1B7C-4FB5-85EA-E622B24E9B9A@stewe.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format=flowed
Content-Transfer-Encoding: 8bit
X-Mailer: MailMate (1.9.4r5239)
X-Originating-IP: [10.80.80.8]
X-ClientProxiedBy: NASANEXM01G.na.qualcomm.com (10.85.0.33) To NASANEXM01F.na.qualcomm.com (10.85.0.32)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/dFzf67eQsgZjl_7s_KEOkI9b4uc>
Cc: IETF <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: Fri, 29 Apr 2016 19:59:07 -0000

On 25 Apr 2016, at 16:31, Stephan Wenger wrote:

> On 4/25/16, 13:15, "ietf on behalf of Jari Arkko" 
> <ietf-bounces@ietf.org on behalf of jari.arkko@piuha.net> wrote:
>
>>
>>> - Section 5.5(C): Two things:
>>>
>
> [...]
>
>>> OLD
>>>      must ensure that such
>>>      commitments are binding on any subsequent transferee of the
>>>      relevant IPR.
>>> NEW
>>>      must ensure that such commitments are binding on a transferee 
>>> of
>>>      the relevant IPR, and that such transferee will use reasonable
>>>      efforts to ensure that such commitments are binding on a
>>>      subsequent transferee of the relevant IPR, and so on.
>>> END
>>>
>>> The object of the "subsequent" wasn't clear, so this just spells it 
>>> out. Wordy, but more precise.
>>
>> Right
>
> Iâ€™m not sure I agree that the object of â€śsubsequent wasnâ€™t clear 
> from context.  However, I donâ€™t mind to see that fixed if others 
> feel so.  However, the fix as proposed sets a very low standard 
> (reasonable efforts) for ensuring that subsequent transferees are 
> bound. That a substantial change from the WG consensus, and IMO in the 
> wrong direction.

Let's be clear that there was no "WG consensus" on this, since there was 
no WG. But let's assume that the consensus of the BoF was for something 
strong.

I disagree that "use reasonable efforts to ensure" is such a low 
standard, and the stronger language you propose concerns me:

> What we want to achieve is that if A assigns a patent to B, B and all 
> further transferees (B to C, C to D, etc. etc.) are similarly bound.  
> We want to make sure if any of these entities doesnâ€™t feel bound for 
> whatever reason, the patent is held unenforcible by a well-informed 
> court.  Itâ€™s clear that this is much more onerous to the 
> rightholder, and may well lower the value of the IPR.
>
> I would be fine if the NEW part would be reworded as follows:
> NEW
>       must ensure that such commitments are binding on a transferee of
>       the relevant IPR, and also binding on any subsequent transferees
> of the relevant IPR.
> END

This seems to require that if my IPR is transferred 20 times over 20 
years, I am on the hook in perpetuity to absolutely make sure that the 
next person down the line sticks to the agreement. I'm certainly willing 
to make *reasonable* efforts to do so, and it will be up to a court to 
determine if my efforts were reasonable, but I certainly don't want to 
be forced to completely indemnify to 21st person down the line. "Use 
reasonable efforts to ensure" seems reasonable. Otherwise, it's not 
clear to me what I'm signing up to.

>>> - Section 7, paragraph 6:
>>>
>>> The only change in this paragraph from 3979 was to add the word 
>>> "all" in the second-to-last sentence. My lawyer friends tell me that 
>>> this little change is opening a can of worms, having to do with 
>>> licensing to makers of parts instead of implementers of the whole 
>>> specification. I don't think we meant to change the meaning from the 
>>> 3979 meaning, and I certainly don't think that we meant to change 
>>> some implication about whether folks in general needed to license to 
>>> people that make parts where they wouldn't have before. Was there 
>>> something unclear about that sentence that needed the word "all" 
>>> added to it? We aren't making a substantive change, are we? Can we 
>>> just strike it? It seemed pretty clear to me before.
>>
>> Agree
>
> Iâ€™m not sure here.
> For context, the paragraph is in section 7 of RFC3979bis (which used 
> to be the second paragraph of section 8 of RFC3979).  The sentence in 
> question describes an purported IETF consensus established in 
> pre-RFC3979 times, as follows (the critical and new â€śALLâ€ť is 
> capitalized):
>
> â€ś
> An IETF consensus has developed that no mandatory-to-implement 
> security technology can be specified in an IETF specification unless 
> it has no known IPR claims against it or a royalty-free license is 
> available to ALL implementers of the specification unless there is a 
> very good reason to do so.
> â€ś

Right, the only change between 3979 and the above is the addition of the 
word "ALL" (not in all caps in 3979bis).

> I agree that the tightened language removes an arguably unclear 
> loophole that has been present in RFC3979, and which Peteâ€™s 
> lawyer-friends probably would like to preserve.  However, generally 
> speaking, removing loopholes like this is a Good Thing, unless the 
> consensus at the time was such that there ought to be a loophole.  I 
> did not follow the consensus process in sufficient detail to have an 
> opinion, but perhaps security and IPR conscious folks in the IETF 
> remember?

Wait, what "arguably unclear loophole" do you think was there that 
adding "all" in the above sentence tightens? Calling it a "loophole" 
implies that somehow the IETF intention was to disallow something that 
the current text allows. What is that something that you think we ought 
to be removing?

I know that my lawyer friend was concerned not about security technology 
per se, but the issue of licensing levels more generally. I'm pretty 
sure we only wanted to talk about requiring royalty-free licensing for 
security protocols specifically and never intended to require particular 
kinds of licensing across the board. Either way, I think that the 
original text was perfectly clear and had no loopholes.

So, why are we adding "all"? What loophole are we trying to close? If 
there is none, let's strike "all" and use the original text.

pr
-- 
Pete Resnick <http://www.qualcomm.com/~presnick/>
Qualcomm Technologies, Inc. - +1 (858)651-4478


From nobody Fri Apr 29 19:23:30 2016
Return-Path: <stewe@stewe.org>
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 4BE2D12B00D for <ietf@ietfa.amsl.com>; Fri, 29 Apr 2016 19:23:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] 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 rHFvzQf8mkwf for <ietf@ietfa.amsl.com>; Fri, 29 Apr 2016 19:23:25 -0700 (PDT)
Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1on0750.outbound.protection.outlook.com [IPv6:2a01:111:f400:fc10::750]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8B0B1120047 for <ietf@ietf.org>; Fri, 29 Apr 2016 19:23:25 -0700 (PDT)
Received: from BLUPR17MB0275.namprd17.prod.outlook.com (10.162.235.146) by BLUPR17MB0276.namprd17.prod.outlook.com (10.162.235.147) with Microsoft SMTP Server (TLS) id 15.1.477.8; Sat, 30 Apr 2016 02:23:01 +0000
Received: from BLUPR17MB0275.namprd17.prod.outlook.com ([10.162.235.146]) by BLUPR17MB0275.namprd17.prod.outlook.com ([10.162.235.146]) with mapi id 15.01.0477.015; Sat, 30 Apr 2016 02:23:01 +0000
From: Stephan Wenger <stewe@stewe.org>
To: Pete Resnick <presnick@qti.qualcomm.com>
Subject: Re: Last Call on draft-bradner-rfc3979bis-08.txt ("Intellectual Property Rights in IETF Technology")
Thread-Topic: Last Call on draft-bradner-rfc3979bis-08.txt ("Intellectual Property Rights in IETF Technology")
Thread-Index: AQHRhDTbKR9yu1RueEWA9RrAiHSISp+FI5mAgBYyZID//5/2gIAGpMUA///18oA=
Date: Sat, 30 Apr 2016 02:23:01 +0000
Message-ID: <C7E5B6F0-23C9-4A94-9A8B-2A65490F0F8C@stewe.org>
References: <0000431F-F977-4A24-BA4D-064F740977A0@piuha.net> <E7E31E22-1C86-40C4-BC5B-F65132015EF5@qti.qualcomm.com> <6CA3C554-0FF6-4779-80B9-C75698FB61C1@piuha.net> <EC4CBF0D-1B7C-4FB5-85EA-E622B24E9B9A@stewe.org> <9AFC22D7-C509-4765-AAC9-3096F188C4C6@qti.qualcomm.com>
In-Reply-To: <9AFC22D7-C509-4765-AAC9-3096F188C4C6@qti.qualcomm.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: qti.qualcomm.com; dkim=none (message not signed) header.d=none; qti.qualcomm.com; dmarc=none action=none header.from=stewe.org; 
x-ms-exchange-messagesentrepresentingtype: 1
x-originating-ip: [50.174.30.183]
x-ms-office365-filtering-correlation-id: 09d7e489-ced4-46c4-560d-08d3709e5ace
x-microsoft-exchange-diagnostics: 1; BLUPR17MB0276; 5:DO1YhpObgcdmXL/xeq1zqNOtiLglrgTeTXDmA74tLJVh2j7KMOLiWtvrzUrzz5bdnKICAz8MFS2GZXc6glaS8zpwPOmphyoG+hTYH43yo1LdMQRTc0duaUBSUQ3kQLtd1tlLsVNka6/8tK9J/mFXTQ==; 24:Y6U84yu+PtVvIQTfu0aspv6erejg2BarxenryEVHmzgCTxM0sckyP2AZWExEyfSN7mVlUcJpv8gKHIbjlW6C96mp4L5XES7C2FSy84lfJvk=; 7:JHsW+8Crs+AgoRgdgDKzkSWQzlkqbTuqZYq0sK5G/x0ZRXtT0hP2uBhrxTqqCxEYpQLy4KOz3K1siZi3kIWnOyL4S41HdEoVz0l+eALnUgk34ez1mHA18/lJeaopuvOr+f4BT/+c9SarD8AUdYCcU/JiEZb0+AOYcxLgDPScLkHvu8yJMLHOx4lHrlsj8Q07
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:BLUPR17MB0276;
x-microsoft-antispam-prvs: <BLUPR17MB02763663370E321995C1245DAE670@BLUPR17MB0276.namprd17.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(9101521072)(6040130)(601004)(2401047)(8121501046)(5005006)(3002001)(10201501046)(6041072)(6043046); SRVR:BLUPR17MB0276; BCL:0; PCL:0; RULEID:; SRVR:BLUPR17MB0276; 
x-forefront-prvs: 0928072091
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(979002)(6009001)(51444003)(24454002)(5004730100002)(83716003)(2906002)(19580405001)(19580395003)(1220700001)(33656002)(1096002)(92566002)(6116002)(102836003)(3846002)(586003)(122556002)(76176999)(3660700001)(50986999)(86362001)(106116001)(11100500001)(230783001)(81166005)(54356999)(82746002)(99286002)(3280700002)(10400500002)(4326007)(5008740100001)(87936001)(36756003)(77096005)(2900100001)(2950100001)(5002640100001)(563304003)(93886004)(15975445007)(189998001)(66066001)(110136002)(104396002)(42262002)(969003)(989001)(999001)(1009001)(1019001); DIR:OUT; SFP:1102; SCL:1; SRVR:BLUPR17MB0276; H:BLUPR17MB0275.namprd17.prod.outlook.com; FPR:; SPF:None; MLV:ovrnspm; PTR:InfoNoRecords; LANG:en; 
spamdiagnosticoutput: 1:23
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
Content-ID: <A40BACE9B845EB44BEE49992B9F8A547@namprd17.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: stewe.org
X-MS-Exchange-CrossTenant-originalarrivaltime: 30 Apr 2016 02:23:01.5143 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 865fc51c-5fae-4322-98ef-0121a85df0b6
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BLUPR17MB0276
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/BbV_nzVeG_w9ePAt0QU9LC_jUbw>
Cc: IETF <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: Sat, 30 Apr 2016 02:23:29 -0000

SGkgUGV0ZS4NCkkgY29uY3VyIHRoYXQgdGhlcmUgd2FzIG5vIFdHLiAgU29ycnkgZm9yIGltcGx5
aW5nIHRoYXQgdGhlcmUgd2FzIG9uZS4gIEkgc2hvdWxkIGhhdmUgd3JpdHRlbiBCT0YgY29uc2Vu
c3VzIG9yIHNvbWV0aGluZyBsaWtlIHRoYXQuDQpBcyBmb3IgdGhlIHN1YnN0YW5jZSwgcGxlYXNl
IHNlZSBpbmxpbmUuDQpTdGVwaGFuDQoNCg0KDQoNCk9uIDQvMjkvMTYsIDEyOjU4LCAiUGV0ZSBS
ZXNuaWNrIiA8cHJlc25pY2tAcXRpLnF1YWxjb21tLmNvbT4gd3JvdGU6DQoNCj5PbiAyNSBBcHIg
MjAxNiwgYXQgMTY6MzEsIFN0ZXBoYW4gV2VuZ2VyIHdyb3RlOg0KPg0KPj4gT24gNC8yNS8xNiwg
MTM6MTUsICJpZXRmIG9uIGJlaGFsZiBvZiBKYXJpIEFya2tvIiANCj4+IDxpZXRmLWJvdW5jZXNA
aWV0Zi5vcmcgb24gYmVoYWxmIG9mIGphcmkuYXJra29AcGl1aGEubmV0PiB3cm90ZToNCj4+DQo+
Pj4NCj4+Pj4gLSBTZWN0aW9uIDUuNShDKTogVHdvIHRoaW5nczoNCj4+Pj4NCj4+DQo+PiBbLi4u
XQ0KPj4NCj4+Pj4gT0xEDQo+Pj4+ICAgICAgbXVzdCBlbnN1cmUgdGhhdCBzdWNoDQo+Pj4+ICAg
ICAgY29tbWl0bWVudHMgYXJlIGJpbmRpbmcgb24gYW55IHN1YnNlcXVlbnQgdHJhbnNmZXJlZSBv
ZiB0aGUNCj4+Pj4gICAgICByZWxldmFudCBJUFIuDQo+Pj4+IE5FVw0KPj4+PiAgICAgIG11c3Qg
ZW5zdXJlIHRoYXQgc3VjaCBjb21taXRtZW50cyBhcmUgYmluZGluZyBvbiBhIHRyYW5zZmVyZWUg
DQo+Pj4+IG9mDQo+Pj4+ICAgICAgdGhlIHJlbGV2YW50IElQUiwgYW5kIHRoYXQgc3VjaCB0cmFu
c2ZlcmVlIHdpbGwgdXNlIHJlYXNvbmFibGUNCj4+Pj4gICAgICBlZmZvcnRzIHRvIGVuc3VyZSB0
aGF0IHN1Y2ggY29tbWl0bWVudHMgYXJlIGJpbmRpbmcgb24gYQ0KPj4+PiAgICAgIHN1YnNlcXVl
bnQgdHJhbnNmZXJlZSBvZiB0aGUgcmVsZXZhbnQgSVBSLCBhbmQgc28gb24uDQo+Pj4+IEVORA0K
Pj4+Pg0KPj4+PiBUaGUgb2JqZWN0IG9mIHRoZSAic3Vic2VxdWVudCIgd2Fzbid0IGNsZWFyLCBz
byB0aGlzIGp1c3Qgc3BlbGxzIGl0IA0KPj4+PiBvdXQuIFdvcmR5LCBidXQgbW9yZSBwcmVjaXNl
Lg0KPj4+DQo+Pj4gUmlnaHQNCj4+DQo+PiBJ4oCZbSBub3Qgc3VyZSBJIGFncmVlIHRoYXQgdGhl
IG9iamVjdCBvZiDigJxzdWJzZXF1ZW50IHdhc27igJl0IGNsZWFyIA0KPj4gZnJvbSBjb250ZXh0
LiAgSG93ZXZlciwgSSBkb27igJl0IG1pbmQgdG8gc2VlIHRoYXQgZml4ZWQgaWYgb3RoZXJzIA0K
Pj4gZmVlbCBzby4gIEhvd2V2ZXIsIHRoZSBmaXggYXMgcHJvcG9zZWQgc2V0cyBhIHZlcnkgbG93
IHN0YW5kYXJkIA0KPj4gKHJlYXNvbmFibGUgZWZmb3J0cykgZm9yIGVuc3VyaW5nIHRoYXQgc3Vi
c2VxdWVudCB0cmFuc2ZlcmVlcyBhcmUgDQo+PiBib3VuZC4gVGhhdCBhIHN1YnN0YW50aWFsIGNo
YW5nZSBmcm9tIHRoZSBXRyBjb25zZW5zdXMsIGFuZCBJTU8gaW4gdGhlIA0KPj4gd3JvbmcgZGly
ZWN0aW9uLg0KPg0KPkxldCdzIGJlIGNsZWFyIHRoYXQgdGhlcmUgd2FzIG5vICJXRyBjb25zZW5z
dXMiIG9uIHRoaXMsIHNpbmNlIHRoZXJlIHdhcyANCj5ubyBXRy4gQnV0IGxldCdzIGFzc3VtZSB0
aGF0IHRoZSBjb25zZW5zdXMgb2YgdGhlIEJvRiB3YXMgZm9yIHNvbWV0aGluZyANCj5zdHJvbmcu
DQo+DQo+SSBkaXNhZ3JlZSB0aGF0ICJ1c2UgcmVhc29uYWJsZSBlZmZvcnRzIHRvIGVuc3VyZSIg
aXMgc3VjaCBhIGxvdyANCj5zdGFuZGFyZCwgYW5kIHRoZSBzdHJvbmdlciBsYW5ndWFnZSB5b3Ug
cHJvcG9zZSBjb25jZXJucyBtZToNCj4NCj4+IFdoYXQgd2Ugd2FudCB0byBhY2hpZXZlIGlzIHRo
YXQgaWYgQSBhc3NpZ25zIGEgcGF0ZW50IHRvIEIsIEIgYW5kIGFsbCANCj4+IGZ1cnRoZXIgdHJh
bnNmZXJlZXMgKEIgdG8gQywgQyB0byBELCBldGMuIGV0Yy4pIGFyZSBzaW1pbGFybHkgYm91bmQu
ICANCj4+IFdlIHdhbnQgdG8gbWFrZSBzdXJlIGlmIGFueSBvZiB0aGVzZSBlbnRpdGllcyBkb2Vz
buKAmXQgZmVlbCBib3VuZCBmb3IgDQo+PiB3aGF0ZXZlciByZWFzb24sIHRoZSBwYXRlbnQgaXMg
aGVsZCB1bmVuZm9yY2libGUgYnkgYSB3ZWxsLWluZm9ybWVkIA0KPj4gY291cnQuICBJdOKAmXMg
Y2xlYXIgdGhhdCB0aGlzIGlzIG11Y2ggbW9yZSBvbmVyb3VzIHRvIHRoZSANCj4+IHJpZ2h0aG9s
ZGVyLCBhbmQgbWF5IHdlbGwgbG93ZXIgdGhlIHZhbHVlIG9mIHRoZSBJUFIuDQo+Pg0KPj4gSSB3
b3VsZCBiZSBmaW5lIGlmIHRoZSBORVcgcGFydCB3b3VsZCBiZSByZXdvcmRlZCBhcyBmb2xsb3dz
Og0KPj4gTkVXDQo+PiAgICAgICBtdXN0IGVuc3VyZSB0aGF0IHN1Y2ggY29tbWl0bWVudHMgYXJl
IGJpbmRpbmcgb24gYSB0cmFuc2ZlcmVlIG9mDQo+PiAgICAgICB0aGUgcmVsZXZhbnQgSVBSLCBh
bmQgYWxzbyBiaW5kaW5nIG9uIGFueSBzdWJzZXF1ZW50IHRyYW5zZmVyZWVzDQo+PiBvZiB0aGUg
cmVsZXZhbnQgSVBSLg0KPj4gRU5EDQo+DQo+VGhpcyBzZWVtcyB0byByZXF1aXJlIHRoYXQgaWYg
bXkgSVBSIGlzIHRyYW5zZmVycmVkIDIwIHRpbWVzIG92ZXIgMjAgDQo+eWVhcnMsIEkgYW0gb24g
dGhlIGhvb2sgaW4gcGVycGV0dWl0eSB0byBhYnNvbHV0ZWx5IG1ha2Ugc3VyZSB0aGF0IHRoZSAN
Cj5uZXh0IHBlcnNvbiBkb3duIHRoZSBsaW5lIHN0aWNrcyB0byB0aGUgYWdyZWVtZW50LiBJJ20g
Y2VydGFpbmx5IHdpbGxpbmcgDQo+dG8gbWFrZSAqcmVhc29uYWJsZSogZWZmb3J0cyB0byBkbyBz
bywgYW5kIGl0IHdpbGwgYmUgdXAgdG8gYSBjb3VydCB0byANCj5kZXRlcm1pbmUgaWYgbXkgZWZm
b3J0cyB3ZXJlIHJlYXNvbmFibGUsIGJ1dCBJIGNlcnRhaW5seSBkb24ndCB3YW50IHRvIA0KPmJl
IGZvcmNlZCB0byBjb21wbGV0ZWx5IGluZGVtbmlmeSB0byAyMXN0IHBlcnNvbiBkb3duIHRoZSBs
aW5lLiAiVXNlIA0KPnJlYXNvbmFibGUgZWZmb3J0cyB0byBlbnN1cmUiIHNlZW1zIHJlYXNvbmFi
bGUuIE90aGVyd2lzZSwgaXQncyBub3QgDQo+Y2xlYXIgdG8gbWUgd2hhdCBJJ20gc2lnbmluZyB1
cCB0by4NCg0KRm9yIHRoZSBpbmZvcm1hdGlvbiBvZiB0aGUgYnJvYWRlciBjb21tdW5pdHkgaGVy
ZTogdGhlIHN1YmplY3Qgb2YgbGljZW5zaW5nIGNvbW1pdG1lbnRzIHRyYXZlbGluZyB3aXRoIHBh
dGVudHMgaXMgY3VycmVudGx5IGEgaG90IHRvcGljIGluIHNldmVyYWwgSVBSIHdvcmtpbmcgZ3Jv
dXBzIG9mIGEgbnVtYmVyIG9mIFNET3MuICBQZXRl4oCZcyBlbXBsb3llciBoYXMgYSBmYWlybHkg
c3Ryb25nIHBvc2l0aW9uIG9uIHRoYXQgbWF0dGVyLCBhbmQgc28gaGF2ZSBJIChhbmQgYSBidW5j
aCBvZiBvdGhlciBmb2xrcykuICBJIHdvdWxkbuKAmXQgY2FsbCB0aGlzIGEgcHJveHkgZGlzY3Vz
c2lvbiBoZXJlLS10aGUgSUVURuKAmXMgcG9saWN5IGlzIHRvbyBpbXBvcnRhbnQgZm9yIHRoYXQt
LWJ1dCBJ4oCZbSBub3Qgc3VycHJpc2VkIHRoYXQgaXQgY29tZXMgdXAgcHJvbWluZW50bHkgbm93
LiAgSG93ZXZlciwgSSBkbyBiZWxpZXZlIHRoYXQgdGhlIElFVEbigJlzIHBhdGVudCBwb2xpY3kg
cHJhY3RpY2UgaGFzIHR3byB1bmlxdWUgZmVhdHVyZXMsIGxhY2sgb2YgUkFORCBsaWNlbnNpbmcg
cmVxdWlyZW1lbnQgYmFzZWQgb24gbWVtYmVyc2hpcCBvciBwYXJ0aWNpcGF0aW9uIGFuZCB0aGUg
Y29tbW9uIHVzZSBvZiBub24tYXNzZXJ0IGNvdmVuYW50cywgdGhhdCBtYWtlIGEgY2xlYW4gc29s
dXRpb24gaGVyZSBldmVuIG1vcmUgaW1wb3J0YW50IHRoYW4gaW4sIHNheSwgdGhlIElUVS4NCg0K
TXkgdmlldyBpcyB0aGF0IGNlcnRhaW50eSBmb3IgdGhlIGltcGxlbWVudGVyIHRoYXQgbGljZW5z
aW5nIGNvbW1pdG1lbnRzIG1hZGUgc2hvdWxkIHRydW1wIGZyZWVkb20gb2YgYnVzaW5lc3MgZm9y
IHBhdGVudHMuICBJIHdhbnQgdGhhdCBhIGxpY2Vuc2luZyBjb21taXRtZW50IHRyYXZlbHMgd2l0
aCB0aGUgcGF0ZW50LCBqdXN0IGFzIGEgbGljZW5zZSB0cmF2ZWxzIHdpdGggdGhlIHBhdGVudCAo
dGhlIGxhdHRlciBhcyBhIG1hdHRlciBvZiBsYXcsIGFsbW9zdCBldmVyeXdoZXJlIGluIHRoZSB3
b3JsZCBhbmQgdW5kZXIgYWxtb3N0IGFsbCBjaXJjdW1zdGFuY2VzIHNob3J0IG9mIGJhbmtydXB0
Y3kpLg0KDQpJZiB5b3UgYXJlIG5vdCB3aWxsaW5nIHRvIHN0YW5kIGJlaGluZCB5b3VyIGNvbW1p
dG1lbnQgb25jZSBtYWRlLCBhbmQgZW5mb3JjZSBpdCB5b3Vyc2VsZiBpZiB2aW9sYXRlZCBieSBz
b21lIGd1eSBkb3duc3RyZWFtLCB0aGVuIGRvbuKAmXQgc2VsbCB5b3VyIHBhdGVudC4gIE9yLCBz
ZWxsIHlvdXIgcGF0ZW50IGJ1dCBtYWtlIHN1ZmZpY2llbnQgYWxsb3dhbmNlcyB0byBkZWFsIHdp
dGggdGhlIGNvbnNlcXVlbmNlcyBvZiBhIHNhbGUgdG8gYSBtaXNiZWhhdmluZyBlbnRpdHkgZG93
bnN0cmVhbS4NCg0KRXhhbXBsZTogQXNzdW1lIEEgbWFrZXMgYSBub24tYXNzZXJ0IGNvdmVuYW50
LCBhbmQgZnVydGhlciBhc3N1bWUgdGhhdCBhbiBpbXBsZW1lbnRhdGlvbiBpbmZyaW5nZXMgb24g
dGhlIHBhdGVudCBpbiBxdWVzdGlvbiAobWVhbmluZyBhbiBpbXBsZW1lbnRlciBuZWVkcyBhIGxp
Y2Vuc2Ugb3IgYSByZWxpYW5jZSBvbiBhIG5vbi1hc3NlcnQgY292ZW5hbnQpLiAgTWUsIHJlbHlp
bmcgb24gdGhpcyBjb3ZlbmFudCwgaW1wbGVtZW50IHRoZSB0ZWNobm9sb2d5IGFuZCBuZXZlciB2
aW9sYXRlIGNvbmRpdGlvbnMgaW4gdGhlIGNvdmVuYW50LS1mb3IgZXhhbXBsZSwgSSBuZXZlciBz
dWUgQSBhbmQgdGhlcmVieSB2aW9sYXRlIGEgcmVjaXByb2NpdHkgY29uZGl0aW9uIG9mIHRoZSBj
b3ZlbmFudC4gIEEgbGF0ZXIgYXNzaWducyB0byBCLCBCIGFzc2lnbnMgdG8gdHJvbGwgQywgQyBz
dWVzIG1lIG92ZXIgYSBwYXRlbnQgdmlvbGF0aW9uLiAgQiBhbmQgQyBtYXkgd2VsbCBub3QgaGF2
ZSBhIGRpc2Nsb3N1cmUgb2JsaWdhdGlvbiBpbiB0aGUgSUVURi4gIFRoZSBsYXdzdWl0IHdvdWxk
IGNvbWUgb3V0IG9mIHRoZSBibHVlIHRvIG1lLiAgVGhhdOKAmXMganVzdCB3cm9uZyBhbmQgZXhh
Y3RseSB3aGF0IHRoZSBwb2xpY3kgdHJpZXMgdG8gYXZvaWQuICBJZiB0aGUgbm9uLWFzc2VydCB3
b3VsZCB0cmF2ZWwgd2l0aCB0aGUgcGF0ZW50LCBvZiBjb3Vyc2UgSSBjb3VsZCBzdGlsbCBnZXQg
c3VlZCwgYnV0IHN1Y2ggYSBsYXdzdWl0IHdvdWxkIG1vc3QgbGlrZWx5IGhhdmUgYSByYXRoZXIg
c3dpZnQgcmVzb2x1dGlvbiBpbiBteSBmYXZvci4gIA0KDQpXaXRoIHlvdXIgbGFuZ3VhZ2UsIG9u
Y2UgQyBzdWVzIG1lLCBhcyB0aGUgdmVyeSBtaW5pbXVtIEkgd291bGQgaGF2ZSB0byBnbyB0aHJv
dWdoIGRpc2NvdmVyeSBvZiBib3RoIGFzc2lnbm1lbnRzICh0aGVyZSBnb2VzIHRoZSBmaXJzdCBt
aWxsaW9uIG9mIG1hbnkpLiAgSSBtYXkgb3IgbWF5IG5vdCB3aW4gdGhlIGxhd3N1aXQgYmFzZWQg
b24gYW4gZXhpc3RpbmcgY292ZW5hbnQgb3IgcmVzdWx0aW5nIGltcGxpZWQgbGljZW5zZS4gIE9u
Y2UgZG9uZSwgSSBjYW7igJl0IGV2ZW4gZ28gYWZ0ZXIgQSBmb3IgZGFtYWdlcyB1bmxlc3MgSSBj
b3VsZCBzaG93IEEgZm9yZ290IHRvIHB1dCBzb21lIOKAnGJlc3QgZWZmb3J04oCdIGxhbmd1YWdl
IGluIEEncyBhc3NpZ25tZW50IHBhcGVyd29yay4gIFRoYXTigJlzIG5vdCBlcXVpdGFibGUsIGJl
Y2F1c2UgQSBkaWQgcHJvZml0IGZyb20gdGhlIGFzc2lnbm1lbnQgb2YgdGhlIHBhdGVudC4gIA0K
DQo+DQo+Pj4+IC0gU2VjdGlvbiA3LCBwYXJhZ3JhcGggNjoNCg0KVGhpcyBpcyBJTU8gYSBtdWNo
IGxlc3MgY3JpdGljYWwgcG9pbnQgdGhlbiB0aGUgb25lIGFib3ZlLCBhbmQgaW4gZmFjdCBJIHdh
cyBtYWlubHkgYXNraW5nIGEgcXVlc3Rpb24gKG9mIGFuIElFVEYgc2VjdXJpdHkgY29uc2Vuc3Vz
IGFzIG9mIDIwMDUpIHJhdGhlciB0aGFuIHB1c2hpbmcgYSBwb2ludC4gIFN0aWxsLCBhcyB5b3Ug
YXJlIGFyZ3Vpbmcgc3Vic3RhbmNlIHJhdGhlciB0aGFuIHByb3ZpZGUgaGlzdG9yaWMgY29udGV4
dCwgcGxlYXNlIHNlZSBiZWxvdyBmb3IgbXkgb3duIGFyZ3VtZW50cy4NCg0KPj4+Pg0KPj4+PiBU
aGUgb25seSBjaGFuZ2UgaW4gdGhpcyBwYXJhZ3JhcGggZnJvbSAzOTc5IHdhcyB0byBhZGQgdGhl
IHdvcmQgDQo+Pj4+ICJhbGwiIGluIHRoZSBzZWNvbmQtdG8tbGFzdCBzZW50ZW5jZS4gTXkgbGF3
eWVyIGZyaWVuZHMgdGVsbCBtZSB0aGF0IA0KPj4+PiB0aGlzIGxpdHRsZSBjaGFuZ2UgaXMgb3Bl
bmluZyBhIGNhbiBvZiB3b3JtcywgaGF2aW5nIHRvIGRvIHdpdGggDQo+Pj4+IGxpY2Vuc2luZyB0
byBtYWtlcnMgb2YgcGFydHMgaW5zdGVhZCBvZiBpbXBsZW1lbnRlcnMgb2YgdGhlIHdob2xlIA0K
Pj4+PiBzcGVjaWZpY2F0aW9uLiBJIGRvbid0IHRoaW5rIHdlIG1lYW50IHRvIGNoYW5nZSB0aGUg
bWVhbmluZyBmcm9tIHRoZSANCj4+Pj4gMzk3OSBtZWFuaW5nLCBhbmQgSSBjZXJ0YWlubHkgZG9u
J3QgdGhpbmsgdGhhdCB3ZSBtZWFudCB0byBjaGFuZ2UgDQo+Pj4+IHNvbWUgaW1wbGljYXRpb24g
YWJvdXQgd2hldGhlciBmb2xrcyBpbiBnZW5lcmFsIG5lZWRlZCB0byBsaWNlbnNlIHRvIA0KPj4+
PiBwZW9wbGUgdGhhdCBtYWtlIHBhcnRzIHdoZXJlIHRoZXkgd291bGRuJ3QgaGF2ZSBiZWZvcmUu
IFdhcyB0aGVyZSANCj4+Pj4gc29tZXRoaW5nIHVuY2xlYXIgYWJvdXQgdGhhdCBzZW50ZW5jZSB0
aGF0IG5lZWRlZCB0aGUgd29yZCAiYWxsIiANCj4+Pj4gYWRkZWQgdG8gaXQ/IFdlIGFyZW4ndCBt
YWtpbmcgYSBzdWJzdGFudGl2ZSBjaGFuZ2UsIGFyZSB3ZT8gQ2FuIHdlIA0KPj4+PiBqdXN0IHN0
cmlrZSBpdD8gSXQgc2VlbWVkIHByZXR0eSBjbGVhciB0byBtZSBiZWZvcmUuDQo+Pj4NCj4+PiBB
Z3JlZQ0KPj4NCj4+IEnigJltIG5vdCBzdXJlIGhlcmUuDQo+PiBGb3IgY29udGV4dCwgdGhlIHBh
cmFncmFwaCBpcyBpbiBzZWN0aW9uIDcgb2YgUkZDMzk3OWJpcyAod2hpY2ggdXNlZCANCj4+IHRv
IGJlIHRoZSBzZWNvbmQgcGFyYWdyYXBoIG9mIHNlY3Rpb24gOCBvZiBSRkMzOTc5KS4gIFRoZSBz
ZW50ZW5jZSBpbiANCj4+IHF1ZXN0aW9uIGRlc2NyaWJlcyBhbiBwdXJwb3J0ZWQgSUVURiBjb25z
ZW5zdXMgZXN0YWJsaXNoZWQgaW4gDQo+PiBwcmUtUkZDMzk3OSB0aW1lcywgYXMgZm9sbG93cyAo
dGhlIGNyaXRpY2FsIGFuZCBuZXcg4oCcQUxM4oCdIGlzIA0KPj4gY2FwaXRhbGl6ZWQpOg0KPj4N
Cj4+IOKAnA0KPj4gQW4gSUVURiBjb25zZW5zdXMgaGFzIGRldmVsb3BlZCB0aGF0IG5vIG1hbmRh
dG9yeS10by1pbXBsZW1lbnQgDQo+PiBzZWN1cml0eSB0ZWNobm9sb2d5IGNhbiBiZSBzcGVjaWZp
ZWQgaW4gYW4gSUVURiBzcGVjaWZpY2F0aW9uIHVubGVzcyANCj4+IGl0IGhhcyBubyBrbm93biBJ
UFIgY2xhaW1zIGFnYWluc3QgaXQgb3IgYSByb3lhbHR5LWZyZWUgbGljZW5zZSBpcyANCj4+IGF2
YWlsYWJsZSB0byBBTEwgaW1wbGVtZW50ZXJzIG9mIHRoZSBzcGVjaWZpY2F0aW9uIHVubGVzcyB0
aGVyZSBpcyBhIA0KPj4gdmVyeSBnb29kIHJlYXNvbiB0byBkbyBzby4NCj4+IOKAnA0KPg0KPlJp
Z2h0LCB0aGUgb25seSBjaGFuZ2UgYmV0d2VlbiAzOTc5IGFuZCB0aGUgYWJvdmUgaXMgdGhlIGFk
ZGl0aW9uIG9mIHRoZSANCj53b3JkICJBTEwiIChub3QgaW4gYWxsIGNhcHMgaW4gMzk3OWJpcyku
DQo+DQo+PiBJIGFncmVlIHRoYXQgdGhlIHRpZ2h0ZW5lZCBsYW5ndWFnZSByZW1vdmVzIGFuIGFy
Z3VhYmx5IHVuY2xlYXIgDQo+PiBsb29waG9sZSB0aGF0IGhhcyBiZWVuIHByZXNlbnQgaW4gUkZD
Mzk3OSwgYW5kIHdoaWNoIFBldGXigJlzIA0KPj4gbGF3eWVyLWZyaWVuZHMgcHJvYmFibHkgd291
bGQgbGlrZSB0byBwcmVzZXJ2ZS4gIEhvd2V2ZXIsIGdlbmVyYWxseSANCj4+IHNwZWFraW5nLCBy
ZW1vdmluZyBsb29waG9sZXMgbGlrZSB0aGlzIGlzIGEgR29vZCBUaGluZywgdW5sZXNzIHRoZSAN
Cj4+IGNvbnNlbnN1cyBhdCB0aGUgdGltZSB3YXMgc3VjaCB0aGF0IHRoZXJlIG91Z2h0IHRvIGJl
IGEgbG9vcGhvbGUuICBJIA0KPj4gZGlkIG5vdCBmb2xsb3cgdGhlIGNvbnNlbnN1cyBwcm9jZXNz
IGluIHN1ZmZpY2llbnQgZGV0YWlsIHRvIGhhdmUgYW4gDQo+PiBvcGluaW9uLCBidXQgcGVyaGFw
cyBzZWN1cml0eSBhbmQgSVBSIGNvbnNjaW91cyBmb2xrcyBpbiB0aGUgSUVURiANCj4+IHJlbWVt
YmVyPw0KPg0KPldhaXQsIHdoYXQgImFyZ3VhYmx5IHVuY2xlYXIgbG9vcGhvbGUiIGRvIHlvdSB0
aGluayB3YXMgdGhlcmUgdGhhdCANCj5hZGRpbmcgImFsbCIgaW4gdGhlIGFib3ZlIHNlbnRlbmNl
IHRpZ2h0ZW5zPyANCg0KVGhlIGxvb3Bob2xlIGlzIGFzIGZvbGxvd3M6IEFyZ3VhYmx5LCB3aXRo
b3V0IHRoZSBBTEwsIHRoZXJlIGNvdWxkIGJlIHNvbWUgaW1wbGVtZW50ZXJzIG9mIG1hbmRhdG9y
eSB0byBpbXBsZW1lbnQgc2VjdXJpdHkgdGVjaG5vbG9naWVzIHRoYXQgYXJlIG5vdCBjb3ZlcmVk
IGJ5IHRoZSBSRkMzOTc5IGxhbmd1YWdlLiAgWW91IHlvdXJzZWxmIG1hZGUgdGhhdCBwb2ludCwg
Ynkgc2F5aW5nIHRoYXQgdGhlcmUgYWN0dWFsbHkgSVMgYSBkaWZmZXJlbmNlIGJldHdlZW4gcHJl
c2VuY2UgYW5kIGFic2VuY2Ugb2YgdGhlIOKAnEFMTCIuICBJIGdvdCBhbGFybWVkIGJ5IHlvdXIg
c3RhdGVtZW50LiAgSWYgeW91IGd1eXMgcmVhbGx5IHRoaW5rIHRoYXQgdGhlIGxhbmd1YWdlIGdp
dmVzIGVub3VnaCB3aWdnbGUtcm9vbSB0aGF0LCBmb3IgZXhhbXBsZSwgYSBsaWJyYXJ5L2NoaXAt
SVAgaG91c2Ugb2ZmZXJpbmcgYSBjaXBoZXIgY291bGQgY2hhcmdlIHBhdGVudCByb3lhbHRpZXMg
Zm9yIGEgbWFuZGF0b3J5IHRvIGltcGxlbWVudCBjeXBoZXIgdGVjaG5vbG9neSBldmVuIGlmIHRo
ZSBmaW5hbCBoYXJkd2FyZSBvciBzb2Z0d2FyZSBwcm9kdWN0IGNhbm5vdCwgdGhlbiBJIGZpbmQg
dGhhdCBhbGFybWluZy4gIFRoZXkgc2hvdWxkbuKAmXQgYmUgYWJsZSB0byBkbyBzbywgYmVjYXVz
ZSBhdCBsZWFzdCBteSB1bmRlcnN0YW5kaW5nIG9mIHRoZSBJRVRGIGNvbnNlbnN1cyBoZXJlIGhh
cyBiZWVuIHRoYXQgdGhleSB3b3VsZCBuZXZlciwgZXZlciBzZWxlY3QgYSBjaXBoZXIgYXMgbWFu
ZGF0b3J5IHRvIGltcGxlbWVudCB1bmxlc3MgdGhhdCBjaXBoZXIgaXMgZnJlZSBvZiBwYXRlbnQg
cm95YWx0aWVzLiAgDQoNCj5DYWxsaW5nIGl0IGEgImxvb3Bob2xlIiANCj5pbXBsaWVzIHRoYXQg
c29tZWhvdyB0aGUgSUVURiBpbnRlbnRpb24gd2FzIHRvIGRpc2FsbG93IHNvbWV0aGluZyB0aGF0
IA0KPnRoZSBjdXJyZW50IHRleHQgYWxsb3dzLiBXaGF0IGlzIHRoYXQgc29tZXRoaW5nIHRoYXQg
eW91IHRoaW5rIHdlIG91Z2h0IA0KPnRvIGJlIHJlbW92aW5nPw0KDQpTZWUgYWJvdmUuDQoNCj4N
Cj5JIGtub3cgdGhhdCBteSBsYXd5ZXIgZnJpZW5kIHdhcyBjb25jZXJuZWQgbm90IGFib3V0IHNl
Y3VyaXR5IHRlY2hub2xvZ3kgDQo+cGVyIHNlLCBidXQgdGhlIGlzc3VlIG9mIGxpY2Vuc2luZyBs
ZXZlbHMgbW9yZSBnZW5lcmFsbHkuIEknbSBwcmV0dHkgDQo+c3VyZSB3ZSBvbmx5IHdhbnRlZCB0
byB0YWxrIGFib3V0IHJlcXVpcmluZyByb3lhbHR5LWZyZWUgbGljZW5zaW5nIGZvciANCj5zZWN1
cml0eSBwcm90b2NvbHMgc3BlY2lmaWNhbGx5IGFuZCBuZXZlciBpbnRlbmRlZCB0byByZXF1aXJl
IHBhcnRpY3VsYXIgDQo+a2luZHMgb2YgbGljZW5zaW5nIGFjcm9zcyB0aGUgYm9hcmQuIEVpdGhl
ciB3YXksIEkgdGhpbmsgdGhhdCB0aGUgDQo+b3JpZ2luYWwgdGV4dCB3YXMgcGVyZmVjdGx5IGNs
ZWFyIGFuZCBoYWQgbm8gbG9vcGhvbGVzLg0KDQpBZ2FpbiwgdGhlIHRleHQgYWJvdmUgaXMgT05M
WSByZWxhdGVkIHRvIG1hbmRhdG9yeSB0byBpbXBsZW1lbnQgc2VjdXJpdHkgdGVjaG5vbG9neS4g
IE5vdGhpbmcgKGJ1dCBjb21tb24gc2Vuc2UgYW5kIHRoZSBsYXcsIGluY2x1ZGluZyBhbnRpdHJ1
c3QgbGF3KSBwcmV2ZW50cyB5b3UgZ3V5cyB0byBjaG9vc2Ugd2hhdGV2ZXIgbGFuZ3VhZ2UgeW91
IHByZWZlciBpbiB5b3VyIGZyZWUtZm9ybSBsaWNlbnNpbmcgZGVjbGFyYXRpb24uDQoNClN0ZXBo
YW4NCg0KPg0KPlNvLCB3aHkgYXJlIHdlIGFkZGluZyAiYWxsIj8gV2hhdCBsb29waG9sZSBhcmUg
d2UgdHJ5aW5nIHRvIGNsb3NlPyBJZiANCj50aGVyZSBpcyBub25lLCBsZXQncyBzdHJpa2UgImFs
bCIgYW5kIHVzZSB0aGUgb3JpZ2luYWwgdGV4dC4NCj4NCj5wcg0KPi0tIA0KPlBldGUgUmVzbmlj
ayA8aHR0cDovL3d3dy5xdWFsY29tbS5jb20vfnByZXNuaWNrLz4NCj5RdWFsY29tbSBUZWNobm9s
b2dpZXMsIEluYy4gLSArMSAoODU4KTY1MS00NDc4DQo=


From nobody Sat Apr 30 01:41:41 2016
Return-Path: <peter@akayla.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 0383C12B006; Sat, 30 Apr 2016 01:41:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.92
X-Spam-Level: 
X-Spam-Status: No, score=-1.92 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01] 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 PI1DzYrdK-Gx; Sat, 30 Apr 2016 01:41:35 -0700 (PDT)
Received: from p3plsmtpa06-10.prod.phx3.secureserver.net (p3plsmtpa06-10.prod.phx3.secureserver.net [173.201.192.111]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E2CB012B056; Sat, 30 Apr 2016 01:41:34 -0700 (PDT)
Received: from spectre ([173.8.184.78]) by p3plsmtpa06-10.prod.phx3.secureserver.net with  id oYha1s0021huGat01YhaSE; Sat, 30 Apr 2016 01:41:34 -0700
From: "Peter Yee" <peter@akayla.com>
To: <draft-ietf-isis-node-admin-tag.all@ietf.org>
Subject: Gen-ART LC review of draft-ietf-isis-node-admin-tag-08
Date: Sat, 30 Apr 2016 01:41:41 -0700
Message-ID: <00ef01d1a2bc$1e6a0130$5b3e0390$@akayla.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AdGiqAdNKLGcXI+xSwe3lnyhPEdRpQ==
Content-Language: en-us
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/Mb6DA9oggL5Fwj5l9NqCiNsIGV0>
Cc: gen-art@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: Sat, 30 Apr 2016 08:41:37 -0000

I am the assigned Gen-ART reviewer for this draft.  The General Area Review
Team (Gen-ART) reviews all IETF documents being processed by the IESG for
the IETF Chair.  Please treat these comments just like any other last call
comment.  For background on Gen-ART, please see the FAQ at
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>

Document: draft-ietf-isis-node-admin-tag-08
Reviewer: Peter Yee
Review Date: April 27, 2016
IETF LC End Date: April 29, 2016
IESG Telechat date: May 5, 2016

Summary: This draft is basically ready for publication as a Standards Track
RFC, but has some issues that should be fixed/considered before publication.
[Ready with issues]

This draft defines a means to carry additional per-node administrative tags
with the IS-IS protocol.  These tags can be used along with local policy to
simplify the management of routing and path selection.  This specification
gives informative examples of such tag usage but does not otherwise
prescribe the meaning of the tags.

This review was generated prior to the release of draft -09 (but not keyed
in until April 29th), but many of the issues and nits noted below remain in
draft -09.  Obviously, some of my comments no longer apply.  I'll address
draft -09 specifically for the telechat review, but you should look at the
points here prior to that review to save time.  Given that draft -09
substantially reduces Section 5, I've removed my comments regarding that
section as well as in a few other places.

Major issues: None

Minor issues:

Page 4, last partial paragraph: the number 63 is given for the maximum
number of per-node administrative tags that can be carried in a sub-TLV.
Given the maximum length of a sub-TLV is 250 octets (and 2 octets are
otherwise used by type and length), I would argue that the correct number
here is 62 (62*4 = 248).  Also, I would delete the text starting at "and".
In all cases, when more than 62 tags are used, a single sub-TLV will not
provide sufficient space.

Page 5, 1st partial paragraph, 1st full sentence: Sub-TLV values are given
here as cumulative.  Is there any need or desire to be able to subtract
tags?  How would a router disassociate itself from a tag that was no longer
relevant to the router?  This ability is implied in Section 4.3, 2nd
paragraph, but that conflicts with the statement given here.  In general, I
believe the ability to reset the flooded tags associated with a router or to
delete a tag is underspecified.

Page 6, 1st partial paragraph, 1st sentence: Care to define "reasonably
small"?  Previously, the ability to send more than 63 (or perhaps 62, see
above) tags was specified in section 3.1.  What's the limit to
reasonableness?  (Not that an exact number seems to matter at all for the
purposes of this specification, which is agnostic to the specific number or
the use of the tags.)

Page 6, Section 4.3, 2nd paragraph: This paragraph implies that a large set
(greater than 62 at least) of sub-TLVs will have to be sent in multiple
Router CAPABILITY TLVs and those TLVs must(?) occur in a single Link-State
PDU.  Or how is the receiving router to know that it has the complete set of
tags?  Also, the implication seems to be that while section 3.1 indicates a
strictly cumulative capability, there must be someway of terminating those
cumulative changes and allowing a reset.  What is that signaling mechanism?

Nits:

General:

The use of capitalization of Per-node administrative tag varies throughout
the document.  It seems clear that you mean for it to be written as
"Per-node Administrative Tag" when referring to the name of sub-TLV.  For
other uses, I would suggest using "per-node administrative tag"
consistently.  Use that to replace "Per-node administrative tag".

Separate parenthetical elements from the preceding and following words with
a space.  These aren't function calls. ;-)

Replace any use of "per-node admin tag" with "per-node administrative tag".
The shortening is fine for the document header which would otherwise become
unreadable.

And change all of my references to "per-node" to "node", since draft -09
drops the "per-". :-)

Replace "TLV 242" with "the Router CAPABILITY TLV".  

Specific:

 Page 1, Abstract:  delete the first comma in the Abstract.

Page 3, first paragraph after the lettered items, 3rd sentence: insert "the"
before "Router".

Page 3, Section 2, 1st sentence: change "Tag" to "tag".

Page 3, Section 2, 3rd sentence: insert "a" before "certain".

Page  3, Section 3, 1st paragraph, 1st sentence: change "TLV-242" to "TLV
(IS-IS TLV type 242)" and delete the closing parenthesis after "[RFC4971".

Page 3, Section 3, 1st paragraph, 3rd sentence: change "the same" to "it".
Change "they" to "it".  Change "specfied" to "specified".  Insert "the"
before "originating".  Delete "the" before "other".

Page 3, Section 3, 1st paragraph, 5th sentence: change "are" to "is".

Page 3, Section 3, 1st paragraph, 6th sentence: delete the comma.

Page 3, Section 3, 1st paragraph, 7th sentence: change "Operator" to "The
operator".

Page 4, Section 3, last paragraph, 1st sentence: insert "the" before
"Per-node" (after having changed "per-node" to "Per-node").

Page 4, Section 3, last paragraph, 2nd sentence: change "topology specific"
to "topology-specific".

Page 4, Section 3.1, 1st paragraph, 1st sentence: change "ISIS" to "IS-IS".

Page 4, Section 3.1, Length definition: change "A" to "An".

Page 4, Section 3.1, Value definition: change "sequence" to "set".  Sequence
would seem to imply order which is contradicted by Section 4.1.  Change "4
octets" to "4-octet values".

Page 5, 1st partial paragraph, 1st full sentence: append a comma after
"such" and insert "each" before "occurrence".

Page 5, Section 4.1, 1st paragraph, 1st sentence: change "Meaning" to "The
meaning".

Page 5, Section 4.1, 1st paragraph, 2nd sentence: change "Router" to "A
router".

Page 5, Section 4.1, 2nd paragraph, last sentence: append a comma after
"change".

Page 5, Section 4.1, 4th paragraph, 2nd sentence: delete "The".  Change
"TLVs" to "sub-TLVs".  Change "adminsitrative" to "administrative".

Page 5, Section 4.1, 4th paragraph: the paragraph, starting at "The list of
per-node" is pretty much redundant given the admonition in the first
sentence of the previous paragraph.  Perhaps delete it rather than belabor
the point?

Page 5, Section 4.1, 1st paragraph, 4th sentence: change "well known" to
"well-known".  Change "capability" to "CAPABILITY".

Page 6, 1st partial paragraph, 2nd sentence: insert "the" before
"reachability".

Page 6, Section 4.3, 1st paragraph, 1st sentence: delete "(TLV-242)".

Page 6, Section 4.3, 1st paragraph, 3rd sentence: change "an" to "a".  Based
on Section 3.1, I might change "changes" to "adds to" because Section 3.1
specifies that sub-TLVs are cumulative.

Page 10, Section 7, 1st paragraph, 3rd sentence: change "ISIS" to "IS-IS".
Change "is" to "are".  

Page 10, Section 7, 2nd paragraph, 2nd sentence: insert "the" before "case".
Insert "the" before "forwarding".  Insert a space before "and".

Page 12, Section 8, 2nd sentence: insert "The" before "YANG".

Page 12, Section 8, 3rd sentence: insert "The" before "IS-IS".  Insert "the"
before "routing".

Page 12, Section 9, item i): why is the sub-TLV name hyphenated here and not
elsewhere?

Page 12, Section 10: append a comma after "Chunduri".


From nobody Sat Apr 30 02:05:01 2016
Return-Path: <stewart.bryant@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 9E25C12B02E for <ietf@ietfa.amsl.com>; Sat, 30 Apr 2016 02:04:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.677
X-Spam-Level: 
X-Spam-Status: No, score=-1.677 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, LOTS_OF_MONEY=0.001, MISSING_HEADERS=1.021, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=no 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 bHG8dqDqoxxT for <ietf@ietfa.amsl.com>; Sat, 30 Apr 2016 02:04:58 -0700 (PDT)
Received: from mail-wm0-x234.google.com (mail-wm0-x234.google.com [IPv6:2a00:1450:400c:c09::234]) (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 608B912B017 for <ietf@ietf.org>; Sat, 30 Apr 2016 02:04:57 -0700 (PDT)
Received: by mail-wm0-x234.google.com with SMTP id e201so52836092wme.0 for <ietf@ietf.org>; Sat, 30 Apr 2016 02:04:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=subject:references:cc:from:message-id:date:user-agent:mime-version :in-reply-to; bh=YA7Spa/ehKos4yV+br89X+9+jg7GoIAmiuhrXLcTT6I=; b=zs3dc8SWpLHT8nRtaHHCsClfPQCmCXkhlbVnUl3yx59/YzGk/PDZA8k2c+P+ltLfEs QPwKokvk0QYd+ptcgk9l4v3rKJl42SFTyt1a08bbWOpmWP5ru28DtB3RUkDVd6suPn5j sXof+zq5xWikS10YmmfNDMzBIik9yv7uw/yahjCnlBUIZKbRbclL3bArD4hv3+ifNOEq ZlmWEkzN0alzLl5sesgHvCrtRo0ZBsj7xk5HYRLHKfVKVmW52WfkHLommKNK+cwVfRHb moLscMvkaNFi1xQ1YNy0OMts6Htg3538CjBPyGa9uvdR6G/ggoJwq/0GDrS8MlNuL9Lx kBEA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to; bh=YA7Spa/ehKos4yV+br89X+9+jg7GoIAmiuhrXLcTT6I=; b=KNQbmrkBTvnk2+QIq60wNUq6g9gAn91Mg7QJ1MhIoo3ncYVt3o+TcJs0hNIniazuS/ N8AJswUk2e0a6dBqnqqxOe54kbkLH+e6XEPChvZcMdVkZB3rLKoHwKKzRfHSHx7+8UYS cAkP6G6apIGTD/62Wz0CQ/W6kogz+rlUY8VDWBhp/OoOm+737yXxZAZaIZ70HGHCouZQ Lf5HQ8Ry3FkU312nZO7Lba6BORvp0WUxwOx8egtEL/woOftfmlSQ4SMze0/hJNnzQzFK 2JaW6yo0aR3t0K5al486LD7qaaU0z6JxpBqZ1X7NrgieHhJXkMALqGpxf767Qe5DMHST jOUQ==
X-Gm-Message-State: AOPr4FUGMyboP3xb5Z7/a7FTseFZs0/rX5sj4zzLtTijZAKQ/xHtksyVGELi6QxoYU6Kcg==
X-Received: by 10.194.14.130 with SMTP id p2mr28017113wjc.173.1462007095833; Sat, 30 Apr 2016 02:04:55 -0700 (PDT)
Received: from [192.168.2.126] (host213-123-124-182.in-addr.btopenworld.com. [213.123.124.182]) by smtp.gmail.com with ESMTPSA id u12sm7253855wmu.12.2016.04.30.02.04.54 for <ietf@ietf.org> (version=TLSv1/SSLv3 cipher=OTHER); Sat, 30 Apr 2016 02:04:54 -0700 (PDT)
Subject: Re: Last Call on draft-bradner-rfc3979bis-08.txt ("Intellectual Property Rights in IETF Technology")
References: <0000431F-F977-4A24-BA4D-064F740977A0@piuha.net> <E7E31E22-1C86-40C4-BC5B-F65132015EF5@qti.qualcomm.com> <6CA3C554-0FF6-4779-80B9-C75698FB61C1@piuha.net> <EC4CBF0D-1B7C-4FB5-85EA-E622B24E9B9A@stewe.org> <9AFC22D7-C509-4765-AAC9-3096F188C4C6@qti.qualcomm.com>
Cc: IETF <ietf@ietf.org>
From: Stewart Bryant <stewart.bryant@gmail.com>
Message-ID: <57247534.3060609@gmail.com>
Date: Sat, 30 Apr 2016 10:04:52 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2
MIME-Version: 1.0
In-Reply-To: <9AFC22D7-C509-4765-AAC9-3096F188C4C6@qti.qualcomm.com>
Content-Type: multipart/alternative; boundary="------------090605060601040801030509"
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/mmRNYHtkpSfKto-XNI-AZdIyDI4>
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, 30 Apr 2016 09:04:59 -0000

This is a multi-part message in MIME format.
--------------090605060601040801030509
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit


    l. "Reasonably and personally known": means something an individual
       knows personally or, because of the job the individual holds,
       would reasonably be expected to know.  This wording is used to
       indicate that an organization cannot purposely keep an individual
       in the dark about patents or patent applications just to avoid the
       disclosure requirement.  But this requirement should not be
       interpreted as requiring the IETF Contributor or Participant (or
       his or her represented organization, if any) to perform a patent
       search to find applicable IPR.


How do we deal with the case of a an individual that was exposed to IPR 
in a previous
employment, but no longer having access to the records of that employer is
uncertain about whether they know of such IPR? A third party disclosure 
is one
solution, but without access to records it may not be possible to 
sufficiently
identify the patent such that the legal department can file the disclosure.


6. Failure to Disclose

    There may be cases in which individuals are not permitted by their
    employers or by other factors to disclose the existence or substance
    of patent applications or other IPR.  Since disclosure is required
    for anyone making a Contribution or participating in IETF activities,
    a person who is not willing or able to disclose IPR for this reason,
    or any other reason, must not contribute to or participate in IETF
    activities with respect to technologies that he or she reasonably and
    personally knows to be Covered by IPR which he or she will not
    disclose, unless that person knows that his or her employer or
    sponsor will make the required disclosures on his or her behalf.

    Contributing to or participating in IETF activities about a
    technology without making required IPR disclosures is a violation of
    IETF process.

    In addition to any remedies the IESG may consider other actions. See
    [RFC6701] for details.


This assumes that the individual intends to support the technology that they
know to be encumbered.

Surely we need to also consider the case of an individual that although 
unable
to disclose IPR without breaching confidentiality is arguing for an 
alternative
unencumbered solution.

We also need to visit the matter of licence fees.

The IETF has a policy of not discussing licence terms, and in particular 
licence fees
in determining whether a technology is to be adopted or avoided. This 
policy does
not properly consider the extremity of the range of devices we support. 
What is
technically the best solution for a $1m router despite a significant 
licence fee
may not be viable for $0.01 IoT sensor because of the licence fee. Yet 
the WG is
not permitted to discuss those economics.

- Stewart





--------------090605060601040801030509
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta content="text/html; charset=utf-8" http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <br>
    <pre style="box-sizing: border-box; overflow: auto; font-family: 'PT Mono', Monaco, monospace; font-size: 14px; display: block; padding: 10px; margin: 0px 0px 10.5px; line-height: 1.214; color: rgb(0, 0, 0); word-break: break-all; word-wrap: break-word; border: 1px solid rgb(204, 204, 204); border-radius: 4px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; widows: 1; word-spacing: 0px; -webkit-text-stroke-width: 0px; background-color: rgb(255, 253, 245);">   l. "Reasonably and personally known": means something an individual
      knows personally or, because of the job the individual holds,
      would reasonably be expected to know.  This wording is used to
      indicate that an organization cannot purposely keep an individual
      in the dark about patents or patent applications just to avoid the
      disclosure requirement.  But this requirement should not be
      interpreted as requiring the IETF Contributor or Participant (or
      his or her represented organization, if any) to perform a patent
      search to find applicable IPR.</pre>
    <br>
    How do we deal with the case of a an individual that was exposed to
    IPR in a previous<br>
    employment, but no longer having access to the records of that
    employer is<br>
    uncertain about whether they know of such IPR? A third party
    disclosure is one<br>
    solution, but without access to records it may not be possible to
    sufficiently<br>
    identify the patent such that the legal department can file the
    disclosure.<br>
    <br>
    <br>
    <pre style="box-sizing: border-box; overflow: auto; font-family: 'PT Mono', Monaco, monospace; font-size: 14px; display: block; padding: 10px; margin: 0px 0px 10.5px; line-height: 1.214; color: rgb(0, 0, 0); word-break: break-all; word-wrap: break-word; border: 1px solid rgb(204, 204, 204); border-radius: 4px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; widows: 1; word-spacing: 0px; -webkit-text-stroke-width: 0px; background-color: rgb(255, 253, 245);"><span class="m_h" style="box-sizing: border-box;">6. Failure to Disclose</span>

   There may be cases in which individuals are not permitted by their
   employers or by other factors to disclose the existence or substance
   of patent applications or other IPR.  Since disclosure is required
   for anyone making a Contribution or participating in IETF activities,
   a person who is not willing or able to disclose IPR for this reason,
   or any other reason, must not contribute to or participate in IETF
   activities with respect to technologies that he or she reasonably and
   personally knows to be Covered by IPR which he or she will not
   disclose, unless that person knows that his or her employer or
   sponsor will make the required disclosures on his or her behalf.

   Contributing to or participating in IETF activities about a
   technology without making required IPR disclosures is a violation of
   IETF process.

   In addition to any remedies the IESG may consider other actions. See
   [RFC6701] for details.
</pre>
    <br>
    This assumes that the individual intends to support the technology
    that they<br>
    know to be encumbered.<br>
    <br>
    Surely we need to also consider the case of an individual that
    although unable<br>
    to disclose IPR without breaching confidentiality is arguing for an
    alternative<br>
    unencumbered solution.<br>
    <br>
    We also need to visit the matter of licence fees.<br>
    <br>
    The IETF has a policy of not discussing licence terms, and in
    particular licence fees<br>
    in determining whether a technology is to be adopted or avoided.
    This policy does<br>
    not properly consider the extremity of the range of devices we
    support. What is<br>
    technically the best solution for a $1m router despite a significant
    licence fee<br>
    may not be viable for $0.01 IoT sensor because of the licence fee.
    Yet the WG is<br>
    not permitted to discuss those economics.<br>
    <br>
    - Stewart<br>
    <br>
    <br>
    <br>
    <br class="Apple-interchange-newline">
  </body>
</html>

--------------090605060601040801030509--


From nobody Sat Apr 30 02:10:47 2016
Return-Path: <pushpasis.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 1E97112B051; Sat, 30 Apr 2016 02:10:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 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, RCVD_IN_DNSWL_LOW=-0.7, 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 ShpAqXudY-m4; Sat, 30 Apr 2016 02:10:43 -0700 (PDT)
Received: from mail-pa0-x22b.google.com (mail-pa0-x22b.google.com [IPv6:2607:f8b0:400e:c03::22b]) (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 0CD2C12B017; Sat, 30 Apr 2016 02:10:43 -0700 (PDT)
Received: by mail-pa0-x22b.google.com with SMTP id bt5so54632106pac.3; Sat, 30 Apr 2016 02:10:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=QG9He10IRV5b9U4UEPty4UZGaiFp6hPd0KgICW4F7Ls=; b=w7R4k1FIauLG5QtQgpbp4mhVpQxc4Q3eUxV2NSXwNVfTO2256hiop+qX1GbQk9A50c iqNJtKqg2IESD/WI5YdmQQCQ/f/OAd7RljDqmQ8/mlpUWV2vkb11dPDUN7GOcnTIKIEk fc2CJgC0x61KVmW4j2hEFTzz3mW5gaQSCO5Z8nXJ5MHLjXxEt1BtPzUuDir50ID5GgUs 4j4fB7CY3QTdWioIh6mwSKF4455BAC6Ou3V1vol8ZHkB7nL1bWEYPReGOL0ySkdcRapa 3nirEicXw6r1kMqNZMMj6pcOfGAucCv/QLZurEfQVQt47KBUlctMT+7bMNOQzUDp2S9N EpoA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=QG9He10IRV5b9U4UEPty4UZGaiFp6hPd0KgICW4F7Ls=; b=MVF/mVdeYoAmqoLwCNPYaCMDasWDltxZoSY5DKCSTtW6sK+7Aaafzzsv7s9rLWfl3j OGVuOFlI6nD4d4c+1uSFBuWdF8er5+hZ7YzfnmSwDSzNOAd/XFlyZgpnmR1UQg96pnna oWp75qR+CRGH+GIbSOBQixEgPQ6/KWgjrKK7SjQ1WxA4ShTqSQ+6J3d/15tp83RwcAFz 4ffkRo3Qbgp1JhKxSlvTQyI8zW4g6Ti0iG5tfMvcrcjRr+/Eh42TpP4oItfxTKnDwpqW qS3kw4xsQgQa23dr3w1PTf7owPT+j/2DY+9vGc7NpxNThNlU2Tb7/ISHmyJgSFN7wK0M vRww==
X-Gm-Message-State: AOPr4FV8yquB0W4Vt5Af1+k6PeNju0dugCzb4eayib+ORiAy6b2k5M4We4AOmlhTj9Manw==
X-Received: by 10.66.175.110 with SMTP id bz14mr35545105pac.41.1462007442648;  Sat, 30 Apr 2016 02:10:42 -0700 (PDT)
Received: from [192.168.1.235] ([103.6.157.63]) by smtp.gmail.com with ESMTPSA id g5sm36648931pac.1.2016.04.30.02.10.40 (version=TLSv1/SSLv3 cipher=OTHER); Sat, 30 Apr 2016 02:10:42 -0700 (PDT)
Subject: Re: Gen-ART LC review of draft-ietf-isis-node-admin-tag-08
To: Peter Yee <peter@akayla.com>, draft-ietf-isis-node-admin-tag.all@ietf.org
References: <00ef01d1a2bc$1e6a0130$5b3e0390$@akayla.com>
From: Pushpasis Sarkar <pushpasis.ietf@gmail.com>
Message-ID: <5724768F.9060407@gmail.com>
Date: Sat, 30 Apr 2016 14:40:39 +0530
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0
MIME-Version: 1.0
In-Reply-To: <00ef01d1a2bc$1e6a0130$5b3e0390$@akayla.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/dV6LB_zULsYGCCD62nv16ckiMEs>
Cc: gen-art@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: Sat, 30 Apr 2016 09:10:45 -0000

Hi Peter,

Thanks a lot for the comments. I will address them soon in the next version.

Best Regards,
-Pushpasis

On Saturday 30 April 2016 02:11 PM, Peter Yee wrote:
> I am the assigned Gen-ART reviewer for this draft.  The General Area Review
> Team (Gen-ART) reviews all IETF documents being processed by the IESG for
> the IETF Chair.  Please treat these comments just like any other last call
> comment.  For background on Gen-ART, please see the FAQ at
> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>
>
> Document: draft-ietf-isis-node-admin-tag-08
> Reviewer: Peter Yee
> Review Date: April 27, 2016
> IETF LC End Date: April 29, 2016
> IESG Telechat date: May 5, 2016
>
> Summary: This draft is basically ready for publication as a Standards Track
> RFC, but has some issues that should be fixed/considered before publication.
> [Ready with issues]
>
> This draft defines a means to carry additional per-node administrative tags
> with the IS-IS protocol.  These tags can be used along with local policy to
> simplify the management of routing and path selection.  This specification
> gives informative examples of such tag usage but does not otherwise
> prescribe the meaning of the tags.
>
> This review was generated prior to the release of draft -09 (but not keyed
> in until April 29th), but many of the issues and nits noted below remain in
> draft -09.  Obviously, some of my comments no longer apply.  I'll address
> draft -09 specifically for the telechat review, but you should look at the
> points here prior to that review to save time.  Given that draft -09
> substantially reduces Section 5, I've removed my comments regarding that
> section as well as in a few other places.
>
> Major issues: None
>
> Minor issues:
>
> Page 4, last partial paragraph: the number 63 is given for the maximum
> number of per-node administrative tags that can be carried in a sub-TLV.
> Given the maximum length of a sub-TLV is 250 octets (and 2 octets are
> otherwise used by type and length), I would argue that the correct number
> here is 62 (62*4 = 248).  Also, I would delete the text starting at "and".
> In all cases, when more than 62 tags are used, a single sub-TLV will not
> provide sufficient space.
>
> Page 5, 1st partial paragraph, 1st full sentence: Sub-TLV values are given
> here as cumulative.  Is there any need or desire to be able to subtract
> tags?  How would a router disassociate itself from a tag that was no longer
> relevant to the router?  This ability is implied in Section 4.3, 2nd
> paragraph, but that conflicts with the statement given here.  In general, I
> believe the ability to reset the flooded tags associated with a router or to
> delete a tag is underspecified.
>
> Page 6, 1st partial paragraph, 1st sentence: Care to define "reasonably
> small"?  Previously, the ability to send more than 63 (or perhaps 62, see
> above) tags was specified in section 3.1.  What's the limit to
> reasonableness?  (Not that an exact number seems to matter at all for the
> purposes of this specification, which is agnostic to the specific number or
> the use of the tags.)
>
> Page 6, Section 4.3, 2nd paragraph: This paragraph implies that a large set
> (greater than 62 at least) of sub-TLVs will have to be sent in multiple
> Router CAPABILITY TLVs and those TLVs must(?) occur in a single Link-State
> PDU.  Or how is the receiving router to know that it has the complete set of
> tags?  Also, the implication seems to be that while section 3.1 indicates a
> strictly cumulative capability, there must be someway of terminating those
> cumulative changes and allowing a reset.  What is that signaling mechanism?
>
> Nits:
>
> General:
>
> The use of capitalization of Per-node administrative tag varies throughout
> the document.  It seems clear that you mean for it to be written as
> "Per-node Administrative Tag" when referring to the name of sub-TLV.  For
> other uses, I would suggest using "per-node administrative tag"
> consistently.  Use that to replace "Per-node administrative tag".
>
> Separate parenthetical elements from the preceding and following words with
> a space.  These aren't function calls. ;-)
>
> Replace any use of "per-node admin tag" with "per-node administrative tag".
> The shortening is fine for the document header which would otherwise become
> unreadable.
>
> And change all of my references to "per-node" to "node", since draft -09
> drops the "per-". :-)
>
> Replace "TLV 242" with "the Router CAPABILITY TLV".
>
> Specific:
>
>   Page 1, Abstract:  delete the first comma in the Abstract.
>
> Page 3, first paragraph after the lettered items, 3rd sentence: insert "the"
> before "Router".
>
> Page 3, Section 2, 1st sentence: change "Tag" to "tag".
>
> Page 3, Section 2, 3rd sentence: insert "a" before "certain".
>
> Page  3, Section 3, 1st paragraph, 1st sentence: change "TLV-242" to "TLV
> (IS-IS TLV type 242)" and delete the closing parenthesis after "[RFC4971".
>
> Page 3, Section 3, 1st paragraph, 3rd sentence: change "the same" to "it".
> Change "they" to "it".  Change "specfied" to "specified".  Insert "the"
> before "originating".  Delete "the" before "other".
>
> Page 3, Section 3, 1st paragraph, 5th sentence: change "are" to "is".
>
> Page 3, Section 3, 1st paragraph, 6th sentence: delete the comma.
>
> Page 3, Section 3, 1st paragraph, 7th sentence: change "Operator" to "The
> operator".
>
> Page 4, Section 3, last paragraph, 1st sentence: insert "the" before
> "Per-node" (after having changed "per-node" to "Per-node").
>
> Page 4, Section 3, last paragraph, 2nd sentence: change "topology specific"
> to "topology-specific".
>
> Page 4, Section 3.1, 1st paragraph, 1st sentence: change "ISIS" to "IS-IS".
>
> Page 4, Section 3.1, Length definition: change "A" to "An".
>
> Page 4, Section 3.1, Value definition: change "sequence" to "set".  Sequence
> would seem to imply order which is contradicted by Section 4.1.  Change "4
> octets" to "4-octet values".
>
> Page 5, 1st partial paragraph, 1st full sentence: append a comma after
> "such" and insert "each" before "occurrence".
>
> Page 5, Section 4.1, 1st paragraph, 1st sentence: change "Meaning" to "The
> meaning".
>
> Page 5, Section 4.1, 1st paragraph, 2nd sentence: change "Router" to "A
> router".
>
> Page 5, Section 4.1, 2nd paragraph, last sentence: append a comma after
> "change".
>
> Page 5, Section 4.1, 4th paragraph, 2nd sentence: delete "The".  Change
> "TLVs" to "sub-TLVs".  Change "adminsitrative" to "administrative".
>
> Page 5, Section 4.1, 4th paragraph: the paragraph, starting at "The list of
> per-node" is pretty much redundant given the admonition in the first
> sentence of the previous paragraph.  Perhaps delete it rather than belabor
> the point?
>
> Page 5, Section 4.1, 1st paragraph, 4th sentence: change "well known" to
> "well-known".  Change "capability" to "CAPABILITY".
>
> Page 6, 1st partial paragraph, 2nd sentence: insert "the" before
> "reachability".
>
> Page 6, Section 4.3, 1st paragraph, 1st sentence: delete "(TLV-242)".
>
> Page 6, Section 4.3, 1st paragraph, 3rd sentence: change "an" to "a".  Based
> on Section 3.1, I might change "changes" to "adds to" because Section 3.1
> specifies that sub-TLVs are cumulative.
>
> Page 10, Section 7, 1st paragraph, 3rd sentence: change "ISIS" to "IS-IS".
> Change "is" to "are".
>
> Page 10, Section 7, 2nd paragraph, 2nd sentence: insert "the" before "case".
> Insert "the" before "forwarding".  Insert a space before "and".
>
> Page 12, Section 8, 2nd sentence: insert "The" before "YANG".
>
> Page 12, Section 8, 3rd sentence: insert "The" before "IS-IS".  Insert "the"
> before "routing".
>
> Page 12, Section 9, item i): why is the sub-TLV name hyphenated here and not
> elsewhere?
>
> Page 12, Section 10: append a comma after "Chunduri".
>


From nobody Sat Apr 30 13:36:02 2016
Return-Path: <brian.e.carpenter@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 64A4A12D17F for <ietf@ietfa.amsl.com>; Sat, 30 Apr 2016 13:35:59 -0700 (PDT)
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, FREEMAIL_FROM=0.001, LOTS_OF_MONEY=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 aqauF9GOl5sq for <ietf@ietfa.amsl.com>; Sat, 30 Apr 2016 13:35:57 -0700 (PDT)
Received: from mail-pa0-x22e.google.com (mail-pa0-x22e.google.com [IPv6:2607:f8b0:400e:c03::22e]) (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 AC70A12D128 for <ietf@ietf.org>; Sat, 30 Apr 2016 13:35:57 -0700 (PDT)
Received: by mail-pa0-x22e.google.com with SMTP id r5so59986386pag.1 for <ietf@ietf.org>; Sat, 30 Apr 2016 13:35:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=subject:to:references:cc:from:organization:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=FVLl/Ka4z3etut4veDY7S6B04NnbvSwkx16IQwrKr4o=; b=GSdAq2CKOeYSjHQKpEBSBoK4sUbimz+xlUPrJHS7styuWKZCi5plYQZxYJcT0KBEgL 5mShzQdQc7ElU1PajOCG6po0wUnBZLc5DWYNd6Kq7X7KsdJsDwRlYRlFunkr8mKugC6L 740ltsMIajung287sWZ2cu4h+evUxlXjaKWZxAI0SrkNVtzp979XNTfCue6WtdHoFYxj zTNgKVdl1DOXejUraZlwY6zyMnMldngoj7wpHnc4HBZAJtxfg6jxzs6kNYrHSqcRxDwV WKefYe7kcnYYXxQvE0s0YIbPCqT8ABw1LjjxdBGki9nhe1gEa2WIjcnFjN/DAdtPzQ4b Tt+g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:cc:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=FVLl/Ka4z3etut4veDY7S6B04NnbvSwkx16IQwrKr4o=; b=SZzx2eI2cUEKh5J2n/9ZmWu6R1uCoRbyKtPSSuay4ke+/4g1Fdu+7bdwkBtSO4L75B fIm+TnghZvPvvYIv2dNTewzq7rqfybMp8lo4Ayz7LXysyltpd2dqzkraYrJszNrM5jRn HhDW1sKAGBe6PlenxhBEU+ZTpzv2DJ/6SJlkBxwfpeY3tNCFjURZK/mvpB5/lY8gS6GF DhwtEQ1WF+f58aWwged8H5RxskCcaAlf2mxql6EpzfSb4UDeT5HR0UZB1OI9cpyK0+0j rRdXgqJuMYt5Sbn+krHN4+coFCfvrz34rVZO8bH9MMCHHoqj6IdcP++HAp2BtVeP0Eou PVYQ==
X-Gm-Message-State: AOPr4FURFQrt/utNp+b8mK8oOFrO2m71hI/u4i6PCv7XCbxaGWALI64rdpW9+owgVVJqkg==
X-Received: by 10.66.146.164 with SMTP id td4mr39214879pab.47.1462048557242; Sat, 30 Apr 2016 13:35:57 -0700 (PDT)
Received: from ?IPv6:2406:e007:4037:1:28cc:dc4c:9703:6781? ([2406:e007:4037:1:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id d78sm33407016pfb.59.2016.04.30.13.35.54 (version=TLSv1/SSLv3 cipher=OTHER); Sat, 30 Apr 2016 13:35:55 -0700 (PDT)
Subject: Re: Last Call on draft-bradner-rfc3979bis-08.txt ("Intellectual Property Rights in IETF Technology")
To: Stewart Bryant <stewart.bryant@gmail.com>
References: <0000431F-F977-4A24-BA4D-064F740977A0@piuha.net> <E7E31E22-1C86-40C4-BC5B-F65132015EF5@qti.qualcomm.com> <6CA3C554-0FF6-4779-80B9-C75698FB61C1@piuha.net> <EC4CBF0D-1B7C-4FB5-85EA-E622B24E9B9A@stewe.org> <9AFC22D7-C509-4765-AAC9-3096F188C4C6@qti.qualcomm.com> <57247534.3060609@gmail.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <bba3bcb2-fc0f-45e9-dd83-e96b715e7a02@gmail.com>
Date: Sun, 1 May 2016 08:35:48 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.0
MIME-Version: 1.0
In-Reply-To: <57247534.3060609@gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/2Sk_zjP_7Kgnk60gDTc-OqJefoY>
Cc: IETF <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: Sat, 30 Apr 2016 20:35:59 -0000

On 30/04/2016 21:04, Stewart Bryant wrote:
> 
>    l. "Reasonably and personally known": means something an individual
>       knows personally or, because of the job the individual holds,
>       would reasonably be expected to know.  This wording is used to
>       indicate that an organization cannot purposely keep an individual
>       in the dark about patents or patent applications just to avoid the
>       disclosure requirement.  But this requirement should not be
>       interpreted as requiring the IETF Contributor or Participant (or
>       his or her represented organization, if any) to perform a patent
>       search to find applicable IPR.
> 
> 
> How do we deal with the case of a an individual that was exposed to IPR in a previous
> employment, but no longer having access to the records of that employer is
> uncertain about whether they know of such IPR? A third party disclosure is one
> solution, but without access to records it may not be possible to sufficiently
> identify the patent such that the legal department can file the disclosure.

So the individual does a voluntary disclosure based on what she happens
to remember, and then her obligation is satisfied. We have no control
over what non-participants at her previous employer do.

> 
> 6. Failure to Disclose
> 
>    There may be cases in which individuals are not permitted by their
>    employers or by other factors to disclose the existence or substance
>    of patent applications or other IPR.  Since disclosure is required
>    for anyone making a Contribution or participating in IETF activities,
>    a person who is not willing or able to disclose IPR for this reason,
>    or any other reason, must not contribute to or participate in IETF
>    activities with respect to technologies that he or she reasonably and
>    personally knows to be Covered by IPR which he or she will not
>    disclose, unless that person knows that his or her employer or
>    sponsor will make the required disclosures on his or her behalf.
> 
>    Contributing to or participating in IETF activities about a
>    technology without making required IPR disclosures is a violation of
>    IETF process.
> 
>    In addition to any remedies the IESG may consider other actions. See
>    [RFC6701] for details.
> 
> 
> This assumes that the individual intends to support the technology that they
> know to be encumbered.
> 
> Surely we need to also consider the case of an individual that although unable
> to disclose IPR without breaching confidentiality is arguing for an alternative
> unencumbered solution.

What's the difference? If you participate, you must disclose. I agree it
would be an annoying situation for the individual.

> 
> We also need to visit the matter of licence fees.
> 
> The IETF has a policy of not discussing licence terms, and in particular licence fees
> in determining whether a technology is to be adopted or avoided.

Where does it say that? What I read is the opposite:

"    A. Since IPR disclosures will be used by IETF working groups during
     their evaluation of alternative technical solutions, it is helpful
     if an IPR disclosure includes information about licensing of the
     IPR in case Implementing Technologies require a license...."

   Brian


> This policy does
> not properly consider the extremity of the range of devices we support. What is
> technically the best solution for a $1m router despite a significant licence fee
> may not be viable for $0.01 IoT sensor because of the licence fee. Yet the WG is
> not permitted to discuss those economics.
> 
> - Stewart
> 
> 
> 
> 
> 

