Re: [Isms] TBD secshell
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Isms] TBD secshell
>>>>> On Mon, 9 Feb 2009 23:19:25 -0500, "David B Harrington" <dbharrington at comcast.net> said:
DBH> I just sent out updates to all three documents.
DBH> This problem is not addressed.
DBH> Can you tell me how to change the text?
DBH> I am not sure I understand the edits.
Sure. The only thing that needs to be added, IMHO, is a note saying the
address should be consistent during the life of a session. i.e.:
5.1. Procedures for an Incoming Message
1. The SSH Transport Model queries the SSH engine, in an
implementation-dependent manner, to determine the
transportAddress, the principal name authenticated by SSH, and a
session identifier. {+The transportAddress must be consistent
during the life of a SSH session.+}
... jump to text after bullet 2 of 5.1 ...
Prepare the transport parameters for the ASI:
transportDomain = snmpSSHDomain
transportAddress = the address {+of the SSH session that+} the message
originated from, determined in an implementation-dependent way
... jump to bullet 2 of section 5.3 ...
2. Using tmTransportAddress, the client will establish an SSH
transport connection using the SSH transport protocol,
authenticate the server, and exchange keys for message integrity
and encryption. {+The transportAddress associated with a session
MUST remain constant during the lifetime of the SSH session.
Implementations may need to cache the transportAddress passed to
the openSession API for later use when performing incoming
message processing (see section Section 5.1).+}
--
Wes Hardaker
Sparta, Inc.
Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.