Petr Spacek wrote:
Thanks again for your feedback.
> > Is the indirection problem specific to classless reverse DNS (which
> > is the approach I took) or does it apply to the forward DNS as well?
> > Suggestions for wording welcome.
>
> Personally I would mention that this
On 10.11.2015 15:22, Tony Finch wrote:
> I have published a new version of my Classless IN-ADDR.ARPA draft. This
> incorporates some miscellaneous suggestions from before the IETF meeting,
> and Petr's suggestions from last week.
>
> All comments and suggestions welcome!
>
> Petr, I've cut down
On 10 Nov 2015, at 12:43, Mark Andrews wrote:
> Perhaps we should be getting Jari, Suzanne and Andrew to push this
> at IGF meetings.
Or perhaps we should not.
--Paul Hoffman
___
DNSOP mailing list
DNSOP@ietf.org
Paul Hoffman 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.
>
> I'm confused. How does the stub
Ólafur Guðmundsson wrote:
> 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
Perhaps we should be getting Jari, Suzanne and Andrew to push this
at IGF meetings.
In message <20151110152511.6f1a1...@pallas.home.time-travellers.org>, Shane Ker
r writes:
> Mark,
>
> On Fri, 06 Nov 2015 10:54:02 +1100
> Mark Andrews wrote:
>
> > I keep getting told the
> On 10 Nov 2015, at 21:11, Paul Hoffman wrote:
>
> On 10 Nov 2015, at 12:43, Mark Andrews wrote:
>
>> Perhaps we should be getting Jari, Suzanne and Andrew to push this
>> at IGF meetings.
>
> Or perhaps we should not.
+1
Do we know of any implementations that have tried this?
>From my high tech gadget
> On Nov 10, 2015, at 13:29, Tony Finch wrote:
>
> Paul Hoffman wrote:
>
>>> With the current DNS protocol, a stub resolver can get all the records it
>>> needs to
>> Yes. Daily checks of all delegated server. I don't believe they are
>> currently reporting the discovered faults.
>>
>> http://bamus.switch.ch/edns/summary.html
> Cool, but unless they inform someone it won't help improve anything.
> Others do and it's good to see some people on the
Hi Stephane,
I read over this and have a few thoughts to share:
This updates RFC 2308 (Negative Caching of DNS Queries). This would seem to be
the
key text from 2308 to update:
A negative answer that resulted from a name error (NXDOMAIN) should
be cached such that it can be retrieved
In message <2015020725.34ce83c82...@rock.dv.isc.org>, Mark Andrews writes:
> In message , "Wessels, Dua
> ne
> " writes:
>
> > I think the WG needs to discuss and agree whether or not to make the
> > NXDOMAIN cut based on QNAME only, or on
In message , "Wessels, Duane
" writes:
> Hi Stephane,
>
> I read over this and have a few thoughts to share:
>
> This updates RFC 2308 (Negative Caching of DNS Queries). This would seem to
> be the
> key text from 2308 to update:
>
>A
> On 11 nov. 2015, at 08:11, Dr Eberhard W Lisse wrote:
>
> So whatever comes out of that could, eventually, also go in.
I completely agree.
My only point is that I urge IETF to write text som that any(!) reader can
understand there will always be cases where "errors" for
On 10 Nov 2015, at 22:24, Jim Reid wrote:
>> Or perhaps we should not.
>
> +1
This discussion on making tests is coming back now and then. In RIPE, in IETF,
in discussions around TLDs (specifically ccTLDs).
I have run one such initiative myself.
Everything has so far collapsed into collision
In message <5373ddab-1ed2-489b-ab62-ba7cf6d3d...@frobbit.se>, "Patrik =?utf-8?b
?RsOkbHRzdHLDtm0=?=" writes:
> On 10 Nov 2015, at 22:24, Jim Reid wrote:
>
> >> Or perhaps we should not.
> >
> > +1
>
> This discussion on making tests is coming back now and then. In RIPE, in
> IETF, in discussions
On Wed, Nov 11, 2015 at 07:25:39AM +0100, Patrik Fältström wrote:
> Everything has so far collapsed into collision between tech people not
> agreeing on what is right and wrong. It also collapses into clashes between
> registry policy and the tests made. I.e. just the registration policy is
>
I have published a new version of my Classless IN-ADDR.ARPA draft. This
incorporates some miscellaneous suggestions from before the IETF meeting,
and Petr's suggestions from last week.
All comments and suggestions welcome!
Petr, I've cut down your security considerations fairly viciously; please
Mark,
On Fri, 06 Nov 2015 10:54:02 +1100
Mark Andrews wrote:
> I keep getting told the IETF can't tell people what to do
> but that is *exactly* what we do do when we issue a BCP.
> We tell people what best current practice is and ask them
> to follow it.
On Wed, Nov 11, 2015 at 07:43:30AM +1100, Mark Andrews wrote:
> Perhaps we should be getting Jari, Suzanne and Andrew to push this
> at IGF meetings.
Not knowing what IGF meetings are, I can't comment on this specific
point.
> So we don't say what's right because you fear that not everybody
>
On Tue, Nov 10, 2015 at 09:29:30PM +, Tony Finch wrote:
> Paul Hoffman 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
20 matches
Mail list logo