Re: [dhcwg] IETF-115 London, DHC session topic request

Bernie Volz <bevolz@gmail.com> Mon, 17 October 2022 16:18 UTC

Return-Path: <bevolz@gmail.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 09CF5C1524BE for <dhcwg@ietfa.amsl.com>; Mon, 17 Oct 2022 09:18:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.105
X-Spam-Level:
X-Spam-Status: No, score=-2.105 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_ZEN_BLOCKED_OPENDNS=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 ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uRZWcCe2BJme for <dhcwg@ietfa.amsl.com>; Mon, 17 Oct 2022 09:18:28 -0700 (PDT)
Received: from mail-qt1-x829.google.com (mail-qt1-x829.google.com [IPv6:2607:f8b0:4864:20::829]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 666BFC1524BC for <dhcwg@ietf.org>; Mon, 17 Oct 2022 09:18:28 -0700 (PDT)
Received: by mail-qt1-x829.google.com with SMTP id g11so8012835qts.1 for <dhcwg@ietf.org>; Mon, 17 Oct 2022 09:18:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=to:in-reply-to:references:message-id:date:subject:mime-version:from :content-transfer-encoding:from:to:cc:subject:date:message-id :reply-to; bh=sQ6vtiOcBXpi4UDoA8ck2B6eyaKdnFhHd/EMhDkjDJQ=; b=kAG3TWXf3/PctIpRO8jRzVdqO+rzgOIjqHOpT5b9bXRrcnyYdolNn9+i2j888xZgGs JeLrfsPVQ72y/KyeOZVKKumwM1HQWZ3eGhFXumUJCpatBNhYcYW9Yop5mZk4YS9Ka+SU pC53B7FnwfulbvnRqr/U6q8w5Z7WLbHJJvOCVnmLyhiMcpV8fWOaTJg/FcE0+Bo3LSd+ Yl94sFE5XmM5QnVTWJroncaY/XLfvbw42mLAag1+EleVelBESJlrq6U2CRcvxXUjIrOK atJvaHU7+h4Rtp0gmwsST9owmxzo+6swu43KYmbHUfgVWQCKgN9FG4+OgbV2LCDqQkOo h05Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=to:in-reply-to:references:message-id:date:subject:mime-version:from :content-transfer-encoding:x-gm-message-state:from:to:cc:subject :date:message-id:reply-to; bh=sQ6vtiOcBXpi4UDoA8ck2B6eyaKdnFhHd/EMhDkjDJQ=; b=JL2Qv1cUgORIXDmaAfvhXje/quoC1EVCdtVp6RDGqrydKNMmoAThfuEjvK9NKCTp5c X2Vn0krJBaqd1pGlUXPxmg46jr8kHGzped8BVhHK0Oi/PzvsywseIsOZueVmfICQ2j8Z AvQr6KzFcuVRlXElcV9yLOBfoMW9/SbFfzNPSgEoma9x45oaEhUrg/8/1/y7yav/L7BC 0TVty9mfqgFN73eVoQsfPCkvEDTOVb6HXRZLLakfLDTPhiyqg78UQbfHFrUaLCler4gD 3A/fuQSTnhmUi9nRFiEmyGNzDQzOadKU/eVOYjpKHdGGZF0w/ygZqb6DxkCD8toa5GTv 9NxQ==
X-Gm-Message-State: ACrzQf3GFSn/Igm7xTMHGWVdb14p/dmmfaqiPzpdyc1V6A0NnlKQWVzA KXbopRIgkSNb4m5MtnGGYvtXF+cW6g==
X-Google-Smtp-Source: AMsMyM4yHKH2BduXqE48I/fehR8Aek2M537hVeQWT4Dg3DqNdbbdrgZwoaAhpsYeyXtnm8PXR3BHew==
X-Received: by 2002:a05:622a:4ce:b0:39c:de34:139a with SMTP id q14-20020a05622a04ce00b0039cde34139amr9574744qtx.380.1666023506858; Mon, 17 Oct 2022 09:18:26 -0700 (PDT)
Received: from smtpclient.apple (d-24-233-121-124.nh.cpe.atlanticbb.net. [24.233.121.124]) by smtp.gmail.com with ESMTPSA id s6-20020a05620a0bc600b006e6a7c2a269sm190440qki.22.2022.10.17.09.18.26 for <dhcwg@ietf.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 17 Oct 2022 09:18:26 -0700 (PDT)
Content-Type: multipart/alternative; boundary="Apple-Mail-218E4AA5-3399-4380-A0FF-7281B7BE2CE4"
Content-Transfer-Encoding: 7bit
From: Bernie Volz <bevolz@gmail.com>
Mime-Version: 1.0 (1.0)
Date: Mon, 17 Oct 2022 12:18:25 -0400
Message-Id: <56F9ADBA-8426-478A-A474-A2B3D1ED06EB@gmail.com>
References: <1976114A-7B79-4A2F-A20A-5B44C635E942@gmail.com>
In-Reply-To: <1976114A-7B79-4A2F-A20A-5B44C635E942@gmail.com>
To: dhcwg <dhcwg@ietf.org>
X-Mailer: iPad Mail (19G82)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dhcwg/t1BxDFRSBmaVnKGqoMZjXfGc3LA>
Subject: Re: [dhcwg] IETF-115 London, DHC session topic request
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.39
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: Mon, 17 Oct 2022 16:18:29 -0000

Hi, just a friendly reminder if you would like to have some time at the DHC WG session at the London IETF to discuss a topic. We have a 1 hour session scheduled for Tuesday 11/8 at 16:30.

The RFC8415bis first draft was submitted and discussing issues related to it will be on the agenda. See https://mailarchive.ietf.org/arch/msg/dhcwg/YIsIbQ3M7X1jW3-K6qIBUyBZwFk/.

There was an updated version of draft-cheng-dhc-distribute-srv6-locator-by-dhcp submitted that incorporated the feedback from IETF-114, but there has not been a request for time. See https://mailarchive.ietf.org/arch/msg/dhcwg/BxaVsOIaKDa8OEStL-_6r3TQDPI/.

- Bernie Volz (for DHC cochairs)

> On Sep 20, 2022, at 11:42 AM, Bernie Volz <bevolz@gmail.com> wrote:
> 
> Hi:
> 
> The co-chairs have decided to request a session at IETF-115 (London). One topic of discussion will be the forthcoming RFC8415 bis draft.
> 
> If others have topics they would like to offer for discussion, please contact the chairs to request time … please specify topic and related drafts, presenter(s), requested time, and brief description of need for time.
> 
> We did have some good discussion of the two related drafts (draft-wkumari-dhc-addr-notification and draft-cheng-dhc-distribute-srv6-locator-by-dhcp-01) during IETF-114, but those documents have not been updated since that discussion.
> 
> Just as an FYI, I will not be able to attend IETF-115 either physically or virtually, so Tim will be on his own.
> 
> - Bernie Volz