[DNSOP] Call for Adoption: RFC8499-bis
Tim Wicinski <tjw.ietf@gmail.com> Fri, 25 September 2020 15:23 UTC
Return-Path: <tjw.ietf@gmail.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 EFEC23A0EC5; Fri, 25 Sep 2020 08:23:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.087
X-Spam-Level:
X-Spam-Status: No, score=-2.087 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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, URIBL_BLOCKED=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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HborFWF-2tGc; Fri, 25 Sep 2020 08:23:54 -0700 (PDT)
Received: from mail-oo1-xc33.google.com (mail-oo1-xc33.google.com [IPv6:2607:f8b0:4864:20::c33]) (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 07F893A0E1B; Fri, 25 Sep 2020 08:23:54 -0700 (PDT)
Received: by mail-oo1-xc33.google.com with SMTP id y25so838575oog.4; Fri, 25 Sep 2020 08:23:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to:cc; bh=j7KF2VRBm6NFkdVWxSa232Qx3z9CBu/CKuOJZJQUD0s=; b=K7QdhJsPw0xEUl437ZrD+4dany4cGdLPdMva4l7jGS0mYJTI1Ra+vEJDM2Q+QtUurA EwF3qz+Y8N3iwMPQpujim1rqiMTkecu46jsH15ObsHZFnw6Wdzktm/ugVjhlLr9TibkV UWZtZ4vb0w/XgwYm7eOM26CnKrbn+xxN+dgQWmt/98yigsEGLNLVa1cjAnGvL2iItB+0 ka2HagdWlCaEQPQmtZ0/MbmGWIYtdqeLCcAf9lgVqutULVwhQd1rHm2TTyyzTC7Ga8dB yp4b0nJg60p7UGXhvLw8a1EzBu27lL8f237pWAU2QOKxsGjFL0EPaZtRlIeflG9w+xL5 zJGw==
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:cc; bh=j7KF2VRBm6NFkdVWxSa232Qx3z9CBu/CKuOJZJQUD0s=; b=O9b8seEeqc2wcpCdIkjXTjxEZR6fBbfN5gTTO+RNoz1CXCjT9kmno+rW7/0LfyWesw +tGqfEtYOa0seZWsZV/pO+WOZ8Z+5HNSyNuoTrKk/Z1GCYE/ksztr1hDlyILeW9Oup2Q Ku8m35+vcSnHPxt1BKcjAjxOC5IaIHRV7WMsryIoKY8rpR6UTxYiIYHpEBCAY2YekFNV asIDZiDlvNbF91teTWZOnorFt7bFlRMbO2TrnYcgYOFbZGl3cvm62yrBe4KWPyDSxMIK sllkoigcnn405lTK3fiSfmYm9g0bbp2f0WmkSAi0zuw72YTeeWJfzZnmQL1rvDBjdrK5 A6Gw==
X-Gm-Message-State: AOAM533k+y973B13qNe9Gw2zLTSQ3n/6Az6SaMOLGV8I/AuC0Xw6qI/e v1c2C0UQVXWapFADuVuBWPSpFDwhSUXjfaD3s73JrYNIcJhWWw==
X-Google-Smtp-Source: ABdhPJzhG0hWfTPLdxh1ZtEFdRcbAW+riVYB1MfCyicOXrT1L3oaPiK3hn8Sjn6Y91O0SyNWnd5Yomg6e9mqZkpze/g=
X-Received: by 2002:a4a:aec3:: with SMTP id v3mr1209141oon.66.1601047433081; Fri, 25 Sep 2020 08:23:53 -0700 (PDT)
MIME-Version: 1.0
From: Tim Wicinski <tjw.ietf@gmail.com>
Date: Fri, 25 Sep 2020 11:23:42 -0400
Message-ID: <CADyWQ+HO1fjuBWTmNNr1F4ydc=KPPpCeg01WTKsNaeNH0F2QJA@mail.gmail.com>
To: dnsop <dnsop@ietf.org>
Cc: dnsop-chairs <dnsop-chairs@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000084766a05b024e72b"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/ZCg3EmD9BSAXFUydFrd25h-0F6E>
Subject: [DNSOP] Call for Adoption: RFC8499-bis
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, 25 Sep 2020 15:23:56 -0000
During the IETF108 meeting, it was brought up by the chairs that we have been talking to the authors of RFC8499 on updating the document. We propose these steps: - Update some of the current language in the existing RFC8499 - Add new terms draft-ietf-dnsop-terminology-ter on which the WG agrees - Reach consensus and be ready for the Working Group Last Call in the IETF109 timeframe. This starts a Call for Adoption for RFC8499-bis Current text is https://tools.ietf.org/html/rfc8499 and the current terminology additions are https://tools.ietf.org/html/draft-ietf-dnsop-terminology-ter-02 Please review this draft to see if you think it is suitable for adoption by DNSOP, and comments to the list, clearly stating your view. Please also indicate if you are willing to contribute text, review, etc. This call for adoption ends: 9 October 2020 Thanks, tim wicinski DNSOP co-chair
- [DNSOP] Call for Adoption: RFC8499-bis Tim Wicinski
- Re: [DNSOP] [Ext] Call for Adoption: RFC8499-bis Paul Hoffman