[dispatch] BoF deadline for IETF-101

Mary Barnes <mary.ietf.barnes@gmail.com> Mon, 22 January 2018 18:56 UTC

Return-Path: <mary.ietf.barnes@gmail.com>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id CE95F1289B0 for <dispatch@ietfa.amsl.com>; Mon, 22 Jan 2018 10:56:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
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 ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id IUxZH9WWADbQ for <dispatch@ietfa.amsl.com>; Mon, 22 Jan 2018 10:56:40 -0800 (PST)
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 E2F09126D73 for <dispatch@ietf.org>; Mon, 22 Jan 2018 10:56:39 -0800 (PST)
Received: by mail-lf0-x22c.google.com with SMTP id f3so11907443lfe.4 for <dispatch@ietf.org>; Mon, 22 Jan 2018 10:56:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=Rhx7KB+XajAYBRujffKLRUavtajn+4IGJAErd07Kykk=; b=XUlpeMoPzFsbI3SwraBxyLm+po9yLZjWzAfVoPEeaX4C2banoxqVAaplFQO7pcXnaN jvBIKj2QU0Nltv71hyba7VIZW/jjOJ1KvcLiRaJTZnxScLtb1eFSnkWI6k6sJXwlVxCu 9NX6LczXSJU/BB3ZXi4JndzR5Q5UYjrs9eTJ/sYt7BS/13WXm30jDTpCPomdJBVQTaVQ edqbOI7ot/T4/VvLJ/sjE/iMha9AC2obh3Ucr/wQXkYK4Yrzh2S2699t0IF8qEtnZozR 8ML9n6mi7SS/nftJ1wC2y8QOpIQnSeM4D2cxaZk4p9DhlvX0a0CgTAxd9DkQo7hzHN3v BRjg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=Rhx7KB+XajAYBRujffKLRUavtajn+4IGJAErd07Kykk=; b=SEO4wJTqb/Iu9S8RsTZlJja78Cbcc9+v+qpQulf/VESItlyvlP4xRXvSQL/xEnmF4v dmNee8W6niiKiOLXHEEeQJhL3aGM4KZu51FEOZY22VBzjOkVUQh6MYDl2AokXrFc3ATq TBJkTxbXul9CYmIqWhG9rXjt1rSmi2pGj/LCBYG4t8tIE3xCa2fgUfDNQAi1Ttr/FaAI A4HPYQ6Ya9NKEB/RYuj+GOqRmunOkwtRqPyH+z5PiPBia6vlnLXTb00n2UHVT3BouvDP t1LZVJx932KLXR4dDksPP+sKUkB5UHOig4b1pQDcO7aWZO0LQJxY8WsDNtbcq26gwgrt JhXA==
X-Gm-Message-State: AKwxytf/fj/rrti2hKSEQdRP09wyKBE74ngIQph+aQE60TPWm1+v3/qh ttLv/UhuhD9t7JgbkEXAB46/k4632s7y2bXbbCvoug==
X-Google-Smtp-Source: AH8x224sdpY+53dYv5Y/chRbO1UbC/4AJ2qiHDNJ+AcrZp3a85LpLpEOjlIzIZce+o8rhTtwqUofEMl8IY11eccmj0Y=
X-Received: by with SMTP id 25mr4145469lju.104.1516647397834; Mon, 22 Jan 2018 10:56:37 -0800 (PST)
MIME-Version: 1.0
Received: by with HTTP; Mon, 22 Jan 2018 10:56:37 -0800 (PST)
From: Mary Barnes <mary.ietf.barnes@gmail.com>
Date: Mon, 22 Jan 2018 12:56:37 -0600
Message-ID: <CAHBDyN5h5euQ9iZc4O8Wq8=FD-PqLjzhEGNg7uz79DG=TyAtzg@mail.gmail.com>
To: DISPATCH <dispatch@ietf.org>
Content-Type: multipart/alternative; boundary="f403045fbd1065c349056361fd47"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/CHGmBYkcSLiY8X2LB_wnQzipAL4>
Subject: [dispatch] BoF deadline for IETF-101
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dispatch/>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Jan 2018 18:56:43 -0000

Hi all,

Sorry for the duplicate but I wanted to remind folks that since they moved
the Bof deadline up over the past few years and we've shifted the deadlines
to DISPATCH later over time, there's no longer an opportunity for us to
dispatch something as a BoF for the upcoming meeting.  So, if you think you
have new work that has any possibility of being a BoF, you need to be
working it through the BoF process.  If you're not sure, it's a really good
idea to get discussion going with the ADs and WG chairs *now*.

As a reminder, here are the DISPATCH WG deadlines:

   - Feb 2, 2018. Cutoff date for IETF BoF submissions.

   - Feb 10, 2018. Cutoff date to notify the chairs/DISPATCH WG of plans to
   submit a proposal.

   - Feb 15, 2018. Cutoff for charter proposals (i.e., problem statement
   and proposed deliverables) for topics.

   - Feb 21, 2018. Announcement of topics that have been dispatched for

   - March 3, 2018. Draft submission deadline.


---------- Forwarded message ----------
From: IETF Chair <chair@ietf.org>
Date: Mon, Jan 22, 2018 at 11:25 AM
Subject: New work proposals for IETF 101 due Feb 2
To: IETF Announcement List <ietf-announce@ietf.org>
Cc: IETF <ietf@ietf.org>

I wanted to remind everyone that the deadline to submit Birds of a Feather
(BoF) proposals for IETF 101 is rapidly approaching: Friday, February 2 at
23:59 UTC. Hopefully those whose have been working on ideas that seem like
they need to extend an existing working group’s charter, need a new working
group altogether, or need some dedicated face-to-face discussion in the
community have already been talking to your area directors [1] about these
proposals. If not, please do so right away! And please take a look at the
recommendations in RFC 5434 [2] about how to have a successful BoF.

Based on community discussion the IESG kicked off last fall [3], we have
updated the BoF wiki [4] to request some additional information from BoF
proponents. In addition to the information we require about every BoF
proposal, proponents are also encouraged to do the following in their BoF
wiki entries:

- List any protocols or practices that already exist in the space in which
the new work is being proposed.
- List any modifications to existing protocols or practices that will be
required by the new work.
- List any entirely new protocols or practices that will be required by the
new work.
- List any open source projects implementing the new work.

This information will allow the IESG, with the IAB’s assistance, to make
more informed decisions more quickly about BoF proposals.

Alissa Cooper
IETF Chair

[1] https://www.ietf.org/about/groups/iesg/members/
[2] https://tools.ietf.org/html/rfc5434
[3] https://mailarchive.ietf.org/arch/msg/ietf/orzFAklApVtBSlgK8LBb4Gc-OZY
[4] https://trac.tools.ietf.org/bof/trac/wiki/WikiStart