[netconf] RFC 9644 on YANG Groupings for SSH Clients and SSH Servers

rfc-editor@rfc-editor.org Fri, 11 October 2024 01:12 UTC

Return-Path: <wwwrun@rfcpa.rfc-editor.org>
X-Original-To: netconf@ietf.org
Delivered-To: netconf@ietfa.amsl.com
Received: from rfcpa.rfc-editor.org (unknown [167.172.21.234]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 337BEC151996; Thu, 10 Oct 2024 18:12:55 -0700 (PDT)
Received: by rfcpa.rfc-editor.org (Postfix, from userid 461) id 7AE263B87A; Thu, 10 Oct 2024 18:12:54 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20241011011254.7AE263B87A@rfcpa.rfc-editor.org>
Date: Thu, 10 Oct 2024 18:12:54 -0700
Message-ID-Hash: 7YJGF2UK7KFGM7KLPIGG56HB4QP5JDH3
X-Message-ID-Hash: 7YJGF2UK7KFGM7KLPIGG56HB4QP5JDH3
X-MailFrom: wwwrun@rfcpa.rfc-editor.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-netconf.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, netconf@ietf.org
X-Mailman-Version: 3.3.9rc5
Precedence: list
Subject: [netconf] RFC 9644 on YANG Groupings for SSH Clients and SSH Servers
List-Id: NETCONF WG list <netconf.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/XqchtUdzBikqQ_F_rZm0raEfP5k>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netconf>
List-Help: <mailto:netconf-request@ietf.org?subject=help>
List-Owner: <mailto:netconf-owner@ietf.org>
List-Post: <mailto:netconf@ietf.org>
List-Subscribe: <mailto:netconf-join@ietf.org>
List-Unsubscribe: <mailto:netconf-leave@ietf.org>

A new Request for Comments is now available in online RFC libraries.

        
        RFC 9644

        Title:      YANG Groupings for SSH Clients 
                    and SSH Servers 
        Author:     K. Watsen
        Status:     Standards Track
        Stream:     IETF
        Date:       October 2024
        Mailbox:    kent+ietf@watsen.net
        Pages:      64
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-netconf-ssh-client-server-40.txt

        URL:        https://www.rfc-editor.org/info/rfc9644

        DOI:        10.17487/RFC9644

This document presents three IETF-defined YANG modules and a script
used to create four supporting IANA modules.

The three IETF modules are ietf-ssh-common, ietf-ssh-client, and
ietf-ssh-server.  The "ietf-ssh-client" and "ietf-ssh-server" modules
are the primary productions of this work, supporting the
configuration and monitoring of Secure Shell (SSH) clients and
servers.

The four IANA modules are iana-ssh-encryption-algs,
iana-ssh-key-exchange-algs, iana-ssh-mac-algs, and
iana-ssh-public-key-algs.  These modules each define YANG
enumerations providing support for an IANA-maintained algorithm
registry.

This document is a product of the Network Configuration Working Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  Distribution of this 
memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC