Dear colleagues,
Please note the new revision of our agenda for IETF 115 at
https://datatracker.ietf.org/meeting/115/materials/agenda-115-dnsop-01.
The main change is that we've added some time for draft-ietf-dnsop-alt-tld. The
chairs have discussed extensively what to do next with alt-tld, sin
OARC 40 will be a two-day hybrid meeting held on 16 & 17 February in
Atlanta (GA), USA at 10:00 AM (Local time - EST (UTC-05:00)). The onsite
part of the meeting will be colocated with NANOG 87.
The Programme Committee is seeking contributions from the community.
All DNS-related subjects and sug
Reviewer: Scott Rose
Review result: Ready with Nits
This Internet-Draft assigns a code point to a cryptographic algorithm for use
in DNSSEC and obsoletes a preceding algorithm. The DNS and DNSSEC protocols are
not changed in any way and in that sense of review the I-D is Ready.
The nits listed in
Dear colleagues,
[ObDisclaimer: I work for the Internet Society but I'm not speaking for them.]
On Wed, Oct 26, 2022 at 05:23:42PM +, Paul Hoffman wrote:
Thus, we have a standards-track document that requires that every resolver on
the planet is supposed to have special rules for this part
On 8/1/22 15:58, Ben Schwartz wrote:
On Mon, Aug 1, 2022 at 8:32 AM Independent Submissions Editor (Eliot
Lear) mailto:rfc-...@rfc-editor.org>> wrote:
...
I do agree with Martin that it would be helpful to have some
registration of names so that conflicts between name spaces can be
