[Gen-art] Re: Gen-art review of draft-bberry-pppoe-credit-04.txt

James Carlson <james.d.carlson@sun.com> Tue, 03 January 2006 19:57 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 1EtsHk-0000i0-Rk; Tue, 03 Jan 2006 14:57:32 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EtsHg-0000he-5N for gen-art@megatron.ietf.org; Tue, 03 Jan 2006 14:57: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 OAA20435 for <gen-art@ietf.org>; Tue, 3 Jan 2006 14:56:12 -0500 (EST)
Received: from brmea-mail-3.sun.com ([192.18.98.34]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EtsMu-0000zP-7B for gen-art@ietf.org; Tue, 03 Jan 2006 15:02:59 -0500
Received: from eastmail1bur.East.Sun.COM ([129.148.9.49]) by brmea-mail-3.sun.com (8.12.10/8.12.9) with ESMTP id k03JvE3F024009 for <gen-art@ietf.org>; Tue, 3 Jan 2006 12:57:14 -0700 (MST)
Received: from phorcys.East.Sun.COM (phorcys.East.Sun.COM [129.148.174.143]) by eastmail1bur.East.Sun.COM (8.12.10+Sun/8.12.10/ENSMAIL, v2.2) with ESMTP id k03JvCH4007850 for <gen-art@ietf.org>; Tue, 3 Jan 2006 14:57:13 -0500 (EST)
Received: from phorcys.East.Sun.COM (localhost [127.0.0.1]) by phorcys.East.Sun.COM (8.13.5+Sun/8.13.5) with ESMTP id k03JvCXf018795; Tue, 3 Jan 2006 14:57:12 -0500 (EST)
Received: (from carlsonj@localhost) by phorcys.East.Sun.COM (8.13.5+Sun/8.13.5/Submit) id k03JvCuB018792; Tue, 3 Jan 2006 14:57:12 -0500 (EST)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Message-ID: <17338.55064.4387.404948@gargle.gargle.HOWL>
Date: Tue, 03 Jan 2006 14:57:12 -0500
From: James Carlson <james.d.carlson@sun.com>
To: Elwyn Davies <elwynd@dial.pipex.com>
In-Reply-To: Elwyn Davies's message of 3 January 2006 19:45:08
References: <43B57671.6050609@dial.pipex.com> <43B9650E.3020405@cisco.com> <43BAB7DF.3040602@dial.pipex.com> <17338.47871.815713.962360@gargle.gargle.HOWL> <43BACA9D.7090200@dial.pipex.com> <17338.52447.802990.819791@gargle.gargle.HOWL> <43BAD444.5000209@dial.pipex.com>
X-Mailer: VM 7.01 under Emacs 21.3.1
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 21c69d3cfc2dd19218717dbe1d974352
Content-Transfer-Encoding: 7bit
Cc: Margaret Wasserman <margaret@thingmagic.com>, Mark Townsley <townsley@cisco.com>, gen-art@ietf.org, bberry@cisco.com, hholgate@cisco.com
Subject: [Gen-art] Re: Gen-art review of draft-bberry-pppoe-credit-04.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
Sender: gen-art-bounces@ietf.org
Errors-To: gen-art-bounces@ietf.org

Elwyn Davies writes:
> >PPPoE and PPP are independent protocols.  PPP tunnels over PPPoE.
> >  
> >
> That's fine and dandy but I think the problem is that as drafted, some 
> of the PPP packets would not have any credit tag on them so you have to 
> distinguish between the ones with a credit tag plus a PPP packet and 
> those that just have a PPP packet. A strange form of tunnel!

I don't see that in the draft.  They do make a distinction between
PPPoE control and data messages -- control messages don't contain
embedded PPP data and don't employ the credit scheme, and data
messages *do* carry the PPP data and do use credits.  I see no
opportunity here for a problem.

I suspect you're referring to the ability to piggyback credit grants
atop PPPoE data messages.  That's not a problem because even messages
without grants consume credit space and are thus metered.

As best I can tell, it works.

(Even if it didn't work, I wouldn't be too worked up about it.  It's
"only" PPPoE ... and likely only affects this one vendor's recommended
baroque deployment.)

> >It's not exactly "Emporer's New Clothes."
> >  
> >
> There certainly appear to be a few rents leaving the naughty bits 
> showing ;-)

Hardly the biggest ones.  PPPoE itself has holes fit for a truck --
including security (none), MTU (non-standard), and session ID
assignment (unidirectional).  It's a tough neighborhood.

> I think we know where we stand on this one and we don't need to expend 
> any more cycles on it.  Let's see what happens...

OK; sounds good.

-- 
James Carlson, KISS Network                    <james.d.carlson@sun.com>
Sun Microsystems / 1 Network Drive         71.232W   Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757   42.496N   Fax +1 781 442 1677

_______________________________________________
Gen-art mailing list
Gen-art@ietf.org
https://www1.ietf.org/mailman/listinfo/gen-art