|
|||||||||||
|
|||||||||||
|
|||||||||||
|
|
Follow this link to
the e-mail application form.
This page describes the most important parameters of the
e-mail application form. The respective parts of the template are shown
within a colored area, with helpful comments located below them.
Self-explanatory parameters
like email will not be mentioned here.
The form is divided into multiple sections:
Introduction (section 0)#----------------------------------------------------------------------- # | | # | knipp | Knipp Medien und Kommunikation GmbH # -------
All the lines beginning with # are comments and can be ignored.
These lines are only used to improve structure and readability.
The same is true for blank lines. They are only used to clearly
arrange the form and can be added or deleted arbitrarily.
section: 0
The application form is divided into several sections.
Each section forms a chapter by itself and is separated
from the other chapters by the
key section. Do not remove these lines.
doc-id: appli-en-tel.txt
version: 4.0.3
Is required for further processing by Knipp. Please do not delete.
reference:
You can insert any text you like here. This text will be quoted in all of
the responses of our system. This allows for an easy
recognition and classification of your applications by your robots,
if you want to automatically process our responses.
You might want to use this field to indicate reference numbers
of your customers, for example, or a contract number, etc.
Registration data (section 1) section: 1
mode:
domain:
comment:
authinfo:
new-authinfo:
With the
mode-parameter
you can normally define if you wish to perform a new registration,
a transfer from another registrar,
an update, or a deletion.
At this point of time, however, only new registrations are possible for .tel (
mode: new)
Next to domain,
the complete domain name has to be given.
For example:
domain: my-name.tel.
Only one domain name can be given per e-mail application form.
The field comment can be used to save a
free-text comment about this domain.
authinfo is
some kind of password, which is required for changing the registrar of a domain.
It thus protects you against unauthorized persons initiating such an operation.
You can choose it freely during the registration of a new domain.
It must consist of at least 6 and a maximum of 16 characters.
Example: authinfo: this is secret.
If at some time you want to change the sponsoring
registrar (CTSR), you
have to know the authinfo for the respective
domain and to name it in this field. This proves that you are authorized to
request the change. At the same time, you have to constitute a new password
by using the new-authinfo-field.
This specification is mandatory. The same rules concerning the number of
characters apply for new-authinfo, of course,
since it becomes the authinfo for the
domain after the change.
 Important:
