On Thu, 11 Apr 2019 at 20:02, Richard Gibson
wrote:
>
> The first problem is for the owner of the ANAME-containing zone, for whom the
> upstream misconfiguration will result in downtime and be extended by caching
> to the MINIMUM value from their SOA, which in many cases will be one to three
>
Responses inline.
On 4/11/19 18:50, Matthew Pounsett wrote:
On Wed, 10 Apr 2019 at 16:43, Richard Gibson
wrote:
The first problem is for the owner of the ANAME-containing zone, for whom the
upstream misconfiguration will result in downtime and be extended by caching to
the MINIMUM value from
On Wed, 10 Apr 2019 at 16:43, Richard Gibson
wrote:
>
>
> The first problem is for the owner of the ANAME-containing zone, for whom the
> upstream misconfiguration will result in downtime and be extended by caching
> to the MINIMUM value from their SOA, which in many cases will be one to three
On Thu, Apr 11, 2019 at 12:20:21PM -0400, Warren Kumari wrote:
> [ - IESG (for clutter), Bob & Tim (through DNSOP / Chairs respectively) ]
>
>
> On Tue, Apr 9, 2019 at 7:55 AM Paul Wouters wrote:
>
> > On Fri, 5 Apr 2019, Bob Harold wrote:
> >
> > [ SNIP ]
> >
> > > In a similar vein, if
[ - IESG (for clutter), Bob & Tim (through DNSOP / Chairs respectively) ]
On Tue, Apr 9, 2019 at 7:55 AM Paul Wouters wrote:
> On Fri, 5 Apr 2019, Bob Harold wrote:
>
> [ SNIP ]
>
> > In a similar vein, if we stay at PS, a lot of the references seem
> like
> > they would need to mov
The following errata report has been held for document update
for RFC8552, "Scoped Interpretation of DNS Resource Records through
"Underscored" Naming of Attribute Leaves".
--
You may review the report below and at:
http://www.rfc-editor.org/errata/eid5665
-
On Wed, Apr 10, 2019 at 4:42 PM Richard Gibson
wrote:
> Responses below.
> On 4/9/19 16:04, Bob Harold wrote:
>
> If it gets an authoritative answer saying that there are no address
> records, then it should respect that answer. If that is incorrect, then
> whatever gave that answer is broken or
