[Dance] John Scudder's No Objection on charter-ietf-dance-00-02: (with COMMENT)

John Scudder via Datatracker <noreply@ietf.org> Thu, 09 September 2021 12:33 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: dance@ietf.org
Delivered-To: dance@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id AED673A090B; Thu, 9 Sep 2021 05:33:20 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: John Scudder via Datatracker <noreply@ietf.org>
To: "The IESG" <iesg@ietf.org>
Cc: dance-chairs@ietf.org, dance@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 7.37.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: John Scudder <jgs@juniper.net>
Message-ID: <163119080055.20817.1235176727120133683@ietfa.amsl.com>
Date: Thu, 09 Sep 2021 05:33:20 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/dance/8zshToUZCV2NUHttZwuoDXAVZqA>
Subject: [Dance] John Scudder's No Objection on charter-ietf-dance-00-02: (with COMMENT)
X-BeenThere: dance@ietf.org
X-Mailman-Version: 2.1.29
List-Id: DANE Authentication for Network Clients Everywhere <dance.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dance>, <mailto:dance-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dance/>
List-Post: <mailto:dance@ietf.org>
List-Help: <mailto:dance-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dance>, <mailto:dance-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Sep 2021 12:33:21 -0000

John Scudder has entered the following ballot position for
charter-ietf-dance-00-02: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)



The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/charter-ietf-dance/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

The charter defines “RPK” as “raw public keys”. This is a near-collision with
“RPKI” defined in RFC 6480 as “resource public key infrastructure“. Maybe this
use of “RPK” is long-standing practice, in which case of course there’s not
much to be done. I point it out in case the observation is useful. (Also, the
acronym although defined is never referenced in the charter, so the definition
could easily be left out if desired. The same is true of a few other acronyms.)