Found 1 record.

Status: Rejected (1)

RFC 6093, "On the Implementation of the TCP Urgent Mechanism", January 2011

Note: This RFC has been obsoleted by RFC 9293

Errata ID: 4312
Status: Rejected
Type: Technical
Publication Format(s) : TEXT
Reported By: Justin Yirka
Date Reported: 2015-03-24
Rejected by: Martin Stiemerling
Date Rejected: 2015-04-21

Section 3.1 says:

Unfortunately, virtually all TCP implementations process TCP urgent
indications differently.  By default, the last byte of "urgent data"
is delivered "out of band" to the application.  That is, it is not
delivered as part of the normal data stream [UNPv1].  For example,
the "out-of-band" byte is read by an application when a recv(2)
system call with the MSG_OOB flag set is issued.

It should say:

Unfortunately, virtually all TCP implementations process TCP urgent
indications differently.

For example, by default in particular UNIX implementations, the last
byte of "urgent data" is delivered "out of band" to the application.
That is, it is not delivered as part of the normal data stream [UNPv1].
For example, the "out-of-band" byte is read by an application when a
recv(2) system call with the MSG_OOB flag set is issued.

Notes:

The first and latter statements are contradictory, as a default is unlikely to apply when "virtually all" implementations process differently.
This correction to include "in particular UNIX implementations" would be appropriate at many points throughout the document in order to differentiate references to implementation specific features and terminology from references to terminology established in prior RFCs.
--VERIFIER NOTES--
Reading the text in a flow isn't giving the contradiction that there is a contradiction.

Report New Errata