Hi Ray
On Fri, Oct 24, 2014 at 10:09:39AM +, Ray Bellis wrote:
There are several outstanding questions therein - some relating to TCP
state where I don’t know the technical answer, and a couple where
opinions from the WG would be welcomed. The latter mostly relate to
whether it’s useful
Hi all,
This draft has risen from the deep...
It describes a technique that a number of DNS operators use to
surgically / tactically deal with DNSSEC validation failures, for
large-scale outages.
We believe that this is needed -- simply telling customers This
doesn't work though us, but does
On Oct 24, 2014, at 9:01 AM, Warren Kumari war...@kumari.net wrote:
This draft has risen from the deep...
Like
http://www.sfweekly.com/foodie/2008/03/31/dread-cherry-chip-cthulhu-rises-from-the-deep?
We believe that this is needed -- simply telling customers This
doesn't work though us, but
On 10/24/14 12:06 PM, David Conrad wrote:
On Oct 24, 2014, at 9:01 AM, Warren Kumari war...@kumari.net wrote:
This draft has risen from the deep...
Like
http://www.sfweekly.com/foodie/2008/03/31/dread-cherry-chip-cthulhu-rises-from-the-deep?
We believe that this is needed -- simply
P Vixie wrote:
Ohta-san, like you I would like to see stateless address auto
configuration for ipv6 (SLAAC) die in a fire. Sadly this outcome is
beyond our powers.
Not necessarily.
Let's start from where we are, no matter how unpleasant that place
may be. Vixie
From where we are, fix
On 10/24/14 9:01 AM, Warren Kumari wrote:
Hi all,
This draft has risen from the deep...
It describes a technique that a number of DNS operators use to
surgically / tactically deal with DNSSEC validation failures, for
large-scale outages.
We believe that this is needed -- simply telling
Moin!
On 25 Oct 2014, at 01:06, Doug Barton do...@dougbarton.us wrote:
Currently the operators of example.com have introduced an error into their
DNS information which is causing the domain to be unresolvable. Once they
have corrected that error our customers will be able to reach their
