Re: [DNSOP] Terry Manderson's Discuss on draft-ietf-dnsop-dnssec-roadblock-avoidance-04: (with DISCUSS and COMMENT)

2016-07-13 Thread Terry Manderson
Hi Spencer, On 14/07/2016, 12:57 PM, "Spencer Dawkins at IETF" wrote: > >Terry, I like where you're headed, but just to ask the obvious question, >are you thinking the draft would, or would not, also contain something >like "at the time this document was approved,

Re: [DNSOP] Terry Manderson's Discuss on draft-ietf-dnsop-dnssec-roadblock-avoidance-04: (with DISCUSS and COMMENT)

2016-07-13 Thread Spencer Dawkins at IETF
This is Not My Yes, but ... On Wed, Jul 13, 2016 at 12:28 AM, Terry Manderson wrote: > Hi Wes, > > Thanks for responding. > > I'll trim to only the the remaining items needing a response, and express > my appreciation at the clarified items. > > On 9/07/2016, 9:53

Re: [DNSOP] JavaScript use case for DNS-over-HTTP (was Call for Adoption: draft-song-dns-wireformat-http)

2016-07-13 Thread John Levine
>> why all that complexity? if some remote device (iot thingy) wants 'dns over >>> http' why would it not (as a first order answer) just ask >>> /cgi-bin/dnslookup for 'srv:foo.com' ? (returned answer in txt, json, >>> etc...) >> Security in IoT is close to an oxymoron, but my device would like

Re: [DNSOP] JavaScript use case for DNS-over-HTTP (was Call for Adoption: draft-song-dns-wireformat-http)

2016-07-13 Thread Christopher Morrow
On Wed, Jul 13, 2016 at 3:42 PM, John R Levine wrote: > why all that complexity? if some remote device (iot thingy) wants 'dns over >> http' why would it not (as a first order answer) just ask >> /cgi-bin/dnslookup for 'srv:foo.com' ? (returned answer in txt, json, >> etc...) >>

Re: [DNSOP] JavaScript use case for DNS-over-HTTP (was Call for Adoption: draft-song-dns-wireformat-http)

2016-07-13 Thread John R Levine
why all that complexity? if some remote device (iot thingy) wants 'dns over http' why would it not (as a first order answer) just ask /cgi-bin/dnslookup for 'srv:foo.com' ? (returned answer in txt, json, etc...) why bother with a bunch of javascript tomfoolery? Security in IoT is close to an

Re: [DNSOP] JavaScript use case for DNS-over-HTTP (was Call for Adoption: draft-song-dns-wireformat-http)

2016-07-13 Thread Christopher Morrow
On Wed, Jul 13, 2016 at 10:59 AM, Tony Finch wrote: > Shane Kerr wrote: > > > > OTOH, I am (obviously) not a web developer, so perhaps I overestimate > > the difficulty in working with DNS binary-format. Maybe it's a > > relatively compact set of

Re: [DNSOP] JavaScript use case for DNS-over-HTTP (was Call for Adoption: draft-song-dns-wireformat-http)

2016-07-13 Thread Tony Finch
Shane Kerr wrote: > > OTOH, I am (obviously) not a web developer, so perhaps I overestimate > the difficulty in working with DNS binary-format. Maybe it's a > relatively compact set of JavaScript functions that can be used? It wouldn't be completely horrible to parse