[netconf] why did we breakout the groupings?

[Kent Watsen <[e-mail]>]

Hi Balazs,

I'm in the middle of answering your other question when I was reminded that I've been meaning to follow up with you on this issue...

Can you please help me recall why several months back we made the decision to redefine the ietf-ssh-[client/server]-grouping statements to use other groupings?  For instance, here's the current definition:

    grouping ssh-client-grouping {
       uses client-identity-grouping;
       uses server-auth-grouping;
       uses transport-params-grouping;
       uses keepalives-grouping;
     }

Obviously it was because you (I think it was you) wanted to be able to "use" the inner grouping in another context, but why?

I ask because this strategy is percolating into all of the client/server models and it seems weird, if not wrong.  I currently have it as an "open issue" in my presentation for Monday, but I'd rather resolve it offline/now if possible.

Kent // contributor