From nobody Tue Feb 28 08:59:42 2017 Return-Path: X-Original-To: manycouches@ietfa.amsl.com Delivered-To: manycouches@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7BF75129630 for ; Tue, 28 Feb 2017 08:59:41 -0800 (PST) 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 87hYAlCBl5W6 for ; Tue, 28 Feb 2017 08:59:39 -0800 (PST) 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 4EF8A12962F for ; Tue, 28 Feb 2017 08:59:39 -0800 (PST) Received: by mail-qk0-x236.google.com with SMTP id s186so27709944qkb.1 for ; Tue, 28 Feb 2017 08:59:39 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=IAw1CxnUqTcLmPTrsp5yEeqNAuavBoNLRMMe6QgqXyU=; b=avdwbMMsXPgX6mW0AHVgSXa3Gm3dIlnR70/3Mv24TbvnfckEyqucvcwz+3AqHreIHe JaS5y1pRfDrRrzlV9y1hfTgkvrOgZVRRGyC7Y5lcKxlC20N8ote7CJT7XcjAkBOA6UMX EKE/kgcGxnZb1WngKz3mjVPT7zz84u8A3IMe2LGDE+G1XFP+2wJmSWTGpS4wN48a8NnR ipSosKIvDOw9h3M97Bw9xgBrjrCChzgicGOp2w8eTyp/XW3baKM5jnzZ+HcqP4xMxCuP y3ArLwp3P/uKT1USbOn7NgR2pF/wO6x8tmtJygZdnj2GtywVUrSELoxoZXUAKymSe7S5 V+fA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=IAw1CxnUqTcLmPTrsp5yEeqNAuavBoNLRMMe6QgqXyU=; b=EtWDASdCoVyMk0GVVFqzHTfhJXy47mH7PHfPKPJgdLB+efWbXmutGXDMqW+WiPXHRr EIq5Ez4c8t6AGdheOtwQ3GU93+CLOFmoQtYI/4tmUKeAqAMlEJP76NhGKvIYvxSD/IIn JUjvH3uGKQAW5hnDbknqxy8F6iA4v828p+1InkA+qD5UsdoZ1Yb78VLDBmXtugcXVnAH 3xNKgg+8dcFqUJg2gdoJLhBemsq62eWd1/6sDCCe26KDLAAIivT8H6tbNJ1ZJKnnFde3 nmPHwcfsXxcHIdMZnNOh7aKAC5cISLQfgqsBk9OQZ91xJ3VbayMG3MmX9jrEW93ezUNs fhYQ== X-Gm-Message-State: AMke39l4vWD9wrNghz4Z8+fwJ5W/a2O7SmQSOJb47uW9T/koZ/dwdg9Sm4CK+J4nAOb31pQWkL2zKAhy1Lbo6Q== X-Received: by 10.233.235.132 with SMTP id b126mr3772359qkg.262.1488301178183; Tue, 28 Feb 2017 08:59:38 -0800 (PST) MIME-Version: 1.0 Received: by 10.12.140.78 with HTTP; Tue, 28 Feb 2017 08:59:37 -0800 (PST) In-Reply-To: References: <148422861194.19294.7055110454014498123.idtracker@ietfa.amsl.com> From: Kathleen Moriarty Date: Tue, 28 Feb 2017 11:59:37 -0500 Message-ID: To: Dan York Content-Type: text/plain; charset=UTF-8 Archived-At: Cc: "manycouches@ietf.org" Subject: Re: [Manycouches] FYI - new version capturing feedback from Seoul meeting... Fwd: New Version Notification for draft-manycouches-completely-virtual-meetings-04.txt X-BeenThere: manycouches@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "List is a design team list to identify issues that would arise should an IETF meeting ever be held with O\(1000\) 'remote' participants." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Feb 2017 16:59:41 -0000 crickets... is anyone interested? I think we will have increased remote attendance in Chicago and would like us to be ready. The plenary has been tough to get full access to remotely for the meetings I was unable to attend and I had trouble with remotely attending some other sessions. We will likely see an increase in problems and it would be good to be prepared if we can do anything. The Google effort is great, but we'll have home users too. Should we have a call to discuss? I'm happy to set up a doodle poll. On Mon, Jan 30, 2017 at 12:23 PM, Kathleen Moriarty wrote: > Hi All, > > If we switch gears to a meeting with increased virtual attendance, > Dan's draft (just read it) is a good starting point to run through the > considerations. I didn't see a section on > directions/information/guidance for remote participants and think that > will be important from the 2 meetings I attended remotely. I'm sure I > mentioned it already, but the methods used to connect to sessions make > a difference in your ability to participate if something goes wrong. > I connect in with jabber before starting meetecho so I can fall back > on jabber and the audio only. Not everyone would think to do this or > to plan for something going wrong. > > I also reached out to Jim Martin who is already connected to this > effort. If more NOC volunteers are needed to help, Jim will figure > that out and we can add them to this list. If they have existing > documentation of their considerations, we should review that prior to > recreating any wheel, so let's give them a little time to share that > with us. > > I'm wondering if a virtual meeting might help us get focused. The > agenda could be to run through the sections outlined in Dan's draft > with the focused changed to increased remote attendance. There are > numerous known considerations that we should ack and try to plan for > as well (plenary connections dropping, etc.). > > Thank you, > Kathleen > > > > On Mon, Jan 30, 2017 at 11:32 AM, Kathleen Moriarty > wrote: >> Hi Dan, >> >> Thanks so much for pulling this together. Being able to handle larger >> scale remote attendance may become a reality for us quicker than we >> expected. I would not expect Chicago to be completely remote as the >> target of this draft, but I do think we'll get lower in-person >> attendance. I'll read through your draft, but think we may want to >> get serious on this effort focused on increased remote attendance. >> >> First, do others agree in this shift of focus? I was supposed to be >> pulling together something on interim meetings, but this seems more >> important. We also need to involve the NOC in our discussions or see >> where we can help them with their efforts. I can reach out and see >> which way we should plug in and report back to the team. >> >> I think it would be helpful to agree on a course of action before >> delving into one/many. >> >> Thanks, >> Kathleen >> >> On Thu, Jan 12, 2017 at 8:46 AM, Dan York wrote: >>> manycouches team, >>> >>> FYI, I've submitted a new version of the overall document based on feedback >>> from the Seoul meeting. The doc is at: >>> >>> https://datatracker.ietf.org/doc/draft-manycouches-completely-virtual-meetings/ >>> >>> My version in Github is at: >>> >>> https://github.com/danyork/draft-york-manycouches-completely-virtual-meetings >>> >>> Comments are naturally welcome, >>> Dan >>> >>> >>> Begin forwarded message: >>> >>> From: >>> Subject: New Version Notification for >>> draft-manycouches-completely-virtual-meetings-04.txt >>> Date: January 12, 2017 at 8:43:31 AM EST >>> To: Dan York , " york@isoc.org" >>> >>> >>> A new version of I-D, draft-manycouches-completely-virtual-meetings-04.txt >>> has been successfully submitted by Dan York and posted to the >>> IETF repository. >>> >>> Name: draft-manycouches-completely-virtual-meetings >>> Revision: 04 >>> Title: Thoughts on Completely Virtual IETF Meetings >>> Document date: 2017-01-11 >>> Group: Individual Submission >>> Pages: 15 >>> URL: >>> https://www.ietf.org/internet-drafts/draft-manycouches-completely-virtual-meetings-04.txt >>> Status: >>> https://datatracker.ietf.org/doc/draft-manycouches-completely-virtual-meetings/ >>> Htmlized: >>> https://tools.ietf.org/html/draft-manycouches-completely-virtual-meetings-04 >>> Diff: >>> https://www.ietf.org/rfcdiff?url2=draft-manycouches-completely-virtual-meetings-04 >>> >>> Abstract: >>> This document captures initial thoughts about having IETF meetings >>> that are completely virtual. It explores the issues involved with >>> both a "planned" virtual meeting and an "emergency" virtual meeting. >>> The intent is to evolve this document to provide answers to the >>> questions posed throughout the text. This is currently a thought >>> experiment. There are no current plans to hold a completely virtual >>> IETF meeting. >>> >>> >>> >>> >>> Please note that it may take a couple of minutes from the time of submission >>> until the htmlized version and diff are available at tools.ietf.org. >>> >>> The IETF Secretariat >>> >>> >>> -- >>> Dan York >>> Senior Content Strategist, Internet Society >>> york@isoc.org +1-802-735-1624 >>> Jabber: york@jabber.isoc.org >>> Skype: danyork http://twitter.com/danyork >>> >>> http://www.internetsociety.org/ >>> >>> >>> >>> >>> >>> _______________________________________________ >>> Manycouches mailing list >>> Manycouches@ietf.org >>> https://www.ietf.org/mailman/listinfo/manycouches >>> >> >> >> >> -- >> >> Best regards, >> Kathleen > > > > -- > > Best regards, > Kathleen -- Best regards, Kathleen From nobody Tue Feb 28 11:36:43 2017 Return-Path: X-Original-To: manycouches@ietfa.amsl.com Delivered-To: manycouches@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C14211296B3 for ; Tue, 28 Feb 2017 11:36:31 -0800 (PST) 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, RCVD_IN_DNSWL_NONE=-0.0001, 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 AbyXMCt7r7iC for ; Tue, 28 Feb 2017 11:36:28 -0800 (PST) Received: from mail-wr0-x233.google.com (mail-wr0-x233.google.com [IPv6:2a00:1450:400c:c0c::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 AE04C1296B1 for ; Tue, 28 Feb 2017 11:36:18 -0800 (PST) Received: by mail-wr0-x233.google.com with SMTP id g10so15759506wrg.2 for ; Tue, 28 Feb 2017 11:36:18 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=Vd524NHF3InT58jBBBIdom3TZ/AFi7OLci7aEDD47g0=; b=FPdczyOkusBiyMTd1N6nkz8w2Tdpm+evCijftpYQDv7Zh5bdIoZ0ye6AuSVZOwUzOo 9cMEptHRSPKu9r11zHjA1tuuFC5qi0N0axMxUaQtjzJxdHYPuxrpzY57gWOVzV8EBJ8s ititQl+pdoE5axaGtgIhIHnledsg7f52RcphoYvhK3AUHw2Q7m0rvVmn6ST4iloXanyZ 07/H3CzjOy43TimkbsOnL21w4c4BnqPc4cHex5mIUj3iIy0ipq8y9p7rS0x7r5pSN2bJ pTIDXVh3YQxeNwNSSLBK1gZFpeh0OrQDTUGmJkXQ1Y/377s5HRaBrk0fDMVPrvmcnQ7S vfrg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=Vd524NHF3InT58jBBBIdom3TZ/AFi7OLci7aEDD47g0=; b=VZ6BtQcBSKqkflLeFLOmPkvvioOzE12DQVUk15FeQMFxV+pd42HaYsaMgm6Nnk/L+r XK5zUfwB0QqYGJZslFMB7T5YvBni1H2LxvHsmkUT6RH9gFRsyMB2AYRmMaawuzINd9yr r/XlWKe7VtjOZjWyh3Q8AAHa6deD9kGNsErnGbzBjQMdN5QUbn7ttomzXLMyljcCAJ7m LNu3WIOG+CFaFESCDq41k5uYiym8IbgiV+SQ2oKFTU04si9j67wPMuW88w1fnbTYoS4a ikgnOuRG5aQWPDRMlDQIyjKhBp7Fc11gmLgtrpwDYhuyt1CjjxrqUieBPI9xfK04bANK NUFA== X-Gm-Message-State: AMke39l7LL/rWKwDW+vvhJCvmaO/qxng899lzcc40eSoasY+ntIfgS/BUAIafeAoyIigBCxwwyUHFmLbURUHQw== X-Received: by 10.223.136.4 with SMTP id d4mr3835267wrd.44.1488310576763; Tue, 28 Feb 2017 11:36:16 -0800 (PST) MIME-Version: 1.0 Received: by 10.223.145.5 with HTTP; Tue, 28 Feb 2017 11:36:16 -0800 (PST) In-Reply-To: References: <148422861194.19294.7055110454014498123.idtracker@ietfa.amsl.com> From: Alia Atlas Date: Tue, 28 Feb 2017 14:36:16 -0500 Message-ID: To: Kathleen Moriarty Content-Type: multipart/alternative; boundary=001a11461d183e55a405499c4fd2 Archived-At: Cc: Dan York , "manycouches@ietf.org" Subject: Re: [Manycouches] FYI - new version capturing feedback from Seoul meeting... Fwd: New Version Notification for draft-manycouches-completely-virtual-meetings-04.txt X-BeenThere: manycouches@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "List is a design team list to identify issues that would arise should an IETF meeting ever be held with O\(1000\) 'remote' participants." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Feb 2017 19:36:32 -0000 --001a11461d183e55a405499c4fd2 Content-Type: text/plain; charset=UTF-8 A call would probably help focus and encourage more prep work. I continue to think that having more interested folks pulled in would help. Regards, Alia On Tue, Feb 28, 2017 at 11:59 AM, Kathleen Moriarty < kathleen.moriarty.ietf@gmail.com> wrote: > crickets... is anyone interested? I think we will have increased > remote attendance in Chicago and would like us to be ready. The > plenary has been tough to get full access to remotely for the meetings > I was unable to attend and I had trouble with remotely attending some > other sessions. We will likely see an increase in problems and it > would be good to be prepared if we can do anything. > > The Google effort is great, but we'll have home users too. Should we > have a call to discuss? I'm happy to set up a doodle poll. > > On Mon, Jan 30, 2017 at 12:23 PM, Kathleen Moriarty > wrote: > > Hi All, > > > > If we switch gears to a meeting with increased virtual attendance, > > Dan's draft (just read it) is a good starting point to run through the > > considerations. I didn't see a section on > > directions/information/guidance for remote participants and think that > > will be important from the 2 meetings I attended remotely. I'm sure I > > mentioned it already, but the methods used to connect to sessions make > > a difference in your ability to participate if something goes wrong. > > I connect in with jabber before starting meetecho so I can fall back > > on jabber and the audio only. Not everyone would think to do this or > > to plan for something going wrong. > > > > I also reached out to Jim Martin who is already connected to this > > effort. If more NOC volunteers are needed to help, Jim will figure > > that out and we can add them to this list. If they have existing > > documentation of their considerations, we should review that prior to > > recreating any wheel, so let's give them a little time to share that > > with us. > > > > I'm wondering if a virtual meeting might help us get focused. The > > agenda could be to run through the sections outlined in Dan's draft > > with the focused changed to increased remote attendance. There are > > numerous known considerations that we should ack and try to plan for > > as well (plenary connections dropping, etc.). > > > > Thank you, > > Kathleen > > > > > > > > On Mon, Jan 30, 2017 at 11:32 AM, Kathleen Moriarty > > wrote: > >> Hi Dan, > >> > >> Thanks so much for pulling this together. Being able to handle larger > >> scale remote attendance may become a reality for us quicker than we > >> expected. I would not expect Chicago to be completely remote as the > >> target of this draft, but I do think we'll get lower in-person > >> attendance. I'll read through your draft, but think we may want to > >> get serious on this effort focused on increased remote attendance. > >> > >> First, do others agree in this shift of focus? I was supposed to be > >> pulling together something on interim meetings, but this seems more > >> important. We also need to involve the NOC in our discussions or see > >> where we can help them with their efforts. I can reach out and see > >> which way we should plug in and report back to the team. > >> > >> I think it would be helpful to agree on a course of action before > >> delving into one/many. > >> > >> Thanks, > >> Kathleen > >> > >> On Thu, Jan 12, 2017 at 8:46 AM, Dan York wrote: > >>> manycouches team, > >>> > >>> FYI, I've submitted a new version of the overall document based on > feedback > >>> from the Seoul meeting. The doc is at: > >>> > >>> https://datatracker.ietf.org/doc/draft-manycouches- > completely-virtual-meetings/ > >>> > >>> My version in Github is at: > >>> > >>> https://github.com/danyork/draft-york-manycouches- > completely-virtual-meetings > >>> > >>> Comments are naturally welcome, > >>> Dan > >>> > >>> > >>> Begin forwarded message: > >>> > >>> From: > >>> Subject: New Version Notification for > >>> draft-manycouches-completely-virtual-meetings-04.txt > >>> Date: January 12, 2017 at 8:43:31 AM EST > >>> To: Dan York , " york@isoc.org" > >>> > >>> > >>> A new version of I-D, draft-manycouches-completely- > virtual-meetings-04.txt > >>> has been successfully submitted by Dan York and posted to the > >>> IETF repository. > >>> > >>> Name: draft-manycouches-completely-virtual-meetings > >>> Revision: 04 > >>> Title: Thoughts on Completely Virtual IETF Meetings > >>> Document date: 2017-01-11 > >>> Group: Individual Submission > >>> Pages: 15 > >>> URL: > >>> https://www.ietf.org/internet-drafts/draft-manycouches- > completely-virtual-meetings-04.txt > >>> Status: > >>> https://datatracker.ietf.org/doc/draft-manycouches- > completely-virtual-meetings/ > >>> Htmlized: > >>> https://tools.ietf.org/html/draft-manycouches-completely- > virtual-meetings-04 > >>> Diff: > >>> https://www.ietf.org/rfcdiff?url2=draft-manycouches- > completely-virtual-meetings-04 > >>> > >>> Abstract: > >>> This document captures initial thoughts about having IETF meetings > >>> that are completely virtual. It explores the issues involved with > >>> both a "planned" virtual meeting and an "emergency" virtual meeting. > >>> The intent is to evolve this document to provide answers to the > >>> questions posed throughout the text. This is currently a thought > >>> experiment. There are no current plans to hold a completely virtual > >>> IETF meeting. > >>> > >>> > >>> > >>> > >>> Please note that it may take a couple of minutes from the time of > submission > >>> until the htmlized version and diff are available at tools.ietf.org. > >>> > >>> The IETF Secretariat > >>> > >>> > >>> -- > >>> Dan York > >>> Senior Content Strategist, Internet Society > >>> york@isoc.org +1-802-735-1624 > >>> Jabber: york@jabber.isoc.org > >>> Skype: danyork http://twitter.com/danyork > >>> > >>> http://www.internetsociety.org/ > >>> > >>> > >>> > >>> > >>> > >>> _______________________________________________ > >>> Manycouches mailing list > >>> Manycouches@ietf.org > >>> https://www.ietf.org/mailman/listinfo/manycouches > >>> > >> > >> > >> > >> -- > >> > >> Best regards, > >> Kathleen > > > > > > > > -- > > > > Best regards, > > Kathleen > > > > -- > > Best regards, > Kathleen > > _______________________________________________ > Manycouches mailing list > Manycouches@ietf.org > https://www.ietf.org/mailman/listinfo/manycouches > --001a11461d183e55a405499c4fd2 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
A call would probably help focus and encourage more prep w= ork.
I continue to think that having more interested folks pulled in wo= uld help.

