[Ietf-not43] status in Domain

[Andrew Newton]

Marcos Sanz/Denic wrote:
>>The change as described in part two:
>>
>><status>
>><registrarLock appliedDate="11/15/03" .../>
>><assignedAndActive appliedDate="11/10/03" .../>
>><registrarLock appliedDate="11/09/03" .../>
>></status>
> 
> 
> I don't feel comfortable with this possibility. The service wasn't 
> conceived to supply historical information and it may be that we are 
> missing the scope if we walk down that way.

I should note that this attribute would be optional.  There is no amount 
of specifying that can help if the operator doesn't have the data.

After being slapped about by a couple of individuals here at the IETF 
meeting, I've come to the conclusion that this feature should only be 
included if there is a stronger use-case than "it would be a neat feature."

-andy