Re: [regext] New Version Notification for draft-ietf-regext-rdap-jscontact-04.txt

2021-12-13 Thread Jasdip Singh
Hi. +1 for this doc being on standards track. Jasdip From: regext on behalf of Antoin Verschuren Date: Monday, December 13, 2021 at 10:10 AM To: "regext@ietf.org" Subject: Re: [regext] New Version Notification for draft-ietf-regext-rdap-jscontact-04.txt Hi All, I’m glad t

Re: [regext] New Version Notification for draft-ietf-regext-rdap-jscontact-04.txt

2021-12-13 Thread Antoin Verschuren
s and we have evidence that >> >> the new will be significantly better than the old (and it seems to me we >> have it in this case). >> >> But, at the same time, we are not sure that the majority of EPP or RDAP >> operators will implement it. That's it

Re: [regext] New Version Notification for draft-ietf-regext-rdap-jscontact-04.txt

2021-12-08 Thread Gould, James
following two points left for WG discussion: >>> 1) In the sentence "To aid interoperability, RDAP providers are RECOMMENDED to use as map keys the following string values and labels defined in [RFC5733].", should "are RECOMMNEDED to" be replaced with

Re: [regext] New Version Notification for draft-ietf-regext-rdap-jscontact-04.txt

2021-12-08 Thread Gavin Brown
Best, > > Mario > >> >>> “Be liberal in what you accept” applies. >> >> yes. >> >> Marc. >> >>> >>> Scott >>> >>> From: regext On Behalf Of Mario Loffredo >>> Sent: Tuesday, December 7,

Re: [regext] New Version Notification for draft-ietf-regext-rdap-jscontact-04.txt

2021-12-08 Thread Mario Loffredo
t:*Tuesday, December 7, 2021 3:45 AM *To:*Antoin Verschuren ;regext@ietf.org *Subject:*[EXTERNAL] Re: [regext] New Version Notification for draft-ietf-regext-rdap-jscontact-04.txt *Caution:*This email originated from outside the organization. Do not click links or open attachments unless you

Re: [regext] New Version Notification for draft-ietf-regext-rdap-jscontact-04.txt

2021-12-07 Thread Marc Blanchet
21 3:45 AM > To: Antoin Verschuren <mailto:ietf=40antoin...@dmarc.ietf.org>>; regext@ietf.org > <mailto:regext@ietf.org> > Subject: [EXTERNAL] Re: [regext] New Version Notification for > draft-ietf-regext-rdap-jscontact-04.txt > > Caution: This email originated fro

Re: [regext] New Version Notification for draft-ietf-regext-rdap-jscontact-04.txt

2021-12-07 Thread Hollenbeck, Scott
rd to JSContact transition signaling add significant implementation overhead for RDAP servers and clients? Could an out-of-band (OOB) method have been employed? Three more implementations were included. Best, Mario Messaggio Inoltrato ---- Oggetto: New Version Notification fo

Re: [regext] New Version Notification for draft-ietf-regext-rdap-jscontact-04.txt

2021-12-07 Thread Mario Loffredo
of the spec for jCard to JSContact transition signaling add significant implementation overhead for RDAP servers and clients? Could an out-of-band (OOB) method have been employed? Three more implementations were included. Best, Mario Messaggio Inoltrato Oggetto: New Version Notif

Re: [regext] New Version Notification for draft-ietf-regext-rdap-jscontact-04.txt

2021-12-06 Thread Marc Blanchet
ion of the spec for jCard to JSContact transition signaling >> add significant implementation overhead for RDAP servers and clients? Could >> an out-of-band (OOB) method have been employed? >> >> >> Three more implementations were included. >> >> Best,

Re: [regext] New Version Notification for draft-ietf-regext-rdap-jscontact-04.txt

2021-12-06 Thread Antoin Verschuren
servers and clients? Could > an out-of-band (OOB) method have been employed? > > > Three more implementations were included. > > Best, > Mario > > > ---- Messaggio Inoltrato > Oggetto: New Version Notification for > draft-ietf-regext-rdap-jscon