<<<
Chronological Index
>>> <<<
Thread Index
>>>
[registrars] [Ietf-not43] Last-Verified Date Contact Element (fwd)
FYI
A note I posted to the IESG, provreg and the crips working groups. I
welcome registrars comments on a proposal to add a "last-verified-date"
to the epp specification.
I have not attempted to qualify or define "verification" as the discussion
is about protocols not policy and different registries may interpret
verification differently.
I am interested to hear the registrars view point on the utility of a
last-verified element in registrant data. I look forward to your input.
best,
-rick
---------- Forwarded message ----------
Date: Wed, 23 Oct 2002 08:34:31 -0700 (PDT)
From: Rick Wesson <wessorh@ar.com>
To: shollenbeck@verisign.com
Cc: "'ietf-provreg@cafax.se'" <ietf-provreg@cafax.se>,
ietf-not43@lists.verisignlabs.com, iesg@ietf.org
Subject: [Ietf-not43] Last-Verified Date Contact Element
Scott && IESG,
I realized that there is an item we have overlooked in the wg. In private
conversations, myself and others have noted that there is no way to
identify the last time a contact object was verified.
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.
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.
I know it is late in the game for identifing issues with the epp proposals
so I have CCed the IESG.
-rick
_______________________________________________
Ietf-not43 mailing list
Ietf-not43@lists.verisignlabs.com
http://lists.verisignlabs.com/mailman/listinfo/ietf-not43
<<<
Chronological Index
>>> <<<
Thread Index
>>>
|