Interesting… Probably be. As a native English speaker, frankly, your version simply doesn’t parse. The grammar doesn’t really work.
“Providing addressing space” is an invalid construct. You could correct this with “Providing address space” to fix the grammar, but it doesn’t
really fix the remaining awkwardness of the rest of the sentence. I chose the words “Providing IP number resources” to match the common
technical phrase used in a lot of RIR policy to cover IPv4, IPv6, and possibly ASNs.
If you want to limit it to just IP addresses, including both v4 and v6 (and possible future protocols), we could use “Providing IP address(es)”
The construct non-permanently is awkward and does not read well. Perhaps it works in other languages, but in English a native speaker
would either use some conjugation of “impermanent” or more often, “temporary” (e.g. temporarily). Since I know you previously had some
negative emotional reaction to the idea of replacing non-permanent with “temporary”, I decided to try “impermanent”
I also removed a number of improper commas that really really made it hard to parse properly.
Yep… That’s an easy solution to your concern. However, FWIW, to a native speaker, in that context, the or is clearly intended to be inclusive rather than exclusive as an exclusive or would be nonsensical.
So I guess the question is do we want to write policies in english that are best suited for foreign readers while ill suited to parsing by native speakers, or, do we want
to write policies in grammatically proper english.
Don’t get me wrong, I’m the first to admit I make my share of spelling and grammar errors. The person I’d defer to for judgment on any such issue would be Lee Howard.
I’m actually OK either way, but, it seems to me that if we want the former, we have a slippery slope of problems, including, but not limited to:
+ Which language(s) native speakers are we optimizing for?
+ How do we resolve conflicts in optimizing for multiple different non-english languages in our english
+ If we have some other target language we prefer to optimize for, why aren’t we just using that language in the first place?
At the end of the day, my only dog in the fight is wanting to have clear policy that is understood by all who must live with and/or implement it.