nanog mailing list archives
Re: Ipv6 for the content provider
From: Antonio Querubin <tony () lava net>
Date: Wed, 26 Jan 2011 12:59:36 -1000 (HST)
On Wed, 26 Jan 2011, Owen DeLong wrote:
It would be nice if BSD would correct their IPV6_V6ONLY behavior instead of putting up an alleged security red herring. I'm not sure why Micr0$0ft suffers from this braindeath.
Or at the very least document this in plain site in the IPv6 section of the docs. Their non-RFC-compliant behaviour is a hidden land mine.
Antonio Querubin e-mail/xmpp: tony () lava net
Current thread:
- RE: Ipv6 for the content provider, (continued)
- RE: Ipv6 for the content provider George Bonser (Jan 26)
- Re: Ipv6 for the content provider Dale W. Carder (Jan 26)
- Re: Ipv6 for the content provider Antonio Querubin (Jan 26)
- Re: Ipv6 for the content provider Antonio Querubin (Jan 26)
- Re: Ipv6 for the content provider Owen DeLong (Jan 26)
- Re: Ipv6 for the content provider Antonio Querubin (Jan 26)
- Re: Ipv6 for the content provider Valdis . Kletnieks (Jan 26)
- Re: Ipv6 for the content provider Owen DeLong (Jan 26)
- Re: Ipv6 for the content provider Owen DeLong (Jan 26)
- Re: Ipv6 for the content provider Antonio Querubin (Jan 26)
- Re: Ipv6 for the content provider Owen DeLong (Jan 26)
- Re: Ipv6 for the content provider Antonio Querubin (Jan 26)
- Re: Ipv6 for the content provider Jared Mauch (Jan 27)
- Re: Ipv6 for the content provider Dale W. Carder (Jan 26)
- Re: Ipv6 for the content provider Charles N Wyble (Jan 26)
- Re: Ipv6 for the content provider Randy McAnally (Jan 26)
- Re: Ipv6 for the content provider Lamar Owen (Jan 26)
- Re: Ipv6 for the content provider Valdis . Kletnieks (Jan 26)
- Re: Ipv6 for the content provider Blake Hudson (Jan 31)