FYI – it’s not too late to register!
Scott
From: regi...@googlegroups.com On Behalf Of nicoleta
munteanu
Sent: Friday, June 10, 2022 8:03 AM
Subject: [EXTERNAL] [regiops] ROW11 agenda & registration
Caution: This email originated from outside the organization. Do not click
links or open
Thanks for doing all this work, Jasdip. Now we have to decide what to do with
all of this information.
As a first step, I think we need to submit errata to address issues with the
existing RFC(s). RFC 9083 uses both "lunarNIC" and "lunarNIC_level_0". At a
minimum, Andy and I agree that "lunarN
an't be addressed with
errata. If that's what the WG wants to do, fine, but we'd better make our mind
up about that sooner rather than later.
Scott
> -Original Message-
> From: Gould, James
> Sent: Wednesday, June 15, 2022 1:59 PM
> To: Hollenbeck, Scott ; j
> -Original Message-
> From: regext On Behalf Of Mario Loffredo
> Sent: Thursday, June 16, 2022 2:57 AM
> To: regext@ietf.org
> Subject: [EXTERNAL] Re: [regext] OK, What Next? (was RDAP Extensions
> Approach Analysis v2)
>
> Caution: This email originated from outside the organization. Do
ust be treated and, then, correct RFC 9083 to make it consistent with what
> decided.
>
> Once agreed on which approach to follow, we could proceed in parallel with
> the correction of RFC 9083 and the writing of a document defining the
> guidelines for extending RDAP.
>
> For the sake
I can only disagree. That wasn't the original intent, and the inconsistency is
clearly causing confusion.
Scott
> -Original Message-
> From: Gould, James
> Sent: Monday, June 27, 2022 9:57 AM
> To: Hollenbeck, Scott ; mario.loffr...@iit.cnr.it;
> regext@ietf.org
> -Original Message-
> From: Gould, James
> Sent: Monday, June 27, 2022 10:32 AM
> To: Hollenbeck, Scott ; mario.loffr...@iit.cnr.it;
> regext@ietf.org
> Subject: [EXTERNAL] Re: RE: Re: [regext] OK, What Next? (was RDAP
> Extensions Approach Analysis v2)
>
> Cau
forth discussions.
Scott
> -Original Message-
> From: Mario Loffredo
> Sent: Monday, June 27, 2022 11:18 AM
> To: Hollenbeck, Scott ;
> jgould=40verisign@dmarc.ietf.org; regext@ietf.org
> Subject: [EXTERNAL] Re: [regext] OK, What Next? (was RDAP Extensions
> Ap
> -Original Message-
> From: Gould, James
> Sent: Monday, June 27, 2022 12:37 PM
> To: Hollenbeck, Scott ; mario.loffr...@iit.cnr.it;
> regext@ietf.org
> Subject: [EXTERNAL] Re: RE: [regext] OK, What Next? (was RDAP Extensions
> Approach Analysis v2)
>
> Cau
Thanks, Rick. I'll take a more detailed look as I have time.
Scott
From: Rick Wilhelm
Sent: Thursday, June 23, 2022 4:07 PM
To: regext@ietf.org; Hollenbeck, Scott
Subject: [EXTERNAL] Re: [EXTERNAL] [regext] I-D Action:
draft-ietf-regext-rdap-openid-15.txt
Caution: This email origi
Notes below, Rick. Thanks for the feedback.
From: Rick Wilhelm
Sent: Thursday, June 23, 2022 4:07 PM
To: regext@ietf.org; Hollenbeck, Scott
Subject: [EXTERNAL] Re: [EXTERNAL] [regext] I-D Action:
draft-ietf-regext-rdap-openid-15.txt
Caution: This email originated from outside the
Thanks, Rick. Trimming things up a bit and changing the subject
appropriately...
>>> In the last sentence: Is the client required to wait until the access
>>> token has
>>> expired before submitting the new login request? Or can it send logout
>>> and
>>> login back-to-back? (Or even just a l
> -Original Message-
> From: regext On Behalf Of Mario Loffredo
> Sent: Friday, July 8, 2022 2:52 AM
> To: Hollenbeck, Scott ;
> rwilh...@pir.org; regext@ietf.org
> Subject: [EXTERNAL] Re: [regext] Login/Logout Processing (was RE: I-D
> Action: draft-ietf-rege
Thanks, Jim. I'm working on -16 to address this topic and other recent
feedback. I'm planning to include text that describes error return conditions.
Scott
> -Original Message-
> From: Gould, James
> Sent: Tuesday, July 12, 2022 9:13 AM
> To: Hollenbeck, Sc
Notes below, Rick.
From: Rick Wilhelm
Sent: Tuesday, July 12, 2022 4:05 PM
To: Hollenbeck, Scott ;
jgould=40verisign@dmarc.ietf.org; regext@ietf.org
Subject: [EXTERNAL] Re: [regext] Login/Logout Processing (was RE: I-D
Action: draft-ietf-regext-rdap-openid-15.txt)
Caution: This
> -Original Message-
> From: Mario Loffredo
> Sent: Monday, July 18, 2022 4:40 AM
> To: Gould, James ; a...@hxr.us
> Cc: Hollenbeck, Scott ; regext@ietf.org
> Subject: [EXTERNAL] Re: [regext] OK, What Next? (was RDAP Extensions
> Approach Analysis v2)
>
> Cau
> -Original Message-
> From: Mario Loffredo
> Sent: Monday, July 18, 2022 10:51 AM
> To: Hollenbeck, Scott ; Gould, James
> ; 'a...@hxr.us'
> Cc: 'regext@ietf.org'
> Subject: [EXTERNAL] Re: [regext] OK, What Next? (was RDAP Extensions
> A
> -Original Message-
> From: Gould, James
> Sent: Monday, July 18, 2022 10:58 AM
> To: Hollenbeck, Scott ; mario.loffr...@iit.cnr.it;
> a...@hxr.us
> Cc: regext@ietf.org
> Subject: [EXTERNAL] Re: RE: Re: [regext] OK, What Next? (was RDAP
> Extensions Approach
> -Original Message-
> From: Gould, James
> Sent: Monday, July 18, 2022 1:06 PM
> To: Hollenbeck, Scott ; mario.loffr...@iit.cnr.it;
> a...@hxr.us
> Cc: regext@ietf.org
> Subject: [EXTERNAL] Re: RE: RE: Re: [regext] OK, What Next? (was RDAP
> Extensi
> -Original Message-
> From: Gould, James
> Sent: Monday, July 18, 2022 2:11 PM
> To: Hollenbeck, Scott ; mario.loffr...@iit.cnr.it;
> a...@hxr.us
> Cc: regext@ietf.org
> Subject: [EXTERNAL] Re: RE: RE: RE: Re: [regext] OK, What Next? (was RDAP
> Extensions App
OAuth 2.0 includes the ability to authorize a class of clients known as
"confidential clients" in a machine-to-machine manner using the "Client
Credentials Grant". The grant is described here:
https://datatracker.ietf.org/doc/html/rfc6749#section-4.4
A description of confidential and public cli
I support this proposal.
Scott
> On Aug 1, 2022, at 9:49 AM, James Galvin 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.
>
> As everyone knows there has been q
> -Original Message-
> From: Andrew Newton
> Sent: Monday, August 1, 2022 4:31 PM
> To: Mario Loffredo
> Cc: Hollenbeck, Scott ; regext@ietf.org
> Subject: [EXTERNAL] Re: [regext] Federated Authentication for Machine-to-
> Machine Interactions in RDAP
>
> Cau
I've submitted the errata reports.
Scott
> -Original Message-
> From: regext On Behalf Of James Galvin
> Sent: Tuesday, August 16, 2022 10:31 AM
> To: REGEXT WG
> Subject: [EXTERNAL] Re: [regext] CONSENSUS CALL: discussion regarding
> rdapConformance
>
> Caution: This email originated f
> -Original Message-
> From: regext On Behalf Of internet-dra...@ietf.org
> Sent: Thursday, August 18, 2022 9:19 AM
> To: i-d-annou...@ietf.org
> Cc: regext@ietf.org
> Subject: [EXTERNAL] [regext] I-D Action: draft-ietf-regext-rdap-openid-17.txt
>
> Caution: This email originated from outs
> -Original Message-
> From: last-call On Behalf Of John C Klensin
> Sent: Monday, August 22, 2022 10:27 PM
> To: Gould, James ; beld...@gmail.com;
> p...@paftech.se; jgould=40verisign@dmarc.ietf.org
> Cc: a...@ietf.org; draft-ietf-regext-epp-eai@ietf.org; last-c...@ietf.org;
> reg
I originally made this request in a note to the list on 18 August:
https://mailarchive.ietf.org/arch/msg/regext/DhG25zCOF4RoR5TukZIg_CLzjrU/
The request might have been lost or missed given the different subject on that
message, so I'll make the request explicit with this note. I believe this
d
> -Original Message-
> From: regext On Behalf Of James Galvin
> Sent: Monday, August 29, 2022 9:45 AM
> To: REGEXT WG
> Subject: [EXTERNAL] [regext] status of draft-ietf-regext-rdap-reverse-search
>
> Caution: This email originated from outside the organization. Do not click
> links
> or
> -Original Message-
> From: regext On Behalf Of Antoin Verschuren
> Sent: Monday, September 12, 2022 9:55 AM
> To: regext
> Subject: [EXTERNAL] [regext] Second WG LAST CALL: draft-ietf-regext-rdap-
> reverse-search
>
> Caution: This email originated from outside the organization. Do not
> -Original Message-
> From: regext On Behalf Of James Galvin
> Sent: Monday, September 26, 2022 10:04 AM
> To: REGEXT WG
> Subject: [EXTERNAL] [regext] WGLC: draft-ietf-regext-rdap-openid-17
>
> Caution: This email originated from outside the organization. Do not click
> links
> or open
> -Original Message-
> From: regext On Behalf Of James Galvin
> Sent: Monday, October 3, 2022 8:40 AM
> To: REGEXT WG
> Subject: [EXTERNAL] Re: [regext] WGLC: draft-ietf-regext-rdap-openid-17
>
> Caution: This email originated from outside the organization. Do not click
> links
> or open
Thanks for the feedback, Andy. More below...
> -Original Message-
> From: Andrew Newton
> Sent: Tuesday, October 4, 2022 10:37 AM
> To: REGEXT WG ; Hollenbeck, Scott
>
> Cc: James Galvin
> Subject: [EXTERNAL] Re: [regext] WGLC: draft-ietf-regext-rdap-openid-17
&g
the WG shall get the consensus around whether these web
> application related use-cases shall be supported in order to move forward
> with
> the WGLC.
>
>
> Kind regards,
>
> Pawel
>
>
> Am 04.10.22 um 15:42 schrieb Hollenbeck, Scott:
> >> -Original Me
From: regext On Behalf Of Pawel Kowalik
Sent: Thursday, October 6, 2022 7:24 PM
To: Andrew Newton
Cc: regext@ietf.org
Subject: [EXTERNAL] Re: [regext] WGLC: draft-ietf-regext-rdap-openid-17
Caution: This email originated from outside the organization. Do not click
links or open attachments u
From: regext On Behalf Of Pawel Kowalik
Sent: Thursday, October 6, 2022 7:24 PM
To: Andrew Newton
Cc: regext@ietf.org
Subject: [EXTERNAL] Re: [regext] WGLC: draft-ietf-regext-rdap-openid-17
Caution: This email originated from outside the organization. Do not click
links or open attachments un
Thanks for the feedback, Jasdip! More below...
> -Original Message-
> From: regext On Behalf Of Jasdip Singh
> Sent: Sunday, October 9, 2022 5:16 PM
> To: James Galvin ; regext@ietf.org
> Subject: [EXTERNAL] Re: [regext] WGLC: draft-ietf-regext-rdap-openid-17
>
> Caution: This email origi
Thanks for the feedback, Tom! More below...
> -Original Message-
> From: regext On Behalf Of Tom Harrison
> Sent: Monday, October 10, 2022 10:13 AM
> To: James Galvin
> Cc: REGEXT WG
> Subject: [EXTERNAL] Re: [regext] WGLC: draft-ietf-regext-rdap-openid-17
>
> Caution: This email origin
> -Original Message-
> From: Tom Harrison
> Sent: Monday, October 10, 2022 7:16 PM
> To: Hollenbeck, Scott
> Cc: gal...@elistx.com; regext@ietf.org
> Subject: [EXTERNAL] Re: Re: [regext] WGLC: draft-ietf-regext-rdap-openid-17
>
> Caution: This email ori
> -Original Message-
> From: regext On Behalf Of Pawel Kowalik
> Sent: Tuesday, October 11, 2022 11:42 AM
> To: regext@ietf.org
> Subject: [EXTERNAL] Re: [regext] WGLC: draft-ietf-regext-rdap-openid-17 -
> Clients
>
> Caution: This email originated from outside the organization. Do not cli
> -Original Message-
> From: Pawel Kowalik
> Sent: Wednesday, October 12, 2022 12:36 PM
> To: Hollenbeck, Scott ; regext@ietf.org
> Subject: [EXTERNAL] Re: [regext] WGLC: draft-ietf-regext-rdap-openid-17 -
> Clients
>
> Caution: This email originated from outside
> -Original Message-
> From: Pawel Kowalik
> Sent: Wednesday, October 12, 2022 3:35 PM
> To: Hollenbeck, Scott ; regext@ietf.org
> Subject: [EXTERNAL] Re: [regext] WGLC: draft-ietf-regext-rdap-openid-17 -
> Clients
>
> Caution: This email originated from outside
> -Original Message-
> From: I-D-Announce On Behalf Of internet-
> dra...@ietf.org
> Sent: Monday, October 17, 2022 9:02 AM
> To: i-d-annou...@ietf.org
> Cc: regext@ietf.org
> Subject: [EXTERNAL] I-D Action: draft-ietf-regext-rdap-openid-18.txt
>
> Caution: This email originated from outsi
the organization. Do not click
> links
> or open attachments unless you recognize the sender and know the content is
> safe.
>
> Am 17.10.22 um 15:32 schrieb Hollenbeck, Scott:
>
> >> [SAH] This update addresses most of the feedback received during the
> recent WG last
From: Mario Loffredo
Sent: Wednesday, October 19, 2022 5:13 AM
To: Pawel Kowalik ; regext@ietf.org; Hollenbeck, Scott
Subject: [EXTERNAL] Re: [regext] I-D Action:
draft-ietf-regext-rdap-openid-18.txt
Caution: This email originated from outside the organization. Do not click
links or open
the organization. Do not click
> links
> or open attachments unless you recognize the sender and know the content is
> safe.
>
> Am 19.10.22 um 14:13 schrieb Hollenbeck, Scott:
> > [SAH] If the PII data you're referring to is what's included in the
> > userCla
> -Original Message-
> From: Pawel Kowalik
> Sent: Friday, October 21, 2022 5:18 AM
> To: Hollenbeck, Scott ; regext@ietf.org
> Subject: [EXTERNAL] Re: [regext] I-D Action: draft-ietf-regext-rdap-openid-
> 18.txt
>
> Caution: This email originated from outside
> -Original Message-
> From: Pawel Kowalik
> Sent: Monday, October 24, 2022 10:58 AM
> To: Hollenbeck, Scott ; regext@ietf.org
> Subject: [EXTERNAL] Re: [regext] I-D Action: draft-ietf-regext-rdap-openid-
> 18.txt
>
> Caution: This email originated from outside
> -Original Message-
> From: mario.loffr...@iit.cnr.it
> Sent: Tuesday, October 25, 2022 3:15 AM
> To: Hollenbeck, Scott
> Cc: kowa...@denic.de; regext@ietf.org
> Subject: [EXTERNAL] Re: [regext] I-D Action: draft-ietf-regext-rdap-openid-
> 18.txt
>
[SAH] [sn
> -Original Message-
> From: Pawel Kowalik
> Sent: Monday, October 24, 2022 10:58 AM
> To: Hollenbeck, Scott ; regext@ietf.org
> Subject: [EXTERNAL] Re: [regext] I-D Action: draft-ietf-regext-rdap-openid-
> 18.txt
>
> Caution: This email originated from outside
We need to decide what to do with draft-ietf-regext-rdap-openid and web
service clients. Our choices:
1. Finish the draft as-is, noting that it's limited to clients that can
implement OpenID Connect flows and can process session cookies. This implies
that we need another draft to describe OAuth
> -Original Message-
> From: regext On Behalf Of Pawel Kowalik
> Sent: Monday, November 14, 2022 12:18 PM
> To: regext@ietf.org
> Subject: [EXTERNAL] Re: [regext] draft-ietf-regext-rdap-openid Post IETF-115
>
> Caution: This email originated from outside the organization. Do not click
> l
> -Original Message-
> From: Marc Blanchet
> Sent: Tuesday, November 15, 2022 10:57 AM
> To: Pawel Kowalik
> Cc: Hollenbeck, Scott ; regext@ietf.org
> Subject: [EXTERNAL] Re: [regext] draft-ietf-regext-rdap-openid Post IETF-115
>
> Caution: This email ori
> -Original Message-
> From: Mario Loffredo
> Sent: Wednesday, November 16, 2022 2:31 AM
> To: Hollenbeck, Scott ;
> marc.blanc...@viagenie.ca; kowa...@denic.de
> Cc: regext@ietf.org
> Subject: [EXTERNAL] Re: [regext] draft-ietf-regext-rdap-openid Post IETF-115
Is this a correct sequence of steps for a web service client flow?
The RDAP Web Service Client sends an RDAP "help" query to an RDAP server to
determine the type and capabilities of the OpenID Providers (Ops) that are
used by the RDAP server.
The RDAP Web Service Client determines the End-User's
ck
> links
> or open attachments unless you recognize the sender and know the content is
> safe.
>
> Hi Scott,
>
> Am 17.11.22 um 15:47 schrieb Hollenbeck, Scott:
> > Is this a correct sequence of steps for a web service client flow?
> >
> > The RDAP Web Servic
> -Original Message-
> From: Mario Loffredo
> Sent: Friday, November 18, 2022 6:59 AM
> To: Pawel Kowalik ; Hollenbeck, Scott
> ; regext@ietf.org
> Subject: [EXTERNAL] Re: [regext] Web Service Client Flow
>
> Caution: This email originated from outside the or
> -Original Message-
> From: Pawel Kowalik
> Sent: Monday, November 21, 2022 6:22 AM
> To: Hollenbeck, Scott ; mario.loffr...@iit.cnr.it;
> regext@ietf.org
> Subject: [EXTERNAL] Re: [regext] Web Service Client Flow
>
> Caution: This email originated from outside
> -Original Message-
> From: regext On Behalf Of Stephane Bortzmeyer
> Sent: Wednesday, November 23, 2022 10:03 AM
> To: regext@ietf.org
> Cc: bortzme...@nic.fr
> Subject: [EXTERNAL] [regext] About conformance to RFC 8521
>
> Caution: This email originated from outside the organization. Do
Does this make sense for use as introductory text to appear in new Section
3.1.2 of what will be -19? Please make suggestions for improvement as you see
fit.
3.1.1 Terminology
3.1.2 Client Considerations
Clients that can accept and process HTTP cookies [RFC6265] as part of
session-oriented in
> -Original Message-
> From: Pawel Kowalik
> Sent: Wednesday, November 30, 2022 11:15 AM
> To: Hollenbeck, Scott ; mario.loffr...@iit.cnr.it;
> regext@ietf.org
> Subject: [EXTERNAL] Re: [regext] Web Service Client Flow
>
> Caution: This email originated from outs
> -Original Message-
> From: regext On Behalf Of Michael Bauland
> Sent: Friday, December 2, 2022 6:41 AM
> To: regext@ietf.org
> Subject: [EXTERNAL] [regext] CDS/CDNSKEY vs. EPP update prohibited
>
> Caution: This email originated from outside the organization. Do not click
> links
> or
> -Original Message-
> From: regext On Behalf Of Michael Bauland
> Sent: Friday, December 2, 2022 8:55 AM
> To: regext@ietf.org
> Subject: [EXTERNAL] Re: [regext] CDS/CDNSKEY vs. EPP update prohibited
>
> Caution: This email originated from outside the organization. Do not click
> links
>
> -Original Message-
> From: regext On Behalf Of internet-dra...@ietf.org
> Sent: Friday, December 2, 2022 9:26 AM
> To: i-d-annou...@ietf.org
> Cc: regext@ietf.org
> Subject: [EXTERNAL] [regext] I-D Action: draft-ietf-regext-rdap-openid-19.txt
>
> Caution: This email originated from outsi
> -Original Message-
> From: Pawel Kowalik
> Sent: Friday, December 2, 2022 9:45 AM
> To: Hollenbeck, Scott ; mario.loffr...@iit.cnr.it;
> regext@ietf.org
> Subject: [EXTERNAL] Re: [regext] Web Service Client Flow
>
> Caution: This email originated from outside
Thanks for the feedback. More below...
> -Original Message-
> From: Pawel Kowalik
> Sent: Tuesday, December 6, 2022 4:12 AM
> To: Hollenbeck, Scott ; regext@ietf.org
> Subject: [EXTERNAL] Re: [regext] I-D Action: draft-ietf-regext-rdap-openid-
> 19.txt
>
> Cautio
> -Original Message-
> From: Pawel Kowalik
> Sent: Tuesday, December 6, 2022 4:12 AM
> To: Hollenbeck, Scott ; regext@ietf.org
> Subject: [EXTERNAL] Re: [regext] I-D Action: draft-ietf-regext-rdap-openid-
> 19.txt
[SAH] I'm working on -20. I need a few more clar
> -Original Message-
> From: regext On Behalf Of Mario Loffredo
> Sent: Wednesday, January 4, 2023 11:33 AM
> To: Gould, James ; regext@ietf.org
> Subject: [EXTERNAL] [regext] RDAP queries based on redacted properties
>
> Caution: This email originated from outside the organization. Do not
> -Original Message-
> From: regext On Behalf Of Gould, James
> Sent: Monday, January 9, 2023 12:08 PM
> To: a...@hxr.us
> Cc: mario.loffr...@iit.cnr.it; regext@ietf.org
> Subject: [EXTERNAL] Re: [regext] RDAP queries based on redacted properties
>
> Caution: This email originated from out
> -Original Message-
> From: regext On Behalf Of internet-dra...@ietf.org
> Sent: Tuesday, January 10, 2023 10:03 AM
> To: i-d-annou...@ietf.org
> Cc: regext@ietf.org
> Subject: [EXTERNAL] [regext] I-D Action: draft-ietf-regext-rdap-openid-20.txt
>
> Caution: This email originated from out
Thanks for the feedback and questions, Julien. More below.
> -Original Message-
> From: Julien Bernard
> Sent: Monday, January 16, 2023 2:33 PM
> To: Hollenbeck, Scott ; regext@ietf.org
> Subject: [EXTERNAL] Re: [regext] I-D Action: draft-ietf-regext-rdap-openid-
>
> -Original Message-
> From: Julien Bernard
> Sent: Wednesday, January 18, 2023 11:05 AM
> To: Hollenbeck, Scott ; regext@ietf.org
> Subject: [EXTERNAL] Re: [regext] I-D Action: draft-ietf-regext-rdap-openid-
> 20.txt
>
> Caution: This email originated from outs
> -Original Message-
> From: Mario Loffredo
> Sent: Tuesday, January 24, 2023 9:57 AM
> To: Hollenbeck, Scott ; jbern...@cofomo.com;
> regext@ietf.org
> Subject: [EXTERNAL] Re: [regext] I-D Action: draft-ietf-regext-rdap-openid-
> 20.txt
>
> Caution: This email
> -Original Message-
> From: I-D-Announce On Behalf Of internet-
> dra...@ietf.org
> Sent: Wednesday, February 1, 2023 12:31 PM
> To: i-d-annou...@ietf.org
> Cc: regext@ietf.org
> Subject: [EXTERNAL] I-D Action: draft-ietf-regext-rdap-openid-21.txt
>
> Caution: This email originated from o
> -Original Message-
> From: Pawel Kowalik
> Sent: Thursday, February 2, 2023 1:59 AM
> To: Hollenbeck, Scott ; regext@ietf.org
> Subject: [EXTERNAL] Re: [regext] I-D Action: draft-ietf-regext-rdap-openid-
> 21.txt
>
> Caution: This email originated from outside
> -Original Message-
> From: Pawel Kowalik
> Sent: Thursday, February 2, 2023 4:58 PM
> To: Hollenbeck, Scott ; regext@ietf.org
> Subject: [EXTERNAL] Re: [regext] I-D Action: draft-ietf-regext-rdap-openid-
> 21.txt
>
> Caution: This email originated from outside
> -Original Message-
> From: I-D-Announce On Behalf Of internet-
> dra...@ietf.org
> Sent: Monday, February 6, 2023 8:46 AM
> To: i-d-annou...@ietf.org
> Cc: regext@ietf.org
> Subject: [EXTERNAL] I-D Action: draft-ietf-regext-rdap-openid-22.txt
>
> Caution: This email originated from outsi
; -Original Message-
> From: RFC Errata System
> Sent: Tuesday, February 7, 2023 12:35 PM
> To: rfc-edi...@rfc-editor.org
> Cc: r...@instant.ca; Hollenbeck, Scott ;
> a...@hxr.us; regext@ietf.org
> Subject: [EXTERNAL] [Editorial Errata Reported] RFC9083 (7340)
>
> The
I'm aware of two other RFCs that also define terms like this: 4949 (security)
and 8499 (DNS). The intended status for this draft is "Standards Track". At
best, this should be Informational in the same way that 4949 is informational.
Neither of these RFCs creates a registry. As such, I don't see
point for
text to be added to the draft.
Scott
From: Steve Crocker
Sent: Tuesday, February 14, 2023 11:11 AM
To: Gould, James ; Hollenbeck, Scott
Cc: regext@ietf.org; Steve Crocker
Subject: [EXTERNAL] Re: [regext] WGLC: draft-ietf-regext-datadictionary-03
Caution: This email originated
the chance of
those definitions conflicting with standards track specifications approaches
zero.
Scott
From: Tim Wicinski
Sent: Friday, February 17, 2023 10:10 AM
To: Gould, James
Cc: Hollenbeck, Scott ; st...@shinkuro.com;
regext@ietf.org
Subject: [EXTERNAL] Re: [regext] WGLC: draft-ietf
I see the value in supporting multiple email addresses from a protocol
perspective. If, however, the purpose of this draft is narrowly scoped such
that the goal is to support either a single SMTPUTF8 or ASCII address, I can
support option #1. That probably means that we need to think about futur
I see the value in supporting multiple email addresses from a protocol
perspective. If, however, the purpose of this draft is narrowly scoped such
that the goal is to support either a single SMTPUTF8 or ASCII address, I can
support option #1. That probably means that we need to think about futur
> -Original Message-
> From: regext On Behalf Of James Galvin
> Sent: Monday, March 20, 2023 9:41 AM
> To: REGEXT WG
> Subject: [EXTERNAL] [regext] WGLC: draft-ietf-regext-rdap-reverse-search-20
>
> Caution: This email originated from outside the organization. Do not click
> links
> or o
FYI, folks!
Scott
From: row-commit...@googlegroups.com On Behalf
Of nicoleta munteanu
Sent: Wednesday, March 29, 2023 10:38 AM
Subject: [EXTERNAL] ROW12 - Call for proposals
Caution: This email originated from outside the organization. Do not click
links or open attachments unless you r
> -Original Message-
> From: regext On Behalf Of Mario Loffredo
> Sent: Friday, March 31, 2023 7:45 AM
> To: regext@ietf.org
> Subject: [EXTERNAL] [regext] Redacting JSContact uid in RDAP - Updated
>
> Caution: This email originated from outside the organization. Do not click
> links
> or
From: regext On Behalf Of Jasdip Singh
Sent: Tuesday, April 4, 2023 11:38 AM
To: Mario Loffredo ; Andrew Newton
Cc: regext@ietf.org
Subject: [EXTERNAL] Re: [regext] WGLC:
draft-ietf-regext-rdap-reverse-search-20
Caution: This email originated from outside the organization. Do not click
link
From: regext On Behalf Of Jasdip Singh
Sent: Tuesday, April 4, 2023 11:38 AM
To: Mario Loffredo ; Andrew Newton
Cc: regext@ietf.org
Subject: [EXTERNAL] Re: [regext] WGLC: draft-ietf-regext-rdap-reverse-search-20
Caution: This email originated from outside the organization. Do not click
links
> -Original Message-
> From: Mario Loffredo
> Sent: Wednesday, April 5, 2023 4:24 AM
> To: Andrew Newton ; Hollenbeck, Scott
>
> Cc: jasd...@arin.net; regext@ietf.org
> Subject: [EXTERNAL] Re: [regext] WGLC: draft-ietf-regext-rdap-reverse-search-
> 20
>
>
> -Original Message-
> From: Jasdip Singh
> Sent: Wednesday, April 5, 2023 10:40 AM
> To: Hollenbeck, Scott ; mario.loffr...@iit.cnr.it;
> a...@hxr.us
> Cc: regext@ietf.org
> Subject: [EXTERNAL] Re: [regext] WGLC: draft-ietf-regext-rdap-reverse-search-
> 20
> -Original Message-
> From: Mario Loffredo
> Sent: Wednesday, April 5, 2023 10:04 AM
> To: Hollenbeck, Scott ; a...@hxr.us
> Cc: jasd...@arin.net; regext@ietf.org
> Subject: [EXTERNAL] Re: [regext] WGLC:
> draft-ietf-regext-rdap-reverse-search-
> 20
>
>
> -Original Message-
> From: regext On Behalf Of Antoin Verschuren
> Sent: Monday, April 17, 2023 9:27 AM
> To: regext
> Subject: [EXTERNAL] [regext] WGLC: draft-ietf-regext-rdap-redacted-11
>
> Caution: This email originated from outside the organization. Do not click
> links
> or open
FYI, folks.
Scott
From: row-commit...@googlegroups.com On Behalf
Of nicoleta munteanu
Sent: Wednesday, April 26, 2023 8:41 AM
Subject: [EXTERNAL] ROW12 -> Call for Proposals & Registration
Caution: This email originated from outside the organization. Do not click
links or open attachmen
> -Original Message-
> From: regext On Behalf Of Antoin Verschuren
> Sent: Tuesday, April 25, 2023 4:54 PM
> To: regext
> Subject: [EXTERNAL] [regext] CALL FOR ADOPTION: draft-regext-brown-epp-ttl
>
> Caution: This email originated from outside the organization. Do not click
> links
> or
This report doesn't contain any useful information. It can be ignored.
Scott
> -Original Message-
> From: regext On Behalf Of RFC Errata System
> Sent: Friday, April 28, 2023 9:05 AM
> To: marc.blanc...@viagenie.ca; superu...@gmail.com;
> francesca.palomb...@ericsson.com; o...@nlnetlabs.
This report contains no useful information. It can be ignored.
Scott
> -Original Message-
> From: RFC Errata System
> Sent: Friday, April 28, 2023 5:40 AM
> To: Hollenbeck, Scott ; superu...@gmail.com;
> francesca.palomb...@ericsson.com; i...@antoin.nl; gal...@
This report contains no useful information. It can be ignored.
Scott
> -Original Message-
> From: RFC Errata System
> Sent: Friday, April 28, 2023 8:38 AM
> To: Hollenbeck, Scott ; nk...@cnnic.cn;
> superu...@gmail.com; francesca.palomb...@ericsson.com; o...@nlnetla
This report contains no useful information. It can be ignored.
Scott
> -Original Message-
> From: RFC Errata System
> Sent: Friday, April 28, 2023 8:59 AM
> To: Hollenbeck, Scott ; nk...@cnnic.cn;
> superu...@gmail.com; francesca.palomb...@ericsson.com; o...@nlnetla
This report contains no useful information. It can be ignored.
Scott
> -Original Message-
> From: RFC Errata System
> Sent: Friday, April 28, 2023 9:03 AM
> To: a...@arin.net; Hollenbeck, Scott ;
> superu...@gmail.com; francesca.palomb...@ericsson.com; o...@nlnetla
This report contains no useful information. It can be ignored.
Scott
> -Original Message-
> From: RFC Errata System
> Sent: Friday, April 28, 2023 8:40 AM
> To: a...@arin.net; Hollenbeck, Scott ;
> superu...@gmail.com; francesca.palomb...@ericsson.com; o...@nlnetla
FYI, folks – final call for proposals.
Scott
From: row-commit...@googlegroups.com On Behalf
Of nicoleta munteanu
Sent: Tuesday, May 9, 2023 5:04 AM
Subject: [EXTERNAL] ROW12 - Final call for proposals
Caution: This email originated from outside the organization. Do not click
links or op
1 - 100 of 757 matches
Mail list logo
