IETF-SSH archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
authors 48 hours: RFC 4250 <draft-ietf-secsh-assignednumbers-12.txt> NOW AVAILABLE (fwd)
Hi,
Here's what I intend to send to the RFC Editors. Please review and send
specific edits or comments to the list.
Thanks,
Chris
===
1)
Section 4.1.2, remove the following lines from the table
SSH_MSG_KEXDH_INIT 30 [SSH-TRANS]
SSH_MSG_KEXDH_REPLY 31 [SSH-TRANS]
2)
Section 4.3.4, first bullet after first paragraph
- remove a comma
OLD:
consistent with the proposed, local 'channel type'. It is assumed
^
NEW:
consistent with the proposed local 'channel type'. It is assumed
3)
Section 4.5
- replace the paragraph
OLD:
SSH_MSG_CHANNEL_REQUEST messages with a "pty-req" string MUST contain
"encoded terminal modes". These "encoded terminal modes" are
opcode-argument pairs consisting of an opcode and an argument.
NEW:
SSH_MSG_CHANNEL_REQUEST messages with a "pty-req" string MUST contain
'encoded terminal modes'. The 'encoded terminal modes' value is a
byte stream of opcode-argument pairs.
4)
Section 4.5.1, first paragraph
- replace the paragraph
OLD:
Protocol packets containing the SSH_MSG_CHANNEL_REQUEST message with
a "pty-req" string MUST contain "encoded terminal modes" with an
opcode of 1 byte. The opcode values are in the range of 1 to 255.
Opcodes 1 to 159 have a single uint32 argument. Opcodes 160 to 255
are not yet defined.
NEW:
Protocol packets containing the SSH_MSG_CHANNEL_REQUEST message with
a "pty-req" string MUST contain a 'encoded terminal modes' value.
The opcode values consist of a single byte and are in the range of 1
to 255. Opcodes 1 to 159 have a uint32 argument. Opcodes 160 to
255 are not yet defined.
5)
Section 4.5.2, first paragraph
- replace the paragraph
OLD:
The following table identifies the initial assignments of the opcode
and argument values that make up the "encoded terminal modes" values.
NEW:
The following table identifies the initial assignments of the opcode
values that are used in the 'encoded terminal modes' value.
6)
Section 4.5.2, table
- replace the table header
OLD:
opcode argument description
^^^^^^^^
NEW:
opcode mnemonic description
7)
Section 4.5.2, table
- reinstate deleted text
OLD:
52 XCASE Enable input and output of uppercase
characters by preceding their lowercase
equivalents with "
NEW:
52 XCASE Enable input and output of uppercase
characters by preceding their lowercase
equivalents with "\".
^^^
8)
Section 4.6.1, first paragraph
- add a clause
OLD:
at-sign ("@"), a comma (","), whitespace, or control characters
^^^
(ASCII codes 32 or less). Names are case-sensitive, and MUST NOT
NEW:
at-sign ("@"), a comma (","), whitespace, control characters
(ASCII codes 32 or less), or the ASCII code 127 (DEL). Names are
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
case-sensitive, and MUST NOT ...
9)
Section 4.6.1, third paragraph
- replace the paragraph
OLD:
Names with the at-sign in them will have the format of
"name@domainname" (without the double quotes) where the part
preceding the at-sign is the name. The format of the part preceding
the at-sign is not specified; however, these names MUST be printable
US-ASCII strings, and MUST NOT contain the comma character (","),
whitespace, or control characters (ASCII codes 32 or less). The part
following the at-sign MUST be a valid, fully qualified internet
domain name [RFC1034] controlled by the person or organization
defining the name. Names are case-sensitive, and MUST NOT be longer
than 64 characters. It is up to each domain how it manages its local
namespace. It has been noted that these names resemble STD 11
[RFC0822] email addresses. This is purely coincidental and has
nothing to do with STD 11 [RFC0822]. An example of a locally defined
name is "ourcipher-cbc%example.com@localhost" (without the double quotes).
NEW:
Names with the at-sign in them will have the format of
"name@domainname" (without the double quotes) where the part
preceding the at-sign is the name. The format of the part preceding
the at-sign is not specified; however, these names MUST be printable
US-ASCII strings, and MUST NOT contain the comma character (","),
whitespace, control characters (ASCII codes 32 or less), or the ASCII
code 127 (DEL). They MUST have only a single at-sign in them. The
part
following the at-sign MUST be a valid, fully qualified internet
domain name [RFC1034] controlled by the person or organization
defining the name. Names are case-sensitive, and MUST NOT be longer
than 64 characters. It is up to each domain how it manages its local
namespace. It has been noted that these names resemble STD 11
[RFC0822] email addresses. This is purely coincidental and has
nothing to do with STD 11 [RFC0822]. An example of a locally defined
name is "ourcipher-cbc%example.com@localhost" (without the double quotes).
10)
Section 4.6.2, first paragraph
- change the case of Name
OLD:
Requests for assignments of new Names MUST be done through the IETF
^
NEW:
Requests for assignments of new names MUST be done through the IETF
11)
Section 4.7, first paragraph
- replace the paragraph
OLD:
The Service Name is used to describe a protocol layer. The following
table lists the initial assignments of the Service Names.
NEW:
The 'service name' is used to describe a protocol layer. The following
table lists the initial assignments of the 'service name' values.
12)
Section 4.9.5
- substitute "to" for "of"
OLD:
There are no initial assignments of the Connection Protocol Subsystem
^^
NEW:
There are no initial assignments to the Connection Protocol Subsystem
^^
13)
Section 4.10, first paragraph
- quote a value
OLD:
diffie-hellman-group14-sha1 for the name of the second defined group.
NEW:
"diffie-hellman-group14-sha1" for the name of the second defined group.
^ ^
14)
Section 4.10, second paragraph
- remove a dash
OLD:
The following table identifies the initial assignments of the key-
^
NEW:
The following table identifies the initial assignments of the key
15)
Section 4.11.1, FIPS-46-3 reference
- insert a dash
OLD:
des-cbc [FIPS-46-3] HISTORIC; See
page 4 of [FIPS 46-3]
^
NEW:
des-cbc [FIPS-46-3] HISTORIC; See
page 4 of [FIPS-46-3]
16)
Section 6.2, FIPS-46-3 reference
- modify the reference to FIPS-46-3
OLD:
[FIPS-46-3] National Institute of Standards and Technology, "Data
NEW:
[FIPS-46-3] US National Institute of Standards and Technology,
^^
===
---------- Forwarded message ----------
Date: Wed, 26 Oct 2005 16:09:38 -0700
From: RFC Editor <rfc-editor%rfc-editor.org@localhost>
To: sjl%ssh.com@localhost, clonvick%cisco.com@localhost
Cc: RFC Editor <rfc-editor%rfc-editor.org@localhost>, Russ Housley <housley%vigilsec.com@localhost>,
Sam Hartman <hartmans-ietf%mit.edu@localhost>, sommerfeld%sun.com@localhost
Subject: authors 48 hours: RFC 4250 <draft-ietf-secsh-assignednumbers-12.txt>
NOW AVAILABLE
****IMPORTANT*****
Updated 2005/10/26
RFC AUTHOR(S):
--------------
This is your LAST CHANCE to make changes to your RFC to be:
draft-ietf-secsh-assignednumbers-12.txt, once the document is
published as an RFC we *WILL NOT* make any changes.
Please check your document at
ftp://ftp.rfc-editor.org/in-notes/authors/rfc4250.txt
ATTENTION: The editing process occasionally introduces errors that
were not in the Internet Draft. Although the RFC Editor tries very
hard to catch all errors, proofreading the text at least twice, typos
can slip through. You, as an author of the RFC, are taking
responsibility for the correctness of the final product when you OK
publication. You should therefore proofread the entire RFC carefully
and without assumptions. Errors in RFCs last forever.
NOTE: We have run a diff tool that compares the approved internet-draft
against our edited RFC version of the document. Please review this
file at:
ftp://ftp.rfc-editor.org/in-notes/authors/rfc4250-diff.html
The document will NOT BE PUBLISHED until ALL of the authors listed in
the RFC have affirmed that the document is ready to be
published, as ALL of the authors are equally responsible for verifying
the documents readiness for publication.
** Please send us a list of suitable keywords for this document, over
and above those which appear in the title.
Frequently INCORRECT information includes
- Contact Information
- References (are they up to date)
- Section Numbers
(especially if you originally put the copyright somewhere
other than the VERY end of the document, or if you numbered
the "Status of the Memo" field)
Please send us the changes, *DO NOT* send a new document with the
changes made. (If we think that the changes might be more than
editorial we will contact the AD or the IESG to confirm that the
changes do not require review.)
Send us the changes in THIS format.
1)*** SECTION #'s*** [i.e. Section 5, 2nd paragraph]
2) the text you want changed,
3) the new correct text and
4) if the changes are spacing or indentation than please note
that.
FOR EXAMPLE:
Section 5.6, 3rd paragraph
OLD:
The quick brown fox jumped over the lazy dog.
NEW:
The quick brown dog jumps over the lazy fox.
^^^ ^ ^^^
If you have a whole paragraph to replace you do not need to use
the arrow to point out the differences
INTRODUCTION, 2nd paragraph
Replace OLD:
alsdfja;sldjf;lajsd;fljas;dlfj;
With NEW:
nv;alkjd;lsf;aoisj;ltjka;sldkjf
Spacing or indentation problems...
Section 10, 1st paragraph (remove spaces between bit
and of, add space after butter)
OLD:
Better botter bought a bit
of bitter butterMary mary quite contrary
NEW:
Better botter bought a bit of bitter butter
Mary mary quite contrary
This document will NOT be published until we receive agreement, from
ALL listed authors, that the document is ready for publication.
Thanks for your cooperation,
-RFC Editor
Home |
Main Index |
Thread Index |
Old Index