Last call, folks!
Scott
From: Row
Sent: Thursday, July 31, 2025 11:55 AM
Subject: [EXTERNAL] ROW14 - Final Call for Proposals
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
FYI, folks. Please note that the topic list described below isn’t exclusive.
Any topic focused on registry operations is in scope.
Scott
From: 'Row' via Regiops
Sent: Tuesday, June 24, 2025 7:20 AM
Subject: [EXTERNAL] [regiops] ROW14 - Call for proposals & registrations
Caution: This ema
FYI, people.
Scott
> -Original Message-
> From: internet-dra...@ietf.org
> Sent: Tuesday, June 17, 2025 3:16 PM
> To: i-d-annou...@ietf.org
> Subject: [EXTERNAL] I-D Action: draft-hollenbeck-rfc7451bis-00.txt
>
> Caution: This email originated from outside the organization. Do not click
From: kowa...@denic.de
Sent: Friday, June 13, 2025 6:03 AM
To: Hollenbeck, Scott ; maarten.wull...@sidn.nl;
a...@hxr.us
Cc: Gould, James ; regext@ietf.org
Subject: [EXTERNAL] Re: [regext] On bare identifiers in Extensions draft
Hi,
On 03.06.25 14:42, Hollenbeck, Scott wrote:
having
Thanks, Roger.
Scott
From: rcar...@godaddy.com
Sent: Tuesday, June 3, 2025 10:39 AM
To: drafts-expert-review-comm...@iana.org
Cc: Hollenbeck, Scott ; regext@ietf.org;
rcar...@godaddy.com; ietf...@gmail.com; gavin.br...@icann.org;
gal...@elistx.com; alex.mayrhofer.i...@gmail.com
Subject
I'd like a few minutes to discuss the need for a 7451bis draft, possibly with
Gavin Brown as co-presenter.
Scott
> -Original Message-
> From: James Galvin
> Sent: Monday, June 2, 2025 10:40 AM
> To: Antoin Verschuren
> Cc: REGEXT Working Group
> Subject: [EXTERNAL] [regext] Re: REGEXT
> -Original Message-
> From: Maarten Wullink
> Sent: Tuesday, June 3, 2025 2:12 AM
> To: Andrew (andy) Newton
> Cc: Pawel Kowalik ; Hollenbeck, Scott
> ; Gould, James ;
> regext@ietf.org
> Subject: [EXTERNAL] Re: [regext] On bare identifiers in Extensions draft
> -Original Message-
> From: Andrew (andy) Newton
> Sent: Friday, May 30, 2025 3:26 PM
> To: Pawel Kowalik ; Gould, James ;
> Hollenbeck, Scott ; regext@ietf.org
> Subject: [EXTERNAL] Re: [regext] Re: On bare identifiers in Extensions draft
>
> Caution: This email
so recommend removing the old registry entry and replacing it
with the two new entries to avoid confusion.
Scott
> -Original Message-
> From: David Dong via RT
> Sent: Tuesday, May 27, 2025 4:29 PM
> Cc: Hollenbeck, Scott
> Subject: [EXTERNAL] [IANA #1419774] Swedish Int
> -Original Message-
> From: Andrew (andy) Newton
> Sent: Wednesday, May 21, 2025 3:21 PM
> To: regext@ietf.org
> Subject: [EXTERNAL] [regext] unicode assignables and RDAP extensions
>
> Caution: This email originated from outside the organization. Do not click
> links
> or open attachmen
From: Gould, James
Sent: Wednesday, May 21, 2025 2:39 PM
To: kowa...@denic.de; Hollenbeck, Scott ;
a...@hxr.us; regext@ietf.org
Subject: Re: [EXTERNAL] [regext] Re: On bare identifiers in Extensions draft
I don’t view the use of a bare identifier as being a bad practice, since the
goal is to
> -Original Message-
> From: mohamed.boucad...@orange.com
>
> Sent: Wednesday, May 7, 2025 4:40 AM
> To: Hollenbeck, Scott ;
> i...@ietf.org
> Cc: draft-ietf-regext-epp-...@ietf.org; regext-cha...@ietf.org;
> regext@ietf.org;
> jkol...@godaddy.com
> S
Thanks for the comments, Paul. More below...
> -Original Message-
> From: Paul Wouters via Datatracker
> Sent: Thursday, May 8, 2025 9:39 AM
> To: The IESG
> Cc: draft-ietf-regext-epp-...@ietf.org; regext-cha...@ietf.org;
> regext@ietf.org;
> jkol...@godaddy.com; jkol...@godaddy.com
> S
> -Original Message-
> From: Ketan Talaulikar via Datatracker
> Sent: Tuesday, May 6, 2025 1:43 PM
> To: The IESG
> Cc: draft-ietf-regext-epp-...@ietf.org; regext-cha...@ietf.org;
> regext@ietf.org;
> jkol...@godaddy.com; jkol...@godaddy.com
> Subject: [EXTERNAL] Ketan Talaulikar's No Ob
It's in the regext archive.
Scott
> -Original Message-
> From: Andrew (andy) Newton
> Sent: Thursday, May 8, 2025 7:22 AM
> To: Hollenbeck, Scott ; epp...@ietf.org
> Subject: [EXTERNAL] Re: [regext] Does EPPEXT Still Work?
>
> Caution: This email originated fro
This is a test to see what happens to messages sent to epp...@ietf.org.
Scott
___
regext mailing list -- regext@ietf.org
To unsubscribe send an email to regext-le...@ietf.org
Thanks for the feedback, Med. More below...
> -Original Message-
> From: Mohamed Boucadair via Datatracker
> Sent: Monday, May 5, 2025 10:53 AM
> To: The IESG
> Cc: draft-ietf-regext-epp-...@ietf.org; regext-cha...@ietf.org;
> regext@ietf.org;
> jkol...@godaddy.com; jkol...@godaddy.com
Thanks for the review, Roman. More below...
> -Original Message-
> From: Roman Danyliw via Datatracker
> Sent: Friday, May 2, 2025 12:01 PM
> To: The IESG
> Cc: draft-ietf-regext-epp-...@ietf.org; regext-cha...@ietf.org;
> regext@ietf.org;
> jkol...@godaddy.com; jkol...@godaddy.com
> Su
+1
From: kowa...@denic.de
Sent: Tuesday, April 29, 2025 10:32 AM
To: Jasdip Singh ; Andrew (andy) Newton ; James
Galvin ; REGEXT Working Group
Subject: [EXTERNAL] [regext] Re: Experimental Extensions (was Re: ONE WEEK
REVIEW of FINAL proposed revised charter for REGEXT)
+1 from me as well
From: Jasdip Singh
Sent: Tuesday, April 22, 2025 11:05 AM
To: regext@ietf.org
Subject: [EXTERNAL] [regext] Sunsetting an RDAP extension
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
> -Original Message-
> From: Pawel Kowalik
> Sent: Wednesday, April 2, 2025 11:38 AM
> To: Andrew Newton (andy) ; regext@ietf.org
> Subject: [EXTERNAL] [regext] Re: simplifying the extensions rules
>
[SAH] [snip]
> Also talking about 22 issues seems an amplification to me, as one may thi
I’m interested and willing to attend virtually depending on the date and time.
Scott
From: James Galvin
Sent: Wednesday, April 2, 2025 10:21 AM
To: Jasdip Singh
Cc: Andrew Newton (andy) ; regext@ietf.org
Subject: [EXTERNAL] [regext] PLEASE RESPOND: INTERIM MEETING PLANNING (was:
simplifyin
FYI, folks!
Scott
From: 'Row' via Regiops
Sent: Thursday, April 3, 2025 7:20 AM
To: 'Row' via Regiops
Subject: [EXTERNAL] [regiops] ROW14 - Call for proposals
Caution: This email originated from outside the organization. Do not click
links or open attachments unless you recognize the se
This request looks fine to me, David.
Scott
> -Original Message-
> From: David Dong via RT
> Sent: Friday, March 14, 2025 9:22 PM
> Cc: a...@hxr.us; Hollenbeck, Scott ;
> regext@ietf.org
> Subject: [EXTERNAL] [IANA #1414867] expert review for draft-ietf-regext-rda
> -Original Message-
> From: Éric Vyncke via Datatracker
> Sent: Thursday, February 27, 2025 7:38 AM
> To: The IESG
> Cc: draft-ietf-regext-epp-delete-...@ietf.org; regext-cha...@ietf.org;
> regext@ietf.org; a...@hxr.us; a...@hxr.us; d...@fl1ger.de
> Subject: [EXTERNAL] Éric Vyncke's No O
IANA,
The XML schema that was registered by RFC 3915 and the schema found in the IANA
registry of XML schemas [1] are inconsistent. The schema found in RFC 3915
includes this element:
The value of this element differs in the schema found in the IANA registry. It
contains this value:
> -Original Message-
> From: Gould, James
> Sent: Friday, February 21, 2025 7:16 AM
> To: gavin.br...@icann.org; Hollenbeck, Scott
> Cc: regext@ietf.org
> Subject: Re: [EXTERNAL] [regext] Re: [Ext] RFC 3915 and
> elements
>
> Gavin,
>
> I agree with yo
This is indeed interesting. I just looked at the IETF DataTracker, which shows
the history of the draft that became RFC 3915. The last version of the draft
prior to RFC publication (draft-hollenbeck-epp-rgp-04) is missing the
maxOccurs="unbounded" attribute. That could explain where the schema i
> -Original Message-
> From: Gavin Brown
> Sent: Thursday, February 20, 2025 12:15 PM
> To: REGEXT Working Group
> Cc: Hollenbeck, Scott
> Subject: [EXTERNAL] RFC 3915 and elements
>
> Caution: This email originated from outside the organization. Do not
lowed this draft to proceed
with 5 extension identifiers. The registration requests for those identifiers
look fine.
Scott
> -Original Message-
> From: David Dong via RT
> Sent: Friday, February 14, 2025 11:21 PM
> Cc: a...@hxr.us; Hollenbeck, Scott ;
> regext@ietf.org
&g
> -Original Message-
> From: Andrew Newton (andy)
> Sent: Tuesday, February 18, 2025 2:02 PM
> To: Hollenbeck, Scott
> Cc: Gould, James ; regext@ietf.org
> Subject: [EXTERNAL] Re: [regext] Re: Charter question (was Re: CALL FOR
> ADOPTION: draft-yao-regext-epp-qu
> -Original Message-
> From: Gould, James
> Sent: Wednesday, February 12, 2025 8:15 AM
> To: a...@hxr.us; Hollenbeck, Scott
> Cc: regext@ietf.org
> Subject: Re: [EXTERNAL] [regext] Re: Charter question (was Re: CALL FOR
> ADOPTION: draft-yao-regext-epp-quic and draf
From: Pawel Kowalik
Sent: Wednesday, February 12, 2025 11:59 AM
To: Andrew Newton (andy)
Cc: regext@ietf.org
Subject: [EXTERNAL] [regext] Re: I-D Action:
draft-ietf-regext-rdap-extensions-05.txt
Hi Andy,
On 12.02.25 17:06, Andrew Newton (andy) wrote:
Allowing bare identifiers still l
> -Original Message-
> From: Andrew Newton (andy)
> Sent: Tuesday, February 11, 2025 12:26 PM
> To: James Galvin
> Cc: Registration Protocols Extensions
> Subject: [EXTERNAL] [regext] Charter question (was Re: CALL FOR ADOPTION:
> draft-yao-regext-epp-quic and draft-loffredo-regext-epp-o
> -Original Message-
> From: internet-dra...@ietf.org
> Sent: Monday, February 10, 2025 4:04 PM
> To: i-d-annou...@ietf.org
> Cc: regext@ietf.org
> Subject: [EXTERNAL] [regext] I-D Action: draft-ietf-regext-epp-eai-24.txt
>
> Caution: This email originated from outside the organization. Do
> -Original Message-
> From: John C Klensin
> Sent: Thursday, January 30, 2025 12:04 AM
> To: last-c...@ietf.org
> Cc: draft-ietf-regext-epp-...@ietf.org; jkol...@godaddy.com; regext-
> cha...@ietf.org; regext@ietf.org
> Subject: [EXTERNAL] Re: Last Call: (Use of
> Internationalized Email
> -Original Message-
> From: James Galvin
> Sent: Monday, February 3, 2025 9:06 AM
> To: Registration Protocols Extensions
> Subject: [EXTERNAL] [regext] CALL FOR ADOPTION: draft-yao-regext-epp-quic
> and draft-loffredo-regext-epp-over-http
>
> Caution: This email originated from outside
> On Jan 27, 2025, at 3:30 PM, Andrew Newton (andy) 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.
>
>> On Mon, Jan 27, 2025 at 3
> -Original Message-
> From: Andrew Newton (andy)
> Sent: Monday, January 27, 2025 2:57 PM
> To: Hollenbeck, Scott
> Cc: ietf=40antoin...@dmarc.ietf.org ; regext@ietf.org
> Subject: [EXTERNAL] Re: [regext] Re: CALL FOR ADOPTION: draft-jasdips-
> regext-rdap-rpki
>
s OK to use the first response received.
Scott
> -Original Message-
> From: David Dong via RT
> Sent: Sunday, January 26, 2025 1:13 AM
> Cc: Hollenbeck, Scott ; draft-ietf-regext-epp-
> eai@ietf.org; regext@ietf.org
> Subject: [EXTERNAL] [IANA #1411725] expert review
> -Original Message-
> From: David Dong via RT
> Sent: Sunday, January 26, 2025 1:13 AM
> Cc: Hollenbeck, Scott ; draft-ietf-regext-epp-
> eai@ietf.org; regext@ietf.org
> Subject: [EXTERNAL] [IANA #1411725] expert review for draft-ietf-regext-
> epp-eai (epp-ex
> -Original Message-
> From: Antoin Verschuren
> Sent: Monday, January 13, 2025 8:28 AM
> To: regext
> Subject: [EXTERNAL] [regext] CALL FOR ADOPTION: draft-jasdips-regext-rdap-
> rpki
>
> Caution: This email originated from outside the organization. Do not click
> links
> or open attac
Thanks for closing the loop, Tim.
Scott
From: Tim Bray
Sent: Tuesday, January 21, 2025 10:45 AM
To: Gould, James
Cc: m...@lowentropy.net; regext@ietf.org; drafts-expert-review-comm...@iana.org
Subject: [EXTERNAL] [regext] Re: [IANA #1410981] expert review for
draft-ietf-regext-epp-eai (xml
From: Tim Bray
Sent: Friday, January 17, 2025 11:12 AM
To: Gould, James
Cc: m...@lowentropy.net; regext@ietf.org; drafts-expert-review-comm...@iana.org
Subject: [EXTERNAL] [regext] Re: [IANA #1410981] expert review for
draft-ietf-regext-epp-eai (xml-registry)
Caution: This email originate
> -Original Message-
> From: internet-dra...@ietf.org
> Sent: Tuesday, December 3, 2024 11:26 AM
> To: i-d-annou...@ietf.org
> Cc: regext@ietf.org
> Subject: [EXTERNAL] I-D Action: draft-ietf-regext-epp-eai-23.txt
>
> Caution: This email originated from outside the organization. Do not cli
> -Original Message-
> From: Linda Dunbar via Datatracker
> Sent: Monday, December 2, 2024 12:56 PM
> To: gen-...@ietf.org
> Cc: draft-ietf-regext-epp-delete-bcp@ietf.org; last-c...@ietf.org;
> regext@ietf.org
> Subject: [EXTERNAL] Genart last call review of draft-ietf-regext-epp-delet
Given the options, my preference is to do nothing.
Scott
From: James Galvin
Sent: Monday, December 2, 2024 9:46 AM
To: Gould, James
Cc: joseph@gmail.com; Hollenbeck, Scott ;
a...@gulbrandsen.priv.no; regext@ietf.org
Subject: [EXTERNAL] Re: [regext] WGLC: draft-ietf-regext-epp-eai (was
> -Original Message-
> From: Carl Wallace via Datatracker
> Sent: Wednesday, November 27, 2024 4:37 PM
> To: sec...@ietf.org
> Cc: draft-ietf-regext-epp-delete-bcp@ietf.org; last-c...@ietf.org;
> regext@ietf.org
> Subject: [EXTERNAL] Secdir last call review of
> draft-ietf-regext-epp-
> -Original Message-
> From: Jiankang Yao via Datatracker
> Sent: Tuesday, November 26, 2024 9:29 AM
> To: a...@ietf.org
> Cc: draft-ietf-regext-epp-delete-bcp@ietf.org; last-c...@ietf.org;
> regext@ietf.org
> Subject: [EXTERNAL] Artart last call review of
> draft-ietf-regext-epp-dele
> -Original Message-
> From: Andrew Newton (andy)
> Sent: Friday, November 22, 2024 2:14 PM
> To: Hollenbeck, Scott
> Cc: regext@ietf.org
> Subject: [EXTERNAL] Re: [regext] Re: WGLC: draft-ietf-regext-epp-eai (was:
> WGLC: draft-ietf-regext-rdap-rir-search-09)
&g
> -Original Message-
> From: Andrew Newton (andy)
> Sent: Thursday, November 21, 2024 4:17 PM
> To: REGEXT Working Group
> Subject: [EXTERNAL] [regext] Re: WGLC: draft-ietf-regext-epp-eai (was: WGLC:
> draft-ietf-regext-rdap-rir-search-09)
>
> Caution: This email originated from outside t
> -Original Message-
> From: Gavin Brown
> Sent: Tuesday, November 19, 2024 5:12 AM
> To: James Galvin
> Cc: REGEXT Working Group
> Subject: [EXTERNAL] [regext] Re: [Ext] WGLC: draft-ietf-regext-epp-eai (was:
> WGLC: draft-ietf-regext-rdap-rir-search-09)
>
> Caution: This email originate
ginated from outside the organization. Do not click
> links
> or open attachments unless you recognize the sender and know the content is
> safe.
>
> Hollenbeck, Scott writes:
> > Please note that I have a comment from Joseph Yee that needs to be
> > addressed if there's no
> -Original Message-
> From: James Galvin
> Sent: Monday, November 18, 2024 9:17 AM
> To: kowa...@denic.de
> Cc: REGEXT Working Group
> Subject: [EXTERNAL] [regext] WGLC: draft-ietf-regext-epp-eai (was: WGLC:
> draft-ietf-regext-rdap-rir-search-09)
>
[SAH] [snip]
Please note that I have
Thanks, Ruth. Those both need to be fixed.
Scott
From: Ruth Trevor-Allen
Sent: Wednesday, November 13, 2024 3:13 AM
Cc: REGEXT Working Group
Subject: [EXTERNAL] [regext] Re: WGLC: draft-ietf-regext-rdap-rir-search-09
Caution: This email originated from outside the organization. Do not cl
Looks good to me!
Scott
> -Original Message-
> From: David Dong via RT
> Sent: Friday, November 8, 2024 3:48 PM
> Cc: Hollenbeck, Scott ; regext@ietf.org
> Subject: [EXTERNAL] [IANA #1393970] expert review for draft-ietf-regext-
> epp-ttl (epp-extensions)
>
RFC 8807 describes login improvements. There haven’t been ay other attempts to
extend the protocol that I’m aware of.
Scott
From: Victor Zhou
Sent: Thursday, October 17, 2024 5:37 PM
To: regext@ietf.org
Cc: Hollenbeck, Scott
Subject: [EXTERNAL] Question regarding client identifiers and
> -Original Message-
> From: Andrew Newton (andy)
> Sent: Thursday, October 17, 2024 2:10 PM
> To: James Galvin
> Cc: regext@ietf.org
> Subject: [EXTERNAL] [regext] Re: normative language and references in draft-
> ietf-regext-delete-bcp
>
> Caution: This email originated from outside th
From: Mario Loffredo
Sent: Friday, October 11, 2024 2:44 AM
To: Hollenbeck, Scott ; jasd...@arin.net;
a...@hxr.us; regext@ietf.org
Subject: [EXTERNAL] Re: [regext] Re: Extension Identifiers in
draft-ietf-regext-rdap-rir-search
Caution: This email originated from outside the organization. Do
> -Original Message-
> From: Andrew Newton (andy)
> Sent: Thursday, October 10, 2024 3:24 PM
> To: Hollenbeck, Scott ; regext@ietf.org
> Subject: [EXTERNAL] Re: [regext] Re: Comments Regarding draft-ietf-regext-
> rdap-extensions-04
>
> Caution: This email ori
comments might
have come in after the last call, but they were sent prior to AD review.
They're not invalid.
Scott
From: Jasdip Singh
Sent: Wednesday, October 9, 2024 12:47 PM
To: Hollenbeck, Scott ; a...@hxr.us; regext@ietf.org
Subject: [EXTERNAL] Re: [regext] Re: Extension Identifie
From: Jasdip Singh
Sent: Wednesday, October 9, 2024 11:54 AM
To: Hollenbeck, Scott ; a...@hxr.us; regext@ietf.org
Subject: [EXTERNAL] Re: [regext] Re: Extension Identifiers in
draft-ietf-regext-rdap-rir-search
Caution: This email originated from outside the organization. Do not click
links
From: Andrew Newton (andy)
Sent: Wednesday, October 9, 2024 11:47 AM
To: regext@ietf.org
Subject: [EXTERNAL] [regext] Re: Comments Regarding
draft-ietf-regext-rdap-extensions-04
Caution: This email originated from outside the organization. Do not click
links or open attachments unless you
From: Andrew Newton (andy)
Sent: Wednesday, October 9, 2024 11:41 AM
To: Hollenbeck, Scott ; regext@ietf.org
Subject: [EXTERNAL] Re: [regext] Extension Identifiers in
draft-ietf-regext-rdap-rir-search
Caution: This email originated from outside the organization. Do not click
links or open
In another thread focused on the extensions draft, I was asked "Would you like
regext to revisit Reverse Search?" That prompted me to take another look at the
draft. It currently defines five extension identifiers (two for path segments,
two for result data structures, and one for something else
From: Jasdip Singh
Sent: Monday, October 7, 2024 4:52 PM
To: Hollenbeck, Scott ; a...@hxr.us; regext@ietf.org
Subject: [EXTERNAL] Re: [regext] Re: Comments Regarding
draft-ietf-regext-rdap-extensions-04
Caution: This email originated from outside the organization. Do not click
links or
From: Joseph Yee
Sent: Friday, October 4, 2024 9:29 AM
To: regext@ietf.org
Subject: [EXTERNAL] [regext] Re: I-D Action: draft-ietf-regext-epp-eai-22.txt
Caution: This email originated from outside the organization. Do not click
links or open attachments unless you recognize the sender and know
From: Jasdip Singh
Sent: Monday, October 7, 2024 3:53 PM
To: Hollenbeck, Scott ; a...@hxr.us; regext@ietf.org
Subject: [EXTERNAL] Re: [regext] Re: Comments Regarding
draft-ietf-regext-rdap-extensions-04
Caution: This email originated from outside the organization. Do not click
links or
From: Andrew Newton (andy)
Sent: Monday, October 7, 2024 6:41 AM
To: Hollenbeck, Scott ; regext@ietf.org
Subject: [EXTERNAL] Re: [regext] Comments Regarding
draft-ietf-regext-rdap-extensions-04
Caution: This email originated from outside the organization. Do not click
links or open
From: Andrew Newton (andy)
Sent: Thursday, October 3, 2024 8:19 AM
To: Hollenbeck, Scott ; regext@ietf.org
Subject: [EXTERNAL] Re: [regext] Comments Regarding
draft-ietf-regext-rdap-extensions-04
Caution: This email originated from outside the organization. Do not click
links or open
I've read draft-ietf-regext-rdap-extensions-04 completely and have several
comments to share. An overarching comment is that any update to Standard 95
responses means that the modified responses will not be consistent with
"rdap_level_0". A new identifier will be needed. I'd very much prefer to
> -Original Message-
> From: Andrew Newton (andy)
> Sent: Monday, September 30, 2024 5:52 PM
> To: Hollenbeck, Scott
> Cc: jgould=40verisign@dmarc.ietf.org; gal...@elistx.com; regext-
> cha...@ietf.org; regext@ietf.org
> Subject: [EXTERNAL] Re: [regext]
I have two items that are either candidates for agenda time (if there's
something to discuss) or chair action before the meeting:
draft-ietf-regext-delete-bcp: waiting on chair action after the editors and
shepherd completed requested actions regarding normative language in the draft.
draft-iet
I'd like to echo something that Jim Gould noted below. As currently written,
the document proposes to update RFCs 7480, 9082, 9083. They're all part of
Standard 95. I'd REALLY like to see more discussion of the draft, though I will
note that expressions of support or concern can be made during t
This request looks fine to me.
Scott
> -Original Message-
> From: Amanda Baber via RT
> Sent: Wednesday, September 25, 2024 7:10 PM
> Cc: Hollenbeck, Scott
> Subject: [EXTERNAL] [IANA #1377600] EPP Extension Registration according
> to RFC7451
>
> Caution: Th
> -Original Message-
> From: kowa...@denic.de
> Sent: Thursday, September 19, 2024 9:47 AM
> To: Hollenbeck, Scott ; regext@ietf.org
> Subject: [EXTERNAL] Re: [regext] FW: Re: normative language and references
> in draft-ietf-regext-delete-bcp
>
> Hi Scott
I'm sending this to the list in the hope of prompting some movement. The
document authors and shepherd believe we've addressed the mailing list feedback
and the document is ready for AD review.
Scott
> -Original Message-
> From: Hollenbeck, Scott
> Sent: Wednesday,
This may be of interest to people here.
Scott
> -Original Message-
> From: IETF Secretariat
> Sent: Friday, August 23, 2024 3:13 PM
> To: IETF Announcement List
> Cc: r...@ietf.org
> Subject: [EXTERNAL] New Non-WG Mailing List: rpp (a provisioning protocol
> based on RESTful principles
> -Original Message-
> From: Andrew Newton (andy)
> Sent: Tuesday, August 20, 2024 8:27 AM
> To: regext@ietf.org
> Subject: [EXTERNAL] [regext] Re: I-D Action: draft-ietf-regext-rdap-
> extensions-02.txt
>
> Caution: This email originated from outside the organization. Do not click
> lin
> -Original Message-
> From: internet-dra...@ietf.org
> Sent: Wednesday, August 21, 2024 3:00 PM
> To: i-d-annou...@ietf.org
> Cc: regext@ietf.org
> Subject: [EXTERNAL] I-D Action: draft-ietf-regext-epp-eai-21.txt
>
> Caution: This email originated from outside the organization. Do not cl
> -Original Message-
> From: Andrew Newton (andy)
> Sent: Monday, August 19, 2024 7:14 PM
> To: regext@ietf.org
> Subject: [EXTERNAL] [regext] a list of RDAP clients
>
> Caution: This email originated from outside the organization. Do not click
> links
> or open attachments unless you rec
> -Original Message-
> From: Andrew Newton (andy)
> Sent: Wednesday, July 31, 2024 11:08 AM
> To: regext@ietf.org
> Subject: [EXTERNAL] [regext] normative language and references in draft-ietf-
> regext-delete-bcp
>
> Caution: This email originated from outside the organization. Do not cl
From: kowa...@denic.de
Sent: Wednesday, August 7, 2024 4:15 AM
To: Hollenbeck, Scott ; a...@hxr.us;
orie@transmute.industries
Cc: regext@ietf.org
Subject: [EXTERNAL] Re: [regext] Re: I-D Action:
draft-ietf-regext-epp-delete-bcp-07.txt
Hi Scott,
> > -07 restructured the section 6 so th
So can we make that change and consider the draft ready for AD review?
Scott
From: Andrew Newton (andy)
Sent: Tuesday, August 6, 2024 10:50 AM
To: Orie Steele ; Hollenbeck, Scott
Cc: kowa...@denic.de; regext@ietf.org
Subject: [EXTERNAL] Re: [regext] Re: I-D Action:
draft-ietf-regext-epp
> -Original Message-
> From: kowa...@denic.de
> Sent: Wednesday, July 31, 2024 4:46 PM
> To: Andrew Newton (andy) ; regext@ietf.org
> Subject: [EXTERNAL] [regext] Re: I-D Action: draft-ietf-regext-epp-delete-bcp-
> 07.txt
>
> Hi Andy,
>
> On 31.07.24 22:16, Andrew Newton (andy) wrote:
>
> -Original Message-
> From: Andrew Newton (andy)
> Sent: Wednesday, July 31, 2024 1:30 PM
> To: kowa...@denic.de; regext@ietf.org
> Subject: [EXTERNAL] [regext] Re: I-D Action: draft-ietf-regext-epp-delete-bcp-
> 07.txt
>
> Caution: This email originated from outside the organization. Do
> -Original Message-
> From: David Dong via RT
> Sent: Tuesday, July 30, 2024 6:08 PM
> Cc: Hollenbeck, Scott ; regext@ietf.org
> Subject: [EXTERNAL] [IANA #1369317] expert review for draft-ietf-regext-
> epp-ttl (epp-extensions)
>
> Caution: This email ori
> -Original Message-
> From: George Michaelson
> Sent: Wednesday, July 24, 2024 9:51 PM
> To: Jim Reid
> Cc: Registration Protocols Extensions
> Subject: [EXTERNAL] [regext] Re: RESTful EPP Charter side meeting Thursday
> 13:00
>
> Caution: This email originated from outside the organiz
Here's where you can find the regext wiki that was mentioned during Monday's
session:
https://wiki.ietf.org/group/regext
Scott
___
regext mailing list -- regext@ietf.org
To unsubscribe send an email to regext-le...@ietf.org
ink-restful-epp%2F>
-
Maarten
Op 23 jul 2024, om 07:03 heeft Hollenbeck, Scott
het volgende geschreven:
-Original Message-
From: Maarten Wullink
Sent: Monday, July 22, 2024 9:59 PM
To: Registration Protocols Extensions
Subject: [EXTERNAL] [regext] RESTful EPP draft next session how t
> -Original Message-
> From: Maarten Wullink
> Sent: Monday, July 22, 2024 9:59 PM
> To: Registration Protocols Extensions
> Subject: [EXTERNAL] [regext] RESTful EPP draft next session how to move
> forward
>
> Caution: This email originated from outside the organization. Do not click
>
I've reviewed the draft again. It's ready to go, +1.
Scott
> -Original Message-
> From: James Galvin
> Sent: Friday, July 12, 2024 5:12 PM
> To: REGEXT Working Group
> Subject: [EXTERNAL] [regext] WGLC: draft-ietf-regext-rdap-geofeed-05
>
> Caution: This email originated from outside th
A few small things:
The last call notice refers to the draft as "considered for publication as a
Best Current Practice". The draft describes itself as a Standards Track
candidate. I believe that's just an error in the last call notice.
[I-D.ietf-regext-rdap-reverse-search] is now RFC 9536.
I'd
> -Original Message-
> From: James Galvin
> Sent: Wednesday, July 10, 2024 4:36 PM
> To: Hollenbeck, Scott
> Cc: regext@ietf.org
> Subject: [EXTERNAL] Re: [regext] WGLC: draft-ietf-regext-epp-delete-bcp-03
>
> Caution: This email originated from outside the or
> -Original Message-
> From: James Galvin
> Sent: Monday, June 24, 2024 9:27 AM
> To: REGEXT Working Group
> Subject: [EXTERNAL] [regext] Re: WGLC: draft-ietf-regext-epp-delete-bcp-03
>
> Caution: This email originated from outside the organization. Do not click
> links
> or open attachm
3 PM
> To: Hollenbeck, Scott ; regext@ietf.org
> Subject: [EXTERNAL] Re: [regext] Re: WGLC: draft-ietf-regext-epp-delete-bcp-
> 03
>
> Hi Scott,
>
> Splitting Section 5 into "Current Practices" and "Proposed experimental
> Practices" would offer a lot of m
Pawel, the document already describes known practices, their issues, and those
that are proposed, along with analysis of how they're thought to be better.
What's missing?
Scott
> -Original Message-
> From: kowa...@denic.de
> Sent: Tuesday, June 18, 2024 11:36 AM
> To: regext@ietf.org
>
> -Original Message-
> From: James Galvin
> Sent: Monday, June 3, 2024 10:56 AM
> To: REGEXT Working Group
> Subject: [EXTERNAL] [regext] WGLC: draft-ietf-regext-epp-delete-bcp-03
>
> Caution: This email originated from outside the organization. Do not click
> links
> or open attachments
> -Original Message-
> From: Andrew Newton (andy)
> Sent: Tuesday, June 18, 2024 8:10 AM
> To: Mario Loffredo ;
> regext@ietf.org; Maarten Wullink
> ; George Michaelson
>
> Subject: [EXTERNAL] [regext] Re: Fwd: using experimental to move items
> forward
>
> Caution: This email originated
> -Original Message-
> From: Andrew Newton (andy)
> Sent: Friday, June 14, 2024 6:23 AM
> To: regext@ietf.org
> Subject: [EXTERNAL] [regext] using experimental to move items forward
>
> Caution: This email originated from outside the organization. Do not click
> links
> or open attachment
1 - 100 of 757 matches
Mail list logo
