The Secure Shell (SSH) Session Channel Break Extension
draft-ietf-secsh-break-04
Yes
(Sam Hartman)
No Objection
(Alex Zinin)
(Bert Wijnen)
(Bill Fenner)
(David Kessens)
(Jon Peterson)
(Margaret Cullen)
(Mark Townsley)
(Russ Housley)
(Ted Hardie)
Note: This ballot was opened for revision 04 and is now closed.
Sam Hartman Former IESG member
Yes
Yes
()
Unknown
Alex Zinin Former IESG member
No Objection
No Objection
()
Unknown
Allison Mankin Former IESG member
No Objection
No Objection
(2005-09-01)
Unknown
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 IESG member
No Objection
No Objection
()
Unknown
Bill Fenner Former IESG member
No Objection
No Objection
()
Unknown
Brian Carpenter Former IESG member
(was Discuss)
No Objection
No Objection
(2005-08-31)
Unknown
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 IESG member
No Objection
No Objection
()
Unknown
Jon Peterson Former IESG member
No Objection
No Objection
()
Unknown
Margaret Cullen Former IESG member
No Objection
No Objection
()
Unknown
Mark Townsley Former IESG member
No Objection
No Objection
()
Unknown
Russ Housley Former IESG member
No Objection
No Objection
()
Unknown
Scott Hollenbeck Former IESG member
No Objection
No Objection
(2005-08-29)
Unknown
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 IESG member
No Objection
No Objection
()
Unknown