Comment on drafts in last call

[<jml%ssh.com@localhost>]

Regarding the Secure Shell I-D's presently in WG Last Call:

The name "SSH" is, and always has been, a major identifier of SSH
Communications Security Corp. To protect the identifier in commercial
settings, we have obtained trademark registration for the name in the
United States, Europe, and Japan.

The Secure Shell protocol has often been referred to with the name
"SSH". This has not always been a source of confusion, as until some
time ago we were the only major source of products associated with the
Secure Shell protocol.  Another reason adding to the confusion is that
the user base of Secure Shell products has only recently grown well
outside the group of early adopters who know the technology and the
field.

Presently, with the user base continually growing, the confusion of
the protocol and a major participant in the field is real and
increasing.  We note that the confusion affects all producers of
Secure Shell products - we often get the blame as well as the praise
for products made by others. This is not a benefit for anyone.

Official names in standard documents have a large influence on the
usage of terms in everyday practice.  Therefore, we present the wish
that the IETF would not elect to support the present situation and the
continuing increase in the confusion.  We note that RFC 2026, section
10.1, states that

   In all matters of intellectual property rights and procedures, the
   intention is to benefit the Internet community and the public at
   large, while respecting the legitimate rights of others.

To minimize the confusion and to reach the objectives of that section, we
propose that the official name of the protocol - which is defined by the
titles of the corresponding Internet Drafts - be changed to refer to
"Secure Shell".



Markus Levlin
Intellectual Property Rights Manager
SSH Communications Security Corp