Hi Jasdip,
again my comments inline.
Il 20/08/2025 16:33, Jasdip Singh ha scritto:
Hi Mario,
*From: *Mario Loffredo <[email protected]>
*Date: *Wednesday, August 20, 2025 at 3:30 AM
*To: *Jasdip Singh <[email protected]>,
[email protected] <[email protected]>,
Mario Loffredo <[email protected]>,
[email protected] <[email protected]>
*Subject: *[regext] Re: Fwd: I-D Action:
draft-ietf-regext-rdap-jscontact-22.txt
<snip>
On 18.08.25 14:45, Mario Loffredo wrote:
[ML] I think a reasonable compromise is to allow both formats,
but we could require that they NOT be used simultaneously.
This could avoid confusion for clients. The same could apply
to the full name and name components.
[JS] Glad to see that we won’t be excluding unstructured addresses
in RDAP JSContact. Though, not sure about "they NOT be used
simultaneously”. Even if structured components are available,
unstructured data is typically intended for human-friendly
presentation of an address or a name per some economy or culture.
IMO, the guidance should be to encourage supplying structured
components but not discourage additionally providing unstructured
data, be it for an address or a name.
[ML2] Clients don't need to get the unstructured format if they can
get the structured one and present the address as they want, instead
of how servers chose. It could happen, perhaps it is unlikely but we
cannot completely rule it out, that there could be inconsistencies
between the two formats if both were presented.
[JS2] That’s an interesting point -- whether a client should honor the
unstructured address’ presentation when provided from the server side
or not. RFC 9083 discusses structured versus unstructured addresses
[2] but not sufficiently to help with our discussion point.
[2]
https://www.rfc-editor.org/rfc/rfc9083.html#name-structured-vs-unstructured-
[ML3] My interpretation of that section is that it warns clients that a
postal address could appear in either format in an RDAP response and,
therefore, they should be prepared to handle both of them.
But I'm pretty sure that clients typically consider the unstructured
version only when the structured one isn't available. For an
implementer, it's much easier to start with structured data and
aggregate/manage it as desired rather than the other way around.
<snip>
Jasdip
Best,
Mario
--
Dott. Mario Loffredo
Senior Technologist
Technological Unit “Digital Innovation”
Institute of Informatics and Telematics (IIT)
National Research Council (CNR)
Address: Via G. Moruzzi 1, I-56124 PISA, Italy
Phone: +39.0503153497
Web:http://www.iit.cnr.it/mario.loffredo
_______________________________________________
regext mailing list -- [email protected]
To unsubscribe send an email to [email protected]
