RFC 6093 on On the Implementation of the TCP Urgent Mechanism
rfc-editor@rfc-editor.org Tue, 04 January 2011 19:18 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@core3.amsl.com
Delivered-To: ietf-announce@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 27DD93A6CD9; Tue, 4 Jan 2011 11:18:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.007
X-Spam-Level:
X-Spam-Status: No, score=-102.007 tagged_above=-999 required=5 tests=[AWL=-0.007, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fL2U9dmtefhx; Tue, 4 Jan 2011 11:18:09 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by core3.amsl.com (Postfix) with ESMTP id 63CDE3A6BDB; Tue, 4 Jan 2011 11:18:09 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id C142EE071A; Tue, 4 Jan 2011 11:20:16 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 6093 on On the Implementation of the TCP Urgent Mechanism
From: rfc-editor@rfc-editor.org
Message-Id: <20110104192016.C142EE071A@rfc-editor.org>
Date: Tue, 04 Jan 2011 11:20:16 -0800
Cc: tcpm@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Jan 2011 19:18:10 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 6093
Title: On the Implementation of the
TCP Urgent Mechanism
Author: F. Gont, A. Yourtchenko
Status: Standards Track
Stream: IETF
Date: January 2011
Mailbox: fernando@gont.com.ar,
ayourtch@cisco.com
Pages: 12
Characters: 25921
Updates: RFC793, RFC1011, RFC1122
I-D Tag: draft-ietf-tcpm-urgent-data-07.txt
URL: http://www.rfc-editor.org/rfc/rfc6093.txt
This document analyzes how current TCP implementations process TCP
urgent indications and how the behavior of some widely deployed
middleboxes affects how end systems process urgent indications.
This document updates the relevant specifications such that
they accommodate current practice in processing TCP urgent
indications, raises awareness about the reliability of TCP urgent
indications in the Internet, and recommends against the use of urgent
indications (but provides advice to applications that do).
[STANDARDS-TRACK]
This document is a product of the TCP Maintenance and Minor Extensions Working Group of the IETF.
This is now a Proposed Standard Protocol.
STANDARDS TRACK: 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-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
http://www.ietf.org/mailman/listinfo/ietf-announce
http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC