Re: [regext] Re-chartering REGEXT?
InterNetX - Marco Schrieck <marco.schrieck@internetx.com> Tue, 16 April 2024 14:41 UTC
Return-Path: <marco.schrieck@internetx.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 86DF5C14F710 for <regext@ietfa.amsl.com>; Tue, 16 Apr 2024 07:41:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level:
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iy20izXER60C for <regext@ietfa.amsl.com>; Tue, 16 Apr 2024 07:41:32 -0700 (PDT)
Received: from mx1.internetx.com (mx1.internetx.com [62.116.129.39]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C5CCBC14F684 for <regext@ietf.org>; Tue, 16 Apr 2024 07:41:31 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mx1.internetx.com (Postfix) with ESMTP id E89974C4C524 for <regext@ietf.org>; Tue, 16 Apr 2024 16:41:28 +0200 (CEST)
X-Virus-Scanned: InterNetX GmbH amavisd-new at ix-mailer.internetx.de
Received: from mx1.internetx.com ([62.116.129.39]) by localhost (ix-mailer.internetx.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8VUhkpmTbS2J for <regext@ietf.org>; Tue, 16 Apr 2024 16:41:25 +0200 (CEST)
Received: from [192.168.100.95] (pizza.internetx.de [62.116.129.3]) by mx1.internetx.com (Postfix) with ESMTPSA id 9EC724C4C0E3 for <regext@ietf.org>; Tue, 16 Apr 2024 16:41:25 +0200 (CEST)
Message-ID: <767a3023-1109-41ca-a55b-0d80a6e9aba1@internetx.com>
Date: Tue, 16 Apr 2024 16:41:25 +0200
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
To: regext@ietf.org
References: <50556621-BBB1-41D8-A167-96508F5FF0C6@sidn.nl> <CAAQiQRezKGVaSdqb9nRKhw3Jdd+0R=Tikhe0hQgsq8vMcGGTgQ@mail.gmail.com> <92D7BA88-CC1C-4A5E-9407-BCAE029FAFA3@verisign.com> <CAKr6gn1H2fDcwyWN4L-_hOQY9O2biBwD07udQ=VHpAg4F1J2mQ@mail.gmail.com>
Content-Language: en-US
From: InterNetX - Marco Schrieck <marco.schrieck@internetx.com>
Organization: InterNetX GmbH
In-Reply-To: <CAKr6gn1H2fDcwyWN4L-_hOQY9O2biBwD07udQ=VHpAg4F1J2mQ@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/regext/EZjr1HLd2tkmu_9iK_XhiwYScpg>
Subject: Re: [regext] Re-chartering REGEXT?
X-BeenThere: regext@ietf.org
X-Mailman-Version: 2.1.39
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: Tue, 16 Apr 2024 14:41:36 -0000
Hello I fully agree with you. Regards marco On 16.04.24 01:14, George Michaelson wrote: > I don't think the new protocol is just a new transport *LAYER* but I > also do support re-charter to include consideration of this protocol > suite. > > My reasoning is that we're the people who are going to wind up having > to talk about it. Of course it's irritating from a perspective of RDAP > and EPP proponents to see more work jammed into this WG and I actually > generally dislike charter extension, but the context is clear: > > The protocol is in the registry-registrar and client-registrar > interaction space we work on. > > G > > On Tue, Apr 16, 2024 at 3:37 AM Gould, James > <jgould=40verisign.com@dmarc.ietf.org> wrote: >> Andy, >> >> REPP is not a transport, but a new provisioning protocol that is not supported in the existing charter. If you believe REPP is a transport, please describe how it complies with section 2.1 of RFC 5730. >> >> Thanks, >> >> -- >> >> JG >> >> >> >> James Gould >> Fellow Engineer >> jgould@Verisign.com <applewebdata://13890C55-AAE8-4BF3-A6CE-B4BA42740803/jgould@Verisign.com> >> >> 703-948-3271 >> 12061 Bluemont Way >> Reston, VA 20190 >> >> Verisign.com <http://verisigninc.com/> >> >> >> >> >> On 4/15/24, 1:20 PM, "regext on behalf of Andrew Newton (andy)" <regext-bounces@ietf.org <mailto:regext-bounces@ietf.org> on behalf of andy@hxr.us <mailto:andy@hxr.us>> wrote: >> >> >> Caution: This email originated from outside the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. >> >> >> Maarten, >> >> >> I think proposing some charter text is a good idea. >> >> >> And I support this if the charter is to be used to exclude some >> proposals for EPP transports but not others, as has been argued. >> >> >> -andy >> >> >> On Thu, Apr 11, 2024 at 11:59 PM Maarten Wullink >> <maarten.wullink=40sidn.nl@dmarc.ietf.org <mailto:40sidn.nl@dmarc.ietf.org>> wrote: >>> Hello everyone, >>> >>> The REGEXT WG charter seems to be limited to only allow work on EPP extensions? >>> >>> The WG preliminary consensus is that updating the charter for new transports (requires RFC5730, sec 2.1 compliance) is not required. >>> Because a new transport is regarded as a type of extension, so for anything else we would need to update the charter? >>> >>> This means there is no defined process anywhere, currently, for EPP related work, such as RESTful EPP (or anything else that is not a extension), >>> which according to some in this WG is not a transport but something else. >>> >>> RESTful EPP does not require modification of the EPP RFCs, it does include support for alternative data representations such as JSON. >>> >>> The participants of this WG are the experts in this area, and the right people to also work on improvements and/or enhancements of the EPP protocol and new work such as RESTful EPP. >>> >>> Therefore, I propose that we expand the charter of this WG to also include the above-mentioned activities e.g. not strictly limiting the WG to extensions only. >>> >>> I’m willing to help in updating the charter if this something we agree on doing. >>> >>> Best, >>> >>> Maarten >>> >>> ------ >>> ps: >>> >>> The previous version of the charter included text, that did allow work on more than extensions only: >>> >>> “The working group may also, in consultation with its responsible area >>> director, take on work related to the operation of Internet identifier >>> registries, beyond the EPP and RDAP protocols.” >>> >>> See: https://secure-web.cisco.com/1pZ9xY4B2hhezD1LASpYU9C9QLU_I8ijwDhrAONiX2WujSy1_vkXH6R3dC-XOs3hs8GhnjSqn4hoIrURMcauciMp2aW9yObvXrtcQfNn5y39QAI_y_nrDueqrchdGrckElb2y8uY6jnSOVocfgGUy3JGWGYYRDY4eaaVGYW4p0HCiWXl_U-V5l_hWGXcSEavgzX-crhYmdNvhH-u2THur7He9dDY47ixzEm4kaOgHenXF4Mjj6Xw63FB7TA6StLsEn1cH4ZzXrkRso6sqhMOPIxW0M12SiAp3Az1rqdgYd_E/https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fcharter-ietf-regext%2F01-00%2F <https://secure-web.cisco.com/1pZ9xY4B2hhezD1LASpYU9C9QLU_I8ijwDhrAONiX2WujSy1_vkXH6R3dC-XOs3hs8GhnjSqn4hoIrURMcauciMp2aW9yObvXrtcQfNn5y39QAI_y_nrDueqrchdGrckElb2y8uY6jnSOVocfgGUy3JGWGYYRDY4eaaVGYW4p0HCiWXl_U-V5l_hWGXcSEavgzX-crhYmdNvhH-u2THur7He9dDY47ixzEm4kaOgHenXF4Mjj6Xw63FB7TA6StLsEn1cH4ZzXrkRso6sqhMOPIxW0M12SiAp3Az1rqdgYd_E/https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fcharter-ietf-regext%2F01-00%2F> >>> >>> This was modified for the current charter, but still not very specific and may allow for work on RESTful EPP? >>> >>> "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.” >>> >>> >>> _______________________________________________ >>> regext mailing list >>> regext@ietf.org <mailto:regext@ietf.org> >>> https://secure-web.cisco.com/1KvgG0690znrXWuB3hdtOx8bFSBFJMVkNZ5g8zPMeStofdEIwM5iRQBNJUcSsE6gROXlW9ce2rNNyP9JIFNMdD3qAJa8xrA2wKLFakvQ61DRHxQLVjdwPbxzo5BV1itYp75wcGjQk4CwDA0lQI54wUygUhug3rcMp5yeQb9_PLgXgM8eklr87_hvlNWXU_-41hgJWbb4kMACk-BRDzKtZHXPAUm6b27OZrVUNee4FpEbr5z2ZmhGFmjGtaGbOFxjlmkUq5FUncipetsTP1KpPA-g33rNu37yQBieczmC5kkY/https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Fregext <https://secure-web.cisco.com/1KvgG0690znrXWuB3hdtOx8bFSBFJMVkNZ5g8zPMeStofdEIwM5iRQBNJUcSsE6gROXlW9ce2rNNyP9JIFNMdD3qAJa8xrA2wKLFakvQ61DRHxQLVjdwPbxzo5BV1itYp75wcGjQk4CwDA0lQI54wUygUhug3rcMp5yeQb9_PLgXgM8eklr87_hvlNWXU_-41hgJWbb4kMACk-BRDzKtZHXPAUm6b27OZrVUNee4FpEbr5z2ZmhGFmjGtaGbOFxjlmkUq5FUncipetsTP1KpPA-g33rNu37yQBieczmC5kkY/https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Fregext> >> >> _______________________________________________ >> regext mailing list >> regext@ietf.org <mailto:regext@ietf.org> >> https://secure-web.cisco.com/1KvgG0690znrXWuB3hdtOx8bFSBFJMVkNZ5g8zPMeStofdEIwM5iRQBNJUcSsE6gROXlW9ce2rNNyP9JIFNMdD3qAJa8xrA2wKLFakvQ61DRHxQLVjdwPbxzo5BV1itYp75wcGjQk4CwDA0lQI54wUygUhug3rcMp5yeQb9_PLgXgM8eklr87_hvlNWXU_-41hgJWbb4kMACk-BRDzKtZHXPAUm6b27OZrVUNee4FpEbr5z2ZmhGFmjGtaGbOFxjlmkUq5FUncipetsTP1KpPA-g33rNu37yQBieczmC5kkY/https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Fregext <https://secure-web.cisco.com/1KvgG0690znrXWuB3hdtOx8bFSBFJMVkNZ5g8zPMeStofdEIwM5iRQBNJUcSsE6gROXlW9ce2rNNyP9JIFNMdD3qAJa8xrA2wKLFakvQ61DRHxQLVjdwPbxzo5BV1itYp75wcGjQk4CwDA0lQI54wUygUhug3rcMp5yeQb9_PLgXgM8eklr87_hvlNWXU_-41hgJWbb4kMACk-BRDzKtZHXPAUm6b27OZrVUNee4FpEbr5z2ZmhGFmjGtaGbOFxjlmkUq5FUncipetsTP1KpPA-g33rNu37yQBieczmC5kkY/https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Fregext> >> >> >> >> _______________________________________________ >> 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 Marco Schrieck Bereichsleiter Entwicklung -- InterNetX GmbH Johanna-Dachs-Str. 55 • 93055 Regensburg • Germany Tel. +49 941 59559-0 internetx.com • internetx.com/linkedin • internetx.com/twitter Geschäftsführer: Elias Rendón Benger (CEO), Lars Krämer Amtsgericht Regensburg, HRB 7142
- [regext] Re-chartering REGEXT? Maarten Wullink
- Re: [regext] Re-chartering REGEXT? Andrew Newton (andy)
- Re: [regext] Re-chartering REGEXT? Gould, James
- Re: [regext] Re-chartering REGEXT? George Michaelson
- Re: [regext] Re-chartering REGEXT? Maarten Wullink
- Re: [regext] Re-chartering REGEXT? kowalik
- Re: [regext] Re-chartering REGEXT? Jasdip Singh
- Re: [regext] Re-chartering REGEXT? Mario Loffredo
- Re: [regext] Re-chartering REGEXT? kowalik
- Re: [regext] Re-chartering REGEXT? Andrew Newton (andy)
- Re: [regext] Re-chartering REGEXT? InterNetX - Marco Schrieck
- Re: [regext] Re-chartering REGEXT? Hollenbeck, Scott
- Re: [regext] Re-chartering REGEXT? Marc Blanchet
- Re: [regext] Re-chartering REGEXT? kowalik
- Re: [regext] Re-chartering REGEXT? James Galvin
- Re: [regext] Re-chartering REGEXT? Maarten Wullink
- Re: [regext] [Ext] Re-chartering REGEXT? Gavin Brown
- Re: [regext] [Ext] Re-chartering REGEXT? Maarten Wullink
- [regext] quasi-technical terms (was Re: [Ext] Re-… Andrew Newton (andy)