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

[Nico Williams <[e-mail]>]

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.

> 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??

> 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 :(

Nico
--