Re: [Isms] wg last call followup - tsm

["tom.petch" <cfinss at dial.pipex.com>]

Editorial

TSM s3.1.2 uses REQUIRES, an excellent word, one I use myself, but which does
not appear in RFC2119.  Is this a problem?  If so, I suggest inverting the
sentence from

" The Transport Security Model REQUIRES that the security parameters
   used for a response are the same as those used for the corresponding
   request.  "
to
 "For the Transport Security Model, the security parameters used for a
  response MUST be the same as those used for the corresponding
  request.  "

4.2 2)  SSHTM requires a value for tmSameSecurity in the cache else processing
stops 5.2 1).  Here, 4.2 1) specifies the setting of tmSameSecurity to true so
for clarity, I think that 4.2 2) should specify the setting of tmSameSecurity to
false.

4.2 indentation changes half way through, I am unclear why.

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>
>
> Please take a look at the changes. Let us know by March 6th if there
> are any major technical problems with the changes that must be fixed
> before submitting the documents to the AD for publication.  Please
> keep in mind that we are going for Proposed Standard, the entry-level
> maturity level for the standards track.
>
> If you find editorial issues, please report them clearly marked as
> editorial issues.
>