Movatterモバイル変換


[0]ホーム

URL:


Search RFCs

Advanced Search

RFC Editor

RFC 6093

On the Implementation of the TCP Urgent Mechanism,January 2011

File formats:
icon for text fileicon for PDFicon for HTML
Status:
PROPOSED STANDARD
Obsoleted by:
RFC 9293
Updates:
RFC 793,RFC 1011,RFC 1122
Authors:
F. Gont
A. Yourtchenko
Stream:
IETF
Source:
tcpm (wit)

Cite this RFC:TXT  | XML  |  BibTeX

DOI:  https://doi.org/10.17487/RFC6093

Discuss this RFC: Send questions or comments to the mailing listtcpm@ietf.org

Other actions:View Errata  | Submit Errata  | Find IPR Disclosures from the IETF  | View History of RFC 6093


Abstract

This document analyzes how current TCP implementations process TCPurgent indications and how the behavior of some widely deployedmiddleboxes affects how end systems process urgent indications.This document updates the relevant specifications such thatthey accommodate current practice in processing TCP urgentindications, raises awareness about the reliability of TCP urgentindications in the Internet, and recommends against the use of urgentindications (but provides advice to applications that do). [STANDARDS-TRACK]


For the definition ofStatus,seeRFC 2026.

For the definition ofStream, seeRFC 8729.




IABIANAIETFIRTFISEISOCIETF Trust
ReportsPrivacy StatementSite MapContact Us

Advanced Search

[8]ページ先頭

©2009-2025 Movatter.jp