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 : BULK DNS Resource Records
Authors : John Woodworth
Dean Ballew
Need a short slot (5 mn) about the revision of TSIG specs just
submitted as draft-dupont-dnsop-rfc2845bis-00.txt
Thanks
francis.dup...@fdupont.fr
PS: there are in fact only a few since IETF99: just the work is in
progress and should one day become a WG item. IMHO today the main
difference is
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 : Serving Stale Data to Improve DNS Resiliency
Authors : David C Lawrence
Thanks! Verified.
W
On Mon, Oct 30, 2017 at 2:24 AM, Matthijs Mekking
wrote:
> Hi,
>
> This errata appears to be valid. In addition, the following text must also
> be corrected, from:
>
>The rest of the zone data has the same signature as the SOA record,
>i.e.,
The following errata report has been verified for RFC6781,
"DNSSEC Operational Practices, Version 2".
--
You may review the report below and at:
http://www.rfc-editor.org/errata/eid5174
--
Status: Verified
Type: Technical
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 : Serving Stale Data to Improve DNS Resiliency
Authors : David C Lawrence
All
Please submit any request for presenting at IETF100 to the chairs. We'll
be working on a draft agenda in the interim.
thanks
tim
___
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop
> I see that this draft uses a syntax similar to RFC 8145 Trust Anchor
> Telemetry RFC (which uses _ta-) albeit without the leading
> underscore, i.e. .ta-.
>
> I'd like to propose instead ._ta.
>
> This would allow _ta to be registered as a standalone entry in the
> underscore label registry,
I see that this draft uses a syntax similar to RFC 8145 Trust Anchor
Telemetry RFC (which uses _ta-) albeit without the leading
underscore, i.e. .ta-.
I'd like to propose instead ._ta.
This would allow _ta to be registered as a standalone entry in the
underscore label registry, whilst also avoid
On Mon, Oct 30, 2017 at 03:33:00PM +,
Ray Bellis wrote
a message of 24 lines which said:
> Multiple answers:
Also draft-fujiwara-dnsop-additional-answers
___
DNSOP mailing list
DNSOP@ietf.org
WG chairs
Could you please let me / the WG know where we stand with the various
drafts describing ways to accommodate multiple questions and/or answers
in a single request?
Multiple questions:
- draft-bellis-dnsext-multi-qtypes
- draft-yao-dnsop-accompanying-questions
Multiple answers:
-
Hello,
I submitted another multiple response proposal.
https://tools.ietf.org/html/draft-fujiwara-dnsop-additional-answers-00
It is similar to draft-wkumari-dnsop-multiple-responses, however, it
proposes authoritative DNS server software developers choose
additional resource records.
# Many
Hi,
This errata appears to be valid. In addition, the following text must
also be corrected, from:
The rest of the zone data has the same signature as the SOA record,
i.e., an RRSIG created with DNSKEY_K_14.
to:
The rest of the zone data has the same signature as the SOA record,
13 matches
Mail list logo