[135604] in North American Network Operators' Group
Re: Ipv6 for the content provider
daemon@ATHENA.MIT.EDU (Antonio Querubin)
Thu Jan 27 02:54:10 2011
Date: Wed, 26 Jan 2011 21:53:17 -1000 (HST)
From: Antonio Querubin <tony@lava.net>
To: Owen DeLong <owen@delong.com>
In-Reply-To: <5B7007C4-2F56-4193-8A5F-EFDDCCB49830@delong.com>
Cc: nanog@nanog.org
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
On Wed, 26 Jan 2011, Owen DeLong wrote:
> It's actually pretty well known and it is documented in several places in plain
> sight.
Where?
A search for IPV6_V6ONLY in the FreeBSD Handbook yields nothing. You'd
think the brokenness would at least be mentioned in the handbook.
A similar search of the FreeBSD FAQ yields a bunch of hits but none that
really mention the RFC brokenness.
The only place where I've seen this behaviour mentioned in the past is in
bug reports. And the responses to those were that the non-compliant
behaviour was preferred but would/should be more clearly documented.
Years later, the documentation is still lacking.
Antonio Querubin
e-mail/xmpp: tony@lava.net
