Re: [netconf] Murray Kucherawy's Discuss on draft-ietf-netconf-ssh-client-server-38: (with DISCUSS and COMMENT)

[Kent Watsen <[e-mail]>]

Hi Murray,

Thank you for your comments.
Responses below.

Kent // author


> On Feb 29, 2024, at 9:37 AM, Murray Kucherawy via Datatracker <[e-mail]> wrote:
> 
> Murray Kucherawy has entered the following ballot position for
> draft-ietf-netconf-ssh-client-server-38: Discuss
> 
> When responding, please keep the subject line intact and reply to all
> email addresses included in the To and CC lines. (Feel free to cut this
> introductory paragraph, however.)
> 
> 
> Please refer to https://www.ietf.org/about/groups/iesg/statements/handling-ballot-positions/ 
> for more information about how to handle DISCUSS and COMMENT positions.
> 
> 
> The document, along with other ballot positions, can be found here:
> https://datatracker.ietf.org/doc/draft-ietf-netconf-ssh-client-server/
> 
> 
> 
> ----------------------------------------------------------------------
> DISCUSS:
> ----------------------------------------------------------------------
> 
> BCP 81 says the registration contact has to be the IESG for things developed by
> the IETF.  Why do some of them list IANA as the contact?

Per my previous response, I have switched the contact to "The IESG” in my local copy.

I made the change for both this draft and also the tls-client-server draft.


> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
> 
> From Orie Steele, incoming ART Area Director:
> 
> Regarding Section 6.3 (Considerations for the "iana-ssh-encryption-algs" Module):
> 
> Does IANA accept the python script and the manual revision statement process that is required?

Amanda (IANA) responded separately stating that it’s okay.


Thanks again,
Kent