From owner-freebsd-net Fri Oct 27 18: 7: 3 2000 Delivered-To: freebsd-net@freebsd.org Received: from whizzo.transsys.com (whizzo.TransSys.COM [144.202.42.10]) by hub.freebsd.org (Postfix) with ESMTP id 3BEB537B4C5 for ; Fri, 27 Oct 2000 18:06:56 -0700 (PDT) Received: from whizzo.transsys.com (localhost.transsys.com [127.0.0.1]) by whizzo.transsys.com (8.11.0/8.11.0) with ESMTP id e9S16iG52793; Fri, 27 Oct 2000 21:06:44 -0400 (EDT) (envelope-from louie@whizzo.transsys.com) Message-Id: <200010280106.e9S16iG52793@whizzo.transsys.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: gcorcoran@lucent.com Cc: Garrett Wollman , Julian Elischer , freebsd-net@FreeBSD.ORG X-Image-URL: http://www.transsys.com/louie/images/louie-mail.jpg From: "Louis A. Mamakos" Subject: Re: More on PPPoE & ADSL (Telstra Bigpond) References: <39F8C29F.D785C588@lucent.com> <39F9210E.B728D4F8@elischer.org> <39F9B679.CA563B9E@lucent.com> <39F9E669.FB8D77D2@elischer.org> <39F9F1FB.F00E686F@lucent.com> <39F9FFAD.2992767D@elischer.org> <39FA0056.8CB7D452@elischer.org> <39FA081C.3E56D791@lucent.com> <200010280008.UAA35316@khavrinen.lcs.mit.edu> <39FA19AF.B385583F@lucent.com> In-reply-to: Your message of "Fri, 27 Oct 2000 20:11:27 EDT." <39FA19AF.B385583F@lucent.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 27 Oct 2000 21:06:44 -0400 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > > Garrett Wollman wrote: > > > > < said: > > > > > if you actually wanted multiple _concurrent_ sessions, my current driver > > > couldn't do it. However I (personally) wouldn't want to pay for several > > > ISPs! :) > > > > Consider the case where you have a DSL connection into a private > > network, but also want to have access to the public network. > > Good point - that might actually occur... This scenario was exactly one of the configurations we wanted to support whilst developing the protocol. The thought was to be able to concurrently support a "consumer"-style (e.g., AOL, MSN) user as well as a teleworker on different end-systems simultaneously, with different access policies and characteristics. I was part of the architecture that this policy would be implemented at the access concentrator, which is where filtering, over-subscription, etc. is managed. Having multiple sessions per end-system also seemed useful, and is why there's a session id so you can multiplex on that as well as the end-system and access concentrator MAC addresses. Louis Mamakos (AKA louie@UU.NET, one of the instigators of the protocol) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message