Jim and Antoin, I support having an interim meeting to discuss. I see distinct problems being solved by the three drafts draft-gould-regext-rdap-versioning, draft-newton-regext-rdap-extensions, and draft-newton-regext-rdap-x-media-type. I highlight them below to prime the discussion:
1. draft-newton-regext-rdap-extensions – Provide clarification of the creation of RDAP extensions, where we can address much of the clarification issues that we’ve struggled with on the mailing list. 2. draft-newton-regext-rdap-x-media-type – Provide an alternative mechanism to the use of a query parameter that does not pose an issue with RDAP redirection servers. 3. draft-gould-regext-rdap-versioning – Provide support for an extensible set of RDAP extension versioning types with Opaque Versioning and Semantic Versioning initially defined that will work in unison with draft-newton-regext-rdap-extensions and draft-newton-regext-rdap-x-media-type. Thanks for catching up on the thread and setting up an interim meeting. -- JG [cid87442*image001.png@01D960C5.C631DA40] 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/> From: regext <regext-boun...@ietf.org> on behalf of James Galvin <gal...@elistx.com> Date: Monday, December 11, 2023 at 9:09 AM To: Jasdip Singh <jasd...@arin.net> Cc: "regext-cha...@ietf.org" <regext-cha...@ietf.org>, "regext@ietf.org" <regext@ietf.org>, Andy Newton <a...@hxr.us> Subject: [EXTERNAL] [regext] ACTION REQUESTED: Re: RDAP-X draft adoption Caution: This email originated from outside the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. The Chairs have caught up on this thread and have the following proposal for the working group We suggest that the working group take on the problem space of considering negotiation, signaling, and versioning in RDAP. To properly consider this problem space we should adopt as working group documents the following three drafts, all of which address at least part of this problem space: https://datatracker.ietf.org/doc/draft-gould-regext-rdap-versioning/<https://secure-web.cisco.com/1QCHC-8xG9hJOoNbDI71pTXPcfNXNxXahQ0yAk0Kh8n3TXFaZLQfStyi73ETpLrp_VAHHTyrIcEJ1weZ5qZK0_cMTDTToIZEXQTyVvz1nTTW2OeinyEGs8qLf6H8JMh4D95TGSm8YxgqIGgdjwc44vpZ1HlC681iv-gRwvPf44zqTfXU7Ea2Y0kdFm3MdTltH9A-lyRa62J8JCOpzibzxwuOlV9nyEZRbgGx-igLxtkEXJx9YuGuT4b4hIrWyi9BEyLDDhYIUsv1VHWfnOXcZ98-fW-vSrVZhf4yJVDKmywc/https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fdraft-gould-regext-rdap-versioning%2F> (-02 just posted) https://datatracker.ietf.org/doc/draft-newton-regext-rdap-extensions/<https://secure-web.cisco.com/1tXp4Qvx3ZwxG_JflI4RWAyuNSLesY6v6F5e9PHM3ctG7AuM03M1XKq6jWKNaM2yzhJjFAloK2L8Oe1aJQeTz-uEOhhJhNghoaikvt1cM1fxGnP0im7Jni_CBtXgmhabRX8d0RI66AXRxn3eKUilGE1ly_u8FQtP2KRPDAfTKn1D8d1zqDbAumaroM7OwHBkjxv8Zx55y57aKLDNy3qfUdIsWItVWPTlsFF1w3Gi7lncjGoKkbPpLE4Dfl-bV0NMH_G0teF32FxJ1_qT8GeyW1lhG_fX3KGqySJLYWyhuerQ/https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fdraft-newton-regext-rdap-extensions%2F> https://datatracker.ietf.org/doc/draft-newton-regext-rdap-x-media-type/<https://secure-web.cisco.com/1vynEGONnD6c3jpzASNi5JktCxoaatpSGQAe_7sPbWti_DS6KBeAEzmjYodzPnMkGJFZSes0qKsvlXGLTvk-UM4ES8robG3bVG0wp-U5YLKrqMw3XHYqIhzRzlozE3u9f2BfrayUT6rMVulRSqQAaCpGb082NbSazOzqabjjrN0TMq5GEyFK712UYoAAj1z3Xkr2dm9i0MKG8qfQduKAv5EBZ5mR6GZBz8gbqkp_OQ70hqPpAGjQO1L05zXkNRAksLsw4fQINAQ3vk1cINy1G1snWMle58uKD22RAzuGnyLo/https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fdraft-newton-regext-rdap-x-media-type%2F> In general, our goal as a working group is to have one solution on the standards track to a problem. After we have adopted these documents the working group will have to answer at least two questions: 1. Is there one problem to be solved or more than one? 2. Is there one solution or, if there are multiple problems, do we need multiple solutions? These are technical questions based on use cases that have been discussed. The Chairs also suggest that we have an interim meeting, perhaps in late January or early February, during which we have a focused discussion seeking answers to those two questions, studying the value and benefits of each of the proposals in the documents above. The Chairs will address the logistics of an interim meeting after we have adopted these documents. In addition, there is the question of whether or not the solution(s) to be proposed impact the following two documents: https://datatracker.ietf.org/doc/draft-ietf-regext-rdap-jscontact/<https://secure-web.cisco.com/1S9ALApi40ba4zWCpUTXYYjMunNt48SIfnUV-8edz0DsRDFt5n8btojt93HE1usEXJoGyQ6iqqOT-SWBwrX_YlnEuHWsBafhxAUpe3Aq3hAtzhnRPpeij3d8xSGmg64SMsHvXNxnixfYy83zq1lbUMhFKOvkWFYB2ZuAs6vL1x5rplznSm005msv_VHqboptdHU3PscEqbXrvGQcB-vmlz14aHPlzS9VtelNaKtE4LyHJZvZxd-eLJ_ZY-hihFCPF04L-9oBdVu_BaX9HXjncTs_ZfaWrskVeEnR01X0gmbo/https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fdraft-ietf-regext-rdap-jscontact%2F> https://datatracker.ietf.org/doc/draft-newton-regext-rdap-simple-contact/<https://secure-web.cisco.com/1a-3X4qV0mHjwRXynJmerEbK47F9vDkdT29ilFGzopWUKvznE8BJCmDCundvB0K3XiPXLNyEVpV7Z5y0V6B3bRGjBPPjslP3nqO9VEQiQ8cUBBN_82O9gkc7plmWEFnliCpmUkW7n_sgBg9DJgKuoloTXchUt2woEY4BTGzYZdJsgJLu7RB3r8I8JuXKVYAI6NkU_6ROMTm8I42OI3hG-D5yEtvATfpxVwnsXF_DtfcdtNgbbUKqSTu0IZIR4dclFNZvWW7zroiywf7uBbwrerWD_XOk-5Qh_Riw6iOSiNcM/https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fdraft-newton-regext-rdap-simple-contact%2F> The Chairs suggest that the simple-contact document should also be adopted, to move forward on the Experimental track with jsContact, and that we consider if either is impacted by the solution(s) to be proposed. Thanks, Antoin and Jim On 14 Nov 2023, at 18:26, Jasdip Singh wrote: Hello Antoin, Jim, Given the ongoing discussion on how to negotiate extensions between RDAP clients and servers (using HTTP headers versus query parameters), be it for SimpleContact [1], JSContact [2], or versioning in RDAP [3], Andy and I want to request a call for WG adoption of the RDAP-X draft [4]. We believe that the HTTP headers-based approach could help unify extensions negotiation across the RDAP ecosystem. Thanks, Jasdip & Andy [1] https://datatracker.ietf.org/doc/draft-newton-regext-rdap-simple-contact/<https://secure-web.cisco.com/1a-3X4qV0mHjwRXynJmerEbK47F9vDkdT29ilFGzopWUKvznE8BJCmDCundvB0K3XiPXLNyEVpV7Z5y0V6B3bRGjBPPjslP3nqO9VEQiQ8cUBBN_82O9gkc7plmWEFnliCpmUkW7n_sgBg9DJgKuoloTXchUt2woEY4BTGzYZdJsgJLu7RB3r8I8JuXKVYAI6NkU_6ROMTm8I42OI3hG-D5yEtvATfpxVwnsXF_DtfcdtNgbbUKqSTu0IZIR4dclFNZvWW7zroiywf7uBbwrerWD_XOk-5Qh_Riw6iOSiNcM/https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fdraft-newton-regext-rdap-simple-contact%2F> [2] https://datatracker.ietf.org/doc/draft-ietf-regext-rdap-jscontact/<https://secure-web.cisco.com/1S9ALApi40ba4zWCpUTXYYjMunNt48SIfnUV-8edz0DsRDFt5n8btojt93HE1usEXJoGyQ6iqqOT-SWBwrX_YlnEuHWsBafhxAUpe3Aq3hAtzhnRPpeij3d8xSGmg64SMsHvXNxnixfYy83zq1lbUMhFKOvkWFYB2ZuAs6vL1x5rplznSm005msv_VHqboptdHU3PscEqbXrvGQcB-vmlz14aHPlzS9VtelNaKtE4LyHJZvZxd-eLJ_ZY-hihFCPF04L-9oBdVu_BaX9HXjncTs_ZfaWrskVeEnR01X0gmbo/https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fdraft-ietf-regext-rdap-jscontact%2F> [3] https://datatracker.ietf.org/doc/draft-gould-regext-rdap-versioning/<https://secure-web.cisco.com/1QCHC-8xG9hJOoNbDI71pTXPcfNXNxXahQ0yAk0Kh8n3TXFaZLQfStyi73ETpLrp_VAHHTyrIcEJ1weZ5qZK0_cMTDTToIZEXQTyVvz1nTTW2OeinyEGs8qLf6H8JMh4D95TGSm8YxgqIGgdjwc44vpZ1HlC681iv-gRwvPf44zqTfXU7Ea2Y0kdFm3MdTltH9A-lyRa62J8JCOpzibzxwuOlV9nyEZRbgGx-igLxtkEXJx9YuGuT4b4hIrWyi9BEyLDDhYIUsv1VHWfnOXcZ98-fW-vSrVZhf4yJVDKmywc/https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fdraft-gould-regext-rdap-versioning%2F> [4] https://datatracker.ietf.org/doc/draft-newton-regext-rdap-x-media-type/<https://secure-web.cisco.com/1vynEGONnD6c3jpzASNi5JktCxoaatpSGQAe_7sPbWti_DS6KBeAEzmjYodzPnMkGJFZSes0qKsvlXGLTvk-UM4ES8robG3bVG0wp-U5YLKrqMw3XHYqIhzRzlozE3u9f2BfrayUT6rMVulRSqQAaCpGb082NbSazOzqabjjrN0TMq5GEyFK712UYoAAj1z3Xkr2dm9i0MKG8qfQduKAv5EBZ5mR6GZBz8gbqkp_OQ70hqPpAGjQO1L05zXkNRAksLsw4fQINAQ3vk1cINy1G1snWMle58uKD22RAzuGnyLo/https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fdraft-newton-regext-rdap-x-media-type%2F>
_______________________________________________ regext mailing list regext@ietf.org https://www.ietf.org/mailman/listinfo/regext
