This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
[enum-announce] Fw: NCC#2009051650 [Fw: 2.6.9.e164.arpa]
- Next message (by thread): [enum-announce] Fw: NCC#2009051650 [Fw: 2.6.9.e164.arpa]
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
RIPE NCC Staff
enum-request at ripe.net
Mon Oct 5 11:22:55 CEST 2009
----- Begin forwarded message ----- Date: Fri, 05 Jun 2009 11:38:27 +0200 From: RIPE NCC Hostmaster <hostmaster at ripe.net> To: enum-announce at ripe.net Subject: Fw: NCC#2009051650 2.6.9.e164.arpa ----- Begin forwarded message ----- Date: Fri, 29 May 2009 16:26:24 +0200 From: <richard.hill at itu.int> To: <enum-request at ripe.net> Subject: RE: NCC#2009051650 [RE: ENUM RIPE-384 Form Questions] Message-Id: <334A4109C6BEA14ABB48EBCF274A6C8A048B42CE at MAILBOX1.blue.itu.ch> The ITU Telecommunications Standardization Bureau (TSB) objects to this request because no approval for delegation of the code 962 has been received from the concerned country, Jordan. Until formal approval is given in writing by the Director of TSB, no delegation should take place for this code. Richard Hill ----------------------------------------- Richard Hill Counsellor, ITU-T SG2 and SG3 International Telecommunication Union Place des Nations CH-1211 Geneva 20 Switzerland tel: +41 22 730 5887 FAX: +41 22 730 5853 Email: richard.hill at itu.int Study Group 2 email: tsbsg2 at itu.int Study Group 3 email: tsbsg3 at itu.int > -----Original Message----- > From: RIPE NCC Staff [mailto:enum-request at ripe.net] > Sent: Monday, May 18, 2009 10:32 AM > To: Hill, Richard; enum-announce at ripe.net > Subject: Fw: NCC#2009051650 [RE: ENUM RIPE-384 Form Questions] > > ----- Begin forwarded message ----- > > Date: Mon, 18 May 2009 09:53:54 +0300 > From: Fahd Batayneh <fahd.b at nitc.gov.jo> > To: RIPE NCC Staff <enum-request at ripe.net> > Subject: RE: NCC#2009051650 ENUM RIPE-384 Form Questions > Message-Id: <251EF2F094F40640943E9B30CC7CCE150A3E768996 at GOJVMB03.GOJ.GOV> > > > Hi, > > > > Here is what you requested for. > > > ENUM Request Form > > RIPE NCC > Document ID: ripe-384 > Date: August 2006 > > % ENUM Request Form > % You can use this form to request ENUM delegation of an E.164 country > code. > % Submit the completed form to <enum-request at ripe.net>. > % Please see ripe-385 for instructions on how to complete this form. > > #[GENERAL INFORMATION]# > % > % Please do not change the value of the two fields below. > Request-type: enum > Form-version: 1.0 > > #[REQUESTER DETAILS]# > % > % Please add your contact details. > Name: Fahd A. Batayneh (ENUM Administrator) > Phone: (962) 6 5300 267 > Fax-no: (962) 6 5300 277 > E-mail: fahd.b at nitc.gov.jo<mailto:fahd.b at nitc.gov.jo> > #[ORGANISATION DETAILS]# > % > % Which organization is requesting the delegation? > Legal-organization-name: National Information Technology Center (NITC) > Organisation-location: Royal Scientific Society Campus, Al-Jubeiha, > Amman, Jordan > Website: http://www.nitc.gov.jo/en/ > > #[DATABASE TEMPLATE]# > % > % Please complete all of the fields below. > Domain: 2.6.9.e164.arpa > Descr: National Information Technology Center (NITC) > Org: ORG-NIC1-RIPE > Admin-c: Fahd A. Batayneh (fahd.b at nitc.gov.jo<mailto:fahd.b at nitc.gov.jo>) > Tech-c: Fahd A. Batayneh (fahd.b at nitc.gov.jo<mailto:fahd.b at nitc.gov.jo>) > Zone-c: Fahd A. Batayneh (fahd.b at nitc.gov.jo<mailto:fahd.b at nitc.gov.jo>) > NServer: ns1.nitc.gov.jo > NServer: ns2.nitc.gov.jo > NServer: jordan1st.nic.gov.jo > Mnt-by: Fahd A. Batayneh > Changed: hostmaster at ripe.net > Source: RIPE > > #[SUPPLEMENTAL COMMENTS]# > % > % Please add more information if you think it will help us understand > % this request. > The Jordanian NITC is an affiliate of the Jordanian Ministry of > Information and Communication Technology (MoICT) - the Jordanian > administration recognized by the ITU > #[END of REQUEST]# > > > > Thank you, > > > > -- FAB > > > > -----Original Message----- > From: RIPE NCC Staff [mailto:enum-request at ripe.net] > Sent: Monday, May 18, 2009 9:49 AM > To: Fahd Batayneh > Subject: Re: NCC#2009051650 ENUM RIPE-384 Form Questions > > > > Dear Fahd, > > > > Thank you for your email. > > > > Can you please resend your request but with the ENUM template as plain > text in the ticket? (so not as an attachement) > > > > This is necessary for that we can proceed with your request. > > > > > > We look forward to your reply. > > > > Kind regards, > > > > Marco Schmidt > > RIPE NCC IPRA > > > > On Sun, 17 May 2009 10:31:58 +0300, Fahd Batayneh wrote: > > > Hi, > > > > > > > > > > > > Firstly, thank you your informative reply; it was quite helpful. > > > > > > > > > > > > Please find attached the official Jordan ENUM registration form. > > > > > > > > > > > > Please don't hesitate to contact me if there are any misleading > information that may require any clarity or amendments. > > > > > > > > > > > > Thank you, > > > > > > > > > > > > -- FAB > > > > > > > > > > > > -----Original Message----- > > > From: RIPE NCC Staff [mailto:enum-request at ripe.net] > > > Sent: Wednesday, May 13, 2009 12:08 PM > > > To: Fahd Batayneh > > > Subject: Re: NCC#2009051650 ENUM RIPE-384 Form Questions > > > > > > > > > > > > Dear Fahd, > > > > > > > > > > > > Thank you for your email. > > > > > > > > > > > > We are aware that people face some difficulties when they face the > first time the RIPE Whois database. But no worries, it is not so > difficult :) > > > > > > > > > > > > > > > > > > We set up some supporting notes for ENUM requests that should answer > most of your questions: > > > > > > http://www.ripe.net/ripe/docs/ripe-385.html > > > > > > > > > > > > Let me also answer in detail your questions: > > > > > > > > > > > > > org: <add org-ID> ==> Where can I obtain the org-ID from? > > > > > > This is described in the the link above. > > > > > > > > > > > > > admin-c: <add nic-handle of administrative contact> ==> What is an > nic-handle? > > > > > > This is the person object described in the link above > > > > > > > > > > > > > tech-c: <add nic-handle of technical contact> ==> Should this be > different from the other two contacts? > > > > > > No, it can be the same nic-handle like for admin-c: > > > > > > > > > > > > > zone-c: <add nic-handle of DNS contact> ==> Should this be different > from the other two contacts? > > > > > > No, it can be the same nic-handle like the others > > > > > > > > > > > > > nserver: <add nameserver name> ==> > > > > > > > nserver: <add nameserver name> ==> Is this one and the above one the > NS of the current DNS system? Or should I dedicate NS for the ENUM > > > > > > The Domain object must contain at least two "nserver" lines with names > of nameservers, those can look like > > > > > > > > > > > > nserver: myserver.com > > > > > > nserver: ns.company.org > > > > > > or > > > > > > nserver: ns.4.0.5.e164.arpa 192.0.2.1 > > > > > > > > > > > > > mnt-by: <add mntner name> ==> What is a mntner name? > > > > > > This is described in the the link above. > > > > > > > > > > > > > changed: hostmaster at ripe.net ==> Should I change this e-mail ID? > > > > > > No, please leave this email. > > > > > > > > > > > > > source: RIPE ==> Should I change this? If yes, to what? > > > > > > No, please leave the source. > > > > > > > > > > > > > > > > > > Please reply to this email with the completed ENUM request form. > > > > > > > > > > > > Don't hesitate to contact me if you have any open question. > > > > > > > > > > > > > > > > > > Kind regards, > > > > > > > > > > > > Marco Schmidt > > > > > > RIPE NCC > > > > > > > > > > > > Please don't hesitate > > > > > > > > > > > > On Sun, 10 May 2009 09:33:07 +0300, Fahd Batayneh wrote: > > > > > > > Hi, > > > > > > > > > > > > > > My name is Fahd. I work with the Jordanian NITC; an branch of the > Ministry of Information and Communication Technology (MoICT). Since MoICT > is the Jordanian administration recognized by the ITU, we are currently > in the process of launching our ENUM service. As I was filling out the > request form (RIPE-384), I faced a few problems as follows: > > > > > > > > > > > > > > org: <add org-ID> ==> Where can I obtain the org-ID from? > > > > > > > admin-c: <add nic-handle of administrative contact> ==> What is an > nic-handle? > > > > > > > tech-c: <add nic-handle of technical contact> ==> Should this be > different from the other two contacts? > > > > > > > zone-c: <add nic-handle of DNS contact> ==> Should this be different > from the other two contacts? > > > > > > > nserver: <add nameserver name> ==> > > > > > > > nserver: <add nameserver name> ==> Is this one and the above one the > NS of the current DNS system? Or should I dedicate NS for the ENUM > > > > > > > mnt-by: <add mntner name> ==> What is a mntner name? > > > > > > > changed: hostmaster at ripe.net ==> Should I change this e-mail ID? > > > > > > > source: RIPE ==> Should I change this? If yes, to what? > > > > > > > > > > > > > > I would appreciate it if you can help me on these matters. > > > > > > > > > > > > > > Thank you, > > > > > > > > > > > > > > [cid:image001.jpg at 01C9D152.5343DE50] > > > > > > > > > > > > No virus found in this incoming message. > > > > > > Checked by AVG - www.avg.com > > > > > > Version: 8.5.336 / Virus Database: 270.12.27/2111 - Release Date: > 05/12/09 18:03:00 > > > > No virus found in this incoming message. > > Checked by AVG - www.avg.com > > Version: 8.5.336 / Virus Database: 270.12.32/2118 - Release Date: > 05/17/09 16:58:00 > > ------ End forwarded message ------ ------ End forwarded message ------ ------ End forwarded message ------ -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 206 bytes Desc: not available URL: </ripe/mail/archives/enum-announce/attachments/20091005/da5c4d64/attachment.sig>
- Next message (by thread): [enum-announce] Fw: NCC#2009051650 [Fw: 2.6.9.e164.arpa]
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]