I really don't understand this decision tree. JCard is in the standard today while JSContact is not. Any transition that aims to be as non-disruptive as possible would need to start at serving JCard today, serving both JCard and JSContact, and then phasing out JCard.
-andy On Thu, Mar 30, 2023 at 8:37 PM Mario Loffredo <[email protected]> wrote: > > Hi Marc, > > thanks for your quick reply. > > Think it's always better to reduce the response payload when you can > through a low implementation effort. But it's just my opinion. > > So now we have 3 proposals on the table :-)) > > > Best, > > Mario > > > Il 30/03/2023 13:09, Marc Blanchet ha scritto: > > > >> Le 30 mars 2023 à 19:47, Mario Loffredo <[email protected]> a > >> écrit : > >> > >> Hi folks, > >> > >> this is a post to resume the discussion about how to execute the > >> transition from jCard to JSContact. > >> > >> Up to now, there are two approaches on the table: > >> > >> > >> 1) Returning JSContact in place of jCard (current proposal) > >> > >> Until transition is ended, a server returns one of the two formats by > >> default and returns the other on request. > >> > >> Each server can decide that it's time to stop supporting jCard based on > >> the evidence that it's no more requested. > >> > >> > >> 2) Returning JSContact in addition to jCard > >> > >> Until transition is ended, a server returns jCard by default and adds > >> JSContact to the response on request. > >> > >> Each server arbitrarily decides when it's time to stop supporting jCard. > >> > > Sorry Mario, I’ve been a bit off on this, so maybe my comment is off. But > > why not: > > > > 3) Returning JSContact in addition to jCard > > > > Until transition is ended, a server returns jCard by default and always > > adds JSContact to the response > > > > Each server arbitrarily decides when it's time to stop supporting jCard. > > > > Regards, Marc. > > > > > > > >> Please see Section 4.2.1 of the rdap-jscontact document and my today's > >> presentation for more information about pros/cons of each approach and > >> provide feedback. > >> > >> > >> Best, > >> > >> Mario > >> > >> > >> -- > >> Dott. Mario Loffredo > >> Technological Unit “Digital Innovation” > >> Institute of Informatics and Telematics (IIT) > >> National Research Council (CNR) > >> via G. Moruzzi 1, I-56124 PISA, Italy > >> Phone: +39.0503153497 > >> Web: http://www.iit.cnr.it/mario.loffredo > >> > >> _______________________________________________ > >> regext mailing list > >> [email protected] > >> https://www.ietf.org/mailman/listinfo/regext > > -- > Dott. Mario Loffredo > Technological Unit “Digital Innovation” > Institute of Informatics and Telematics (IIT) > National Research Council (CNR) > via G. Moruzzi 1, I-56124 PISA, Italy > Phone: +39.0503153497 > Web: http://www.iit.cnr.it/mario.loffredo > > _______________________________________________ > regext mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/regext _______________________________________________ regext mailing list [email protected] https://www.ietf.org/mailman/listinfo/regext
