Re: [Rfced-future] RFC Editors Future Program @ IETF 108
Eliot Lear <lear@cisco.com> Mon, 27 July 2020 06:15 UTC
Return-Path: <lear@cisco.com>
X-Original-To: rfced-future@ietfa.amsl.com
Delivered-To: rfced-future@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 032B33A16F9 for <rfced-future@ietfa.amsl.com>; Sun, 26 Jul 2020 23:15:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.601
X-Spam-Level:
X-Spam-Status: No, score=-9.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_PASS=-0.001, URIBL_BLOCKED=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 Y7XSa8hza_n5 for <rfced-future@ietfa.amsl.com>; Sun, 26 Jul 2020 23:15:52 -0700 (PDT)
Received: from aer-iport-3.cisco.com (aer-iport-3.cisco.com [173.38.203.53]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AD9F03A16F5 for <rfced-future@iab.org>; Sun, 26 Jul 2020 23:15:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3049; q=dns/txt; s=iport; t=1595830551; x=1597040151; h=mime-version:subject:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=WeVZxmyAWZsuXZNE3geNhYJ6aFRTpjcTWDPQmJb4AfU=; b=h0BKsUeuzrUfQDYRXNAzZwJHCQTT259f2HDVmkXBOQYItU6zlOrsi61c z5Dq+awnxyZd7tH1HByzbKE2QfB8TCCWx//JY1jQBe80o+JPJxQSG0CO4 rIjMSNdloYm0E7HHE1o8qzg3+LpPJVeTDzeJchpt6Qm29UrrS66DMVtEC g=;
X-IPAS-Result: A0A5AQDRcB5f/xbLJq1dAxsBAQEBAQEBAQUBAQESAQEBAwMBAQFAgUqBe4EeVAEgEiyENIkBh3glnAwLAQEBDAEBGAsMBAEBhEwCgiQlOBMCAwEBAQMCAwEBAQEFAQEBAgEGBG2FXAyFcQEBAQMBAQEhSwsFCQILGAICJgICFhEwBhOCW0sBgksDDiAPq2Z2gTKFUoJmFIIbBYEJKgGGOIZeggCBOAwQgk0+gQSBWAEDF4FGISaCTzOCLQSPS6YfgmiDCIVOkRgDHoJ7gSGIJ5MhhUWWf5EWg1YCBAYFAhWBaiOBVzMaCBsVOyoBgj4JNRIZDY42gQ0BCYJChRSFRD8DMAI1AgYBBwEBAwmQGAEB
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos;i="5.75,401,1589241600"; d="scan'208";a="25781104"
Received: from aer-iport-nat.cisco.com (HELO aer-core-1.cisco.com) ([173.38.203.22]) by aer-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 27 Jul 2020 06:15:47 +0000
Received: from ams3-vpn-dhcp4178.cisco.com (ams3-vpn-dhcp4178.cisco.com [10.61.80.81]) by aer-core-1.cisco.com (8.15.2/8.15.2) with ESMTPS id 06R6FljZ012151 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 27 Jul 2020 06:15:47 GMT
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>
X-Mailer: Apple Mail (2.3608.120.23.2.1)
X-Outbound-SMTP-Client: 10.61.80.81, ams3-vpn-dhcp4178.cisco.com
X-Outbound-Node: aer-core-1.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/rgNQBTnaxgnhW9L--gysYJbYwro>
Subject: Re: [Rfced-future] RFC Editors Future Program @ IETF 108
X-BeenThere: rfced-future@iab.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: RFC Editor Future Development Program <rfced-future.iab.org>
List-Unsubscribe: <https://www.iab.org/mailman/options/rfced-future>, <mailto:rfced-future-request@iab.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rfced-future/>
List-Post: <mailto:rfced-future@iab.org>
List-Help: <mailto:rfced-future-request@iab.org?subject=help>
List-Subscribe: <https://www.iab.org/mailman/listinfo/rfced-future>, <mailto:rfced-future-request@iab.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Jul 2020 06:15:54 -0000
Hi Ole: Please see https://meetings.conf.meetecho.com/ietf108/?group=rfcefdp&short=&item=1. Eliot > On 27 Jul 2020, at 08:05, Ole Jacobsen <olejacobsen=40me.com@dmarc.ietf.org> wrote: > > Hi Eliot (before I get some sleep), > > 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. > > Please elaborate. > > (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). > > Thanks in advance, > > Ole > >> On 16 Jul 2020, at 03:20, Eliot Lear <lear=40cisco.com@dmarc.ietf.org> wrote: >> >> Colleagues, >> >> 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. >> >> A few additional points: >> • Materials have been uploaded. These include the agenda and the chairs’ slides. We have adjusted one question from discussion based on feedback from EKR. Now is a good time to discuss those questions. >> • 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. >> • 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. >> • One of the things we haven’t 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: >> • Agenda Bashing >> • What we’ve covered >> • Decisions we’ve made >> • Questions we’ve asked >> • Refinements on those questions >> • Some hums >> • Wanted: one document editor >> • AOB >> Eliot >> >> <rfcefdp.ics> >> -- >> Rfced-future mailing list >> Rfced-future@iab.org >> https://www.iab.org/mailman/listinfo/rfced-future > > 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 >
- [Rfced-future] RFC Editors Future Program @ IETF … Eliot Lear
- Re: [Rfced-future] RFC Editors Future Program @ I… Martin J. Dürst
- Re: [Rfced-future] RFC Editors Future Program @ I… Eliot Lear
- Re: [Rfced-future] RFC Editors Future Program @ I… Brian E Carpenter
- Re: [Rfced-future] RFC Editors Future Program @ I… Eliot Lear
- Re: [Rfced-future] RFC Editors Future Program @ I… Ole Jacobsen
- Re: [Rfced-future] RFC Editors Future Program @ I… Eliot Lear