Re: Introducing draft-denog-v6ops-addresspartnaming
Richard Hartmann <richih.mailinglist@gmail.com> writes:
I will add quad to -03 anyway. If you get a few +1 on hexquad, I am against adding that, as well.
Quad is a standard term for "64 bit integer" in C/C++. For example: $ grep -c quad /usr/src/sys/netinet6/*|awk -F: '{tot+=$2} END{print tot}' 171 which is to say, the kame derived ipv6 stack on this machine uses one of the *quad_t types 171 times. Ambiguating usages like "Take the least signifigant quad of that ipv6 address" to mean either 16 bits or 64 bits, when it currently is unamibigously 64 bits won't make the lives of C/C++ programmers writing IPv6 code any easier.
On Mon, Nov 22, 2010 at 18:33, Daniel Hagerty <hag@linnaean.org> wrote:
Ambiguating usages like "Take the least signifigant quad of that ipv6 address" to mean either 16 bits or 64 bits, when it currently is unamibigously 64 bits won't make the lives of C/C++ programmers writing IPv6 code any easier.
Agreed. Thanks a lot for pointing this out. Comments like this are incredibly valuable to me. I think I will still add quad to -03 as it has been requested a lot of times, but more to point out and document that there is a significant problem with it than anything else. Thanks again, Richard
participants (2)
-
Daniel Hagerty
-
Richard Hartmann