Re: [ire] Variant Domain Names

James Mitchell <james.mitchell@ausregistry.com.au> Tue, 09 April 2013 01:02 UTC

Return-Path: <james.mitchell@ausregistry.com.au>
X-Original-To: ire@ietfa.amsl.com
Delivered-To: ire@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C7CCF21F8E73 for <ire@ietfa.amsl.com>; Mon, 8 Apr 2013 18:02:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.808
X-Spam-Level:
X-Spam-Status: No, score=-1.808 tagged_above=-999 required=5 tests=[AWL=0.086, BAYES_00=-2.599, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iKPfM5vTAVBW for <ire@ietfa.amsl.com>; Mon, 8 Apr 2013 18:02:58 -0700 (PDT)
Received: from mx01.ausregistry.net.au (mx01.ausregistry.net.au [202.65.15.41]) by ietfa.amsl.com (Postfix) with ESMTP id 3203C21F8E63 for <ire@ietf.org>; Mon, 8 Apr 2013 18:02:56 -0700 (PDT)
Received: from off-win2003-01.stkildard.vic.ausregistry.com.au (HELO off-win2003-01.ausregistrygroup.local) ([10.30.1.3]) by iron01.off08.stkildard.vic.ausregistry.com.au with ESMTP; 09 Apr 2013 11:02:54 +1000
Received: from off-win2003-01.ausregistrygroup.local ([10.30.1.3]) by off-win2003-01.ausregistrygroup.local ([10.30.1.3]) with mapi; Tue, 9 Apr 2013 11:02:48 +1000
From: James Mitchell <james.mitchell@ausregistry.com.au>
To: Bhadresh Modi <bmodi@afilias.info>, "ire@ietf.org" <ire@ietf.org>
Date: Tue, 9 Apr 2013 11:02:50 +1000
Thread-Topic: [ire] Variant Domain Names
Thread-Index: Ac40vfMvCpCvYxAtSYimIAnUYjNwsw==
Message-ID: <CD897BCC.782A7%james.mitchell@ausregistry.com.au>
In-Reply-To: <CAMi4TxzsnHghFM2dLNp48B2TFE8PFsD2dKrtMJQRktE2zKGs=g@mail.gmail.com>
Accept-Language: en-US, en-AU
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.3.2.130206
acceptlanguage: en-US, en-AU
x-kse-antivirus-interceptor-info: scan successful
x-kse-antivirus-info: Clean
Content-Type: multipart/alternative; boundary="_000_CD897BCC782A7jamesmitchellausregistrycomau_"
MIME-Version: 1.0
Subject: Re: [ire] Variant Domain Names
X-BeenThere: ire@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Internet Registration Escrow discussion list." <ire.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ire>, <mailto:ire-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ire>
List-Post: <mailto:ire@ietf.org>
List-Help: <mailto:ire-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ire>, <mailto:ire-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Apr 2013 01:02:58 -0000

Apologies, I was intending to use the term "activated". I have "allocated" on my mind from the launch discussions..

Thanks,
James

From: Bhadresh Modi <bmodi@afilias.info<mailto:bmodi@afilias.info>>
Date: Tuesday, 9 April 2013 3:06 AM
To: "ire@ietf.org<mailto:ire@ietf.org>" <ire@ietf.org<mailto:ire@ietf.org>>
Subject: Re: [ire] Variant Domain Names

More precise terms are certainly helpful, I think the main point is that the current set of "blocked" and "withheld" as shown in the draft is insufficient.

Perhaps it makes sense to simply use the same terms with the same definitions from the IDN TLD project that Andrew provided.

Regards,
Bhadresh

On Mon, Apr 8, 2013 at 12:49 PM, Andrew Sullivan <ajs@anvilwalrusden.com<mailto:ajs@anvilwalrusden.com>> wrote:
I have no idea how those terms got adopted, but I'd like to point out
the distinctions that were made by the variant issues project/IDN TLD
project:

Delegated: actually in a zone with an SOA and parent NS RRset.

Activated: in the DNS somehow.  (Delegated is a species of activated.
For instance, a DNAME would be activated but not delegated.)

Allocated: someone has administrative control over the name, but it is
not activated.  For instance, any domain on Hold in EPP would be
allocated.

Blocked: nobody is allowed to register the name.  For instance, in
.com nobody may register the label example (so example.com<http://example.com> is
blocked).

I think these distinctions are all extremely useful.

On Mon, Apr 08, 2013 at 12:07:18PM -0400, Bhadresh Modi wrote:
> I agree - we were using the "allocated" value in the previous revision to
> differentiate between IDN variants that simply blocked registration and
> variants that would actual resolve similar to the original domain name.
>  With the omission of this value there is no longer any way to express this.
>
> Regards,
> Bhadresh
>
>
> On Mon, Apr 8, 2013 at 3:29 AM, James Mitchell <
> james.mitchell@ausregistry.com.au<mailto:james.mitchell@ausregistry.com.au>> wrote:
>
> > Gustavo,
> >
> > I would like the nameState of NNDNs to include "activated". The
> > "allocated" value was in revision –01, however seems to have disappeared
> > without reason? Adding "allocated" would make the NNDN consistent with the
> > text in Section 6 that states that either domain objects or NNDNs may be
> > used to represent variants.
> >
> > Also, the NNDN <crDate> should be optional as some registries may not
> > track the creation date of reserved list entries.
> >
> > Regards,
> > James
> >
> >
> > _______________________________________________
> > ire mailing list
> > ire@ietf.org<mailto:ire@ietf.org>
> > https://www.ietf.org/mailman/listinfo/ire
> >
> >

> _______________________________________________
> ire mailing list
> ire@ietf.org<mailto:ire@ietf.org>
> https://www.ietf.org/mailman/listinfo/ire


--
Andrew Sullivan
ajs@anvilwalrusden.com<mailto:ajs@anvilwalrusden.com>
_______________________________________________
ire mailing list
ire@ietf.org<mailto:ire@ietf.org>
https://www.ietf.org/mailman/listinfo/ire