Re: [netconf] I-D Action: draft-ietf-netconf-crypto-types-09.txt

[Kent Watsen <[e-mail]>]

Hi Martin,

>> 4) to enable the SSH and TLS models to use types defined in their
>> protocol specs, mapping tables were added to those drafts to map the
>> protocol-specific types to the generic crypto-types type.
> 
> So perhaps this is not the best solution?  The big set of types (in
> crypto-types) will change over time, and the subsets used in various
> applications will also change over time.  The best solution for such
> sets in the IETF seems to be IANA registries, with corresponding
> IANA-maintained YANG modules.

I'm hoping someone, perhaps my co-authors, can suggest a path forward.



>> 8) our efforts to normalize this may be futile, and yet we want to
>> support keystore.
> 
> Perhaps we can take a step back and define just the types we need
> right now for keystore, in order to finish these drafts.  Then we (or
> some other WG) can immediately start to work on an update to
> crypto-types that would define more types for other purposes as well.

Maybe, depending on how that turns out, it may be trivial to extend the approach to cover everything.


Kent // contributor