Re: NETCONF over TLS

[Phil Shafer <phil@juniper.net>]

Eliot Lear writes:
>This is where BEEP does its thing.  You do both TLS *and* SASL, and 
>voila: you can mix and match, even, based on deployment needs.

Can we hear from folks with experience with netconf/beep?  I was
an early advocate for beep, but our experience was fairly negative.

For us, the quality of the freely-available implementations, as
well as issues with the spec, were seen as trouble, but the bigger
issue was just the complexity.  Yes, you can read a (decoded) beep
session, but do developers understand what they are looking at
without smoke pouring from their ears?

Thanks,
 Phil

--
to unsubscribe send a message to netconf-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://ops.ietf.org/lists/netconf/>