[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Ipv6 for the content provider

Subject: Ipv6 for the content provider
From: tony at lava.net (Antonio Querubin)
Date: Wed, 26 Jan 2011 12:59:36 -1000 (HST)
In-reply-to: <[email protected]>
References: <[email protected]> <[email protected]> <[email protected]>

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 at lava.net

Follow-Ups:
- Ipv6 for the content provider
  - From: owen at delong.com (Owen DeLong)

References:
- Ipv6 for the content provider
  - From: charles at knownelement.com (Charles N Wyble)
- Ipv6 for the content provider
  - From: ftigeot at wolfpond.org (Francois Tigeot)
- Ipv6 for the content provider
  - From: owen at delong.com (Owen DeLong)

Prev by Date: Ipv6 for the content provider
Next by Date: Ipv6 for the content provider
Previous by thread: Ipv6 for the content provider
Next by thread: Ipv6 for the content provider
Index(es):
- Date
- Thread