
EPP Repository Identifiers - per [RFC3730]

(last updated 2007-12-10)

Registration procedures:
Until the IANA requests or implements an automated process for the
registration of these identifiers, any specifications must make that
request part of the IANA considerations section of their respective
documents.  A request must be in the form of the following template:

ID
  The repository identifier to be registered by IANA. If the
  registrant is requesting that the IANA assign an ID then this
  field should be specified as "Please assign".  IANA will then
  assign an identifier derived from provided contact information,
  such as by using an organizational name.  Formatting
  requirements:

  * 1 character minimum length
  * 80 characters maximum length
  * String MUST contain only letters or digits as defined by XML 1.0
    or the "_" (#x005F) character.  XML letter and digit characters 
    are defined here:

    http://www.w3.org/TR/2000/REC-xml-20001006#CharClasses

  The registration request must contain both the requested string
  and the hexadecimal representation of the characters present in
  the string, formatted according to the XML character classes.
  For example, the string "foo" would be identified as follows:

  ID: foo, #x0066 #x006F #x006F

Registrant Contact
  The individual/organization that is the registration contact for
  the component being registered.  Ideally, this will include the
  name and pertinent physical and network contact information.

Requests MAY be sent directly to IANA without a formal specification.  
The registry itself should be a list of registered strings.
No review beyond IANA review is required.


EPP Repository ID                                            Reference/Contact                                        Registration Date
-----------------------------------------------------------  -------------------------------------------------------  -----------------
ENUMAT, #x0045 #x004E #x0055 #x004D #x0041 #x0054            enum.at GmbH 
                                                             <office&enum.at>
MX, #x004D #x0058                                            Network Information Center México
                                                             <dtic&nic.mx>
NAME, #x004E #x0041 #x004D #x0045                            The Global Name Registry Ltd.
                                                             <iana&gnr.com>
VRSN, #x0056 #x0052 #x0053 #x004E                            VeriSign Naming and Directory Services
                                                             <info&verisign-grs.com>
IENUM43, #x0049 #x0045 #x004e #x0055 #x004d #x0034 #x0033    enum.at GmbH
                                                             <office&enum.at>  
SWITCH, #x0053 #x0057 #x0049 #x0054 #x0043 #x0048            SWITCH - Teleinformatikdienste für Lehre und Forschung
                                                             <info&switch.ch>
DOMICILIUM, #x0044 #x004F #x004D #x0049 #x0043 #x0049        Domicilium (IOM) Ltd
#x004C #x0049 #x0055 #x004D                                  <padcock&domicilium.com>
CNIC, #x0043 #x004E #x0049 #x0043                            CentralNic Ltd
                                                             <gavin.brown&centralnic.com> 
NORID, #x004E #x004F #x0052 #x0049 #x0044                    UNINETT Norid AS                                         2007-12-10
                                                             <info&norid.no>

References
----------
[RFC3730]  S. Hollenbeck, "Extensible Provisioning Protocol (EPP)",
           RFC 3730, March 2004.


(registry created 2004-10-26)
		  
[]


