On 9 Jul 2018, at 19:28, Suzanne Woolf wrote:
Thanks to all who commented. The WGLC is over and the chairs have seen
strong support for this document and lots of participation in getting
it right, so we’ll be advancing it for publication.
The authors will be spinning up a new version, incorpo
Thanks to Vladimír,
> From: Vladimír Čunát
> "Bailiwick" definition: I have (also) seen use like "in-bailiwick
> records" in the sense being in a subdomain. I can't really judge how
> common that usage is, but it has already been discussed wrt. this draft:
> https://mailarchive.ietf.org/arch/msg
Thanks to all who commented. The WGLC is over and the chairs have seen strong
support for this document and lots of participation in getting it right, so
we’ll be advancing it for publication.
The authors will be spinning up a new version, incorporating the last call
comments, and we’ll submit
On Jul 5, 2018, at 19:38, George Michaelson wrote:
> Only the zone authority can publish a DNSSEC signed zone.
I don't know what this means exactly, but I think it's wrong. I will
illustrate my thinking by using some of these words (like "publish")
in the way that I understand them, to see if t
Only the zone authority can publish a DNSSEC signed zone.
Anyone can claim to publish a view of a non-DNSSEC signed zone.
On Thu, Jul 5, 2018 at 7:11 PM, Dick Franks wrote:
>
> On 3 July 2018 at 16:40, Joe Abley wrote:
>>
>> On 3 Jul 2018, at 09:11, Matthew Pounsett wrote:
>>
>> > This is not
On 3 July 2018 at 16:40, Joe Abley wrote:
> On 3 Jul 2018, at 09:11, Matthew Pounsett wrote:
>
> > This is not a complete review of the latest revision.. I'm hoping to get
> to that in a day or two. But I've got a question about whether something
> should be added to the document..
> >
> > A q
On 4/7/18 1:40 am, Joe Abley wrote:
On 3 Jul 2018, at 09:11, Matthew Pounsett wrote:
This is not a complete review of the latest revision.. I'm hoping to get to
that in a day or two. But I've got a question about whether something should
be added to the document..
A question came up in
On 3 Jul 2018, at 09:11, Matthew Pounsett wrote:
> This is not a complete review of the latest revision.. I'm hoping to get to
> that in a day or two. But I've got a question about whether something
> should be added to the document..
>
> A question came up in conversation recently about the
This is not a complete review of the latest revision.. I'm hoping to get to
that in a day or two. But I've got a question about whether something
should be added to the document..
A question came up in conversation recently about the use of the verb "to
publish" in reference to managing DNS data
Hi all,
Two questions came up recently when writing the DNS Privacy BCP with respect to
terminology (and on the dns-operations list):
1) What do folks think about adding a new definition to this document for a
shortened term for DNS-over-TLS? Since we now have DoH I’ve often taken to
referri
On 2 July 2018 at 00:03, Paul Hoffman wrote
>8
> Well, RFC 1035 *does* say that it is in ASCII, whether we like that or not.
Perhaps we need to remind ourselves what RFC1035 actually *does* say.
ASCII is mentioned in three places only:
2.3.3 para 1, initially about case-insensitive characte
Thanks Paul!
I'm very happy with all the proposed formulation changes (your commit
0fqxn1k41).
--Vladimir
___
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop
On 27 Jun 2018, at 12:56, Dick Franks wrote:
The document appears to be in good shape.
However, I have some difficulty with the wording of these two
paragraphs in
section 2.
The basic wire format for names in the global DNS is a list of
labels ordered by decreasing distance from
On 26 Jun 2018, at 10:09, Vladimír Čunát wrote:
Greetings!
I really like the draft, and I'm sorry to be so late.
This is not late, especially if you really like the draft. :-)
I see one minor
issue just below and then a few nitpicks that I don't feel strongly
about.
I'm marking these in
The document appears to be in good shape.
However, I have some difficulty with the wording of these two paragraphs in
section 2.
The basic wire format for names in the global DNS is a list of
labels ordered by decreasing distance from the root, with the root
label last. Each la
Greetings!
I really like the draft, and I'm sorry to be so late. I see one minor
issue just below and then a few nitpicks that I don't feel strongly about.
> NXDOMAIN:
> "Name Error - Meaningful only for responses from an authoritative
> name server, this code signifies that the domain name
Colleagues,
This begins the working group last call for
draft-ietf-dnsop-terminology-bis-10, "DNS Terminology”. The document has gotten
significant feedback and the editors have worked hard to document current
terminology usage, both among practitioners and for broader audiences; we’d
like to
17 matches
Mail list logo
