Re: [Crisp] new status for DREG2

Alexander Mayrhofer <alexander.mayrhofer@enum.at> Tue, 28 March 2006 10:43 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FOBfy-0005Hq-Ni; Tue, 28 Mar 2006 05:43:50 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FOBfx-0005Hl-O9 for crisp@ietf.org; Tue, 28 Mar 2006 05:43:49 -0500
Received: from pahula.nona.net ([193.80.224.123] helo=kahua.nona.net) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FOBfu-00045d-EF for crisp@ietf.org; Tue, 28 Mar 2006 05:43:49 -0500
Received: from [10.10.0.63] (nat.labs.nic.at [::ffff:83.136.33.3]) (AUTH: PLAIN axelm, TLS: TLSv1/SSLv3,256bits,AES256-SHA) by pahula with esmtp; Tue, 28 Mar 2006 12:43:44 +0200 id 00004003.44291360.0000411C
Message-ID: <44291355.4000508@enum.at>
Date: Tue, 28 Mar 2006 12:43:33 +0200
From: Alexander Mayrhofer <alexander.mayrhofer@enum.at>
Organization: enum.at GmbH
User-Agent: Thunderbird 1.5 (Windows/20051201)
MIME-Version: 1.0
To: Andrew Newton <andy@hxr.us>
Subject: Re: [Crisp] new status for DREG2
References: <6CEB55DE-2DD5-463B-BE15-145B241D8DCF@hxr.us>
In-Reply-To: <6CEB55DE-2DD5-463B-BE15-145B241D8DCF@hxr.us>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
Cc: crisp@ietf.org
X-BeenThere: crisp@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Cross Registry Information Service Protocol <crisp.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/crisp>, <mailto:crisp-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:crisp@ietf.org>
List-Help: <mailto:crisp-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/crisp>, <mailto:crisp-request@ietf.org?subject=subscribe>
Errors-To: crisp-bounces@ietf.org

Andrew Newton wrote:
> I had a meeting with an sTLD operator last week where it was brought to
> my attention that they would like to mark domains with a status
> indicating compliance with regulations not directly related to the
> actual domain registration process... as in, they have conducted a
> compliance check and have found that a domain holder's web site meets
> certain accessibility requirements or internationalization requirements,
> etc...
> 
> To do what they would like, I think we should add a <compliant:> and
> <noncompliant> enhanced status to the base enhanced status set in
> DREG2.  The substatus and related authority would indicate the type of
> compliance.

That looks to me like some "validation status" - might be very similar to
what is used in ENUM.

Any chance to recycly valdationEvents from EREG here?

cheers

alex

_______________________________________________
Crisp mailing list
Crisp@ietf.org
https://www1.ietf.org/mailman/listinfo/crisp