bugtraq - IETF RFC on "the implementation of the TCP urgent mechanism"

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <AANLkTin-KmXOGFahsthzoH799KEiWGDaC65bUQQWWMYD@mail.gmail.com>
Date: Tue, 25 Jan 2011 18:18:33 -0300
From: Fernando Gont <fernando.gont@...il.com>
To: bugtraq@...urityfocus.com
Cc: full-disclosure@...ts.grok.org.uk
Subject: IETF RFC on "the implementation of the TCP urgent mechanism"

Folks,

RFC 6093, entitled "On the Implementation of the TCP Urgent Mechanism"
has just been published. It is available at:
http://www.rfc-editor.org/rfc/rfc6093.txt

This RFC has been motivated, to a large extent, by the behavior of
some well-known firewalls.

The Abstract of the RFC is:

---- cut here ----
   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).
---- cut here ----

More informantion about this and other related issues is available at
my web site: http://www.gont.com.ar

Thanks!

Best regards,
-- 
Fernando Gont
e-mail: fernando@...t.com.ar || fgont@....org
PGP Fingerprint: 7809 84F5 322E 45C7 F1C9 3945 96EE A9EF D076 FFF1