Re: [kitten] Adoption of draft-mccallum-kitten-krb-service-discovery?

[Petr Spacek <[e-mail]>]

On 2.6.2016 19:21, Nico Williams wrote:
> On Wed, Jun 01, 2016 at 12:46:18PM +0200, Petr Spacek wrote:
>> On 20.5.2016 17:06, Nico Williams wrote:
>>> Er, OK, how do we help you implement it?  :)
>>
>> Personally I think that this can be solved by some clever usage of an existing
>> bidirectional language + some metadata.
> 
> I'm not sure what you mean.  "Bi-directional language", to me, refers to
> natural languages where writing is done in two directions.

I'm sorry for being terse but the long answer is here:
https://www.cis.upenn.edu/~bcpierce/papers/lenses-etapsslides.pdf

"Need to find a way of deriving both functions from a single
description" (of RR type in our case).

Of course the description could be encoded in any format. The main point is
that this conversion should be based on very solid theory to eliminate risk of
encode()/decode() inconsistencies.


>> My experience with Augeas shows that it works quite well and that people
>> ironed out a lot of details and difficult corner cases so might be worth
>> investigating this direction.
> 
> The configuration editing tool??
Yes, Augeas is using an bidirectional language.


>> If you do not like bidirectional languages look at
>> https://datatracker.ietf.org/doc/draft-levine-dnsextlang/
>> and implement it :-)
> 
> My preference would be to use XML (I know, I know[*]), mostly because
> people could (and almost certainly would) then write XSLs to generate
> client- and maybe server-side code for dealing with unknown RR types.
> 
> Mostly you just need to generate a tiny bit of HTML and JavaScript to
> present a UI specific to any given RR type, type-check user inputs,
> provide help bubbles and such, format the RDATA with valid
> user inputs, and produce hex-encoded RDATA that the server can then use
> (the server doesn't need to validate the RDATA, but it could do that
> too, also with generated code).
> 
> [*] XSLT is what makes XML tolerable and even desirable for this task.
> 
> I suppose one would have to... design an XML schema for this, write an
> I-D and sample XSLs, submit, and see if dnsop has interest.  I don't
> have the cycles for this :(

I share the same problem :-(

-- 
Petr Spacek  @  Red Hat