The Secure Shell (SSH) Session Channel Break Extension
RFC 4335

Note: This ballot was opened for revision 04 and is now closed.

(Sam Hartman; former steering group member) Yes

Yes ()
No email
send info

(Alex Zinin; former steering group member) No Objection

No Objection ()
No email
send info

(Allison Mankin; former steering group member) No Objection

No Objection (2005-09-01)
No email
send info
Clearly written.

A repeating typo that a spell-checker misses (though the RFC Ed will also
catch: preform in place of perform.

(Bert Wijnen; former steering group member) No Objection

No Objection ()
No email
send info

(Bill Fenner; former steering group member) No Objection

No Objection ()
No email
send info

(Brian Carpenter; former steering group member) (was Discuss) No Objection

No Objection (2005-08-31)
No email
send info
From review by Elwyn Davies:

s1: para 1: Add a reference to the SSH Connection protocol [5] after 'session channel'.
s3: Choose between 'break-length' (as in message format) and 'BREAK-length' (as in para 4).
s3: next to last para: (2 places) s/preformed/performed/

(David Kessens; former steering group member) No Objection

No Objection ()
No email
send info

(Jon Peterson; former steering group member) No Objection

No Objection ()
No email
send info

(Margaret Cullen; former steering group member) No Objection

No Objection ()
No email
send info

(Mark Townsley; former steering group member) No Objection

No Objection ()
No email
send info

(Russ Housley; former steering group member) No Objection

No Objection ()
No email
send info

(Scott Hollenbeck; former steering group member) No Objection

No Objection (2005-08-29)
No email
send info
A normative reference to SSH should really be included with this sentence fragment noted in Section 1:

"The Secure Shell (SSH) session channel"

maybe this?:

"The Secure Shell (SSH) [5] session channel"

(Ted Hardie; former steering group member) No Objection

No Objection ()
No email
send info