"Sharp Close": Elimination of TIME-WAIT state of TCP connections
draft-kitamura-tcp-sharp-close-02
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Hiroshi Kitamura , Shingo Ata , Masayuki Murata | ||
| Last updated | 2016-04-17 (Latest revision 2015-10-15) | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This document describes an idea "Sharp Close" that eliminates or minimizes TIME-WAIT state of TCP connections. In the current TCP specification ([RFC0793]), there are some inappropriate or not up-to-date functions. Here we focus and discuss on TCP TIME-WAIT state function. TIME-WAIT is the last state of TCP connections of Active Close side nodes. After TCP connections are effectively closed, state of them move to TIME-WAIT state. After TIME-WAIT state is finished, resources of connections are released. This means that even if connections are effectively finished, resources of connections are NOT released. The TIME-WAIT state prevents from releasing them. From the viewpoints of current high-speed and high-multiplicity communication styles, it is thought that TIME-WAIT state is one of evil functions. In order to provide efficient communications that match current styles, an idea "Sharp Close" that eliminates or minimizes TIME- WAIT state of TCP connections is proposed.
Authors
Hiroshi Kitamura
Shingo Ata
Masayuki Murata
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)