Actually most business dsl setups are either at or moving to PPPoA, with
is very similar to PPPoE. PPPoE uses a DSL modem, and, if wanted, a
broadband router for NAT.
PPPoA is a system where the device at the customer prem is an actual
router, (a DSL Router) that terminates PPP over an ATM pvc that rides
the DSL circuit. The service provider then routes a subnetwork to that
DSL router.
The router performs the username and password combo to the service
providers equipment. All the customer sees is the network on the
ethernet side of the router.
PPPoE lets service providers oversubscribe their DSL termination
routers. If just regular bridged connections were used a router can
only handle so many (8000 for redback sms-1800 routers) of those
circuits. With PPPoE the service provider can terminate many more
circuits since not everyone is using the system at the same time. This
greatly recudes the per-user cost of the equipment for the service
provider. It also works the same as a dialup connection that the user
is already familiar with. There really arent many problems with PPPoE
at all. It's very more scalable than bridged RFC1483 operation.
-----Original Message-----
From: owner-6bone@ISI.EDU [mailto:owner-6bone@ISI.EDU] On Behalf Of
Michael Richardson
Sent: Monday, April 29, 2002 4:40 PM
To: Christian Kuhtz
Cc: 6bone@ISI.EDU
Subject: Re: about IPv6 PPPoE
>>>>> "Christian" == Christian Kuhtz <ck@arch.bellsouth.net> writes:
Christian> there's a difference between a user's perspective and
service
Christian> provider. i was stating the service provider side.
bridged dsl is
Christian> grandfathered, being phased out, and all new deployment
for the past
Christian> couple of years has been pppoe at the sp i'm most
familiar with. the
Christian> issues are around management and scalability of the
service.
Well, it might be the going concern for residential, but almost no
soho/business installations I'm familliar with will tolerate pppoe.
There just isn't a point. We do not want the address negotiated, we do
not need another password
that could be divulged, and we *do* want some address space behind the
box.
PPPoE deployment ==> more NAT in my opinion.
] ON HUMILITY: to err is human. To moo, bovine. |
firewalls [
] Michael Richardson, Sandelman Software Works, Ottawa, ON |net
architect[
] mcr@sandelman.ottawa.on.ca http://www.sandelman.ottawa.on.ca/ |device
driver[ ] panic("Just another NetBSD/notebook using, kernel hacking,
security guy"); [