Re: [L2tpext] Offset size
"W. Mark Townsley" <townsley@cisco.com> Sat, 02 March 2002 10:53 UTC
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA27407 for <l2tpext-archive@odin.ietf.org>; Sat, 2 Mar 2002 05:53:27 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id FAA11623; Sat, 2 Mar 2002 05:48:22 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id FAA11597 for <l2tpext@optimus.ietf.org>; Sat, 2 Mar 2002 05:48:20 -0500 (EST)
Received: from franklin.cisco.com (franklin.cisco.com [171.70.156.17]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA27339 for <l2tpext@ietf.org>; Sat, 2 Mar 2002 05:48:16 -0500 (EST)
Received: from cisco.com (ams-clip-vpn-dhcp4182.cisco.com [10.50.16.85]) by franklin.cisco.com (8.8.6 (PHNE_17190)/CISCO.SERVER.1.2) with ESMTP id CAA12087; Sat, 2 Mar 2002 02:47:44 -0800 (PST)
Message-ID: <3C80AD5E.17635F30@cisco.com>
Date: Sat, 02 Mar 2002 11:45:50 +0100
From: "W. Mark Townsley" <townsley@cisco.com>
X-Mailer: Mozilla 4.76 [en]C-CCK-MCD (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Cédric Fau <tra27@etu.enseeiht.fr>
CC: l2tpext@ietf.org
Subject: Re: [L2tpext] Offset size
References: <3C7FA655.8060607@etu.enseeiht.fr>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit
Sender: l2tpext-admin@ietf.org
Errors-To: l2tpext-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Layer Two Tunneling Protocol Extensions <l2tpext.ietf.org>
X-BeenThere: l2tpext@ietf.org
Content-Transfer-Encoding: 8bit
If you have an odd-sized layer two frame being carried between your tunnel header and the framed network packets (e.g. an IP packet being framed by a PPP packet with PFC negotiated, resulting in a 3 byte PPP frame) then it could help the performance of some implementations to insert padding bytes to ensure alignment of the framed network packet (e.g. the IP packet). At one time, it's affect on at least some implementations was measurable, particularly on an LNS which routed the tunneled, framed, IP packet locally rather than sending it out another physical connection. The implications today may not be as marked, and is in fact becoming more and more contraversial as to whether it is even necessary, but still could theoretically be an issue. It is always, of course, optional. - Mark Cédric Fau wrote: > > Hello, > > I have some issues with the offset size field. I don't understand its aim. > If it is still present in the L2TP header in the > draft-ietf-l2tpext-l2tp-ppp-01.txt, that's > because there is a use of this field. But what kind of use ? > > Cédric Fau > mailto: cedric.fau@etu.enseeiht.fr > > Student in Telecommunication and Network Engineering > http://www.enseeiht.fr/ > > _______________________________________________ > L2tpext mailing list > L2tpext@ietf.org > https://www1.ietf.org/mailman/listinfo/l2tpext _______________________________________________ L2tpext mailing list L2tpext@ietf.org https://www1.ietf.org/mailman/listinfo/l2tpext
- [L2tpext] Offset size Cédric Fau
- Re: [L2tpext] Offset size W. Mark Townsley
- Re: [L2tpext] Offset size Cédric Fau
- Re: [L2tpext] Offset size W. Mark Townsley