home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!cs.utexas.edu!uwm.edu!ogicse!das-news.harvard.edu!cantaloupe.srv.cs.cmu.edu!crabapple.srv.cs.cmu.edu!andrew.cmu.edu!ms6b+
- From: ms6b+@andrew.cmu.edu (Marvin Sirbu)
- Newsgroups: comp.dcom.cell-relay
- Subject: Re: Future of IP routers
- Message-ID: <geb3Mva00VADI4SMED@andrew.cmu.edu>
- Date: 26 Aug 92 17:56:11 GMT
- Article-I.D.: andrew.geb3Mva00VADI4SMED
- Organization: Engineering and Public Policy, Carnegie Mellon, Pittsburgh, PA
- Lines: 35
- In-Reply-To: <BtLKKH.CJ6@usenet.ucs.indiana.edu>
-
- Excerpts from netnews.comp.dcom.cell-relay: 26-Aug-92 Re: Future of IP
- routers by Allen Robel@ucs.indiana.
- > Which means that the filtering functionality currently available
- > in routers gets pushed out to end nodes and is carried out
- > at call setup? I'm not sure that I'm comfortable with this
- > sort of arrangement. Take a hypothetical situation where,
- > as a part of organizational policy--possibly for budgetary
- > reasons--users should be denied access to interactive video
- > communication outside of a given administrative domain but
- > that other services, some of which might include non-interactive
- > video/audio retrieval from a subset of information providers,
- > should be allowed. With TCP, we have "well known" port numbers
-
- Remember that ATM is going to replace the voice network as well as the
- data network. Take a look at call screening and call control in today's
- voice networks; it is actually quite sophisticated. In an ATM world,
- the local ATM switch--acting much like today's PBX--will no doubt be
- able to do all kinds of policy restrictions. Today's PBX can limit
- calls to local versus toll or intra-company versus external; it can vary
- the service by time of day (toll restriction after 5 pm so the custodial
- staff doesn't make long distance calls...) or even provide a different
- grade of service depending upon the caller callee pair. And this is all
- done at call setup.
-
- When the call setup message specifies a service type (e.g. in ISDN the
- call setup message can specify "speech" versus "3.1 KHz audio" vs
- "unrestricted data" versus "video"), it will be simple enough to add
- that to the list of variables on which call setup decisions are made.
- Indeed, if I don't specify that I want circuit switched data capability
- when I sign up for ISDN service, -- and pay extra for it compared to
- voice only--any call setup message specifying unrestricted data will be
- blocked by my CO today!
-
- Marvin Sirbu
- CMU
-