Re: [Crisp] new status for DREG2

Andrew Newton <andy@hxr.us> Tue, 21 March 2006 19:21 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FLmQI-0005Zp-Lx; Tue, 21 Mar 2006 14:21:42 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FLmQG-0005Zk-PI for crisp@ietf.org; Tue, 21 Mar 2006 14:21:41 -0500
Received: from zeke.hxr.us ([69.31.8.124] helo=zeke.ecotroph.net) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FLmQF-0004zC-Hw for crisp@ietf.org; Tue, 21 Mar 2006 14:21:40 -0500
Received: from [130.129.130.179] ([::ffff:130.129.130.179]) (AUTH: PLAIN anewton, SSL: TLSv1/SSLv3,128bits,RC4-SHA) by zeke.ecotroph.net with esmtp; Tue, 21 Mar 2006 14:20:46 -0500 id 015880B0.4420520E.00007D91
In-Reply-To: <20060321164915.GA1244@afilias.info>
References: <6CEB55DE-2DD5-463B-BE15-145B241D8DCF@hxr.us> <20060321164915.GA1244@afilias.info>
Mime-Version: 1.0 (Apple Message framework v746.2)
Content-Type: text/plain; charset="US-ASCII"; delsp="yes"; format="flowed"
Message-Id: <6382DC48-2654-472C-8A5E-8DB4A8348E2D@hxr.us>
Content-Transfer-Encoding: 7bit
From: Andrew Newton <andy@hxr.us>
Subject: Re: [Crisp] new status for DREG2
Date: Tue, 21 Mar 2006 14:21:36 -0500
To: Andrew Sullivan <andrew@ca.afilias.info>
X-Mailer: Apple Mail (2.746.2)
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 97adf591118a232206bdb5a27b217034
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

On Mar 21, 2006, at 11:49 AM, Andrew Sullivan wrote:
> Hmm.  I've seen proposed a case where the policy is actually
> many-valued: compliant, noncompliant, and N/A, for instance.

I'm a little puzzled about N/A.  Wouldn't that just be the absence of  
any compliance/noncompliance status?

> 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.

I was thinking of having it simply derive from the regular enhanced  
status type.  So it would look like this:

<noncompliant>
   <description language="en">
     Scan detected multiple compliance issues.
   </description>
   <substatus authority="tld.example">
     COMPLIANCE-CODE-X
   </substatus>
   <substatus authority="tld.example">
     COMPLIANCE-CODE-Y
   </substatus>
</noncompliant>

Perhaps changing the element names to <policyCompliance> and  
<policyNoncompliance>.

-andy

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