Re: [regext] Proposed Revision to our Charter

Antoin Verschuren <ietf@antoin.nl> Fri, 15 June 2018 12:06 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 60A46130DF2 for <regext@ietfa.amsl.com>; Fri, 15 Jun 2018 05:06:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level:
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, 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 8d8PLPPhOP9l for <regext@ietfa.amsl.com>; Fri, 15 Jun 2018 05:06:05 -0700 (PDT)
Received: from walhalla.antoin.nl (walhalla.antoin.nl [62.251.108.8]) (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 5EF63130DF5 for <regext@ietf.org>; Fri, 15 Jun 2018 05:06:05 -0700 (PDT)
Received: from [IPv6:2001:985:b3c0:1:462a:60ff:fef4:e7f2] (unknown [IPv6:2001:985:b3c0:1:462a:60ff:fef4:e7f2]) by walhalla.antoin.nl (Postfix) with ESMTPSA id EE20228017F for <regext@ietf.org>; Fri, 15 Jun 2018 14:06:02 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=antoin.nl; s=walhalla; t=1529064363; bh=Ypo0PAeL8lYiTH74Ms4Qb43qV0Q60GM7VCWKwh08LMg=; h=Subject:From:In-Reply-To:Date:References:To:From; b=ISz9I/5AuS9ek2fvGTEQFG+z5qE9bREYGycVAKFl6kW0K5b6O2BzMqdiIvgMb0bCC UTa51Bz8kaDtfi1DFG/V2amG+idcesxshMVoqWMc96MWq8Dm/bpFkckhXSs8QMy103 CBS1GHEauPcHrpK+sQDJGCFnn7f+ZbmIN5TpOS5A=
Content-Type: multipart/signed; boundary="Apple-Mail=_F7641FCE-7879-4B39-81CF-8001F27D1E72"; protocol="application/pgp-signature"; micalg="pgp-sha256"
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
X-Pgp-Agent: GPGMail
From: Antoin Verschuren <ietf@antoin.nl>
In-Reply-To: <CAAQiQRePPZtMJiwcYq=AJRO=6M9_nkROiEn0xx=9_1fxP2i1mQ@mail.gmail.com>
Date: Fri, 15 Jun 2018 14:05:55 +0200
Message-Id: <C46EC7F5-16AD-4BE7-B7D0-3B419C521B4A@antoin.nl>
References: <D6C067B9-E65C-4692-8AC3-BDC1430B97C6@elistx.com> <MW2PR02MB3899D7B485756BB05134BB29B17E0@MW2PR02MB3899.namprd02.prod.outlook.com> <CAAQiQRff3fQbwngnEtfiRQt9_kJep1Hv3Z7cLQyEX2z0d-7OoA@mail.gmail.com> <MW2PR02MB389992FCA6E53E727B1E1466B17E0@MW2PR02MB3899.namprd02.prod.outlook.com> <CAAQiQRePPZtMJiwcYq=AJRO=6M9_nkROiEn0xx=9_1fxP2i1mQ@mail.gmail.com>
To: Registration Protocols Extensions <regext@ietf.org>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <https://mailarchive.ietf.org/arch/msg/regext/FLvlKW4tioicJnFkhwk5tKBkHWc>
Subject: Re: [regext] Proposed Revision to our Charter
X-BeenThere: regext@ietf.org
X-Mailman-Version: 2.1.26
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, 15 Jun 2018 12:06:11 -0000

Ok, perhaps some clarification.

The broadening of the charter is not to broaden the scope of EPP or RDAP.
Both EPP and RDAP have always been protocols to serve any "internet infrastructure identifier registry”, be it TLD’s RIR’s, ENUM registries, 2nd/3th/4th/.. level domain registries, so currently basically domains or IP’s or anything that does something DNS, but we have never limited the protocols to be used by any other registry that could arise and saw it fit to use it for their provisioning.
We have chosen this term to avoid this working group to only think of policy limited gTLD’s as the only usage for EPP and RDAP, which is not true. ccTLD’s, sTLD’s, RIR’s and ENUM registries also use EPP and/or RDAP.

The only change to the charter is that we previously had only one permitted extra work item of the dns-operators draft beyond EPP and RDAP protocol work, because we had a long milestone list that our AD wanted us to do first before we took on new work items. Now that our milestone list shortens, we have more time to take on this additional work, but as the charter proposal says, it should be limited to work related to the provisioning of "internet infrastructure identifier registries” that use EPP or RDAP, and the extra limitation is our AD needs to approve the topic as being in scope.

I hope this helps, and if you have a better suggestion for scoping or wording, we’ll be happy to hear.
We have put this proposed charter out here for formal discusion on the mailinglist and we will also have an item on our agenda in Montreal to discuss.

- --
Antoin Verschuren

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






Op 13 jun. 2018, om 23:39 heeft Andrew Newton <andy@hxr.us> het volgende geschreven:

> Thanks for the clarification, Roger.
> 
> The file formats seem like appropriate work to me. That said, the
> wording of the proposed charter seemed to indicate to me there was a
> broader motivation. If there is such, it be best if it were stated.
> 
> -andy
> 
> On Wed, Jun 13, 2018 at 11:52 AM, Roger D Carney <rcarney@godaddy.com> wrote:
>> Good Morning,
>> 
>> 
>> 
>> I was definitely not thinking of two working groups.
>> 
>> 
>> 
>> The focus of the WG is EPP and RDAP extensions. The additional suggested
>> wording just adds on the ability to take on relevant (as determined by WG
>> and AD) work (e.g. Third Party DNS Operator…). My suggestion was not to
>> exclude, but to provide more focused wording. Maybe that wording is better,
>> change the entire sentence to state: “The working group may also take on
>> relevant (as determined by WG and AD) work, beyond the EPP and RDAP
>> protocols.”
>> 
>> 
>> 
>> Andy, I think your original question that you posted earlier in the week is
>> what needs to be answered first, paraphrasing “what is the motivation for
>> this change”. Several others I think have basically asked the same question.
>> 
>> 
>> 
>> I don’t think I was the one asking for the charter change but here are my
>> thoughts on why I see a change being beneficial.
>> 
>> 
>> 
>> To me this started with the proposed Third Party DNS Operator document. At
>> one point the Charter was updated to add in this specific item (our current
>> Charter). Then over the past year some discussions were had on standardizing
>> the files that registries and registrars share (Unavailable Names,
>> Non-Standard/Premium Domain Fees, Invoicing) which lead into the discussion
>> of standardizing the storage of these files and other items (reporting comes
>> to mind). Today different registries have different web portals and ftp
>> sites to get this information from and different registrars request the
>> information in different formats. Many registries and registrars have agreed
>> that they would like to see a much better experience here. These topics do
>> not fit into the EPP/RDAP focus of our current charter but the people with
>> the most interest and expertise in these ideas are in this WG.
>> 
>> 
>> 
>> 
>> 
>> Thanks
>> 
>> Roger
>> 
>> 
>> 
>> 
>> 
>> -----Original Message-----
>> From: Andrew Newton [mailto:andy@hxr.us]
>> Sent: Wednesday, June 13, 2018 9:45 AM
>> To: Roger D Carney <rcarney@godaddy.com>
>> Cc: Registration Protocols Extensions <regext@ietf.org>
>> Subject: Re: [regext] Proposed Revision to our Charter
>> 
>> 
>> 
>> On Wed, Jun 13, 2018 at 10:35 AM, Roger D Carney <rcarney@godaddy.com>
>> wrote:
>> 
>>> Good Morning,
>> 
>>> 
>> 
>>> 
>> 
>>> 
>> 
>>> I agree with those saying this new wording seems a bit broad, what if
>> 
>>> "...related to the operation of Internet identifier registries..." was
>> 
>>> changed to "...related to the operation of Internet domain name
>> 
>>> registration systems..."?
>> 
>> 
>> 
>> What about RIRs? Or would you suggest we split REGEXT into two working
>> groups?
>> 
>> 
>> 
>> -andy
>> 
>> 
>> _______________________________________________
>> regext mailing list
>> regext@ietf.org
>> https://www.ietf.org/mailman/listinfo/regext
>> 
> 
> _______________________________________________
> regext mailing list
> regext@ietf.org
> https://www.ietf.org/mailman/listinfo/regext