Regards,
Alia

On Tue, Feb 28, 2017 a= t 11:59 AM, Kathleen Moriarty <kathleen.moriarty.ietf@gmail= .com> wrote:
crickets... is= anyone interested?=C2=A0 I think we will have increased
remote attendance in Chicago and would like us to be ready.=C2=A0 The
plenary has been tough to get full access to remotely for the meetings
I was unable to attend and I had trouble with remotely attending some
other sessions.=C2=A0 We will likely see an increase in problems and it
would be good to be prepared if we can do anything.

The Google effort is great, but we'll have home users too.=C2=A0 Should= we
have a call to discuss? I'm happy to set up a doodle poll.

On Mon, Jan 30, 2017 at 12:23 PM, Kathleen Moriarty
<kathleen.moriarty.ietf@gmail.com> wrote: > Hi All,
>
> If we switch gears to a meeting with increased virtual attendance,
> Dan's draft (just read it) is a good starting point to run through= the
> considerations.=C2=A0 I didn't see a section on
> directions/information/guidance for remote participants and think= that
> will be important from the 2 meetings I attended remotely.=C2=A0 I'= ;m sure I
> mentioned it already, but the methods used to connect to sessions make=
> a difference in your ability to participate if something goes wrong. > I connect in with jabber before starting meetecho so I can fall back > on jabber and the audio only.=C2=A0 Not everyone would think to do thi= s or
> to plan for something going wrong.
>
> I also reached out to Jim Martin who is already connected to this
> effort.=C2=A0 If more NOC volunteers are needed to help, Jim will figu= re
> that out and we can add them to this list.=C2=A0 If they have existing=
> documentation of their considerations, we should review that prior to<= br> > recreating any wheel, so let's give them a little time to share th= at
> with us.
>
> I'm wondering if a virtual meeting might help us get focused.=C2= =A0 The
> agenda could be to run through the sections outlined in Dan's draf= t
> with the focused changed to increased remote attendance.=C2=A0 There a= re
> numerous known considerations that we should ack and try to plan for > as well (plenary connections dropping, etc.).
>
> Thank you,
> Kathleen
>
>
>
> On Mon, Jan 30, 2017 at 11:32 AM, Kathleen Moriarty
> <kathleen.moria= rty.ietf@gmail.com> wrote:
>> Hi Dan,
>>
>> Thanks so much for pulling this together.=C2=A0 Being able to hand= le larger
>> scale remote attendance may become a reality for us quicker than w= e
>> expected.=C2=A0 I would not expect Chicago to be completely remote= as the
>> target of this draft, but I do think we'll get lower in-person=
>> attendance.=C2=A0 I'll read through your draft, but think we m= ay want to
>> get serious on this effort focused on increased remote attendance.=
>>
>> First, do others agree in this shift of focus?=C2=A0 I was suppose= d to be
>> pulling together something on interim meetings, but this seems mor= e
>> important.=C2=A0 We also need to involve the NOC in our discussion= s or see
>> where we can help them with their efforts.=C2=A0 I can reach out a= nd see
>> which way we should plug in and report back to the team.
>>
>> I think it would be helpful to agree on a course of action before<= br> >> delving into one/many.
>>
>> Thanks,
>> Kathleen
>>
>> On Thu, Jan 12, 2017 at 8:46 AM, Dan York <york@isoc.org> wrote:
>>> manycouches team,
>>>
>>> FYI, I've submitted a new version of the overall document = based on feedback
>>> from the Seoul meeting. The doc is at:
>>>
>>> https://= datatracker.ietf.org/doc/draft-manycouches-completely-virtual-mee= tings/
>>>
>>> My version in Github is at:
>>>
>>> https://gi= thub.com/danyork/draft-york-manycouches-completely-virtual-meetin= gs
>>>
>>> Comments are naturally welcome,
>>> Dan
>>>
>>>
>>> Begin forwarded message:
>>>
>>> From: <internet= -drafts@ietf.org>
>>> Subject: New Version Notification for
>>> draft-manycouches-completely-virtual-meetings-04.txt
>>> Date: January 12, 2017 at 8:43:31 AM EST
>>> To: Dan York <york@isoc.or= g>, " york@isoc.org" = <york@isoc.org>
>>>
>>>
>>> A new version of I-D, draft-manycouches-completely-virtua= l-meetings-04.txt
>>> has been successfully submitted by Dan York and posted to the<= br> >>> IETF repository.
>>>
>>> Name: draft-manycouches-completely-virtual-meetings
>>> Revision: 04
>>> Title: Thoughts on Completely Virtual IETF Meetings
>>> Document date: 2017-01-11
>>> Group: Individual Submission
>>> Pages: 15
>>> URL:
>>> https://www.ietf.org/internet-drafts/draft-manycouches-complete= ly-virtual-meetings-04.txt
>>> Status:
>>> https://= datatracker.ietf.org/doc/draft-manycouches-completely-virtual-mee= tings/
>>> Htmlized:
>>> https://too= ls.ietf.org/html/draft-manycouches-completely-virtual-meetings-04=
>>> Diff:
>>> htt= ps://www.ietf.org/rfcdiff?url2=3Ddraft-manycouches-completely-vir= tual-meetings-04
>>>
>>> Abstract:
>>>=C2=A0 =C2=A0This document captures initial thoughts about havi= ng IETF meetings
>>>=C2=A0 =C2=A0that are completely virtual.=C2=A0 It explores the= issues involved with
>>>=C2=A0 =C2=A0both a "planned" virtual meeting and an = "emergency" virtual meeting.
>>>=C2=A0 =C2=A0The intent is to evolve this document to provide a= nswers to the
>>>=C2=A0 =C2=A0questions posed throughout the text.=C2=A0 This is= currently a thought
>>>=C2=A0 =C2=A0experiment.=C2=A0 There are no current plans to ho= ld a completely virtual
>>>=C2=A0 =C2=A0IETF meeting.
>>>
>>>
>>>
>>>
>>> Please note that it may take a couple of minutes from the time= of submission
>>> until the htmlized version and diff are available at tools.ietf.= org.
>>>
>>> The IETF Secretariat
>>>
>>>
>>> --
>>> Dan York
>>> Senior Content Strategist, Internet Society
>>> york@isoc.org=C2=A0 =C2= =A0+1-802-735-1624=
>>> Jabber: york@jabber.is= oc.org
>>> Skype: danyork=C2=A0 =C2=A0http://twitter.com/danyork
>>>
>>> http://www.internetsociety.org/
>>>
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> Manycouches mailing list
>>> Manycouches@ietf.org
>>> https://www.ietf.org/mailman/list= info/manycouches
>>>
>>
>>
>>
>> --
>>
>> Best regards,
>> Kathleen
>
>
>
> --
>
> Best regards,
> Kathleen



