Paul,
At 2016-09-03 15:43:34 -0700
"Paul Hoffman" wrote:
> Greetings again. I have updated my draft on describing DNS messages in
> JSON. I still don't think that this WG needs to adopt this given that it
> is, as far as I can tell, thinly implemented. I think it's probably
> about baked enou
Hi Paul,
On 09/03/16 22:43, Paul Hoffman wrote:
> Greetings again. I have updated my draft on describing DNS messages in
> JSON. I still don't think that this WG needs to adopt this given that it
> is, as far as I can tell, thinly implemented. I think it's probably
> about baked enough for me to t
On 05/09/2016 09:42, Jerry Lundström wrote:
> - The use of "!" and "*" in object attribute names will make it hard to
> use in language that can read JSON and give out native objects such as
> JavaScript.
Harder, but not "hard", in JS.
You can always use myObject['RDATA*'] syntax if you need t
Shane Kerr wrote:
>
> It occurs to me that maybe we want an option to have arrays of RRset
> instead of arrays of RRs?
If you do that, how do you represent the covering signature(s)?
Tony.
--
f.anthony.n.finchhttp://dotat.at/ - I xn--zr8h punycode
South Utsire, East Forties: Southerly 4,
>First, it seems like it might be nice to have a way to express RDATA in
>DNS presentation format. The document is very clear that no way is
>provided for this, but it seems like it would be really, really useful.
If you want to do that, you could probably piggyback it on my recently
revived draft
On 3 Sep 2016, at 20:20, Robert Edmonds wrote:
In section 3:
A paired DNS query and response is represented as an object. Two
optional members of this object are names "queryRecord" and
"responseRecord", and each has a value that is an message object.
This design was chosen (as com
On 5 Sep 2016, at 0:47, Shane Kerr wrote:
First, it seems like it might be nice to have a way to express RDATA
in
DNS presentation format. The document is very clear that no way is
provided for this, but it seems like it would be really, really
useful.
If it useful for a particular applicati
On 5 Sep 2016, at 1:42, Jerry Lundström wrote:
Overall looks good, just a few minor concerns with adaptation/
interoperability:
- Non-ASCII octets escaping "\DDD" may lead to broken implementations
and/or encoding problem (oh so many printf()'ed JSON implementations
out
there)
Sure, but I'm
John,
At 2016-09-05 16:38:00 -
"John Levine" wrote:
> >First, it seems like it might be nice to have a way to express RDATA in
> >DNS presentation format. The document is very clear that no way is
> >provided for this, but it seems like it would be really, really useful.
>
> If you want t
Tony,
At 2016-09-05 11:22:48 +0100
Tony Finch wrote:
> Shane Kerr wrote:
> >
> > It occurs to me that maybe we want an option to have arrays of RRset
> > instead of arrays of RRs?
>
> If you do that, how do you represent the covering signature(s)?
I'm not sure I understand the question? An
Paul,
At 2016-09-05 10:21:40 -0700
"Paul Hoffman" wrote:
> On 5 Sep 2016, at 0:47, Shane Kerr wrote:
>
> > First, it seems like it might be nice to have a way to express RDATA
> > in
> > DNS presentation format. The document is very clear that no way is
> > provided for this, but it seems like
Hi Paul,
On 09/05/16 17:40, Paul Hoffman wrote:
> On 5 Sep 2016, at 1:42, Jerry Lundström wrote:
>
>> - Non-ASCII octets escaping "\DDD" may lead to broken implementations
>> and/or encoding problem (oh so many printf()'ed JSON implementations out
>> there)
>
> Sure, but I'm not sure what to do
12 matches
Mail list logo
