Re: [regext] id_token parameter usage in rdap-openid

2022-01-24 Thread Tom Harrison
On Mon, Jan 24, 2022 at 02:43:40PM +, Hollenbeck, Scott wrote: > [SAH] The best thing we can do is to explain the situation in > Section 3.1.3.1. What's there now needs to change: > > OLD: > 3.1.3.1. Provider Discovery > > An RDAP server/RP needs to receive an identifier from an End-User >

Re: [regext] Anyone interested in being a document shepherd fortheData Dictionary?

2022-01-24 Thread Sarah Wyld
That’s great to hear, thanks Heather. -- Sarah Wyld, CIPP/E Policy & Privacy Manager Pronouns: she/they sw...@tucows.com +1.416 535 0123 Ext. 1392 From: Heather Flanagan Sent: January 24, 2022 1:17 PM To: Registration Protocols Extensions; Sarah Wyld Subject: RE: [regext] Anyone interest

Re: [regext] Anyone interested in being a document shepherd for theData Dictionary?

2022-01-24 Thread Heather Flanagan
‌ On Jan 24, 2022, 10:14 AM -0800, Sarah Wyld , wrote: I’m fairly new to the process so likely not a good candidate for helping shepherd this doc, but I do want to make sure that my question re the scope of Section 3 eventually gets addressed. Thanks Heather! Definitely. I’ve created

Re: [regext] Anyone interested in being a document shepherd for theData Dictionary?

2022-01-24 Thread Sarah Wyld
I’m fairly new to the process so likely not a good candidate for helping shepherd this doc, but I do want to make sure that my question re the scope of Section 3 eventually gets addressed. Thanks Heather! -- Sarah Wyld, CIPP/E Policy & Privacy Manager Pronouns: she/they sw...@tucows.com +

[regext] Anyone interested in being a document shepherd for the Data Dictionary?

2022-01-24 Thread Heather Flanagan
Hello all, As Jim and Antoin have noted, we need to get a doc shepherd assigned to the data dictionary draft. Do we have any volunteers? (Reminder re: doc shepherd responsibilities:  https://trac.ietf.org/trac/wgchairs/wiki/ExtendedDocumentShepherding) It’s an important role, and very much appr

Re: [regext] id_token parameter usage in rdap-openid

2022-01-24 Thread Hollenbeck, Scott
> -Original Message- > From: Tom Harrison > Sent: Sunday, January 23, 2022 5:11 PM > To: Hollenbeck, Scott > Cc: mario.loffr...@iit.cnr.it; regext@ietf.org > Subject: [EXTERNAL] Re: Re: Re: Re: [regext] id_token parameter usage in > rdap-openid > > Caution: This email originated from outs

Re: [regext] Call for agenda items IETF 113

2022-01-24 Thread Antoin Verschuren
Reminder… Jim and Antoin > Op 17 jan. 2022, om 15:22 heeft Antoin Verschuren > het volgende geschreven: > > Hi All, > > Ii’s time to think about agenda items for IETF 113 to see how much time we > need for our meeting. > The deadline for requesting a meeting slot will be end of next week. >

Re: [regext] Redacted implemented server side?

2022-01-24 Thread Gould, James
Mario and Marc, It's great to see plans to implement both a production client and server. Receiving implementation feedback would be very valuable. Once you have something in place, please let us know and we can add an Implementation Status section to the draft to include both the client and

Re: [regext] id_token parameter usage in rdap-openid

2022-01-24 Thread Mario Loffredo
Il 23/01/2022 23:11, Tom Harrison ha scritto: On Fri, Jan 21, 2022 at 03:10:02PM +, Scott Hollenbeck wrote: On Fri, Jan 21, 2022 at 08:26:20AM +1000, Tom Harrison wrote: But it's not guaranteed that every user identifier will be associated with a host that is implementing issuer discovery.