This change didn't seem appropriate. Now we need a new gRFC to make it stable? I thought it was going to be unstable until it was shown to be tested, and that is enough to make it stable, like we have done for some other cases like Least Request.

This is sort of a problem, because we are about to make a release that tells people about this, but if it is permanently experimental, we shouldn't advertise it is available. We were going to tell people, "please test this and tell us if it works for you, so we can stabilize it." But that is useless now with this change.

(This had been planned to be discussed today, but that discussion ended up not happening, so now we're in this situation until next year when people are back from holidays.)

Result from a discussion on Friday: The "stable" way to access this policy will be xDS (which has reduced stability guarantees compared to the normal "forever"). It will need further discussion to make stable from regular json service config.