Hi DNSOP,
we have prepared a specification document (see below), which fills a gap
that appears to be missing currently — The EDNS(0) textual and JSON format.
It also fixes a "specification bug" in an existing and related RFC.
We believe this draft is pretty much complete and have a first PoC
implementation ready. While it would be viable to submit it
individually, we believe that the adoption by the WG would be generally
beneficial.
We would also welcome any improvement suggestions and useful
corrections. However, fearing discussion loops arguments about details,
we encourage to moderate discussion of details, such as if some fields
in a specific option shall be separated by commas or slashes.
This document is full of design decisions that might be differently
appealing to everyone. The format might seem complicated, but the goal
was best possible human readability.
And the more general (and important) goal is to make the standard
useful, so that it gets adopted by implementations.
Thank you for reading the document and for considering its adoption,
Libor & Tom
-------- Přeposlaná zpráva --------
Předmět: New Version Notification for
draft-peltan-edns-presentation-format-00.txt
Datum: Wed, 23 Nov 2022 11:20:19 -0800
Od: internet-dra...@ietf.org
Komu: Libor Peltan <libor.pel...@nic.cz>, Tom Carpay <t...@nlnetlabs.nl>
A new version of I-D, draft-peltan-edns-presentation-format-00.txt
has been successfully submitted by Libor Peltan and posted to the
IETF repository.
Name: draft-peltan-edns-presentation-format
Revision: 00
Title: EDNS Presentation and JSON Format
Document date: 2022-11-23
Group: Individual Submission
Pages: 19
URL:
https://www.ietf.org/archive/id/draft-peltan-edns-presentation-format-00.txt
Status:
https://datatracker.ietf.org/doc/draft-peltan-edns-presentation-format/
Htmlized:
https://datatracker.ietf.org/doc/html/draft-peltan-edns-presentation-format
Abstract:
This document describes textual and JSON representation format of
EDNS option. It also modifies the escaping rules of JSON
representation of DNS messages, previously defined in RFC8427.
The IETF Secretariat
_______________________________________________
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop
