draft-ietf-secsh-break-01.txt   draft-ietf-secsh-break-02.txt 
Secure Shell Working Group J. Galbraith Secure Shell Working Group J. Galbraith
Internet-Draft VanDyke Software Internet-Draft VanDyke Software
Expires: February 17, 2004 P. Remaker Expires: October 18, 2004 P. Remaker
Cisco Systems, Inc Cisco Systems, Inc
August 19, 2003 April 19, 2004
Session Channel Break Extension Session Channel Break Extension
draft-ietf-secsh-break-01.txt draft-ietf-secsh-break-02.txt
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC2026. all provisions of Section 10 of RFC2026.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that other Task Force (IETF), its areas, and its working groups. Note that other
groups may also distribute working documents as Internet-Drafts. groups may also distribute working documents as Internet-Drafts.
skipping to change at page 1, line 32 skipping to change at page 1, line 32
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at http:// The list of current Internet-Drafts can be accessed at http://
www.ietf.org/ietf/1id-abstracts.txt. www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on February 17, 2004. This Internet-Draft will expire on October 18, 2004.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2003). All Rights Reserved. Copyright (C) The Internet Society (2004). All Rights Reserved.
Abstract Abstract
The Session Channel Break Extension provides a means to send a BREAK The Session Channel Break Extension provides a means to send a BREAK
signal [2] over an SSH terminal session [5]. signal [2] over an SSH terminal session [5].
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. The Break Request . . . . . . . . . . . . . . . . . . . . . . . 4 2. The Break Request . . . . . . . . . . . . . . . . . . . . . . 4
3. Security Considerations . . . . . . . . . . . . . . . . . . . . 6 3. Security Considerations . . . . . . . . . . . . . . . . . . . 6
Normative References . . . . . . . . . . . . . . . . . . . . . . 7 4. References . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Informative References . . . . . . . . . . . . . . . . . . . . . 8 4.1 Normative References . . . . . . . . . . . . . . . . . . . . 7
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 8 4.2 Informative References . . . . . . . . . . . . . . . . . . . 7
Intellectual Property and Copyright Statements . . . . . . . . . 9 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 7
Intellectual Property and Copyright Statements . . . . . . . . 8
1. Introduction 1. Introduction
The SSH session channel provides a mechanism for the client-user to The SSH session channel provides a mechanism for the client-user to
interactively enter commands and receive output from a remote host interactively enter commands and receive output from a remote host
while taking advantage of the SSH transport's privacy and integrity while taking advantage of the SSH transport's privacy and integrity
features. SSH is increasingly being used to replace telnet for features. SSH is increasingly being used to replace telnet for
terminal access applications. terminal access applications.
A common application of the telnet protocol is the "Console Server" A common application of the telnet protocol is the "Console Server"
skipping to change at page 7, line 5 skipping to change at page 7, line 5
BREAK-enabled ports are limited to users with appropriate priviliges BREAK-enabled ports are limited to users with appropriate priviliges
to execute such functions. Alternatively, support for the BREAK to execute such functions. Alternatively, support for the BREAK
facility MAY be imlemented configurable or a per port or per server facility MAY be imlemented configurable or a per port or per server
basis. basis.
Implementations that literally intepret the BREAK length parameter Implementations that literally intepret the BREAK length parameter
without imposing the suggested BREAK time limit may cause a denial without imposing the suggested BREAK time limit may cause a denial
of service to or unexpected results from attached devices receiving of service to or unexpected results from attached devices receiving
the very long BREAK signal. the very long BREAK signal.
Normative References 4. References
4.1 Normative References
[1] Postel, J. and J. Reynolds, "Telnet Protocol Specification", STD [1] Postel, J. and J. Reynolds, "Telnet Protocol Specification", STD
8, RFC 854, May 1983. 8, RFC 854, May 1983.
Informative References 4.2 Informative References
[2] Harris, D., "Greater Scroll of Console Knowledge", April 2003. [2] Harris, D., "Greater Scroll of Console Knowledge", March 2004.
[3] Rinne, T., Ylonen, T., Kivinen, T. and S. Lehtinen, "SSH [3] Rinne, T., Ylonen, T., Kivinen, T. and S. Lehtinen, "SSH
Protocol Architecture", draft-ietf-secsh-architecture-14 (work Protocol Architecture", draft-ietf-secsh-architecture-15 (work
in progress), July 2003. in progress), October 2003.
[4] Rinne, T., Ylonen, T., Kivinen, T., Saarinen, M. and S. [4] Rinne, T., Ylonen, T., Kivinen, T., Saarinen, M. and S.
Lehtinen, "SSH Transport Layer Protocol", Lehtinen, "SSH Transport Layer Protocol",
draft-ietf-secsh-transport-16 (work in progress), July 2003. draft-ietf-secsh-transport-17 (work in progress), October 2003.
[5] Rinne, T., Ylonen, T., Kivinen, T. and S. Lehtinen, "SSH [5] Rinne, T., Ylonen, T., Kivinen, T. and S. Lehtinen, "SSH
Connection Protocol", draft-ietf-secsh-connect-17 (work in Connection Protocol", draft-ietf-secsh-connect-18 (work in
progress), July 2003. progress), October 2003.
Authors' Addresses Authors' Addresses
Joseph Galbraith Joseph Galbraith
VanDyke Software VanDyke Software
4848 Tramway Ridge Blvd 4848 Tramway Ridge Blvd
Suite 101 Suite 101
Albuquerque, NM 87111 Albuquerque, NM 87111
US US
Phone: +1 505 332 5700 Phone: +1 505 332 5700
EMail: galb-list@vandyke.com EMail: galb-list@vandyke.com
Phillip Remaker Phillip Remaker
Cisco Systems, Inc Cisco Systems, Inc
170 West Tasman Drive 170 West Tasman Drive
San Jose, CA 95120 San Jose, CA 95120
US US
Phone: +1 408 526 8614
EMail: remaker@cisco.com EMail: remaker@cisco.com
Intellectual Property Statement Intellectual Property Statement
The IETF takes no position regarding the validity or scope of any The IETF takes no position regarding the validity or scope of any
intellectual property or other rights that might be claimed to intellectual property or other rights that might be claimed to
pertain to the implementation or use of the technology described in pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights this document or the extent to which any license under such rights
might or might not be available; neither does it represent that it might or might not be available; neither does it represent that it
has made any effort to identify any such rights. Information on the has made any effort to identify any such rights. Information on the
skipping to change at page 9, line 29 skipping to change at page 8, line 29
be obtained from the IETF Secretariat. be obtained from the IETF Secretariat.
The IETF invites any interested party to bring to its attention any The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary copyrights, patents or patent applications, or other proprietary
rights which may cover technology that may be required to practice rights which may cover technology that may be required to practice
this standard. Please address the information to the IETF Executive this standard. Please address the information to the IETF Executive
Director. Director.
Full Copyright Statement Full Copyright Statement
Copyright (C) The Internet Society (2003). All Rights Reserved. Copyright (C) The Internet Society (2004). All Rights Reserved.
This document and translations of it may be copied and furnished to This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph are kind, provided that the above copyright notice and this paragraph are
included on all such copies and derivative works. However, this included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing document itself may not be modified in any way, such as by removing
the copyright notice or references to the Internet Society or other the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of Internet organizations, except as needed for the purpose of
skipping to change at page 10, line 7 skipping to change at page 9, line 7
The limited permissions granted above are perpetual and will not be The limited permissions granted above are perpetual and will not be
revoked by the Internet Society or its successors or assignees. revoked by the Internet Society or its successors or assignees.
This document and the information contained herein is provided on an This document and the information contained herein is provided on an
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Acknowledgement Acknowledgment
Funding for the RFC Editor function is currently provided by the Funding for the RFC Editor function is currently provided by the
Internet Society. Internet Society.
 End of changes. 

This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/