This ACTION REQUEST is now closed. The Chairs see two take-aways from this working group discussion.
1. We still have support for “jscontact” and we have support for the Experimental track. However, we don’t believe we are ready to publish yet. 2. While the concepts of signaling vs extension have some broad understanding, we don’t have consensus on what they mean with respect to RDAP. The “jscontact” document stood alone for some time but we now have several potential documents that interact and there is more work to be done to understand and come to consensus about the status of the various documents. The Chairs will start a separate thread so that we can get all documents in front of us and we will be proposing an interim meeting to have a detailed discussion about the statuses. Thank you, Antoin and Jim On 13 Nov 2023, at 10:53, James Galvin wrote: > Following up from last week’s REGEXT meeting, there was consensus in the room > that the document: > > https://datatracker.ietf.org/doc/draft-ietf-regext-rdap-jscontact-16/ > > Should be split into two documents: the signaling function and the extension. > > The signaling function draft would be put on the standards track and the > extension draft would be put on the experimental track. > > With this message the Chairs are asking the broader working group to confirm > this action. If you have questions or concerns please reply to this message > by Monday, 20 November 2023. If you need more time please ask on the list > and the Chairs will consider an extension. > > Although we had consensus in the meeting room, the Chairs would appreciate a > “+1” reply if you agree with this action. > > Thanks, > > Antoin and Jim _______________________________________________ regext mailing list regext@ietf.org https://www.ietf.org/mailman/listinfo/regext
