[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]


To: "'Daniel Manley'" <dmanley@tucows.com>
Cc: ietf-provreg@cafax.se
From: "Hollenbeck, Scott" <shollenbeck@verisign.com>
Date: Sat, 19 Jan 2002 09:12:16 -0500
Sender: owner-ietf-provreg@cafax.se
Subject: RE: <poll> and object changes (was authInfo in <info> commands)

Dan,

Text describing the notification needs you mentioned below is going into the
next version of the documents.

-Scott-

> -----Original Message-----
> From: Daniel Manley [mailto:dmanley@tucows.com]
> Sent: Friday, January 18, 2002 10:53 PM
> To: Ed Rahn
> Cc: asbjorn.rrp@theglobalname.org; ietf-provreg@cafax.se
> Subject: <poll> and object changes (was authInfo in <info> commands)
> 
> 
> It's my philosophy (and perhaps this should go into the 
> drafts) that an 
> EPP registry should/must create a notification to sponsoring 
> client of 
> an object when that object is modified without that client's direct 
> involvement.  So a domain registrar, for example, would be 
> notified of 
> changes in the status of a transfer initiated by the other 
> registrar or 
> by the registry's auto-approve/deny mechanisms.  Actually, the 
> requesting registrar should also be notified if the transfer 
> is denied 
> by the losing registrar or auto-denied/approved by the registry.
> 
> Other situations where a registry would notify a registrar of 
> changes to 
> objects it owns:  auto-renewals, object (domain) expiry, changes 
> initiated by the registry's support staff, etc...
> 
> this way, the owning registrar (with regular polling, or with 
> pushing) 
> can count on always being in the know of changes to its 
> objects in the 
> registry.
> 
> Dan

Home | Date list | Subject list