Content-Type: text/plain;
	charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.1\))
From: Eliot Lear <lear@cisco.com>
In-Reply-To: <3120DCA9-3CCA-4E76-8648-F37B472020D4@me.com>
Date: Mon, 27 Jul 2020 08:15:46 +0200
Cc: Ole Jacobsen <olejacobsen@me.com>, rfced-future@iab.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <3EA42114-4E4D-4447-A992-6C5EB059CCC6@cisco.com>
References: <FFFDC3FA-D1FD-484E-9D77-88A33E8E25FE@cisco.com>
 <3120DCA9-3CCA-4E76-8648-F37B472020D4@me.com>
To: Ole Jacobsen <olejacobsen=40me.com@dmarc.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/rgNQBTnaxgnhW9L--gysYJbYwro>
Subject: Re: [Rfced-future] RFC Editors Future Program @ IETF 108
Precedence: list

Hi Ole:

Please see =
https://meetings.conf.meetecho.com/ietf108/?group=3Drfcefdp&short=3D&item=3D=
1.

Eliot


> On 27 Jul 2020, at 08:05, Ole Jacobsen =
<olejacobsen=3D40me.com@dmarc.ietf.org> wrote:
>=20
> Hi Eliot (before I get some sleep),
>=20
> It would be REALLY useful if you could give us the actual link to
> how to participate in this meeting. I believe only registered =
attendees
> can attend which presumably means entering our reg number at some URL
> to get let in and so on.
>=20
> Please elaborate.
>=20
> (Yes, I know this is probably somewhere on the meeting website, but I
> think we should all get into the habit of creating meeting invitations
> that do more than place an entry in a calendar with the agenda).
>=20
> Thanks in advance,
>=20
> Ole
>=20
>> On 16 Jul 2020, at 03:20, Eliot Lear =
<lear=3D40cisco.com@dmarc.ietf.org> wrote:
>>=20
>> Colleagues,
>>=20
>> A reminder: we will meet virtually on the 27th of July from 14:10 to =
15:50 as part of the 108 meeting.  Agenda picking tool does not let you =
select this meeting.  There is an iCal event included in this message so =
that you can see it on your calendars if you wish.  Yours truly is a =
meetecho neophyte, and so I beg your patience we have a bumpy start.
>>=20
>> A few additional points:
>> 	=E2=80=A2 Materials have been uploaded.  These include the =
agenda and the chairs=E2=80=99 slides.  We have adjusted one question =
from discussion based on feedback from EKR.  Now is a good time to =
discuss those questions.
>> 	=E2=80=A2 The chairs seek a jabber scribe/minute taker.  Tim =
Wicinski has been extraordinarily helpful in the past, but it would be =
nice if someone else could take the role so that he can have a break.
>> 	=E2=80=A2 Our time will be precious.  It will be important for =
people to be familiar with the material prior to the meeting.  The =
chairs intend for the meeting to move pretty quickly along.   We will be =
doing some hums as you will see.
>> 	=E2=80=A2 One of the things we haven=E2=80=99t discussed, and is =
not on the agenda, is future meetings.  I think that may be something we =
may need to discuss in some detail, perhaps toward the end of the =
meeting, based on how hums go, and how we see our work from that point.
>> A reminder of the agenda:
>> 	=E2=80=A2 Agenda Bashing
>> 	=E2=80=A2 What we=E2=80=99ve covered
>> 	=E2=80=A2 Decisions we=E2=80=99ve made
>> 	=E2=80=A2 Questions we=E2=80=99ve asked
>> 	=E2=80=A2 Refinements on those questions
>> 	=E2=80=A2 Some hums
>> 	=E2=80=A2 Wanted: one document editor
>> 	=E2=80=A2 AOB
>> Eliot
>>=20
>> <rfcefdp.ics>
>> --=20
>> Rfced-future mailing list
>> Rfced-future@iab.org
>> https://www.iab.org/mailman/listinfo/rfced-future
>=20
> Ole J. Jacobsen
> Editor and Publisher
> The Internet Protocol Journal
> Office: +1 415-550-9433
> Cell:   +1 415-370-4628
> Web: protocoljournal.org
> E-mail: olejacobsen@me.com
> E-mail: ole@protocoljournal.org
> Skype: organdemo
>=20