Re: Review of draft-bberry-pppoe-credit (Informational)

Vernon Schryver <[email protected]>
Newsgroups gmane.ietf.pppext
Message-ID <[email protected]>
> From: Mark Lanzo <[email protected]>
> To: [email protected]
> cc: [email protected], [email protected], [email protected],
>         [email protected], [email protected]


> PPPoE is really just being used as a means to multiplex multiple
> PPP sessions over the ethernet link to the radio, and as a carrier
> for signalling info between radio and router.

Which raises my question of what PPPoE has to do with the solution
and my point that PPP(oE) is widely misunderstood as other than a
link layer protocol.  Why use PPPoE to link networks instead of IP?


> A completely new protocol could have been devised for all of this,
> but since the nature of the info traded by that protocol would have
> been very much like the nature of the info traded by PPPoE, I think
> the authors wanted to use PPPoE precisely so they wouldn't be
> completely reinventing the same old wheel.  The purpose of the document
> isn't to make a general-purpose extension to PPPoE, it's to create
> a special purpose extension for a very specific sort of environment.

So why not use the official IETF standard way to link networks instead
of piling kludges on top of the kludge that is PPPoE? 

The IETF standard way would be to give the routers IP addresses and
use a real routing protocol (or even static routes) instead of what
looks sounds like a retread of IGRP.  You might use PPPoE (or not)
between the access concentrators and their neighboring stationary
radios.  You might define a PPP over RLP encapsulation that would have
credits, battery condition, and so forth among the radios.
Wouldn't that produce products with a wider potential market as well
as fewer nastinesses such as an MTU that is even smaller than the bad
old PPPoE MTU of 1492?

Why egregiously violate layering by trying to convert IEEE 802.3
into an inter-network protocol?


Vernon Schryver    [email protected]

_______________________________________________
Pppext mailing list
[email protected]
https://www1.ietf.org/mailman/listinfo/pppext
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.