To:
Rick Wesson <wessorh@ar.com>
cc:
shollenbeck@verisign.com, "'ietf-provreg@cafax.se'" <ietf-provreg@cafax.se>, ietf-not43@lists.verisignlabs.com, iesg@ietf.org, brunner@nic-naa.net
From:
Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net>
Date:
Wed, 23 Oct 2002 12:21:54 -0400
Content-ID:
<16714.1035390114.1@nic-naa.net>
In-Reply-To:
Your message of "Wed, 23 Oct 2002 08:34:31 PDT." <Pine.LNX.4.33.0210230819410.17489-100000@flash.ar.com>
Sender:
owner-ietf-provreg@cafax.se
Subject:
Re: Last-Verified Date Contact Element
Rick, > I propose that we add a "Last-Verified" date element to the contact object > so that registries/registrars may express the last time the object was > verified. Since contacts have no expiration date and the "last-modified" > date is irreverent to verification. What does "verified" mean? > I believe that this will aid in identifying old, stale and irreverent data > within a registry and if the element is published in CRISP or whois to the > community in general. How? Why? What prevents a client providing some authInfo from also attempting to set upID and set or modify upDate? Eric