[Coin] Fwd: [irsg] IETF 106 Final Agenda

Marie-Jose Montpetit <marie@mjmontpetit.com> Fri, 25 October 2019 22:07 UTC

Return-Path: <marie@mjmontpetit.com>
X-Original-To: coin@ietfa.amsl.com
Delivered-To: coin@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BA52F120041 for <coin@ietfa.amsl.com>; Fri, 25 Oct 2019 15:07:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.895
X-Spam-Level:
X-Spam-Status: No, score=-1.895 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_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mjmontpetit-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 ZcSJcg9f37lO for <coin@ietfa.amsl.com>; Fri, 25 Oct 2019 15:07:41 -0700 (PDT)
Received: from mail-il1-x12d.google.com (mail-il1-x12d.google.com [IPv6:2607:f8b0:4864:20::12d]) (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 3B50B120020 for <coin@irtf.org>; Fri, 25 Oct 2019 15:07:41 -0700 (PDT)
Received: by mail-il1-x12d.google.com with SMTP id t5so3116864ilh.10 for <coin@irtf.org>; Fri, 25 Oct 2019 15:07:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mjmontpetit-com.20150623.gappssmtp.com; s=20150623; h=from:mime-version:date:message-id:subject:to; bh=cH0aIqTz3ijsoQFrN2oWTVPUY3+3xEwFjj1qRjhXRIw=; b=AGYiCs4IT5uR6q0B6HDCxTqRLzwJXWMA+uMhnru9eLTB/e26Mx9h+mWd3Yf4zGACw3 DwDfblulyDmaLs52XObx1+Xubsks8MN8Fq3gTaf7pUC3EebDj/YF7uQG8px/XfdzJeru b8o+zLpRXp3gkkepN2g2aZ1pJQTu9gHeXH15bKTqEUMUtgyz5WbU5g6m8iYmYgx7y5Qn YtRcvUOxiYDy8u3EO2oNp3gepMEN+H9HpHC1KrEsAgbLUUEUrFgy1jBrVpXjwEVcnAJ/ whVBzZlgzujyiIFZwrT01bhFIE7oxu270uKkBWMOqB8tu5qjYDeFQFAwRKbTWTTkSzVi i+3w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:mime-version:date:message-id:subject:to; bh=cH0aIqTz3ijsoQFrN2oWTVPUY3+3xEwFjj1qRjhXRIw=; b=XZVRjYcJsbRDD5LNiveOaKsILB1E7XCfVLCrMv5kqB1vXhgp05E+xv80MBETvGytkD b0fmwgdGGBptMu3xpsm+CDD6mbLWWSeKbwIRBtLMdGd9k4W/CJ3n3aQpnCw7G/ThUrAZ FOqK6jTefQY3G+T0/KeL8GTdwbOAmjXsRT/JujBk2z2iW7xsT8DvJW+lbaRLpgQOYDKa Q+6tJQW0hRYMsDltEASS6MBM82rR3QappEtqp5xWxtuRGuIDzvCiifmOC/7aGm4KzHtN /oj7BD2nmKbA3cxP7a9khGcGAG1wJ7J5IiWhNpwrXTkAcxG9/YDZ0pCv6m/WDqHZkQVN bDOA==
X-Gm-Message-State: APjAAAVDQEj6h6hZTW8RoXSzfz78aFl7athFbN9S2aG85On60B1kObTH 1ORrcgTl26BekUlCd8XbXA1y/lSGRG58oIohs6gFV7XR
X-Google-Smtp-Source: APXvYqzSaTYg24fWmM1BJMw/J8v+us2Hv1YEM8Pw/O90QZJCYKdWeM9o7Q9fkw8Xx5OQew6rk1VBjjDI8UDdLRTa+mk=
X-Received: by 2002:a92:4743:: with SMTP id u64mr6989673ila.239.1572041260161; Fri, 25 Oct 2019 15:07:40 -0700 (PDT)
Received: from 1058052472880 named unknown by gmailapi.google.com with HTTPREST; Fri, 25 Oct 2019 22:07:39 +0000
From: Marie-Jose Montpetit <marie@mjmontpetit.com>
MIME-Version: 1.0
Date: Fri, 25 Oct 2019 22:07:39 +0000
Message-ID: <CAPjWiCQeHuzBR_CAPCtBJSpwg5agyhNvEuE4kmTyzOpUqd=Swg@mail.gmail.com>
To: coin@irtf.org
Content-Type: multipart/alternative; boundary="000000000000e279250595c36065"
Archived-At: <https://mailarchive.ietf.org/arch/msg/coin/3jOWDAqnkz30nyaQGQGvuDU5ZAM>
Subject: [Coin] Fwd: [irsg] IETF 106 Final Agenda
X-BeenThere: coin@irtf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "COIN: Computing in the Network" <coin.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/coin>, <mailto:coin-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/coin/>
List-Post: <mailto:coin@irtf.org>
List-Help: <mailto:coin-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/coin>, <mailto:coin-request@irtf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Oct 2019 22:07:44 -0000

Here we go. Please plan accordingly :)

mjm

Marie-José Montpetit, Ph.D.
Research Affiliate, MIT Media Laboratory
mariejose@mjmontpetit.com
mariejo@mit.edu

On October 25, 2019 at 5:23:31 PM, IETF Agenda (agenda@ietf.org) wrote:

IETF 106
Singapore
November 16-22, 2019
Hosted By: Nokia

The IETF 106 Final Agenda is now available. At this point only Area
Directors can submit changes in the form of a swap to agenda@ietf.org.

https://datatracker.ietf.org/meeting/106/agenda.html
https://datatracker.ietf.org/meeting/106/agenda.txt


While this is considered the final agenda for printing, changes may be made
to the agenda up until and during the meeting. Updates will be reflected on
the web versions of the agenda.


Side Meetings / Open Time

The experiment with open agenda time continues at IETF 106 in the same way
as IETF 105, with an hour and fifteen minutes each morning. Beverages will
be provided in the Stamford & Fairmont Ballroom Foyers from 08:00 - 09:00.
Meeting rooms will be available for signups from 08:30 - 09:45. Regular WG
sessions will begin at 10:00. In addition, two attendee signup rooms will
be available throughout the week as usual. Signups for meeting rooms begin
are now open.

- Meeting wiki: https://trac.ietf.org/trac/ietf/meeting/wiki/ietf106
- To reserve a side meeting room:
https://trac.ietf.org/trac/ietf/meeting/wiki/106sidemeetings
- IETF Meeting Room Policy:
https://www.ietf.org/how/meetings/meeting-rooms-policy/


Code Lounge

At IETF 106 WG Chairs will have the ability to organize sessions focused on
running code in an effort to diversify the type of work that happens during
IETF meetings. This will allow for groups to informally meet to brainstorm,
code, and test ideas in the Code Lounge, a portion of the IETF lounge set
aside for such activities. The area will be designated by signage. WG
chairs can sign up for timeslots here:
https://trac.ietf.org/trac/ietf/meeting/wiki/106codelounge

WG Chairs are encouraged to look at the final agenda and determine
timeslots that have the least conflict to ensure successful attendance to
the Code Lounge sessions as well as any traditional working group sessions.
It is okay for multiple WG chairs to sign up for the same timeslots. This
is in fact encouraged for work that spans multiple WGs.