Re: [Ssh] Re: draft charter

--------------KyamGFFJ15kpd5GVD1Vhz1RL
Content-Type: multipart/mixed; boundary="------------I77uIw6Vhvczclseetk1JmeO";
 protected-headers="v1"
From: Stephen Farrell <[email protected]>
To: [email protected], [email protected]
Message-ID: <[email protected]>
Subject: Re: [Ssh] Re: draft charter
References: <CAGgd1OfLCQS-ztVXuwV1Rg31SXp6jbxdqi-mB5S1eUG1Hz6LiQ@mail.gmail.com>
 <[email protected]>
In-Reply-To: <[email protected]>

--------------I77uIw6Vhvczclseetk1JmeO
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit


Hi again,

On 13/08/2024 23:38, Stephen Farrell wrote:
> 
> Meanwhile, comments on the draft charter, [1] as Deb said, would be
> good to get in the immediate future.

I got a request that the current draft charter text be sent to the
list itself, which seems like a good idea, so that's below.

Cheers,
S.

The main goal of the working group is to maintain the Secure Shell (SSH)
protocol. SSH provides support for secure remote login, file transfer,
and forwarding UNIX-domain sockets, TCP/IP and X11. It can automatically
encrypt, authenticate, and compress transmitted data.

At the time of writing this charter, it has been more than 17 years
since the previous Secure Shell WG has been closed and its documents
published. In the intervening years, current day implementations and
RFCs have diverged, although the (now closed) curdle WG and various AD-
sponsored RFCs have updated some of the SSH documentation, but in a
somewhat sporadic manner as there was no WG chartered to generally
maintain the SSH protocol documentation.

The initial goals of this new working group are:

     to update the RFCs documenting SSH to reflect what is implemented
and deployed in practice. In particular, the working group will document
the OpenSSH certificate structure, the SSH agent protocol, and SFTP, as
they are commonly implemented.

     to update and maintain the list of cryptographic algorithms used by
SSH. This includes documenting existing algorithms, deprecating unsafe
algorithms, selecting new algorithms (such as post-quantum), and
determining the set of recommended and mandatory-to-implement
algorithms. Updating IANA SSH registries and changing their registration
policies is in scope.

     while the development of formal verification proofs is out of scope,
this working group can respond to emerging proofs, and to security
issues found by formal verification tools. This can be done for example
by defining new extensions to improve the security of SSH.

This working group will strive for strong security, simplicity, and ease
of implementation. In particular, proposals should only be adopted if
there is evidence of significant existing deployment or broad interest
in new implementation and deployment. Protocol documents should not be
submitted to the IESG for publication before they have at least two
demonstrably interoperable implementations.

Out of scope initially includes:

     defining new certificate types or trust mechanisms;
     new transports for SSH;
     while defining how SSH uses cryptographic algorithms is in scope,
defining the algorithms themselves is out of scope.



--------------I77uIw6Vhvczclseetk1JmeO--

--------------KyamGFFJ15kpd5GVD1Vhz1RL
Content-Type: application/pgp-signature; name="OpenPGP_signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="OpenPGP_signature.asc"

-----BEGIN PGP SIGNATURE-----

wnsEABYIACMWIQQwbnhHy1kPJkWsM6fk2On5l6gz3QUCZrvoMAUDAAAAAAAKCRDk2On5l6gz3f23
AQChr2hFuWN8tfOjyWH60T8kZQuYhNxttA9CTHqCedxWKgEAzi4fp5ri6/cCbQDXNDgX5wdrtcNH
KfrFyIS7935qDQI=
=FWWN
-----END PGP SIGNATURE-----

--------------KyamGFFJ15kpd5GVD1Vhz1RL--