RE: "status" element in <domain:info> response

["Liu, Hong" <Hong.Liu@neustar.biz>]

Thanks, Scott. That will do it.

-----Original Message-----
From: Hollenbeck, Scott [mailto:shollenbeck@verisign.com]
Sent: Wednesday, September 11, 2002 2:20 PM
To: 'Liu, Hong'; 'ietf-provreg@cafax.se'
Subject: RE: "status" element in <domain:info> response


> <HL>
> Thanks for the clarification. If at least one status tag 
> should exist, then
> the example on page 15 as well as the 
> domain_info_unauth_result.xml in the
> example package need to be fixed to include at least one status value.
> </HL>

Sigh, you found the spot I forgot that explains why it's OPTIONAL and zero
is possible.  Back to zero being the minimum.

> <HL>
> You are right, not all 17 values are allowed to co-exist at 
> the same time
> according to section 2.3. But I am having difficulty 
> understanding how 12 is
> derived from the complex rules in section 2.3. Could you 
> explain that to me?
> Thanks! 
> </HL>

The "pending" status values can't be set if the corresponding "prohibited"
status values are set; all of the "prohibited" values can be set at the same
time.  An object also can't be in both "ok" and any other status at the same
time.  The combination with the greatest number of members is thus:

clientDeleteProhibited
clientHold
clientRenewProhibited
clientTransferProhibited
clientUpdateProhibited
inactive
serverDeleteProhibited
serverHold
serverRenewProhibited
serverTransferProhibited
serverUpdateProhibited

That's 11.  OK, so I missed by one ;-).  I'll check the contact and host
combinations again to be sure they're right, too.

-Scott-