[dhcwg] DHC WG Meeting IETF 113

Timothy Winters <tim@qacafe.com> Fri, 21 January 2022 13:19 UTC

Return-Path: <tim@qacafe.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 716FD3A1F97 for <dhcwg@ietfa.amsl.com>; Fri, 21 Jan 2022 05:19:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=qacafe.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 PewpMMqBbkyE for <dhcwg@ietfa.amsl.com>; Fri, 21 Jan 2022 05:19:38 -0800 (PST)
Received: from mail-lj1-x236.google.com (mail-lj1-x236.google.com [IPv6:2a00:1450:4864:20::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 DC2DF3A1FA0 for <dhcwg@ietf.org>; Fri, 21 Jan 2022 05:19:37 -0800 (PST)
Received: by mail-lj1-x236.google.com with SMTP id w7so133531ljw.11 for <dhcwg@ietf.org>; Fri, 21 Jan 2022 05:19:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=qacafe.com; s=google; h=mime-version:from:date:message-id:subject:to; bh=TeWg4UXaVbfZLUUSdhg4oxHTTR/Ish5UF/2k9agVqHA=; b=CkWbQ7l0v6OC59o41BZy0yJiaSk5KMoUhZvzB9vRjZPriNzoMoNk+IgmzqE72ZlEvO I0iMnBHNoC9ZDdYQGOIUJ075m87hMIssGKeYpV84a2fzxAksGSzKPTA06IdBixgcnmKZ Xx+ivHoRfVtDudA0EeFok9cVHfwkIzw9ODC7Q=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=TeWg4UXaVbfZLUUSdhg4oxHTTR/Ish5UF/2k9agVqHA=; b=8HCcW1rodyrs3K84Y4hMuEzrJgR3fHV3W01zgTXIIy1buPdsZLwasIu4I1ioCQZnZN ahrNXj7u5d2G6nKwMXlZzvfd/mvnGmzNM1wWWm9ZpGOLShInCB81GZmbYixb1pkDuVDJ 3AdJxxoYvkxsM5eRv7eYJGVj0uQqt0nAwmXGY/s0OLyK/f5jWV9iwHa76yCl0bNIC5al GYfF1UdHB3+x4RgrsvaCr5ARIcpCqYaMnsQerFFhxOGNq+fq8amRD8WzftRYnRLqbKUY 9P4TbPA14OZdu7C0VVK8wmNCxV3lIWpmzDymJ5BCx2N+e1paoD2ypnxFsxEcX5pfPRlc k6rg==
X-Gm-Message-State: AOAM531yPGkwA5aLz5CqeGMF9s7OP/LbN9LnXF/9WTiwZxKGlJ9shC8E SpeMX0xNBmUdJLjZjK3hHjZFZbFAZMHGQBuaWWLCcUKNoB0/GQ==
X-Google-Smtp-Source: ABdhPJyWkgXCJmnkAMrcdHqvqcZ2AKaF+hunMu2sExzi9WOzmJ4SvolmRcrNvA4mOuwLFASxSveOh7EeeGtUgWfca9Q=
X-Received: by 2002:a2e:9b17:: with SMTP id u23mr3191266lji.330.1642771174782; Fri, 21 Jan 2022 05:19:34 -0800 (PST)
MIME-Version: 1.0
From: Timothy Winters <tim@qacafe.com>
Date: Fri, 21 Jan 2022 08:19:23 -0500
Message-ID: <CAJgLMKvsSTu=yintNUTH+hOGPX5RaqQRSmbpdwpS3EfVUBtoMw@mail.gmail.com>
To: dhcwg <dhcwg@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000521bd605d6177832"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dhcwg/PJtRP6W20GZmImB12k8L2xTbAiA>
Subject: [dhcwg] DHC WG Meeting IETF 113
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Dynamic Host Configuration <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Jan 2022 13:19:43 -0000

Hello,

Bernie and I are leaning towards not having a DHC WG meeting at IETF 113,
but having one at IETF 114.

As of writing this we only have one working group document (
https://datatracker.ietf.org/doc/draft-ietf-dhc-dhcpv6-yang/) that is in
IESG Review.

We will be starting work on Advancing 8415, which we'll be sending some
information out about shortly.

If someone does need us to reconsider requesting a DHC WG session for IETF
113, please contact the chairs promptly (the IETF deadline to request a
session is February 4) . In general, new potential work should be
initiated by submitting an individual-submission draft and sending details
to the DHC WG mailing list.

Thanks Everyone!

~Tim