--

Best regards,
Kathleen

_______________________________________________
Manycouches mailing list
Manycouches@ietf.org
https://www.ietf.org/mailman/listinfo/manycouc= hes

--001a11461d183e55a405499c4fd2-- From nobody Tue Feb 28 13:34:48 2017 Return-Path: X-Original-To: manycouches@ietfa.amsl.com Delivered-To: manycouches@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1BF33129500 for ; Tue, 28 Feb 2017 13:34:48 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.689 X-Spam-Level: X-Spam-Status: No, score=-2.689 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, T_REMOTE_IMAGE=0.01] 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 gWX84ddmodt4 for ; Tue, 28 Feb 2017 13:34:46 -0800 (PST) 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 352B6126D73 for ; Tue, 28 Feb 2017 13:34:46 -0800 (PST) Received: by mail-qk0-x233.google.com with SMTP id n127so40149195qkf.0 for ; Tue, 28 Feb 2017 13:34:46 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=LG47jfkWW9iEXbJHBXTaViU/D+TwBn7TthDsWWhXZAI=; b=ltHK77nQZXyLsoJ6kXm0geCs7PqWWsVrrkrsGoLeASMJYQhXc1RhtU3OO2ffr6rza8 2Li0LNK/FxmoS/qhIbeZ3cvqmFkObmYz3b3hKvWB398sMb7wpddsrp0SSbVqWEOaU73k L4ogBmQTkYVuZt1WRaHDtRX99P4GZEp15gSSqBlAskDRfl0P6mPr7epB/yVIEBkRnt2G EkBY2m+M0wkDDqnLNAzxPCGjWoYrAgdJz/Ev9YvlD1AXOg6kapnXeEE9Iw8dsRtVd/7i gJxcGXLMtPEvPBlretIkRNbxq4Y1FqGICkq/2mEPca9RqX+jPBOjGsupVczM975roQ6V IeIQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=LG47jfkWW9iEXbJHBXTaViU/D+TwBn7TthDsWWhXZAI=; b=r8fBR/rdY0KoaM1wKtYhM4prJVrEKq5YQGm+CPVnpeuVmDsZIMVXQPBn7WpmkJpmj6 /WtRMiBeAeWYXzAGcXyfqLlscFs5x2zJN6uHhNG/BHhJr2wK3CSEHRbnD0vS+L6tUW69 fDdFg28N19jhiT8PnUx7ntqXHgq3lAsRyl7YdwUXkhiZAosna7XhPoPqbtkR8PzROvsf KKxJMZ7mcVKNaUpZRE9nlcqkMbyuZkLI3Em6uRBWS8fmf1nBAxnrmQMvoB3SG2OgZSYl u1T5rbGDva4LhFPMls7NQmKPsIal8ubsSVPOZ2a9ZaChm+sLY++u43tWxJ4XWhbBXJMs 3KQQ== X-Gm-Message-State: AMke39n2GsGViMzX93HhmauV5oclf9l9kxKXdiNK8K8gWcCG01fHz5bUX+A30F8ziU/cTBzeb876HkHwRr/Iuw== X-Received: by 10.237.34.76 with SMTP id o12mr5955189qtc.261.1488317685166; Tue, 28 Feb 2017 13:34:45 -0800 (PST) MIME-Version: 1.0 Received: by 10.12.140.78 with HTTP; Tue, 28 Feb 2017 13:34:44 -0800 (PST) In-Reply-To: <453207644.114931.1488317464202.POLL_INVITECONTACT_PARTICIPANT_INVITATION_WITH_MESSAGE@worker10.doodle.com> References: <453207644.114931.1488317464202.POLL_INVITECONTACT_PARTICIPANT_INVITATION_WITH_MESSAGE@worker10.doodle.com> From: Kathleen Moriarty Date: Tue, 28 Feb 2017 16:34:44 -0500 Message-ID: To: "" Content-Type: multipart/alternative; boundary=001a113e7c4cf01ae405499df678 Archived-At: Subject: [Manycouches] Fwd: ManyCouches X-BeenThere: manycouches@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "List is a design team list to identify issues that would arise should an IETF meeting ever be held with O\(1000\) 'remote' participants." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Feb 2017 21:34:48 -0000 --001a113e7c4cf01ae405499df678 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi, Here is a doodle poll to see if we can find a time that works for a call next week. Thanks, Kathleen ---------- Forwarded message ---------- From: Kathleen (via Doodle) Date: Tue, Feb 28, 2017 at 4:31 PM Subject: ManyCouches To: kathleen.moriarty.ietf@gmail.com Kathleen invites you to participate in the Doodle poll "ManyCouches." Hi there, Kathleen (Kathleen.moriarty.ietf@gmail.com) invites you to participate in the Doodle poll "ManyCouches." Meeting to discuss improving remote access for participants Participate now What is Doodle? Doodle is a web service that helps Kathleen to find a suitable date for meeting with a group of people. Learn more about how Doodle works. You have received this e-mail because "Kathleen" has invited you to participate in the Doodle poll "ManyCouches." Doodle is also available for iOS and Android. Doodle AG, Werdstrasse 21, 8021 Z=C3=BCrich --=20 Best regards, Kathleen --001a113e7c4cf01ae405499df678 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi,

