Hello WG, During the presentation of draft-lozano-regext-rdap-transf-contact-inf in the IETF96, it was mentioned that there could be other options to represent transformations (i.e. translations and transliterations) in RDAP, for example, within the jCard itself. These are the possibilities that were analyzed while writing the draft:
It’s worth mentioning that the policy recommendation requires to show the source of the transformation (e.g. registry, registrar, etc), and the type of transformation (e.g. translation or transliteration). Option 1: * Use the ALTID vCard parameter to represent the transformations. * Register new parameters in the vCard elements registry (http://www.iana.org/assignments/vcard-elements/vcard-elements.xhtml) to show the source of the transformation, and the type of transformation. I think that these parameters are too specific to the DNS industry, therefore it may not be a good idea to register them in the vCard elements registry. Option 2: * Use the ALTID vCard parameter to represent the transformations. * Include new elements in the JSON response to show the source of the transformation, and the type of transformation. A PID parameter could be used to reference the transformation within the vCard. I think this option is complex. The advantage is that there is no need to add new parameters to the vCard elements registry. Option 3: Using additional jCard objects to represent the transformations. This option is explained in draft-lozano-regext-rdap-transf-contact-inf-00. Option 4: Use the NOTE vCard property to specify the extra transformation information. I don't like this idea, because we can end with overloading the NOTE property (similar to the overloading of the TXT RRTYPE). What option do you think should be preferred? Any other options worth considering? Additional feedback? Example of option 1: "entities": [ { "objectClassName": "entity", "handle": "XXXX", "vcardArray": [ "vcard", [ [ "version", {}, "text", "4.0" ], [ "fn", { "language": "ru", "altid": "1", "infSource": "registrant", "transMechanism": "authoritative" }, "text", "Иван Петрович Сидоров" ], [ "fn", { "language": "ru-Latn", "altid": "1", "infSource": "registrar", "transMechanism": "transliteration", "transliterationStd": "iso9" }, "text", "Ivan Petrovič Sidorov" ] ] ] } ] Examples of option 2: "entities": [ { "objectClassName": "entity", "handle": "XXXX", "vcardArray": [ "vcard", [ [ "version", {}, "text", "4.0" ], [ "fn", { "language": "ru", "altid": "1", "pid": "1" }, "text", "Иван Петрович Сидоров" ], [ "fn", { "language": "ru-Latn", "altid": "1", "pid": "2" }, "text", "Ivan Petrovič Sidorov" ] ] ], "transformations": [ { "objectClassName": "transformation", "pidRef": "1", "infSource": "registrant", "transMechanism": "authoritative" }, { "objectClassName": "transformation", "pidRef": "2", "infSource": "registrar", "transMechanism": "transliteration", "transliterationStd": "iso9" } ] } ] Regards, Gustavo
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ regext mailing list regext@ietf.org https://www.ietf.org/mailman/listinfo/regext
