Re: [regext] CALL FOR ADOPTION: draft-loffredo-regext-rdap-jcard-deprecation-03

> -Original Message- > From: regext On Behalf Of James Galvin > Sent: Monday, January 18, 2021 9:29 AM > To: REGEXT WG > Subject: [EXTERNAL] [regext] CALL FOR ADOPTION: draft-loffredo-regext- > rdap-jcard-deprecation-03 > > Caution: This email originated from outside the organization. Do

Re: [regext] CALL FOR ADOPTION: draft-loffredo-regext-rdap-jcard-deprecation-03

Interesting point, Scott. Adopting JSContact (and deprecating jCard eventually) seems a tradeoff between ease-of-implementation for future servers/clients and diminishing returns for the current servers/clients. Should the latter (diminishing returns) prevent the former (easy-of-implementation)?

Re: [regext] CALL FOR ADOPTION: draft-loffredo-regext-rdap-jcard-deprecation-03

Hi, the document has a twofold goal: - introducing an  alternative to jcard as an extension - defining a deprecation process through which the extension can replace jcard progressively The document doesn't state that replacing jcard with jscontact is an absolute must but it provides the mea

Re: [regext] WG LAST CALL: draft-ietf-regext-epp-registry-maintenance-09

Quoc, I provide feedback to your points below. -- JG [cid:image001.png@01D6F65B.5515B0B0] James Gould Fellow Engineer jgo...@verisign.com 703-948-3271 12061 Bluemont Way Reston, VA 20190 Verisign.com From: regext on behalf of "Quoc@registry.godaddy" Date: Wednesd