Here is a doodle poll to see if we = can find a time that works for a call next week.

T= hanks,
Kathleen

--------= -- Forwarded message ----------
From: Kath= leen (via Doodle) <mailer@doodle.com>
Date: Tue, Feb 28, 2017 at 4:31 P= M
Subject: ManyCouches
To: kathleen.moriarty.ietf@gmail.com


Kathleen invites you to participa= te in the Doodle poll "ManyCouches."
=20 =
Hi there,
=C2=A0
=20
Kathleen (Kathleen.moriarty.ietf@gmail.com) invites you to parti= cipate in the Doodle poll "ManyCouches.&= quot;
Meeting to discuss improving remote access for participants
=20
Participate=C2=A0now=
What is Doodle? Doodle is a= web service that helps Kathleen to find a suitable date for meeting with a= group of people. Learn more about how Doodle works.
You have received this e-mail because "Kathleen" has i= nvited you to participate in the Doodle poll "ManyCouches."
Doodle is also available for iOS and Android.
Doodle AG, Werdstrasse 21, 8021 Z=C3=BCrich




--

Be= st regards,
Kathleen
--001a113e7c4cf01ae405499df678-- From nobody Tue Feb 28 13:35:30 2017 Return-Path: X-Original-To: manycouches@ietfa.amsl.com Delivered-To: manycouches@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A4754129532 for ; Tue, 28 Feb 2017 13:35:28 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.582 X-Spam-Level: X-Spam-Status: No, score=-1.582 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, LOCALPART_IN_SUBJECT=1.107, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, T_REMOTE_IMAGE=0.01] 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 lBDXBWfhP1IS for ; Tue, 28 Feb 2017 13:35:27 -0800 (PST) Received: from mail-qk0-x234.google.com (mail-qk0-x234.google.com [IPv6:2607:f8b0:400d: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 C0E02126D73 for ; Tue, 28 Feb 2017 13:35:26 -0800 (PST) Received: by mail-qk0-x234.google.com with SMTP id s186so40057158qkb.1 for ; Tue, 28 Feb 2017 13:35:26 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=o5HnH3yE3AEnFwqv3rdi/lrRwsfEqNguAooogFo9D74=; b=t2o5JQK2YLUVEq67b8GHDf/9XeoNFeuWfYlv8+hy1f0BAPmb85KfwtyARxLdPAClT3 IXoMw3uN3w2PSLKwhd9YhGkkv3uPX/dbdGf/K/EUWSYF3sUrIJzKu/jjYWEQ9E9Kfs3q UB+uCgysj5ZWG+TR66sD8iOqR7HwAP9M0olw8UYxzmwiHC/pdywl513iZFfXG8j8TbEe 4/NKnzK7edx8VIE1QPE6fMVn2A/lu8Oz/jm/F1TgUMDuy9ny7eLwOLB27Ng08UQQ5lXz DUOJ1EKQWe5fKmvEdx7WCPKGYirsw81H27BYR0M6wvqqG5UDs315vtvA0/p06HUqfFvG YcTQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=o5HnH3yE3AEnFwqv3rdi/lrRwsfEqNguAooogFo9D74=; b=AFcG53Ii+dVYXEed3tchV54gypaGZbeE+dNleK4VIQVeLSLTUqAOHtzO5ACZ8phaws ZrxLrBW6rVq9Gwe31xia2pwHy+DKq4YzWB62HEFaq4qoGpKvcBygpamt3oQLJpQRPTbV r9MvX/+1fQg/SksFPRHmiW2eN1cxnLo/HbmrZDfwZix+SdckE8Q2NT0o/3vuSGXCQrjs iMrHsAa4qzs2ej6cJNoH4rGElceq+lOwi3qENj0SLPd436leMXwWCrr91spsc1+5eCw1 +eNusGVdHQUJLVDox+f8xtWf/lyihIoDGbJSYysyfLgabhFaGPyzkR6vTI8cHjocT8oU tQuQ== X-Gm-Message-State: AMke39mv2P9Wqquof5M4dn7buH/JJ++l6ofzgo3cC/2bfwDAOG2SkcZ4xtrWmQVHZ5JgnJEoYZb+zyCSQPnWIQ== X-Received: by 10.237.37.229 with SMTP id y34mr5670036qtc.30.1488317725715; Tue, 28 Feb 2017 13:35:25 -0800 (PST) MIME-Version: 1.0 Received: by 10.12.140.78 with HTTP; Tue, 28 Feb 2017 13:35:25 -0800 (PST) In-Reply-To: References: <453207644.114931.1488317464202.POLL_INVITECONTACT_PARTICIPANT_INVITATION_WITH_MESSAGE@worker10.doodle.com> From: Kathleen Moriarty Date: Tue, 28 Feb 2017 16:35:25 -0500 Message-ID: To: "" Content-Type: multipart/alternative; boundary=001a114012465abc9d05499df9f4 Archived-At: Subject: Re: [Manycouches] ManyCouches X-BeenThere: manycouches@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "List is a design team list to identify issues that would arise should an IETF meeting ever be held with O\(1000\) 'remote' participants." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Feb 2017 21:35:28 -0000 --001a114012465abc9d05499df9f4 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Here is the link: http://doodle.com/poll/enecty3363etzc75 On Tue, Feb 28, 2017 at 4:34 PM, Kathleen Moriarty < kathleen.moriarty.ietf@gmail.com> wrote: > Hi, > > Here is a doodle poll to see if we can find a time that works for a call > next week. > > Thanks, > Kathleen > > ---------- Forwarded message ---------- > From: Kathleen (via Doodle) > Date: Tue, Feb 28, 2017 at 4:31 PM > Subject: ManyCouches > To: kathleen.moriarty.ietf@gmail.com > > > Kathleen invites you to participate in the Doodle poll "ManyCouches." > > > > Hi there, > > Kathleen (Kathleen.moriarty.ietf@gmail.com) invites you to participate in > the Doodle poll "ManyCouches." > Meeting to discuss improving remote access for participants > Participate now > > > What is Doodle? Doodle is a web service that helps Kathleen to find a > suitable date for meeting with a group of people. Learn more about how > Doodle works. > > You have received this e-mail because "Kathleen" has invited you to > participate in the Doodle poll "ManyCouches." > > Doodle is also available for iOS and Android. > > > Doodle AG, Werdstrasse 21, 8021 Z=C3=BCrich > > > > > -- > > Best regards, > Kathleen > --=20 Best regards, Kathleen --001a114012465abc9d05499df9f4 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

On Tue, Feb 28, 2017 at= 4:34 PM, Kathleen Moriarty <kathleen.moriarty.ietf@gmail.c= om> wrote:
Hi,

Here is a doodle poll to see if we can find a time = that works for a call next week.

Thanks,
Kathleen

-= --------- Forwarded message ----------
From: Kathleen (via Doodle) <mailer@doodle.com>
Date: Tu= e, Feb 28, 2017 at 4:31 PM
Subject: ManyCouches
To: kathleen.moriarty.ietf= @gmail.com


Kathleen invites you to participa= te in the Doodle poll "ManyCouches."
=20 =
Hi there,
=C2=A0
=20
Kathleen (Kathleen.moriarty.ietf@gmail.com) invites you to parti= cipate in the Doodle poll "ManyCouches.&= quot;
Meeting to discuss improving remote access for participants
=20
Participate=C2=A0now=
What is Doodle? Doodle is a= web service that helps Kathleen to find a suitable date for meeting with a= group of people. Learn more about how Doodle works.
You have received this e-mail because "Kathleen" has i= nvited you to participate in the Doodle poll "ManyCouches."
Doodle is also available for iOS and Android.
Doodle AG, Werdstrasse 21, 8021 Z=C3=BCrich




--

<= div>Best regards,
Kathleen



--
Best regards,
Kathleen
--001a114012465abc9d05499df9f4--