[DNSOP] draft-johnson-dns-ipn-cla-07
Scott Johnson <scott@spacelypackets.com> Mon, 01 July 2024 11:29 UTC
Return-Path: <scott@spacelypackets.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 DDBFDC151995; Mon, 1 Jul 2024 04:29:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.908
X-Spam-Level:
X-Spam-Status: No, score=-1.908 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
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 ZltVA72zJThm; Mon, 1 Jul 2024 04:29:36 -0700 (PDT)
Received: from www.spacelypackets.com (www.spacelypackets.com [IPv6:2602:fdf2:bee:feed::ee]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ED6EFC15198F; Mon, 1 Jul 2024 04:29:31 -0700 (PDT)
Received: from scott (helo=localhost) by www.spacelypackets.com with local-esmtp (Exim 4.96) (envelope-from <scott@spacelypackets.com>) id 1sOFD6-0001I6-2L; Mon, 01 Jul 2024 11:28:40 +0000
Date: Mon, 01 Jul 2024 11:28:40 +0000
From: Scott Johnson <scott@spacelypackets.com>
To: dtn@ietf.org, dnsop@ietf.org
Message-ID: <803448b5-da5a-6865-0ac3-089b0baea631@spacelypackets.com>
MIME-Version: 1.0
Content-Type: text/plain; format="flowed"; charset="US-ASCII"
Message-ID-Hash: N4WWTRPDQWIXGPVYEL6Q5Y3CHRM3FQPH
X-Message-ID-Hash: N4WWTRPDQWIXGPVYEL6Q5Y3CHRM3FQPH
X-MailFrom: scott@spacelypackets.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-dnsop.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [DNSOP] draft-johnson-dns-ipn-cla-07
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/wrrCNqaQUWmqQqPLtOzNMvG6Oko>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Owner: <mailto:dnsop-owner@ietf.org>
List-Post: <mailto:dnsop@ietf.org>
List-Subscribe: <mailto:dnsop-join@ietf.org>
List-Unsubscribe: <mailto:dnsop-leave@ietf.org>
Hi All, Please find a new version of this draft, revised per recommendations from DNSOP and DTN members. https://datatracker.ietf.org/doc/draft-johnson-dns-ipn-cla/ I would be willing to entertain DTN WG taking up this document if there is an alternate proposal for the syntax for CLA RRTYPE, sections 3.2 and 4, and the WG so desires. If IANA is to make an official registry, a IANA Considerations section will need to be added to this or another document requesting such, and the document must run the gauntlet of the IETF, which starts with WG adoption. Unless and until this course of action is taken, these are only suggested values, but Section 3.2 of the draft governs the bounds of what those values _may_ be; basically a TXT with additional limitations as to character set. Thanks, Scott Johnson
- [DNSOP] draft-johnson-dns-ipn-cla-07 Scott Johnson