Re: [netconf] I-D Action: draft-ietf-netconf-ssh-client-server-32.txt

[Kent Watsen <[e-mail]>]

Hi Tom,

> On Feb 23, 2023, at 6:50 AM, tom petch <[e-mail]> wrote:
> 
> From: Kent Watsen <[e-mail]>
> Sent: 29 January 2023 02:24
> 
> <inline under <tp> >

Whittling down to just the open items...



>>        Note that this grouping uses fairly typical descendant
>>         node names such that a stack of 'uses' statements will
>> suggest nest rather than stack.
> 
> I used "nesting" - okay?
> 
> <tp>
> Yes fine
> </tp>

Thanks.



>>            list host-key {
>> RFC4251 might be a better reference for host keys
> 
> I don't understand this comment.
> <tp>
> This is  a list of host key and that is part of the SSH architecture defined in 4251.  The KEXINIT message is defined in 4253 but that for me is not as relevant as the explanation of what a host key and how it is crucial to SSH
> </tp>

Added RFC 4251 as a reference.



>>               "The 'user name' for the SSH client, as defined in
>>                 the SSH_MSG_USERAUTH_REQUEST message in RFC 4253.";
>> RFC4252 not RFC4253
> 
> What?   I got it right...
> 
> <tp>
> Again this is about authentication and that is explained in RFC4252.  The message is listed in 4253 but I see that as less relevant than the issue of authentication which is covered in RFC4252
> 
> Tom Petch
> 
> </tp>

Added a reference to RFC 4252.


K.