WPC 2" ZB|!HP LaserJet IIPX\  PG;P  7a1IndentedLeft-indented text$a2IndentedLeft-indented text-` ` ` 2Tya3IndentedLeft-indented text6 a4IndentedLeft-indented text?a5IndentedLeft-indented textH hhha6IndentedLeft-indented textQ 2 a Wa7IndentedLeft-indented textZ a8IndentedLeft-indented textcpppa1151Starts with A. at margin, 1 at first indent OO#Xx6X@QX@##d6X@Q@#a2151Starts with A. at margin, 1 at first indent / 2   B  a3151Starts with A. at margin, 1 at first indent : a4151Starts with A. at margin, 1 at first indent E a5151Starts with A. at margin, 1 at first indent P a6151Starts with A. at margin, 1 at first indent[ 2   Z  a7151Starts with A. at margin, 1 at first indentf a8151Starts with A. at margin, 1 at first indentq  a1150Right-Aligned Paragraph Numbers8!"@   a2150Right-Aligned Paragraph NumbersA#$@` `  ` ` ` 2 ] a3150Right-Aligned Paragraph NumbersJ%&@  ` `  a4150Right-Aligned Paragraph NumbersS'(@  a5150Right-Aligned Paragraph Numbers\)*@hh# hhh a6150Right-Aligned Paragraph Numberse+,@( hh# 2<yJqa7150Right-Aligned Paragraph Numbersn-.@- ( a8150Right-Aligned Paragraph Numbersw/0@pp2 -ppp a1AgendaAgenda Items%12*  a2AgendaAgenda Items3422qnqqPqa3AgendaAgenda Items56a4AgendaAgenda Items78a5AgendaAgenda Items9:a6AgendaAgenda Items;<2sqd q!F"a7AgendaAgenda Items=>a8AgendaAgenda Items ?@a1145Right-Aligned Paragraph Numbers!8AB@   a2145Right-Aligned Paragraph Numbers"ACD@` `  ` ` ` 2k#$I%&a3145Right-Aligned Paragraph Numbers#JEF@  ` `  a4145Right-Aligned Paragraph Numbers$SGH@  a5145Right-Aligned Paragraph Numbers%\IJ@hh# hhh a6145Right-Aligned Paragraph Numbers&eKL@( hh# 2;'(e)}6*a7145Right-Aligned Paragraph Numbers'nMN@- ( a8145Right-Aligned Paragraph Numbers(wOP@pp2 -ppp a1Paragraph1. a. i. (1) (a) (i) 1) a))$QR a2Paragraph1. a. i. (1) (a) (i) 1) a)*/ST 2+m,-.Ga3Paragraph1. a. i. (1) (a) (i) 1) a)+:UV a4Paragraph1. a. i. (1) (a) (i) 1) a),EWX a5Paragraph1. a. i. (1) (a) (i) 1) a)-PYZ a6Paragraph1. a. i. (1) (a) (i) 1) a).[[\ 2#/- 0 1!2p"a7Paragraph1. a. i. (1) (a) (i) 1) a)/f]^ a8Paragraph1. a. i. (1) (a) (i) 1) a)0q_` a1DocumentDocument Style1Fab *  ׃  a2DocumentDocument Style2*c d   2%35#4p#5e:$6e$a3DocumentDocument Style30e f    a4DocumentDocument Style4gh . a5DocumentDocument Style5 ij a6DocumentDocument Style6 kl 2b'7p6%8p%9&:&a7DocumentDocument Style7mn` ` ` a8DocumentDocument Style8op` ` ` a1TechnicalTechnical Document Style94q!r     a2TechnicalTechnical Document Style:*st    2);'<)(=(>A)a3TechnicalTechnical Document Style;'uv    a4TechnicalTechnical Document Style<&wx    a5TechnicalTechnical Document Style=&yz  . a6TechnicalTechnical Document Style>&{|  . 28-?)@{*e*Ad,a7TechnicalTechnical Document Style?&}~  . a8TechnicalTechnical Document Style@&  . #X\  PG;P# I. A. 1. a.(1)(a) i) a)X0Í ÍX0Í Ífootnote refA>>#Xw P;7XP##Xw P<7XP#23BOj-CO/DX2E`2Header B! #Xj\  P}G;XP# 4 <DL!#Xj\  P}G;XP#Footer C! #Xj\  P}G;XP# 4 <DL!#Xj\  P}G;XP#Page Number DHeading 1 E0 '#Xj\  P}G;XP# #X\  P}G;P#26FK3G-4H 5I5footnote texFEE#Xw P}7XP##Xw P}7XP#Heading 2 G=4 X #Xj\  P}G;XP# X   X #X\  P}G;P#Body Text H''#Xj\  P}G;XP# #X\  P}G;P#Body Text InI44 , #Xj\  P}G;XP# ,   , #X\  P}G;P#2=J`6K8L:M;149footnote referenceJ>#P}P##P}P#148endnote referenceK#P}P##P}P#147_Equation CaptionL#P}P##P}P#146Default Paragraph FontM#P}P##P}P#2wANd=OZb>P<>Q@A, B,Uppercase LettersN .1, 2, 3,NumbersO1.toatoaP ` hp x (#head1Q'#2p}C #2GRAS=BTCU<EWFG Letter HWFG Letter HeadingR whitewhiteS8. ?? USenvelope retenvelope returnT @ HPX #d6X@}Q@##Xx6X@}QX@#` hp x (#envelope addenvelope addressU @ HPX ` hp x (#2;QV<GW9JX<LY<NAPOAPOV @ HPX ` hp x (#macromacroW   @ `PX #d6X@}Q@##Xx6X@}QX@#` hp x (#heading 9heading 9X @ HPX ` hp x (#heading 8heading 8Y @ HPX ` hp x (#2WYZFmQ[rS\%T]Vheading 4heading 4Z  @ HPX ` hp x (#Interrogator[ HEADING 5\0 p Zwp x (#DDDDDD#&m P}7&P# 4 hp x (##&m P}7&P# HEADING 6]0 p Zwp x (#DDDDDD#&m P}7&P# 4 hp x (##&m P}7&P# 2^^Y_"\`\a]HEADING 7^0 p Zwp x (#DDDDDD#&m P}7&P# 4 hp x (##&m P}7&P# NormalNormal_11#Xw P}7XP##XZ2P}XP#Word222NullWord222Null`11#XZ2P}XP##XZ2P}XP#142Format Downloaded Documenta XX #P}#  #X\  P}G;P# \ #d6X@}Q@#2`b^cW_d_eg`SubheadingSubheadingb.   Right ParRight-Aligned Paragraph Numbersc<@    HeadingChapter Headingd3  *  ׃  Trianglee2gf#agbh]-ciheFormat DownlFormat Downloaded Documentf XX #P}#  #X\  P}G;P# \\ #d6X@}Q@#CitatorFormat Secretary's Citator Output Fileg#d6X@}Q@# XX  \X b#d6X@}Q@# XX *  bheading 3h #XN\  P}XP# #XN\  P}XP#header2i `    #XN\  P}XP# `   #XN\  P}XP#2Bnj$hkjlhkkmomitemizej*  XF r#XN\  P}XP# FF r#XN\  P}XP#referencek;'#XN\  P}XP##XN\  P}XP#headerl   #XN\  P}XP#  #XN\  P}XP#Footnotem..2pntnonp~oq.p141Technical Document Stylen&  . 140Technical Document Styleo&  . 139Technical Document Stylep4$     138Technical Document Styleq&   2/srpsqt%rur137Technical Document Styler'   136Technical Document Styles*    135Technical Document Stylet&  . 134Technical Document Styleu&  . 2svvaswtxtyu133Document StylevF *  ׃  132Right-Aligned Paragraph Numbersww@pp2 -ppp 131Right-Aligned Paragraph Numbersxn@- ( 130Right-Aligned Paragraph Numbersye@( hh# 2Ayzv{[w|x}x129Right-Aligned Paragraph Numbersz\@hh# hhh 128Right-Aligned Paragraph Numbers{S@  127Right-Aligned Paragraph Numbers|J@  ` `  126Document Style}0    2{~syzpz{125Right-Aligned Paragraph Numbers~A@` `  ` ` ` 124Right-Aligned Paragraph Numbers8@   123Document Style` ` ` 122Document Style*   2}e{e:|q|p}121Document Style  120Document Style  119Document Style  . 118Document Style  ` ` ` 2g}~ Quick   117footnote referenceR R#Xw P}7XP##X\  P}G;P#116footnote textYO #Xw P}7XP##X\  P}G;P#115endnote referenceRR#Xw P}7XP##X\  P}G;P#2ԃeM2Quick 1. . page numberpage number114_Equation Caption;;#Xw P}7XP##X\  P}G;P#endnote refeendnote reference>>#Xw P}7XP##X\  P}G;P#2‡U@endnote textendnote textE; #Xw P}7XP##X\  P}G;P#WILL FORMATLast Will & Testament Format#x6X@}@# F  X JL#x6X@}@#). JMEMO FORMATParameters for In-House Memos #x6X@}@#    L#x6X@}@#  #x6X@}@#  ,. NOTEPAPERParameters for notepaper*!"    2AMgAyUSDC PLEADFormat for USDC Pleading#$   X @ HPX "%PLAIN PAPERPLAIN PAPER PARAMETERS%&#x6X@}@#   X X` hp x (#%'0*,.8135@8: 101Document Style? @ . 100Document Style0A B    2?~99Document Style*CD    98Document StyleFEF *  ׃  97Technical Document Style&GH  . 96Technical Document Style&IJ  . 2h5?Ӛ95Technical Document Style&KL  . 94Technical Document Style&MN  . 93Technical Document Style&OP   92Technical Document Style'QR   2691Technical Document Style*ST    90Technical Document Style4U$V     89Right-Aligned Paragraph NumberswWX@pp2 -ppp 88Right-Aligned Paragraph NumbersnYZ@- ( 2wp&Ӡ87Right-Aligned Paragraph Numberse[\@( hh# 86Right-Aligned Paragraph Numbers\]^@hh# hhh 85Right-Aligned Paragraph NumbersS_`@  84Right-Aligned Paragraph NumbersJab@  ` `  2Dp֢pF83Right-Aligned Paragraph NumbersAcd@` `  ` ` ` 82Right-Aligned Paragraph Numbers8ef@   81Document Stylegh` ` ` 80Document Styleij` ` ` 2eeMq#79Document Style kl 78Document Style mn 77Document Styleo p . 76Document Style0q r    2A}775Document Style*st    74Document StyleFuv *  ׃  73Technical Document Style&wx  . 72Technical Document Style&yz  . 2s}71Technical Document Style&{|  . 70Technical Document Style&}~  . 69Technical Document Style&   68Technical Document Style'   2تt$67Technical Document Style*    66Technical Document Style4$     65Right-Aligned Paragraph Numbersw@pp2 -ppp 64Right-Aligned Paragraph Numbersn@- ( 2d63Right-Aligned Paragraph Numberse@( hh# 62Right-Aligned Paragraph Numbers\@hh# hhh 61Right-Aligned Paragraph NumbersS@  60Right-Aligned Paragraph NumbersJ@  ` `  2pp59Right-Aligned Paragraph NumbersA@` `  ` ` ` 58Right-Aligned Paragraph Numbers8@   57Document Style` ` ` 56Document Style` ` ` 2e&eqa55Document Style  54Document Style  53Document Style  . 52Document Style0     2(u51Document Style*    50Document StyleF *  ׃  49Technical Document Style&  . 48Technical Document Style&  . 26O47Technical Document Style&  . 46Technical Document Style&  . 45Technical Document Style&   44Technical Document Style'   2lb43Technical Document Style*    42Technical Document Style4$     41Technical Document Style&  . 40Technical Document Style&  . 2Nw39Technical Document Style4$     38Technical Document Style&   37Technical Document Style'   36Technical Document Style*    2EʿO 35Technical Document Style&  . 34Technical Document Style&  . 33Document StyleF *  ׃  32Right-Aligned Paragraph Numbersw@pp2 -ppp 2 I31Right-Aligned Paragraph Numbersn@- ( 30Right-Aligned Paragraph Numberse@( hh# 29Right-Aligned Paragraph Numbers\@hh# hhh 28Right-Aligned Paragraph NumbersS@  2(a27Right-Aligned Paragraph NumbersJ@  ` `  26Document Style0     25Right-Aligned Paragraph NumbersA@` `  ` ` ` 24Right-Aligned Paragraph Numbers8@   2p0ee(23Document Style` ` ` 22Document Style*   21Document Style  20Document Style  2qp0pp19Document Style  . 18Document Style` ` ` 17Document Style` ` ` 16Document Style` ` ` 2eeq|15Document Style  14Document Style  13Document Style  . 12Document Style0     2 G11Document Style*    10Document StyleF *  ׃  9Technical Document Style&  . 8Technical Document Style&  . 2=0G7Technical Document Style&  . 6Technical Document Style&  . X\  PG;P%\  `&Times New RomanXx6X@QX@<6X9`("Courier New (TT)Xd6X@Q@<6X9`("Courier New (TT)X\  PG;P%\  `&Times New RomanX\  PG;P%\  `&Times New Roman&m P7&P) `CG Times&Xw P7XP* `CG TimesXv6X@7N@<6X9`(CourierNXj\  PG;XP%\  `&Times New RomanXX\  P G;P%\  `&Times New RomanX\  P G;P%\  `&Times New RomanX\  P G;P%\  `&Times New RomanX\  P G;P%\  `&Times New RomanX\  P G;P%\  `&Times New RomanX\  PG;P%\  `&Times New RomanX\  PG;P%\  `&Times New RomanX\  PG;P%\  `&Times New RomanX\  PG;P%\  `&Times New RomanX\  PG;P%\  `&Times New RomanX\  PG;P%\  `&Times New RomanX\  PG;P%\  `&Times New RomanX\  PG;P%\  `&Times New RomanX\  PG;P%\  `&Times New RomanX\  PG;P%\  `&Times New RomanX\  PG;P%\  `&Times New RomanX\  PG;P%\  `&Times New RomanX\  PG;P%\  `&Times New RomanX\  PG;P%\  `&Times New RomanX\  PG;P%\  `&Times New RomanX\  PG;P%\  `&Times New RomanX\  PG;P%\  `&Times New RomanX\  PG;P%\  `&Times New RomanX\  P G;P%\  `&Times New RomanX\  P!G;P%\  `&Times New RomanX\  P"G;P%\  `&Times New RomanX\  P#G;P%\  `&Times New RomanX\  P$G;P%\  `&Times New RomanX\  P%G;P%\  `&Times New RomanX\  P&G;P%\  `&Times New RomanX\  P'G;P%\  `&Times New RomanX\  P(G;P%\  `&Times New RomanX\  P)G;P%\  `&Times New RomanX\  P*G;P%\  `&Times New RomanX\  P+G;P%\  `&Times New RomanX\  P,G;P%\  `&Times New RomanX\  P-G;P%\  `&Times New RomanX\  P.G;P%\  `&Times New RomanX\  P/G;P%\  `&Times New RomanX\  P0G;P%\  `&Times New RomanX\  P1G;P%\  `&Times New RomanX\  P2G;P%\  `&Times New RomanX\  P3G;P%\  `&Times New RomanX\  P4G;P%\  `&Times New RomanX\  P5G;P%\  `&Times New RomanX\  P6G;P%\  `&Times New RomanX\  P7G;P%\  `&Times New RomanX\  P8G;P%\  `&Times New RomanX\  P9G;P%\  `&Times New RomanX\  P:G;P%\  `&Times New RomanXw P;7XP* `CG TimesXXw P<7XP* `CG TimesXXw P=7XP* `CG TimesXX\  P>G;P%\  `&Times New RomanX\  P?G;P%\  `&Times New RomanX\  P@G;P%\  `&Times New RomanX\  PAG;P%\  `&Times New RomanX\  PBG;P%\  `&Times New RomanX\  PCG;P%\  `&Times New RomanX\  PDG;P%\  `&Times New RomanX\  PEG;P%\  `&Times New RomanX\  PFG;P%\  `&Times New RomanX\  PGG;P%\  `&Times New RomanX\  PHG;P%\  `&Times New RomanX\  PIG;P%\  `&Times New RomanX\  PJG;P%\  `&Times New RomanXj\  PKG;XP%\  `&Times New RomanXX\  PLG;P%\  `&Times New RomanXj\  PMG;XP%\  `&Times New RomanXX\  PNG;P%\  `&Times New RomanXj\  POG;XP%\  `&Times New RomanXX\  PPG;P%\  `&Times New RomanX\  PQG;P%\  `&Times New RomanXj\  PRG;XP%\  `&Times New RomanXX\  PSG;P%\  `&Times New RomanX\  PTG;P%\  `&Times New RomanXj\  PUG;XP%\  `&Times New RomanXX\  PVG;P%\  `&Times New RomanX\  PWG;P%\  `&Times New RomanXj\  PXG;XP%\  `&Times New RomanXX\  PYG;P%\  `&Times New RomanX\  PZG;P%\  `&Times New RomanXj\  P[G;XP%\  `&Times New RomanXX\  P\G;P%\  `&Times New RomanX\  P]G;P%\  `&Times New RomanXj\  P^G;XP%\  `&Times New RomanXX\  P_G;P%\  `&Times New RomanX\  P`G;P%\  `&Times New RomanXj\  PaG;XP%\  `&Times New RomanXX\  PbG;P%\  `&Times New RomanX\  PcG;P%\  `&Times New RomanXj\  PdG;XP%\  `&Times New RomanXX\  PeG;P%\  `&Times New RomanX\  PfG;P%\  `&Times New RomanXj\  PgG;XP%\  `&Times New RomanXX\  PhG;P%\  `&Times New RomanX\  PiG;P%\  `&Times New RomanXj\  PjG;XP%\  `&Times New RomanXX\  PkG;P%\  `&Times New RomanX\  PlG;P%\  `&Times New RomanXj\  PmG;XP%\  `&Times New RomanXX\  PnG;P%\  `&Times New RomanX\  PoG;P%\  `&Times New RomanXj\  PpG;XP%\  `&Times New RomanXX\  PqG;P%\  `&Times New RomanX\  PrG;P%\  `&Times New RomanXj\  PsG;XP%\  `&Times New RomanXX\  PtG;P%\  `&Times New RomanX\  PuG;P%\  `&Times New RomanXj\  PvG;XP%\  `&Times New RomanXX\  PwG;P%\  `&Times New RomanX\  PxG;P%\  `&Times New RomanXj\  PyG;XP%\  `&Times New RomanXX\  PzG;P%\  `&Times New RomanX\  P{G;P%\  `&Times New RomanXj\  P|G;XP%\  `&Times New RomanXX\  P}G;P%\  `&Times New RomanX\  P~G;P%\  `&Times New RomanXj\  PG;XP%\  `&Times New RomanXX\  PG;P%\  `&Times New RomanX\  PG;P%\  `&Times New RomanXj\  PG;XP%\  `&Times New RomanXX\  PG;P%\  `&Times New RomanX\  PG;P%\  `&Times New RomanXj\  PG;XP%\  `&Times New RomanXX\  PG;P%\  `&Times New RomanX\  PG;P%\  `&Times New RomanXj\  PG;XP%\  `&Times New RomanXX\  PG;P%\  `&Times New RomanX\  PG;P%\  `&Times New RomanXj\  PG;XP%\  `&Times New RomanXX\  PG;P%\  `&Times New RomanX\  PG;P%\  `&Times New RomanXj\  PG;XP%\  `&Times New RomanXX\  PG;P%\  `&Times New RomanX\  PG;P%\  `&Times New RomanXj\  PG;XP%\  `&Times New RomanXX\  PG;P%\  `&Times New RomanX\  PG;P%\  `&Times New RomanXj\  PG;XP%\  `&Times New RomanXX\  PG;P%\  `&Times New RomanX\  PG;P%\  `&Times New RomanXj\  PG;XP%\  `&Times New RomanXX\  PG;P%\  `&Times New RomanX\  PG;P%\  `&Times New RomanXj\  PG;XP%\  `&Times New RomanXX\  PG;P%\  `&Times New RomanX\  PG;P%\  `&Times New RomanXj\  PG;XP%\  `&Times New RomanXX\  PG;P%\  `&Times New RomanX\  PG;P%\  `&Times New RomanXj\  PG;XP%\  `&Times New RomanXX\  PG;P%\  `&Times New RomanXj\  PG;XP%\  `&Times New RomanXXw P7XP* `CG TimesXX\  PG;P%\  `&Times New RomanXj\  PG;XP%\  `&Times New RomanXX\  PG;P%\  `&Times New RomanX\  PG;P%\  `&Times New RomanXj\  PG;XP%\  `&Times New RomanXX\  PG;P%\  `&Times New RomanX\  PG;P%\  `&Times New RomanXj\  PG;XP%\  `&Times New RomanXX\  PG;P%\  `&Times New RomanX\  PG;P%\  `&Times New RomanX\  PG;P%\  `&Times New RomanX\  PG;P%\  `&Times New RomanX\  PG;P%\  `&Times New RomanX\  PG;P%\  `&Times New RomanX\  PG;P%\  `&Times New RomanX\  PG;P%\  `&Times New RomanX\  PG;P%\  `&Times New RomanX\  PG;P%\  `&Times New RomanX\  PG;P%\  `&Times New RomanX\  PG;P%\  `&Times New RomanX\  PG;P%\  `&Times New RomanXj\  PG;XP%\  `&Times New RomanXXw P7XP* `CG TimesXXj\  PG;XP%\  `&Times New RomanXXw P7XP* `CG TimesXX\  PG;P%\  `&Times New RomanXj\  PG;XP%\  `&Times New RomanXX\  PG;P%\  `&Times New RomanX\  PG;P%\  `&Times New RomanXj\  PG;XP%\  `&Times New RomanXX\  PG;P%\  `&Times New RomanX\  PG;P%\  `&Times New RomanXj\  PG;XP%\  `&Times New RomanXX\  PG;P%\  `&Times New RomanX\  PG;P%\  `&Times New RomanXj\  PG;XP%\  `&Times New RomanXX\  PG;P%\  `&Times New RomanX\  PG;P%\  `&Times New RomanXj\  PG;XP%\  `&Times New RomanXX\  PG;P%\  `&Times New RomanX\  PG;P%\  `&Times New RomanXj\  PG;XP%\  `&Times New RomanXX\  PG;P%\  `&Times New RomanX\  PG;P%\  `&Times New RomanXj\  PG;XP%\  `&Times New RomanXX\  PG;P%\  `&Times New RomanX\  PG;P%\  `&Times New RomanXj\  PG;XP%\  `&Times New RomanXX\  PG;P%\  `&Times New RomanX\  PG;P%\  `&Times New RomanXj\  PG;XP%\  `&Times New RomanXX\  PG;P%\  `&Times New RomanX\  PG;P%\  `&Times New RomanXj\  PG;XP%\  `&Times New RomanXX\  PG;P%\  `&Times New RomanX\  PG;P%\  `&Times New RomanXj\  PG;XP%\  `&Times New RomanXX\  PG;P%\  `&Times New RomanX\  PG;P%\  `&Times New RomanXj\  PG;XP%\  `&Times New RomanXX\  PG;P%\  `&Times New RomanX\  PG;P%\  `&Times New RomanXj\  PG;XP%\  `&Times New RomanXX\  PG;P%\  `&Times New RomanX\  PG;P%\  `&Times New RomanXj\  PG;XP%\  `&Times New RomanXX\  PG;P%\  `&Times New RomanX\  PG;P%\  `&Times New RomanXj\  PG;XP%\  `&Times New RomanXX\  PG;P%\  `&Times New RomanX\  PG;P%\  `&Times New RomanXj\  PG;XP%\  `&Times New RomanXX\  PG;P%\  `&Times New RomanX\  PG;P%\  `&Times New RomanXj\  PG;XP%\  `&Times New RomanXX\  PG;P%\  `&Times New RomanX\  PG;P%\  `&Times New RomanXj\  PG;XP%\  `&Times New RomanXX\  PG;P%\  `&Times New RomanX\  PG;P%\  `&Times New RomanXj\  PG;XP%\  `&Times New RomanXX\  PG;P%\  `&Times New RomanX\  PG;P%\  `&Times New RomanXj\  PG;XP%\  `&Times New RomanXX\  PG;P%\  `&Times New RomanX\  PG;P%\  `&Times New RomanXj\  PG;XP%\  `&Times New RomanXX\  PG;P%\  `&Times New RomanX\  PG;P%\  `&Times New RomanXj\  PG;XP%\  `&Times New RomanXX\  PG;P%\  `&Times New RomanX\  PG;P%\  `&Times New RomanXj\  PG;XP%\  `&Times New RomanXX\  PG;P%\  `&Times New RomanX\  PG;P%\  `&Times New RomanXj\  PG;XP%\  `&Times New RomanXX\  PG;P%\  `&Times New RomanX\  PG;P%\  `&Times New RomanXj\  PG;XP%\  `&Times New RomanXX\  PG;P%\  `&Times New RomanX\  PG;P%\  `&Times New RomanXj\  P G;XP%\  `&Times New RomanXX\  P G;P%\  `&Times New RomanX\  P G;P%\  `&Times New RomanXj\  P G;XP%\  `&Times New RomanXX\  P G;P%\  `&Times New RomanX\  PG;P%\  `&Times New RomanXj\  PG;XP%\  `&Times New RomanXX\  PG;P%\  `&Times New RomanX\  PG;P%\  `&Times New RomanXj\  PG;XP%\  `&Times New RomanXX\  PG;P%\  `&Times New RomanX\  PG;P%\  `&Times New RomanXj\  PG;XP%\  `&Times New RomanXX\  PG;P%\  `&Times New RomanX\  PG;P%\  `&Times New RomanXj\  PG;XP%\  `&Times New RomanXX\  PG;P%\  `&Times New RomanX\  PG;P%\  `&Times New RomanXj\  PG;XP%\  `&Times New RomanXX\  PG;P%\  `&Times New RomanXj\  PG;XP%\  `&Times New RomanXXw P7XP* `CG TimesXX\  PG;P%\  `&Times New RomanXj\  P G;XP%\  `&Times New RomanXX\  P!G;P%\  `&Times New RomanXj\  P"G;XP%\  `&Times New RomanXXw P#7XP* `CG TimesXX\  P$G;P%\  `&Times New RomanXj\  P%G;XP%\  `&Times New RomanXX\  P&G;P%\  `&Times New RomanXj\  P'G;XP%\  `&Times New RomanXXw P(7XP* `CG TimesXX\  P)G;P%\  `&Times New RomanXj\  P*G;XP%\  `&Times New RomanXX\  P+G;P%\  `&Times New RomanX\  P,G;P%\  `&Times New RomanXj\  P-G;XP%\  `&Times New RomanXX\  P.G;P%\  `&Times New RomanXj\  P/G;XP%\  `&Times New RomanXXw P07XP* `CG TimesXXj\  P1G;XP%\  `&Times New RomanXXw P27XP* `CG TimesXX\  P3G;P%\  `&Times New RomanX\  P4G;P%\  `&Times New RomanX\  P5G;P%\  `&Times New RomanX\  P6G;P%\  `&Times New RomanX\  P7G;P%\  `&Times New RomanX\  P8G;P%\  `&Times New RomanXj\  P9G;XP%\  `&Times New RomanXXw P:7XP* `CG TimesXX\  P;G;P%\  `&Times New RomanX\  P<G;P%\  `&Times New RomanX\  P=G;P%\  `&Times New RomanX\  P>G;P%\  `&Times New RomanX\  P?G;P%\  `&Times New RomanX\  P@G;P%\  `&Times New RomanX\  PAG;P%\  `&Times New RomanX\  PBG;P%\  `&Times New RomanX\  PCG;P%\  `&Times New RomanX\  PDG;P%\  `&Times New RomanX\  PEG;P%\  `&Times New RomanX\  PFG;P%\  `&Times New RomanX\  PGG;P%\  `&Times New RomanX\  PHG;P%\  `&Times New RomanX\  PIG;P%\  `&Times New RomanX\  PJG;P%\  `&Times New RomanXj\  PKG;XP%\  `&Times New RomanXXw PL7XP* `CG TimesXXj\  PMG;XP%\  `&Times New RomanXXw PN7XP* `CG TimesXX\  POG;P%\  `&Times New RomanXj\  PPG;XP%\  `&Times New RomanXX\  PQG;P%\  `&Times New RomanX\  PRG;P%\  `&Times New RomanX\  PSG;P%\  `&Times New RomanX\  PTG;P%\  `&Times New RomanX\  PUG;P%\  `&Times New RomanX\  PVG;P%\  `&Times New RomanX\  PWG;P%\  `&Times New RomanX\  PXG;P%\  `&Times New RomanX\  PYG;P%\  `&Times New RomanX\  PZG;P%\  `&Times New RomanX\  P[G;P%\  `&Times New RomanX\  P\G;P%\  `&Times New RomanX\  P]G;P%\  `&Times New RomanX\  P^G;P%\  `&Times New RomanX\  P_G;P%\  `&Times New RomanX\  P`G;P%\  `&Times New RomanX\  PaG;P%\  `&Times New RomanX\  PbG;P%\  `&Times New RomanX\  PcG;P%\  `&Times New RomanX\  PdG;P%\  `&Times New RomanX\  PeG;P%\  `&Times New RomanX\  PfG;P%\  `&Times New RomanX\  PgG;P%\  `&Times New RomanX\  PhG;P%\  `&Times New RomanX\  PiG;P%\  `&Times New RomanX\  PjG;P%\  `&Times New RomanX\  PkG;P%\  `&Times New RomanX\  PlG;P%\  `&Times New RomanX\  PmG;P%\  `&Times New RomanX\  PnG;P%\  `&Times New RomanX\  PoG;P%\  `&Times New RomanX\  PpG;P%\  `&Times New RomanX\  PqG;P%\  `&Times New RomanX\  PrG;P%\  `&Times New RomanX\  PsG;P%\  `&Times New RomanX\  PtG;P%\  `&Times New RomanX\  PuG;P%\  `&Times New RomanXj\  PvG;XP%\  `&Times New RomanXXj\  PwG;XP%\  `&Times New RomanXXw Px7XP* `CG TimesXXj\  PyG;XP%\  `&Times New RomanXX\  PzG;P%\  `&Times New RomanX\  P{G;P%\  `&Times New RomanX\  P|G;P%\  `&Times New Roman2#|X  #X\  PG;P# I. A. 1. a.(1)(a) i) a) >#&m P7&P#Federal Communications Commission`|(#CFCC 99223 #Xw P7XP#у yxdddy` hp x (##v6X@7N@# #Xj\  PG;XP#Before the Federal Communications Commission Washington, D.C.  In the Matter of * Implementation of the)CC Docket No. 96115 Telecommunications Act of 1996) ) Telecommunications Carriers' Use) of Customer Proprietary Network ) Information and Other Customer Information;) ) Implementation of the NonAccounting)CC Docket No. 96149 Safeguards of Sections 271  and 272 of the) Communications Act of 1934, As Amended) *  ORDER ON RECONSIDERATION AND PETITIONS FOR FORBEARANCE ă Adopted:August 16, 1999Released:September 3, 1999 By the Commission:Commissioner FurchtgottRoth approving in part, concurring in part and issuing a statement; Commissioner Tristani approving in part, dissenting in part and issuing a statement. ! TABLE OF CONTENTS  ` (#DParagraph X` hp x (#%'0*,.8135@8:........................173 X.PROCEDURAL ISSUES`(#!...........................................................................................177 XI.ORDERING CLAUSES`(# .............................................................................................201 APPENDIX A APPENDIX B  I.INTRODUCTION  1. 1. 1. a.(1)(a) i) a)On February 26, 1998, the Commission released the CPNI OrderX` hp x (#%'0*,.8135@8:X` hp x (#%'0*,.8135@8: The CPNI Order addressed the scope and meaning of section 222, and promulgated regulations to implement that section. It concluded, among other things, as follows: (a) carriers are permitted to use CPNI, without customer approval, to market offerings that are related to, but limited by, the customers' existing service relationship; (b) before carriers may use CPNI to market outside the customer's existing service relationship, carriers must obtain express written, oral, or electronic customer approval; (c) prior to soliciting customer approval, carriers must provide a onetime notification to customers of their CPNI rights; (d) in light of the comprehensive regulatory scheme established in section 222, the Computer III CPNI framework is unnecessary; and (e) sections 272 and 274 impose no additional CPNI requirements on the Bell Operating Companies (BOCs) beyond those imposed by section 222. B.The Clarification Order On May 21, 1998, in response to a number of requests for clarification of the CPNI Order, the Common Carrier Bureau released a Clarification Order.X0ÍX0Í#X\  P%G;P# I. A. 1. a.(1)(a) i) a)X` hp x (#%'0*,.8135@8:G;P# I. A. 1. a.(1)(a) i) a)Ѝ` hp x (#See discussion infra Part VII.I. See also CenturyTel Reply at 25 ("Rural carriers should have the flexibility to continue their present and customary marketing and business practices with existing subscribers.").p As we noted in the CPNI Order, however, the Commission's CPNI rules apply to small carriers just as they apply to other sized carriers "because we are unpersuaded that customers of small businesses have less meaningful privacy interests in their CPNI."4X` hp x (#%'0*,.8135@8:X` hp x (#%'0*,.8135@8:G;P# ÍBell Atlantic Petition at 916. As explained below, we deny this request. ` ` X` hp x (#%'0*,.8135@8:#X\  P}G;P# I. A. 1. a.(1)(a) i) a)#Xj\  P}G;XP#`  x (##X\  P}G;P# ÍClarification Order, 13 FCC Rcd at 1239899,  12. > Although it is true that the Computer III consents were given prior to the advent of local competition, we believe that the detailed notice and express, affirmative consent required under that regime compensate for this deficiency. Moreover, we are not persuaded by CompTel's assertion that the BOCs warnings that they may have to change the customer's account representatives put undue pressure on these business customers to relent. Finally, we also conclude that although some of the Computer III annual notifications may not have been "proximate to" the carrier solicitations as required by section 222, the Computer III regime's annual notification requirement and limitation to business customers with more than 20 access lines"requirements that we note are more stringent than required by section 222"materially satisfy the concerns we intended to address by the proximate notification requirement promulgated in the CPNI Order. As such, we agree with the Bureau that the Computer III notifications are in material compliance with section 222 and the Commission's rules, and adopt the reasoning and conclusions of the Clarification Order as our own. Other carriers request that the Commission "grandfather" authorizations obtained subsequent to the enactment of section 222, but prior to the promulgation of rules in the CPNI Order.X0ÍX0Í#X\  P}G;P# I. A. 1. a.(1)(a) i) a)#Xj\  P}G;XP#`  x (##X\  P}G;P# ÍAT&T Petition at 1822; CWI Comments at 57; GTE Comments at 24; Sprint Comments at 910; U S WEST Comments at 1518; LCI Reply at 5. AT&T requests that the Commission clarify that the rules promulgated in the CPNI Order have prospective application only and, as such, that AT&T may continue to rely on approvals it obtained from customers in an attempt to comply with section 222 prior to the CPNI Order.X0ÍX0Í#X\  P}G;P# I. A. 1. a.(1)(a) i) a)#Xj\  P}G;XP#`  x (##X\  P}G;P# ÍAT&T Petition at 18. Bell Atlantic, CWI, and Sprint support AT&T's request.X0ÍX0ÍC#X\  P}G;P# I. A. 1. a.(1)(a) i) a)#Xj\  P}G;XP#`  x (##X\  P}G;P# ÍCWI Comments at 6; Sprint Comments at 9; Bell Atlantic Reply at 7.C All four of these carriers argue that it would be confusing to customers and a waste of resources to require the resolicitation of these authorizations.X0ÍX0ÍX#X\  P}G;P# I. A. 1. a.(1)(a) i) a)#Xj\  P}G;XP#`  x (##X\  P}G;P# ÍAT&T Petition at 20; CWI Comments at 6; Sprint Comments at 9; Bell Atlantic Reply at 8.X U S WEST and GTE agree that such authorizations should be grandfathered, but only where they are in writing.X0ÍX0Í-#X\  P}G;P# I. A. 1. a.(1)(a) i) a)#Xj\  P}G;XP#`  x (##X\  P}G;P# ÍGTE Comments at 24; U S WEST Comments at 16.- In contrast, however, MCI opposes any grandfathering.X0ÍX0Í#X\  P}G;P# I. A. 1. a.(1)(a) i) a)#Xj\  P}G;XP#`  x (##X\  P}G;P# ÍMCI Comments at 4548. Several carriers requesting that we "grandfather" these authorizations have provided descriptions of varying detail of their solicitations. AT&T's description was the most detailed. Subsequent to the enactment of section 222, but prior to the CPNI Order, AT&T apparently solicited millions of its customers for consent to use their CPNI to market new products and services to them by reading prepared solicitations to them over the phone during inbound and outbound calls.X0ÍX0Í&#X\  P}G;P# I. A. 1. a.(1)(a) i) a)#Xj\  P}G;XP#`  x (##X\  P}G;P# ÍAT&T Petition at 19 and Appendix A. & AT&T's various versions of its script all essentially stated that AT&T would like to inform the customer about "other" AT&T products and services from timetotime and requested permission to use the customer's "account information" to aid in this purpose.X0ÍX0Í#X\  P}G;P# I. A. 1. a.(1)(a) i) a)#Xj\  P}G;XP#`  x (##X\  P}G;P# ÍAT&T Petition at Appendix A. AT&T argues that the "nontrivial" percentage of customers who declined to authorize the use of their CPNI indicates that customers "understood AT&T's explanation, understood their rights, and"where it was given"consent was informed."X0ÍX0Íy#X\  P}G;P# I. A. 1. a.(1)(a) i) a)#Xj\  P}G;XP#`  x (##X\  P}G;P# ÍAT&T Petition at 20. Of the 27.9 million customers solicited, 24 million agreed to AT&T's request. Id. at 1920.y To "ameliorate" the possibility that customers may not have been fully advised of their rights, AT&T has offered to send customers who gave their approval to AT&T's solicitations written notices of their rights including an explanation that they have a right to withdraw their approval.X0ÍX0Í#X\  P}G;P# I. A. 1. a.(1)(a) i) a)#Xj\  P}G;XP#`  x (##X\  P}G;P# ÍAT&T Petition at 21. We conclude, based upon the evidence presented in the record of this proceeding, that AT&T's solicitations constitute a good faith effort to materially comply with section 222 provided they are supplemented with the curative written notification of rights AT&T has offered to distribute. Accordingly, we find that AT&T may continue to rely on the approvals given, provided the approvals were obtained in the manner detailed above, so long as AT&T supplements those approvals with a written notice to customers of their rights including an explanation that they have the right to withdraw their approval.  The descriptions provided by the other carriers are too brief to analyze whether their solicitations were adequate. For example, Sprint only states that it "informed [several hundred thousand] customers that they had to give their permission to enable Sprint to review their account information in order to inform them about other Sprintbranded services and products."X0ÍX0Í#X\  P}G;P# I. A. 1. a.(1)(a) i) a)#Xj\  P}G;XP#`  x (##X\  P}G;P# ÍSprint Comments at 9. CWI merely states that it "requested CPNI use approval from consumers who became customers after the 1996 Communications Act was enacted" and that it "amended its order forms to include a CPNI notice and approval section in its terms and conditions."X0ÍX0Í#X\  P}G;P# I. A. 1. a.(1)(a) i) a)#Xj\  P}G;XP#`  x (##X\  P}G;P# ÍCWI Comments at 8. Finally, Bell Atlantic briefly notes that it "provided written notice to thousands of its customers of their CPNI rights and secured written release from many of those customers."X0ÍX0Í #X\  P}G;P# I. A. 1. a.(1)(a) i) a)#Xj\  P}G;XP#`  x (##X\  P}G;P# ÍBell Atlantic Reply at 8. We conclude that these descriptions are inadequate to make a determination about whether the notices given and the solicitations made are in material compliance with section 222. Other than AT&T, the parties in this proceeding have not provided sufficient detail describing their solicitations for the Commission to make a determination of material compliance. We urge them to examine the showing made by AT&T as discussed above. We will accept further waiver requests that are materially compliant with section 222, provided the carriers requesting waivers can make a showing similar to the one made by AT&T.   B.Oral and Written Notification  4`  x (# 1.Background X` hp x (#%'0*,.8135@8:X` hp x (#%'0*,.8135@8:#X\  P}G;P# I. A. 1. a.(1)(a) i) a)#Xj\  P}G;XP#` hp x (##X\  P}G;P# ÍCPNI Order, 13 FCC Rcd at 817475, 8179,  160, 169.> The Commission reached this conclusion only after recognizing an apparent conflict between sections 222 and 272.X0ÍX0Í0#X\  P}G;P# I. A. 1. a.(1)(a) i) a)#Xj\  P}G;XP#` hp x (##X\  P}G;P# ÍCPNI Order, 13 FCC Rcd at 8174,  158.0 We noted in the CPNI Order that, on the one hand, certain parties argued that under the principle of statutory construction the "specific governs the general," and that section 222 specifically governs the use and protection of CPNI, but section 272 only refers to "information" generally.X0ÍX0Í3#X\  P}G;P# I. A. 1. a.(1)(a) i) a)#Xj\  P}G;XP#` hp x (##X\  P}G;P# ÍCPNI Order, 13 FCC Rcd at 817475,  160.3 As such, they claimed that section 222 should control section 272.X0ÍX0Í3#X\  P}G;P# I. A. 1. a.(1)(a) i) a)#Xj\  P}G;XP#` hp x (##X\  P}G;P# ÍCPNI Order, 13 FCC Rcd at 817475,  160.3 On the other hand, under the same principle of construction, other parties argued that section 272 specifically governs the BOCs' sharing of information with affiliates, whereas section 222 generally relates to all carriers.X0ÍX0Í3#X\  P}G;P# I. A. 1. a.(1)(a) i) a)#Xj\  P}G;XP#` hp x (##X\  P}G;P# ÍCPNI Order, 13 FCC Rcd at 817475,  160.3 Therefore, they asserted, section 272 should control section 222.X0ÍX0Í3#X\  P}G;P# I. A. 1. a.(1)(a) i) a)#Xj\  P}G;XP#` hp x (##X\  P}G;P# ÍCPNI Order, 13 FCC Rcd at 817475,  160.3 Because either interpretation is plausible, it was left to the Commission to resolve the tension between these provisions, and to formulate the interpretation that, in the Commission's judgment, best furthers the policies of both provisions and the statutory design.X0ÍX0Í3#X\  P}G;P# I. A. 1. a.(1)(a) i) a)#Xj\  P}G;XP#` hp x (##X\  P}G;P# ÍCPNI Order, 13 FCC Rcd at 817475,  160.3 We determine that interpreting section 272 to impose no additional obligations on the BOCs when they share CPNI with their section 272 affiliates according to the requirements of section 222 most reasonably reconciles the goals of these two principles.X0ÍX0Í3#X\  P}G;P# I. A. 1. a.(1)(a) i) a)#Xj\  P}G;XP#` hp x (##X\  P}G;P# ÍCPNI Order, 13 FCC Rcd at 817475,  160.3 2.Discussion We affirm our conclusion in the CPNI Order that the most reasonable interpretation of the interplay of sections 222 and 272 is that section 272 does not impose any additional obligations on the BOCs when they share CPNI with their section 272 affiliates.X0ÍX0Í0#X\  P}G;P# I. A. 1. a.(1)(a) i) a)#Xj\  P}G;XP#` hp x (##X\  P}G;P# ÍCPNI Order, 13 FCC Rcd at 8179,  169.0 We disagree with the parties that argue that we misinterpreted the relationship between section 222 and 272. A number of carriers assert that section 272 sets out additional requirements for BOCs with respect to the transfer of CPNI to section 272 affiliates than are required by section 222 alone.X0ÍX0Í#X\  P}G;P# I. A. 1. a.(1)(a) i) a)#Xj\  P}G;XP#` hp x (##X\  P}G;P# ÍAT&T Petition at 2324; CompTel Petition at 210; MCI Petition at 621; Sprint Petition at 68; Intermedia Comments at 69; WorldCom Comments at 37; TRA Comments at 25. For the same reasons described in the CPNI Order, however, we conclude that our prior interpretation of the relationship between sections 222 and 272 is correct.X0ÍX0Í#X\  P}G;P# I. A. 1. a.(1)(a) i) a)#Xj\  P}G;XP#` hp x (##X\  P}G;P# ÍAmeritech Comments at 911; Bell Atlantic Comments at 25; BellSouth Comments at 1416; SBC Comments at 914; U S WEST Comments at 610. At the outset, we reject MCI's argument that there was not adequate notice that the Commission might reverse its conclusion in the NonAccounting Safeguards Order relating to CPNI.X0ÍX0Í#X\  P}G;P# I. A. 1. a.(1)(a) i) a)#Xj\  P}G;XP#` hp x (##X\  P}G;P# ÍMCI Petition at 67. On February 20, 1997, in a Public Notice issued subsequent to the NonAccounting Safeguards Order, but prior to the CPNI Order, the Commission sought comment on specific questions for the CPNI rulemaking proceeding.X0ÍX0Í#X\  P}G;P# I. A. 1. a.(1)(a) i) a)#Xj\  P}G;XP#` hp x (##X\  P}G;P# ÍTelecommunications Carriers' Use of Customer Proprietary Network Information and Other Customer Information, Public Notice, CC Docket No. 096115, DA 97385 (rel. Feb. 20, 1997) (Public Notice). Although the Public Notice did not specifically seek comment on whether the NonAccounting Safeguards Order's conclusion should be reversed, it did pose a series of detailed questions relating to the interplay between sections 222 and 272. For example, the Public Notice inquired whether:  . . . the requirement in section 272(c)(1) that a BOC may not discriminate between its section 272 "affiliate and any other entity in the provision or procurement of . . . services . . . and information . . ." mean that a BOC may use, disclose, or permit access to CPNI for or on behalf of that affiliate only if the CPNI is made available to all other entities? If not, what obligation does the nondiscrimination requirement of section 272(c)(1) impose on a BOC with respect to the use, disclosure, or permission of access to CPNI? Parties were, therefore, on notice that we might reconsider our conclusion concerning the relationship between sections 222 and 272. Accordingly, we affirm our conclusion that notice was adequate. We further disagree with MCI's claim that the Commission's "approach" is flawed by its "failure to analyze MCI's proposed nondiscrimination rule on its own terms."X0ÍX0Í#X\  P}G;P# I. A. 1. a.(1)(a) i) a)#Xj\  P}G;XP#` hp x (##X\  P}G;P# ÍMCI Petition at 8. MCI asserts without support that it previously proposed"presumably in its comments or reply comments to the NPRM"that section 272(c)(1) requires that BOCs that obtain a customer's approval to use his or her CPNI on behalf of a section 272 affiliate or to disclose CPNI to a section 272 affiliate must likewise provide customer CPNI to any third party that can demonstrate that it has also obtained that customer's oral approval.X0ÍX0Í#X\  P}G;P# I. A. 1. a.(1)(a) i) a)#Xj\  P}G;XP#` hp x (##X\  P}G;P# ÍMCI Petition at 2, 810. MCI contends that the Commission "admitted" that MCI's proposal is consistent with section 222, but improperly rejected the proposal.X0ÍX0Í#X\  P}G;P# I. A. 1. a.(1)(a) i) a)#Xj\  P}G;XP#` hp x (##X\  P}G;P# ÍMCI Petition at 9. Although we addressed the substance of this argument in the CPNI Order, it is not clear that it was MCI that raised the argument at that time. In any case, MCI's contention apparently refers to our conclusion that requiring BOCs to disclose CPNI to unrelated entities upon oral customer approval when they share CPNI with their section 272 affiliates upon oral approval is not necessarily inconsistent with section 222.X0ÍX0Í3#X\  P}G;P# I. A. 1. a.(1)(a) i) a)#Xj\  P}G;XP#` hp x (##X\  P}G;P# ÍCPNI Order, 13 FCC Rcd at 817677,  163.3 MCI fails to mention, however, that we further concluded that if that aspect of section 272(c)(1) was applicable, there would be no principled basis upon which not to impose other obligations required by that section. We concluded that if section 272(c)(1)'s nondiscrimination obligation applies to the form of customer approval then it would also apply when BOCs solicit customer approval to share CPNI with their 272 affiliates.X0ÍX0Í3#X\  P}G;P# I. A. 1. a.(1)(a) i) a)#Xj\  P}G;XP#` hp x (##X\  P}G;P# ÍCPNI Order, 13 FCC Rcd at 817677,  163.3 In other words, section 272(c)(1) would seemingly require BOCs to solicit customer authorizations on behalf of other carriers when soliciting for such authorizations on behalf of their own BOC affiliates. We further concluded that such a requirement would present insurmountable hurdles for BOC compliance with section 222.X0ÍX0Í3#X\  P}G;P# I. A. 1. a.(1)(a) i) a)#Xj\  P}G;XP#` hp x (##X\  P}G;P# ÍCPNI Order, 13 FCC Rcd at 817677,  163.3 We noted that requiring BOCs to solicit approval for unspecified "all other" entities would neither constitute effective notice nor informed approval as customers cannot knowingly approve release of their CPNI unless and until they are made aware of the identity of the party that will receive the CPNI.X0ÍX0Í0#X\  P}G;P# I. A. 1. a.(1)(a) i) a)#Xj\  P}G;XP#` hp x (##X\  P}G;P# ÍCPNI Order, 13 FCC Rcd at 8177,  163.0 Alternatively, we also noted, it would be difficult as a practical matter for BOCs to provide specific notice, and obtain informed approval, for each entity that so requests.X0ÍX0Í0#X\  P}G;P# I. A. 1. a.(1)(a) i) a)#Xj\  P}G;XP#` hp x (##X\  P}G;P# ÍCPNI Order, 13 FCC Rcd at 8177,  163.0 MCI is incorrect, therefore, that we failed to analyze this proposal on its own terms. We did so and rejected it in the CPNI Order. Accordingly, we affirm our previous conclusion based upon our prior reasoning. We also reject MCI and TRA's argument that the "except as required by law" clause in section 222(c)(1) encompasses, at least in part, section 272(c)(1).X0ÍX0Í(#X\  P}G;P# I. A. 1. a.(1)(a) i) a)#Xj\  P}G;XP#` hp x (##X\  P}G;P# ÍMCI Petition at 78; TRA Comments at 3.( Both parties conclude that as a result of their interpretation of this clause there is no conflict between sections 222 and 272, and that section 272 trumps section 222.X0ÍX0Í(#X\  P}G;P# I. A. 1. a.(1)(a) i) a)#Xj\  P}G;XP#` hp x (##X\  P}G;P# ÍMCI Petition at 78; TRA Comments at 3.( Bell Atlantic and SBC oppose this interpretation.X0ÍX0Í3#X\  P}G;P# I. A. 1. a.(1)(a) i) a)#Xj\  P}G;XP#` hp x (##X\  P}G;P# ÍBell Atlantic Comments at 34; SBC Comments at 11.3 SBC and Bell Atlantic respectively counter that Congress intended the "except required by law" clause as an exception (1) for disclosures pursuant to court order,X0ÍX0Í#X\  P}G;P# I. A. 1. a.(1)(a) i) a)#Xj\  P}G;XP#` hp x (##X\  P}G;P# ÍSBC Comments at 11. and (2) to law enforcement agencies, regulators, and other public officials as required by subpoena regulation, statute, or other legal process.X0ÍX0Í#X\  P}G;P# I. A. 1. a.(1)(a) i) a)#Xj\  P}G;XP#` hp x (##X\  P}G;P# ÍBell Atlantic Comments at 3. Bell Atlantic also argues that if Congress meant to include section 272 as an exception to section 222 then it would have specifically included a reference to the section as it has done in other parts of the Act.X0ÍX0Í##X\  P}G;P# I. A. 1. a.(1)(a) i) a)#Xj\  P}G;XP#` hp x (##X\  P}G;P# ÍBell Atlantic Comments at 4 & n.2.# Although SBC and Bell Atlantic have proposed possible interpretations of this clause, we do not agree that those are the only interpretations. Unfortunately, the legislative history provides little guidance either way,X0ÍX0Í/#X\  P}G;P# I. A. 1. a.(1)(a) i) a)#Xj\  P}G;XP#` hp x (##X\  P}G;P# ÍThe only related reference in the legislative history is a statement in the Joint Explanatory Statement's description of the Senate bill, and not the Conference agreement, which states as follows: ` ` ` [i]n general, a BOC may not share with anyone customerspecific proprietary information without the consent of the person to whom it relates. Exceptions to this general rule permit disclosure in response to a court order or to initiate, render, bill and collect for telecommunications services. Joint Explanatory Statement at 203./ and MCI and TRA's position is also plausible. Thus, we conclude that the meaning of this clause is ambiguous. As such, we must interpret this clause in a way that best reflects the statutory design and furthers the policies of the 1996 Act. We conclude, for the same reasons as those we previously described in the CPNI Order,X0ÍX0Í6#X\  P}G;P# I. A. 1. a.(1)(a) i) a)#Xj\  P}G;XP#` hp x (##X\  P}G;P# ÍCPNI Order, 13 FCC Rcd at 817579,  16169.6 that the "except as required by law" clause does not encompass section 272. We affirm the CPNI Order's conclusion that the term "information" in section 272(c)(1) does not include CPNIX0ÍX0Í>#X\  P}G;P# I. A. 1. a.(1)(a) i) a)#Xj\  P}G;XP#` hp x (##X\  P}G;P# ÍCPNI Order, 13 FCC Rcd at 817172, 8174,  154, 158.> despite CompTel and Intermedia's assertion that such an interpretation is contrary to the plain meaning of the Act and should be reconsidered. They argue that where Congress intended to limit the term "information" it did so explicitly, but the term "information" in section 272(c)(1) is not qualified or limited in that way.X0ÍX0Í#X\  P}G;P# I. A. 1. a.(1)(a) i) a)#Xj\  P}G;XP#` hp x (##X\  P}G;P# ÍCompTel Petition at 45. Moreover, both argue that the fact that section 272(g)(3) contains the only exception to section 272(c) specifically created by Congress adds weight to its broad construction of the term "information" in section 272(c)(1). Finally, Intermedia argues that the definition of CPNI as "information that relates to the quantity, technical configuration, type, destination, and amount of use of a telecommunications service . . ." indicates that CPNI falls squarely within the category of "information" in section 272(c)(1). Taken in context of the entire Act, it is not readily apparent that the meaning of "information" in section 272 necessarily includes CPNI. As we stated in the CPNI Order, the sections read together could also indicate that section 222's specific definition of CPNI is meant to govern the more general use of the term "information" in section 272(c)(1).X0ÍX0ÍR#X\  P}G;P# I. A. 1. a.(1)(a) i) a)#Xj\  P}G;XP#` hp x (##X\  P}G;P# ÍCPNI Order, 13 FCC Rcd at 817475,  160. 47 U.S.C.  222(f)(1) defines CPNI, in part, as: (A) information that relates to the quantity, technical configuration, type, destination, and amount of use of a telecommunications service subscribed to by any customer of a telecommunications carrier, and that is made available to the carrier by the customer solely by virtue of the carriercustomer relationship; and (B) information contained in the bills pertaining to telephone exchange service or telephone toll service received by a customer of a carrier . . ..R While the legislative history is silent about the meaning of "information" in section 272(c)(1), the structure of the Act indicates strongly that the provision is susceptible to differing meanings. Indeed, as the courts have cautioned, the Commission is bound to move beyond dictionary meanings of terms and to consider other possible interpretations, assess statutory objectives, weigh congressional policy, and apply our expertise in telecommunications in determining the meaning of provisions.X0ÍX0Í[#X\  P}G;P# I. A. 1. a.(1)(a) i) a)#Xj\  P}G;XP#` hp x (##X\  P}G;P# ÍSee Alarm Indus. Communications Comm. v. FCC, 131 F.3d 1066, 1069 (D.C. Cir. 1997).[ In this instance, we believe that the structure of the Act belies petitioners' contention that the term "information" has a plain meaning that encompasses CPNI. In enacting section 222, Congress carved out very specific restrictions governing consumer privacy in CPNI and consolidated those restrictions in a single, comprehensive provision. We believe that the specific requirements governing CPNI use are contained in that section and we disfavor, accordingly, an interpretation of section 272 that would create constraints for CPNI beyond those embodied in the specific provision delineating those constraints. As a practical matter, the interpretation proffered by petitioners would bar BOCs from sharing CPNI with their affiliates: the burden imposed by the nondiscrimination requirements would, in this context, pose a potentially insurmountable burden because a BOC soliciting approval to share CPNI with its affiliate would have to solicit approval for countless other carriers as well, known or unknown.X0ÍX0Í0#X\  P}G;P# I. A. 1. a.(1)(a) i) a)#Xj\  P}G;XP#` hp x (##X\  P}G;P# ÍCPNI Order, 13 FCC Rcd at 8174,  159.0 We do not believe that is what Congress envisioned when it enacted sections 222 and 272. Rather, as we concluded in the CPNI Order, we find it a more reasonable interpretation of the statute to conclude that section 222 contemplates a sharing of CPNI among all affiliates (whether BOCs or others), consistent with customer expectations that related entities will share information so as to offer services best tailored to customers' needs.X0ÍX0Í0#X\  P}G;P# I. A. 1. a.(1)(a) i) a)#Xj\  P}G;XP#` hp x (##X\  P}G;P# ÍCPNI Order, 13 FCC Rcd at 8175,  160.0 For these reasons, we find that the "plain meaning" argument raised by Comptel and Intermedia is not persuasive, and further that their meaning is not the one Congress most likely intended. Therefore, we affirm our previous conclusion.  In addition, we are not persuaded by CompTel's assertion that there is no indication that section 222 was intended to trump section 272 because the Commission previously recognized, in the First Report and Order, that section 222's obligations are not exclusive.X0ÍX0Í#X\  P}G;P# I. A. 1. a.(1)(a) i) a)#Xj\  P}G;XP#` hp x (##X\  P}G;P# ÍCompTel Petition at 6. We held in the First Report and Order that customer authorization pursuant to section 222(c)(1) does not extend to any CPNI subject to the Section 275(d) prohibition.X0ÍX0Í;#X\  P}G;P# I. A. 1. a.(1)(a) i) a)#Xj\  P}G;XP#` hp x (##X\  P}G;P# ÍIn the Matter of Implementation of the Telecommunications Act of 1996: Telecommunications Carriers' Use of Customer Proprietary Network Information; Use of Data Regarding Alarm Monitoring Service Providers, Report and Order, CC Docket No. 96115, 11 FCC Rcd 9553, 9557,  9 (First Report and Order).; Section 275(d) prohibits local exchange carriers from the using or recording "in any fashion the occurrence or contents of calls received by providers of alarm monitoring services for the purposes of marketing such services on behalf of such local exchange carrier, or any other entity."X0ÍX0Í#X\  P}G;P# I. A. 1. a.(1)(a) i) a)#Xj\  P}G;XP#` hp x (##X\  P}G;P# Í47 U.S.C.  275(d). Thus, section 275(d) specifically describes a subset of CPNI, namely information concerning the occurrence of calls received by alarm monitoring service providers, that may not be used by local exchange carriers for marketing of alarm monitoring services on their own behalf or on behalf of any other entity.X0ÍX0Í#X\  P}G;P# I. A. 1. a.(1)(a) i) a)#Xj\  P}G;XP#` hp x (##X\  P}G;P# Í47 U.S.C.  275(d). Because Congress unambiguously prohibited the use of such CPNI in section 275(d), we concluded that the specific prohibition in section 275(d) controls the general CPNI rules described in section 222.X0ÍX0ÍD#X\  P}G;P# I. A. 1. a.(1)(a) i) a)#Xj\  P}G;XP#` hp x (##X\  P}G;P# ÍSee First Report and Order, 11 FCC Rcd at 9557,  9.D This stands in stark contrast to the difficult task of reconciling sections 222 and 272.X0ÍX0Í3#X\  P}G;P# I. A. 1. a.(1)(a) i) a)#Xj\  P}G;XP#` hp x (##X\  P}G;P# ÍCPNI Order, 13 FCC Rcd at 817475,  160.3 Moreover, we do not agree with WorldCom's assertion that the Commission ignored section 272(b)(1). WorldCom argues that Section 272(b)(1) requires that a section 272 affiliate "operate independently from the Bell operating company," and prohibits the section 272 affiliate from providing or coordinating any of its CPNIrelated functions with the BOC when read in conjunction with section 222.X0ÍX0Í#X\  P}G;P# I. A. 1. a.(1)(a) i) a)#Xj\  P}G;XP#` hp x (##X\  P}G;P# ÍWorldCom Comments at 6. WorldCom apparently believes that the "operate independently" requirement of section 272(b)(1), when read in conjunction with section 222, demonstrates Congressional intent to establish a statutory dichotomy between CPNI and CPNIrelated services used, disclosed, or accessed by other unaffiliated entities.X0ÍX0Í#X\  P}G;P# I. A. 1. a.(1)(a) i) a)#Xj\  P}G;XP#` hp x (##X\  P}G;P# ÍWorldCom Comments at 6. WorldCom is incorrect, however, that we "ignored" section 272(b)(1). Rather, the Commission directly addressed this argument in the CPNI Order.X0ÍX0Í8#X\  P}G;P# I. A. 1. a.(1)(a) i) a)#Xj\  P}G;XP#` hp x (##X\  P}G;P# ÍCPNI Order, 13 FCC Rcd at 8179,  168 & n.582.8 Thus, we deny reconsideration on this basis as WorldCom has not presented any new arguments or facts we did not already consider. Finally, several parties also argue that our interpretation of the interplay of sections 222 and 272 gives BOC affiliates an unfair competitive advantage over other competitors.X0ÍX0Íb#X\  P}G;P# I. A. 1. a.(1)(a) i) a)#Xj\  P}G;XP#` hp x (##X\  P}G;P# ÍAT&T Petition at 2324; CompTel Petition at 710; Sprint Petition at 7; Intermedia Comments at 9.b These parties raise no new arguments or facts on reconsideration of this point that we did not already consider. We previously identified in detail specific mechanisms in section 222 that address such competitive concerns.X0ÍX0Í6#X\  P}G;P# I. A. 1. a.(1)(a) i) a)#Xj\  P}G;XP#` hp x (##X\  P}G;P# ÍCPNI Order, 13 FCC Rcd at 817778,  16467.6 We therefore deny these parties' requests for reconsideration of this conclusion.  B.Disclosure of NonCPNI Information Pursuant to Section 272 The Commission noted in a footnote in the CPNI Order that BOC nondiscrimination obligations under section 272 would apply to the sharing of all other information and services with their section 272 affiliates.X0ÍX0Íg#X\  P}G;P# I. A. 1. a.(1)(a) i) a)#Xj\  P}G;XP#` hp x (##X\  P}G;P# ÍCPNI Order, 13 FCC Rcd at 8177,  164, n.573 ("We note, however, that our interpretation does not render the BOCs' nondiscrimination obligations as to 'information' or 'services' in section 272 meaningless. The requirement would apply to the BOCs' sharing of all other information (i.e., nonCPNI) and services with their section 272 affiliates.").g The Common Carrier Bureau further concluded in the Clarification Order that a customer's name, address, and telephone number are not CPNI.X0ÍX0Í;#X\  P}G;P# I. A. 1. a.(1)(a) i) a)#Xj\  P}G;XP#` hp x (##X\  P}G;P# ÍClarification Order, 13 FCC Rcd at 1239697,  9.; The Bureau reasoned that "[i]f the definition of CPNI included a customer's name, address, and telephone number, a carrier would be prohibited from using its business records to contact any of its customers to market any new service that falls outside the scope of the existing service relationship with those customers.X0ÍX0Í;#X\  P}G;P# I. A. 1. a.(1)(a) i) a)#Xj\  P}G;XP#` hp x (##X\  P}G;P# ÍClarification Order, 13 FCC Rcd at 1239697,  9.;  We agree with the Common Carrier Bureau's clarification and adopt its reasoning and conclusion as our own. Accordingly, we grant MCI's request that we clarify that a customer's name, address, and telephone number are "information" for purposes of section 272(c)(1), and if a BOC makes such information available to its affiliate, then it must make that information available to nonaffiliated entities.X0ÍX0Í#X\  P}G;P# I. A. 1. a.(1)(a) i) a)#Xj\  P}G;XP#` hp x (##X\  P}G;P# ÍMCI Petition at 13. We note, as the Bureau did, that our conclusion is not intended to override any other obligations carriers may have with respect to customer information, such as those imposed under section 64.1201 of the Commission's rules relating to carrier disclosure of customer billing names and addresses. See Clarification Order, 13 FCC Rcd at 12396,  9, n.20. We reject U S WEST's bald assertion that requiring disclosure of this information would raise "serious constitutional issues, such as those already presented by U S WEST." U S WEST does not explain which constitutional issues it considers implicated by this determination. To the extent that U S WEST means to incorporate any constitutional arguments raised by U S WEST and addressed in the CPNI Order, we reject those arguments for the reasons set forth in that order.X0ÍX0Í#X\  P}G;P# I. A. 1. a.(1)(a) i) a)#Xj\  P}G;XP#` hp x (##X\  P}G;P# ÍU S WEST Comments at 14. We also deny U S WEST's request that the Commission hold that section 222 controls all issues involving customer information, rather than issues pertaining to CPNI.X0ÍX0Í#X\  P}G;P# I. A. 1. a.(1)(a) i) a)#Xj\  P}G;XP#` hp x (##X\  P}G;P# ÍU S WEST Comments at 1415. We are not persuaded that any portion of section 222 indicates that Congress intended such a result, nor does U S WEST delineate any portion of section 222 that would support its argument. Finally, we reject SBC's argument that, although this information is not CPNI, it is an activity that is encompassed within the joint marketing exception in section 272(g)(3) of the 1996 Act because "use of lists of such information is an integral part of"indeed, is likely the first step of"the overall marketing of long distance services."X0ÍX0Í#X\  P}G;P# I. A. 1. a.(1)(a) i) a)#Xj\  P}G;XP#` hp x (##X\  P}G;P# ÍSBC Comments at 14. Such a consideration is outside the purview of this proceeding. MCI also argues that the Commission should find that a customer's PIC choice and PICfreeze status are not CPNI as defined in section 222(f)(1).X0ÍX0Í#X\  P}G;P# I. A. 1. a.(1)(a) i) a)#Xj\  P}G;XP#` hp x (##X\  P}G;P# ÍMCI Petition at 14. Several carriers oppose MCI's argument.X0ÍX0Í^#X\  P}G;P# I. A. 1. a.(1)(a) i) a)#Xj\  P}G;XP#` hp x (##X\  P}G;P# ÍE.g., Bell Atlantic Comments at 56; GTE Comments at 2324; U S WEST Comments at 2324.^ MCI asserts that the identity of a customer's carrier is not information concerning the "type" of service under section 222(f)(1)(A) and is not information "pertaining to" the service itself under section 222(f)(1)(B) despite the fact that the customer's PIC choice appears on the customer's telephone bill.X0ÍX0Í#X\  P}G;P# I. A. 1. a.(1)(a) i) a)#Xj\  P}G;XP#` hp x (##X\  P}G;P# ÍMCI Petition at 16. MCI further discloses that it has argued in its Comments to the FNPRM in the CPNI Order that a customer's PIC choice and PIC changes are carrier proprietary information of the interexchange carrier. Id. As such, MCI argues, a local exchange carrier may not use such information for marketing purposes. Id. We decline to address this argument in this proceeding because it is more appropriately left to the FNPRM. MCI argues that PICfreeze information does not meet the definition of CPNI for like reasons. We are not persuaded by MCI's statutory interpretation. We conclude that a customer's PIC choice falls squarely within the definition of CPNI set out in both sections 222(f)(1)(A) and (B), and that PICfreeze information meets the requirements of section 222(f)(1)(A). Finally, we agree with GTE that this result is consistent with the privacy goals set out by Congress in section 222.X0ÍX0Í#X\  P}G;P# I. A. 1. a.(1)(a) i) a)#Xj\  P}G;XP#` hp x (##X\  P}G;P# ÍGTE Comments at 24 ("Given the privacy and consumer protection interests at stake, PIC and PICfreeze information is precisely the type of information that customers want to be kept confidential from third parties."). C.Section 222 and Section 254 CenturyTel also argues that restricting the use of CPNI in marketing enhanced services and CPE to existing customers in rural exchanges is inconsistent with Universal Service provisions of the Act.X0ÍX0Í#X\  P}G;P# I. A. 1. a.(1)(a) i) a)#Xj\  P}G;XP#` hp x (##X\  P}G;P# ÍCenturyTel Reply at 5. CenturyTel argues that section 222(c) of the Act permits a carrier to use CPNI in the provision of new service if "...required by law or with approval of the customer... ." CenturyTel further argues that the Commission failed to include the "required by law" exception to the restrictions on the use of CPNI, and only included the "customer approval" exception in its rulesX0ÍX0Í #X\  P}G;P# I. A. 1. a.(1)(a) i) a)#Xj\  P}G;XP#` hp x (##X\  P}G;P# ÍId. . CenturyTel maintains that the Commission must harmonize the two provisions of law by inserting the "required by law" exception to the CPNI rules, and recognizing that Congress's Universal Service requirements provide an additional exception to the CPNI restrictions.X0ÍX0Í#X\  P}G;P# I. A. 1. a.(1)(a) i) a)#Xj\  P}G;XP#` hp x (##X\  P}G;P# ÍId. at 6. CenturyTel maintains that the Commission should permit rural telephone companies, as defined in section 153(37) of the Act to use, disclose, or permit access to CPNI to market to an existing customer in rural areas served by the rural telephone company categories of service to which that customer does not already subscribe.X0ÍX0Í#X\  P}G;P# I. A. 1. a.(1)(a) i) a)#Xj\  P}G;XP#` hp x (##X\  P}G;P# ÍId. at 7. NTCA makes a similar argument. NTCA argues that the Commission is under a statutory mandate to promote the delivery of advanced telecommunications capability to rural areas on a reasonable and timely basis.X0ÍX0Í#X\  P}G;P# I. A. 1. a.(1)(a) i) a)#Xj\  P}G;XP#` hp x (##X\  P}G;P# ÍNTCA Petition at 4. NTCA points out that very often in a rural area, there is only one provider of telecommunications service, and the carrier does not benefit from an unfair competitive advantage by promoting new services or equipment to its subscribers.X0ÍX0Í #X\  P}G;P# I. A. 1. a.(1)(a) i) a)#Xj\  P}G;XP#` hp x (##X\  P}G;P# ÍId.  NTCA therefore requests that the Commission reconsider its "total service approach", stating that it disadvantages small LECs seeking to expand the array of services rural customers demand. TDS, in addition, asserts that restrictions on the use of CPNI to market information services run counter to the goal of affordable telecommunications and information services of section 254(b)(3) of the Act.X0ÍX0Í#X\  P}G;P# I. A. 1. a.(1)(a) i) a)#Xj\  P}G;XP#` hp x (##X\  P}G;P# ÍTDS Petition at 7. We disagree with the arguments made by CenturyTel and NTCA. As stated in Section V.A of this Order, we affirm the "total service approach" for all carriers. We find no reason to impose different notification requirements on large and small carriers. As we stated in the CPNI Order, concerns regarding customer privacy are the same irrespective of the carrier's size or identity.X0ÍX0Í0#X\  P}G;P# I. A. 1. a.(1)(a) i) a)#Xj\  P}G;XP#` hp x (##X\  P}G;P# ÍCPNI Order, 13 FCC Rcd at 8161,  134.0 Further to the extent that CenturyTel and NTCA are requesting to use CPNI, without customer approval, to market CPE and certain information services, those requests have been granted above.X0ÍX0Í!#X\  P}G;P# I. A. 1. a.(1)(a) i) a)#Xj\  P}G;XP#` hp x (##X\  P}G;P# ÍSee Part V.B, supra.! We also disagree with CenturyTel and NTCAs argument that section 254 requires the use of CPNI to allow rural carriers to implement Congress Universal Service standards. Section 254 envisions that rural carriers would introduce and make available new technology to all of its customers. The CPNI rules in no way discourage rural carriers from doing that. In fact, one could argue that some of the CPNI rules require a carrier to make all of its customers aware of such new technology rather than using CPNI to pick and choose which customers to market the new technology to. The basis of CenturyTel and NTCAs arguments, however, is that they do not want to market the new technology to all of its customers. They want to make it available only to certain customers that they select by using their customers CPNI. We fail to see how section 254 requires this outcome. D.Application of Nondiscrimination Rules Under Sections 201(b) and 202(a) We reject MCI's argument that the nondiscrimination requirement described in section 272 should be applied to all ILECs through the requirements of sections 201(b) and 202(a).X0ÍX0Í#X\  P}G;P# I. A. 1. a.(1)(a) i) a)#Xj\  P}G;XP#` hp x (##X\  P}G;P# ÍMCI Petition at 1821. See also LCI Petition at 15; AT&T Reply at 2223 & n. 24. Several parties oppose MCI's proposition. GTE Comments at 2022; Sprint Comments at 68; Independent Alliance Reply at 89. MCI asserts that "the leveraging of dominance in one telecommunications market in order to gain a competitive advantage in another telecommunications market is an unreasonable and unjust practice in violation of Section 201(b)."X0ÍX0Í#X\  P}G;P# I. A. 1. a.(1)(a) i) a)#Xj\  P}G;XP#` hp x (##X\  P}G;P# ÍMCI Petition at 1819. MCI further asserts that it is a violation of section 202(a) "[f]or an ILEC to favor its own affiliate with local service CPNI and other customerspecific information that is not made available to competitors" as such an action would provide an "undue or unreasonable preference or advantage" to such an affiliate.X0ÍX0Í#X\  P}G;P# I. A. 1. a.(1)(a) i) a)#Xj\  P}G;XP#` hp x (##X\  P}G;P# ÍMCI Petition at 19. Thus, MCI concludes sections 201(b) and 202(a) require that an ILEC, including BOCs, must electronically transmit a customer's CPNI to any other entity that has obtained that customer's oral approval upon the ILEC's use of such CPNI for marketing on behalf of its interexchange affiliate or disclosure of the CPNI to its affiliate.X0ÍX0Í#X\  P}G;P# I. A. 1. a.(1)(a) i) a)#Xj\  P}G;XP#` hp x (##X\  P}G;P# ÍMCI Petition at 19. We agree with GTE that there is no justification to conclude, as a matter of statutory construction, that the broad nondiscrimination requirements of these sections impose a specific disclosure obligation on ILEC use of CPNI.X0ÍX0Í#X\  P}G;P# I. A. 1. a.(1)(a) i) a)#Xj\  P}G;XP#` hp x (##X\  P}G;P# ÍGTE Comments at 21. In any case, the same privacy concerns we identified in our discussion of the relationship between sections 222 and 272 apply here equally. For instance, requiring the disclosure of CPNI to other companies to maintain competitive neutrality would defeat, rather than protect, customers' privacy expectations and control over their own CPNI.X0ÍX0Í0#X\  P}G;P# I. A. 1. a.(1)(a) i) a)#Xj\  P}G;XP#` hp x (##X\  P}G;P# ÍCPNI Order, 13 FCC Rcd at 8176,  162.0 We conclude that the specific consumer privacy and consumer choice protections established in section 222 supersede the general protections identified in sections 201(b) and 202(a). Thus, we are not persuaded that section 201(b) or section 202(a) require the result MCI seeks. Accordingly, we reject MCI's request. IX. OTHER ISSUES  A.Status of Customer Rewards Program   Section 64.2005(b) of the Commission's Rules prohibits a telecommunications carrier from using, disclosing, or permitting access to CPNI to market to a customer, without customer approval, service offerings that are within a category of service to which the customer does not already subscribe. Omnipoint and Vanguard contend that when a carrier provides free rewards, such as free equipment, for the purpose of retaining its accounts, the prohibition in section 64.2005(b) should not apply because (1) the customer subscribes to the service for which the reward is provided; and (2) the reward is free, and therefore is not marketed.X0ÍX0ÍL#X\  P}G;P# I. A. 1. a.(1)(a) i) a)#Xj\  P}G;XP#` hp x (##X\  P}G;P# ÍOmnipoint Petition at 19; Omnipoint Reply at 8; Vanguard Petition at 1516.L Omnipoint and Vanguard request clarification because they claim that carriers are more likely to offer rewards if they are able to target them to highvolume or longterm customers, and if carriers do not need to seek customer approval.X0ÍX0ÍL#X\  P}G;P# I. A. 1. a.(1)(a) i) a)#Xj\  P}G;XP#` hp x (##X\  P}G;P# ÍOmnipoint Petition at 19; Omnipoint Reply at 8; Vanguard Petition at 1516.L No party has objected to this proposal.  We agree with Omnipoint and Vanguard that, where a carrier uses CPNI to provide free rewards to its customer, such use of CPNI is within the scope of the carriercustomer relationship. As such, the use of the CPNI is limited to the existing service relationship between the carrier and the customer. Therefore, although the provision of free rewards is a marketing activity, it does not violate the Act or our rules, provided the telecommunications service being marketed is the service currently subscribed to by the customer.X0ÍX0Í#X\  P}G;P# I. A. 1. a.(1)(a) i) a)#Xj\  P}G;XP#` hp x (##X\  P}G;P# ÍVanguard Petition at 16. B.Nontelecommunications Services Listed on Telephone Bill CPNI is defined in section 222(f)(1)(B) of the Act as including information contained in the bills pertaining to telephone exchange service or telephone toll service received by a customer of a carrier; except that such term does not include subscriber list information. However, section 222(c)(1) prohibits a carrier's use of CPNI only where it receives the CPNI by virtue of its provision of a telecommunications service. In the Common Carrier Bureau's Clarification Order, the Bureau said that customer information derived from the provision of any nontelecommunications service, such as CPE or information services . . . may be used to provide or market any telecommunications service . . . .X0ÍX0Í;#X\  P}G;P# I. A. 1. a.(1)(a) i) a)#Xj\  P}G;XP#` hp x (##X\  P}G;P# ÍClarification Order, 13 FCC Rcd at 1239293,  3.; Omnipoint asks the Commission to clarify that section 222 does not prohibit the use of customer information derived from nontelecommunications services bundled with telecommunications services merely because charges for those services appeared on a customer's telephone bill. Omnipoint contends that its position logically follows from the statement in the Clarification Order.X0ÍX0Í#X\  P}G;P# I. A. 1. a.(1)(a) i) a)#Xj\  P}G;XP#` hp x (##X\  P}G;P# ÍOmnipoint Petition at 1920. U S WEST agrees with Omnipoint's position, but contends that the statute is clear, and no clarification is required.X0ÍX0Í#X\  P}G;P# I. A. 1. a.(1)(a) i) a)#Xj\  P}G;XP#` hp x (##X\  P}G;P# ÍU S WEST Comments at 2425.  Section 222(c)(1) prohibits the use of CPNI only where it is derived from the provision of a telecommunications service. Consequently, we find that information that is not received by a carrier in connection with its provision of telecommunications service can be used by the carrier without customer approval, regardless of whether such information is contained in a bill generated by the carrier. Therefore, consistent with the Clarification Order, customer information derived from information services that are held not to be telecommunications services may be used, even if the telephone bill covers charges for such information services. C.  Provision of Calling Card As "Provision" of Service LECs often offer socalled "postpaid" calling cards that enable customers to complete long distance calls over a particular interexchange carrier's network when the customer is away from home. Such cards enable a customer to have the calls billed subsequently on the customer's local bill issued by the LEC. MCI asks the Commission to clarify that LECs may not use CPNI garnered in such circumstances to market services that the LEC offers absent permission from the customer.X0ÍX0Í#X\  P}G;P# I. A. 1. a.(1)(a) i) a)#Xj\  P}G;XP#` hp x (##X\  P}G;P# ÍMCI Petition at 46. We grant MCI's request for clarification. In the traditional LEC postpaid calling card situation, the LEC serves merely as a billing and collection agent on behalf of the interexchange carrier, much as the LEC does when a customer places long distance calls from home through the customer's presubscribed interexchange carrier (IXC). In both instances, the customer has established a customercarrier relationship for the provision of interexchange services with the IXC that carried the customer's call over its network. The LEC, on the other hand, is standing in the place of the IXC only for billing and collection purposes, a service which the IXC could have chosen to provide itself. Where a LEC acts as a billing and collection agent, it may not use CPNI without the customer's permission under the total services approach.  D.Use of CPNI to Prevent Fraud  Section 222(d)(2) of the Act permits the use of CPNI to protect the rights or property of the carrier, or to protect users of those services and other carriers from fraudulent, abusive, or unlawful use of, or subscription to services . . . . Section 64.2005 of the Commission's Rules provides that a telecommunications carrier may use, disclose, or permit access to CPNI, without customer approval, for a number of purposes, but does not mention the use of CPNI in connection with fraud prevention programs.X0ÍX0Í#X\  P}G;P# I. A. 1. a.(1)(a) i) a)#Xj\  P}G;XP#` hp x (##X\  P}G;P# Í47 C.F.R.  64.2005. Comcast requests that the Commission clarify its rules to specify that (1) carriers are authorized to use CPNI in connection with fraud prevention programs; and (2) such use is permissible even after a customer has terminated service from the carrier making such use of the customer's CPNI.X0ÍX0Í#X\  P}G;P# I. A. 1. a.(1)(a) i) a)#Xj\  P}G;XP#` hp x (##X\  P}G;P# ÍComcast Petition at 19. U S WEST argues that there is no need for the clarification requested by Comcast, because the statute is clear.X0ÍX0Í#X\  P}G;P# I. A. 1. a.(1)(a) i) a)#Xj\  P}G;XP#` hp x (##X\  P}G;P# ÍU S WEST Comments at 21.  We agree that Section 222(d)(2) on its face permits the use of CPNI in connection with fraud prevention programs, and does not limit such use of CPNI that is generated during the customer's period of service to any period of time. Since our rules do not cover the use of CPNI for fraud prevention programs, we will amend our rules to do so, in order to eliminate the possibility of misinterpretation. E.Definition of "Subscribed" in Section 222(f)(1)(A) We grant MCI's request for clarification of the meaning of the phrase "service subscribed to by any other customer" in section 222(f)(1)(A).X0ÍX0Í#X\  P}G;P# I. A. 1. a.(1)(a) i) a)#Xj\  P}G;XP#` hp x (##X\  P}G;P# ÍMCI Petition at 4849. Section 222(f)(1) defines CPNI, in part, as follows:  (A) information that relates to the quantity, technical configuration, type, destination, and amount of use of a telecommunications service subscribed to by any customer of a telecommunications carrier, and that is made available to the carrier by the customer solely by virtue of the customercarrier relationship; and (B) information contained in the bills pertaining to the telephone exchange service or telephone toll service received by a customer of a carrier . . ..X0ÍX0Í+#X\  P}G;P# I. A. 1. a.(1)(a) i) a)#Xj\  P}G;XP#` hp x (##X\  P}G;P# Í47 U.S.C.  222(f)(1) (emphasis added).+ MCI concludes that section 222(f)(1)(A) does not cover casual traffic, but section 222(f)(1)(B) does.X0ÍX0Í#X\  P}G;P# I. A. 1. a.(1)(a) i) a)#Xj\  P}G;XP#` hp x (##X\  P}G;P# ÍMCI Petition at 4849. MCI further argues that under the usual meaning of the term "subscribed service," casual traffic such as its 1800COLLECT service calls would not be included because they are carried outside any subscribed service relationship.X0ÍX0Í#X\  P}G;P# I. A. 1. a.(1)(a) i) a)#Xj\  P}G;XP#` hp x (##X\  P}G;P# ÍMCI Petition at 48. MCI asserts that a comparison of section 222(f)(1)(A) with section 222(f)(1)(B) "may shed some light on this question" as it more broadly defines CPNI as information contained in telephone bills.X0ÍX0Í#X\  P}G;P# I. A. 1. a.(1)(a) i) a)#Xj\  P}G;XP#` hp x (##X\  P}G;P# ÍMCI Petition at 4849. We conclude that MCI's reading of section 222(f)(1) is reasonable and clarify that casual traffic reflected in a customer's telephone bill is CPNI under 222(f)(1)(B), but is not "subscribed" service in 222(f)(1)(A). F.CPNI "Laundering" MCI requests clarification that "the status of information as CPNI or carrier proprietary information [under section 222] is not lost or altered if [a] carrier discloses or transmits such information to an affiliated or unaffiliated entity, whether or not that entity transfers such information to other parties or back to the original carrier."X0ÍX0Í7#X\  P}G;P# I. A. 1. a.(1)(a) i) a)#Xj\  P}G;XP#` hp x (##X\  P}G;P# ÍMCI Petition at 53. See also TRA Comments at 8.7 MCI argues that the original carrier retains all of the obligations imposed by section 222 for such information, no matter where the CPNI or carrier proprietary information ultimately "resides."X0ÍX0Í#X\  P}G;P# I. A. 1. a.(1)(a) i) a)#Xj\  P}G;XP#` hp x (##X\  P}G;P# ÍMCI Petition at 53. As such, MCI concludes that carriers must take steps to safeguard all such information, especially information that is transmitted to third parties in the course of providing service.X0ÍX0Í#X\  P}G;P# I. A. 1. a.(1)(a) i) a)#Xj\  P}G;XP#` hp x (##X\  P}G;P# ÍMCI Petition at 53. MCI also seeks clarification that there is a rebuttable presumption that customerspecific information in a carrier's files was received on a confidential basis or through a service relationship governed by section 222.X0ÍX0Í#X\  P}G;P# I. A. 1. a.(1)(a) i) a)#Xj\  P}G;XP#` hp x (##X\  P}G;P# ÍMCI Petition at 53. MCI argues that the burden should be on the carrier to rebut the presumption through records showing the time and manner of its first receipt of the information.X0ÍX0Í#X\  P}G;P# I. A. 1. a.(1)(a) i) a)#Xj\  P}G;XP#` hp x (##X\  P}G;P# ÍMCI Petition at 54. MCI further asserts that customers should not be permitted to approve the use of CPNI that is also carrier proprietary information because carrier proprietary information is "absolutely protected under section 222(b)."X0ÍX0Í#X\  P}G;P# I. A. 1. a.(1)(a) i) a)#Xj\  P}G;XP#` hp x (##X\  P}G;P# ÍMCI Petition at 54.  We agree that as the stewards of CPNI and carrier proprietary information carriers must take steps to safeguard such information. Moreover, we find that implicit in section 222 is a rebuttable presumption that information that fits the definition of CPNI contained in section 222(f)(1) is in fact CPNI. We decline, however, to speak to MCI's other clarification requests as they regard issues relating to carrier proprietary information in section 222(b) and enforcement mechanisms to ensure carrier compliance with both sections 222(a) and (b). As the Further Notice of Proposed Rulemaking (FNPRM) in this docket seeks comment on those specific issues, we would not want to prejudice resolution of those issues in this order.X0ÍX0Í8#X\  P}G;P# I. A. 1. a.(1)(a) i) a)#Xj\  P}G;XP#` hp x (##X\  P}G;P# ÍCPNI Order, 13 FCC Rcd at 8200202,  203207.8 G.Acts of Agents of Wireless Providers ` ` ` Vanguard argues that sales agents of CMRS providers are not subject to Commission rules, and that CMRS providers should not be held responsible for the use of CPNI independently obtained by agents because it would be difficult or impossible for CMRS providers to enforce these obligations on agents. Vanguard contends that difficulties arise because agents may sell the services of competing providers and their contracts do not expire in the near future.X0ÍX0Í3#X\  P}G;P# I. A. 1. a.(1)(a) i) a)#Xj\  P}G;XP#` hp x (##X\  P}G;P# ÍVanguard Petition at 1819; Vanguard Reply at 67.3 MCI responds that carriers are always responsible for the acts of their agents and, if they share CPNI with agents, must take all steps necessary to ensure that the agent does not misuse CPNI.X0ÍX0Í#X\  P}G;P# I. A. 1. a.(1)(a) i) a)#Xj\  P}G;XP#` hp x (##X\  P}G;P# ÍMCI Comments at 5758. Omnipoint proposes that carriers should not be held responsible for the ultra vires acts of agents and should not be liable for an independent agent's conduct unless the carrier has ratified it.X0ÍX0Í#X\  P}G;P# I. A. 1. a.(1)(a) i) a)#Xj\  P}G;XP#` hp x (##X\  P}G;P# ÍOmnipoint Reply at 9.   We find that telecommunications service providers will be responsible for the actions of their agents to comply with our CPNI rules to the extent that telecommunications service providers share CPNI with their agents. Moreover, telecommunications service providers will be responsible for the actions of agents with respect to the use of CPNI acquired by their agents. It is well established that principals are responsible for the actions of their agents.X0ÍX0Í#X\  P}G;P# I. A. 1. a.(1)(a) i) a)#Xj\  P}G;XP#` hp x (##X\  P}G;P# ÍSee, e.g., United States v. Park, 421 U.S. 658, 670, 95 S. Ct. 1903, 1910 (1975); McAndrew v. Mularchuk, 33 N.J. 172, 189, 162 A. 2d 820, 830 (Sup. Ct. N.J., 1960). In the absence of such a rule, the important consumer protections enacted by Congress in section 222 may be vitiated by the actions of agents. We believe that telecommunications service providers can meet these requirements through the private contract arrangements they have with their agents. Carriers would normally have negotiating leverage to enforce this requirement in the case of agents who serve more than one carrier, since all carriers would be required to enforce the same rules. To the extent that it may be shown that some carriers would not be able to enforce these requirements, the Commission will address the exceptions on a casebycase basis.  H.Information Known to Employees  X` hp x (#%'0*,.8135@8:#& P}7&P#Federal Communications Commission`|(#CFCC 99223 #Xw P}7XP#у yxdddy` hp x (##v6X@}7N@#ѭ#XN\  P}XP#  #Xw P}7XP# fStatement of Commissioner Harold W. FurchtgottRoth#XN\  P}XP# ă & Concurring in Part ă  Re:Telecommunications Carriers' Use of Customer Proprietary Network Information and Other Information; Implementation of the NonAccounting Safeguards Of Section 271 and 272 of the Communications Act of 1934, As Amended. CC Docket Nos. 9645 and 96149. I support today's Order to the extent that it provides the relief requested by the petitioners. I question, however, the approach that the Commission has taken with respect to certain of the forbearance petitions. While I concur in the result reached in today's Order, I would have preferred reaching it through action taken on these petitions. I am troubled that the Commission has decided to provide regulatory relief through reconsideration and then use that proceeding as part of the justification for denying full regulatory forbearance as requested. The Commission has determined that the simplest method of dealing with these petitions is to deny the forbearance relief at issue while at the same time providing relief in a separate proceeding. In particular, I am troubled by the approach that the Commission has taken with respect to carriers' use of customer proprietary network information (CPNI) to market customer premises equipment (CPE) and information services. In this respect, I agree with the wellreasoned statement of my colleague, Commissioner Tristani, to the extent that she believes that the Commission's reading of section 222(c)(1)(B) of the Act is "contrary to the plain language of what the Commission previously found to be a 'clear and ambiguous' provision."X0ÍX0Í,X` hp x (#%'0*,.8135@8:  #X\  P}G;P# I. A. 1. a.(1)(a) i) a)#Xj\  P}G;XP#4 <DL!#X\  P}G;P#4 <DL!Ffootnote tex#Xw P}7XP#Í#Ffootnote tex#ې#X\  P}G;P#Ffootnote tex#Xw P}7XP#Afootnote ref#Xw P}7XP##Afootnote ref##Xw P}7XP# For similar reasons, I do not agree with SBC and GTE that the term necessary to in section 222(c)(1)(B) should not be interpreted restrictively because in other proceedings the Commission has used the term necessary not to mean indispensable but rather used or useful. See GTE Petition at 8; SBC Petition at 7.#Ffootnote tex#ې#X\  P}G;P#Ffootnote tex#Xw P}7XP#I #Xj\  P}G;XP# In todays decision, the majority also relies on what it concludes are customer expectations regarding how services will be provisioned as the touchstone of whether an offering falls within the section 222(c)(1)(B) exception, an approach that I believe cannot be squared with the language of that provision. For example, the majoritys reliance on the lack of record evidence showing that allowing wireline carriers to market CPE to their customers violates customer expectations is misplaced.#Xw P}7XP##Xj\  P}G;XP#X0ÍX0Í+?  #X\  P}G;P# I. A. 1. a.(1)(a) i) a)#Xj\  P}G;XP#4 <DL!#X\  P}G;P#4 <DL!Ffootnote tex#Xw P}7XP#Afootnote ref#Xw P}7XP#ۍ#Afootnote ref##Xw P}7XP# CPNI Recon, __ FCC Rcd at __,  44.#Ffootnote tex#ې#X\  P}G;P#Ffootnote tex#Xw P}7XP#+ Ultimately, regardless of what customers expect, the language of the provision itself governs. Similarly, the principle of customer convenience#Xw P}7XP##Xj\  P}G;XP#X0ÍX0Í3@  #X\  P}G;P# I. A. 1. a.(1)(a) i) a)#Xj\  P}G;XP#4 <DL!#X\  P}G;P#4 <DL!Ffootnote tex#Xw P}7XP#Afootnote ref#Xw P}7XP#ۍ#Afootnote ref##Xw P}7XP# Id. at __,  42.3 cannot be exalted above congressional intent in enacting the provision. Accordingly, unlike the majority, I would decline to grant petitioners requests that, because of the integrated nature of certain information services with telecommunications service, we should distinguish among information services for purposes of section 222(c)(1)(B).#Xw P}7XP##Xj\  P}G;XP#X0ÍX0ÍA  #X\  P}G;P# I. A. 1. a.(1)(a) i) a)4 <DL!Ffootnote tex#Xw P}7XP#Í#Ffootnote tex#ې#X\  P}G;P#Ffootnote tex#Xw P}7XP#Afootnote ref#Xw P}7XP##Afootnote ref##Xw P}7XP# See Bell Atlantic Petition at 79; GTE Petition at 2126; NTCA Petition at 67; SBC Petition at 7; TDS Petition at 6. See also PrimeCo Petition at 67 (asserting that voice mail enables CMRS customers to receive communications when the handset is temporarily out of service); Cable & Wireless Comments at 10 (urging the Commission to allow use of CPNI only when the information service is an integral part of or otherwise related to the underlying telecommunications service).#Ffootnote tex#ې#X\  P}G;P#Ffootnote tex#Xw P}7XP#۬ In my view, none of the parties has presented a statutory basis for treating messaging services differently from other information services under section 222. As I note above, information services may well constitute an important component of the services a telecommunications carrier offers its customers. Nevertheless, these information services are not necessary to, or used in, the provision of the underlying telecommunications service.  X In construing the phrase services necessary to, or used in,#Xw P}7XP##Xj\  P}G;XP#X0ÍX0Í7B  #X\  P}G;P# I. A. 1. a.(1)(a) i) a)#Xj\  P}G;XP#4 <DL!#X\  P}G;P#4 <DL!Ffootnote tex#Xw P}7XP#Afootnote ref#Xw P}7XP#ۍ#Afootnote ref##Xw P}7XP# 47 U.S.C.  222(c)(1)(B).7 the Commission must be guided by the statutes focus on the protection of customer privacy and hence narrowly construe the statute in order to optimize consumer protections. A carrier need only obtain permission to use CPNI in order to market CPE or information services to its customers, a minimal burden when weighed against the purposes of section 222. I believe this approach best effectuates Congresss intent by balancing competitive interests with the consumers interests in privacy and control over CPNI.    #Xw P}7XP#