Hi Branden, > Date: 2026-11-15 15:53:59-0600 > From: "G. Branden Robinson" > > Hi Alex, > > At 2026-11-15T22:18:06+0100, Alejandro Colomar wrote: > > > Date: 2026-11-15 21:55:50+0100 > > > From: Matthieu Buffet > > > On 11/6/26 11:02 PM, Günther Noack wrote: > > > > On Tue, Nov 03, 2026 at 12:39:32AM +0100, Matthieu Buffet wrote: > > > >> A Landlock rule with port 0 > > > >> and the > > > >> .B LANDLOCK_ACCESS_NET_BIND_TCP > > > >> -right means that requesting to bind on port 0 is allowed > > > >> -and it will automatically translate to binding on the related port > > > range. > > > >> +or > > > >> +.B LANDLOCK_ACCESS_NET_BIND_UDP > > > >> +right means that requesting to bind on port 0 > > > >> +(explicitly, or implicitly > > > >> +for instance by sending a datagram on an unbound UDP socket) > > > >> +is allowed > > > >> +and it will automatically translate to binding on a kernel-assigned > > > ephemeral port. > > > > > > > > With the caveat of not being a native speaker either, the commas in > > > > this sentence feel wrong to me. > > > > > > I was trying to make the comma match the fact that the example only applies > > > to the implicit case, but if it sounds wrong let's use your suggestion. > > > > Perhaps you could use two levels of separation, with ';': > > > > (explicitly; > > or implicitly, > > for instance, by sending a datagram ...) > > > > But this is a bit beyond my expertise. I've CCd Branden, which will > > surely be able to help. > > Well, maybe. > > I don't know of hard rules governing this sort of construction, but use > of a semicolon here "feels" wrong, as you're not joining independent > clauses nor are you separating list items, at least some of which > contain commas. > > I might use an em dash here. But, trying to interpret this language for > myself, I think the best solution might be to recast to break up this > long sentence into shorter ones. > > Thus: > > A Landlock rule with port 0 > and the > .B LANDLOCK_ACCESS_NET_BIND_TCP > or > .B LANDLOCK_ACCESS_NET_BIND_UDP > right means that a port 0 binding request is allowed, > automatically translating > to a binding on a kernel-assigned ephemeral port. > Such binding can be done explicitly or implicitly. > Sending a datagram on an unbound UDP socket is one implicit means. Thanks! That sounds good. Perhaps we could put the last sentence in parentheses, as it's not part of the specification. A Landlock rule with port 0 and the .B LANDLOCK_ACCESS_NET_BIND_TCP or .B LANDLOCK_ACCESS_NET_BIND_UDP right means that a port 0 binding request is allowed, automatically translating to a binding on a kernel-assigned ephemeral port. Such binding can be done explicitly or implicitly (sending a datagram on an unbound UDP socket is one implicit means). Have a lovely day! Alex > > I also recast the text to tighten wording, to reduce use of passive > voice, and to favor present tense over future. > > Does this help? > > Regards, > Branden --