I like the Extended Error Code using EDNS idea. This was effectively
what was done with TSIG and TKEY that have an expanded Error field
inside the RR. However:
>> I don't see any reason for the complex two-dimensional table to
new error codes. Given that 16 bits is available for "INFO-CODE"
(whic
On Thu, Nov 22, 2018 at 12:01:00PM +, Sara Dickinson wrote:
>
> > Begin forwarded message:
> >
> > From: Benjamin Kaduk mailto:ka...@mit.edu>>
> > Subject: Benjamin Kaduk's Discuss on
> > draft-ietf-dnsop-dns-capture-format-08: (with DISCUSS and COMMENT)
> > Date: 19 November 2018 at 00:28:1
On Wed, Nov 21, 2018 at 01:53:09PM +, Sara Dickinson wrote:
>
>
> > Begin forwarded message:
> >
> > From: Benjamin Kaduk mailto:ka...@mit.edu>>
> > Subject: Benjamin Kaduk's Discuss on
> > draft-ietf-dnsop-dns-capture-format-08: (with DISCUSS and COMMENT)
> > Date: 19 November 2018 at 00:2
On timekeeping:
On 11/22/18 07:01, Sara Dickinson wrote:
Section 7.5.1
Does "earliest-time" include leap seconds?
Thanks for noticing this…after digging into it…
The description specifies the number of seconds to be the
number of seconds since the POSIX epoch ("time_t"). POSIX requires that
FYI, this will be +1 UTC for those keeping track of the time
While I don't receive the travel approval to attend this, I have in the
past woken early to listen to many of these talks.
This is useful to operators as well as developers.
Tim
On Thu, Nov 15, 2018 at 4:09 PM Peter van Dijk
wrote:
