On Fri, Jul 26, 2019 at 4:06 AM Gavin Brown <[email protected]> wrote: > > On 25 Jul 2019, at 22:43, Andrew Newton <[email protected]> wrote: > > In other words, who is NOT doing RDAP because of jCard? Are there any > > registries willing to step up and say they'll deploy RDAP if we move > > to JSContact? > > I'm not too concerned about jCard as a barrier to server deployment. I'm more > concerned about how it impedes *client* deployment (and consequently, > migration of legacy whois clients to RDAP).
I agree, clients have the most pain wrt jCard. That said, having implemented two clients I found it annoying but not super painful. However, you are a client implementer as well, so maybe your experience was different. I do think that clients will have the biggest burden during a transition as they will need to support a new representation in addition to the jCard wackiness. I'd be happier if we had commitment from server operators to move to the new format as soon as possible to avoid the need for multiple code paths in the clients. Do we have that commitment? > > If there were multiple, lossless jCard <=> vCard converters, implemented in > different (popular) programming languages, then I would be less concerned. > But there aren't (and I doubt there ever will be). Yes, I doubt there will ever be libraries to help out here. -andy _______________________________________________ regext mailing list [email protected] https://www.ietf.org/mailman/listinfo/regext
