Happy to do that. I keep a couple of notes here handy, just for that purpose. Let me -- well, first of all, it's easy to get confused. I completely understand that. There's a lot of -- we talk about this every quarter and there are a lot of terms that we use, acronyms like IRP and CEP that even experienced lawyers wouldn't be familiar with if they didn't operate in the ICANN world. So maybe I can simplify with a little bit of background what's happened. Maybe even define some of these terms. So first, when we talk about an IRP, independent review panel, that's a lawsuit, not in court but more like an arbitration demand that someone can bring against ICANN. However, the only claims allowed are those based on a violation by ICANN of its bylaws. A CEP, you've heard us use that, or cooperative engagement process, is a discussion between a potential IRP filer and ICANN ahead of an IRP. And all actions associated with the issue behind the IRP are automatically put on hold during the CEP and that's kind of what we've been in for the last few weeks. You've also heard another acronym, NDC, that's -- that stands for Nu Dot Co and that's a company that VeriSign entered into an agreement with about .web. So let me try to simplify just how we got here. I don't want to speculate about what's going to happen going forward, not just because it's pending litigation but much of it is ICANN process that's not ours. But let me just give you a really brief history now that some of the terms are easier to understand with .web. So in 2016, there was an auction for .web. NDC won that auction with our backing. In 2018, a company called Afilias, the plaintiff, filed an IRP seeking to have the IRP panel disqualify NDC and to award .web to them because Afilias objected to the auction and to our, VeriSign's, participation with NDC. A few years later in 2021 after a lengthy legally maneuverings, the IRP panel said, no. The panel said, ICANN owns the issue and the panel tells ICANN to go review and decide the issue. But Afilias doesn't like that answer and files a follow-up motion asking the panel essentially for a do-over. And the panel once again tells Afilias, no. But this time, they call Afilias' request frivolous and they sanction Afilias, ordering Afilias to pay ICANN's attorney fees. During 2022 and early '23, ICANN then follow the panel's recommendation. They undertook a thorough 16-month review process. In early May of this year, ICANN announced that it had completed its review and had concluded, by a Board vote that was without objection, that Afilias' accusations were wrong and that the Board -- and then the Board directed ICANN's staff to proceed with processing NDC's .web application. Afilias then filed the CEP which then automatically paused the processing of .web. So now Afilias has filed another IRP, that's true. But this time, there's something new and substantial. There's the definitive and affirmative ruling from the ICANN Board of Directors, again, without objection, a vote that .web should be awarded to NDC, a vote resulting from a 16-month process that included work by ICANN's staff who reviewed new submissions by VeriSign and Afilias, working with their law firms, who were allowed to use and even supplement the entire legal record from the earlier 2-year IRP, a vote that resulted in a finding that .web should be awarded to NDC. So that's new and that's not trivial. We believe that Afilias has been and is still litigating for delay. Now in terms of next steps, we'll have to see whether ICANN continues with the hold on .web, the .web delegation or not during the IRP. ICANN could continue processing the .web PLD during the IRP, although that decision could be challenged. We don't believe there should be any further delay but this is ICANN's process and we will continue to work within that system. So what happens next? I don't want to comment on, as I said, it's pending litigation but I hope that bit of background and history was helpful.