Re: [radext] [netmod] Comment on draft-ietf-netmod-system-mgmt-05

[Andy Bierman <[e-mail]>]

....
>    container radius {
>      list server {
>        key name;
>        ordered-by user;
>
>        leaf name {
>          type string;  // arbitrary name
>        }
>        leaf address {
>          type inet:host;
>          mandatory true;
>        }
>        choice transport {
>          case udp {
>            container udp {
>              leaf authentication-port { ... }
>              leaf shared-secret { ... }
>            }
>          case tcp {
              if-feature radius-over-tcp;
>            container tcp {
>              leaf authentication-port { ... }
>              // RFC 6613 section 2.6.7 talks about config parameters
>              // maybe include them here?
>            }
>          }
>          case tls {
                if-feature radius-over-tls;
>              leaf port { ... }
>              // what else...?
>            }
>          }
>        }
>        ...
>      }
>
> Note that this is an extensible model; other transports can be added
> or augmented into this structure.
>

Re: features:
Doesn't the NETCONF server decide what transports it
can use, not the client?  So new cases need to be optional.

> One option could be to restructure like this but only actually define
> the udp case above, and leave the rest (tcp, tls, dtls) for future
> work.
>

Or just define the leafs you have here and leave
the rest for future work.

>
> /martin
>
>

Andy