аЯрЁБс>ўџ 57ўџџџ4џџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџьЅСM №Пяbjbjт=т= "(€W€Wяџџџџџџlў ў ў ў ў ў ў  ќќќќ $ i:888888nІ$ЪЎАААААА$Ѓ Уdдў о88оод:ў ў 88щ8:::о"ў 8ў 8Ў:оЎ:’:Ьrў ў š8, PшІ= BТ ъќ:Šš!Hi’':'š:  ў ў ў ў йENUM FORUM CONTRIBUTION: Contribution #: GEN0041R0 SOURCE: AT&T Contributor: Steven D. Lind sdlind@att.com 973-236-6787 DATE SUBMITTED: August 12, 2002 TITLE: Proposed Introductory Sections for the Unified Document This document is offered to the ENUM Forum as a basis for discussion and is not a binding proposal on AT&T. AT&T specifically reserves the right to amend or withdraw the statements contained herein. Introduction ENUM is a protocol developed in the IETF (RFC 2916) whereby the "Domain Name System (DNS) can be used for identifying available services connected to one E.164 number." Specifically "through [the] transformation of E.164 numbers into DNS names and the use of existing DNS services like delegation through Name Server (NS) records, and use of Naming Authority Pointer (NAPTR) records in DNS, one can look up what services are available for a specific domain name (E.164 number) in a decentralized way with distributed management of the different levels in the lookup process." RFC 2916 provided both that "the domain ‘e164.arpa’ is being populated in order to provide the infrastructure in DNS for storage of E.164 numbers" and that "names within this zone are to be delegated to parties according to the International Telecommunication Union - Telecommunication Standardization Sector (ITU-T) Recommendation E.164." In order to implement ENUM for U.S. telephone numbers, substantial DNS-based infrastructure must be put into place within the United States. A registry(ies) needs to be established to contain DNS records for the domain names based on participating telephone numbers. Other name servers also need to be established to hold the ENUM application information in NAPTR records for each participating number. A provisioning process needs to be established in order for subscribers who wish to opt-in to ENUM to populate all the necessary DNS records through the use of registrars. Purpose [propose to delete this section] Scope This document is intended to provide the specifications necessary to implement the Tier 1 registry for ENUM within the United States. It should provide sufficient information to allow a contracting entity to put such an implementation out for bid to business organizations in the industry. As such, it describes, among other things, the reference architecture for the US portion of ENUM, the operational and administrative aspects of a Tier 1 registry, and the provisioning process. It also addresses the necessary security and privacy issues inherent in implementing this system. Background – ENUM Ad-Hoc Report At the meeting of ITU-T Working Party 1/2 in Berlin in October 2000, RFC2916 was discussed and the participants "noted that most ENUM service and administrative decisions are national issues under the purview of ITU Member States, since most of the E.164 resources are utilized nationally." On December 18, 2000 the National Telecommunications and Information Administration (NTIA) held a public meeting on ENUM at the Department of Commerce in Washington, D.C. at which ENUM was discussed and various perspectives on how ENUM services might be instantiated in the United States were presented. It was proposed to establish a new Ad Hoc group to advise the US Department of State on US implementation of a designated ENUM DNS domain. At the January 2001 meeting for the US Study Group A, this new Ad Hoc group was created, and the group held its first meeting February 12-13, 2001. The Ad Hoc group presented its completed report at a US Study Group A meeting on July 31, 2001. Interested participants of the Internet and telecommunications industries founded the ENUM Forum to further the work presented in the Ad Hoc group’s report and laid the groundwork for implementation of ENUM in the United States. This specification is a product of those efforts. On the international front, ITU-T Study Group 2 has developed a Supplement to educate Administrations about the issues to be addressed in the national implementation of ENUM. In addition, a Recommendation on the delegation of E.164 country codes is in the process of being developed. Until that Recommendation is approved, a set of interim procedures have been approved to govern the process of such delegations into “e164.arpa” using RIPE-NCC. Б№§'(ХЧд­ Ў Ж И ж и о $DE012яї№хн№№иЭи№ШПИШИЎИШИШИПИЋCJ6PJ]mH sH  PJmH sH B*CJhphPJ^J56OJQJ\]OJQJ5OJQJ^J5>*OJQJ\^J OJQJ^JCJ OJQJ^J6789:GHIfw‡ŽЏАБ№ёњјњчњјккјаајЦЦЦјајаајјј „а„а^„а`„а &dPЦџ $&d PЦџ a$$ Ц„„„^„`„a$$a$я§ёђѓєѕіїјљњћќ§ХЦЧдеm §ѓѓѓѓѓѓѓѓѓѓѓцс§ž§§CEЦ€ёДg&$a$ $ Цf!„0§]„0§a$ $dNЦџm n ­ Ў Ж З и о п $DE§§§И§§И§§u§§§CEЦ€ёДg&DC$EЦ€ёДg& 12я§§§ 1hАа/ Ар=!А"А# $ %А i8@ёџ8 NormalCJ_HaJmH sH tH R@R ƒHeading 1,heading 1,Heading1,h1,H1-Heading 1,1,Header 1,Legal Line 1,head 1,l1,II+,I,list 1,Head 1 (Chapter heading),H1,Huvudrubrik$$ & FЄ№Є<@&5CJKHOJQJaJmH sH << ќHeading 2,Heading2,h2,H2-Heading 2,2,Header 2,l2,Header2,Header 2,heading 2,2 2,heading 2,22,heading2,list2,H2,A,A.B.C.,list 2,list 2,heading 2TOC,Head 2,List level 2,Level 2 Head,Heading Indent No L2,UNDERRUBRIK 1-2,Rubrik 02,PRTM Heading 2,H21,a2,21$ & FЄ№Є<@&56OJQJaJmH sH 44 ћHeading 3,Heading3,h3,H3-Heading 3,3,l3.3,l3,list 3,heading 3,list3,subhead,h31,H3,Underrubrik2,H31,a3,1.,Heading No. L3,3 bullet,b,Second,SECOND,3 Ggbullet,BLANK2,4 bullet,3m,H32,H33,H311,H34,H312,H35,H36,H37,H313,H321,H331,H3111,H341,H3121,H351,H361$ & FЄ№Є<@&OJQJaJmH sH †† $Heading 4,Heading4,h4,4,H4-Heading 4$ & FЄ№Є<@&OJQJaJmH sH РР AHeading 5,Heading5,h5,5,H5-Heading 5,H5-Heading 5 ,l5,heading5,H5 & FЄ№Є<@&CJOJQJaJmH sH pp Heading 6,Heading6,h6,6 & FЄ№Є<@&6CJOJQJaJmH sH ОО @Heading 7,7,ExhibitTitle,st,Objective,heading7,req3,h7,SDL title & FЄ№Є<@&CJOJQJaJmH sH тт PHeading 8,8,FigureTitle,Condition,requirement,req2,req,figure title,heading 8,ft & FЄ№Є<@&6CJOJQJaJmH sH њ њ [Heading 9,9,TableTitle,Cond'l Reqt.,rb,req bullet,req1,tt,table title,TableText,Table Title & FЄ№Є<@&56CJOJQJaJmH sH <A@ђџЁ< Default Paragraph FontBўOђB bullet$„„˜ў^„`„˜ўa$ OJQJaJя(џџџџ6789:GHIfw‡ŽЏАБ№ёђѓєѕіїјљњћќ§ХЦЧдеmn­ЎЖЗиоп$ D E 12ё˜0€€˜0€€˜0€€˜0€€˜0€€˜0€€˜0€€˜0€€˜0€€˜0€€˜0€€˜0€€˜0€€˜0€€˜0€€˜0€€˜0€€˜0€€˜0€€˜0€€˜0€€˜0€€˜0€€˜0€€˜0€€˜0€€˜0€€˜0€€˜0€€˜0€€˜0€€˜0€€˜0€€˜0€€˜0€€˜0€€˜0€€˜0€€ 0€€˜0€Ч˜0€Ч˜0€Ч˜0€Ч˜0€Ч 0€€˜0€Ў˜0€Ў 0€€˜0€и˜0€и 0€€˜0€€˜0€€˜0€€˜0€€˜0€€š0€€яёm яяџџ _Toc15143993 _Toc15143994 _Toc15143995 _Toc15143996Ўи$ ёгЕнC ё хэё§ИПќ § u•ё3333џџ Steven D. LindSC:\Documents and Settings\sdlind\My Documents\standards\enumf\intro-6000_ENUMUD.docSteven D. LindkC:\Documents and Settings\sdlind\Application Data\Microsoft\Word\AutoRecovery save of intro-6000_ENUMUD.asdSteven D. LindkC:\Documents and Settings\sdlind\Application Data\Microsoft\Word\AutoRecovery save of intro-6000_ENUMUD.asdSteven D. LindkC:\Documents and Settings\sdlind\Application Data\Microsoft\Word\AutoRecovery save of intro-6000_ENUMUD.asdSteven D. LindbC:\Documents and Settings\sdlind\My Documents\standards\enumf\GEN0041R0-Lind-intro-6000_ENUMUD.doc.—aвцxФ „А„PўЦА^„А`„Pў„@„Р§Ц@^„@`„Р§.„а„0§Ца^„а`„0§..„`„ ќЦ`^„``„ ќ... „№„ќЦ№^„№`„ќ .... „€„€ћЦ€^„€`„€ћ ..... „„№њЦ^„`„№њ ...... „ „`њЦ ^„ `„`њ....... „0„аљЦ0^„0`„аљ.........—aџџџџџџџџ1ёџ@€ююЌрtюGяp@џџUnknown Eric C. JungATGџџџџџџџџџџџџG‡z €џTimes New Roman5€Symbol3& ‡z €џArialG€  MS Mincho-џ3џ fg;& ‡z €џHelvetica"qˆ№аhŒbh&Œbh&sі Y№ ДД20%D 2ƒq№џџ1Steven D. LindSteven D. Lindўџр…ŸђљOhЋ‘+'Гй0x˜ЄАШдрє  4 @ LX`hpф1ssSteven D. Lindtevtev Normal.dotiSteven D. Lind2evMicrosoft Word 9.0@^аВ@Иg9 BТ@Иg9 BТsі ўџеЭеœ.“—+,љЎ0ь hp€ˆ˜  ЈАИ Р ЮфAT&Titl%э 1 Title ўџџџ !"#ўџџџ%&'()*+ўџџџ-./0123ўџџџ§џџџ6ўџџџўџџџўџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџRoot Entryџџџџџџџџ РFPМз= BТ8€1Tableџџџџџџџџџџџџ'WordDocumentџџџџџџџџ"(SummaryInformation(џџџџ$DocumentSummaryInformation8џџџџџџџџџџџџ,CompObjџџџџjObjectPoolџџџџџџџџџџџџPМз= BТPМз= BТџџџџџџџџџџџџўџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџўџ џџџџ РFMicrosoft Word Document MSWordDocWord.Document.8є9Вq