A Customer joins a new Registry
(C,d) joins R':
- (C,d), R' -> (C,d,R')
- CDB adds R' to record, wich now relates (C,R',d)
- DNS record stays the same (if the ISP hasn't changed) OR
- DNS record changes to point to R' or ISP'
A Customer Sits on a Domain-Name
- tick, tick, tick....
A Registry Drops a Customer
- (C,R,d) -> (R,d) C
- CDB drops C, record relates R,d
- Question:
- DNS data removed?
- DNS data points to R?
- DNS point disappears?
- DNS points to hyperspace?
A Registry Sits on a Domain-Name
- tick...
A Registry Sells a Name
- C' (R,d) --> (C',R,d)
- CDB adds C' to record, relates all three again
- DNS data changes
- C is nameless
A Registry Drops a Customer and Domain
- (C,R,d) -> R (C,d)
- CDB takes R out of record, record relates C,r
- Question:
- DNS data stays same?
- points to R?
- points to C?
- is removed?
A Customer Loses His Name
presumably as a result of a lawsuit...- (C,R,d) -> (C,R) d
- CDB takes d out of record, record relates only C and R
- DNS data removed
A Customer Gives up His Registry and Domain
- (C,R,d) -> C, R, d
- CDB takes out it's record
- domain name is now available for reclamation
- DNS data removed
Conclusions
The intention is to show what actions preserve some selected desirable policies, by enumerating the actions, examining them and then pointing a finger at the bad ones and saying ``begone''. For example, one could use the example policy decisions I used for the diagram and decide to make the arc labelled ERR disappear by making a customer leading a (registry,domain) pair turn into a complete disassociation of all three. (By the way, that's a terrible idea!) Similarly, one could define the C (R,d) out of existence in favor of (C,d) R so long as there was a timeout state which would take the customer to the dissolution state if he didn't register wit somebody. And so on. Dave Collier-Brown Description reference: Tag list:- bullet
- second bullet
definition list:- title>/DT>
- data
- title 2
- data 2