Re: [regext] WGLC redux: REGEXT working group charter

Antoin Verschuren <ietf@antoin.nl> Fri, 07 September 2018 14:20 UTC

Return-Path: <ietf@antoin.nl>
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 2320D130F1E for <regext@ietfa.amsl.com>; Fri, 7 Sep 2018 07:20:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=antoin.nl
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 YEE6d9BVLIYJ for <regext@ietfa.amsl.com>; Fri, 7 Sep 2018 07:20:10 -0700 (PDT)
Received: from walhalla.antoin.nl (walhalla.antoin.nl [IPv6:2001:985:b3c0:1:e2cb:4eff:fe5e:3096]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 765D2130EBB for <regext@ietf.org>; Fri, 7 Sep 2018 07:20:10 -0700 (PDT)
Received: by walhalla.antoin.nl (Postfix, from userid 5001) id A5A0B280446; Fri, 7 Sep 2018 16:20:08 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=antoin.nl; s=walhalla; t=1536330008; bh=X6pUITwWxuj5cf0ATz15kEvPueqR3BFrLQwQ3xsqozM=; h=From:Subject:Date:References:To:In-Reply-To:From; b=h/0OR1s0uRVX7b/K5jC8U43gcmdRj1NU0xf7YlIP7IfC12rePP81JkIRdP2bTSLQ8 vvTrgo/8Be/+jutLzIhK2i/eTEg9Tnacfox5rXF+MtNQ8uw8BfwoS+JCasz2OkoNlf 1SbXYC+ZM5gRxywo8ktzoAt+luQO/YKqxsY+gqUY=
Received: from 192.168.1.131 (unknown [77.173.24.208]) by walhalla.antoin.nl (Postfix) with ESMTPSA id 8D19628017A for <regext@ietf.org>; Fri, 7 Sep 2018 16:20:05 +0200 (CEST)
From: Antoin Verschuren <ietf@antoin.nl>
Content-Type: multipart/signed; boundary="Apple-Mail=_B29D389A-5298-4A09-B023-3F096AB8C2A6"; protocol="application/pgp-signature"; micalg="pgp-sha256"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
Date: Fri, 07 Sep 2018 16:20:02 +0200
References: <EE97966C-ED38-44B2-B2E4-ECADF12DB751@elistx.com> <1535748374.1368478.1492979664.420FC310@webmail.messagingengine.com> <CAHXf=0pWm=Y1+5UC2hm8+Hd+W-FgfNW8aC3=jfdh1VGKidOGEA@mail.gmail.com>
To: Registration Protocols Extensions <regext@ietf.org>
In-Reply-To: <CAHXf=0pWm=Y1+5UC2hm8+Hd+W-FgfNW8aC3=jfdh1VGKidOGEA@mail.gmail.com>
Message-Id: <7F455DEC-F623-4BC8-9440-874AFE3FEC52@antoin.nl>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/regext/hPT1vXoLZfpoJQoIGDNQU7hlcVQ>
Subject: Re: [regext] WGLC redux: REGEXT working group charter
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, 07 Sep 2018 14:20:22 -0000

Alex,Patrick,

Thank you for your comments. You made some good suggestions.
I agree the scope of the bulletpoints are not that clear and not scoped narrow enough for people not in this working group and not knowing which documents we discussed.
How about changing the last paragraph with bulletpoints to this:

---
The working group may also take on work to develop specifications that
describe the following types of information exchanged between entities
involved in Internet identifier registration that are using the RDAP or
EPP protocols:

*Uniform representation formats for publishing local policy or
 configuration options regarding EPP and RDAP use.
*Data formats for files exchanged between registration entities that
 need insertion in or extraction from EPP or RDAP.
*Technical guidance for registration processes that are supported by
 EPP or RDAP.
—

To explain out thinking:
The “registry mapping” and similar documents will fall under bulletpoint 1
The draft-gould-regext-dataset and similar documents will fall under bulletpoint 2
The “dnsoperator-to-rrr-protocol” and similar documents will fall under bulletpoint 3

If you agree to this text, than we will change that in the version we resend to the IESG for reconsideration.

- --
Antoin Verschuren

Tweevoren 6, 5672 SB Nuenen, NL
M: +31 6 37682392






> Op 3 sep. 2018, om 17:31 heeft Alexander Mayrhofer <alex.mayrhofer.ietf@gmail.com> het volgende geschreven:
> 
> Hello everyone,
> 
> tl;dr - i do agree with all what Patrick said - more inline
> 
> On Fri, Aug 31, 2018 at 10:46 PM Patrick Mevzek <pm@dotandco.com> wrote:
>> And I still think it is too broad, especially "Data formats for files"
>> (which files? what data? why the format needs a specification and a working group?).
>> "Registry mapping" and "Registry transition" will probably seem obscure to anyone
>> outside of the working group. I am myself not even sure what it covers or not.
> 
> I do agree to these points. For a charter, i think the functional area
> would be required, and if there wasn't a draft names "registry
> mapping", i wouldn't know what it meant (quite blunt: would this
> covering the creation of a geographic map of all EPP/RDAP accessible
> registries? ;)
> 
> Some (hopefully more productive) thoughts:
> 
> "Data format for files" -> Data format, yes, but only in the scope of
> EPP/RDAP registries and between the involved parties. Limited to
> frequent cases of such data exchange.
> 
> "Registry mapping" -> Representation of configuration options for
> EPP/RDAP registries.
> 
> "Registry transition" -> not sure what we should standardize here... a
> process? Data beyond escrow?
> 
> I understand the intention behind all these, but it seems to me those
> reflect milestones rather than an abstract charter strategy.
> 
> best,
> Alex
> 
> _______________________________________________
> regext mailing list
> regext@ietf.org
> https://www.ietf.org/mailman/listinfo/regext