[rpp] An implementation of JSContact in JSON Schema

[Stephane Bortzmeyer <[e-mail]>]

Hello from Shenzhen,

Playing with RPP during the hackathon, I searched resources about
JSContact (RFC 9553) since I think it would be hard to explain that
RPP use a different model for contacts/entities than RDAP (see
draft-ietf-regext-rdap-jscontact and draft-ietf-rpp-requirements-03,
section 18.4.3).

Also, I think that a provisioning protocol needs to validate the
requests, otherwise, there is a risk that the registry does not really
register what the client wanted. There are many schema languages for
JSON but I focused on JSON Schema.

Someone was nice enough to produce a JSON Schema for JSContact (RFC
9553 does not contain a formal description)
<https://github.com/federicotdn/jscontact-json-schema>. It is not
perfect (JSContact Ids are too lax) but it's still very useful.

I tested it with a small demo RPP implementation
<https://github.com/bortzmeyer/RPP-Afnic>, using this JSON Schema
validator <https://github.com/python-jsonschema/jsonschema> and it seems to work.

See
<https://github.com/bortzmeyer/RPP-Afnic/blob/main/contact-creation.json>
for an example of what the RPP client would have to send to create a
contact. Obviously, a real registry would have a profile of JSContact
(publically documented, I hope), making more fields mandatory.