I believe it is "Out Of Renderer".
Historically, the renderer was in charge of CORS handling/management (either partially or fully). Since this could be insecure, as a renderer process can be compromised within itself (much more than the browser, thanks to the sandbox feature), CORS handling/management is being re-implemented in the browser process (or in the network service perhaps). This will allow two things, I think -
1. sendBeacon/fetch-with-keepAlive with CORS support.
2. CORS support for content script fetches.