What I think essential is an expanatory paragraph, much earlier, in tmsm
even (thinking that another transport model might find a use for this)
saying eg
"The transportAddress, as passed by the application may take the form
user at example.com:port
The 'user' part may be used to establish a transport and then be used by
the remote engine as securityName. The local engine still uses
securityName as well and so has two names, one of which is used somewhere
and the other elsewhere making this specification hard to understand,
dysfunctional even. This capability meets no known requirement but there
is a good reason for it being present".
Well, you might find a better pair of the last two sentences but after
expending so much effort, I am a tad frustrated at my lack of
understanding:-). I really would like to understand why we introduced
this and how it works. My current focus is on a Command Generator as ssh
client and the processing of outbound Request and inbound Response;
forget about Command Responders and Notification engines for the moment.
