Re: [Pppext] Re: Last Call: 'Accommodating an MTU/MRU greater than 1492 in PPPoE' to Informational RFC
Pekka Savola <pekkas@netcore.fi> Fri, 17 February 2006 21:59 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 1FADdv-00076w-Jc; Fri, 17 Feb 2006 16:59:59 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1FADdt-00075Q-7W; Fri, 17 Feb 2006 16:59:57 -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 QAA17496; Fri, 17 Feb 2006 16:58:08 -0500 (EST)
Received: from netcore.fi ([193.94.160.1]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FADsN-00054t-Jh; Fri, 17 Feb 2006 17:14:57 -0500
Received: from netcore.fi (localhost [127.0.0.1]) by netcore.fi (8.12.8/8.12.8) with ESMTP id k1HLxhHa009810; Fri, 17 Feb 2006 23:59:43 +0200
Received: from localhost (pekkas@localhost) by netcore.fi (8.12.8/8.12.8/Submit) with ESMTP id k1HLxhWV009807; Fri, 17 Feb 2006 23:59:43 +0200
Date: Fri, 17 Feb 2006 23:59:43 +0200
From: Pekka Savola <pekkas@netcore.fi>
To: James Carlson <james.d.carlson@sun.com>
In-Reply-To: <17398.16971.577636.543375@gargle.gargle.HOWL>
Message-ID: <Pine.LNX.4.64.0602172342070.9251@netcore.fi>
References: <E1F9lDN-0003AG-9f@stiedprstage1.ietf.org> <Pine.LNX.4.64.0602172155370.6502@netcore.fi> <17398.16971.577636.543375@gargle.gargle.HOWL>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"; format="flowed"
X-Virus-Scanned: ClamAV 0.88/1291/Thu Feb 16 22:15:09 2006 on otso.netcore.fi
X-Virus-Status: Clean
X-Spam-Status: No, score=-3.5 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.1.0
X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on otso.netcore.fi
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3e15cc4fdc61d7bce84032741d11c8e5
Cc: pppext@ietf.org, iesg@ietf.org, ietf@ietf.org
Subject: Re: [Pppext] Re: Last Call: 'Accommodating an MTU/MRU greater than 1492 in PPPoE' to Informational RFC
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
On Fri, 17 Feb 2006, James Carlson wrote: > Pekka Savola writes: >> This doc seems to define a PPPoE option 'PPP-Max-Payload'. It talks >> of using PPP MRU option. There is no PPP MTU option that I could see. >> >> My question here is, should there be a PPP MTU option instead of a >> PPPoE option? This would be a more generic solution to this part of > > I don't follow. PPP is symmetric -- there are two MRUs negotiated, > one for each direction. Your peer's MRU is your maximum (and default) > MTU. Your peer's MRU is not directly your MTU, because the MTU could be lower as well (e.g., capped by the interface MTU). But yes -- this was mentioned in the pseudo-code. > How could we need another option for this? Or how could one help? > > What's really going on here is negotiation about the existence of a > usable path. Unfortunately, the underlying protocol itself (other > than LLDP) doesn't provide a way to do this. This new mechanism thus > doesn't solve the actual problem, but does at least allow consenting > peers to identify each other. (In other words, I view it as just a > boolean.) I guess the problem I was having here is that I didn't understand why a PPPoE MTU options would be useful (still don't). After all, if both PPP endpoins would signal MRU = 2000 (for example), then PPPoE could just use that with no need for an extra option? Looking back at the archives, it appears others have had related concerns, so I guess this is beating a dead horse.. >> MRU test procedure using MRU-sized Echo-Requests is disabled by >> default and to be used for debug purposes only. I'm questioning >> whether this is wise. The protocol would be much more robust against > > I don't think it is. But we did discuss that during the document > review. I reviewed the mailing list archives for the last 6 months, and at least during that period I didn't see this discussed. But let me qualify that. "The protocol would be more robust against ..." instead of "much more". That is at least an objective statement: as the document specifies that all PPPoE servers MUST support this mechanism, sooner or later someone is going to misconfigure too high MTU usage when jumboframes aren't enabled, or someone is going to disable jumboframes somewhere on the path. Currently there is no jumboframe spec that I'm aware of, and there is no way to recover or notice these situations that I can think of. -- Pekka Savola "You each name yourselves king, yet the Netcore Oy kingdom bleeds." Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings _______________________________________________ Ietf mailing list Ietf@ietf.org https://www1.ietf.org/mailman/listinfo/ietf
- Re: Last Call: 'Accommodating an MTU/MRU greater … Pekka Savola
- Re: [Pppext] Re: Last Call: 'Accommodating an MTU… Pekka Savola
- Re: [Pppext] Re: Last Call: 'Accommodating an MTU… James Carlson
- Re: [Pppext] Re: Last Call: 'Accommodating an MTU… James Carlson
- RE: [Pppext] Re: Last Call: 'Accommodating an MTU… James Carlson