On Wed, Apr 11, 2018 at 8:55 AM, Joe Abley wrote:
> Hi Bob,
>
> On Apr 11, 2018, at 08:50, Bob Harold wrote:
>
> > In various places, like 4.3. TSIG Record Format, "resolver and server"
> is used which seems a little vague to me, since I use TSIG between
On Tue, Apr 10, 2018 at 4:57 PM, 神明達哉 wrote:
> At Tue, 10 Apr 2018 14:56:53 -0400,
> tjw ietf wrote:
>
> > This draft was widely accepted in Singapore, and the chairs were waiting
> for
> > a revision before starting a call for adoption. That revision took
Hi Bob,
On Apr 11, 2018, at 08:50, Bob Harold wrote:
> In various places, like 4.3. TSIG Record Format, "resolver and server" is
> used which seems a little vague to me, since I use TSIG between master and
> slave authoritative servers, neither of which is a resolver.
Sorry its taken me so long to get back to this.
On 3/31/2018 7:09 PM, Tony Finch wrote:
There are a few pertinent differences between trust anchor witnesses and
the undeployed RFC 5011 many-keys setup:
* in RFC 5011 each key is completely trusted, whereas no witness is
trusted; compromise
Dear WG,
As I mentioned in London, Im appointing a 3rd chair for DNSOP, to help
with the load, etc.
A number of people kindly volunteered, and I had a really hard time
selecting from such qualified candidates. After agonizing over it for
a few weeks, I've decided to appoint Benno Overeinder.
I'd like the WG to close on this. It feels to me like we've had useful
edit in the call and the document is now stable and ready to move onto
the next phase.
Ship it.
-George
On Fri, Apr 6, 2018 at 2:35 AM, tjw ietf wrote:
>
> After walking through the 168 emails on this