On 5 Sep 2016, at 23:26, Jerry Lundström wrote:
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
ther
On 5 Sep 2016, at 21:44, 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 applicatio
Shane Kerr wrote:
> 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 u
In your letter dated Mon, 5 Sep 2016 15:47:37 +0800 you wrote:
>Finally, I note that the RIPE Atlas system uses a type of DNS JSON
>representation when you use their API to query for DNS measurement
>results. You can get a sample here:
>
>https://atlas.ripe.net/api/v2/measurements/5009360/results?s
In your letter dated Tue, 6 Sep 2016 06:26:58 + you wrote:
> I was more commenting on the fact that it is escaping in a format
> that already support escaping. The JSON output would be double
> escaped and implementations would need to unescape it themselves
> rather then let JSON handle it.
J
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
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
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
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
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 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
>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
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,
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
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
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
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 take it to the Independent Sub
17 matches
Mail list logo
