On Wed, Mar 02, 2016 at 08:06:39AM +1100, Mark Andrews wrote:
> ANC does not work for zones using OPTOUT. This is just about all
> TLDs and similar zones.
To be pedantic, it doesn't work for optout ranges. I don't actually know
offhand of any zones that mix optout and non-optout, though, so it's
In message , "John R Levine" write
s:
> >> I suppose I could say web based configuration crudware a few dozen more
> >> times, but I doubt it would sink in any more than it has before.
>
> > Look at https://ednscomp.isc.org/compliance/summary.html.
>
> I did. It has nothing to do with configura
We did not use get because get does not have a request payload.
On March 1, 2016 6:44:16 PM PST, Davey Song wrote:
>On Tue, Mar 1, 2016 at 11:58 AM, Paul Hoffman
>wrote:
>
>> This document is a good idea, but it has some faults that need to be
>fixed
>> before it goes forwards.
>>
>> - In the In
On Tue, Mar 1, 2016 at 11:58 AM, Paul Hoffman wrote:
> This document is a good idea, but it has some faults that need to be fixed
> before it goes forwards.
>
> - In the Introduction, it says in essence that this is just using HTTP to
> tunnel DNS and is not of use to web browsers. This is wrong,
In response to the discussion of where the use of TXT records is discussed, see:
https://tools.ietf.org/html/rfc6764
This in turn cites:
https://tools.ietf.org/html/rfc6763#section-6
Which seems like the way to do these things.
___
DNSOP mailing list
I suppose I could say web based configuration crudware a few dozen more
times, but I doubt it would sink in any more than it has before.
Look at https://ednscomp.isc.org/compliance/summary.html.
I did. It has nothing to do with configuration software or new RRTYPEs,
which demonstrates my po
On Tue, Mar 01, 2016 at 06:15:22PM -0500, John R Levine wrote:
> >>The NDR record is deliberately free format because changing DNS
> >>servers is HARD, no really it is ridiculously hard with a ten year
> >>lag. Which is of course why we won't use a new record at all:
> >
> >Really? We have rpm's o
In message , "John R Levine"
writes:
> >> The NDR record is deliberately free format because changing DNS
> >> servers is HARD, no really it is ridiculously hard with a ten year
> >> lag. Which is of course why we won't use a new record at all:
> >
> > Really? We have rpm's of new versions of na
The NDR record is deliberately free format because changing DNS
servers is HARD, no really it is ridiculously hard with a ten year
lag. Which is of course why we won't use a new record at all:
Really? We have rpm's of new versions of named supplied within
hours of ISC's public announcements of
In message
, Phillip
Hallam-Baker writes:
> On Tue, Mar 1, 2016 at 11:59 AM, Ray Bellis wrote:
> >
> >
> > On 01/03/2016 16:56, John Levine wrote:
> >
> >> If you take a look at that registry, it's a stroll down memory lane.
> >> You'll find NVP-II from RFC 741 in 1977, PUP and XNS-IDP from Xer
In message <56d5b830.80...@bellis.me.uk>, Ray Bellis writes:
>
>
> On 01/03/2016 15:26, =D3lafur Gu=F0mundsson wrote:
>
> > Thus I consider your document a distraction, we should push the general
> > solution not a special case
>
> +1
>
> Ray
ANC can be both good and bad depending upon where
On Tue, Mar 1, 2016 at 1:13 PM, John Levine wrote:
>>So while SRV and NAPTR and the TXT records are stuck using the two
>>level approach, there is also a clear need for a meta-discovery record
>>that only uses the service prefix.
>
> Maybe.
>
>>Using SRV discovery you might use:
>>
>>_mmm._tcp.exa
>So while SRV and NAPTR and the TXT records are stuck using the two
>level approach, there is also a clear need for a meta-discovery record
>that only uses the service prefix.
Maybe.
>Using SRV discovery you might use:
>
>_mmm._tcp.example.com SRV 1 10 80 host1.example.com
>_mmm._tcp.example.com
On Tue, Mar 1, 2016 at 11:59 AM, Ray Bellis wrote:
>
>
> On 01/03/2016 16:56, John Levine wrote:
>
>> If you take a look at that registry, it's a stroll down memory lane.
>> You'll find NVP-II from RFC 741 in 1977, PUP and XNS-IDP from Xerox in
>> 1980, and other great hits from networking history
Ok, let's turn that around then - are there entries in the existing
protocol registry that _should_ be reserved in the underscore registry,
"just in case" ?
Not that I can see, but take a look and maybe I missed something. It has
under 150 entries:
http://www.iana.org/assignments/protocol-nu
On 3/1/2016 8:46 AM, Ray Bellis wrote:
I'd suggest that perhaps the keywords from the protocol registry (or a
canonical representation thereof, for those that don't match LDH) should
actually be reserved ?
yeah, that makes sense.
d/
--
Dave Crocker
Brandenburg InternetWorking
bbiw.net
On 01/03/2016 16:56, John Levine wrote:
> If you take a look at that registry, it's a stroll down memory lane.
> You'll find NVP-II from RFC 741 in 1977, PUP and XNS-IDP from Xerox in
> 1980, and other great hits from networking history.
>
> I really doubt that people are going to ever publish
>> The other which I prefer is simply to put the four _proto tags into
>> the new underscore registry. Add a note that they have subnames from
>> the RFC 6335 services registry, and for anew new protocol tags try to to
>> keep the protocol names consistent with the keywords in the protocol
>> numb
On 01/03/2016 16:39, John Levine wrote:
> The other which I prefer is simply to put the four _proto tags into
> the new underscore registry. Add a note that they have subnames from
> the RFC 6335 services registry, and for anew new protocol tags try to to
> keep the protocol names consistent wi
>If SRV continues to specify _Proto choices from a separate IANA
>registry,
It never did and does not now. There is no protocol name registry or
_proto tag registry. (There is a S-NAPTR application protocol tag
registry, but since it contains entries like "diameter.tls.tcp" this
is not the
On 01/03/2016 15:26, Ólafur Guðmundsson wrote:
> Thus I consider your document a distraction, we should push the general
> solution not a special case
+1
Ray
___
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop
On Mon, Feb 29, 2016 at 4:03 PM, Warren Kumari wrote:
>
>
> On Mon, Feb 29, 2016 at 10:04 AM Shane Kerr
> wrote:
>
>> Ed,
>>
>> At 2016-02-29 14:34:39 +
>> Edward Lewis wrote:
>> > I don't think I was clear - this is only about the DNS protocol. This
>> > document proposes that the DNS pro
On 2/29/2016 2:32 PM, Ray Bellis wrote:
On 29/02/2016 22:27, John R Levine wrote:
The existing port and service registry already has all of the _service
names, and is updated as people invent new services. What's the benefit
of duplicating it rather than just pointing to it?
+1
So this c
>> It seems to me that deploying code under the assumption of only limited
>> caching of negative results is a good way to block all kinds of future
>> work, or alternatively, you may be in for a lot of pain if other people
>> decide that negative caching is more important.
>
>ANC was deliberatedly
Having done this myself, I think there are several situations in which it
is common to look up a name shortly before adding it to a zone. e.g. you
expect a name to exist, whoops, fix the omission, then have to wait a TTL.
Or you are trying to come up with a domain name that hasn't already been
reg
In message , Tony
Finch writes:
> Mark Andrews wrote:
> > In message <20160229225356.56583.qm...@ary.lan>, "John Levine" writes:
> > >
> > > >You could apply the technique to any signed zone where you are not
> > > >worried about not having instant visibility after adding a new name
> > > >to th
In message , Philip Homburg writes:
> >Yes, ANC breaks using the DNS for Internet reachability testing.
> >
> >Named has code to return zero TTLs on negative answers to SOA queries
> >to avoid polluting caches with NXDOMAIN results when searching for
> >zone cuts. Nsupdate and similar tools need
Mark Andrews wrote:
> In message <20160229225356.56583.qm...@ary.lan>, "John Levine" writes:
> >
> > >You could apply the technique to any signed zone where you are not
> > >worried about not having instant visibility after adding a new name
> > >to the zone.
> >
> > I don't understand this. If I
>Yes, ANC breaks using the DNS for Internet reachability testing.
>
>Named has code to return zero TTLs on negative answers to SOA queries
>to avoid polluting caches with NXDOMAIN results when searching for
>zone cuts. Nsupdate and similar tools need to be able to find the
>containing zone of name
29 matches
Mail list logo
