Marcusq R
Marcusq R
Marcusq R
Exhibit Q
Case 3:06-cv-00672-VRW Document 294-2 Filed 07/05/2006 Page 2 of 58
Before the
FEDERAL COMMUNICATIONS COMMISSION
Washington, D.C. 20554
RECEIVED
In the Matter of 1
1
Petition for Declaratory Ruling that AT&T’s 1
PhonetePhone IP Telephony SeMces Are 1
Exempt fiom Access Charges 1
October 18,2002 -
1
TABLE OF CONTEXTS
PAGE
LYTRODUCTION AND SUMXIARY ..... ....... I
..RC.UXIEUT ....................................................................................................................... 22
CONCLUSION .................................................................................................................... 33
I
Case 3:06-cv-00672-VRW Document 294-2 Filed 07/05/2006 Page 4 of 58
Before the
FEDERAL C‘OMMUNICATIOYS COMhlISSlON
Washington, D C. 20554
ntling that tlic “plionc-to-phone” IP tclcphony services that A T & T offers over the Internet arc
c-tcmpt ti.oni the access charges irpplicablc to circuit switched iiitcrexchangc calls and arc
Iawlitlly bcins provided over end tticr local services. A T & T sccks this relief to t-c’~oIvc
actual
controvcrsicb \\it11 LECs over the applicability of interstate acccss chargcs to AT&[ scrvices and
to provide guidance to states who follow the federal rulc in asscssing intrastate access charges.
Protocol (“IP”) telephony scrvicc that A T & T and otlicrs arc providing over thc Intcrnct.
;\T&T‘s provision ofthew services rcqttircd i t to makc large invcstmcnts i n “common“ Intcrnct
1xickbc)iic fiicilitics that carry all types of Internet traffic, and A T & T ’ s investtnents a n d vcry
limited initial \‘oicc offerings arc csscntial prcconditiona to future ofrerings of the integrated
\ ‘ O I C ~ .d a t a , a n d multimedia serviccs Lhat IP allows. A T & T submits that [hc [LECs’ cfforrs to
Case 3:06-cv-00672-VRW Document 294-2 Filed 07/05/2006 Page 5 of 58
ilnposc access charges on this plione-to-phone Intcnict traffic violates: ( I ) the congrcss~onal
mand;itc to “prcscrvc tlie vibrant and competiti\;c free market that presently exists for ilic
Internct” and ( 2 ) tlic Commission’s established policy ot‘cxcmpting all voice over lnlcrnct
Protocol (“VOIP”) services from access charges pending the future adoption of
congressional policy of tosrcring the Internet if nascent and emerging Internet services were
rcqttircd IO pay Ihc access charges that are currently applicable to circuit switched iiitcrcxcliangc
services. I t I u s found that access charge rate structures are “above cost” and “incfticicnt” and
that it would distort and disrupt ltitcrnct scrviccs and investments that arc “still c\olving” if thc
w r \ ices were subject to these iiiilaled charges. rather than to rates that apply t o cnd user or other
local scr\ ices and that can fully c-unipcns~teLECs for all legitiniatc costs. Thcsc arc the rcasons
that thi‘ C’otiiniission i n s cxeniptcd all enhanced and informalion service pro\ idcrs (collectively
r c h r e d to as “ISPs”) I’rom the rcqtiirciiicnt that they pay access charges and has pel-niittcd them
For the same reasons, the Commission has treated a11 tlic nascent and emerging
V O I P telephone services as enjoying the ISP cxcmption until such t i m e as the industry matures,
;I full record is compiled, and thc Commission determines wlicthcr some form of;~cccsscharges
particular. the Commission lias repeatedly refused the ILECs’ entreaties that thc Commission
hold that phone-to-phone or other VOIP services arc required to order originating a n d
lcrnlinating acccss services and lo pay tlie sanie access charges applicable to circuil switcllcd
~ntcrcxchangccalls.
2
Case 3:06-cv-00672-VRW Document 294-2 Filed 07/05/2006 Page 6 of 58
Thc first such action was the Commission’s 1998 Universoi Semiie k q A J V f to
Congress. Thc Coinmission there tentatively concludcd that certain configurations 01‘ L‘OIP
scr\ iccs (coniputcr-to-computer and computer-to-phoiic) arc information scr\’iccb ;Ind that othcr
scrviccs arc provided over the coininon Internet (like AT&T’s service) or over iiitci-czciiangc
nctworks t h a t use Internet Protocol. But tlie Commission stated that the nascent services would
Iiavc to mahirc and a complete record would have to be compiled before i t could determine if
thcsc tcntatiw classifications were rational and sustainable, and the Commissioii dctcrred tlicsc
Most fundmicntall)~.[he Commission stated that even i f i t t1icrc;iRcr futind that a11
phone-to-phone IP telephony services arc telecommunications services that placed tlie “samc
burdens‘’ 011 tlie local cxchangc ;is do circuit switched intcrcxchange calls. it would 110t follow
that the IP scr\,ices would be subject to tlie .satw access chargcs that arc applicable to circuit
sivltclicd long distance services. Quite the contrary, the Commission stated only that i t “ m y ”
pay “.~iw7i/nraccess chargcs” and that the adoption of such a requirement would iraisc “difficult
a n d contested issues:” ’..p., whether there was a n “adequate” and technologically sustainable
hiisis I‘or “distinction” between plionc-to-phone and othcr VOIP services and whcthcI- the
eitlier opposed, or expressed gravc reservatioii about, subjecting VOIP and othcr innovative
IP services to tliesc and othcr regillations applicnblc lo circuit switched long distance sewice.
3
Case 3:06-cv-00672-VRW Document 294-2 Filed 07/05/2006 Page 7 of 58
The fdlowing year the C‘ominission thus rcfused even to entertain U S R:cst‘s
:\pril I909 pctitlon tor a clcclaratoq ruliny that access cliargcs apply to phone-to-photic IP
tclcphony scrvicch that arc n o t ofrcrcd over the Internet, but use I P in tlic intcrnal inrcrcxchangc
nct\vorks. U S W c s t had contended that these latter services arc subject to access charges as a
iiiattcr o f I J W because they are “tcleconimunications scrviccs.” and not information w r \ ices. But
tliis RP/JOU
was tlic same legal then17 that the Coinmission had rejected i n the Ci7iiewol Se~i,it.e
;ind the Coinniission did not even issue a Public Notice or otherwise rcquesl coiiinicnl on thc
I! S U’cst petition. In the ensuing years. the Commission has not clsewhere addi-csscd the
qydiciibility ~ ~ C C cliiirges
~ S S to phone-lo-phone I P tclcphony scrviccs.
ordcr inllated acccss service. thc Commission allowcd thcm to tisc cnd user local services that
arc Ipriccd closcr to tlicir economic cost. This has bccn tlie unifomi Ipractice ol’tlic many firins
ATKrT has clcctcd to use acccss scnjices to originate irs calls, AT&T has terminated its plionc-
tv-phone IP tclcphony services ovcr tlie sainc local lacilitics and services that terminale its 1st‘
tuftic: principally. privalz lines obtained tkom C L K s and ILECs. uilh tlic CI-F2C7stci.minating
IHowcvcr. failing
31.1~1 to obtain Commission rulings that providers o f
lplionc-io-phone Ir rcleplion!f services arc required to iisc access services, incunibcnt LECs arc
inow attcniptilig to cn‘ect end runs around tlic Commission‘s policy by engaging in uelf-liclp.
Bccause thcy ~ I I K taklng the position ihat Ihc business lilies and other local facllirics arc ;Ivailablc
4
Case 3:06-cv-00672-VRW Document 294-2 Filed 07/05/2006 Page 8 of 58
I P telephony services. (2) taking down local busincss lincs that they discover arc bcing used to
lci-iiiinate biicli calls, or (3) using Calling Party N u m b e r identifiers to assess intctstaic (;lnd
intr;islatc) ;icccss charges on phone-to-phone IP telephony calls that tcmiinate over rcciprocal
conipcnsatioii trunks.
Tlic unilateral nclions of ILECs have thus given rise to aclual contro\ci.sics ovcr
Plninly. only ;I ruling from this Cummission can resol\,c tlicsc conlrovcrsies. Furthcr. a fcdcIal
dccijion on lliis isstie is iniportant tor Ihc additional rex011 that i t will provide lcaclei.ship nnd
-uiiicl;iiicc to tlic states. Su1c commissions liavc recognized the importance o t u n i f o i - m rules
-.n\:crning cmerging Intcrnct and other s c n i c c s a n d have chosen to follow tllc tcdcral rule in
awxsli1cIiis 011tlicsc scrviccs. ,A declaratory ruling will allow states to acliicvc uniIbrmity.
,AT&T’s plionc-to-phone IP tclcphvny services are cscmpt lion1 access charges applicable to
Firsi. whatcvcr tlic case with the other “forms” of pliolic-to-phone IP telephony
scrv~ccs,the AT&T services at issue licrc arc provided ovcr thc lntcrnel and required large
invcstmcnls to upgrade Intcrnct backhonc facilities and to enable tlicni to carry high quality
Loice as \vel1 as data. The congressional mandate o f “prcscrviiig” a “competlti\c frcc market , ,
k11-the Intcrnct” dictates that providers oflnternct telephony services be pcnnancntly free to
5
Case 3:06-cv-00672-VRW Document 294-2 Filed 07/05/2006 Page 9 of 58
. .
d x a i n local x r v i c c s to vrtginatc. or terminate lntcnier traffic and be exempt from ri'qt~tremcnrs
tlial he!, oi.dcr and pay Tor access ser\;iccs provided at rates that arc above-cob! and ~ n c f t i c ~ c n t .
i i i t c i - c x c h a n ~ ct'ac~liticscising IP. tlic incumbcnts' sclf-help iiicasurcs arc InconsistcnI \vlth tlic
( ~ ' ~ i i i i t i i i s s i ~ 'i wt i a' ~i t and x c " policy ofexcmpting 311 VOlP services from above-cost r~cccss
cli;irgcs i i i i t i l t h e niarket had iiiaturcd and the Cornniission could coniprcltcnsivelq address the
proper r c f ~ i l a t o r yireattncnt o f t l i c i i i . This policy was sound - and remains so. Prcmat~trclyto
SlibJCct new tcchii<)logicsto iiiel'licicnt clinrges could block their developtncnt 311d risk iinIa\.r~fttl
t h a t iiiakc idciitical uscs oi'locnl cxchangc lor identical purposes. The Coninitssion should ratify
its ~ / c , , / ~ K / :iccc\s
o charge cxcinpt ion and foniially impose a moratorium mi x n y ;tcccs\ charge
appropi-ialc chargcs and that allov, llieiii prospcctively to bc nondiscriminatorily applied t o 2111
BJICKGROUND
R c ~ ( J vand
.Cc~~-i~icc. / the c o i i t c ~ i i p ~ r a ~stat~ineiits
i c ~ t ~ ~ of individual Commissioncrs. ( 4 ) Lhc April,
1')9c) U S WCSLPetition For a Dcclora~otyRuling, ( 5 ) thc IF' tclcphony services 11131 ATGLT and
competing provtdcrs no\v otter, ~ i i d( 6 ) tlic actions o t t h c incumbent LECs that give rise to tlic
Iprcscnr iicti~iilcontroversy.
6
Case 3:06-cv-00672-VRW Document 294-2 Filed 07/05/2006 Page 10 of 58
could have rcqLiircd all interstate L I S C ~ Sof local exchange facilities to pay the s a m e ~\\,itclicdpci-
iiiiiiute ncccss chargcs that appl) t o the circuit s\vitchcd s e n ices ol'intercxchangc carriers. I But
Ihc C'oniniission 1x1s refused to do so. Iiistcnd, it has sivcii providers of enhanced ;ind
infoi-mation scr\.iccs ("ISPs") the oprion ol'acting as end users and subscribing to ll;it-i.atcd
1
business liiic and other local end USCI- services:
iitc~stircIllat would protect the tin;incial viability o f t h e [lien-Hcdgliny ISPs and that ivould
Tclccutntiitinicntioni. Act ot 1996. [he Commission found that tlic cxcniption scrced inorc
I'tindnmcnlal purposcs atid t h a t it should apply permanently. pending tlic adoptioii o l ' i i c w tkderal
I n Ipirticular. tlic C'oiiimissioii noted that "hnd access ratcs applicd to IS& ovcr
llic past 14 years, tlic pace ofthc dcveloprnciit of the Intemct and ollicr s c r ~ i c c smay IIUL Iiavc
I k c n so mpid."' Tlic Commission iiiadc the exemption pcrninncnl on tlic ground tliiil i t would
pwtect cnicrging and cvoI\ tiis technologius liom thc advcrsc effects of uticcoiioiiiic charges and
\ \ ~ o u l dadvancc ~ l i cI996 .!,ct's policy ofprcscr\itig "'thc vibrant and compcliti\,c t'rcc market
' .Sei.e.?.. ,L!TS irud M'ATS ,Lltrdcr Srwclwi, 97 FCC 2d 682, 7 77 ( I 983) (statins t h a t tlic
Commission's "ol>.jcctivc" undcr tlic Act is "distributing the costs ofcxchangc ;~cccss i n a fair
:ind rcasoiiablc nianiicr among all ~iscrso ~ a c c c s scrvicc. s irrespective of their designation as ;I
carrier UI' private custonicr"). 111 h i s regard, d i e Commission's historical (and rlic IOU6 A c t ' s )
clistinclions bct\vc.cn tcIcCoiiitiititiiCatioiis carriers and enhanced and inlbrmatioii scrvicc
providers ("ISPs") dcterniiiics wlicthcr these services are to be regulated. and i t is iri-clevaiit to
iltc qucsitoii of what c a d i provider pays for local Cacilities that originate and tcrmirintc lllcir
scr\jiccs.
S1.e /d.
.%e ;<I.
1
c'hf:ee / < i / 0 ) . ~ ? 7 , First Report and Order, 12 FCC Red. 15982. 7 344 ( 1 997)(~~,4cc.cs,v
C'/io/peRe/o/-ni").
7
Case 3:06-cv-00672-VRW Document 294-2 Filed 07/05/2006 Page 11 of 58
tliat presently Cxists for the lntcrnei a n d other interactive computer services.’”i 111 particular. it
twicd Ilia1 while i t 11~1sreformed acccss charges, tlic), continue io he “noti-cos! hascd alid
incffcicnt” and that i t could have detrimental illid disruptive effects to cxtcnd thi: cliarfcs LO
itiforn~ationscri ices that wcrc ‘.still The Commission also rcjcctcd claiiiitr illat ilic
and noted that local service chargcs could fully compensate LECs for the legitimate ccniiomic
costs Ihcy incur in providing their tjcilities.’ Finally. the Commission stated that “ i t IS iiot clear
tliai ISPs tisc the public switched network in a manner analogous to IXC\”.’ and thc Coiniiiission
itistthitcd a procccdinf to considcr “iicw approaches” and nltcrnnlivcs to acccss cliargcs fur ISPs‘
Tlic Court o t Appeals for the Eighth Circuit upheld tlic permanent ISP cxcinptioii
atid rcjcclcd the claim that ii gcncrically gave risc to unlawful discriiiiinntion bctwccn lXCs a n d
ISPS.’”
2 . The Internet And VOlP Tclcpltonv. The public lntcrnct is comprised of's
iiunibcr ot‘lntcrnct “hackbonc” lacilltics that all liavc wcbsites connectcd t n them iiiicl Ilia! ai-c
.I\l’&T Bruadbaiitl arc liitcrncl Scrvicc Providci.s, and ATXrT owns ;tiid operatcs one o t t h c
wurld’s Inrscst “coiiimoii” Iiitcrtict backbone Ihcilitics. I t carries tlic traffic ofA-T&T’s lSPs and
8
Case 3:06-cv-00672-VRW Document 294-2 Filed 07/05/2006 Page 12 of 58
9
Case 3:06-cv-00672-VRW Document 294-2 Filed 07/05/2006 Page 13 of 58
do v>for 1111‘ lbi.csccahlc t‘uhirc. invcstnicnts to alIo\v quality voicc over IP ~ mid tlic c x p a n s ~ o n
;dlo\ving \ oicc and data to b e transmitted w c r a single inel\vork. thcsc in\csinicnts call produce
ciioimotis ct‘tlcicncics by allo\ving the intcgratcd provision o l n n array ol’voicc. data and
11
cii1i;mccd scr\,icc<. But these ftiturc scrviccs will not dcvclop unless pi-ovidcrs tii.st dcvclop tlic
cqxibilit!, to offer high qtialily \,(lice services over Internet backbone facilities or otlicr
11’ iict\r,c>iks. and tliat rcquii.cs t h a t tlicrc bc a n initial economic reason t o make the ncccssal-y
i i i \ , c s t i i i c i i l i . ,A I-LIIS
~ 1 i a iti t i ~ l i o r i i c sC’OIP providers to subscl-ibe to local scrviccs. iratlicr h a i l
;ib(ivc-ccisi ;~cccsscharges, can provide tliat economic rcason until .\uch time a s cnhanccd \ o i c c
I’
caii be pro\,idcd o w r tlic upyraded IF‘ I>ciliric.s.
Rc+nnins ill the iiiid I 000’s certain fimis began to make invcstmcnts tliilt crcatcd
Ilniilcd capacit!’ to pro\.ide quality \,oicc scrviccs ovcr the Tntcrncl o r otlicr nctwxks wins
d ~ a l c dplioncr. tioin phones tu phones, or tiom phones to coniptitcrs by tiriny the “galeways”
protocol.
For cyaniplc. n plionc-lo-plionc IP ciill \vi11 travel o\’cI- tlw public s\\,itclicd
Ilitcrlict hackbone to a tcrniinatinp ytc\vily. whcrc it i s convcrtcd back to voice and w i t over
10
Case 3:06-cv-00672-VRW Document 294-2 Filed 07/05/2006 Page 14 of 58
local cscliange tliciliiies to tlic called party Tliesc c;illb arc s e n t and rcccived it1 L o i c c (TDM)
protiicol. and cffcct no iict chanfe iii format. Tliesc scrviccs can he offered throuzli ti\'o-st:igc
diuliii: aimngcmc'nrs in wliicli tlic callcr dials a local or SO0 number 10 rcacli tlic g a t m t i y ;Ind
t l i c i i dials tlic Iplioiic intimhcr of llic called party. Or thcy ccin be ott'cred through al.reingcmciits iti
\\ l i i c l i tlic pro\,idei-sLibsci.ibcs to a i oi.iginating Feature GI-oup D access sci-\,icc and :iIlo\\,s ilic
\iihscribci- to placc calls h!) dialin$ I plus thc called party's nuiiibcr.
~ 3 1 1 s .and iill coiiipiiter-to-plioiic I P cLi11s iisc the same rermiixiting facilitics as phone-tu-phone
iiills. i;(ii. cyaiiiplc. i l ' a cniiiliiitcr ti\cr lieis a dial-tip cunliguratioii, she. too. wnkild d i l l citlici- an
X O O iiilnibcr 01. ;I loci11 ntimbcr to rcncli the gale\vay tu tlic IP network and would thcn dial tlic
..
~311cdp;il.l!,.s nLiiiibcr.'i Hciwc\ ci.. hccatisc t h e originating PC converts tlic signal\ In IP. no
lptoiocol coiivci.sioii CI~CLIIS in tlic origiiiatiiig pa[cway. and this i s the only ncccssai-y diftkrciicc
;ind all computer-to-iilioiic ccills iirc tcrminated i n identical ways. i n identical III.O~OCO~S. iind w e r
iilciitical loci11 cscliangc tacilitics. Wlicthcr [lie c a l l I S translatcd into I P iii [lie iwiyinatiiig
CoiiipLitci. ( a s iii n comptitcr-to-pliiinc call) o r iii the cirisinatiiig gateway (as i n ;I I'honc-lo-plionc
call). illc I P piickcls I\ ill bc rmrtcd oi'cr Ilic IP rictwork. converted back to \.oicc signal Iii-otoccil
(TDM) i n tlic !cmiincitiiig $atcway. :itid routed to tlic callcd party over Ioc;il exchange h c i l i t i c s i n
Ilictr compuicr to tslcplioncs coiinccicd to the public sn,itcIicd nctlvork or from o11c tslcphonc to
..!&,
:iiiolhcr.
But the K q x w / addrcsscd tlic classilication of only tlic t\\o types 01' \'(I1P
contiguratioiis in which tlic LP network cffccts no changc i n protocol or format ~ i i dthat cicarly
coiistilt t t ~ s : ~ compiitcr-to-compitlcr
' ~ l c I c c O t i i t i i u i i i ~ i l l i o nllic ~ calls (that cntcr and c \ ~ tlic
t net\\ cirh
iii lP) iiiid the phone-to-plione cnlls ( t h a t cntcr and exit in \oicc (TDM) protocol).
out :is pi.ci\,idiiis tCIcCoiiimtinicniiuiis and may 1101 c v c i i be aware that tlicir s c n ICCS :it-c used tor
'I)
tc1ccotiiiiitiiiic;iLtI)iis. Tlic /?qxw/ did 1101address tlic ccinipiitcr.-to-c.otiipiitcr c a l l s llial ttsc
c;ip;ibilitics that iirc nctivcl!, marketed or proniotcd by lSPs or othcr scrLicc pi-cividcr~.
" ~ ~ / i o i i c - ~ ~ ) - ~ IP
) l i Iociliccp h o n ~ . "\\,hiel1 i t dctined ab scr\,iccs: ( I ) iii \viiicli tlic provider Itvlds
ilscll'out ;I< prwidiiig tclcpliony. ( 2 )\vIiicIi iisc tlic simc CPE a s ordinary photic c a l k . ( 3 ) w h i c h
c i l l o ~ctisIoiiicrs
v to c~illtclcphonc numbers :issi_:ncd in ;tccordaiicc wit11 the Noi.tli .\mcrican
-1
iitiiiibcriiig plan. aiid (4)\\hie11 Lr:iiisinit intoriii;ilion without chanyc iii coiltent 01' l?iriiia.- The
\CILICCS.
13
Case 3:06-cv-00672-VRW Document 294-2 Filed 07/05/2006 Page 17 of 58
Case 3:06-cv-00672-VRW Document 294-2 Filed 07/05/2006 Page 18 of 58
Case 3:06-cv-00672-VRW Document 294-2 Filed 07/05/2006 Page 19 of 58
Case 3:06-cv-00672-VRW Document 294-2 Filed 07/05/2006 Page 20 of 58
17
Case 3:06-cv-00672-VRW Document 294-2 Filed 07/05/2006 Page 21 of 58
IS
Case 3:06-cv-00672-VRW Document 294-2 Filed 07/05/2006 Page 22 of 58
number. so orizinating access clinrgcs a l e paid on tlicsc calls (~LISI as they w i - c p a ~ don tllc
Coniicct-U-Save calls that used 800 access). But as i n Connect-N-Saw, AT&T docs iiot order
~ i c c c s s\cr\,iccs lo terminate these calls, but tcmiinates thein over CLEC or ILEC local husincss
liiic!,. with llic CLEC terminating tlic call o w r rcciprocal compensation trunks it’tlic called party
i \ a n ILEC’ cListonicr.
Some ot’thc lraffic that ATSrT is routing tlirough this a r r a n ~ e n i c n lconsists 01‘
cnlianccd >crviccs: prcpaid colliiig c x d services that includes advertising aiiiioiinccmcnts. This
traffic \vas ul’lL-rcdon a non~ariftcdbasis prior to t l ~ cAugust I , 2001 effcclicc datc oftlic
li
I . balaiicc ofthc traffic that uscs this IP triiiisinission
C o i i i m i s ~ i o n ’ sDrrtrr.!J/iiigO I - ~ C J The
passes 1111: Calling Pa$ h’iinibcr (‘.CPN”) on both types trt tral‘fic.
6. The Contrtxersv Over Interstate Access Charqcs. When AT&T had initially
I-ollcd o i i l i l i phone-to-plionc \)01P sersiccs, i t had intended to tcrminatc the calls 111 local calling
rcqiicstcd P R I facilities and have b c y n asscssiiig krininating ;icccss charges 011 the altcrnatlvc
arraiigcmcnts that AT&T liiis proctircd. Other LECs provisioned the PRI facilitich. but
subsccltrntly rcfuscd to Icmiinatc VOlP traffic over them and havc tlircatcned to disconnect tlic
Case 3:06-cv-00672-VRW Document 294-2 Filed 07/05/2006 Page 23 of 58
facilitics uIiIcss AT&T removes its VOIP traffic from them and orders access scr\Jices to
trmiinatc it.
For examplc, when AT&T ordcred these local exchange facilitics ill Virginia,
Verizon refused to provision the facilitics as AT&T requested. Verizon took the position that
although AT&T could order local busincss lines to tcrminate traftic that originntcs on colnputcrs,
AT&T could lint do $0 on VOIP traftic thai originates on ordinary tclcphoncs. ATXT rhus
iiistcad ohtaincd private lines from its local service ann and other CLECs, who would dircctly
tcrminatc tlic enhanced and hasic voice calls io thcir own local subscribers and would tcmiinatc
calls to Vcrizon's subscribers over rcciprocal compensation trunks. AT&T thus wonld pay
local bMiitclies and loops, rather than paying abovc-cost access charges.
Besinning ar thc end of last year, Verizon bcgan cxarnining thc CPN on calls that
Icniiinatc on these rcciprocal compensation trunks and began asscssing LICCCSSchat-ges 011 crrtaiii
of thc calls based o n their CPN. It has thus billcd AT&T for interstate access charges on certain
calls and tot intrastate access charges on others, while charging local reciprocal coinpcnsation
cli;irges only on calls with local CPN. The calls on which Verizon has assessed interstatc and
intrastatc ;icccss cliarzes include the prepaid calling card calls that arc cnhancrd scrvices as wcll
:is phonc-to-phnnc IP tclcphony calls. AT&T has adviscd Vcrizon that it is disputing all these
charges. ;ind that AT&T will be entitled to a refund of thc full amounts in question (plus intercst)
if and wlicii thc Commission grants the declaratory ruling that AT&T is here requcsting.
Other iiicunibcnt LECs have thc capacity to examinc the CPN on cslls terminating
on reciprocal compcnsation trunks or ollier local facilities, and AT&T understands that they, too,
I i a w b c p n to cxamine CPN on this traftic.
20
Case 3:06-cv-00672-VRW Document 294-2 Filed 07/05/2006 Page 24 of 58
calls o\'cr Sprint local business hncs in Tallahassec, Florida. Indccd. rathcr than continuing to
icrniiiiarc these calls. Sprint initially hcpan to route ilic calls to'.dcad air," forcing ATKT to
i.c-i'oute traitic to avoid call disruption and adverse customer impacts. and Sprint had tlil-earencd
io disconiiccr the circuits unless A T & T axreed to move all this traftic o f l o f t h c m and unto
;icccss circuits. Sprint tlicn llircaieried to disconiicct circuits in other arcas as \uclI. \L'licn AT&T
:I hillilig disptitc iii which il clninis 1hat ;iccess chargcs apply to this Iraffic.
coiiiiiiissions. incumbent LECs ha\ c contended intrastate access chargcs can bc iiiiposcd on
;ind othci. ciiierginf services. statcs iavc generally li~llowcdthe fcdcral rule appliciiblc to
111 proceedines undcr $5 251 and 252 u f t h c Act, two statc PUCs have declined to
('olorado PUC has held that incuinbeiit LECs m a y not asscss switched :ICCCSS cliatgcs a h
compcnsntion for the use o f their iictcvorks 10 terrninatc phone-to-plioiic IP tckpholly m L i C c s . "
S i i ~ i i l a d y .(he Florida PSC tias iiotcd that this Commission has dcfcrrcd the question of t h ~
:ipplic;~bIlity ofacccss charges to this tl-atfic to future proceedings and decided. o ~ c BcllSouth's
r
21
Case 3:06-cv-00672-VRW Document 294-2 Filed 07/05/2006 Page 25 of 58
ohicction. that It ivould not address tlic question whether access chargcs should apply to
(NYPSC) held tliiit providers of intrastate phone-to-phone IP telephony scrviccs arc i.ccltiircd to
i c l i ~ p h o n yprcn:idcr had tlierc contcnded that lhc assessment of access chargcs w a s contra1.y r o
Icdcral Ipilicics. \Yliilc tlic NYPSC undertook lo follow federal policy. i t reviewctl llic
tliiln an inl;)rmation o r cnliaiiccd service under fcdcral l a w Ironically, tlic NYPSC' iclicd on tlic
tclcphony pro\ iders pay '.similar" access charges in fittiire proceedinxs. The NY PSC ignored tile
('oinniission's use of 11icc~udifyingword "may." its starcIiiclit that the issucs would bc " difficult
;ind contcstcd."4" and Its st;itciiiciit tliiit ;iccc'ss chargss would only hc imposed in tlic tuturc. By
Contrast. Texas PCIC Chnirniaii Patrick IVood had rcad this language as tlic Commission's
47
holding tlial VOlP scrviccs will inot be subject to access charges.
ARGUMENT
22
Case 3:06-cv-00672-VRW Document 294-2 Filed 07/05/2006 Page 26 of 58
Foremost, incumbent LECs 11aw crcatcd a controversy over the applicahilily nt'
failing to persuade the Commission 10 declare [hat providers of thcsc scrviccs must ordct
intcrstatc iiccess scrviccs, iiidividual incutiibeiit LECs havc begun to refuse propcrl) 10 Iprovision
cnd Liscr scr\,iccs to terminate tlicsc scrviccs. to rcfusc to complcrc calls over tacilitics tliat were
lire\ intiill provisioned, and to asscss interstalc acccss charges on calls from other statcs t h a t arc
lhti2inz this petilion for a dcclaralory ruling that interstate access c h a r y x cannot now be
~sscsscdon t h i s traffic and that 4T&T i s lawfully terminating the traffic over local business
lilies. Accordingly. a declaratory iuliiig i s liere required to resolve a n actual controverby tliat i s
leadership and guidance to states. w11o rccogntzc t h a t uiiiform rttlcs should go\ ern t h e
a n d \vIio Iiavc cndcavorcd to follo\v the federal rule in dctcrnmining the applicability ~~t'iiitrastatc
; ~ c c c s scharges t u In(crnct and othcr such traffic. That tlic NYPSC lias rcnchcd a diffcrcnt
t i 111ciipplicablc lkdcral rille iliaii havc two other statc cominissioiis widcrscorcs tlic
c o ~ ~ c l u s i o011
tiwd Tot- ilic Cnmmiasioii to cxcrcisc leadership on this issuc and to clarify the ticdcral rule.
23
Case 3:06-cv-00672-VRW Document 294-2 Filed 07/05/2006 Page 27 of 58
As dctailcd belou. tlicrz arc two scpamtc rcasoiis \vhy tlic ILECs’ ;iccebs clial-gl:
ithc liircmct Protocol. ,AT&T‘a IP-based scrvices arc provided over tlic Iiitcrncr ttscI1’. The
ltitcriict IS comprised o f t h c \,at-ioity “cotiitiion” Intcrnct backbone facilitics tliitt arc conncclcd to
\\,chzitcs i i t i c l that :ire iiitcrcoiinccrcd t o one anothcr tlit-ou!ji pcering arraiigciiicnts. Tlic calls a t
i s w c ai-c traiismittcd ovcr tlic wine “cotnnion” Internet backbonc facilities that cnl’ry ISP and a11
otlict. typcs o f p i h l i c Internet traffic. And, as dctailcd ahovc. the provision o f \ ’ O l P scrvtccs
ovcr tlic Ititcrnct I-cqtiircd ATGiT to makc large invcstmcnts in 1P technologics t l i i t t Lipgritdcd i t s
ol’qunlity tliat Iiaw bccii pro\,idcd b y .4TSrT’s circuit suitclicd Ion2 dislancc neIwol.k. Tlicse
\ oicc, data. and enhanced scrviccs 011 ill1 integrated basis - and ATSrT i s iiow pro\ tdii~:
ttpgratlcil Ibcilitics. Voice \cr\,icc i n s inow bcconic otic IP application ot’ATJtT.5 Inlcrnct
hackbonc. aiid (lit in\csttiiciits L\ ill ;tIlci\\~ a range offuturc ititcr;icli\,c VI)ICC and otlicr cnhanccd
xwtcc>.
c a ~ i i i o rbc applied to phonc-to-pllolic tclcphony services that arc transmittcd ovct- tlic Intcl-net
ilsclt‘. Ll S \Vest i . c c o y i x d this point in i t s A p r i l 1999 pctirion for a dcclaratow rilling. Thar
Case 3:06-cv-00672-VRW Document 294-2 Filed 07/05/2006 Page 28 of 58
petition csprcssly cxcludcd calls that arc transmitted over t h e Internet froni its dctinitioii o1‘thc
~ I c v c l o p i i i c nof~ thc Iiitcrnci ~ l i a n~\:otiId ;1 rule h a t prohibited lntcrnct scrviccs tiom using local
scr\ ices to i - c x l i end iiscrs and 1ha1 rcqtiircd that they pay tlic access charges t h a t have bccri
l h i i d Lo l i n e riitc stiucturcs that arc “above-cost” and "inefficient.""' That would be llic
cquiLalcnt ol‘a Lax nil tlic Iiitcrnct, aiid would bc flatly contrary to the congrcssioiial dccrcc that
11icCoiiiiiiission ”preserve tlic free aiid coinpetitivc market lliat presently exists for tlic Iiitcriict
i i i i c l ~ t l i c riiitcmctivc comptitcr scr\ ices, tinfcttercd by Federal or state regulation.”” A frcc and
coiiipctili\’c markc1 is one in w l i i c l i providers arc frcc 10 subscribe to services that arc efficient
aiid arc not ai-titicially required hq’ regulation to ~ i s cscrviccs that havc rate structures that arc
clcarlq contrary IO the policy that tlic Corninission 113s lollowcd over tlic past tivc y c m Tlic
Commission hiis t‘ollowcd a “w;ii[ and see” policy iii whIcli all iiascciit ~ ~ l r o n c - t o - l d ~ o i i c
25
Case 3:06-cv-00672-VRW Document 294-2 Filed 07/05/2006 Page 29 of 58
JP tclephoiiy 2nd otlier L'OIP scr\,iccs \Yere lreatcd as excmpt froin access cliargcs ;II ]cast until
the scrb iccs had iiiatured and t h e Commission could consider the proper trcatmcnt ot' them 011 3
kipply to .'ccuraiii lornis" of tlicsc scwices and could adopt rules that allow their
This is a policy t h a t tlic ('ommission had previously bccn nblc l o Ixirsiic througli
the simple device otrcpcalcdly refusing the incumbents' requests for a ruling l h n t Iprovidcrs of
pIioii5-t1)-lilioiic 1P tclcplioiiy scr\ iccs arc required 10 order originating a n d terminating acccss
bcrviccs and to piiy acccss charges. I n parricular, the refiisal to dccide the issue Itad ~ until
i-ccently ~ meant the providers of phone-to-phonc and other VOIP services could. and did,
(iriginalc nnd tcrininntc their S C I ~ \ ~ I C C Sover end tiscr local services and that thcy all cnjoycd the
IIOV, ~CSIII.IC~ to sclt-help, dcnicd cnd ubcr services to phone-to-phone IP tclcphony pro\.idcrs.
and unilaterally asscssed acccss cli;ii-go, !lie incumbents i a v c lbrccd thc Comiiiission to address
tlic ISSLK expressly. I t shoLild n o w do so by lbrrnally ratiryiiig the policy it has long tollowcd inid
hold tli;it IF' XI-\ iccs \vi11 he itnmunc froin ; ~ c c c s scharges tinless ;ind until tlic
1~lioiic~Io-1plioiic
C'omniissioti adopts i.uIcs t h a t provide {'or prospective asscssnieiit ol'tlic clinrgcs 011 some or all
of thcsc wi.viccs.
Thcrc arc niultiplc. cotupelling rcasons h r thc policy that the Commission lhas
long lollowcd. Thcy all dictatc tliiit llic policy now be forinalized i n il Commission ruling that
26
Case 3:06-cv-00672-VRW Document 294-2 Filed 07/05/2006 Page 30 of 58
bars rlic self-help iiicasitrc'r o f tlic incumbents and exempts all VOlP s c n i c c s from access
rcprcscnt a tiny fraction ( b c ~ w e c i il ' %and 5%) of interexchange calling." Tlicy tis< t i c u IP
rcchiiologics that a l l o w packet s\vilclied data networks to provide voice sci-vicc\ i ~ l ' aqualily
i i i t i o \ ~ ~ i i iiiictliods
\c of pricing slid provisioning these services. To preiiiaturcly SII~~CCI
;ind a l l their ;Ittcndants cobts. could stifle innovation and competition, tor a l l the reasons that
..
C'liaiiiiian Powcll identified iii l i i s concurrence to the Urfivrr.vn/ Service RejxJrf.''
hi this rcgard. evc11 i f i t wcrc clear that thcse new IP-bascd scrviccs w i l l
c\,cnltinlly hccomc no morc tliaii substitutes for circuit s\vitcllcd Ions distance scr\:iccs ~ LIS it
p i ~ c t i t l yi 5 1101. scc i,7fizr - tlic Conimissioii should aIlo\v t h e services to cstablisll tlicniscI\,cs a n d
10 iniiturc bctbtc sub.jecting them to tlic above-cost and inefficient access cliargcs that ;ire
SLxond, J P Iclcpliony scrvices arc s t i l l evolving. and thcy hold tllc ptmtiiisc to be
i i t t i ~ ~ C t i Oofupgradcd
ii I P facilities i s not the provision of stand-alone voice scrviccs. but tilc
Case 3:06-cv-00672-VRW Document 294-2 Filed 07/05/2006 Page 31 of 58
ititcgratcd provision of Loice. data. and cnlianccd services." This is retlectcd. i n p x t . i n tlic tact
111a1 sonic of tlic \,oicc scrv~ccsIlia1 AT&T provides civcr IP today arc cnhanccd pi-cpaid C J K I
mcrcly cme application of a n i n t e p t e d voice. data, and cnlianccd services platform. Tlicsc arc
~poiii~s
that 1111: Florida PSC cit1:d in following the Comiiiission's lead and deterring llic ~ s s t ~o fe
5-
I h c applicability of access c h a r y s to plio~ie-to-phoneIP l r a f f i c to future p r o c e e d ~ ~ ~ g s . ~
scvcrc discrimination that will distort competition among dilleretit services thal LIX the same
IP rcchnologies and that have far more iii co~nnionwith onc aiiotlicr ilian they do wit11 circuit
sbitchcd intcrcxchange services. Thc Cf17ive/:ctrlScr.ike R q w f made this v e v point iii dclkrrinp
ilic q i i c ~ ~ i ~\vlictlicr
in\ "cci~taiiiforms" 01 phone-to-plionc I P telephony services sliould pay so11ic
tcI~.~~inmiitiications
s c r \ ~ ~ c c sA. s (lie Coiitmission cinphnsizcd, the distinction tlial the
28
Case 3:06-cv-00672-VRW Document 294-2 Filed 07/05/2006 Page 32 of 58
i'J /i/. 7 87
l ' ' ) Id. 4 00.
anlong them by I-cqttiring a11 or some IP telephony provtders to pay access charges and by
ilocs n u l htrn on lhe distinction bct\4,ceti phone-to-phone and other services, but rather oil
\vhethcr ditfcrent providers arc using idcntical facilities "in the sainc way [and] fot- ~ h sct i i i c
..h?
]pLll-posc'-
~ l i s c r i m i i i a t i c ~siiioiig
ti coiiipcting scrviccs and the resulting marketplacc distortions."' Hcrc. the
11cci\i\c kicl i s that all lypcs o f VOIP providers compete w i t h one anotlicr through IP
tcchnologics. ;ind tlicy a l l use identical local exchange tacilitics for tlie same piitposcs. Most
starkly. ;ill phonc-to-phone and computer-to-phonc scrviccs arc terminated in prcciscly the same
\yay. for they all route trafiic iii voice (TDM) format from the providers' lemiinaLinf gateways I n
(34
callcd pai-tics o \ cr circuit \\r,ikAxI local exchange ficilities. Yet tlie i n c u m b e i i ~ s\vould IISSCSS
~ c t - r n t n a t t ~;icccss
ig charges on Xr&T's plionc-to-phonc scrviccs but 1101o n cotiip~ttcr-to-plioiic
scrviccs. Beyond that. there arc also 110 material distinctions in h c uscs ot'lnciil f x i l i l i c s b y n ~ 7 ~ '
that \vi11 assure that particular IP providers arc not saddled ~ i t ldiscriminatory
i cliargcs that do
tioi apply t o conipclitors. The w:iy to achieve this fundatncntal statutory objcct i s not to allow
c l i x i - i t i i i tintory asscssiiientn bascd on ilic tentative distinctions iii tlie b/7Iver,sd .SC,/-IWC,R ~ p ~ ~ l - 1 .
Case 3:06-cv-00672-VRW Document 294-2 Filed 07/05/2006 Page 34 of 58
but to : i I l m ~ all VOIP providers to cnjo) the ISP cxctiiption until the Commission can compile a
cvinplctc record, determine thc scrvices tliat should and should not bcar access cli:Ir:c>. alid
adopt rules that assure nondiscriminatory a s ~ c ~ s i n c r iot Cs wliatcvcr charscs a1.c approprlatc.
Torn131 ~ i t i l i c a t ~ oofn the policy that tlic Commission lias followed for the past years \vi11 iicliicvc
that end.
complctc rccord. tlic Coinniission iiis rccognizcd that i t would also bc exceedingly "ditlicult." it'
1101 impossible. h r access chargzs t o he iiondiscriiniiiatorily assessed against cvcii a11 providers
hi
of'plionc-to-plioiie IP telcphony services. In particular, the Rcyorl identified tlic difficulties o f
innny firms providing only basic phone-to-plionc 1P lelcpliony liavc had 110 rciison to track or
/pass C a l l i n g Party Number. there often i s no basis to idcntify the calls to w h i c h :~cccsscliargcs
cuiild apply or w e n reliably to cstiiiiatc the pcrccntngcs 01iiitcrstatc and inlrastatc LISC on tliosc
cnlls tli;ii arc clcarly tclccomiiiuiiications sci-vices. Plainly, i t would b c pcrvcrsc i M T & T ' s
V O I P scr\.iccs could aloiic be singlcd out Ihr access cliargcs bccitusc A T B i T passcs CPN.while
othcr 1pr11\idcrs ~t plionc-to-plionc IP rslcphoiiy services would bc csciiipr Irum tlicsc cliargcs
un!innccd a s well as basic services. For examplc. ATBiT's cxisting VOIP scr\Jiccs incltide
c.iilinnccd prepaid calling cirrd sci-\,icescis wcll as basic Loice scrviccs, ;ind AT&T's scI-vicc could
be cxpniidcd to include othcr cnlianccd scrviccs and to tightly intcgratc the basic voice and .
31
Case 3:06-cv-00672-VRW Document 294-2 Filed 07/05/2006 Page 35 of 58
cnlianccd services. Similarly, oilier VOW providers (c.x.. Net-2-Plionc) offer scr\,iccs t h a t can
calls (which h a \ e k e n held not to bc tclcconimunications services), and there Iias b L- L l l 3 110
occasion to de\ clop mcthods to track the information that would permit detcmiinations o r \ v h i c l i
arc not su1,lcct to IICCCS\ chnrpes. The practical difficulties of making notidiscrimin~itor~~
;ICCCSS
cliarfc iisscssmciils providc a tiitthcr reason for il rulc barring tlic imposition o f acccss cliargcs
on a n y \'OlP pi-ovidcrs ~ i n t i lrulcs can be adopted that will allow the prospective
Finally. the adoption of 3 rule that ratifies the longstanding de,lircto ISP
cxcniption foi- all VOlP sci.viccs \rill cause no cognizahlc hami to incumbcnts 01' to a n y objcctivc
of'thc IC!.Fii-st. quile apait froiii tlic f:icl VOW rcpresents a tiny fraction ofiiitcrc~xcliii~i~c
c:~lling. tlic Commission Iias re.jxtcd the claim that end user charges do not liilly compcnsate
h-
~ncumbantstor all Icgitimale costs. I n this regard. AT&T is either t c m i i n a t i n ~c:rIls ovc1' local
pri\j;ile l i n e s or I ~ t ~ s n i c slines
s obt~iinedfrom ILECs or obtaining Iliesc facilities from CLECs and
rcrminatnig calls to ILEC custoiiicts over rcciprocal conipcnsation arrangcnients to which cost-
bascd n t c s apply. In eithcr case. tlic lLEC is compcnsatcd either through AT&T's paymcnls for
ILEC' flat-rate local privatc lines or business lincs purchased undcr end user tariffs 01- tIiroLigIi
tcciprocirl compcnsation payments Ironi the CLEC to the I L K Furthcr, tlic nonpayment o f
:~cccsscliargcs has n o advcrsc clt'ect on universal service. AT&T pays universal scrvice s~ipport
pilyliicfils on the rcvcnucs from a11 its non-cnhanced VOIP calls that i t carries over Intcrllct
32
Case 3:06-cv-00672-VRW Document 294-2 Filed 07/05/2006 Page 36 of 58
xrviccs
I n short, tlic Commissioii should fomially rarify the policy that il has tclllnwcd for
[lie past fivc years ofcxcmpting all \'OIP services from access charges until such lime its rhc
C'omtiiissioii comprehensively rLvicws thc evolving ssrvices. dctcmiines the appmpriarc charpcs
tlia! dioiild apply to them. iind adopts appropriate prospective rules that allo\vs ilicit
CONCLUSION
FOI.the reasons stared. the Commission should enter a dcclnratory I-tiling that:
( Ij L'OIP scrvlccs that are carricd o w r llic Jritcrnct are pennanently entitlcd IO subscribc to local
xrviccs atid cxctnpt from a n y rcquirenient that they subscribe to iicccss services or pay
; i h ~ i \ ~ c - c o sacccs\
t charges. and ( 2 ) all o~licrphone-lo-photic 1P and VOlP tclephony s c ~ ~ v i c arc
cs
excmpt ii-om ;icccss chargcs utilcss atid i i i i t i l thc FCC adopts rcgulations t l i a l prorpcctlvcly
RcspcctCully s~ibmtttcd,
'sr M a r k C . Roscnblum
David I+:. C;irpcntcr Mark C . Roscnbluin
Sidlcy Aitstin Brown 8: Wood Lawrence J . Lafaro
Bank Oiic Plaza Judy Scllo
I O S. Dc;irhorii AT&T Corp.
C'hicag. Illinvis 60603 Room 3 A229
( 3 I 2 j 853-7137 900 Route 202/206 North
Bcdniiiistcr, New Jersey 0792 I
Davtd L. [.awson (908) 532-1846
lulie M.Zainpa
Sidle) . A t ~ ~ I iBrown
ii &. LVood L L P
1501 K Strcct. N . W
li'iisli i ngton. D.C. 20005
( 2 0 2 1 730-8000
Octobcr I X. 2002
33
Case 3:06-cv-00672-VRW Document 294-2 Filed 07/05/2006 Page 37 of 58
CERTlFICATE OF SERVICE
I hereby certify t h a t on this 18th day of October, 2002, I cnuscd truc and corrcct
copies of tlic forgoing Petition for Declaratory Ruling That AT&T’s Phoiic-to-Phonc TI’
Tclcphony Serviccs Are Exempt From Access Charges to be servcd on all partics hy mailing,
i s / Pcter Andros
Pcrcr Andros
Case 3:06-cv-00672-VRW Document 294-2 Filed 07/05/2006 Page 38 of 58
SERVICE LIST
klarlcne H . Dortch
Scci-etary
Fcdcrnl Cummunications Coinmission
455 I zth Strect, S\V
\I';i~hington.D.C. 20554
2
Case 3:06-cv-00672-VRW Document 294-2 Filed 07/05/2006 Page 39 of 58
Exhibit R
Case 3:06-cv-00672-VRW Document 294-2 Filed 07/05/2006 Page 40 of 58
1.1 Overview
This report deals with interconnection between Internet Service Providers. The report
describes the various interconnection arrangements, which are presently in use in the
Internet, and identifies some areas that affect interoperability and reliability. This report
is limited to best effort Internet Protocol (IP) services. The aim is to serve as a framework
for ongoing efforts, and to explain the related issues.
This report seeks to identify the most important issues and exposures in each of these
three main areas, and strives to identify opportunities to address or mitigate these risks.
Where a solution is not readily apparent, we suggest directions for future research and
investigation.
There are other aspects of interconnection between ISPs, such as operational coordination
of issues such as security and quality of service, which focus group 4 is not currently
working on.
Few mediums have grown as quickly as the Internet, or continue to change as rapidly.
We expect and acknowledge that the practices we describe and document will change
over time. It is therefore likely that the issues addressed in this report will need to be
revisited in the future.
1
Case 3:06-cv-00672-VRW Document 294-2 Filed 07/05/2006 Page 41 of 58
1.2 Terminology
1.2.1 Acronyms
1.2.2 Terminology
2
Case 3:06-cv-00672-VRW Document 294-2 Filed 07/05/2006 Page 42 of 58
Paid Peering A form of peering in which one party pays the other, in
order to offset perceived differences in cost or value
received.
2. Background
3
Case 3:06-cv-00672-VRW Document 294-2 Filed 07/05/2006 Page 43 of 58
The current Internet is supported by a very large number (at least thousands) of ISPs.
ISPs range in size from very small (as small as serving an individual building) to very
large (global). It is common for an IP packet, in its path from source to destination over
the Internet, to traverse multiple ISPs. It is therefore necessary for ISPs to cooperate in
the provision of Internet connectivity services. For example, it is necessary for ISPs to
negotiate agreements to achieve connectivity between these various IP networks.
Typically, today in the Internet, the interface between IP service providers offers basic
datagram IP interconnection, and supports only best effort IP traffic. In other words,
today class-of-service (CoS) support is typically not offered across multiple ISPs.
In the future ISPs may provide additional services, such as two or more classes of service
and/or MultiProtocol Label Switching (MPLS). There might also be a need to support
these types of services between providers. These issues are outside of the scope of this
paper. Application level interconnection, such as the operation of DNS between
providers, is similarly outside of the scope of this paper.
Routing in the Internet is generally divided into internal routing and external routing.
Internal routing refers to routing within an Autonomous System (AS), where an AS might
be a service provider network, or a contiguous and well-connected part of an ISP
network. In most cases either “Intermediate-System to Intermediate-System” (IS-IS) [1]
or “Open Shortest Path First” (OSPF) [2] are used as the Internal Gateway Protocol (IGP)
within an AS. These protocols provide dynamic routing within a network, and can be
used to support certain types of traffic engineering (such as balancing of traffic flows
within a network). However, IS-IS and OPSF do not support complex policy-based
routing such as is needed between service providers.
Routing between ASs makes use of “Border Gateway Protocol version 4” (BGP) [3].
BGP supports a wide range of administrative, engineering, and architectural policies
which may affect choice of routes, and also has been shown through operational
experience to scale to support a very large Internet with more than 100,000 routes.
In many cases ISPs use shortest exit routing (also known as "hot potato" routing). With
shortest exit routing, a packet which is to be forwarded via a neighboring ISP is sent via
the nearest interconnect to that ISP, without concern for where in the neighboring ISP the
destination is actually connected. In other words, the packet will use the interconnect
closest to the point where the packet enters the first ISP.
Consider two ISPs which span the same geographic area, and which are interconnected in
multiple locations. Figure 1 shows an example of two backbone ISPs, which are
interconnected in four locations.
4
Case 3:06-cv-00672-VRW Document 294-2 Filed 07/05/2006 Page 44 of 58
ISPx
Backbone ISP1
Backbone ISP2
ISPy
Consider a packet originating in service provider ISPx (served by Backbone ISP1), for a
destination in service provider ISPy (served by Backbone ISP2). ISPx forwards the
packet to its backbone service provider, which is ISP1. ISP1 then does a normal route
lookup, and finds that the destination is served by Backbone ISP2. ISP1 then forwards the
packet to ISP2. With shortest exit routing, ISP1 will use the closest connection to ISP2,
as illustrated in figure 1. ISP2 then forwards the packet on to ISPy.
In this example, the ISP whose customer is originating the packet (ISP1) needs to
forward the packet for only a short distance. The ISP whose customer is receiving the
packet needs to forward the packet for a greater distance. This is a common occurrence
when shortest exit routing is used.
If both ISPs use shortest exit routing, the paths that the packets take will not be the same
in both directions, even between the same two end points.
A significant percentage of the traffic in the Internet goes between web users (i.e.,
personal computers and workstations) and web servers. In general the volume of traffic
from web user to web server is relatively small (consisting of requests for content), and
the volume of traffic from web server to web user is relatively large (consisting of the
content itself).
5
Case 3:06-cv-00672-VRW Document 294-2 Filed 07/05/2006 Page 45 of 58
This implies that in many cases a particular user of the Internet may originate an
exchange of data, for example by using their personal computer or workstation to query a
web server. However, the system which initiates the exchange is typically the source of
only a small percentage of the total traffic, while the web server which is offering a
service is typically the source of the bulk of the traffic.
Where shortest exit routing is used between ISPs with a similar geographic footprint, this
means that the amount of traffic is different in each direction, which may cause one ISP
to incur more cost than the other.
In general some ISPs may be primarily offering services to residential customers, others
may primarily offer services to web servers, others may primarily offer services to
business, while still other ISPs may offer services to a mix of customers. An ISP’s
customer ratio will have an effect on the symmetry or asymmetry of its traffic flows.
Traffic flows between countries are affected by availability and cost of transport as well
as by a host of factors that influence where content is located. For example, flows of data
between countries or between continents may be asymmetric due to a relatively higher
concentration of web servers in some countries and a relatively lower concentration in
other countries. These effects imply that traffic flows may in some cases be highly
asymmetric. In many cases where there is asymmetric traffic flow between two countries,
the bulk of the traffic may be initiated by requests by users in one country, even though
the bulk of the bits are originated in the other country.
In some cases it is possible for two service providers to have so much traffic to exchange
that it is more efficient for them to interconnect directly. Typically this requires
provisioning direct circuits between providers (which can in some cases be in the same
building), and each provider dedicates a router port to the interconnection.
For the interconnection of any two ISPs, there is a tradeoff between the use of more
connections versus the use of faster connections to achieve higher bandwidth. As an
example, consider two ISPs that span the U.S. If they were to interconnect only on the
east coast, then traffic originating at one ISP on the west coast, for a destination at the
other ISP on the west coast, would have to traverse each service provider's network in
order to reach the interconnection point. It is therefore useful for ISPs with a common
geographic range to interconnect at multiple points. However, in general a higher speed
connection costs less than multiple lower speed connections. Also, one higher speed
6
Case 3:06-cv-00672-VRW Document 294-2 Filed 07/05/2006 Page 46 of 58
interconnection implies less total network management effort when compared to multiple
lower speed interconnections. Therefore the number and location of interconnection
points is generally based on economic and other tradeoffs.
Peering is an agreement between ISPs to carry traffic for each other and for their
respective customers. Peering does not include the obligation to carry traffic to third
parties. Peering is usually a bilateral business and technical arrangement, where two
providers agree to accept traffic from one another, and from one another’s customers (and
thus from their customers’ customers).
Peering, as used in this document, refers to a relationship between service providers. The
term “peer”, as used in this context should not be confused with the use of the same term
to describe a relationship between two routers. For example, two routers which directly
exchange BGP packets are referred to (in other documents) as “BGP Peers”.
Transit is an agreement where an ISP agrees to carry traffic on behalf of another ISP or
end user. In most cases transit will include an obligation to carry traffic to third parties.
Transit is usually a bilateral business and technical arrangement, where one provider (the
transit provider) agrees to carry traffic to third parties on behalf of another provider or an
end user (the customer). In most cases, the transit provider carries traffic to and from its
other customers, and to and from every destination on the Internet, as part of the transit
arrangement. In a transit agreement, the ISP often also provides ancillary services, such
as Service Level Agreements, installation support, local telecom provisioning, and
Network Operations Center (NOC) support.
Peering thus offers a provider access only to a single provider’s customers. Transit, by
contrast, usually provides access at a predictable price to the entire Internet.
Historically, peering has often been done on a bill-and-keep basis, without cash
payments. Peering where there is no explicit exchange of money between parties, and
where each party supports part of the cost of the interconnect, may be referred to as
shared-cost peering. Shared-cost peering is typically used where both parties perceive a
roughly equal exchange of value. Peering therefore is fundamentally a barter relationship.
In some cases peering might be desired, but there might be an understanding that the
parties would not receive roughly equal value. In such a case paid peering may be used.
Paid peering is an agreement whereby ISPs agree to carry traffic for each other and for
their respective customers, but with some payment involved in order to offset perceived
differences in value received and/or cost.
7
Case 3:06-cv-00672-VRW Document 294-2 Filed 07/05/2006 Page 47 of 58
The large number of ISPs worldwide implies that it is not feasible for every ISP to
interconnect with every other ISP. Any-to-any interconnection of ten thousand ISPs
would require some fifty million connections – which is not technically feasible.
There are significant equipment, circuit and management costs of interconnection. Even
in an environment where there is a perception of equal value for a particular
interconnection, this value might not be enough to justify the cost of the interconnection.
Any given ISP therefore will not choose to peer with every other ISP on a shared-cost
basis.
Instead ISPs make conscious decisions as to which providers they will peer with, and
under what business terms. In the United States, the decision to peer, or to decline to
peer, is driven by competitive market forces, rather than by government regulation.
Moreover, there is no legal obligation to disclose these decisions or these terms.
An ISP’s criteria for deciding the ISPs with which it will peer are outlined in a peering
policy. As noted above, peering is negotiated based on market forces and will result
when it is mutually beneficial to two ISPs. Thus, the criteria contained in peering
policies are metrics for determining mutuality of benefit.
ISPs are at the same time intense competitors but are driven to cooperate and collaborate
in order to provide the universal connectivity needed and demanded by their customers.
Differences among networks in location, coverage, customer mix, customer size, loyalty
of installed base, service offerings, network quality, cost and market structure complicate
the mutual assessment of peering versus transit. Typically, ISPs develop interconnection
strategies to address two main points: cost and performance.
ISPs may have different peering models due to geographical network footprint or
customer base, etc. ISPs tend to peer with ISPs of a similar scale (as this often allows for
a perceived rough equality of value). Smaller ISPs may have limited peering with larger
ISPs and generally attain connectivity to the global Internet through transit service from
their upstream transit provider(s). It may be that a large ISP may purchase transit from
another large ISP in order to attain connectivity outside of its own network footprint. For
example, a large North American ISP may enter into a transit relationship with another
North American ISP because this other ISP also has a network presence in Europe or
Asia.
In such a case an ISP may have both a peering relationship and a transit relationship with
another ISP. ISP A may peer with ISP B in the United States, for locations in the United
States. Simultaneously ISP A may buy transit from ISP B for locations in Europe or
Asia. Depending upon the geographic reach of ISP A, and depending upon the business
relationships, the actual exchange of routing information and data destined for locations
in Europe or Asia might take place either in the US, or overseas. Consider the scenario in
which each network maintains or separately contracts for their own inter-continental
8
Case 3:06-cv-00672-VRW Document 294-2 Filed 07/05/2006 Page 48 of 58
links. In this case the two ISPs may only announce the US-based customers to one
another in North America. In Europe, ISP B may announce ISP A’s European routes to
both ISP B customer and peers.
The majority of ISPs purchase transit from other ISPs, even in case of ISPs that have
global networks. For example, a global ISP that has a network in the U.S., Europe and
Asia may purchase transit from an Asian ISP that has a more expansive Asian network
than its own.
ISPs’ percentage of connectivity obtained by transit vs. peering may vary greatly
depending on the particular interconnection model. Generally speaking, the larger the ISP
the larger percentage of its traffic will be transported through peering connections as
opposed to transit. This is mainly due to the fact that a larger ISP’s network will
physically reach more locations, implying that the larger ISPs have the ability to peer in
more locations than smaller ISPs.
No single ISP owns a network that reaches all points of the global Internet. Therefore, in
some cases ISPs may choose to buy transit from another ISP rather than build a network
to reach a specific part of the globe. This is typically due to the opportunity cost of
building a network vs. outsourcing (buying transit). This model may apply to the
smallest ISP as well as to the largest of global ISPs. An ISP’s particular interconnection
model therefore will reflect a “buy vs. build” decision: an ISP may either incur the cost
of building its own network and thereby position itself to barter for interconnection (i.e.,
peering), or it can effectively “rent” other ISPs’ networks by buying transit.
Different business arrangements have evolved depending on the type of ISP. For
example: Two peering transport ISPs with similar traffic profiles may split the costs of
bilateral circuit connections. However, in some cases transport ISPs may make use of a
different relationship with ISPs specializing in content hosting. ISPs may exchange traffic
using a 'longest exit' (as opposed to a 'shortest exit') of traffic that is traveling from the
transport ISP to the hosting ISP. The term “cold potato” routing is sometimes used to
refer to this form of interconnection. This of course affects which ISP takes on the cost of
carrying traffic long-haul, which may in turn affect the payment structure which is agreed
between ISPs.
Interconnection strategies also reflect the patterns of industry evolution that have varied
in different countries and regions. The pace of telecommunications liberalization, and
varying patterns of regional development and international transit costs, have shaped the
interconnection in each country and region.
9
Case 3:06-cv-00672-VRW Document 294-2 Filed 07/05/2006 Page 49 of 58
It has been suggested that the complexity evident in actual interconnection agreements
imply that it would be difficult or impossible to write a regulation that addresses the rich
forms of agreement that exist between providers. There is a wide range of interconnection
agreements in place. These exist as efficient market responses that a pair of providers
find mutually beneficial.
3. Quality of Interconnections
The overall Internet service can only be as good as the quality of the interconnection
between ISPs. It is important that the interconnection between ISPs scale in terms of
bandwidth, number of ISPs interconnected, and for efficient Internet-wide routing and
management.
In the past traffic congestion at public interconnection points has been a problem,
resulting in traffic loss. This has been improved considerably through migration of public
interconnection points to relatively faster network technologies and due to the greater use
of private peering.
ISPs’ networks are at risk due to a range of hazards, ranging from equipment and link
failures, power outages, natural disasters, mis-configuration, and intentional attacks.
These intentional attacks include Denial of Service (DoS) and virus attacks. Network
attacks such as the Code Red worm are a serious concern to ISPs.
In general, directly connected ISPs will need to cooperate in fault detection. For example,
if a customer from one ISP is having trouble interconnecting with a customer of another
ISP, then both ISPs may need to get involved in determining whether the problem is
within one ISP's network, within the other ISP's network, or at the interconnection point.
Similarly ISPs may need to cooperate in management of inter-domain routing between
the ISPs.
Due to the interconnected nature of the Internet, it is important that ISPs share
information to respond to such attacks. Operational issues relating to DoS attacks and
other network security threats may be addressed in organizations that are established for
the exchange of information among and between industry participants and government.
However, information sharing has legal implications related to the Freedom of
Information Act (FOIA) and antitrust laws. Various stakeholders are working to identify
and develop the best forum in which ISPs and government can share operational
information related to risks and threats from network attacks while maintaining the
confidentiality of sensitive information and protecting ISPs from legal liability.
10
Case 3:06-cv-00672-VRW Document 294-2 Filed 07/05/2006 Page 50 of 58
There is a need for tools to measure performance and reliability. Here there is a need to
make a distinction between (i) application end to end performance; (ii) IP end to end
performance; (iii) performance within an ISP; and (iv) performance at the interconnection
point. Optimizing performance at each interconnection point is a small but essential part
of optimizing overall performance.
Commonly used measurement tools tend to look at end to end performance, without
isolating where the bottleneck is. Additional work is needed to develop better tools for
measuring performance and to isolate bottlenecks.
4. Potential Issues
In the United States, the decision to connect, how to connect, or to decline to connect, is
driven by competitive market forces, rather than by government regulation. Because of
the competitive nature of these arrangements, there is no legal obligation to disclose these
decisions, terms, or to whom one connects. Decisions about which connection
arrangement; peering, paid peering, or transit, or a hybrid arrangement, are determined by
the competitive conditions of the market. Peering and transit are established pursuant to
contracts between the parties. These contracts are usually treated as confidential business
information.
However, many would argue that the conditions under which providers are willing to
enter into discussions regarding such contracts need not, and perhaps should not, be
treated as confidential information.
There are many players in the worldwide Internet, and a common understanding of
frequently used practices, processes, and procedures is desirable to foster smooth and
efficient operation of processes necessary for the operation of the Internet. In general,
when a process is carried out in private, it is difficult for others to fully understand the
process. A lack of openness can lead to perceptions of lack of fairness in the process,
particularly in the absence of competitive options.
Over the past year, several of the largest ISPs in the United States have voluntarily
chosen to openly publish the basis on which they decide with whom they will enter into
discussions about peering on a shared cost basis. In the opinion of NRIC V, this has been
11
Case 3:06-cv-00672-VRW Document 294-2 Filed 07/05/2006 Page 51 of 58
a positive development, both for U.S. industry and for the global Internet community. It
has significantly enhanced transparency of process in the industry.
For these reasons, NRIC V, Focus Group 4 (FG4) has encouraged service providers, and
especially the large "backbone" Internet providers, to consider, consistent with their
business practices, publication of their criteria for entering discussions about peering.
Some participants have expressed a concern that the process of publishing peering criteria
would itself result in a harshening of peering criteria. Because of the complexity in
evaluating the costs and benefits of interconnections, guidelines may fail to capture all
relevant market factors. If published guidelines are considered as contractual obligations,
ISPs could be tempted to publish unnecessarily harsh guidelines. It is certainly not the
intent of FG4 to recommend a policy that would cause a change in peering criteria.
Rather, our purpose is to support publishing peering policies as an important part of
ensuring efficient operation of the Internet.
This paper does not take a position on the content of the peering requirements posted by
any particular ISP. Some ISPs feel that certain peering practices are exclusionary, others
do not agree. However, publication of an ISP’s peering policies opens these policies to
public scrutiny and debate, arguably making unreasonable or exclusionary policies less
likely.
In general it may be necessary for a service provider to limit the number of other
networks with which it peers, and/or to ensure that peering arrangements are mutually
beneficial and of sufficient value to justify the cost of peering. Internet providers do not
and can not peer with all other Internet providers. This is because peering requires
expenditure of resources, including human resources, use of equipment, and network
bandwidth. Such resources are constrained in most cases. For this reason ISPs make
conscious decisions as to with which providers they will peer, and under what business
terms. In the United States, the decision to peer, or to decline to peer, is driven by market
forces, rather than by government regulation.
For example, peering requires some coordination between ISPs, which in turn implies
human resources to perform the coordination. Network management is needed, for
example for configuration of BGP policies, and for fault isolation, detection, and
correction.
12
Case 3:06-cv-00672-VRW Document 294-2 Filed 07/05/2006 Page 52 of 58
Private peering requires that local circuits be configured (and paid for) between the
peering ISPs. Routers must also be provided and configured.
Adding additional peers at public peering points is relatively less expensive for low or
moderate bandwidth interconnection. For example, if a new provider wished to peer at a
public peering point, then only that one provider will need to provision a circuit to the
peering point, other existing providers will already have circuits to that peering point.
However, addition of a new peer at a public peering point still requires management of
BGP policies. If the aggregate traffic level increases sufficiently, then other providers
may need to increase circuit capacity, or the network capacity at the peering point may
need to be increased. Also, ISPs who directly exchange a large volume of traffic may find
that it is more efficient to use private peering with circuits and routers dedicated to the
exchange of data.
In some cases changes in inter-domain routing may take a while to stabilize in the
Internet. For example, there are cases where routing dynamics have taken as long as
several minutes to converge. One option for improving convergence times is to limit the
path length between any two providers. However, note that reducing all paths to 2 hops
would require that all ISPs peer with all other ISPs, which is technically infeasible. There
is a trade-off here between convergence time versus the overhead of peering (e.g.,
number of interconnections and amount of network management needed).
The Internet primarily uses topology-based addressing [4], in which a customer who
receives Internet connectivity from a provider also receives its address allocation from
that provider. This use of topological addressing is important to limit the growth in the
number of prefixes visible in top-level IP routing. This in turn implies that an ISP that
does a poor job in aggregating addresses may be straining the entire Internet inter-domain
routing system. However, there is in general difficulty in agreeing on the definition of
"poor job" and there is also difficulty in agreeing what should be done to address this
issue. Also, there are reasons to avoid aggregation in some cases, such as where a
customer is attached to multiple service providers ("multi-homing") and to optimize
routes to some customers ("traffic engineering"). Thus, there are engineering trade-offs in
address aggregation decisions.
13
Case 3:06-cv-00672-VRW Document 294-2 Filed 07/05/2006 Page 53 of 58
No two networks are exactly the same. However, in order for the Internet to operate, all
of the IP service providers worldwide must be interconnected in some fashion. At some
level every ISP needs to have a method or criteria to determine which other ISPs it will
connect as peers, and which ones should connect as customers.
Each ISP has the right to define its own peering criteria. The goal of this section is not to
judge whether these criteria are correct, but rather to provider examples of criteria that
may optionally be used, and to educate others on why these criteria exist.
A motivation affecting the design of peering criteria is to ensure a reasonable and fair
allocation of cost to each party, and a mutuality of benefit shared between the peering
parties. ISPs may want to keep this goal in mind in developing peering criteria, and in
evaluating the degree to which these criteria apply in any particular case.
Some ISPs use their peering criteria as guidelines only, and peering criteria may change
over time. The amount of flexibility employed when evaluating conformance with
peering criteria may also change due, for example, to concerns about regulatory issues.
However, it may be undesirable for criteria to be applied too harshly, since
interconnection in some form (whether direct or indirect) is needed for full Internet
connectivity
.
4.3.1 Geographic Coverage
One of the most common criteria for peering is similar geographic coverage. The basis
for this is that it costs more resources to build a national or global network then it does to
build and maintain a regional network. Many ISPs feel that regional and national ISPs
should not be considered peers because the national ISP incurs a greater expense to build
out its network. As an example, a nationwide network may have to carry its customer
traffic an average of 500 route miles, while a regional network may only have to carry the
traffic an average of 100 miles. Geographic coverage therefore serves as a measure of
whether there would be a reasonably balanced benefit to the two ISPs in entering into a
peering relationship.
The relative importance of geographic coverage may change over time. For example, the
relative cost of using 1000 miles of fiber along an existing right of way, versus the cost of
laying 10 miles of fiber within a congested city, may change with advances in
technology. Advances in optical technology may reduce the cost of the former, while
advances in wireless technology may provider an alternative to the latter. Relative costs
may change based on technological advances which are difficult or impossible to predict.
Geographic coverage may be used to represent costs other than just circuit costs. For
example, a geographically limited regional network might operate a single Point of
Presence (PoP). A national or international network might have PoPs in many major
cities across a wide geographic range.
14
Case 3:06-cv-00672-VRW Document 294-2 Filed 07/05/2006 Page 54 of 58
ISPs with a larger geographic footprint also have a larger potential customer base. This
may represent an advantage which offsets the greater cost of maintaining the larger
geographic footprint.
In some cases an ISP will require peering connections to be built in specific geographic
areas. This serves to reduce the cost of exchanging traffic and is also useful to balance
traffic loads. This requirement may in some cases also double as a geographic coverage
requirement.
In many cases it is in the best interest of both parties to peer in geographically dispersed
locations. Fewer connections cause an increase in the consumption of long-haul
bandwidth, and more connections consume more local loops. Both extremes can cause a
significant waste of resources. As an example of why the location of peering may be of
importance: Two nationwide ISPs connecting only on the east coast will consume
significant resources hauling their west coast customer traffic to the east coast.
Some ISPs will modify this requirement to consider geographic differences, such as for
peering for some specific routes for ISPs located on different continents. For example
some US providers may agree to announce US routes to Asian ISPs (and receive Asian
routes) without requiring an east coast peering location, and may announce US routes to
European ISPs (and receive European routes) without requiring a west coast peering
location.
The requirement for a specific geographic coverage can sometimes be coupled with
the requirement of the peer ISP's backbone being able to maintain a certain link capacity.
One reason for this requirement is that it costs more to run a higher capacity
backbone. Also, before agreeing to a peering relationship, an ISP wants to ensure that its
peer will have sufficient capacity to carry the first ISP’s traffic in a manner that satisfies
its customers’ expectations. In many cases the capacity requirements may vary from
region to region with the most restrictive requirements in areas where more capability is
typically available and lower requirements in other areas.
Some ISPs require that the traffic exchanged between networks must be roughly balanced
in order to peer. For example the traffic sent from one ISP to the other must be
comparable to the traffic received. Since most ISPs use shortest exit routing, it usually
costs less resources to produce a bit then it does to consume a bit. Thus if one ISP sends
significantly more traffic to another ISP than it receives, it probably costs it less to peer.
This situation may arise from an ISP focusing on a certain niche market (like hosting, or
access).
15
Case 3:06-cv-00672-VRW Document 294-2 Filed 07/05/2006 Page 55 of 58
Note however, that web traffic tends to be highly asymmetric, with the traffic flows from
web server to client much greater than flows from client to server. An ISP which supports
multiple popular web services will therefore tend to generate more bits of data than one
which supports primarily home users or other web customers. Also where ISPs have
highly different geographic coverage, the asymmetric cost of carrying traffic might be
more balanced. The reasons for asymmetry in IP traffic may therefore need to be taken
into consideration in some cases.
Most private peering guidelines have a minimum traffic load requirement. This tends to
go hand-in-hand with private peering, since for small or moderate traffic loads it costs
more to establish a direct peering connection than to add another peer at a public peering
site. The goal of these requirements is to make sure that there will be enough value in the
exchange of traffic to warrant the cost of interconnection, including the peering circuit as
well as equipment and network management costs.
Almost all ISPs require that a peer have a 24x7 NOC. The Internet has not evolved to the
point where every ISP can completely protect themselves from accidental or malicious
acts by their peers or from attacks launched through a peer. The requirement of a 24x7
NOC ensures that if something does happen it can be rectified quickly. The requirement
to enable loose source routing of packets is sometimes included to enable the operators
and engineers of that network to be able to track the return path of their traffic. In
principle ISPs might also make some requirement with respect to the experience level or
capabilities of their peers, although this could be difficult to quantify.
The efficiency of overall inter-domain routing in the Internet requires that some care be
used in the assignment of addresses (in order to limit the size of the overall Internet
routing tables). However, note that a core ISP which does a good job of address
allocation is aiding its peers more than it is helping itself – each ISP has to maintain
separate routes to its own customers in its internal routing, regardless of whether it can
aggregate these routes for advertisement to other ISPs.
An ISP might therefore require reasonable address aggregation as a criteria for peering.
Alternatively, an ISP might limit which routes it is willing to accept from its peers.
5. Summary
This white paper deals with interconnection between Internet Service Providers (ISPs).
The report describes the various interconnection arrangements which are presently in use
16
Case 3:06-cv-00672-VRW Document 294-2 Filed 07/05/2006 Page 56 of 58
in the Internet, and identifies some areas that affect interoperability and reliability. It is
noted that there is a wide range of interconnection agreements in place, which exist as
efficient market responses to the requirements of maintaining the operational Internet.
The white paper also lists some of the issues that ISPs take into consideration when they
decide what type of interconnection is appropriate with other ISPs and notes that the
Internet is evolving continuously in a manner that is constrained by market forces and
technical feasibility. This report is limited to best effort Internet Protocol (IP) services.
The white paper notes that interconnection strategies also reflect the patterns of industry
evolution that have varied in different countries and regions and notes that the pace of
telecommunications liberalization, and varying patterns of regional development and
international transit costs, have shaped the interconnection in each country and region.
The white paper concludes by encouraging ISPs, and especially the large "backbone"
ISPs, to consider, consistent with their business practices, publication of their criteria for
entering discussions about peering. Publishing peering policies will increase the
transparency and the efficiency of the process, demonstrate that U.S. industry practices
are neither discriminatory nor exclusionary, and allay concerns of domestic and overseas
providers and the public.
6. References
RFCs
[1] Ross Callon, “Use of OSI IS-IS for Routing in TCP/IP and Dual Environments”,
RFC 1195, Dec 1990.
[2] John Moy, “OSPF Version 2”, RFC 2328, April 1998.
[3] Yakov Rekhter and Tony Li, "A Border Gateway Protocol 4 (BGP-4)",
RFC 1771, March 1995.
[4] Yakov Rekhter and Tony Li, “An Architecture for IP Address Allocation with
CIDR”, RFC 1518, September 1993.
ACADEMIC PAPERS/BOOKS
[7] Jean-Jacques Laffont, J. Scott Marcus, Patrick Rey and Jean Tirole,
17
Case 3:06-cv-00672-VRW Document 294-2 Filed 07/05/2006 Page 57 of 58
[9] K. Cukier, Peering and Fearing: ISP Interconnection and Regulatory Issues,
http://www.ksg.harvard.edu/iip/iicompol/Papers/Cukier.html
[10] P. Reichl, S. Leinen, and B. Stiller, A Practical Review of Pricing and Cost
Recovery for Internet Services, IEW ’99, 2nd Internet Economics Workshop,
Berlin, Germany, May 28-29, 1999,
http://www.tik.ee.ethz.ch/~cati/paper/iew99.pdf
INDUSTRY PAPERS
NEWS ARTICLES
[17] Randy Barrett, ISP Survival Guide: Peering into the Future, Inter@ctive
Week Online, ZDNet, 12/7/98,
http://www.zdnet.com/intweek/supplements/survival/peering.html
GOVERNMENT PUBLICATIONS
18
Case 3:06-cv-00672-VRW Document 294-2 Filed 07/05/2006 Page 58 of 58
INTERCONNECTION GUIDELINES
OTHER
[26] Albert, Jeong, and Barabasi, "Error and Attack Tolerance of Complex
Networks", Nature, July 27, 2000.
19