[arabic-vip] FW: [Integrated-vip] Possible actions on IDN variant names

[Sarmad Hussain]

FYI and for your feedback.

Regards,
Sarmad

-----Original Message-----
From: integrated-vip-bounces at icann.org
[mailto:integrated-vip-bounces at icann.org] On Behalf Of Francisco Arias
Sent: Saturday, November 05, 2011 6:46 AM
To: integrated-vip at icann.org
Subject: [Integrated-vip] Possible actions on IDN variant names

Team,

Following our meeting on Wednesday see below (also attached if you prefer
Word) the definitions for the six possible high-level actions that can be
taken once a variant has been identified. I checked the definitions
available on the case study reports and try to harmonize them. Please check
and comment.

 
1. Block:
An administrative action by a registry over a particular string (a potential
domain name) rendering such string unavailable for allocation to anyone.
 

2. Reserve:
To set aside a name for potential allocation to a particular entity (TLD
registry in the case of the root). The name is not yet allocated, but could
be (to that particular entity) if/when certain conditions are met.
 

3. Allocate:
It is the first step on the way to activation. The registry makes an
administrative association between a string and some entity that requests
the string, making the string a potential label inside the zone, and a
candidate for activation. Allocation alone does not affect the DNS at all.
 

4. Delegate:
The act of entering parent-side NS (name server) records in a DNS zone,
thereby creating a subordinate namespace with its own SOA (start of
authority) record. See RFC 1034 for detailed discussion of how the DNS name
space is broken up into zones.
 

5. Mirror:
To activate two or more domain names such that for a namespace starting with
one, the namespace starting with the other is isomorphic to the first,
subject to the usual DNS loose consistency strictures. Currently, there are
two different techniques for this. The first is aliasing: CNAME, DNAME, and
other such techniques that redirect a name or a tree, effectively
substituting one label for another during DNS lookup. The second is by using
provisioning constraints, such that an underlying provisioning system always
effects a change in all of the names whenever that change is effected in one
of the names.
 

6. Activate:
It is the act of entering parent-side DNS records in a zone (e.g., NS,
DNAME, CNAME, NAPTR) making the name entered resolvable in the DNS. (Note
that delegating a name implies activating it, but activation does not
necessarily imply delegation.)
 


It should be noted that IDN variants are necessarily domain names
themselves. 


__

Francisco.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: Possible actions on variant domain names.doc
Type: application/x-msword
Size: 31744 bytes
Desc: not available
Url : http://mm.icann.org/pipermail/arabic-vip/attachments/20111106/714af215/Possibleactionsonvariantdomainnames-0001.doc