NetBSD-Bugs archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: kern/46602: rfc6056 sysctl names are odd
The following reply was made to PR kern/46602; it has been noted by GNATS.
From: yamt%mwd.biglobe.ne.jp@localhost (YAMAMOTO Takashi)
To: gnats-bugs%NetBSD.org@localhost
Cc: kern-bug-people%netbsd.org@localhost, gnats-admin%netbsd.org@localhost,
netbsd-bugs%netbsd.org@localhost, yamt%NetBSD.org@localhost
Subject: Re: kern/46602: rfc6056 sysctl names are odd
Date: Mon, 18 Jun 2012 05:34:48 +0000 (UTC)
> The following reply was made to PR kern/46602; it has been noted by GNATS.
>
> From: christos%zoulas.com@localhost (Christos Zoulas)
> To: gnats-bugs%NetBSD.org@localhost, kern-bug-people%netbsd.org@localhost,
> gnats-admin%netbsd.org@localhost, netbsd-bugs%netbsd.org@localhost
> Cc:
> Subject: Re: kern/46602: rfc6056 sysctl names are odd
> Date: Fri, 15 Jun 2012 10:39:55 -0400
>
> On Jun 15, 7:25am, yamt%NetBSD.org@localhost (yamt%NetBSD.org@localhost)
> wrote:
> -- Subject: kern/46602: rfc6056 sysctl names are odd
>
> | -current has the following sysctl mibs.
> |
> | net.inet.udp.rfc6056.available
> | net.inet.udp.rfc6056.selected
> | net.inet6.udp6.rfc6056.available
> | net.inet6.udp6.rfc6056.selected
> |
> | they seems odd because
> |
> | 1. they are not udp-specific and inconsist with
> | a precedent (net.inet.ip.anonportmin)
> |
> | 2. using the rfc number as a sysctl name is not appropriate.
> | eg. what happens if we add another algorithm?
> | something like "portselect" is a better name.
> |
> | UDP_RFC6056ALGO socket option has the same problems.
>
> Please suggest new names and I'll change them.
>
> christos
how about:
net.inet.ip.anonportsel.available
net.inet.ip.anonportsel.selected
net.inet6.ip6.anonportsel.available
net.inet6.ip6.anonportsel.selected
IP_PORTSEL (IPPROTO_IP-level sockopt, along IP_PORTRANGE)
YAMAMOTOTakashi
Home |
Main Index |
Thread Index |
Old Index