Re: [Isms] wg last call followup - sshtm openSession
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Isms] wg last call followup - sshtm openSession



Not sure if this is editorial, I suspect not.

sshtm openSession used to be

   openSession(
   IN   destTransportAddress     -- transport address to be used
   IN   tmSecurityName             -- on behalf of this principal
   IN   maxMessageSize           -- of the sending SNMP entity
    )

and is now

   openSession(
   IN   tmStateReference       -- transport information to be used
   OUT  tmStateReference       -- transport information to be used
   IN   maxMessageSize           -- of the sending SNMP entity
    )

Why the change? That OUT parameter looks strange to me.

Tom Petch

----- Original Message ----- 
From: "Juergen Schoenwaelder" <j.schoenwaelder at jacobs-university.de>
To: <isms at ietf.org>
Sent: Thursday, February 26, 2009 8:53 AM
Subject: [Isms] wg last call followup


> On November 4th 2008, I started WG last call on the ISMS document set:
> 
> [1] Transport Subsystem for the Simple Network Management Protocol (SNMP)
>     <draft-ietf-isms-tmsm-15.txt>
> [2] Transport Security Model for SNMP
>     <draft-ietf-isms-transport-security-model-10.txt>
> [3] Secure Shell Transport Model for SNMP
>     <draft-ietf-isms-secshell-13.txt>
> [4] Remote Authentication Dial-In User Service (RADIUS) Usage for Simple
>     Network Management Protocol (SNMP) Transport Models
>     <draft-ietf-isms-radius-usage-04.txt>
> 
> We received some comments and the subsequent mailing list discussions
> have led to some changes to the ISMS core documents. David just posted
> revised IDs of the core documents:
> 
> [1] Transport Subsystem for the Simple Network Management Protocol (SNMP)
>     <draft-ietf-isms-tmsm-16.txt>
> [2] Transport Security Model for SNMP
>     <draft-ietf-isms-transport-security-model-11.txt>
> [3] Secure Shell Transport Model for SNMP
>     <draft-ietf-isms-secshell-14.txt>


Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.