Re: [DNSOP] IETF meeting prep and what
Peter van Dijk <peter.van.dijk@powerdns.com> Fri, 18 June 2021 17:40 UTC
Return-Path: <peter.van.dijk@powerdns.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E89ED3A1BDC for <dnsop@ietfa.amsl.com>; Fri, 18 Jun 2021 10:40:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level:
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 RXBOCXgkoNLx for <dnsop@ietfa.amsl.com>; Fri, 18 Jun 2021 10:40:52 -0700 (PDT)
Received: from mx3.open-xchange.com (alcatraz.open-xchange.com [87.191.39.187]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 355E93A1BDB for <dnsop@ietf.org>; Fri, 18 Jun 2021 10:40:52 -0700 (PDT)
Received: from imap.open-xchange.com (imap.open-xchange.com [86.85.149.247]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx3.open-xchange.com (Postfix) with ESMTPSA id DE2C26A0E9; Fri, 18 Jun 2021 19:40:46 +0200 (CEST)
Received: from plato ([86.85.149.247]) by imap.open-xchange.com with ESMTPSA id zIOpNJ7azGDVVQAA3c6Kzw (envelope-from <peter.van.dijk@powerdns.com>); Fri, 18 Jun 2021 19:40:46 +0200
Message-ID: <5a9b35c5806e36b0802be493d87beb8ef2fef18d.camel@powerdns.com>
From: Peter van Dijk <peter.van.dijk@powerdns.com>
To: dnsop <dnsop@ietf.org>
Date: Fri, 18 Jun 2021 19:40:45 +0200
In-Reply-To: <CADyWQ+ESB-W9DvdRjCrdXgaZUWzX5b5cUvu-Ue3zjRrVsnCB2w@mail.gmail.com>
References: <CADyWQ+ESB-W9DvdRjCrdXgaZUWzX5b5cUvu-Ue3zjRrVsnCB2w@mail.gmail.com>
Organization: PowerDNS.COM B.V.
Content-Type: text/plain; charset="UTF-8"
User-Agent: Evolution 3.30.5-1.1
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/oVkgoEpFCsxullLyd5TFdE93lqM>
Subject: Re: [DNSOP] IETF meeting prep and what
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Jun 2021 17:40:57 -0000
On Wed, 2021-06-16 at 19:38 -0400, Tim Wicinski wrote: > All > > The chairs have been doing prep work for the upcoming IETF meeting; one issue that we are working on is reaching out to authors whose working group documents have recently expired. While doing this, Benno did some datatracker stuff and ended up with this list > > https://datatracker.ietf.org/doc/search?name=draft-ietf-dnsop&sort=&olddrafts=on&by=group&group=DNSOP > > All documents from 1 January 2016 onward are open for discussion. For the older documents that are left - if someone wishes to take them on, please reach out. aname can go; I trust the WG feels SVCB will supersede it. I hope MarkA can revive glue-is-not-optional. I propose replacing rfc5011-security-considerations with a short document deprecating 5011 in its entirety. I am happy to write text for that, if there is an appetite - when the WG queue is small enough! There are quite some things I like in rfc2317-bis, especially the parts where it proposes something -other than- slashes in labels. I am not offering to take it on at this time, though. Kind regards, -- Peter van Dijk PowerDNS.COM BV - https://www.powerdns.com/
- [DNSOP] IETF meeting prep and what Tim Wicinski
- Re: [DNSOP] IETF meeting prep and what Warren Kumari
- Re: [DNSOP] [Ext] IETF meeting prep and what Paul Hoffman
- Re: [DNSOP] [Ext] IETF meeting prep and what Paul Wouters
- Re: [DNSOP] IETF meeting prep and what Peter van Dijk
- Re: [DNSOP] IETF meeting prep and what Paul Wouters
- Re: [DNSOP] IETF meeting prep and what Joe Abley
- Re: [DNSOP] IETF meeting prep and what Paul Wouters
- Re: [DNSOP] IETF meeting prep and what Joe Abley
- Re: [DNSOP] IETF meeting prep and what Wes Hardaker
- Re: [DNSOP] [Ext] IETF meeting prep and what Paul Hoffman
- Re: [DNSOP] [Ext] IETF meeting prep and what Paul Hoffman
- Re: [DNSOP] [Ext] IETF meeting prep and what Daniel Migault
- [DNSOP] Review of draft-ietf-dnsop-rfc5011-securi… Paul Wouters
- Re: [DNSOP] [Ext] IETF meeting prep and what Tim Wicinski
- Re: [DNSOP] [Ext] IETF meeting prep and what Shumon Huque
- Re: [DNSOP] IETF meeting prep and what Anthony Eden
- Re: [DNSOP] [Ext] IETF meeting prep and what Michael StJohns
- Re: [DNSOP] Review of draft-ietf-dnsop-rfc5011-se… Michael StJohns
- Re: [DNSOP] IETF meeting prep and what Vladimír Čunát
- Re: [DNSOP] IETF meeting prep and what Joe Abley
- Re: [DNSOP] IETF meeting prep and what Brian Dickson
- Re: [DNSOP] IETF meeting prep and what Peter van Dijk
- Re: [DNSOP] IETF meeting prep and what Joe Abley
- Re: [DNSOP] IETF meeting prep and what Michael StJohns
- Re: [DNSOP] IETF meeting prep and what Mark Andrews
- Re: [DNSOP] IETF meeting prep and what Michael StJohns