Mario,
I have an option 3, which is to leverage the help response to signal what is supported and what the policy is of the server instead of overloading the purpose of the rdapConformance and notices for the transition signaling. Look at section 6.2 "versioning-help" Member of draft-gould-regext-rdap-versioning as an example of the signaling what is supported and the policies of the extension via the help response. The RDAP Conformance is RFC 9083 is defined as: The data structure named "rdapConformance" is an array of strings, each providing a hint as to the specifications used in the construction of the response. This data structure MUST appear in the topmost JSON object of a response and MUST NOT appear anywhere else. A response to a "help" request will include identifiers for all of the specifications supported by the server. For what to include by default at the beginning at the end of a server transition, I like option 1, where only one form should be returned at a time with the policy of a default and the timeframes in the help response. Thanks, -- JG James Gould Fellow Engineer jgo...@verisign.com <applewebdata://13890C55-AAE8-4BF3-A6CE-B4BA42740803/jgo...@verisign.com> 703-948-3271 12061 Bluemont Way Reston, VA 20190 Verisign.com <http://verisigninc.com/> On 3/30/23, 6:51 AM, "regext on behalf of Mario Loffredo" <regext-boun...@ietf.org <mailto:regext-boun...@ietf.org> on behalf of mario.loffr...@iit.cnr.it <mailto:mario.loffr...@iit.cnr.it>> wrote: 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. 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://secure-web.cisco.com/1DrJ2aNA7Ez2f1fkDFn72lEUpX1gQI94lKt93YKPgyrH2jbmQ0Kxl8PSxIc7BHXOlsEXx2mZDFb_N7e0GzWJoXCb6JqONwyGM8olz3j_9mdZeJBv7S278z0IS67wwAQ4rzTWS3InIwCilIi-DmoqU5s56AKK50RML1lQCcazdNmpukZ2CGTrfzIJ945sB718BglZp1mZ_n59143QWYeUrDOy2KSbu3ovpfQMAo0cOapVCOh1Q_cMM_JeISa-h__9IoYFE5YwHTaUZZqhsQS4ZzapFuHG-cAdo3QSfjkxR1f8/http%3A%2F%2Fwww.iit.cnr.it%2Fmario.loffredo <http://secure-web.cisco.com/1DrJ2aNA7Ez2f1fkDFn72lEUpX1gQI94lKt93YKPgyrH2jbmQ0Kxl8PSxIc7BHXOlsEXx2mZDFb_N7e0GzWJoXCb6JqONwyGM8olz3j_9mdZeJBv7S278z0IS67wwAQ4rzTWS3InIwCilIi-DmoqU5s56AKK50RML1lQCcazdNmpukZ2CGTrfzIJ945sB718BglZp1mZ_n59143QWYeUrDOy2KSbu3ovpfQMAo0cOapVCOh1Q_cMM_JeISa-h__9IoYFE5YwHTaUZZqhsQS4ZzapFuHG-cAdo3QSfjkxR1f8/http%3A%2F%2Fwww.iit.cnr.it%2Fmario.loffredo> _______________________________________________ regext mailing list regext@ietf.org <mailto:regext@ietf.org> https://secure-web.cisco.com/1FrPEjGkCSGNA_L46uflYGYSO03BdKvU8oLfbHjt6VoPw5OQ050FfmLTpTie4DHA0TDax8Bx14hVVVAL-DVZ3Fbs9H34pBu_e5Mz2pMxWXe3u8kDkr5eEIov2R7a6FJyqY5Sn_qCAqACXe4uwZMoUiHvId6d8fzH9AqPRHx7QtrjzxuVx8RE9npN5ReItil4Y-7zSFTcF7Wo_X-UglHeqwoqG5icl_saAS7KP0HoHGdtnW52hj7l_WLU000lYlk67EushefrubT4PawPt3SdpsAzDsRt5dqC7w5P9iRwzGO4/https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Fregext <https://secure-web.cisco.com/1FrPEjGkCSGNA_L46uflYGYSO03BdKvU8oLfbHjt6VoPw5OQ050FfmLTpTie4DHA0TDax8Bx14hVVVAL-DVZ3Fbs9H34pBu_e5Mz2pMxWXe3u8kDkr5eEIov2R7a6FJyqY5Sn_qCAqACXe4uwZMoUiHvId6d8fzH9AqPRHx7QtrjzxuVx8RE9npN5ReItil4Y-7zSFTcF7Wo_X-UglHeqwoqG5icl_saAS7KP0HoHGdtnW52hj7l_WLU000lYlk67EushefrubT4PawPt3SdpsAzDsRt5dqC7w5P9iRwzGO4/https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Fregext>
_______________________________________________ regext mailing list regext@ietf.org https://www.ietf.org/mailman/listinfo/regext
