Re: [Crisp] new status for DREG2

Andrew Sullivan <andrew@ca.afilias.info> Tue, 21 March 2006 16:49 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FLk2g-00030K-NJ; Tue, 21 Mar 2006 11:49:10 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FLk2f-00030F-4g for crisp@ietf.org; Tue, 21 Mar 2006 11:49:09 -0500
Received: from vgateway.libertyrms.info ([207.219.45.62] helo=mail.libertyrms.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FLk2d-0007K5-UH for crisp@ietf.org; Tue, 21 Mar 2006 11:49:09 -0500
Received: from andrew-vpn.int.libertyrms.com ([10.1.7.6] helo=dhcp-wireless-129-46.ietf65.org) by mail.libertyrms.com with esmtp (Exim 4.22) id 1FLk2c-0000sg-6g for crisp@ietf.org; Tue, 21 Mar 2006 11:49:07 -0500
Received: by dhcp-wireless-129-46.ietf65.org (Postfix, from userid 1019) id 281FE1943AD; Tue, 21 Mar 2006 11:49:17 -0500 (EST)
Date: Tue, 21 Mar 2006 11:49:17 -0500
From: Andrew Sullivan <andrew@ca.afilias.info>
To: crisp@ietf.org
Subject: Re: [Crisp] new status for DREG2
Message-ID: <20060321164915.GA1244@afilias.info>
References: <6CEB55DE-2DD5-463B-BE15-145B241D8DCF@hxr.us>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <6CEB55DE-2DD5-463B-BE15-145B241D8DCF@hxr.us>
User-Agent: Mutt/1.5.11
X-SA-Exim-Mail-From: andrew@ca.afilias.info
X-SA-Exim-Scanned: No; SAEximRunCond expanded to false
X-Spam-Score: 0.5 (/)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22
X-BeenThere: crisp@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Andrew Sullivan <andrew@ca.afilias.info>
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

On Tue, Mar 21, 2006 at 10:16:07AM -0500, 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...

Hmm.  I've seen proposed a case where the policy is actually
many-valued: compliant, noncompliant, and N/A, for instance.
Trademarks are a good case: if the domain is created during one
period, the trademark has either been checked or not, but if the
domain is created after that period, nobody cares about the
trademark.  I suppose one could argue that the "don't care" case is
compliant anyway, but what about a <policy:> status with <name:>
substatus and <compliance:> substatus?  Maybe that's overengineering.

A


-- 
----
Andrew Sullivan                         204-4141 Yonge Street
Afilias Canada                        Toronto, Ontario Canada
<andrew@ca.afilias.info>                              M2P 2A8
                                        +1 416 646 3304 x4110


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