From enum-request at ripe.net Wed Apr 5 16:34:20 2006 From: enum-request at ripe.net (RIPE NCC Staff) Date: Wed, 05 Apr 2006 16:34:20 +0200 Subject: [enum-announce] Fw: NCC#2006040655 [Bulgaria ENUM Mapping] Message-ID: <200604051434.k35EYMEl017101@cat.ripe.net> ----- Begin forwarded message ----- Date: Wed, 5 Apr 2006 16:00:21 +0300 From: Dimitar Ganchev To: enum-request at ripe.net Subject: NCC#2006040655 Bulgaria ENUM Mapping Message-Id: <200604051600.21607.mitko at bol.bg> Dear Ripe NCC Staff, We hereby apply for the 9.5.3.e164.arpa delegation. Both nameservers are located in Bulgaria Many thanks Dimitar Ganchev BOL.BG 2.1. Domain Object domain: 9.5.3.e164.arpa descr: Bulgaria ENUM Mapping admin-c: VM4-RIPE tech-c: DG7-RIPE tech-c: VM4-RIPE zone-c: DG7-RIPE nserver: ns.bol.bg nserver: ns.bolbg.com mnt-by: BGENUM-MNT mnt-lower: BGENUM-MNT changed: mitko.com source: RIPE 2.2. Administrative Contact person: Veni Markovski address: ISOC - Bulgaria address: p.o.box 71 address: BG-1164 Sofia address: Bulgaria phone: +359 2 9809666 fax-no: +359 2 9806431 e-mail: veni at veni.com nic-hdl: VM4-RIPE source: RIPE # Filtered 2.3. Technical Contact person: Dimitar Ganchev address: BOL.BG address: p.o.box 71 address: BG-1164 Sofia address: Bulgaria phone: +359 2 9809666 fax-no: +359 2 9806431 e-mail: mitko at mitko.com nic-hdl: DG7-RIPE source: RIPE # Filtered person: Veni Markovski address: ISOC - Bulgaria address: p.o.box 71 address: BG-1164 Sofia address: Bulgaria phone: +359 2 9809666 fax-no: +359 2 9806431 e-mail: veni at veni.com nic-hdl: VM4-RIPE source: RIPE # Filtered 2.4. Zone Contact person: Dimitar Ganchev address: BOL.BG address: p.o.box 71 address: BG-1164 Sofia address: Bulgaria phone: +359 2 9809666 fax-no: +359 2 9806431 e-mail: mitko at mitko.com nic-hdl: DG7-RIPE source: RIPE # Filtered 2.5. Maintainer Object mntner: BGENUM-MNT descr: BOL.BG admin-c: VM4-RIPE tech-c: DG7-RIPE tech-c: VM4-RIPE zone-c: DG7-RIPE auth: CRYPT-PW T66H97B/4cJus referral-by: RIPE-DBM-MNT mnt-by: BGENUM-MNT mnt-nfy: mitko at mitko.com notify: mitko at mitko.com upd-to: mitko at mitko.com changed: mitko at mitko.com 20060405 source: RIPE ------ 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: From enum-request at ripe.net Thu Apr 13 15:56:31 2006 From: enum-request at ripe.net (RIPE NCC Staff) Date: Thu, 13 Apr 2006 15:56:31 +0200 Subject: [enum-announce] Fw: NCC#2006040655 [RE: [Bulgaria ENUM Mapping]] Message-ID: <200604131356.k3DDuXnV017486@cat.ripe.net> ----- Begin forwarded message ----- Date: Wed, 12 Apr 2006 16:29:37 +0200 From: To: Subject: RE: NCC#2006040655 [Bulgaria ENUM Mapping] Message-Id: <334A4109C6BEA14ABB48EBCF274A6C8A0187CB52 at MAILBOX1.blue.itu.ch> The TSB confirms that the attached request for ENUM delegation of code 359 has been authorized by the concerned national Administration and the delegation may proceed when RIPE NCC receives formal confirmation from the Director of TSB. ----------------------------------------- Richard Hill Counsellor, ITU-T SG2 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 > -----Original Message----- > From: RIPE NCC Staff [mailto:enum-request at ripe.net] > Sent: Wednesday, 05 April, 2006 16:34 > To: enum-announce at ripe.net; Hill, Richard > Subject: Fw: NCC#2006040655 [Bulgaria ENUM Mapping] > > > ----- Begin forwarded message ----- > > Date: Wed, 5 Apr 2006 16:00:21 +0300 > From: Dimitar Ganchev > To: enum-request at ripe.net > Subject: NCC#2006040655 Bulgaria ENUM Mapping > Message-Id: <200604051600.21607.mitko at bol.bg> > > > > Dear Ripe NCC Staff, > > We hereby apply for the 9.5.3.e164.arpa delegation. > > Both nameservers are located in Bulgaria > > Many thanks > > Dimitar Ganchev > BOL.BG > > > 2.1. Domain Object > > domain: 9.5.3.e164.arpa > descr: Bulgaria ENUM Mapping > admin-c: VM4-RIPE > tech-c: DG7-RIPE > tech-c: VM4-RIPE > zone-c: DG7-RIPE > nserver: ns.bol.bg > nserver: ns.bolbg.com > mnt-by: BGENUM-MNT > mnt-lower: BGENUM-MNT > changed: mitko.com > source: RIPE > > 2.2. Administrative Contact > > person: Veni Markovski > address: ISOC - Bulgaria > address: p.o.box 71 > address: BG-1164 Sofia > address: Bulgaria > phone: +359 2 9809666 > fax-no: +359 2 9806431 > e-mail: veni at veni.com > nic-hdl: VM4-RIPE > source: RIPE # Filtered > > 2.3. Technical Contact > > person: Dimitar Ganchev > address: BOL.BG > address: p.o.box 71 > address: BG-1164 Sofia > address: Bulgaria > phone: +359 2 9809666 > fax-no: +359 2 9806431 > e-mail: mitko at mitko.com > nic-hdl: DG7-RIPE > source: RIPE # Filtered > > > person: Veni Markovski > address: ISOC - Bulgaria > address: p.o.box 71 > address: BG-1164 Sofia > address: Bulgaria > phone: +359 2 9809666 > fax-no: +359 2 9806431 > e-mail: veni at veni.com > nic-hdl: VM4-RIPE > source: RIPE # Filtered > > 2.4. Zone Contact > > person: Dimitar Ganchev > address: BOL.BG > address: p.o.box 71 > address: BG-1164 Sofia > address: Bulgaria > phone: +359 2 9809666 > fax-no: +359 2 9806431 > e-mail: mitko at mitko.com > nic-hdl: DG7-RIPE > source: RIPE # Filtered > > 2.5. Maintainer Object > > mntner: BGENUM-MNT > descr: BOL.BG > admin-c: VM4-RIPE > tech-c: DG7-RIPE > tech-c: VM4-RIPE > zone-c: DG7-RIPE > auth: CRYPT-PW T66H97B/4cJus > referral-by: RIPE-DBM-MNT > mnt-by: BGENUM-MNT > mnt-nfy: mitko at mitko.com > notify: mitko at mitko.com > upd-to: mitko at mitko.com > changed: mitko at mitko.com 20060405 > source: RIPE > ------ 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: From enum-request at ripe.net Thu Apr 13 16:07:50 2006 From: enum-request at ripe.net (RIPE NCC Staff) Date: Thu, 13 Apr 2006 16:07:50 +0200 Subject: [enum-announce] Fw: NCC#2006041549 [FW: Request for delegation] Message-ID: <200604131407.k3DE7qGI017912@cat.ripe.net> ----- Begin forwarded message ----- Date: Wed, 12 Apr 2006 16:56:13 +0200 From: To: Subject: NCC#2006041549 FW: Request for delegation Message-Id: <334A4109C6BEA14ABB48EBCF274A6C8A0187CB53 at MAILBOX1.blue.itu.ch> At the request of the concerned national Administration, the delegation below has been extended until 31 December 2006. Richard Hill ----------------------------------------- Richard Hill Counsellor, ITU-T SG2 and SG4 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 4 email: tsbsg4 at itu.int > -----Original Message----- > From: Hill, Richard > Sent: Tuesday, 25 May, 2004 10:55 > To: 'enum-request at ripe.net' > Cc: 'Carsten Schiefner' > Subject: RE: Request for delegation > > > The TSB confirms that the attached request for ENUM > delegation of code 353 has been authorized by the concerned > national Administration until 30 March 2005 and the > delegation may proceed when RIPE NCC receives formal > confirmation from the Director of TSB. > > > Richard Hill > > > ----------------------------------------- > Richard Hill > Counsellor, ITU-T SG2 > 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 > > > > > > -----Original Message----- > > From: Carsten Schiefner [mailto:carsten at ripe.net] > > Sent: Thursday, 29 April, 2004 15:39 > > To: richard.hill at itu.int > > Cc: enum-announce at ripe.net > > Subject: Request for delegation > > > > > > -------- Original Message -------- > > Subject: Request for delegation > > Date: Thu, 29 Apr 2004 10:05:34 +0100 > > From: Emer McDonagh > > To: 'enum-request at ripe.net' > > > > Please see attached request from the Irish Enum Forum group for > > delegation, sent on behalf of the Forum Chair, Colm Reilly. > > > > Regards, > > > > Emer Mc Donagh > > > ------ 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: From enum-request at ripe.net Fri Apr 28 10:33:21 2006 From: enum-request at ripe.net (RIPE NCC Staff) Date: Fri, 28 Apr 2006 10:33:21 +0200 Subject: [enum-announce] Fw: NCC#2006043179 2.6.2.e164.arpa [Enum delegations for France] Message-ID: <200604280833.k3S8XN7L008667@dog.ripe.net> ----- Begin forwarded message ----- Date: Thu, 27 Apr 2006 20:42:15 +0200 From: "Jean-Pierre HENNINOT" To: Subject: NCC#2006043179 Enum delegations for France Message-Id: Dear Sir/Madam, On behalf of the French Administration and in the name of the MINEFI, I shall request the formal delegation of the Enum domain names corresponding to the French overseas departements , You will find hereunder the first template corresponding to Guadeloupe. Please check it and confirm that it is OK, before I prepare and send the other ones. I wonder wether I need to fill a maintainer object, and do not know how to fill the "auth" item Additionnally, I have to change the records related to ENUM domain name 3.3.e164.arpa (change of MINEFI internal organisation, closing of NUMEROBIS trial and of the delegation to AFNIC). What should be the best way to proceed? Can I send you a new template that would delete and replace the whole present data base informations? For the time being , we envisage the opening of commercial operations with ENUM, but this must still be decided and no date is fixed. I shall then provide in due time the related informations. But this explains the content of informations provided. Thanks for your attention Regards, Jean-Pierre Henninot Request for Guadeloupe 2.1. Domain Object domain: 2.6.2.e164.arpa descr: France in Indian Ocean org: MINEFI-Direction g?n?rale des entreprises admin-c: Jean-Pierre HENNINOT tech-c: Jean-Pierre HENNINOT zone-c: Jean-Pierre HENNINOT nserver: void sub-dom: void dom-net: void remarks: void notify: void mnt-by: Jean-Pierre HENNINOT mnt-lower: Jean-Pierre HENNINOT refer: void changed: jean-pierre.henninot at industrie.gouv.fr 20060427 source: RIPE 2.2. Administrative Contact person: Jean-Pierre HENNINOT address: MINEFI/DGE/STSI/SDRI/MSNaddress: 12, rue Villiotaddress: 75572 Paris CEDEX 12 phone: + 33(0)153449258 fax-no: + 33(0)153449002 e-mail: jean-pierre.henninot at industrie.gouv.fr org: MINEFI-Direction g?n?rale des entreprises nic-hdl: AUTO remarks: [optional] [multiple] [ ] notify: [optional] [multiple] [inverse key] mnt-by: [optional] [multiple] [inverse key] changed: jean-pierre.henninot at industrie.gouv.fr 20060427 source: RIPE2.5. Maintainer Object mntner: Jean-Pierre HENNINOT descr: Charg? de mission org: MINEFI-Direction g?n?rale des entreprises admin-c: Jean-Pierre HENNINOT tech-c: Jean-Pierre HENNINOT upd-to: jean-pierre.henninot at industrie.gouv.fr mnt-nfy: jean-pierre.henninot at industrie.gouv.fr auth: [mandatory] [multiple] [inverse key] remarks: [optional] [multiple] [ ] notify: [optional] [multiple] [inverse key] mnt-by: Jean-Pierre HENNINOT referral-by: Jean-Pierre HENNINOTchanged: jean-pierre.henninot at industrie.gouv.fr 20060427 source: RIPE 2. Database Information Please complete the following database templates. Once the delegation is granted, these objects will be registered in the RIPE Whois Database. An example of the completed database templates is presented in the appendix to this document. For more information about the RIPE Whois Database, please refer to the " RIPE Database User Manual: Getting Started". Documentation about how to complete the database templates can be found at: a.. http://www.ripe.net/perl/whois?-v+domain (for the domain object) b.. http://www.ripe.net/perl/whois?-v+person (for the person object) c.. http://www.ripe.net/perl/whois?-v+role (for the role object) d.. http://www.ripe.net/perl/whois?-v+mntner (for the mntner object) 2.1. Domain Object domain: [mandatory] [single] [primary/look-up key] descr: [mandatory] [multiple] [ ] org: [optional] [multiple] [inverse key] admin-c: [mandatory] [multiple] [inverse key] tech-c: [mandatory] [multiple] [inverse key] zone-c: [mandatory] [multiple] [inverse key] nserver: [optional] [multiple] [inverse key] sub-dom: [optional] [multiple] [inverse key] dom-net: [optional] [multiple] [ ] remarks: [optional] [multiple] [ ] notify: [optional] [multiple] [inverse key] mnt-by: [optional] [multiple] [inverse key] mnt-lower: [optional] [multiple] [inverse key] refer: [optional] [single] [ ] changed: [mandatory] [multiple] [ ] source: [mandatory] [single] [ ]Please note that although the maintainer attributes are optional, we strongly recommend using a maintainer to protect your domain object from unauthorised changes. Maintainers also protect against the unauthorised creation of objects representing sub-domains. See also 2.5. Maintainer Object. 2.2. Administrative Contact The administrative contact is typically the person responsible for the administration of the respective zone under the e164.arpa domain. person: [mandatory] [single] [lookup key] address: [mandatory] [multiple] [ ] phone: [mandatory] [multiple] [ ] fax-no: [optional] [multiple] [ ] e-mail: [optional] [multiple] [lookup key] org: [optional] [multiple] [inverse key] nic-hdl: [mandatory] [single] [primary/look-up key] remarks: [optional] [multiple] [ ] notify: [optional] [multiple] [inverse key] mnt-by: [optional] [multiple] [inverse key] changed: [mandatory] [multiple] [ ] source: [mandatory] [single] [ ] 2.3 Technical Contact The technical contact is typically the person or people responsible for the technical operations of the respective zone under the e164.arpa domain. This contact can be in the same organisation as the administrative contact or an organisation that operates the zone on behalf of the administrative organisation. person: [mandatory] [single] [lookup key] address: [mandatory] [multiple] [ ] phone: [mandatory] [multiple] [ ] fax-no: [optional] [multiple] [ ] e-mail: [optional] [multiple] [lookup key] org: [optional] [multiple] [inverse key] nic-hdl: [mandatory] [single] [primary/look-up key] remarks: [optional] [multiple] [ ] notify: [optional] [multiple] [inverse key] mnt-by: [optional] [multiple] [inverse key] changed: [mandatory] [multiple] [ ] source: [mandatory] [single] [ ] or role: [mandatory] [single] [lookup key] address: [mandatory] [multiple] [ ] phone: [optional] [multiple] [ ] fax-no: [optional] [multiple] [ ] e-mail: [mandatory] [multiple] [lookup key] trouble: [optional] [multiple] [ ] org: [optional] [multiple] [inverse key] admin-c: [mandatory] [multiple] [inverse key] tech-c: [mandatory] [multiple] [inverse key] nic-hdl: [mandatory] [single] [primary/look-up key] remarks: [optional] [multiple] [ ] notify: [optional] [multiple] [inverse key] mnt-by: [optional] [multiple] [inverse key] changed: [mandatory] [multiple] [ ] source: [mandatory] [single] [ ]2.4 Zone Contact The zone contact is typically the person or people responsible for the DNS operations of the respective zone under the e164.arpa domain. This contact can be in the same organisation as the administrative contact or an organisation that operates the DNS on behalf of the administrative organisation. person: [mandatory] [single] [lookup key] address: [mandatory] [multiple] [ ] phone: [mandatory] [multiple] [ ] fax-no: [optional] [multiple] [ ] e-mail: [optional] [multiple] [lookup key] org: [optional] [multiple] [inverse key] nic-hdl: [mandatory] [single] [primary/look-up key] remarks: [optional] [multiple] [ ] notify: [optional] [multiple] [inverse key] mnt-by: [optional] [multiple] [inverse key] changed: [mandatory] [multiple] [ ] source: [mandatory] [single] [ ] or role: [mandatory] [single] [lookup key] address: [mandatory] [multiple] [ ] phone: [optional] [multiple] [ ] fax-no: [optional] [multiple] [ ] e-mail: [mandatory] [multiple] [lookup key] trouble: [optional] [multiple] [ ] org: [optional] [multiple] [inverse key] admin-c: [mandatory] [multiple] [inverse key] tech-c: [mandatory] [multiple] [inverse key] nic-hdl: [mandatory] [single] [primary/look-up key] remarks: [optional] [multiple] [ ] notify: [optional] [multiple] [inverse key] mnt-by: [optional] [multiple] [inverse key] changed: [mandatory] [multiple] [ ] source: [mandatory] [single] [ ]2.5. Maintainer Object Database objects should be protected with a maintainer. The maintainer provides user configurable security for objects referencing it. It can help stop unauthorised changes to the database object representing the zone. The maintainer is referenced in the "mnt-by" and/or "mnt-lower" attributes of the domain object. It can also be referenced in ?person:? and ?role:? objects. The maintainer of database objects is the person or organisation responsible for creating, modifying or deleting these database objects. Multiple "mnt-by" or "mnt-lower" attributes can be included. More information on maintainers and the security options available can be found at: http://www.ripe.net/db/security.html mntner: [mandatory] [single] [primary/look-up key] descr: [mandatory] [multiple] [ ] org: [optional] [multiple] [inverse key] admin-c: [mandatory] [multiple] [inverse key] tech-c: [optional] [multiple] [inverse key] upd-to: [mandatory] [multiple] [inverse key] mnt-nfy: [optional] [multiple] [inverse key] auth: [mandatory] [multiple] [inverse key] remarks: [optional] [multiple] [ ] notify: [optional] [multiple] [inverse key] mnt-by: [mandatory] [multiple] [inverse key] referral-by: [mandatory] [single] [inverse key] changed: [mandatory] [multiple] [ ] source: [mandatory] [single] [ ]3. Submission of Request Please submit the request to . Please note that the submitted information and all communication related to your application will be publicly available at: http://www.ripe.net/enum/ ------ 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: