IETF Logo Mail Archive

[regext] Charter question (was Re: CALL FOR ADOPTION: draft-yao-regext-epp-quic and draft-loffredo-regext-epp-over-http)

"Andrew Newton (andy)" <andy@hxr.us> Tue, 11 February 2025 17:26 UTC

Return-Path: <andy@hxr.us>
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 02647C52D67A for <regext@ietfa.amsl.com>; Tue, 11 Feb 2025 09:26:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.903
X-Spam-Level:
X-Spam-Status: No, score=-1.903 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=hxr-us.20230601.gappssmtp.com
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 x0NYdw7RTKIx for <regext@ietfa.amsl.com>; Tue, 11 Feb 2025 09:26:17 -0800 (PST)
Received: from mail-pj1-x1029.google.com (mail-pj1-x1029.google.com [IPv6:2607:f8b0:4864:20::1029]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1FBB7C52D649 for <regext@ietf.org>; Tue, 11 Feb 2025 09:26:16 -0800 (PST)
Received: by mail-pj1-x1029.google.com with SMTP id 98e67ed59e1d1-2fa3fe04dd2so5462663a91.0 for <regext@ietf.org>; Tue, 11 Feb 2025 09:26:16 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hxr-us.20230601.gappssmtp.com; s=20230601; t=1739294776; x=1739899576; darn=ietf.org; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=EvhTYL1CSN2y3mmcitJxJAvdSaiiDm0n1qMWblJmUxs=; b=ABTboYTX5m+vKqqapWigthkbA//cEqiGj00kfTTxGwnhk6M0Ry5CM9zFk+5EJLPjqc Y5+8HJJv/Htlfh5El99UxXpCxJB3v2p/QmQPURb2tizYsyUP9I+oD/3w54ugZXPe1P6x HRlei0TmewXSVfYS68oFbnFZOupCGxXP0njDoK7HOSKy5sXQ1s581irPfUlzwiRsucCx uRBHvIHarNC7kHQ6a0kmHgyY3Etgm67CkOROho3yRV8bt/Sj46kBU8kdepYWhuLpHd7C lW4dX+jZ1hzw47hA18Mv/MdS+hbScVFnvP1L/F5reOFsVRTya21KbC1tjTXuUCQJYKvX rXcg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1739294776; x=1739899576; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=EvhTYL1CSN2y3mmcitJxJAvdSaiiDm0n1qMWblJmUxs=; b=vFzjJ9LQ0f754g3BUlGQpmtQ66ZEYHiH1OVQDznB8Kp2kkOprf2YvkZtCeEO9oRzHq aFO0P0jB/ZHNQtPG1kbxphxOZeyn/9EMEY8gMR/sCVHTL4i5C5pLRZZ2y4+6xbg5sb8D OrCCmWw9bVA1Inzq16vESUs+joHFbSulvtwtj543J8i6C/gcYecy/mkhw+b8KrrFJDxO 95++5jXCfv5i77N0OJhewKucAh1qtaLDg0qrb2YscJUGoDFxsxgbRgLr4C8AVya027aZ SZhL07Z0RDFKzO25j88ocle0uvj542wzBTyj5TgKHC2itg9OFpodQPwOopqIv2tBwgok KnCQ==
X-Gm-Message-State: AOJu0YzlTjJfdH4KH/WNTZkz62cXuiTOp46UcYINzK2Zuh2ZBC7nCo7s IsilN2daExGxnFiPrYyo6B2ASKna/Y9m18OvH0Vzl/ebWurAgZ0ugq8i8g0iNuz/+JSKNxTm1ZG QVMSUQNZfrzrWikJV/2+twl+onrdjWXEo+7TqFvGDOHUIvR+O4lE=
X-Gm-Gg: ASbGncuCbZ/lt1p/5qL3pRuFG0iGElScOo8Dg+craCvS933CyClIM020DxJx83L9rqh QbnUzxPVQRlsDHdkShZpfPpqboD9Sz8t4Z27Oz6Juznoy1CxMxArixOhHjy0Oy9cMN9siBw==
X-Google-Smtp-Source: AGHT+IENqcdHoVPIsHgFXGxz0G/MxQuBnTnA0UPu/4h1r32Y2Bw6T43CXMpueXfrUk05F5rGU1TZCLA2WY5eY12hIi4=
X-Received: by 2002:a17:90b:3c90:b0:2fa:15ab:4dff with SMTP id 98e67ed59e1d1-2fa243ed7e4mr24467464a91.31.1739294774557; Tue, 11 Feb 2025 09:26:14 -0800 (PST)
MIME-Version: 1.0
References: <A4407EAD-3F1B-452C-9F5B-764C80763AC1@elistx.com>
In-Reply-To: <A4407EAD-3F1B-452C-9F5B-764C80763AC1@elistx.com>
From: "Andrew Newton (andy)" <andy@hxr.us>
Date: Tue, 11 Feb 2025 12:26:03 -0500
X-Gm-Features: AWEUYZmyi-obuRv_bjpiMddeaqZPMHewQPScauIAOP6DPjjq8mklT53gmKWXB_I
Message-ID: <CAAQiQRdwaibyd7cOXGqGigzoOyXPxz34xNMMbiJ6qom0bCQyjQ@mail.gmail.com>
To: James Galvin <galvin@elistx.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Message-ID-Hash: QE5EK5QP4HBPZFVYXBJV6TBT2XERDYYN
X-Message-ID-Hash: QE5EK5QP4HBPZFVYXBJV6TBT2XERDYYN
X-MailFrom: andy@hxr.us
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-regext.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: Registration Protocols Extensions <regext@ietf.org>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [regext] Charter question (was Re: CALL FOR ADOPTION: draft-yao-regext-epp-quic and draft-loffredo-regext-epp-over-http)
List-Id: Registration Protocols Extensions Working Group <regext.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/regext/vf4JYowUl_IkYE3RpkTTj30iRlg>
List-Archive: <https://mailarchive.ietf.org/arch/browse/regext>
List-Help: <mailto:regext-request@ietf.org?subject=help>
List-Owner: <mailto:regext-owner@ietf.org>
List-Post: <mailto:regext@ietf.org>
List-Subscribe: <mailto:regext-join@ietf.org>
List-Unsubscribe: <mailto:regext-leave@ietf.org>

Hi all,

The work of REGEXT is to define extensions for EPP and RDAP, hence the
"EXT" in the name. With regards to the adoption calls for I-Ds
specifying new transports to EPP, where does this fall within the
charter? It has been stated that transports are EPP extensions, but
that argument cuts against the current RFCs. RFC 5730
discusses transports in section 2.1, separate from protocol extensions
in Section 2.7. And RFC 3735 lists 4 types of EPP extensions, none
being transports, and includes the sentence "EPP extensions MUST be
specified in XML."

As there does appear to be energy in the group to work on new EPP
transports, would the group be willing to recharter
to include the scope of I-Ds under discussion?

-andy
soon-to-be ART AD

On Mon, Feb 3, 2025 at 9:06 AM James Galvin <galvin@elistx.com> wrote:
>
> Continuing our potential adoption of new documents, as previously discussed the next two documents will be taken together.  The suggestion is to advance them together, although if these are adopted the working group can choose to advance them separately.
>
> This is a formal adoption request for both:
>
> Extensible Provisioning Protocol (EPP) Transport over QUIC
> https://datatracker.ietf.org/doc/draft-yao-regext-epp-quic/
>
> Extensible Provisioning Protocol (EPP) Transport over HTTPS
> https://datatracker.ietf.org/doc/draft-loffredo-regext-epp-over-http/
>
> Please review these drafts to see if you think they are suitable for adoption by REGEXT and reply to this message on the list, clearly stating your view.  Optionally indicate if you are willing to contribute text, review text, or be a document shepherd.
>
> This Call For Adoption will close on Sunday, 16 February 2025.
>
> If there are no objections, the chairs will consider these documents adopted.
>
> Thanks,
>
> Your REGEXT co-chairs Antoin and Jim
>
> _______________________________________________
> regext mailing list -- regext@ietf.org
> To unsubscribe send an email to regext-leave@ietf.org

v2.29.0 | Report a Bug | By Email | System Status