Tim Wicinski wrote:
>
> The authors have updated their document to address all outstanding
> issues, and we feel the document is ready for Working Group Last Call.
The rationale for this document is still completely wrong. It does not
provide any reduction in latency compared
On Mon, Nov 9, 2015 at 12:52 PM, Evan Hunt wrote:
> On Mon, Nov 09, 2015 at 04:55:24PM +, Tony Finch wrote:
> > With the current DNS protocol, a stub resolver can get all the records it
> > needs to validate a response in 1RTT, by sending multiple concurrent
> > queries for all
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 11/04/2015 03:26 AM, Stephane Bortzmeyer wrote:
> On Sun, Nov 01, 2015 at 03:06:04AM -0500,
> Warren Kumari wrote
> a message of 28 lines which said:
>
>> The chairs also asked for volunteers for the design team on October
Hey,
What I heard last week was that the chairs had a list of volunteers
and had just found someone to lead the effort (Ralph), and that we
should expect an announcement shortly.
Given the lack of free time during IETF week and the confluence of
ICANN, IETF and IGF events all somewhat
Paul Hoffman wrote:
> On 9 Nov 2015, at 5:02, Tony Finch wrote:
> >
> > The rationale for this document is still completely wrong. It does not
> > provide any reduction in latency compared to the existing DNS protocol.
>
> Is that really true? That is, I assume that you
> On Nov 6, 2015, at 12:10 PM, Joe Abley wrote:
>
> Hi Duane,
>
> On 6 Nov 2015, at 14:32, Wessels, Duane wrote:
>
>>> On Nov 5, 2015, at 3:26 AM, Tony Finch wrote:
>>>
>>> Has anyone done a survey of where the leaked .home queries come from?
>>
>> In the
From: Olafur Gudmundsson [mailto:o...@ogud.com]
Subject: Re: [DNSOP] discussion for draft-woodworth-bulk-rr-00.txt
>
> On Nov 2, 2015, at 12:28 AM, Woodworth, John R
> wrote:
>
> See inline comments:
>
>
> > > -Original Message-
> > > From: Edward Lewis
On 9 Nov 2015, at 8:55, Tony Finch wrote:
Paul Hoffman wrote:
On 9 Nov 2015, at 5:02, Tony Finch wrote:
The rationale for this document is still completely wrong. It does
not
provide any reduction in latency compared to the existing DNS
protocol.
Is that really
On 9 Nov 2015, at 5:02, Tony Finch wrote:
Tim Wicinski wrote:
The authors have updated their document to address all outstanding
issues, and we feel the document is ready for Working Group Last
Call.
The rationale for this document is still completely wrong. It does
On Mon, Nov 09, 2015 at 04:55:24PM +, Tony Finch wrote:
> With the current DNS protocol, a stub resolver can get all the records it
> needs to validate a response in 1RTT, by sending multiple concurrent
> queries for all the possible delegation points in the QNAME.
But has to retain state for
The IESG has received a request from the Domain Name System Operations WG
(dnsop) to consider the following document:
- 'Add 100.64.0.0/10 prefixes to IPv4 Locally-Served DNS Zones Registry.'
as Best Current Practice
The IESG plans to make a decision in the next few weeks, and solicits
final
The IESG has received a request from the Domain Name System Operations WG
(dnsop) to consider the following document:
- 'DNS query name minimisation to improve privacy'
as Experimental RFC
The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action.
Wessels, Duane wrote:
> On Nov 5, 2015, at 3:26 AM, Tony Finch wrote:
> >
> > Has anyone done a survey of where the leaked .home queries come from?
>
> In the spirit of Measurement-Driven Protocol Engineering here are some
> recent data points from root
On Sun, Nov 1, 2015 at 5:36 PM, Tim Wicinski wrote:
> Hi
>
> The authors have updated their document to address all outstanding issues,
> and we feel the document is ready for Working Group Last Call.
>
> This starts a Working Group Last Call for
>
14 matches
Mail list logo