[regext] Adam Roach's Yes on charter-ietf-regext-01-00: (with COMMENT)
Adam Roach <adam@nostrum.com> Tue, 24 July 2018 20:43 UTC
Return-Path: <adam@nostrum.com>
X-Original-To: regext@ietf.org
Delivered-To: regext@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 407141277C8; Tue, 24 Jul 2018 13:43:51 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Adam Roach <adam@nostrum.com>
To: The IESG <iesg@ietf.org>
Cc: regext-chairs@ietf.org, regext@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.82.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <153246503118.22549.5199408324841357622.idtracker@ietfa.amsl.com>
Date: Tue, 24 Jul 2018 13:43:51 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/regext/7IXYqTckCuqmvYTknWm8Ap8z50A>
Subject: [regext] Adam Roach's Yes on charter-ietf-regext-01-00: (with COMMENT)
X-BeenThere: regext@ietf.org
X-Mailman-Version: 2.1.27
List-Id: Registration Protocols Extensions <regext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/regext>, <mailto:regext-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/regext/>
List-Post: <mailto:regext@ietf.org>
List-Help: <mailto:regext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/regext>, <mailto:regext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 Jul 2018 20:43:51 -0000
Adam Roach has entered the following ballot position for charter-ietf-regext-01-00: Yes 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-regext/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- This is a relatively minor change to the REGEXT charter, aimed at allowing the definition of, e.g., data formats for files that need to be generated by one organization and potentially read by another (see, e.g., https://tools.ietf.org/html/draft-arias-noguchi-registry-data-escrow-10 for an example of such a format). These are technically not part of the RDAP or EPP protocols, and therefore are not in scope of the current charter; however, they are directly related to registry data, and therefore share the same communities of interest and expertise.