|
North American Network Operators Group Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical RE: Service Provider Exchange requirements
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I'll give a few more hints as to what I'm looking for.. How about ethernet versus ATM? With VLANs and high speed such as Gig/10Gig, I can get speed and one to many arrangements (at least for lower speeds). Should Ethernet be point to point or optionally multiaccess in nature? Or, what about MPLS? With MPLS, service provider connections can be established without concern for underlying media (e.g., ethernet, POS, ATM). Is Diff-Serv or ATM QoS a requirement or can 85-90% of requirements be met with loss/latency service as the baseline? What special arrangements should be made for hosting (e.g., local caching or streamers)? Yes, I'm stretching here a bit. - -----Original Message----- From: [email protected] [SMTP:[email protected]] Sent: Sunday, October 22, 2000 5:24 PM To: [email protected] Cc: '[email protected]' Subject: Re: Service Provider Exchange requirements > What switching and/or service characteristics would you require > such that an exchange point would be desirable (e.g., media types, > switch fabric, route servers, multicast services, SLAs, ..)? > Kind of depends on what you want out of your exchange and who your target marrket(s) are. Factor in budgets, (financial, space, environmental...) and you should have winnowed down the conceivable to the likely. Enjoy. - --bill -----BEGIN PGP SIGNATURE----- Version: PGPfreeware 6.5.8 for non-commercial use <http://www.pgp.com> iQA/AwUBOfNoT5uyh6FekS+1EQI8VgCglnkgxLEuT5LYJAoqsYRFd67JejEAn1VJ jOz0O7zVxclHYHxuSQlqvskL =A7/Z -----END PGP SIGNATURE-----
|