* Stephane Bortzmeyer:
I'm aware of draft-mohan-dns-query-xml, which partially solves my
problem (except I would like the RDATA to be structured as well, not a
blob of hexadecimal data).
In this area, draft-levine-dnsextlang-00 might be helpful.
--
Florian Weimer
I have a project where DNS data must be transported in Web-friendly
environments, which mean encoded in JSON or XML. I'm not asking IETF
to normalize DNS-in-XML or DNS-in-JSON :-) I will define my format and
the field names, but I hope to save time by reusing analogue work.
I'm aware of
On 1/18/2012 7:06 PM, W.C.A. Wijngaards wrote:
this sounds very cool; is there an internet draft or tech note
describing the protocol so that others may also implement this?
It exists to bypass deep inspection firewalls, and it works. The plain
DNS format as you would use over TCP, but
On Jan 18, 2012, at 11:14 AM, Paul Vixie wrote:
On 1/18/2012 7:06 PM, W.C.A. Wijngaards wrote:
this sounds very cool; is there an internet draft or tech note
describing the protocol so that others may also implement this?
It exists to bypass deep inspection firewalls, and it works. The
On Wed, Jan 18, 2012 at 07:14:27PM +,
Paul Vixie p...@redbarn.org wrote
a message of 74 lines which said:
in particular, the order in which it's probed (compared to EDNS0
UDP, EDNS0 TCP, old style UDP, old style TCP) should be
specified. the NS RRset gives no hint of the name server's
On 18 Jan 2012, at 19:41, Stephane Bortzmeyer wrote:
On Wed, Jan 18, 2012 at 07:14:27PM +,
Paul Vixie p...@redbarn.org wrote
a message of 74 lines which said:
in particular, the order in which it's probed (compared to EDNS0
UDP, EDNS0 TCP, old style UDP, old style TCP) should be
