Re: What is a regional exchange point?
"Jere Retzer" <[email protected]> Thu, 06 Mar 2003 09:24:48 -0800
| Newsgroups | gmane.org.operators.rep |
|---|---|
| Message-ID | <[email protected]> |
This is a MIME message. If you are reading this text, you may want to consider changing to a mail reader or gateway that understands how to properly handle MIME multipart messages. --=_D48B8061.D8B85F79 Content-Type: text/plain; charset=ISO-8859-7 Content-Transfer-Encoding: quoted-printable There are really a lot of great thoughts emerging here. I like Dave's list = (below my post) and several other thoughts put forward. Here's a couple = more to add to the below list. I'll leave it to someone else to make these = inputs consistent. I think Celeste's recent summary is a great start. A REP can also provide a way to share point to point connections to enable = applications that will not work reliably or affordably over the = Internet.=20 One example I give is telemedicine. Telemedicine has not taken off due to = a number of reasons that are slowly being overcome (such as insurance = reimbursement =AF people like to get paid). One of these, however is = having enough applications and volume of use to make it worthwhile to = spend the money on equipment, circuits, training, etc. I find that in many = cases in Oregon, that smaller and more rural health care providers in = particular may have professional relationships with several different = regional hospitals/systems =AF pediatrics may have a relationship with = one, ortho another, radiology, etc. It generally does not pencil out, = however for them to get a video unit and dedicated or ISDN lines just for = one application. However, if we can get the major hospitals to connect to = one another there is the possibility of them all becoming accessible to = the small, rural hospitals, increasing the value of the connection and = actually resulting in greater demand for telecommunications and Internet = service. Combine this use, with the ability for the systems to trade = traffic with one another (they tend to work a lot with each other, even = when competitors) and the ability to promote external contract partnerships= as well as access the highly reliable, affordable transit and I think you = have a winning combination. Interactive video is also a great example of = an application that doesnot work across a usual Internet connection, but = can over a regional exchange if the participants are connected by networks = that are properly engineered and the router hops are minimized as a = function of the exchange. This same logic applies to lots of other concepts. Hospitals also have = lots of external relationships with contractors (laboratories, interpreters= , clinics, insurance companies), some of which could be done more = effectively with a high speed/quality connection. Telecommuting (teleworkin= g as I hear it called lately) critical mass becomes easier in a share = environment, etc. I use the generic argument that today these kind of = relationships, if networks are used at all require an "n-squared" (meshed) = network, which is not affordable but that a REP can allow a hub and spoke = architecture, which is much more affordable. Another point. A REP can provide (we hope) a means to enable a region to = attain critical mass to become a major location on the Internet. This is something we are trying to do here. Currently, Oregon is basically = a stub off of the major networks. This occurred both because of size and = notably proximity to Seattle and Northern California. Our hope is that by = greatly increasing the bandwidth across our REP(s) that we can help = cost-justify the major networks to increase their presence and in time to = connect to one another here, moving us in effect closer to if not = eventually on to the "backbone." (Yes, I know there is no "backbone" per = se, the closest thing probably being the major exchanges) There are at = least a couple economic reasons that we want to do this. First, having all = the traffic leave town means that we lose the jobs that a more robust = local Internet would provide =AF local sales and engineers in the = telecommunications and networks companies. Second, it means that local = customers pay a penalty to backhaul their traffic to major connection = points. Third, it means that a lot of opportunities simply go elsewhere. = Oregon has a large tech employment base and is consistently among the = "most wired" communities in the world yet, if an Oregon company wants a = really world class web site they will most likely host it in some city = that is "on the backbone" in order to get the best performance and the = lowest cost bandwidth. Jere >>> [email protected] 03/06/03 06:11AM >>> Hello All .... It sounds like most of the technical aspects of REP's are being covered. I would like to start a similar thread about what is a REP, but from a business perspective. Remember, for REPs to be fully utilized they must be able to speak to a wider (and paying ) audience, the enterprise, municipal government = and Universities. Not just service providers as we tend to see in the MAE model. Who direct connects to a REP : Municipal government, Universities and education, enterprise, application service providers and service providers. >From a business perspective : 1). A REP forms the core of a Metropolitan Internet 2). A Metropolitan Internet provides transport for applications that are Regional. 3). Services is the name of the game, these would be supplied by ASP's not necessarily the REP operator. Regional Applications include : 1). Access to multiple Internet 1 providers ( cost reduction ) 2). Access to multiple I2 routes. ( transport diversity ) 3). Access to regional video distribution -Local University distance learning -Local video conferencing 4). Regional disaster recovery ( public archival storage ) 5). Regional virus protection 6). A gateway for voice softswitch access ( a place for all that Cisco IP phone traffic to go to ) 7). Local higher speed content services 8). HIPAA compliance via a truly survivable geographically diverse architecture Dave ----- Original Message ----- From: "Jere Retzer" <[email protected]> To: <[email protected]> Sent: Wednesday, March 05, 2003 11:27 PM Subject: Re: [REPforum] What is a regional exchange point? > I think there is a continuum from local to global IP exchanges with regional somewhere in the middle. Local exchanges mainly peer to exchange local traffic in order to keep local bits local and save transit. Global exchanges mainly peer to tie together the global Internet. Regional exchanges may provide both local peering as well as access to transit, and = a convenient location for the major networks to peer with one another. > > Jere > --=_D48B8061.D8B85F79 Content-Type: text/html; charset=ISO-8859-7 Content-Transfer-Encoding: quoted-printable Content-Description: HTML <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD> <META http-equiv=3DContent-Type content=3D"text/html; charset=3Diso-8859-1"= > <META content=3D"MSHTML 5.50.4727.700" name=3DGENERATOR></HEAD> <BODY style=3D"MARGIN-TOP: 2px; FONT: 12pt Verdana; MARGIN-LEFT: 2px"> <DIV>There are really a lot of great thoughts emerging here. I like Dave's = list=20 (below my post) and several other thoughts put forward. Here's a = couple=20 more to add to the below list. I'll leave it to someone else to make = these=20 inputs consistent. I think Celeste's recent summary is a great start.</DIV>= <DIV> </DIV> <DIV>A REP can also provide a way to share point to point connections to = enable=20 applications that will not work reliably or affordably over the Internet. = </DIV> <DIV> </DIV> <DIV>One example I give is telemedicine. Telemedicine has not taken off = due to a=20 number of reasons that are slowly being overcome (such as insurance=20 reimbursement — people like to get paid). One of these, however is = having enough=20 applications and volume of use to make it worthwhile to spend the money = on=20 equipment, circuits, training, etc. I find that in many cases in Oregon, = that=20 smaller and more rural health care providers in particular may=20 have professional relationships with several different regional=20 hospitals/systems — pediatrics may have a relationship with one, = ortho another,=20 radiology, etc. It generally does not pencil out, however for them to get = a=20 video unit and dedicated or ISDN lines just for one application. However, = if we=20 can get the major hospitals to connect to one another there is the = possibility=20 of them all becoming accessible to the small, rural hospitals, increasing = the=20 value of the connection and actually resulting in greater demand for=20 telecommunications and Internet service. Combine this use, with the = ability for=20 the systems to trade traffic with one another (they tend to work a lot = with each=20 other, even when competitors) and the ability to promote external = contract=20 partnerships as well as access the highly reliable, affordable transit and = I=20 think you have a winning combination. Interactive video is also a great = example=20 of an application that doesnot work across a usual Internet connection, = but can=20 over a regional exchange if the participants are connected by networks = that are=20 properly engineered and the router hops are minimized as a function of = the=20 exchange.</DIV> <DIV> </DIV> <DIV>This same logic applies to lots of other concepts. Hospitals also = have lots=20 of external relationships with contractors (laboratories, interpreters, = clinics,=20 insurance companies), some of which could be done more effectively with a = high=20 speed/quality connection. Telecommuting (teleworking as I hear it called = lately)=20 critical mass becomes easier in a share environment, etc. I use the = generic=20 argument that today these kind of relationships, if networks are used at = all=20 require an "n-squared" (meshed) network, which is not affordable but that = a REP=20 can allow a hub and spoke architecture, which is much more affordable.</DIV= > <DIV> </DIV> <DIV>Another point. A REP can provide (we hope) a means to enable a region = to=20 attain critical mass to become a major location on the Internet.</DIV> <DIV> </DIV> <DIV>This is something we are trying to do here. Currently, Oregon is = basically=20 a stub off of the major networks. This occurred both because of size and = notably=20 proximity to Seattle and Northern California. Our hope is that by = greatly=20 increasing the bandwidth across our REP(s) that we can help cost-justify = the=20 major networks to increase their presence and in time to connect to one = another=20 here, moving us in effect closer to if not eventually on to the "backbone."= =20 (Yes, I know there is no "backbone" per se, the closest thing probably = being the=20 major exchanges) There are at least a couple economic reasons that we want = to do=20 this. First, having all the traffic leave town means that we lose the jobs = that=20 a more robust local Internet would provide — local sales and = engineers in the=20 telecommunications and networks companies. Second, it means that local = customers=20 pay a penalty to backhaul their traffic to major connection points. Third, = it=20 means that a lot of opportunities simply go elsewhere. Oregon has a large = tech=20 employment base and is consistently among the "most wired" communities in = the=20 world yet, if an Oregon company wants a really world class web site they = will=20 most likely host it in some city that is "on the backbone" in order to get = the=20 best performance and the lowest cost bandwidth.</DIV> <DIV><BR>Jere</DIV> <DIV><BR>>>> [email protected] 03/06/03 06:11AM=20 >>><BR>Hello All ....<BR><BR><BR><BR>It sounds like most of = the=20 technical aspects of REP's are being covered.<BR>I would like to start a = similar=20 thread about what is a REP, but from a<BR>business perspective.<BR><BR>Reme= mber,=20 for REPs to be fully utilized they must be able to speak<BR>to a wider = (and=20 paying ) audience, the enterprise, municipal government=20 and<BR>Universities.<BR>Not just service providers as we tend to see in = the MAE=20 model.<BR><BR>Who direct connects to a REP :<BR><BR>Municipal government,= =20 Universities and education, enterprise, application<BR>service providers<BR= >and=20 service providers.<BR><BR>>From a business perspective :<BR><BR>1). A = REP=20 forms the core of a Metropolitan Internet<BR>2). A Metropolitan Internet=20= provides transport for applications that are<BR>Regional.<BR>3). Services = is the=20 name of the game, these would be supplied by ASP's not<BR>necessarily the = REP=20 operator.<BR><BR>Regional Applications include :<BR><BR>1). Access to = multiple=20 Internet 1 providers ( cost reduction )<BR>2). Access to multiple = I2=20 routes. ( transport diversity )<BR>3). Access to regional video=20 distribution<BR> -Local University distance=20 learning<BR> -Local video conferencing<BR>4). Regional=20= disaster recovery ( public archival storage )<BR>5). Regional virus=20 protection<BR>6). A gateway for voice softswitch access ( a place for all = that=20 Cisco IP<BR>phone traffic to go to )<BR>7). Local higher speed content=20 services<BR>8). HIPAA compliance via a truly survivable geographically=20 diverse<BR>architecture<BR><BR>Dave<BR><BR>----- Original Message = -----<BR>From:=20 "Jere Retzer" <[email protected]><BR>To:=20 <[email protected]><BR>Sent: Wednesday, March 05, 2003 11:27=20 PM<BR>Subject: Re: [REPforum] What is a regional exchange point?<BR><BR><BR= >>=20 I think there is a continuum from local to global IP exchanges with<BR>regi= onal=20 somewhere in the middle. Local exchanges mainly peer to exchange<BR>local= =20 traffic in order to keep local bits local and save transit. Global<BR>excha= nges=20 mainly peer to tie together the global Internet. Regional<BR>exchanges = may=20 provide both local peering as well as access to transit, and a<BR>convenien= t=20 location for the major networks to peer with one another.<BR>><BR>>= =20 Jere<BR>><BR><BR></DIV></BODY></HTML> --=_D48B8061.D8B85F79--