The authinfo-fields may not be used for deletions
(i.e. mode: delete).
Important:
The new-authinfo-field is only neccessary to
change the registrar and may not be used for updates or for the registration of a new domain!
telnic-phase: landrush
telnic-whois-type:
telnic-whois-publish:
telnic-phase: landrush
This field has only to be specified for Landrush registrations. If you
want to preregister the domain name for a registration directly after the
start of the live operation of .tel, do not specify anything here or omit the
field as a whole (as it is the case in the current template).
telnic.whois.type:
Specifies whether the domain is held by a corporation ("legal") or
individual ("natural").
telnic.whois.publish:
Specifies whether to publish social data to the .tel Whois for an
individually owned domain ("true") or not ("false"). This must be
set to "true" for domains held by corporations.
Domain holder (section 2) person:
organization:
The registrant is the designated holder of the domain.
This can be a natural person or a legal person.
In case of a natural person, only person
has to be filled out. If the holder is a legal person (e.g. a company),
you have to specify it at organization in any case.
Nevertheless, a contact person must also be given at
field person
address-1:
address-2:
address-3:
postal-code:
city:
state:
country:
The parameter address-1 is
intended for the street address. Filling this field is mandatory.
address-2
and
address-3
can be used for additional entries (for the zip-code or other add-ons).
The postal-code-parameter (mandatory field)
is intended for the zip/postal code, while city
(mandatory as well) holds the name of town.
state
(Region, Area, Province, State) is an optional parameter, as opposed to
country. The country parameter is required to
hold the international country code representation according to ISO-3166,
like »DE«, »AT«, or »CH«. This field is case-insensitive (so using »de« or »De«
will work as well), but it may not contain periphrases like »Germany« or
»Switzerland«!
phone:
fax:
Specifying a phone number in field phone is
mandatory. The number has to be given in the following format:
+CCC.NNNNN, where CCC represents the country code
(e.g. 49 for Germany)
and NNNN is the actual number including the area code.
Using a plus sign in front of the country code and a dot
to separate it from the rest of the number is
mandatory, too. Example: +49.8912345678
If a fax number is available, it can be specified at
fax.
The format has to be the same as in
phone.
authinfo:
Analogue to the
authinfo-field in
section 1 (Registration data).
This parameter might become necessary in the future.
Independently of the actual usage at the registry,
this field has to be filled out by now already.
handle:
handle
provides an alternative way to specify contact data.
With every successful registration of a domain, a handle is being created for
every contact provided during the registration process.
Once you have a handle for a set of contact data, you don't have to manually
fill out the fields if you want to use the same data again. Instead, it
suffices to specify the appropriate handle in this field. This saves you
a lot of typing. If you fill out the fields and enter a handle at the
same time, the values specified in the fields will be ignored and those
from the handle will be taken instead.
Example:
handle: C14549-TEL.
Important:
The different top level domains each require their own set of handles.
For example, .info handles can not be used for .asia domains, even if both
handles specify the same contact data!
Administrator (section 3)
The administrator is an authorized person who is acting on behalf of the
registrant. He can, for example, request modifications of a domain.
The administrator and the holder of a domain
can be the same person.
The administrator can be a legal department or an external office, as it is
often the case with larger companies.
person:
organization:
address-1:
address-2:
address-3:
postal-code:
city:
state:
country:
phone:
fax:
email:
authinfo:
handle:
The parameters have to be filled out in the same way as described for the
domain holder (or by specifying a handle).
Technical contact (section 4)
The technical contact is the contact person for technical concerns.
He is responsible for operating the name servers, for instance.
person:
organization:
address-1:
address-2:
address-3:
postal-code:
city:
state:
country:
phone:
fax:
email:
authinfo:
handle:
The parameters have to be filled out in the same way as described for the
domain holder (or by specifying a handle).
Billing contact (section 5)
The billing contact is the person who responsible for the payment
within an organization. This distinction is reasonable in larger companies,
although in the majority of cases the billing contact is identical to the
domain holder.
person:
organization:
address-1:
address-2:
address-3:
postal-code:
city:
state:
country:
phone:
fax:
email:
authinfo:
handle:
The parameters have to be filled out in the same way as described for the
domain holder (or by specifying a handle).
Technical data (section 6)section: 6 telnic-th-username: telnic-th-weblink:
Owners of a .tel domain need an account at a TelHosting system where they
can manage the data published within their domain. Therefore, the intended user
name for this system has to be specified as
telnic-th-username.
Optionally, a link to a web page can be given as
telnic-th-weblink, which will then be used for
an initial (public) entry within the domain. If this field is omitted, a generic
initial entry will be generated. Note that .tel domains need such a public entry
to become (and stay) productive due to the registry's policy.
Important:
Just like before during the Sunrise phase, no name servers may currently be
given in section 6. The correct name servers will later be filled automatically
by the system.
Giving lock: yes offers the possibility to automatically
set a lock on a domain after a successful registration or a successful transfer.
By omitting this field (or by giving lock: no, respectively)
no lock will be set as usual. (This option is not available for .de and .eu domains, since
neither DENIC nor EURid support a lock function on the Registry level.)
Customer data (section 7) customer-no:
password:
Please provide your 5-digit customer number
at customer-no, and your
e-mail password in field password.
(Attention: Your e-mail password is required here, not the one
used for the web interface).
Each employee of a company receives his own unique access data.
This ensures that the DRS can identify which person within your
company initiated which process.
Registration terms and conditions (section 8)section: 8 accept-agb:http://www.knipp.de/.../agb/domains.do accept-registry:http://www.knipp.de/.../reg-rev20060515a-en.txt
These fields have to be included without any changes.
Please note the following information concerning this
e-mail application form:
|
||||||||||||||||||||||||||||||||||||
|
|