[regext] Adopting Documents and Adding Milestones

"James Galvin" <galvin@elistx.com> Fri, 26 April 2019 18:50 UTC

Return-Path: <galvin@elistx.com>
X-Original-To: regext@ietfa.amsl.com
Delivered-To: regext@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CDE7F1204AF for <regext@ietfa.amsl.com>; Fri, 26 Apr 2019 11:50:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=elistx-com.20150623.gappssmtp.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 Q0LwEHBOXR0Y for <regext@ietfa.amsl.com>; Fri, 26 Apr 2019 11:50:17 -0700 (PDT)
Received: from mail-qk1-x72a.google.com (mail-qk1-x72a.google.com [IPv6:2607:f8b0:4864:20::72a]) (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 7E1B41205EF for <regext@ietf.org>; Fri, 26 Apr 2019 11:50:16 -0700 (PDT)
Received: by mail-qk1-x72a.google.com with SMTP id p19so2484052qkm.10 for <regext@ietf.org>; Fri, 26 Apr 2019 11:50:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=elistx-com.20150623.gappssmtp.com; s=20150623; h=from:to:subject:date:message-id:mime-version; bh=Xo+je2XEsSdyvc7yP7qoUhDjQ5F6dNJqF9ZMXk+V6Vk=; b=QyvxB4JRGDJa1LR+BuIZ9DrJXTJ7I7TMiL+XLyGSZb6lGRArvYwV4/WbEOjS4d6hXv BWGuisp8bh7MpJ6Woywd2+wMjQyGWljRkuuWiD6+/Eje58NCZ6MHXGz0bIX3IMQnjtHi PLCoffd6UWwknTvG/lxo8dDcJvgmBj52m32DQSkdELOKDk7/N7NrFHnJbCviEWnvI4yn 9wYFrnSE9syOnEZZ4op/Rjux84wSKwMdeQqLqVeqjJU1nz+0fLg4o9pOw5bej3po/vjA Bax96R5KdB7+O4bBr6H4LbuHmK7FUHbzVrjDlAH6XOIFPIp9vITmCQXH1zdsWkyRWTyW DkCw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:subject:date:message-id:mime-version; bh=Xo+je2XEsSdyvc7yP7qoUhDjQ5F6dNJqF9ZMXk+V6Vk=; b=IxWKHptQuMMU0jgzIVrKtcNJUfPUe3H4t89jrrB19V6i4zAcdPCAIKtXqE5J+qfrDV r5ps019te/GWc+q/82Vgc8vjkKcLwVCt5Cvp8JmxSstbpWcHbeBbCB0fOqeGOwbq+PRG PGfpTvHjjNTjf7eAmCmIhyakr0ylzvzAJHhsfdSIpYHfMHIVJuKx19Bn6AUItBqlBqJ8 Y5JVQWlJ3N9DuVTySJzu2Wa4S22sFnl23JO5gpogtajHEG1hPfCU05cGmTvAvDeP2uj1 ruTtnrJF15aOY6QdTPQ7M+13pAef71fVdkjCpKfepZpIBqyUFTCzWeOA53OXTJUOUHRN 0MEw==
X-Gm-Message-State: APjAAAUwqAmWwM8SMHP25VSX5VlMX53LM6wNOQBjpbnERp5zbBzuYNRv 0ZBdIixUD0Culz2ofFyRaDFT7/u0rDY=
X-Google-Smtp-Source: APXvYqxNhBEE5ca0WT2shqTXWkhoKG/6aoEGPgzOlIbZvTK9JljJc2Ia+noHSxjIMTg2tB/IESbFJA==
X-Received: by 2002:a37:6704:: with SMTP id b4mr111759qkc.207.1556304615309; Fri, 26 Apr 2019 11:50:15 -0700 (PDT)
Received: from [10.0.0.103] ([2601:154:c200:10:84ff:4c96:989:e8fa]) by smtp.googlemail.com with ESMTPSA id p27sm15753936qte.25.2019.04.26.11.50.14 for <regext@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 26 Apr 2019 11:50:14 -0700 (PDT)
From: James Galvin <galvin@elistx.com>
To: Registration Protocols Extensions <regext@ietf.org>
Date: Fri, 26 Apr 2019 14:50:15 -0400
X-Mailer: MailMate (1.12.4r5594)
Message-ID: <C1BC50CF-8638-45A1-8A04-23A4CB1DA1E1@elistx.com>
MIME-Version: 1.0
Content-Type: text/plain; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/regext/_9Dl3OlAnZL-9lpKOx7ZWkRXV2Q>
Subject: [regext] Adopting Documents and Adding Milestones
X-BeenThere: regext@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
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: Fri, 26 Apr 2019 18:50:27 -0000

As discussed at our last meeting at IETF104 Prague, we need to set 
milestones for ourself.  As part of the discussion we considered the set 
of documents we have and reminded ourselves that we have two separate 
tracks of work: RDAP related and registry, registrar, and EPP 
(registration) related.

It had been previously suggested we limit ourselves to at most 5 
milestones at a time, even though we have about 20 documents on our 
prospect list.  With the observation of two tracks of work, our area 
director agreed that we could have about 7 milestones at a time, which 
allows us to have about 3 documents per track active at a time.

Recall that in December 2018 we conducted a poll of our prospective 
documents that easily identified 5 documents with the greatest interest. 
  We have already gone through the process of adopting those 5 documents 
and we are ready to set milestones.

However, those 5 documents break down to the OpenID document, 3 RDAP 
related documents, and 1 registration related document.  The suggestion 
is to adopt two additional registration related documents to balance our 
work.

As it turns out, the next two documents from the interest poll conducted 
in December 2018 are registration related documents:

Registry Data Escrow Specification
https://datatracker.ietf.org/doc/draft-arias-noguchi-registry-data-escrow/

Domain Name Registration Data Objects Mapping
https://datatracker.ietf.org/doc/draft-arias-noguchi-dnrd-objects-mapping/

As a result, the chairs are proposing we adopt these two additional 
documents and then move forward with 7 milestones.

Following this message you will see two messages, one for each of the 
above documents to adopt it.  You will have the opportunity to indicate 
your preference for adopting or not each of those documents separately.

Following those messages you will see a message with a proposed set of 
milestones.  The chairs have decided to take one liberty with the 
proposed set of milestones and that is we are including the two 
documents above assuming that they will be adopted.  This will speed up 
our process!

However, rest assured, if the working group does not want to adopt these 
documents and prefers something different we will make the necessary 
adjustment.  Read the voting request carefully when you see it.

Thanks!

Antoin and Jim