Re: [Isms] secshell-pre14 - minor issues

["David Harrington" <ietfdbh at comcast.net>]

> -----Original Message-----
> From: dave.shield at googlemail.com 
> [mailto:dave.shield at googlemail.com] On Behalf Of Dave Shield
> Sent: Friday, February 06, 2009 6:02 AM
> To: j.schoenwaelder at jacobs-university.de; David Harrington
> Cc: isms at ietf.org
> Subject: Re: [Isms] secshell-pre14 - minor issues
> 
> 2009/1/23 Juergen Schoenwaelder 
> <j.schoenwaelder at jacobs-university.de>:
> > On Thu, Jan 22, 2009 at 03:42:22PM -0500, David Harrington wrote:
> >
> >> This is an updated draft for secshell.
> 
> > Can the WG members please review the changes?
> 
> A few minor nits which seem to be still present:
> 
> Section 3.1.1 2.
>   The references to RFC4253 (para 2) and RFC4252 (para 3) are
enclosed
> in both round and square brackets.   All other references 
> throughout the
> document use square brackets only.
> 
>    s/([RFC4252])/[4252]/
>    s/([RFC4253])/[4253]/

fixed.

> 
> 
> Section 5
>   Para 3 of the introduction includes
>    ".... for the returned OID and value contextEngineID would 
> be set ..."
> 
>   Insert a comma after "value".
fixed.

> 
> 
> Section 5.3
>    step 3 states
>       "If the attempt to establish a connection is unsuccessful, or
>        server authentication fails, then sshtmSessionOpenErrors is
>        incremented... and openProcessing stops."
>    This is the only time that sshtmSessionOpenErrors is mentioned.
> 
> 
>   The definition of the sshtmSessionOpenErrors MIB object states
>       "The number of times an openSession() request
>        failed to open a session as a SSH client,
>        for any reason."     <======
> 
>    "For any reason" is wrong.
> 
fixed, I hope.

> 
> 
> 
> 
> Dave
>