Re: [pmtud] Improvement for the current PMTUD mechanism

Fernando Gont <fernando@gont.com.ar> Wed, 09 November 2005 00:55 UTC

Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EZeFP-0004n6-PZ; Tue, 08 Nov 2005 19:55:31 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EZeFO-0004my-3V for pmtud@megatron.ietf.org; Tue, 08 Nov 2005 19:55:30 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA29799 for <pmtud@ietf.org>; Tue, 8 Nov 2005 19:55:03 -0500 (EST)
Received: from server.frh.utn.edu.ar ([170.210.17.146] ident=qmailr) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EZeVG-0002MW-V9 for pmtud@ietf.org; Tue, 08 Nov 2005 20:11:57 -0500
Received: (qmail 10946 invoked from network); 9 Nov 2005 00:54:28 -0000
Received: from ftp.frh.utn.edu.ar (HELO fgont.gont.com.ar) (gont-fernando@170.210.17.150) by server.frh.utn.edu.ar with SMTP; 9 Nov 2005 00:54:28 -0000
Message-Id: <6.2.0.14.0.20051108164856.038e2d80@localhost>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.0.14
Date: Tue, 08 Nov 2005 16:55:20 -0800
To: John Heffner <jheffner@psc.edu>, pmtud@ietf.org
From: Fernando Gont <fernando@gont.com.ar>
Subject: Re: [pmtud] Improvement for the current PMTUD mechanism
In-Reply-To: <200510171608.41054.jheffner@psc.edu>
References: <6.2.0.14.0.20050905131637.039f4138@pop3.frh.utn.edu.ar> <200510101423.17123.jheffner@psc.edu> <6.2.0.14.0.20051016155921.04269278@www.syntrip.com.ar> <200510171608.41054.jheffner@psc.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d
Cc:
X-BeenThere: pmtud@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Path Maximum Transmission Unit Discovery <pmtud.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pmtud>, <mailto:pmtud-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/pmtud>
List-Post: <mailto:pmtud@ietf.org>
List-Help: <mailto:pmtud-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pmtud>, <mailto:pmtud-request@ietf.org?subject=subscribe>
Sender: pmtud-bounces@ietf.org
Errors-To: pmtud-bounces@ietf.org

At 08:08 a.m. 17/10/2005, John Heffner wrote:

> > Actually, this cannot have interoperation problems. IIRC, TCP congestion
> > control is not mandatory.
> > And even then, fast retransmit is not specifically congestion control. If
> > anything, I'm proposing to slow down the packet rate, rather than
> > increasing it. (i.e. being more conservative).
>
>In point of fact TCP congestion control is a MUST per RFC 1122, but this is
>entirely separate from the issue at hand. :-)
>
>Any change to standards constraining how or when TCP may recover from a loss
>is pretty significant.  I think it is a discussion topic for tcpm.

After reading the PLPMTUD draft, I think this is kind of sooting yourself 
in your own foot.

My solution to the scenario you raised was to disable fast-restransmit when 
there's a pending ICMP message.

Disabling fast-retransmit is okay, as it is being more conservative (you 
send *less* data).

PLPMTUD disables *congestion* *control* which leads to more data being 
sent, and could lead to congestion in the Internet.

Yes, it may not be a killer, but it's certainly much less conservative than 
disabling fast-retransmit.

Kindest regards,

--
Fernando Gont
e-mail: fernando@gont.com.ar || fgont@acm.org






_______________________________________________
pmtud mailing list
pmtud@ietf.org
https://www1.ietf.org/mailman/listinfo/pmtud