Jim, Thanks for coordinating the meeting and 2 - 4 PM on Monday works for me.
-- JG James Gould Fellow Engineer [email protected] <applewebdata://13890C55-AAE8-4BF3-A6CE-B4BA42740803/[email protected]> 703-948-3271 12061 Bluemont Way Reston, VA 20190 Verisign.com <http://verisigninc.com/> On 7/17/26, 1:24 PM, "James Galvin" <[email protected] <mailto:[email protected]>> wrote: 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. First, thank you to all who have posted their positions on how to progress these documents. It is extremely helpful for the Chairs and I would expect helpful to all to have the baseline. Let me get to logistics here at the top. Andy is the most conflicted person because of his IESG responsibilities. He did have a preference for an evening meeting. Unfortunately, I have evening commitments that would force this meeting to be at 8pm. We could do that but instead I’m going to ask Andy if he would meet with us on Monday, during Session III, 2pm-4pm local time, in the IESG room. Unless I missed something, for which I sincerely apologize, that time is available to everyone. Please MARK YOUR CALENDARS. Please respond quickly if this is a problem. Hopefully, we will not need all two hours. Hopefully, we’ll get through this in 1 hour or less. Regardless of how long this takes, the consensus we achieve during this meeting will be brought to the mailing list for consideration by the working group. With respect to remote participation, it is not available from the IETF. However, I will arrange for a Zoom room to be available for any principal who can only participate remotely. Please contact me privately and I’ll make sure you’re setup. It won’t be great, I know, but we will make sure you get to participate. Now, on to the substance. The Chairs are reviewing all the contributions, and the history, and we will come prepared to start our discussion with our best understanding of the problem statement at hand. We will distribute this on Monday to those attending before our discussion so you’ll have at least a short bit of time to think about it. This will not be a free-for-all discussion. It should be the case that we will all have all the information we need about all positions, along with our own. Everyone will get a chance to speak once in response to every question or issue on the table. So, please prepare for this discussion and be thoughtful in your responses. The agenda will be as follows. 1. We will start the meeting by reviewing the problem statement and first seek consensus that we all agree what the issue is that needs to be resolved. 2. We will then move to a discussion of a solution. We will review each position and its alignment with the problem, and it how each position compares to the other positions. This will be a technical discussion moderated by the Chairs. 3. We will end with the Chairs asserting a consensus from the discussion. Everyone present will get an opportunity to react to the asserted consensus, which the Chairs will note. The meeting will be adjourned. The Chairs will prepare a summary of this meeting which will be distributed to the mailing list for consideration by the working group. Ideally the summary will have a stated consensus and a plan for bringing these three documents to closure. See you all in Vienna! Jim On 10 Jul 2026, at 18:06, James Galvin wrote: > The Chairs have received requests both on list and privately to please help > facilitate finding a consensus as to how to proceed with these three > documents. > > https://secure-web.cisco.com/1rLqxHD7U9qu0Uu_dhfDfPhDAe89EwnG8PWGhpdDJqLB0oc2NFVB3tsEQtzKkjGsuShkHs5Xjt5BjhU_397cTh9MmTbZs0giz6Zm7i0h1m9d7RcbVpzOWMQu4Brq26mH8jqPOlKhjIHiLywwcWJT1p1DXPdTeqgH8fNR544GWQVo_-PLhosqNUjpFGZ6oTXiMBZXmoOdHa3QerWHPLdorB39qxICOBIukgZvulIpkaHrAuCXH6sDJkJmRPF0BqFaEkN8c8WVlNNb7eSnv7mt_CuFM6dw2cAi3wrUY-t-iZ3I/https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fdraft-ietf-regext-rdap-extensions%2F > > <https://secure-web.cisco.com/1rLqxHD7U9qu0Uu_dhfDfPhDAe89EwnG8PWGhpdDJqLB0oc2NFVB3tsEQtzKkjGsuShkHs5Xjt5BjhU_397cTh9MmTbZs0giz6Zm7i0h1m9d7RcbVpzOWMQu4Brq26mH8jqPOlKhjIHiLywwcWJT1p1DXPdTeqgH8fNR544GWQVo_-PLhosqNUjpFGZ6oTXiMBZXmoOdHa3QerWHPLdorB39qxICOBIukgZvulIpkaHrAuCXH6sDJkJmRPF0BqFaEkN8c8WVlNNb7eSnv7mt_CuFM6dw2cAi3wrUY-t-iZ3I/https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fdraft-ietf-regext-rdap-extensions%2F> > https://secure-web.cisco.com/1n8k-zKeupKTcFELiuaX0nvbNOgNLMZ4mtHaJVcH-r0rl4sA9CuV2SMSYXqc3sExV9ZKtrC5GfwwTLvyl_IyMlQO9UoDMHQDVD2ORgnnI03mpNq84Ic4rBPMmj14Lj25Leji9rDf4eyBi_4DdIUxiFBZ28J64n3Om78J4TO_pBcxXMONbYMuQHCYxQkoUbQnfguLCEjab6JF9HNLBSvJyooVzHwK-EcvWQ9TMRneCm-DCudjP6gq4RJbE3TTHqVSDSAcni9IAdsqOXA-wtjYMgCd3wzg6DZWX2o1G5l9p15Y/https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fdraft-ietf-regext-rdap-x-media-type%2F > > <https://secure-web.cisco.com/1n8k-zKeupKTcFELiuaX0nvbNOgNLMZ4mtHaJVcH-r0rl4sA9CuV2SMSYXqc3sExV9ZKtrC5GfwwTLvyl_IyMlQO9UoDMHQDVD2ORgnnI03mpNq84Ic4rBPMmj14Lj25Leji9rDf4eyBi_4DdIUxiFBZ28J64n3Om78J4TO_pBcxXMONbYMuQHCYxQkoUbQnfguLCEjab6JF9HNLBSvJyooVzHwK-EcvWQ9TMRneCm-DCudjP6gq4RJbE3TTHqVSDSAcni9IAdsqOXA-wtjYMgCd3wzg6DZWX2o1G5l9p15Y/https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fdraft-ietf-regext-rdap-x-media-type%2F> > https://secure-web.cisco.com/10rHVxyMjc7qFP-3ZHTmJ6XdxNrRf86D3TyH86aObUYnYj7plOunuioxPAgXvkqkZvZsjEQFxRos-YrXfCvYsRpKtGbYv7PfewJyjbG-lHWpc-7ddt6ib9mSfrBgrljxPgeAw6dppkW8QI9GjzZS7UjKJ0U8SkBdzkrkPQ3BA7iH9JiLPf1wZ3LiD55RHwDqIQ36dlYR5V2fy5VkuSEoxvtRBhBjmnj8ovHqvJlJRE8LXTSBkeIt26iCs_q2mobFh32xDtxoL8YhyK4fcEUIOIHXZMMHr7XdHSYzsklFad8w/https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fdraft-ietf-regext-rdap-versioning%2F > > <https://secure-web.cisco.com/10rHVxyMjc7qFP-3ZHTmJ6XdxNrRf86D3TyH86aObUYnYj7plOunuioxPAgXvkqkZvZsjEQFxRos-YrXfCvYsRpKtGbYv7PfewJyjbG-lHWpc-7ddt6ib9mSfrBgrljxPgeAw6dppkW8QI9GjzZS7UjKJ0U8SkBdzkrkPQ3BA7iH9JiLPf1wZ3LiD55RHwDqIQ36dlYR5V2fy5VkuSEoxvtRBhBjmnj8ovHqvJlJRE8LXTSBkeIt26iCs_q2mobFh32xDtxoL8YhyK4fcEUIOIHXZMMHr7XdHSYzsklFad8w/https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fdraft-ietf-regext-rdap-versioning%2F> > > It does seem that there is an impasse, which is unfortunate. However, The > Chairs remain ever hopeful that we will find a path forward. > > What we propose is to get the principals together while we are all present in > Vienna. The Chairs will prepare an agenda and review concerns and preferences > among the principals. The objective is for the Chairs to be able to identify > the rough consensus, if not full consensus, in the room. > > The Chairs will provide a summary of the discussion to the list and assert > the identified consensus for review by the working group. we will be looking > for objections from other working group members and, of course, ask that if > you object you provide a technical explanation with new information to > support it. > > The goal is to finalize these documents, or to indicate explicit next steps > to be completed that will finalize these documents. They have been on our > milestone list for years and worse they are about two years overdue. > > The only meeting slot that we have available to do this is Wednesday morning, > 22 July, in the first time slot of the day 9am-11am local time. Our AD has > offered the IESG meeting room for this discussion and it is currently > reserved for us. Sorry folks, there is no remote participation available but > we believe this will be okay as we will be reporting to the working group for > the final decision. > > Although anyone is welcome to join, the principals the Chairs would like to > be present for this discussion are as follows. > > Jim Gould > Tom Harrison > Paweł Kowalik > Mario Loffredo > Andy Newton > Jasdip Singh > > We should appreciate if those on that list would indicate if they are > available for this discussion. As long as we have a quorum, as determined at > the discretion of the Chairs and the AD, we will have the discussion and > report to the mailing list. > > If for some reason this meeting cannot happen, then the Chairs will organize > an interim meeting in the weeks following the IETF. Of course, we’d prefer > not to do this so please do try to accommodate this meeting in your busy > schedules. > > Thanks to all! > > Jorge, Antoin, and Jim _______________________________________________ regext mailing list -- [email protected] <mailto:[email protected]> To unsubscribe send an email to [email protected] <mailto:[email protected]> _______________________________________________ regext mailing list -- [email protected] To unsubscribe send an email to [email protected]
