George Kuo who is not subscribed to the list said this:
>Thanks all for sharing.
>I have learned from all your input.
>
>George Kuo.
On Fri, May 22, 2020 at 2:11 PM George Michaelson wrote:
>
> Thank you all for the responses. This has been very interesting. Paul
> actually hinted this was the p
Thank you all for the responses. This has been very interesting. Paul
actually hinted this was the probable direction, and I think we can
say categorically the dictionary doesn't need updating because there
isn't a sense this concept needs defining in this context within this
WG.
Many thanks
-Geo
IMHO, public DNS is not a technical jargon which needs a DNS terminology
RFC to record (it collects all DNS definition and terms from other DNS
RFC).
The term "Public DNS" or "Public DNS service" belongs to the scope of how
people provide and operate DNS services to their best interests. There ar
A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Domain Name System Operations WG of the IETF.
Title : Recommendations for DNSSEC Resolvers Operators
Authors : Daniel Migault
On Friday, 22 May 2020 00:55:34 UTC George Michaelson wrote:
> My Colleague George Kuo asked me for definitions of public DNS
> service. not "public DNS" but the trigram "public DNS service"
>
> Colloquially we understand this reasonably well. It is in the space of
> what Google, quad9, CloudFlare
On 21 May 2020, at 20:55, George Michaelson wrote:
> My Colleague George Kuo asked me for definitions of public DNS
> service. not "public DNS" but the trigram "public DNS service"
>
> Colloquially we understand this reasonably well. It is in the space of
> what Google, quad9, CloudFlare and oth
On Friday, 22 May 2020 00:31:34 UTC Masataka Ohta wrote:
> ...
>
> While I'm not against the clarification, the draft should mention
> that rfc1034 already states:
>
> To fix this problem, a zone contains "glue" RRs which are not
> part of the authoritative data, and are address RRs for t
My Colleague George Kuo asked me for definitions of public DNS
service. not "public DNS" but the trigram "public DNS service"
Colloquially we understand this reasonably well. It is in the space of
what Google, quad9, CloudFlare and others do. The various clean DNS
feeds people subscribe to, it is
Tim Wicinski wrote:
This starts a Call for Adoption for draft-andrews-dnsop-glue-is-not-optional
The draft is available here:
https://datatracker.ietf.org/doc/draft-andrews-dnsop-glue-is-not-optional/
Please review this draft to see if you think it is suitable for adoption
by DNSOP, and commen
On Thu, 21 May 2020, Warren Kumari wrote:
Yes -- but information in the additional section should not be
promoted to an answer.
A week or two ago I scannned TLD zone files to see how many signed A and
records there were. Quite a lot, most looks to be orphan glue in
Afilias zones that th
On Thu, May 21, 2020 at 6:00 PM Töma Gavrichenkov wrote:
>
> Peace,
>
> On Thu, May 21, 2020 at 11:08 PM Warren Kumari wrote:
> > [..skip..]
> > Looking in the webserver log, there are also some hits - e.g:
> > - - [21/May/2020:19:09:10 +] "GET /favicon.ico HTTP/1.1" 404 209
> > "http://www.w
Peace,
On Thu, May 21, 2020 at 11:08 PM Warren Kumari wrote:
> [..skip..]
> Looking in the webserver log, there are also some hits - e.g:
> - - [21/May/2020:19:09:10 +] "GET /favicon.ico HTTP/1.1" 404 209
> "http://www.wow4dns.com/"; "Mozilla/5.0 (Macintosh; Intel Mac OS X
> 10_15_4) AppleWeb
On Thu, May 21, 2020 at 5:41 PM John Levine wrote:
>
> In article
> you
> write:
> >What if you *only* have glue, and no authoritative answer / server?
> >Can I register example.com, put in www.example.com A 192.0.2.1 as
> >glue, and not bother with this whole annoying authoritative server
> >t
In article
you write:
>What if you *only* have glue, and no authoritative answer / server?
>Can I register example.com, put in www.example.com A 192.0.2.1 as
>glue, and not bother with this whole annoying authoritative server
>thing?
Based on my recent analysis of TLD zones, yes if the zone is m
Hi all,
I decided to start a new thread for this, because it isn't really
about draft-andrews-dnsop-glue-is-not-optional - it is more of an
interesting aside / rathole...
What if you *only* have glue, and no authoritative answer / server?
Can I register example.com, put in www.example.com A 192.0
A new meeting session request has just been submitted by Tim Wicinski, a Chair
of the dnsop working group.
-
Working Group Name: Domain Name System Operations
Area Name: Operations and Management Area
Session Requester: Tim Wicinski
Nu
On Mon, May 18, 2020 at 1:50 PM Tim Wicinski wrote:
> All,
>
> As we stated in the meeting and in our chairs actions, we're going to run
> regular call for adoptions over next few months.
> We are looking for *explicit* support for adoption.
>
>
> This starts a Call for Adoption for
> draft-andre
I am supporting adoption.
Yours,
Daniel
On Thu, May 21, 2020 at 10:41 AM Wes Hardaker wrote:
> Tim Wicinski writes:
>
> > We are looking for *explicit* support for adoption.
>
> Yes please!
> --
> Wes Hardaker
> USC/ISI
>
> ___
> DNSOP mailing list
>
Tim Wicinski writes:
> We are looking for *explicit* support for adoption.
Yes please!
--
Wes Hardaker
USC/ISI
___
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop
On 10. 04. 20 15:45, Shumon Huque wrote:
> Hi folks,
>
> Paul Vixie, Ralph Dolmans, and I have submitted this I-D for
> consideration:
>
> https://tools.ietf.org/html/draft-huque-dnsop-ns-revalidation-01
I would appreciate a practical example of changes envisioned in the following
paragraph:
20 matches
Mail list logo
