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

MIME-Version: 1.0
Content-Type: multipart/mixed; boundary=15efe2c35aaaf0f296dfeefe60f9c2e3
--15efe2c35aaaf0f296dfeefe60f9c2e3
Content-Type: text/plain
Content-Transfer-Encoding: 8bit

A new Request for Comments is now available in online RFC libraries.

        RFC 4335

        Title:      The Secure Shell SSH Session 
                    Channel Break Extension 
        Author:     J. Galbraith,  P. Remaker
        Status:     Standards Track
        Date:       January 2006
        Mailbox:    galb-list@vandyke.com, 
                    remaker@cisco.com
        Pages:      6
        Characters: 11370
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-secsh-break-04.txt

        URL:        http://www.rfc-editor.org/rfc/rfc4335.txt

The Session Channel Break Extension provides a means to send a BREAK
signal over a Secure Shell (SSH) terminal session.  [STANDARDS TRACK]

This document is a product of the Secure Shell Working Group of the IETF.

This is now a Proposed Standard Protocol.

This document specifies an Internet standards track protocol for the
Internet community, and requests discussion and suggestions for
improvements.  Please refer to the current edition of the \"Internet
Official Protocol Standards\" (STD 1) for the standardization state
and status of this protocol.  Distribution of this memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 

help: ways_to_get_rfcs. For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.

Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

...

--15efe2c35aaaf0f296dfeefe60f9c2e3