public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Zephaniah E\. Hull" <warp@babylon.d2dc.net>
To: John Bradford <john@grabjohn.com>
Cc: Valdis.Kletnieks@vt.edu, linux-kernel@vger.kernel.org
Subject: Re: RFC3168, section 6.1.1.1 - ECN and retransmit of SYN
Date: Fri, 21 Feb 2003 15:53:33 -0500	[thread overview]
Message-ID: <20030221205333.GA1684@babylon.d2dc.net> (raw)
In-Reply-To: <200302212040.h1LKejY3001679@81-2-122-30.bradfords.org.uk>

[-- Attachment #1: Type: text/plain, Size: 2188 bytes --]

</lurk>

On Fri, Feb 21, 2003 at 08:40:45PM +0000, John Bradford wrote:
> > RFC3168 section 6.1.1.1 says this:
> > 
> >    A host that receives no reply to an ECN-setup SYN within the normal
> >    SYN retransmission timeout interval MAY resend the SYN and any
> >    subsequent SYN retransmissions with CWR and ECE cleared.  To overcome
> >    normal packet loss that results in the original SYN being lost, the
> >    originating host may retransmit one or more ECN-setup SYN packets
> >    before giving up and retransmitting the SYN with the CWR and ECE bits
> >    cleared.
> > 
> > Supporting this would make using ECN a lot less painful - currently, if
> > I want to use ECN by default, I get to turn it off anytime I find an
> > ECN-hostile site that I'd like to communicate with.
> 
> Linux shouldn't encourage the use of equipment that violates RFCs, in
> this case, RFC 739.

Linux shouldn't encourage the use of equipment that attempts to emulate
<insert thing here> but screws it up.
> 
> The correct way to deal with it, is to contact the maintainers of the
> site, and ask them to fix the non conforming equipment.

The correct way to deal with it, is to contact the manufactures of the
equipment.
> 
> If the problem is caused upstream, by equipment out of the
> site's maintainers' control, it is their responsibility to contact the
> relevant maintainers, or change their upstream provider.

If the hardware is provided by people upstream, and is out of the
control of the sysadmin's control, it is their responsibility to contact
the relevant people, or change hardware providers.

Oh, look, does that mean that we can now remove all the work arounds in
the various network, ide, etc drivers?

No, I believe Linus has stated many times that Linux is not a research
project, it is meant to actually be USED.

<lurk>

-- 
	1024D/E65A7801 Zephaniah E. Hull <warp@babylon.d2dc.net>
	   92ED 94E4 B1E6 3624 226D  5727 4453 008B E65A 7801
	    CCs of replies from mailing lists are requested.

I am an "expert".  Fear me, for I will wreak untold damage upon anything
I can get my grubby hands on.
  -- Matt McLeod on ASR.

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2003-02-21 20:43 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fa.lnpabmu.5sd1q@ifi.uio.no>
2003-02-21 20:13 ` RFC3168, section 6.1.1.1 - ECN and retransmit of SYN Valdis.Kletnieks
2003-02-21 20:40   ` John Bradford
2003-02-21 20:53     ` Zephaniah E. Hull [this message]
2003-02-21 21:25       ` John Bradford
2003-02-22  0:47         ` David S. Miller
2003-02-22  0:48           ` Valdis.Kletnieks
2003-02-22  6:46             ` David S. Miller
2003-02-22 18:45             ` Werner Almesberger
2003-02-22 23:26               ` David S. Miller
2003-02-22 10:56           ` John Bradford
2003-02-22 10:47             ` David S. Miller
2003-02-21 21:43     ` Mika Liljeberg
2003-02-21 22:05       ` Valdis.Kletnieks
2003-02-21 22:32         ` Maciej Soltysiak
2003-02-23  4:57   ` Kevin Buhr
2003-02-21 21:37 jordan.breeding

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20030221205333.GA1684@babylon.d2dc.net \
    --to=warp@babylon.d2dc.net \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=john@grabjohn.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox