WPCz 2BET 3|x ) Y-#Xw P7XP#WP MultinationalA Roman (TT)HPLAS4.WRSSx  @,, PX@2@8P@ ZE3|wWP MultinationalA Roman (TT)Clarendon BT (Bold) (TT)[hXP#"5@^S8*88S:888888828888888S8Sb.xJxJxJxJxJooJfJfJfJfJ8.8.8.8.xSxSxSxSxSxSxSxSxSxSxJxSxSxSxSxR]SxJxJ.xof8xEf.SSSxxxxxxSSxxSSxSo8xx8Sof8JoxAJAJ]x]x]ffx.Sfo@.SASSooffAS.8]fx]xxxxxxxxxxxxxxxoxoxoxxxxxxooxxfSfxfSxfxJSJSJJJJfxfx.SES8xxxNS.f.SS..S.J8fSxxfA.8x.fJxJxSgSoJSJooJ]?t]S[[Ssee*x@A.wR..n[Cfx@xWlRx[][ceIfIs`Wx[rriwgeSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS8*88S:888888828888888S8Sb.xJxJxJxJxJooJfJfJfJfJ8.8.8.8.xSxSxSxSxSxSxSxSxSxSxJxSxSxSxSxR]SxJxJSxJoJoJoJoJxgfJfJfJfJxSxSxSxSxSxSSSxS8.8.8.8.s]A.xSf.f@f.f?f.xSxSxSxSxSxSxo8o8o8]A]A]A]Af@f.f.xSxSxSxSxSxSxxSfJfJfJxSxSf.xSo8]xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx8xxx8xxx8xxx8xxxxxxxxxxxxxxfi]f]oJiAlJ{SxJ8.uJo]]{JoSxJxf`SfSSiJxJofx]fffxi{8SxxxfJffff88SSSSx{SSSxxxf8`SJ8HP LaserJet 4/4MtScript_230_1HPLAS4.WRSSc P7,, PP2 @H v p? "5@^dC2CCdECCCCCCCRight Par 6Right Par 67` hp x (#X` hp x (#X` hp x (#` hp x (#Right Par 7Right Par 78` hp x (#X` hp x (#0X` hp x (#0` hp x (#Right Par 8Right Par 89` hp x (#X` hp x (#X` hp x (#` hp x (#Document 1Document 1:` hp x (#X` hp x (#X` hp x (#` hp x (#2E;$@<$B=lE>lETechnical 5Technical 5;` hp x (#X` hp x (# X` hp x (#` hp x (#Technical 6Technical 6<` hp x (#X` hp x (# X` hp x (#` hp x (#Technical 2Technical 2= Technical 3Technical 3> 2M?$)F@lMHA$HB$JTechnical 4Technical 4?` hp x (#X` hp x (# X` hp x (#` hp x (#Technical 1Technical 1@ Technical 7Technical 7A` hp x (#X` hp x (# X` hp x (#` hp x (#Technical 8Technical 8B` hp x (#X` hp x (# X` hp x (#` hp x (#2UC3MDQOEoQFStoc 1toc 1C` hp x (#(#`(#`` hp x (#toc 2toc 2D` hp x (#` (#`` (#`` hp x (#toc 3toc 3E` hp x (#` (#` (#` hp x (#toc 4toc 4F` hp x (# (# (#` hp x (#2\GUHWIvZJZtoc 5toc 5G` hp x (#h(#h(#` hp x (#toc 6toc 6H` hp x (#(# (# ` hp x (#toc 7toc 7I toc 8toc 8J` hp x (#(# (# ` hp x (#2WeK\L^MaN9ctoc 9toc 9K` hp x (#(#`(#`` hp x (#index 1index 1L` hp x (#` (#` (#` hp x (#index 2index 2M` hp x (#` (#`` (#`` hp x (#toa headingtoa headingN` hp x (#(#(#` hp x (#2 iOvePleQkfRhcaptioncaptionO _Equation Caption_Equation CaptionP footerfooterQ` hp x (# (#  (# ` hp x (#heading 3heading 3RNP2lS;iTkUkVYlpara numnumbered indented paragraphsS' Y- 1.(i) 1) 1.#Xw P7[hXP# 1. 1.ҲHeadingChapter HeadingTJ d  ) I. ׃  Right ParRight-Aligned Paragraph NumbersU>a݅@  I.   X(# SubheadingSubheadingV0\ E A.  2oW^!mXdmYmZnFOOTNOTEFootnote - AppearanceWPHIGHLIGHT 1Italics and BoldldeddX+. DRAFT ONHeader A Text = DRAFT and DateY X =8` (#FDRAFTă r  ` (#=D3 1, 43 12pt (Z)(PC-8))T2Dă  ӟDRAFT OFFTurn Draft Style offZ@@    2s[Xo\1p]1Kq^1|rHEADERHeader A - Appearance[LETTER LANDLetter Landscape - 11 x 8.5\ 3'3'Standard'3'3StandardLetter Portrait - 8.5 x 11 ;   LEGAL LANDLegal Landscape - 14 x 8.5]f 3'3'Standard'A'AStandardZ K e6VE L"nu;   LETTER PORTLetter Portrait - 8.5 x 11^L 3'3'Standard3'3'StandardZ K e6VE L"nU9   2cv_1s`nua~ubduLEGAL PORTLegal Portrait - 8.5 x 14_ 3'3'StandardA'A'StandardLetter Portrait - 8.5 x 119   TITLETitle of a Document`K\ * ăBLOCK QUOTESmall, single-spaced, indentedaN X HIGHLIGHT 2Large and Bold LargebB*d. 2{cjvdveEyf-czHIGHLIGHT 3Large, Italicized and Underscoredc V -qLETTERHEADLetterhead - date/marginsdu H XX  3'3'LetterheadZ K e VE L"n3'3'LetterheadZ K e VE L"nE9    * 3'3'LetterheadZ K e VE L"n3' II"n"Tv3'StandarddZ K e VE L"nU9 Ѓ   INVOICE FEETFee Amount for Math Invoicee ,, $0$0  MEMORANDUMMemo Page FormatfD.   ! M E M O R A N D U M ă r  y<N dddy   2+g8{h8|i2~jXINVOICE EXPSEExpense Subtotals for Math Invoiceg:A ,p, $0$00INVOICE TOTTotals Invoice for Math Macrohz 4p, $0$00INVOICE HEADRHeading Portion of Math Invoicei+C`*   4X 99L$0 **(  ӧ XX NORMALReturn to Normal Typestylej2Ɂk[]l[m[n[nSMALLSmall TypestylekFINEFine TypestylelLARGELarge TypestylemEXTRA LARGEExtra Large Typestylen2o[pVqXكrX1VERY LARGEVery Large TypestyleoENVELOPEStandard Business Envelope with Headerp+w ,,EnvelopeZ K e VE L"n,,EnvelopeLarge, Italicized and Under;    ,, 88+  `   MACNormalq,.1rdf2Fst[uvlڊStyle 14Swiss 8 Pt Without Marginss$$D Co> PfQ  )a [ PfQO Style 12Dutch Italics 11.5t$$F )^ `> XifQ  )a [ PfQO Style 11Initial Codes for Advanced IIuJ )a [ PfQK  dddn  #  [ X` hp x (#%'b, oT9 ! )^ `> XifQ ` Advanced Legal WordPerfect II Learning Guide   x )^ `> XifQ Advanced Legal WordPerfect II Learning Guide   j-n )^ `> XifQ    Copyright  Portola Systems, Inc. 1987, 1988`6 >Page  jBX )^ `> XifQ    Page ` Copyright  Portola Systems, Inc. 1987, 1988 Style 3oDutch Roman 11.5 with Margins/Tabsv )a [ PfQO  ddn  # c0*b, oT9 !2wxxy|zStyle 4 PSwiss 8 Point with MarginswDq Co> PfQ  dddd  #  Style 1.5Dutch Roman 11.5 Fontx4h )a [ PfQO  dddn Style 2Dutch Italic 11.5y$ )^ `> XifQ Style 5Dutch Bold 18 Pointz$RH$L T~> pfQ_  )a [ PfQO 2<{|}.~5Style 7Swiss 11.5{$$V )ao> PfQ ]  )a [ PfQO Style 6Dutch Roman 14 Point|$$N w [ PfQ   )a [ PfQO Style 10oInitial Codes for Advanced} U )a [ PfQK  dddn  ##  [[ b, oT9 !b, oT9 !n )^ `> XifQ ` Advanced Legal WordPerfect Learning Guide   f )^ `> XifQ Advanced Legal WordPerfect Learning Guide   Q" )^ `> XifQ    Copyright  Portola Systems, Inc. 1987, 1988`6 >Page  QN~ )^ `> XifQ    Page ` Copyright  Portola Systems, Inc. 1987, 1988 Style 8PfInitial Codes for Beginningg~i )a [ PfQK  dddn  # X` hp x (#%'b, oT9  [ &e )^ `> XifQ ` Beginning Legal WordPerfect Learning Guide   d )^ `> XifQ Beginning Legal WordPerfect Learning Guide   jH )^ `> XifQ    Copyright  Portola Systems, Inc. 1987, 1988`6 >Page  j )^ `> XifQ    Page ` Copyright  Portola Systems, Inc. 1987, 1988 2ns}Style 9Initial Codes for Intermediate )a [ PfQK  dddn  # X` hp x (#%'b, oT9 Њ [ e )^ `> XifQ ` Intermediate Legal WordPerfect Learning Guide   3 )^ `> XifQ Intermediate Legal WordPerfect Learning Guide   jf )^ `> XifQ    Copyright  Portola Systems, Inc.`+ >Page  jX )^ `> XifQ    Page ` Copyright  Portola Systems, Inc. 1987, 1988 UpdateInitial Codes for Update Module )a [ PfQK  dddn  #  [ X` hp x (#%'b, oT9 !n )^ `> XifQ ` Legal WordPerfect 5.0 Update Class Learning Guide   f )^ `> XifQ Legal WordPerfect 5.0 Update Class Learning Guide   Q" )^ `> XifQ    Copyright  Portola Systems, Inc. 1987, 1988`7 CPage  jN~ )^ `> XifQ    Page ` Copyright  Portola Systems, Inc. 1987, 1988 head1 #'d#2p}wC@ #a1Paragraph R!1. a. i. (1) (a) (i) 1) a)D )DDDFrf$ 2?Ҧpa2Paragraph R!1. a. i. (1) (a) (i) 1) a)D )DDDFrf/` ` ` a3Paragraph R!1. a. i. (1) (a) (i) 1) a)D )DDDFrf:` ` `  a4Paragraph R!1. a. i. (1) (a) (i) 1) a)D )DDDFrfE` ` `  a5Paragraph R!1. a. i. (1) (a) (i) 1) a)D )DDDFrfP  ` ` ` hhh 2Kpa6Paragraph R!1. a. i. (1) (a) (i) 1) a)D )DDDFrf[   a7Paragraph R!1. a. i. (1) (a) (i) 1) a)D )DDDFrff  a8Paragraph R!1. a. i. (1) (a) (i) 1) a)D )DDDFrfq Document[8]C^iDocument StyleNeF2CC -2( -Ct )B` ` ` 2q*eeeDocument[4]C^iDocument StyleNeF2CCW -2( -Ct )B  . Document[6]C^iDocument StyleNeF2CCe -2( -Ct )B  Document[5]C^iDocument StyleNeF2CCs -2( -Ct )B  Document[2]C^iDocument StyleNeF2CC -2( -Ct )B*    2\p*,ǮDocument[7]C^iDocument StyleNeF2CC -2( -Ct )B  ` ` ` Right Par[1]C^iRight-Aligned Paragraph Numbers -2( -Ct )B8@  Right Par[2]C^iRight-Aligned Paragraph Numbers -2( -Ct )BA@` ` `  ` ` ` Document[3]C^iDocument StyleNeF2CC -2( -Ct )B0     2T2߰Right Par[3]C^iRight-Aligned Paragraph Numbers -2( -Ct )BJ` ` ` @  ` ` ` Right Par[4]C^iRight-Aligned Paragraph Numbers -2( -Ct )BS` ` `  @  Right Par[5]C^iRight-Aligned Paragraph Numbers -2( -Ct )B\` ` `  @hhh hhh Right Par[6]C^iRight-Aligned Paragraph Numbers -2( -Ct )Be` ` `  hhh@ hhh 2^NٴRight Par[7]C^iRight-Aligned Paragraph Numbers  -2( -Ct )Bn` ` `  hhh@  Right Par[8]C^iRight-Aligned Paragraph Numbers -2( -Ct )Bw ` ` `  hhh@ppp ppp Document[1]C^iDocument StyleNeF2CCE -2( -Ct )BF34   ׃  Technical[5]C^iTechnical Document StyleCCS -2( -Ct )B&56  . 2ڷFTechnical[6]C^iTechnical Document StyleCCa -2( -Ct )B&78  . Technical[2]C^iTechnical Document StyleCCo -2( -Ct )B*9:    Technical[3]C^iTechnical Document StyleCC} -2( -Ct )B';<   Technical[4]C^iTechnical Document StyleCC -2( -Ct )B&=>   2C A}ƹTechnical[1]C^iTechnical Document StyleCC -2( -Ct )B4?$@     Technical[7]C^iTechnical Document StyleCC -2( -Ct )B&AB  . Technical[8]C^iTechnical Document StyleCC -2( -Ct )B&CD  . Paragraph[1]C^i1. a. i. (1) (a) (i) 1) a)C -2( -Ct )B$ab 2׼u.Paragraph[2]C^i1. a. i. (1) (a) (i) 1) a)C -2( -Ct )B/cd` ` ` Paragraph[3]C^i1. a. i. (1) (a) (i) 1) a)C -2( -Ct )B:ef` ` `  Paragraph[4]C^i1. a. i. (1) (a) (i) 1) a)C -2( -Ct )BEgh` ` `  Paragraph[5]C^i1. a. i. (1) (a) (i) 1) a)C -2( -Ct )BPij` ` ` hhh 2d |FParagraph[6]C^i1. a. i. (1) (a) (i) 1) a)C -2( -Ct )B[kl Paragraph[7]C^i1. a. i. (1) (a) (i) 1) a)C -2( -Ct )Bfmn Paragraph[8]C^i1. a. i. (1) (a) (i) 1) a)C -2( -Ct )Bqop toatoa` hp x (#` hp x (#2dqeel2S&C6C^fDocument StyleNF2CC -2( -Ct )s t . 3S&C7C^fDocument StyleNF2CC -2( -Ct ) uv 4S&C8C^fDocument StyleNF2CC! -2( -Ct ) wx 5S&C9C^fDocument StyleNF2CC/ -2( -Ct )*yz   2p36S&C:C^fDocument StyleNF2CC= -2( -Ct ){|` ` ` 7S&C;C^fRight-Aligned Paragraph NumbersK -2( -Ct )8}~@  8S&C<C^fRight-Aligned Paragraph NumbersY -2( -Ct )A@` ` `  ` ` ` 9S&C=C^fDocument StyleNF2CCg -2( -Ct )0    2K10S&C>C^fRight-Aligned Paragraph Numbersu -2( -Ct )J` ` ` @  ` ` ` 11S&C?C^fRight-Aligned Paragraph Numbers -2( -Ct )S` ` `  @  12S&C@C^fRight-Aligned Paragraph Numbers -2( -Ct )\` ` `  @hhh hhh 13S&CAC^fRight-Aligned Paragraph Numbers -2( -Ct )e` ` `  hhh@ hhh 2E14S&CBC^fRight-Aligned Paragraph Numbers -2( -Ct )n` ` `  hhh@  15S&CCC^fRight-Aligned Paragraph Numbers -2( -Ct )w` ` `  hhh@ppp ppp 16S&CDC^fDocument StyleNF2CC -2( -Ct )F   ׃  17S&CEC^fTechnical Document StyleCC -2( -Ct )&  . 2F18S&CFC^fTechnical Document StyleCC -2( -Ct )&  . 19S&CGC^fTechnical Document StyleCC -2( -Ct )*    20S&CHC^fTechnical Document StyleCC -2( -Ct )'   21S&CIC^fTechnical Document StyleCC -2( -Ct )&   2x(}222S&CJC^fTechnical Document StyleCC -2( -Ct )4$     23S&CKC^fTechnical Document StyleCC+ -2( -Ct )&  . 24S&CLC^fTechnical Document StyleCC9 -2( -Ct )&  . 25S&CMC^f1. a. i. (1) (a) (i) 1) a)CG -2( -Ct )$ 2Ci26S&CNC^f1. a. i. (1) (a) (i) 1) a)CU -2( -Ct )/` ` ` 27S&COC^f1. a. i. (1) (a) (i) 1) a)Cc -2( -Ct ):` ` `  28S&CPC^f1. a. i. (1) (a) (i) 1) a)Cq -2( -Ct )E` ` `  29S&CQC^f1. a. i. (1) (a) (i) 1) a)C -2( -Ct )P` ` ` hhh 2u)30S&CRC^f1. a. i. (1) (a) (i) 1) a)C -2( -Ct )[ 31S&CSC^f1. a. i. (1) (a) (i) 1) a)C -2( -Ct )f 32S&CTC^f1. a. i. (1) (a) (i) 1) a)C -2( -Ct )q Default ParaC^fDefault Paragraph Font2CC -2( -Ct );;#PP##PP#2DTZ_Equation CaC^f_Equation CaptionF2CC -2( -Ct );;#PP##PP#endnote refeC^fendnote referenceF2CC -2( -Ct )>>#PP##PP#footnote refC^ffootnote referenceF2CC -2( -Ct )>#PP#1, 2, 3,?@65NumbersO@/"=(1*1÷$t ?.E1.2 dvpqJeA, B,t ?@65Uppercase Letters1 ?*1÷$t ?.E .33`O5hT(G2PDocument Style&^aO5h.K+&,$@`O5Bȗ+&>` ` ` 34`O5iT(G2PDocument Style&^aO5i.K+&,$@`O5Bȗ+&>  . 35`O5jT(G2PDocument Style&^aO5j.K+&,$@`O5Bȗ+&>  2LeRpJ36`O5kT(G2PDocument Style&^aO5k.K+&,$@`O5Bȗ+&>  37`O5lT(G2PDocument Style&^aO5l.K+&,$@`O5Bȗ+&>*   38`O5mT(G2PDocument Style&^aO5m.K+&,$@`O5Bȗ+&>` ` ` 39`O5nT(G2PRight-Aligned Paragraph NumbersK+&,$@`O5Bȗ+&>8@   2~R40`O5oT(G2PRight-Aligned Paragraph NumbersK+&,$@`O5Bȗ+&>A@` `  ` ` ` 41`O5pT(G2PDocument Style&^aO5p.K+&,$@`O5Bȗ+&>0    42`O5qT(G2PRight-Aligned Paragraph NumbersK+&,$@`O5Bȗ+&>J` ` @  ` `  43`O5rT(G2PRight-Aligned Paragraph NumbersK+&,$@`O5Bȗ+&>S` `  @  2?1n44`O5sT(G2PRight-Aligned Paragraph NumbersK+&,$@`O5Bȗ+&>\` `  @hh# hhh 45`O5tT(G2PRight-Aligned Paragraph NumbersK+&,$@`O5Bȗ+&>e` `  hh#@( hh# 46`O5uT(G2PRight-Aligned Paragraph NumbersK+&,$@`O5Bȗ+&>n` `  hh#(@- ( 47`O5vT(G2PRight-Aligned Paragraph NumbersK+&,$@`O5Bȗ+&>w` `  hh#(-@pp2 -ppp 2q+548`O5wT(G2PDocument Style&^aO5w.K+&,$@`O5Bȗ+&>F *  ׃  49`O5xT(G2PTechnical Document Stylex.K+&,$@`O5Bȗ+&>&  . 50`O5yT(G2PTechnical Document Styley.K+&,$@`O5Bȗ+&>&  . 51`O5zT(G2PTechnical Document Stylez.K+&,$@`O5Bȗ+&>*    2a,52`O5{T(G2PTechnical Document Style{.K+&,$@`O5Bȗ+&>'   53`O5|T(G2PTechnical Document Style|.K+&,$@`O5Bȗ+&>&   54`O5}T(G2PTechnical Document Style}.K+&,$@`O5Bȗ+&>4$     55`O5~T(G2PTechnical Document Style~.K+&,$@`O5Bȗ+&>&  . 2}56`O5T(G2PTechnical Document Style.K+&,$@`O5Bȗ+&>&  . 57`O5T(G2P1. a. i. (1) (a) (i) 1) a).K+&,$@`O5Bȗ+&>$ 58`O5T(G2P1. a. i. (1) (a) (i) 1) a).K+&,$@`O5Bȗ+&>/` ` ` 59`O5T(G2P1. a. i. (1) (a) (i) 1) a).K+&,$@`O5Bȗ+&>:` ` `  2)60`O5T(G2P1. a. i. (1) (a) (i) 1) a).K+&,$@`O5Bȗ+&>E` ` `  61`O5T(G2P1. a. i. (1) (a) (i) 1) a).K+&,$@`O5Bȗ+&>P` ` ` hhh 62`O5T(G2P1. a. i. (1) (a) (i) 1) a).K+&,$@`O5Bȗ+&>[ 63`O5T(G2P1. a. i. (1) (a) (i) 1) a).K+&,$@`O5Bȗ+&>f 264`O5T(G2P1. a. i. (1) (a) (i) 1) a).K+&,$@`O5Bȗ+&>q 65`O5T(G2PDefault Paragraph Font5.K+&,$@`O5Bȗ+&>OO#P P##P P#66`O5T(G2P_Equation Caption^aO5.K+&,$@`O5Bȗ+&>OO#PP##PP#67`O5T(G2Pendnote reference^aO5.K+&,$@`O5Bȗ+&>RR#PP##PP#2?\p^q68`O5T(G2Pfootnote reference^aO5.K+&,$@`O5Bȗ+&>R#PP#69 _5(_>7footnote text _5dK+b70t _5xŗ+tZP70 _5(_>7Document Style _5dK+b70t _5xŗ+t` ` ` 71 _5(_>7Document Style _5dK+b70t _5xŗ+t  . 2>eqe;p72 _5(_>7Document Style _5dK+b70t _5xŗ+t  73 _5(_>7Document Style _5dK+b70t _5xŗ+t  74 _5(_>7Document Style _5dK+b70t _5xŗ+t*   75 _5(_>7Document Style _5dK+b70t _5xŗ+t` ` ` 2p276 _5(_>7Right-Aligned Paragraph NumbersK+b70t _5xŗ+t8@   77 _5(_>7Right-Aligned Paragraph NumbersK+b70t _5xŗ+tA@` `  ` ` ` 78 _5(_>7Document Style _5dK+b70t _5xŗ+t0     79 _5(_>7Right-Aligned Paragraph NumbersK+b70t _5xŗ+tJ` ` @  ` `  2t J@@hZWP MultinationalA Roman (TT)Clarendon BT (Bold) (TT)Courier New (TT)+8xCdXXx{2 PQXP ,9iC@XXi% p"QXV"H(<XhH{2 PQhPddCCCWxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxNdddCdUUddddddFddddFCCssd44ddzzddd~ooCsdF"Ȑdsd岲dCCȐzȲxCddodȐȅdCdYdsȐ`ȐȐȮzȐUvŐdȐddCCCCŐzozoYNYYYN8YooYdYzzdzddYYzozzzNdzYzzzzCCdddddddzCzdYC"5@^<(((<)((((((($(((((((<(2C,2,CC,8&t82772Ec<<22222222222222222222222222222222!!!2#!!!!!!!!!!!!!!2!2;H,H,H,H,H,YCC,=,=,=,=,!!!!H2H2H2H2H2H2H2H2H2H2H,H2H2H2H2H182H,H,2H,C,C,C,C,H>=,=,=,=,H2H2H2H2H2H222H2!!!!E8'H2==&==&=H2H2H2H2H2H2YHC!C!C!8'8'8'8'=&==H2H2H2H2H2H2^HH2=,=,=,H2H2=H2C!8HHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHH!HHH!HHH!HHH!HHHHHHHHHHHHHH=?8=8C,?'A,J2H,!F,C8[8J,C2H,H=92=22?,H,C=H8N===H?J!2HHH=,====!!2222HJ222HHH=!92,!d*x/d8SXXd{2 PQP+8xCdXXx{2 PQXP ,9iC@XXi% p"QX-V"H(<XhH{2 PQhP.H<!2Xb,<{2 PQ,P?xxxX8/Xx6X@DQX@6?xxxXJXx `NQX&6uC;,-/3Xu&_ x$&7XXȈ4dFAȈ"0Ӈ0Ї0ч 0҇\t&Abt?A t t@AȈ0  /@SSM2c \V<WP MultinationalA Roman (TT)Clarendon BT (Bold) (TT)Courier New (TT)Courier New (Bold) (TT)8S]J]J;S].8].]S]]JA8]SxSSJSSSSSSSSS8SSSSSSSS].xSxSxSxSxSxxJoJoJoJoJA.A.A.A.x]SSSSx]x]x]x]xSxSx]SSxSxSd]xSxSxSxSxSxSx]oSoSoSoSSSSSS]]S.S]SS_SS]oSoSoAo.x]x]SS{xSxS]A]S]SoSoSoSx]x]x]x]xxSoJ8SS888WxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxNxxxSSS8SGGSSSSSS;SSSS;88``S++SSffSSxSi]]8`S;"xxSx`xxS唔S88xfxxxxxxxxxxx8SxS]SxoS8SxJS`xrxxxxxxxxxxPxxxxxxofxGcxxxxxxxSxxxxxxxSxxxxSxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx8xxx8xxx8xxx8xxxxxxxxxxxxxxfo]f]oJoAoJJxJA.Jo]]xJoSJxffSfSSoJxJofx]fffxoASxxfJffff88SSSSxSSSxxxf8fSJ8*x/d8SXXd{2 PQP+8xCdXXx{2 PQXP ,9iC@XXi% p"QX-V"H(<XhH{2 PQhP.H<!2Xb,<{2 PQ,P?xxxX8/Xx6X@DQX@6?xxxXJXx `NQXR&HHHX8,hH6X@DQh@1H WP MultinationalA Roman          xxxxxxxxxxxxxxxxxxxxxxxxxx8xxx8xxx8xxx8xxxxxxxxxxxxxfff]f]oJfA]JxSxJ8.oJo]]oJoSxJxffSfSS]J]Joff]fffffx8Sx]]fJffff88SSSSfxSSS]]]f8`SJ8"Sh5^;C`ddCCCdCCCCddddddddddCCȰdxxxsCYoxxdoxxooCCCddCddYdY8dd88Y8ddddLL8dYYYLYdYddddddCddddddddd8xdxdxdxdxdYxYxYxYxYC8C8C8C8dddddddddoYxddddoYdxdxdxdxdddddxdxdxdxddddddddd8ddddddddododp8p8xddddxdxddLddddodododddddodpLCddCCCWxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxNdddCd]]ddddddFddddFCCddd88ddzzdddkddCddF"Ȑddd尰dCCȐzȰxCdzdodȐȅdCdYdsȐ]ȐȐȧzȐUvŐdȐYYCCCCzzzozoYzNoYdYC8YooYdYzzdzddoYoYzzozzzzzCdoozYzzzzCCddddzdddooozCsdYC2F^ppr "H^^@?F$QQd@G@8@@qXzQ8Qdd{{d|oLHFFw||eo^uwcddd@dd!ddBRdd}{{{{{dooooXHXHXHXHwwwww{|wwww|{{{dddoooX}d}ddX}zFRweeooNv@d}?qbb\ZTyT44ccd::{{4cGTtGnnyy2Bx7cbbnCzxhcnonvyXzXshn~|yxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx@?F$QQd@G@8@@qXzQ8Qdd{{d|oLHFFw||eo^uwcdddxxx4c{{d:xxxx44ccvddo:xx@?yd}d\bGdBTTdxd@dTZbqXXXX}{{{{{{dooooHHHHwwwwwwww|2x ?4  ЊjNORMAL yO #Xx6X@DQ/X@# yO ` `  ,hh]pp&  X ` `  ,hh]pp&  XxxFCC 96221  ?XA` `  ,hh] Before the ` `  ,Federal Communications Commission ` `  ,hh]Washington, DC 20554  ?4  ?@4In the Matter of,hh]pp)  ?4` ` ,hh]) pp  ?4Implementation of the hh]pp)&  XCC Docket No. 96115  ?` 4Telecommunications Act of 1996:pp&) ` `  ,hh])  ? 4Telecommunications Carriers' Usepp&)  ? 4of Customer Proprietary Networkpp&)  ? 4Information and Otherhh]pp)  ?H 4Customer Informationhh]pp)  ?A NOTICE OF PROPOSED RULEMAKING ă  ?h4  ?04Adopted: May 16, 1996hh]ppReleased: May 17, 1996  ?4Comment Date: June 11, 1996  ?4Reply Comment Date: June 26, 1996 By the Commission:  ?AX, I. INTRODUCTION  ?p4   ?4c1.` ` On February 14, 1996, several local exchange carrier associations (the Associations) informed the Common Carrier Bureau (Bureau) that their members were uncertain about their  ?X4responsibilities under the Telecommunications Act of 1996X xP'ԍPub. L. No. 104104, 110 Stat. 56 (1996), codified at 47 U.S.C.  151 et seq. (the 1996 Act). regarding use and protection of customer proprietary network  ?4information (CPNI),fX xP 'ԍSee infra  8 for definition of CPNI. f and requested that the Commission conduct a  ?4rulemaking to implement the provisions of the 1996 Act. xP(#'ԍLetter from Mary McDermott, United States Telephone Association (USTA) to Regina Keeney, Chief of the Common Carrier Bureau, FCC, on behalf of USTA, the National Rural Telephone Association (NRTA), the National Telephone Cooperative Association (NTCA), and the Organization for the Promotion & Advancement of Small Telecommunications Companies (OPASTCO), dated February 14, 1996 (Association Letter).  On March 5, 1996, the NYNEX Telephone Companies (NYNEX) filed a petition for declaratory ruling regarding the proper"@` 0*0*0*""  ?4interpretation of one aspect of Section 222.@ xPX'ԍPetition of the NYNEX Telephone Companies for a Declaratory Ruling as to the Interpretation of Section 222 of the Communications Act (filed Mar. 5, 1996) (NYNEX Petition). NYNEX's petition raises issues with respect to the meaning of the term "telecommunications service" as used in Section 222(c)(1). In particular, NYNEX argues that intraLATA service should be distinguished from interLATA service for the purposes of Section 222 CPNI requirements. For a discussion of these issues,  xP'see infra at Section III.B.i. Any pleadings filed in response to the NYNEX petition are hereby included in the record in this proceeding. On March 27, 1996, U S West, Inc. (U S West) responded to the NYNEX Petition by  ?4letter to the Bureau Chief. xP 'ԍLetter from Lawrence E. Sarjeant, Vice President Federal Regulatory, U S West, to Regina M. Keeney, Chief, Common Carrier Bureau, FCC, filed March 27, 1996 (U S West Letter). In the letter, U S West expressed disagreement with NYNEX's interpretation of the CPNI provisions of the statute and stated that the statute supported "the broad use of CPNI with a carrier's provision of telecommunications services." In response to these and other informal requests for guidance from the telecommunications industry, we initiate this proceeding to seek comment on proposed regulations to specify in more detail and clarify the obligations of telecommunications carriers with respect to the use and protection of CPNI and other customer information. We invite parties who wish to respond to any of the abovereferenced industry filings to do so by submitting comments in this proceeding.  Y1-x2.` ` Section 702 of the 1996 Act added a new Section 222 to the Communications  Y -Act of 1934, as amended,[ (  xP-ԍx47 U.S.C.  151 et seq.[ which sets forth, among other things, restrictions on the use of CPNI obtained by telecommunications carriers in providing telecommunications service to customers as well as certain requirements related to the availability of subscriber list  Y -information.   xP>-ԍxSee 47 U.S.C.  222(c)(f). This NPRM focuses on these provisions of Section 222. The 1996 Act's  xP-definition of CPNI is discussed infra at  8. The definition of "subscriber list information" is discussed infra at  xP- 12. The definitions of "telecommunications," "telecommunications service," and "telecommunications carrier"  xP-are discussed infra at n.29. In addition, the 1996 Act establishes a new Section 275(d) that prohibits local exchange carriers (LECs) from using information obtained from calls made to alarm monitoring service providers to market their own alarm monitoring services, or those provided by any other entity, and requires the Commission to adopt implementing regulations within six months. Although the requirements of Section 222 were immediately effective, we tentatively conclude that regulations that interpret and specify in more detail a telecommunications carrier's obligations under subsections 222(c)(f) of the 1996 Act would be in the public interest. In this Notice of Proposed Rulemaking (NPRM), we propose a regulatory regime that balances consumer privacy and competitive considerations to ensure that telecommunications carriers comply with their new statutory obligations to maintain the privacy of CPNI and other customer information. x"0*(("Ԍ Y-x3.` ` In addition, we clarify that the CPNI requirements the Commission previously  Y-established as nonstructural safeguards in the Computer II   xPb-ԍxAmendment of Section 64.702 of the Commission's Rules and Regulations (Computer II), 77 FCC 2d  xP*-384 (1980) (Final Order), recon., 84 FCC 2d 50 (1980) (Reconsideration Order), further recon., 88 FCC 2d  xP-512 (1981) (Further Reconsideration Order), aff'd sub nom. Computer and Communications Industry Ass'n v.  xP-FCC, 693 F.2d 198 (D.C. Cir. 1982), cert. denied, 461 U.S. 938 (1983).  and Computer III, (  xPJ-ԍxAmendment of Section 64.702 of the Commission's Rules and Regulations (Computer III), CC Docket  xP-No. 85229, Phase I, 104 FCC 2d 958 (1986) (Phase I Order), recon., 2 FCC Rcd 3035 (1987) (Phase I  xP-Reconsideration Order), further recon., 3 FCC Rcd 1135 (1988) (Phase I Further Reconsideration Order),  xP -second further recon., 4 FCC Rcd 5927 (1989) (Phase I Second Further Reconsideration Order); Phase I Order  xPj -and Phase I Reconsideration Order vacated California v. FCC, 905 F.2d 1217 (9th Cir. 1990) (California I);  xP2 -Phase II, 2 FCC Rcd 3072 (1987) (Computer III Phase II Order), recon., 3 FCC Rcd 1150 (1988) (Phase II  xP -Reconsideration Order), further recon., 4 FCC Rcd 5927 (1989) (Phase II Further Reconsideration Order);  xP -Phase II Order vacated, California I, 905 F.2d 1217 (9th Cir. 1990); Computer III Remand Proceeding, 5 FCC  xP -Rcd 7719 (1990) (ONA Remand Order), recon., 7 FCC Rcd 909 (1992), pets. for review denied, California v.  xPR-FCC, 4 F.3d 1505 (9th Cir. 1993) (California II); Computer III Remand Proceedings: Bell Operating Company  xP-Safeguards and Tier 1 Local Exchange Company Safeguards, 6 FCC Rcd 7571 (1991) (BOC Safeguards Order),  xP-BOC Safeguards Order vacated in part and remanded, California v. FCC, 39 F.3d 919 (9th Cir. 1994)  xP-(California III), cert. denied, 115 S. Ct. 1427 (1995). , proceedings  Y-for the provision of enhanced servicesC x xP#-ԍxThe Commission has previously defined the term "enhanced services" as services "offered over common carrier transmission facilities used in interstate communications, which employ computer processing applications that act on the format, content, code, protocol or similar aspects of the subscriber's transmitted information; provide the subscriber additional, different, or restructured information; or involve subscriber  xPC-interaction with stored information." See 47 C.F.R.  64.702(a); see also North American Telecommunications Association Petition for Declaratory Ruling Under Section 64.702 of the Commission's Rules Regarding the  xP-Integration of Centrex, 101 FCC 2d 349 (1985), recon, 3 FCC Rcd 4385 (1988). C and customer premises equipment (CPE) by American Telephone and Telegraph (AT&T), the Bell Operating Companies (BOCs), and GTE Corporation (GTE) remain in effect, pending the outcome of the rulemaking, to the extent that they do not conflict with Section 222, since nothing in the 1996 Act affects these requirements. To the extent that the 1996 Act requires more of a carrier, or imposes greater restrictions on a carrier's use of CPNI, the statute, of course, governs. We seek comment on whether there are statutory, competitive, or privacy reasons that justify the continued application of these preexisting rules (which are discussed in greater detail below) to the BOCs, and GTE. With respect to AT&T, we tentatively conclude that these requirements should be removed in light of our recent decisions classifying AT&T as a nondominant carrier, and the pending AT&T reorganization separating its equipment business from its telecommunications service business. We also seek comment regarding the extent to which these preexisting rules should or must be amended in light of the language or procompetitive, deregulatory goals of the new statute. We tentatively conclude that it is not in the public interest, at this time, to extend all of these preexisting CPNI rules to carriers that are not affiliated with AT&T, the BOCs, or GTE, and seek comment on that conclusion. To the extent that we conclude that we should apply more restrictive CPNI access requirements to certain groups of carriers, such as the BOCs, we seek comment on the specific market"K 0*((" conditions or other circumstances that would warrant removal of those requirements in the future.  Y-x II. BACKGROUND ă  Y`-xA.` ` Commission CPNI Requirements Established Prior to Enactment of the  YI-Telecommunications Act of 1996(#`  Y -x4.` ` Prior to enactment of the 1996 Act, in the context of the Computer IIu   xP -ԍxSee Computer II Final Order, 77 FCC 2d at 481,  249.u and  Y -Computer III proceedings, the Commission established requirements applicable to the use of CPNI for the marketing of enhanced services and CPE by AT&T, the BOCs, and GTE. The Commission determined that such requirements were necessary to protect independent enhanced service providers (ESPs) and CPE suppliers from discrimination by AT&T, the BOCs, and GTE. In the absence of these safeguards, the affected carriers could use CPNI obtained from their provision of regulated services to gain an anticompetitive advantage in the unregulated CPE and enhanced services markets. Further, the Commission found that these CPNI requirements were in the public interest because they were intended to protect legitimate customer expectations of confidentiality regarding individually identifiable  Y5-information.{ 5X xP>-ԍxSee Computer III Phase I Order, 104 FCC 2d at 1089,  260. { The Commission defined CPNI to encompass any information about customers' network services and their use of those services that a telephone company  Y-possessed because it provided those network services.  xP-ԍxSee Filing and Review of Open Network Architecture Plans, 4 FCC Rcd 1, 215 (1988) (BOC ONA  xPh-Order).  Y-x5.` ` Under the Commission's Computer III rules, the BOCs have been required to abide by a request from any customer that its CPNI be withheld from the BOCs' enhanced  Y-services and CPE marketing personnel.@ xP-ԍxSee Computer III Phase II Order, 2 FCC Rcd at 3095,  15455. If, however, the customer has not requested CPNI protection, the CPNI rules vary depending on: (1) whether the information is disclosed to the BOC's CPE or ESP affiliate; (2) the number of lines to which a customer subscribes; and (3) whether the subscriber is a residential or business customer. For example, BOC personnel have been able to use CPNI without prior authorization for marketing CPE to all  Y8-customers.8 xP%-ԍxFurnishing of Customer Premises Equipment by the Bell Operating Companies and the Independent  xP&-Telephone Companies, 2 FCC Rcd 143, 15153,  5570 (1987). With respect to marketing enhanced services, written prior authorization has"8( 0*((L"  Y-been required from customers that subscribe to more than 20 lines.r xPy-ԍxSee BOC Safeguards Order, 6 FCC Rcd at 7609,  84.r BOC personnel could use the CPNI of customers that subscribe to 20 or fewer lines, however, without prior authorization. Unaffiliated ESPs by contrast have been required to obtain prior customer  Y-authorization to obtain access to CPNI maintained by the BOCs.hX xP-ԍxBOC Safeguards Order, 6 FCC Rcd at 7605,  75.h The Commission's rules also imposed on BOCs a notification obligation which required BOCs to provide annual  Y-written notification of CPNI rights to multiline (2 or more lines) business customers./ xP& -ԍxSee Computer III Phase II Order, 2 FCC Rcd at 3096,  164 (stating that the written notification  xP -requirement only applies to multiline business customers, not residential and singleline business customers)./ In previous orders, the Commission has required the BOCs to implement various computerized systems to protect against unauthorized access by their enhanced services and CPE  YH-personnel H@ xP9-ԍxSee generally Filing and Review of Open Network Architecture Plans, 8 FCC Rcd 2606, 261011,   xP-1826 (1993); BOC ONA Order, 4 FCC Rcd at 22224,  426430. The Commission has also previously permitted some BOCs to use a system in which they flag restricted account records and administratively prohibit  xP-personnel involved in CPE marketing from obtaining access to these records. Id. at 222,  426. to restricted CPNI.H(  xP!-ԍxThe term "restricted CPNI" refers to CPNI that the carrier is not authorized to disclose due to lack of customer authorization. In addition, the BOCs have been required to accommodate  Y1-customer requests for partial or temporary restrictions on access to their CPNI.1  xPb-ԍxSee Computer III Phase II Reconsideration Order, 3 FCC Rcd at 116364; BOC ONA Order, at 209,  399. The Commission applied these requirements to GTE in its provision of enhanced services, but not CPE, while declining to apply these requirements to other independent telephone  Y -companies.  xPu-ԍxApplication of Open Network Architecture and Nondiscrimination Safeguards to GTE Corporation, 9 FCC Rcd 4922 (1994).     Y -x6.` ` Although AT&T is subject to CPNI restrictions under Computer III, 0 xP-ԍxFiling and Review of Open Network Architecture Plans, Phase II, 4 FCC Rcd 2449,  4655 (1988). the  Y -AT&T requirements generally are less stringent than those applicable to the BOCs. For example, AT&T is not required to obtain prior authorization from a customer with more than 20 lines before using its CPNI to market enhanced services. Similarly, while the BOCs must notify multiline customers annually of their right to restrict disclosure of CPNI to BOC CPE  YK-affiliates, AT&T must only provide such notification in a onetime billing insert.pK xP%-ԍxComputer III Phase II Order, 2 FCC Rcd at 3096,  163.p AT&T,"KP0*((9" however, must maintain password/ID systems and other mechanisms to restrict unauthorized  Y-access to CPNI. xPb-ԍxFiling and Review of Open Network Architecture Plans, Phase II, 4 FCC Rcd at 245556,  4855.  Y-x7.` ` On March 10, 1994, the Bureau issued a Public Notice inviting comments on these CPNI rules in light of the increasing alliances, acquisitions, and mergers by and  Y-between telephone and nontelephone companies.#XX xP-ԍxPleading Cycle Established for Comments on Rules Governing Telephone Companies' Use of Customer  xP^ -Proprietary Network Information, Public Notice, CC Docket Nos. 90623 and 92256, FCC 94063 (rel. Mar. 10, 1994).# In recognition of these changes, the Bureau sought comment from the public on whether the existing CPNI safeguards would continue in the future to strike the appropriate balance among customers' privacy interests,  YH-competitive equity, and efficiency.@Hx xPq-ԍxId. at 1.@  Y -xB.` ` New Sections 222(c) and (d): CPNI Privacy Provisions of the  Y -x` ` Telecommunications Act of 1996  Y - x8.` ` In new Sections 222(c) and (d), the 1996 Act established requirements for maintaining the confidentiality of CPNI that became effective immediately upon enactment  Y-for all telecommunications carriers.  xPI-ԍxWe note that new Section 651(a)(2) of the 1996 Act states that a common carrier providing transmission of video programming on a common carrier basis is subject to Title II requirements, among other  xP-things. See 47 U.S.C.  571(a)(2). Such carriers thus would be subject to Section 222's CPNI requirements as well.  New Section 222(f)(1) defines CPNI as "information that relates to the quantity, technical configuration, type, destination, and amount of use of a  Yb-telecommunications serviceq@b  xP-ԍx47 U.S.C.  153(43) defines "telecommunications" as "the transmission, between or among points specified by the user of information of the user's choosing without change in the form or content of the information as sent and received." "Telecommunications service" is defined as the offering of telecommunications for a fee directly to the public or to such classes of users as to be effectively available directly to the public regardless of facilities used. 47 U.S.C.  153(46). A "telecommunications carrier" is defined as any provider of telecommunications service, except aggregators as defined by 47 U.S.C. 226. 47 U.S.C. 153(44). A telecommunications carrier shall be treated as a common carrier under the Act only to the  xP{"-extent that it provides telecommunications services. Id.q 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 carrier Y4-customer relationship."4 xP%-ԍx47 U.S.C.  222(f)(1)(A). This is similar to the definition of CPNI that the Commission used in the  xP&-Computer II and Computer III proceedings. The statute explicitly includes within the definition of CPNI"4P0*(( " "information contained in the bills pertaining to telephone exchange service or telephone toll  Y-service received by a customer of a carrier." xPb-ԍx See 47 U.S.C.  222(f)(1)(B). CPNI, however, does not include subscriber list information.  xP*-Subscriber list information is discussed infra at  12.  Y- #Xj P[hXP#  Y-x9.` ` New Section 222(c)(1) provides that: XxX` ` Except as required by law or with the approval of the customer, a telecommunications carrier that receives or obtains [CPNI] by virtue of its provision of a telecommunications service shall only use, disclose, or permit access to individually identifiable [CPNI] in its provision of (A) the telecommunications service from which such information is derived, or (B) services necessary to, or used in, the provision of such telecommunications service, including the publishing of  Y -directories.J  xP-ԍx47 U.S.C.  222(c)(1).Jx` Section 222 further provides that "[a] telecommunications carrier shall disclose [CPNI], upon  Y-affirmative written request by the customer, to any person designated by the customer."Y! xP-ԍx47 U.S.C.  222(c)(2).Y  Yb-x 10.` ` The 1996 Act establishes three exceptions to the general prohibition set forth in Section 222(c)(1). A telecommunications carrier, either directly or indirectly through its agents, may use, disclose, or permit access to individually identifiable CPNI: "(1) to initiate, render, bill, and collect for telecommunications services; (2) to protect the carrier's 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, such services; or (3) to provide any inbound telemarketing, referral, or administrative services to the customer for the duration of the call, if such call was initiated by the customer and the customer approves of  Y-the use of such information to provide such service."M"@ xP-ԍx47 U.S.C.  222(d).M  Y|-x 11.` ` The 1996 Act also establishes separate requirements for the treatment of  Ye-"Aggregate Customer Information.".#Xe xP#-ԍxThe statute defines the term "aggregate customer information" as "collective data that relates to a group or category of services or customers, from which individual customer identities and characteristics have been removed." 47 U.S.C.  222(f)(2). . A telecommunications carrier, other than a LEC, may  YN-use, disclose, or permit access to aggregate customer information for purposes other than"N #0*((k"  Y-those specified by Section222(c)(1).J$ xPy-ԍx47 U.S.C.  222(c)(3).J LECs may use aggregate CPNI for purposes other than those specified by Section222(c)(1) only if, upon reasonable request, they provide such aggregate customer information to other carriers or persons on reasonable and  Y-nondiscriminatory terms and conditions._%X xP-ԍx47 U.S.C.  222(c)(3)._  Yv-xC.` ` New Section 222(e): Availability of Subscriber List Information  YH-x 12.` ` New Section 222(e) states that, notwithstanding Sections 222(b),& H xP -ԍxNew Section 222(b) states that a telecommunications carrier that receives or obtains proprietary information from another carrier for purposes of providing any telecommunications service "shall use such information only for such purpose, and shall not use such information for its own marketing efforts." 47  xP9-U.S.C.  222(b). ē (c),  Y1-and(d), a telecommunications carrier that provides telephone exchange service}'1 xP-ԍ xThe term "telephone exchange service" is defined in 47 U.S.C.  153(47).} must provide "subscriber list information gathered in its capacity as a provider of such service on a timely and unbundled basis, under nondiscriminatory and reasonable rates, terms, and conditions, to any person upon request for the purpose of publishing directories in any  Y -format."(  `  xP-ԍ x47 U.S.C.  222(e). See also Joint Statement of Managers, S. Conf. Rep. No. 104230, 104th Cong., 2d Sess. 203 (1996) (Joint Explanatory Statement) (stating that "[t]he subscriber list information provision guarantees independent publishers access to subscriber rates, terms and conditions from any provider of local telephone service.").  "Subscriber list information" is defined as "any information identifying the listed names of subscribers of a carrier and such subscribers' telephone numbers, addresses, or primary advertising classifications . . . that the carrier or an affiliate has published . . . or  Y-accepted for publication in any directory format."M)H  xP-ԍ x47 U.S.C.  222(f)(3). M As with new Sections 222(c) and (d), new Section 222(e) also became effective immediately upon enactment.  Yb-  Y4-XxD.` ` New Section 275(d): Use of Data Regarding Alarm Monitoring Services(#  Y-x 13.` ` With respect to the provision of alarm monitoring services, the 1996 Act states that a LEC "may not record or use in any fashion the occurrence or contents of calls received by providers of alarm monitoring services for the purposes of marketing such  Y-services on behalf of such [LEC], or any other entity."M* xPJ'-ԍx47 U.S.C.  275(d).M The new statute further requires"h*0*((" the Commission to establish, within six months after the enactment of the 1996 Act, any regulations necessary to enforce the provisions concerning LEC use of alarm monitoring service call information.  Y-  Y- x III. DISCUSSION  Yw-  YI-x 14.` ` As noted above, shortly after passage of the 1996 Act, representatives of several telecommunications carriers and carrier associations contacted the Bureau with questions regarding the scope and substance of their obligations under the Section 222 CPNI provisions that became effective immediately upon enactment. The Bureau also received a  Y -letter, submitted on behalf of associations representing a majority of the LECs, that, inter  Y -alia, asked the Commission to commence a rulemaking to resolve questions concerning the  Y -LECs' responsibilities under the CPNI provisions of the 1996 Act.1+  xP8-ԍxIn their letter, the Associations indicate that previously GTE and the BOCs were the only LECs subject to CPNI obligations. Consequently, the Associations assert that their members have not developed procedures to comply with the new legislative requirements. The Associations further claim that their members face "major organizational challenges and unknown financial impacts in attempting to comply" and that compliance with  xPX-Section 222 may take some time. See Association Letter.1 In addition, NYNEX filed a petition for declaratory ruling seeking confirmation of its interpretation of one aspect  Y-of Section 222 and U S West responded by letter to that petition.N,x xP-ԍxSee supra nn.45.N  Yc-x15.` ` In view of these concerns expressed by the industry, as well as our own analysis of the 1996 Act, we tentatively conclude that regulations that interpret and specify in more detail a telecommunications carrier's obligations under Section 222 would be in the public interest. We seek comments on this tentative conclusion and on the specific requirements we propose to adopt. Based on our reading of the 1996 Act and its legislative history, we believe that Congress sought to address both privacy and competitive concerns by enacting Section 222. In their comments, we ask parties to explain specifically whether their arguments in support of, or in opposition to, the adoption of particular CPNI requirements are based on privacy concerns, competitive concerns, or both. In this proceeding, we seek to establish promptly the regulatory framework for carrier compliance with the CPNI requirements contained in Section 222. We also clarify the applicability of our existing  Yf-Computer III CPNI rules to AT&T, the BOCs, and GTE, and seek comment on whether these preexisting rules should continue to apply. In addition, we seek comment on the carrier requirements in Section 222(e) for making subscriber list information available to others upon request for the purpose of publishing directories. Finally, we seek comment on what procedures LECs should develop to comply with their Section 275(d) obligations.  Y- " ,0*(( "Ԍ Y-xA.` ` Scope of the Commission's Authority  Y-x16.` ` Section 2(b) of the 1934 Act preserves state jurisdiction over "charges, classifications, practices, services, facilities, or regulations for or in connection with  Y-intrastate communications service by wire or radio of any carrier . . .."G- xP-ԍx47 U.S.C.  152(b).G Under Louisiana  Y-PSC,w.X xP-ԍxLouisiana Public Service Commission v. FCC, 476 U.S. 355 (1986).w the Commission has authority to preempt state regulation of intrastate telecommunications services where such state regulation would thwart or impede the Commission's exercise of its lawful authority over interstate telecommunications services because regulation of the interstate aspects cannot be severed from regulation of the intrastate  Y1-aspects./1 xP -ԍxSee Public Service Commission of Maryland v. FCC, 909 F.2d 1510, 1515 (D.C. Cir. 1990), citing  xP-National Ass'n of Regulatory Utility Comm'rs v. FCC, 880 F.2d 422, 42930 (D.C. Cir. 1989). We note that, in connection with the CPNI rules we established prior to the enactment of the 1996 Act, we preempted state CPNI rules that required prior authorization inconsistent with our own rules, determining that such state rules would effectively negate  Y -federal policies promoting both carrier efficiency and consumer benefits.i0 @ xP-ԍxBOC Safeguards Order, 6 FCC Rcd at 7636,  130.i The U.S. Court  Y -of Appeals for the Ninth Circuit upheld this exercise of our preemption authority.d1X  xPV-ԍxSee California III, 39 F.3d at 933. The Ninth Circuit noted, "The FCC has shown that conflicting state rules regarding access to CPNI would negate the FCC's goal of allowing the BOCs to develop efficiently a mass  xP-market for enhanced services for small customers." Id.d We note that our preexisting CPNI rules were established pursuant to the Commission's general regulatory authority under the Communications Act of 1934. The 1996 Act establishes a specific statutory scheme governing access to and protection of CPNI in a way that  Yy-"balance[s] both competitive and consumer privacy interests with respect to CPNI."U2y  xP-ԍ xJoint Explanatory Statement at 205.U  YK-x17.` ` We seek comment on the extent to which Section 222 permits states to impose additional CPNI requirements. We further seek comment regarding what aspects of state regulation of CPNI or other customer information would enhance or impede the federal purpose. We are particularly interested in receiving comment on state regulation regarding:  Y-1) whether written or oral authorization is allowed,f3  xP #-ԍxSee discussion infra at Section III.B.ii.f and 2) the appropriate interpretation of  Y-the term "telecommunications service,"f4 xP%-ԍxSee discussion infra at Section III.B.i.f and whether such state regulation would enhance or impede valid federal interests with respect to CPNI and other customer information. " 40*(("Ԍ Y-x18.` ` In addition, we seek comment regarding whether the CPNI provisions of Section 222 and the data safeguards provision of Section 275(d) may by themselves give the Commission jurisdiction over both the interstate and intrastate use and protection of CPNI and other customer information with respect to matters falling within the scope of those sections.  Yv-x19.` ` In addition, we seek comment regarding the scope of the Commission's authority with respect to the subscriber list information provision set out in Section 222(e), which applies to information gathered in the provision of "telephone exchange service." Because Section 222(e) applies to "telephone exchange service," we further seek comment regarding the respective federal and state roles in ensuring that subscriber list information is made available "under nondiscriminatory and reasonable rates, terms, and conditions."  Y -xB.` ` Procedures for All Telecommunications Carriers: Sections 222(c) and (d)  Y-x` ` i. CPNI Use Prohibition  Yy-  Yb-x20.` ` Absent prior customer authorization, Section 222(c)(1) authorizes a telecommunications carrier to use individually identifiable CPNI obtained from the provision of a particular telecommunications service solely to provide "the telecommunications service from which such information is derived," or services necessary to provide that telecommunications service. Neither Section 222 nor the definition of the terms  Y-"telecommunications"L5 xPh-ԍxSee supra n.29.L and "telecommunications service":6X xP-ԍxId.: set forth in the 1996 Act provide explicit guidance as to the scope of the term "a telecommunications service," as used in Section 222. Moreover, the Joint Explanatory Statement in the Conference Report is silent on this issue. Some might contend that Congress intended to define the term "telecommunications service" broadly to include all services that the Commission has  Y|-classified as "basic" services.77X| xP-ԍxSee Computer II Final Order, 77 FCC 2d at 420,  96. As stated supra at n.5, U S West has stated that the statutory "provisions can be read . . . to support the broad use of CPNI within a carrier's provision of telecommunications services."7 Under this interpretation, providers of telecommunications services could use, without prior customer authorization, CPNI obtained from any such service to market any other telecommunications service. We believe, however, that a close reading of Section 222 does not support this interpretation.  Y -x21.` ` Section 222(c)(1), by its terms, bars a telecommunications carrier from using CPNI obtained from the provision of "a telecommunications service" for any purpose other than to provide "the telecommunications service" from which the CPNI is obtained or" 70*(( " services necessary to provide "such telecommunications service." The use of the singular in this section suggests that Congress recognized that telecommunications carriers provide a variety of telecommunications services and intended, absent prior customer approval, to prohibit a carrier from using CPNI obtained from the provision of one service for marketing or other purposes in connection with the provision of another service. This statutory interpretation is reinforced by other provisions of Section 222. Section 222(a) refers to "telecommunications services" and Section 222(b) refers to "any telecommunications service." These references support our reading that Congress contemplated that a single carrier provides different telecommunications services.  Y -x22.` ` We tentatively conclude that it would be reasonable to interpret Section 222 as distinguishing among telecommunications services based on traditional service distinctions. Under this approach, we tentatively conclude that we should treat the following as distinct  Y -"telecommunications services"8  xPN-ԍxUnder our proposed approach, all traditionally distinct telecommunications services include some purely intrastate traffic.: local (including shorthaul toll9  xP-ԍxUnder the AT&T Consent Decree, BOC services have been subject to LATA boundaries. See United  xPn-States v. Western Elec. Co., 552 F. Supp. 131 (D.D.C. 1982), aff'd sub nom. Maryland v. United States, 460  xP6-U.S. 1001 (1983) (subsequent history omitted); 47 U.S.C.  153(25). The Commission has not traditionally applied the interLATA and intraLATA distinction. For purposes of this NPRM, with respect to the BOCs, the term "shorthaul toll" should be interpreted as "intraLATA toll," and the term "interexchange" should be interpreted as "interLATA."); interexchange (including interstate, intrastate, and international long distance offerings, as well as shorthaul toll); and  Y -commercial mobile radio services (CMRS).:  xP-ԍxWe will consider in a separate proceeding whether services in the CMRS category should be further subdivided for purposes of implementing Section 222. We tentatively conclude that shorthaul toll should be treated as both a local telecommunications service, when provided by a LEC, as well as an interexchange telecommunications service, when provided by an interexchange carrier (IXC), because under traditional service distinctions both LECs and IXCs currently market and provide shorthaul toll service as part of an integrated package with local and  Y4-interexchange services, respectively.@;4  xP-ԍxUnder this interpretation, an IXC providing traditional interexchange service could use CPNI derived from the provision of shorthaul toll service for the purpose of providing interexchange service. That IXC, however, could not use such CPNI for the provision of local exchange service, a traditionally distinct service. Similarly, a LEC could use CPNI derived from the provision of local exchange service, but could not use such CPNI for the provision of other traditionally distinct services, such as interexchange service.@ We seek comment on these proposed distinctions and on other possible service distinctions. We further seek comment on how changes in telecommunications technology and regulation that allow carriers to provide more than one traditionally distinct service (e.g., LECs and IXCs may begin providing each others' services) may impact how carriers would implement the requirements of Section 222 to restrict use of CPNI from one telecommunications service to another. " ;0*(("Ԍ Y-x23.` ` CPNI obtained from providing any one of the discrete services listed above may not be used for any purpose, including marketing, involving any of the other services, unless the telecommunications carrier obtained prior customer authorization or one of the exceptions established by Sections 222(c) and (d) applies. We recognize that in the rapidly evolving market for telecommunications services, the distinctions we propose here may become outdated. Thus, we invite parties to suggest other distinctions among telecommunications services that in their view are mandated, envisioned, or logically consistent with the statute for CPNI protection. We request that parties who do so comment specifically on the costs and benefits of the schemes they propose, as well as the impact that such schemes will have on both competitive and consumer privacy interests. We also seek comment on whether and when technological and market developments may require us to revisit the issue of telecommunications service distinctions.  Y -x24.` ` Our interpretation also enhances customer privacy by giving customers greater control over CPNI use; CPNI derived from one telecommunications service cannot be used to provide other services or products without prior customer knowledge. We believe that our interpretation of the term "telecommunications service" also addresses competitive  Yy-considerations.n<` y xP-ԍxThe legislative history supports the view that the term "telecommunications service" should be interpreted in a fashion that considers competitive factors. The Joint Explanatory Statement states that "the new section 222 strives to balance both competitive and consumer privacy interests with respect to CPNI." Joint Explanatory Statement at 205. The Joint Explanatory Statement further states that the conference agreement  xP-adopted the Senate provisions with modifications. Id. The Senate bill restricted BOC use of CPNI as they  xP-entered new markets. See S. 652, 104th Cong., 1st Sess.,  102 (1995). The House bill also considered competitive equity as a factor in any CPNI provisions. In the House bill, the privacy provisions were not included in the BOC safeguards section, but rather were in a separate section that applied to all common  xP2-carriers. See H.R. 1555, 104th Cong., 1st Sess.,  105 (1995). The House Report indicates that the House considered "telecommunications service" to apply to different market sectors, such as local and longdistance,  xP-and that the House intended to prohibit the use of CPNI to crossmarket among these different services. H.R. Rep. No. 104204, 104th Cong., 1st Sess., 8990 (1995).n Our reading of the 1996 Act prohibits carriers that are established providers of certain telecommunications services from gaining an advantage by using CPNI to facilitate their entry into new telecommunications services without obtaining prior  Y4-customer authorization.=4  xP-ԍxWe also note that, in the Cable Communications Policy Act of 1984, Congress also sought to restrict  xP-unauthorized use of personally identifiable information by cable operators. See 47 U.S.C.  551(a). The Cable Act generally prohibits the disclosure of personally identifiable information unless such disclosure is necessary to render the services requested or to a "legitimate business activity related to" such service. 47 U.S.C. 551(c)(2)(A).   Y-x25.` ` We seek comment on our tentative conclusions concerning the scope of the term "telecommunications service," especially regarding the costs and benefits associated with our interpretation. We also seek comment on the effect on customer privacy of precluding the use of CPNI among telecommunications service categories. We further seek comment regarding how our proposed interpretation of the term "telecommunications" =0*((~" service" would affect competition both in the provision of telecommunications services, and the provision of other adjacent services and products, such as information services and CPE.  Y-x26.` ` The CPNI prohibition restricts unauthorized use of CPNI for any purpose other than those specified in Section 222(c)(1) and the exceptions listed in Section 222(d). For example, CPNI obtained from the provision of any telecommunications service may not  Yv-be used to market information services>v xP-ԍx47 U.S.C.  153(20) defines "information service" as "the offering of a capability for generating, acquiring, storing, transforming, processing, retrieving, utilizing, or making information available via telecommunications, and includes electronic publishing, but does not include any use of any such capability for the management, control, or operation of a telecommunications system or the management of a telecommunications service."  or CPE without prior customer authorization. Section 222(d)(1) enables carriers to use, disclose, or permit access to CPNI "to initiate, render, bill, and collect for telecommunications services." We seek comment on whether this exception permits carriers, without prior authorization, to use a customer's CPNI derived from the provision of one telecommunications service to perform installation, maintenance,  Y -and repair for any telecommunications service to which that customer subscribes. We also seek comment on whether, in the alternative, installation, maintenance, and repair would qualify as "services necessary to, or used in, the provision of such telecommunications service," under Section 222(c)(1)(B). We also seek comment on what other services might be "necessary to, or used in the provision of, such telecommunications service" under Section 222(c)(1)(B).  Yb-x` `  ii.Customer Notification of CPNI Rights/Prior Authorization(#  Y4-x27.` ` Section 222(c)(1) authorizes a carrier that obtains CPNI by providing a telecommunications service to use that CPNI for purposes unrelated to the service from which it is obtained if the customer approves. The statute, however, does not specify the procedures that a carrier must use to obtain customer approval, nor whether approval must be written or oral. We seek comment on what methods carriers may use to obtain customer authorization for use of CPNI in compliance with the statute. XxX` ` X Xa. Notification Requirements(#  Ye-x28.` ` We tentatively conclude that, in order to ensure full compliance with the prior authorization requirement specified by Section 222(c)(1), we should require a telecommunications carrier seeking approval for CPNI use from its customers to notify those customers of their rights to restrict access to their CPNI. We tentatively conclude that customers must know that they can restrict access to the CPNI obtained from their use of a telecommunications service before they waive that right, in order to be considered to have given approval. We seek comment on whether we should allow such notification to be given orally and simultaneously with a carrier's attempt to seek approval for CPNI use, or whether we should instead require an advance written notification. We further seek comment on what"!x>0*(("" is the least burdensome method of notification that would meet the objectives of the 1996  Y-Act. We note that under the Computer III CPNI rules, we require AT&T, the BOCs, and GTE to provide to multiline business customers written notification of their CPNI rights, along with election forms to restrict or authorize CPNI access. We seek comment on whether we need to specify the information that should be included in the customer notification, and, if so, the disclosure requirements that we should adopt. XxX` ` X Xb. Authorization Requirements(#  Y1-x29.` ` Carriers may choose to obtain written authorization from customers to use their CPNI for purposes unrelated to the provision of the service from which it was obtained. This authorization could take the form of a letter or a billing insert sent to the customer that contains a summary of the customer's CPNI rights and is accompanied by a postcard which the customer could sign and return to the carrier to authorize CPNI use. Written authorization provides greater protection to both customers and the carrier than oral authorization, in that the former advises customers in writing of their CPNI rights and provides the carrier with evidence that it has obtained customer approval. From a consumer protection standpoint, written notification, which is more specific and verifiable than oral notification, may be preferable.  Y4- x30.` ` We seek comment on whether Section 222(c)(1) allows carriers to choose to use outbound telemarketing programs to obtain oral "approval" from customers for use of  Y-their CPNI. We note that Section 222(c)(1) mandates that carriers obtain "the approval of the customer" in order to obtain access to the customer's CPNI, without indicating whether the approval has to be written or oral. There are two related provisions of the statute which give rise to conflicting inferences on this point. On the one hand, Section 222(c)(2) requires carriers to disclose CPNI to any person designated by a customer "upon affirmative written request by the customer," which suggests that Section 222(c)(1) allows oral approval, because unlike 222(c)(2) it does not specifically require written authorization.  YN-x31.` ` On the other hand, Section 222(d)(3) regarding inbound telemarketing provides that a telecommunications carrier may use, disclose, or permit access to CPNI obtained from its customers "to provide any inbound telemarketing, referral, or administrative services for the duration of the call, if such call was initiated by the customer and the customer approves of the use of such information to provide such service." Section 222(d)(3) could be interpreted as suggesting that oral consent cannot be given for a broader purpose or a longer duration. In the alternative, Section 222(d)(3) could also be interpreted as permitting a carrier to use CPNI to provide a customer with information for the duration of an inbound  Y"-call, even if the customer has otherwise restricted the carrier's use of its CPNI.?" xP%-ԍxCompare BOC ONA Order, 4 FCC Rcd at 217, n.1017 (otherwise restricted CPNI may be used to respond to customerinitiated inquiries). We seek comment on how Section 222(c)(1) should be interpreted in light of Section 222(c)(2) and Section 222(d)(3). We also seek comment on the privacy and competitive implications of"h$ ?0*((%" requiring carriers to obtain prior written approval under Section 222(c)(1) in order to obtain access to customer CPNI, as well as on the costs and benefits of requiring written approval.  Y-x32.` ` To the extent that oral approval is allowed under 222(c)(1), we propose to require carriers choosing to obtain oral approval to bear the burden of proof associated with such a scheme in the event of a dispute. Specifically, such carriers would be required to demonstrate through credible evidence that they had obtained the required customer authorization prior to granting access to the CPNI for purposes that otherwise would be unlawful.  Y -x 33.` ` Additionally, we seek comment on whether we should establish requirements regarding: (1) how long a customer's CPNI use authorization should remain valid; (2) how often carriers may contact a customer in order to attempt to obtain CPNI use authorization, whether or not the customer has requested restriction of its CPNI; and (3) whether and to what extent customers may authorize partial access to their CPNI (for example, limited to certain uses or time periods).  Yy- x` `  iii. CPNI Disclosure to Third Parties  YK-x!34.` ` Section 222(c)(2) requires carriers, when presented with a customer's affirmative written request, to provide that customer's CPNI to any person designated in the written authorization. Section 222(c)(2) imposes a disclosure requirement on carriers to ensure that any party with customer authorization, including unaffiliated third party competitors, can obtain access to individually identifiable CPNI. As such, carriers must provide a customer's CPNI to any party that has obtained an affirmative written authorization from the customer. We seek comment with respect to what additional mechanisms or procedures, if any, we ought to require telecommunications carriers to implement to guard against unauthorized access to CPNI by third parties.  Ye- XxX` `  iv.Safeguards for CustomerRestricted CPNI Data(#  Y7-x"35.` ` We tentatively conclude that all telecommunications carriers must establish effective safeguards to protect against unauthorized access to CPNI by their employees or agents, or by unaffiliated third parties. We noted above that we have required AT&T, the BOCs, and GTE to implement computerized safeguards and manual file indicators to prevent unauthorized access to CPNI. We seek comment on whether these requirements should  Y -continue to apply to AT&T, the BOCs, and GTE.  Y"-x#36.` ` We tentatively conclude that we should not now specify safeguard  Y#-requirements for all other telecommunications carriers, but we note that these carriers may wish to adopt some or all of the types of safeguards against unauthorized access to CPNI that  YQ%-we applied to AT&T, the BOCs, and GTE in Computer III, in satisfaction of their obligation"Q%?0*((p&"  Y-to develop effective means to protect restricted CPNI.l@ xPy-ԍxThese safeguards are discussed supra at Section II.A.l We seek comment, however, regarding whether we should impose on all telecommunications carriers any of the requirements imposed on AT&T, the BOCs, and GTE, or any other safeguard designed to protect against unauthorized access to restricted CPNI, and will adopt such requirements if the record indicates a need for them.  Yv-x` `  v.Aggregate CPNI  YH-x$37.` ` The aggregate CPNI provisions of Section 222(c)(3) permit telecommunications carriers, other than LECs, to use aggregate CPNI for purposes other than providing telecommunications services. LECs, however, may use aggregate CPNI for purposes other than providing telecommunications service only if the aggregate CPNI is  Y -made available to others on a reasonable and nondiscriminatory basis. In Computer III, we required the subject carriers to notify third parties about the availability of aggregate CPNI  Y -used by these carriers by publishing notices in trade publications or newsletters. We seek comment on whether, in addition to the statutory requirements of Section 222, we should also require all LECs to provide similar notification to others regarding the availability of aggregate CPNI, on a reasonable and nondiscriminatory basis prior to using such aggregate CPNI themselves.  Y-xC.` ` Applicability of Computer III CPNI Requirements  Y-x%38.` ` We conclude that the 1996 Act does not prohibit the Commission from enforcing CPNI requirements that are not inconsistent with the new statutory provisions, since nothing in the 1996 Act affects these requirements. We recognize that in certain  Y-respects our existing Computer III requirements place greater restrictions than the 1996 Act on CPNI access by AT&T, the BOCs, and GTE for the provision of enhanced services and  Y|-CPE.A |X xP-ԍxWe recognize that the legislation uses the term "information services" and does not discuss "enhanced services." Pending the outcome of this rulemaking, we require AT&T, the BOCs, and GTE to maintain the  xP-Computer III CPNI rules with respect to "enhanced services" as that term was previously defined by the Commission. To the extent that the 1996 Act requires more of a carrier, the statute of course governs. Under our reading of the new statute, these additional restrictions will continue to apply to those carriers, pending the outcome of this rulemaking.  Y7-x&39.` ` AT&T, the BOCs, and GTE must continue to provide annual written notification to customers about CPNI rights before using this CPNI to market enhanced services. The current retention of this requirement does not supersede the new statutory requirement that all telecommunications carriers, including AT&T, the BOCs, and GTE, obtain prior authorization before using CPNI to engage in any activity other than providing the service from which the CPNI was derived. The BOCs and GTE must also continue to" @A0*((!" obtain prior written authorization from customers with more than twenty lines before using their CPNI to market enhanced services. With respect to use of CPNI for marketing CPE, AT&T must continue to notify customers in a onetime billing insert before using the CPNI of these customers to market CPE. Similarly, the BOCs must continue to notify multiline customers annually about their CPNI rights before using this CPNI to market CPE. In addition, AT&T, the BOCs, and GTE must maintain any previously approved mechanisms (i.e, computer password systems, filing mechanisms) to restrict unauthorized internal access  Y_-to CPNI.  Y1-x'40.` ` We do not propose to extend our preexisting Computer III CPNI requirements, as modified by the 1996 Act, to other telecommunications carriers, because we tentatively conclude that these additional CPNI restrictions are not necessary to secure the public interest objectives of the 1996 Act. The Commission's CPNI rules were established  Y -in the context of the Computer III proceeding, in which the Commission adopted various nonstructural safeguards to protect independent ESPs and CPE suppliers from discrimination by AT&T, the BOCs, and GTE. The Commission specifically sought to prohibit these carriers from using CPNI obtained from their provision of basic regulated services to gain an anticompetitive advantage in the unregulated CPE and enhanced services markets. In that proceeding, we determined that, because AT&T, the BOCs, and GTE could gain anticompetitive advantages in this manner, their use of CPNI must be restricted.  Y-x(41.` ` We, however, recognize that some of the anticompetitive concerns we sought to address through the establishment of our CPNI rules may now be addressed by the new  Y-Section 222. In such light, we seek comment on which, if any, of our Computer III CPNI rules may no longer be necessary as a result of new Section 222. For example, we seek comment on the necessity for continuing to require AT&T, the BOCs, and GTE to provide  Y-written notification to multiline customers of their CPNI rights. Given that the Computer III CPNI rules are part of a scheme of nonstructural safeguards, parties should address how  Y|-changing the CPNI rules might influence the effect of other Computer III requirements. Parties should comment on whether there are privacy or competitive reasons for continuing to apply these specific preexisting requirements to these carriers, as well as on the costs and benefits of maintaining these requirements. We also invite parties to comment on what, if any, modifications to our current CPNI rules should be adopted to further the procompetitive, deregulatory goals of the 1996 Act, in addition to those discussed in this NPRM.  Y -x)42.` ` We further seek comment on whether AT&T, the BOCs, and GTE continue to possess a competitive advantage with respect to access to and use of customer CPNI, as well as whether any other entities, such as independent LECs, now possess similar advantages. In  Y#-particular, it appears that our recent decisions classifying AT&T as a nondominant carrier,8BX# xP%-ԍxSee Motion of AT&T Corp. to be Reclassified as a NonDominant Carrier, 11 FCC Rcd 3271 (1996)  xP&-recon. pending; Motion of AT&T Corp. to be Declared NonDominant for International Service, FCC 96209 (May 14, 1996). 8"#B0*(($" and the pending AT&T reorganization separating its equipment business from its  Y-telecommunications service business, may justify removal of Computer III CPNI requirements for AT&T. We tentatively conclude that removal of these requirements is now justified. We further seek comment regarding whether privacy, competitive concerns, or any other considerations, justify special regulatory treatment of AT&T, the BOCs, and GTE. Further, to the extent that commenters believe differential regulatory treatment is justified for certain carriers, we seek comment on whether such differential treatment should be permanent or limited in duration, and, if limited, what sunset provisions should apply.  Y -xD.` ` Section 222(e): Availability of Subscriber List Information  Y -x*43.` ` Section 222(e) states that a telecommunications carrier that provides "telephone exchange service" shall provide subscriber list information "gathered in its capacity as a provider of such service on a timely and unbundled basis, under nondiscriminatory and reasonable rates, terms, and conditions, to any person upon request for the purpose of  Y-publishing directories in any format."IC xP -ԍx47 U.S.C.  222(e). I We interpret Section 222(e) to require not only  Yy-LECs,DyX xP-ԍxA LEC is defined as "any person that is engaged in the provision of telephone exchange service or exchange access." 47 U.S.C.  153(26). but also any telecommunications carrier, including an IXC or cable operator, for example, to meet the requirements of this section to the extent such carrier provides  YK-telephone exchange service.EK xP-ԍxWe note that the Joint Explanatory Statement states that the subscriber list information requirement applies to "any provider of local telephone service." Joint Explanatory Statement at 205. We seek comment on this interpretation.  Y-x+44.` ` Subscriber list information is defined in Section 222(f)(3) as any information "identifying the listed names of subscribers of a carrier and such subscribers' telephone numbers, addresses, or primary advertising classifications (as such classifications are assigned at the time of the establishment of such service)" or any combination of such information, that the "carrier or an affiliate has published . . . or accepted for publication in  Y-any directory format."LF xPc -ԍx47 U.S.C.  222(f)(3). L We seek comment on what regulations, if any, are necessary to clarify the type and/or categories of information that must be made available under this section. In particular, we seek comment on the meaning of "primary advertising classifications," since the statute does not specify what is meant by this term. We also note that new Section 274(h)(2)(i) of the 1996 Act excepts from the definition of "electronic publishing" the provision of "directory assistance that provides names, addresses, and telephone numbers and does not include advertising." We tentatively conclude that the term "primary advertising classifications" in Section 222(e) is used differently than the term "advertising" in Section 274(h)(2)(i), and that therefore subscriber list information does not"F0*(( " fall within the definition of electronic publishing. We seek comment on this tentative conclusion.  Y-x,45.` ` We also seek comment on what regulations or procedures may be necessary to implement the requirement that subscriber list information be provided "on a timely and  Y-unbundled basis, under nondiscriminatory and reasonable rates, terms, and conditions."G  xP-ԍxWe have received information regarding difficulties faced by independent telephone directory publishers  xP-in obtaining subscriber list information, including rate issues. See Letter and attachment from Philip L.  xP-Verveer, et al., Willkie Farr & Gallagher, to A. Richard Metzger, Deputy Bureau Chief, Common Carrier Bureau, FCC, dated April 4, 1996.  Commenting parties should state specifically what regulations or procedures, if any, should be required and how Section 222(e) makes them necessary. In particular, commenters should comment on the format in which the information should be provided and how it should be unbundled.  Y -x-46.` ` We also seek comment on what safeguards may be necessary to ensure that a person seeking subscriber list information is doing so for the specified purpose of "publishing directories in any format." While the Joint Explanatory Statement states that the purpose of Section 222(e) is to guarantee "independent publishers access to subscriber list information"  Y -upon request,XH  xP-ԍxJoint Explanatory Statement at 205. X we seek comment on how and to what extent a telecommunications carrier subject to this section may seek authorization from a person or entity requesting such information. Parties should comment on whether such requests must be in writing or whether they can be made orally.  Y-xE.` ` Section 275(d): Alarm Monitoring Procedures for LECs  Y-x.47.` ` Section 275(d) prohibits a LEC from recording or using in any fashion "the occurrence or content of calls received by providers of alarm monitoring services for the purposes of marketing such services on behalf of such [LEC], or any other entity." Thus, Section 275(d) restricts LECs from using the information described in that section for marketing another alarm monitoring service, either their own service or a service offered by another affiliated or unaffiliated entity. We tentatively conclude that a customer's authorization under Section 222(c)(1) will not extend to any records concerning the occurrence of calls received by alarm monitoring service providers. Although call content information is not considered CPNI, we note that, pursuant to Section 275(d), LECs may not use information concerning the "content of calls" received by providers of alarm monitoring services to market such services. We seek comment on what procedures LECs should develop to comply with Section 275(d).  X - " @H0*((!"Ԍ X-tIV. CONCLUSION ă x  Y-x/48.` ` In this notice, we seek comment on rules to ensure compliance by telecommunications carriers with the provisions relating to carrier use of and access to CPNI and other customer information established by the Telecommunications Act of 1996 in new Sections 222(c)(f) and 275(d), and to secure the privacy and competitive protections mandated by Congress. We invite comment on our interpretation of the requirements imposed by Section 222(c)(f) and Section 275(d), as well as our tentative conclusions regarding regulations necessary to ensure carrier compliance with these requirements and to more fully effectuate the statutory policies. We also request parties to specify whether their comments on our proposed regulatory requirements address privacy or competitive concerns, and to comment on the appropriate duration of such regulatory requirements. Any party disagreeing with our tentative conclusions should explain with specificity in terms of costs and benefits its position and suggestions for alternative regulatory policies.  Y- V. PROCEDURAL ISSUES  YL-xA.` ` Ex Parte Presentations  Y-x049. ` ` This is a nonrestricted noticeandcomment rulemaking proceeding. Ex parte presentations are permitted, except during the Sunshine Agenda period, provided that they  Y-are disclosed as provided in the Commission's rules. See generally 47 C.F.R.  1.1202, 1.1203, 1.1206.  Y-xB.` ` Initial Regulatory Flexibility Analysis(#`  Yf-x150.` ` Pursuant to the Regulatory Flexibility Act of 1980, 5 U.S.C.  601612, the Commission's Initial Regulatory Flexibility Analysis with respect to the NPRM is as follows:  Y!-x251.` ` Reason for Action: The Commission is issuing this NPRM seeking comment on proposed regulations to ensure telecommunications carriers' compliance with requirements for the use and protection of customer proprietary network information (CPNI) and other customer information set forth in the Telecommunications Act of 1996, Pub. L. 104104, 110 Stat. 56 (1996).  Y"-x352.` ` Objectives: The objective of the NPRM is to provide an opportunity for public comment and to provide a record for a Commission decision on the issues stated above. The Commission is committed to reducing the regulatory burdens on small communications services companies whenever possible, consistent with our other public interest responsibilities. "$'H0*((P("Ԍ Y-x453.` ` Legal basis: The NPRM is adopted pursuant to Sections 1, 4, 222, 275, and 303(r) of the Communications Act of 1934, as amended, 47 U.S.C.  151, 154, 222, 275,  Y-and 303(r).  Y-x554.` ` Description, potential impact, and number of small entities affected: Any rule changes that might occur as a result of this proceeding could impact small business entities, as defined in Section 601(3) of the Regulatory Flexibility Act. After evaluating the comments in this proceeding, the Commission will further examine the impact of any rule changes on small entities and set forth findings in the Final Regulatory Flexibility Analysis. The Secretary shall send a copy of this NPRM to the Chief Counsel for Advocacy of the Small Business Administration in accordance with Section 603(a) of the Regulatory  Y -Flexibility Act, Pub. L. No. 96354, 94 Stat. 1164, 5 U.S.C.  601, et seq. (1981).  Y -x655.` ` Reporting, recordkeeping and other compliance requirement: None.  Y -x756.` ` Federal rules that overlap, duplicate or conflict with the Commission's  Y-proposal: None.  Yb-x857.` ` Any significant alternatives minimizing impact on small entities and consistent  YK-with stated objectives: The NPRM solicits comments on a variety of alternatives.  Y-x958.` ` Comments are solicited: Written comments are requested on this Initial Regulatory Flexibility Analysis. These comments must be filed in accordance with the same filing deadlines set for comments on the other issues in this NPRM but they must have a separate and distinct heading designating them as responses to the Regulatory Flexibility Analysis. The Secretary shall send a copy of the Notice to the Chief Counsel for Advocacy of the Small Business Administration in accordance with Section 603(a) of the Regulatory  Y-Flexibility Act, 5 U.S.C.  601, et seq.  Ye-C.xInitial Paperwork Reduction Act of 1995 Analysis  Y7-x:59.` ` This NPRM contains either a proposed or modified information collection. As part of its continuing effort to reduce paperwork burdens, we invite the general public and the Office of Management and Budget (OMB) to take this opportunity to comment on the information collections contained in this NPRM, as required by the Paperwork Reduction Act of 1995, Pub. L. No. 10413. Public and agency comments are due at the same time as other comments on this NPRM; OMB comments are due 60 days from date of publication of this NPRM in the Federal Register. Comments should address: (a) whether the proposed collection of information is necessary for the proper performance of the functions of the Commission, including whether the information shall have practical utility; (b) the accuracy of the Commission's burden estimates; (c) ways to enhance the quality, utility, and clarity of the information collected; and (d) ways to minimize the burden of the collection of information on the respondents, including the use of automated collection techniques or other forms of information technology."#'H0*((P("Ԍ Y- ęxD.` ` Comment Filing Procedures  Y-x;60.` ` Pursuant to applicable procedures set forth in Sections 1.415 and 1.419 of the Commission's rules, 47 C.F.R.  1.415, 1.419, interested parties may file comments on or before June 11, 1996 and reply comments on or before June 26, 1996. To file formally in this proceeding, you must file an original and six (6) copies of all comments, reply comments, and supporting comments. If you want each Commissioner to receive a personal copy of your comments, you must file an original and eleven (11) copies. Comments and reply comments should be sent to Office of the Secretary, Federal Communications Commission, 1919 M Street, N.W., Room 222, Washington, D.C. 20554, with a copy to Janice Myles of the Common Carrier Bureau, 1919 M Street, N.W., Room 544, Washington, D.C. 20554. Parties should also file one copy of any documents filed in this docket with the Commission's copy contractor, International Transcription Services, Inc., 2100 M Street, N.W., Suite 140, Washington, D.C. 20037. Comments and reply comments will be available for public inspection during regular business hours in the FCC Reference Center, 1919 M Street, N.W., Room 239, Washington, D.C. 20554.  Yy-x<61.` ` In order to facilitate review of comments and reply comments, both by parties and by Commission staff, we require that comments be no longer than twentyfive (25) pages and reply comments be no longer than fifteen (15) pages. Copies of specific proposed rules that conform to the C.F.R. format, relevant state orders, sample CPNI notification and authorization forms or letters, and empirical economic studies will not be counted against these page limits. Comments and reply comments must also comply with Section 1.49 and  Y-all other applicable sections of the Commission's Rules.I  xPh-ԍxSee 47 C.F.R.  1.49. However, we require here that a summary be included with all comments and reply comments, regardless of length, although a summary that does not exceed three pages will not count toward the page limit for comments or reply comments. This summary may be paginated separately from the rest of the pleading (e.g., as "i, ii").  Y-x=62.` ` Parties are also asked to submit comments and reply comments on diskette. Such diskette submissions would be in addition to and not a substitute for the formal filing requirements addressed above. Parties submitting diskettes should submit them to Janice Myles of the Common Carrier Bureau, 1919 M Street, N.W., Room 544, Washington, D.C. 20554. Such a submission should be on a 3.5 inch diskette formatted in an IBM compatible form using MS DOS 5.0 and WordPerfect 5.1 software. The diskette should be submitted in "read only" mode. The diskette should be clearly labelled with the party's name, proceeding, type of pleading (comment or reply comments) and date of submission. The diskette should be accompanied by a cover letter.  Y-x>63.` ` Written comments by the public on the proposed and/or modified information collections are due June 11, 1996. Written comments must be submitted by the Office of Management and Budget (OMB) on the proposed and/or modified information collections on or before 60 days after date of publication in the Federal Register. In addition to filing""I0*((#" comments with the Secretary, a copy of any comments on the information collections contained herein should be submitted to Dorothy Conway, Federal Communications Commission, Room 234, 1919 M Street, N.W., Washington, DC 20554, or via the Internet to dconway@fcc.gov and to Timothy Fain, OMB Desk Officer, 10236 NEOB, 725 17th Street, N.W., Washington, DC 20503 or via the Internet to fain_t@al.eop.gov.  Y_- VI. ORDERING CLAUSES ă  Y2-x?64.` ` Accordingly, IT IS ORDERED that pursuant to Sections 1, 4, 222, 275, and 303(r) of the Communications Act of 1934, as amended, 47 U.S.C.  151, 154, 222, 275,  Y -and 303(r), a NOTICE OF PROPOSED RULEMAKING is hereby ADOPTED.  Y -x@65.` ` IT IS FURTHER ORDERED that, the Secretary shall send a copy of this NOTICE OF PROPOSED RULEMAKING, including the regulatory flexibility certification, to the Chief Counsel for Advocacy of the Small Business Administration, in accordance with  Y-paragraph 603(a) of the Regulatory Flexibility Act, 5 U.S.C.  601 et seq. (1981). x` `  FEDERAL COMMUNICATIONS COMMISSION  Y-x` `  William F. Catonhpp x` `  Acting Secretary  iN  "I0*((" Index Terms: $// NPRM, customer proprietary network information, CPNI, subscriber list information, alarm monitoring data safeguards //$ $/ 47 U.S.C.  222, 47 U.S.C.  275(d) iN   iN /$