Re: [Isms] Comments about draft-ietf-isms-secshell-13, Section 5

[<Pasi.Eronen at nokia.com>]

Oops -- please ignore this one; I just found where the
tmStateReference is created (transport-security-model,
Section 4.2).

Best regards,
Pasi

> -----Original Message-----
> From: isms-bounces at ietf.org [mailto:isms-bounces at ietf.org] On
> Behalf Of Eronen Pasi (Nokia-NRC/Helsinki)
> Sent: 19 February, 2009 10:04
> To: ietfdbh at comcast.net; isms at ietf.org
> Subject: Re: [Isms] Comments about
> draft-ietf-isms-secshell-13, Section 5
>
> David Harrington wrote:
> >
> > Hi Pasi,
> >
> > Iam not certain that I have addressed all your issues.  Can you
> > please check the latest rev?  comments inline.
>
> The one thing that's still slightly unclear is how tmStateReference
> cache entry gets created on SSH client side (e.g. command originator).
>
> In particular, Section 5.2, step 1, seems to assume that it always
> gets a tmStateReference. But when the Dispatcher on e.g. command
> generator (acting as SSH client) calls sendMessage for the first
> time, it doesn't have a tmStateReference yet? (Or if it does have
> a tmStateReference, where did it come from?)
>
> My guess is that Section 5.2 should say that if tmStateReference is
> not present, steps 1..3 are skipped, and instead we create a
> tmStateReference cache entry (because we can't call openSession
> without having one) and go to step 4 (opening a new session).
>
> Best regards,
> Pasi
> _______________________________________________
> Isms mailing list
> Isms at ietf.org
> https://www.ietf.org/mailman/listinfo/isms
>