To:
"Bernie Hoeneisen" <bhoeneis@switch.ch>, <ietf-provreg@cafax.se>
From:
"Hollenbeck, Scott" <shollenbeck@verisign.com>
Date:
Mon, 20 Nov 2006 08:52:33 -0500
Content-class:
urn:content-classes:message
Sender:
owner-ietf-provreg@cafax.se
Thread-Index:
AccMpsGgzD9KXsiSTeS4IzBuIG5gDwAA+MtA
Thread-Topic:
[ietf-provreg] Question concerning Status clientRenewProhibited
Subject:
RE: [ietf-provreg] Question concerning Status clientRenewProhibited
> -----Original Message----- > From: owner-ietf-provreg@cafax.se > [mailto:owner-ietf-provreg@cafax.se] On Behalf Of Bernie Hoeneisen > Sent: Monday, November 20, 2006 7:58 AM > To: ietf-provreg@cafax.se > Subject: [ietf-provreg] Question concerning Status > clientRenewProhibited > > Hi! > > We are currently designing our EPP implementation, and have some > questions concerning the status 'clientRenewProhibited': > > Does anybody use the status 'clientRenewProhibited'? > What purpose(s) is it used for? > > Was there a specific purpose in mind for > 'clientRenewProhibited' while > standardizing the EPP Protocol, or was it just for > completeness / possible > future use? Partially for completeness, but also for the real possibility that renewal needs to be disallowed for some reason. It helps lock down the domain against an unauthorized renewal, for example. -Scott-