|HOME | HANDBOOK | FACTSHEETS | FAQs | RESOURCES | REGISTRATION AGENCIES | NEWS | MEMBERS AREA|
DOI Proxy Implementation Policy
This policy addresses RA implementation of the common proxy server doi.org, and the implementation of proxy-like services that perform URL resolution via HTTP under a domain name that is not doi.org.
1. Every RA is welcome to use the doi.org set of web-to-handle proxy servers run by the IDF to express their DOIs in URL form or as part of any other service they provide to their customers.
2. Every RA is welcome to contribute to the set of doi.org proxy servers by running one or more instances of the common proxy server implementation. Each RA that chooses to do so must agree to run the current version of the software and cooperate in the statistics gathering process which counts the total number of DOI resolutions through the proxy servers on a monthly basis. The IDF reserves the right to limit the total number of doi.org proxy instances should that number grow beyond what is useful and become too cumbersome to manage.
3. RAs may choose instead to run a proxy-like service in which DOIs are embedded in URLs for resolution via HTTP under a domain name that is not doi.org, e.g., doi.RA-name.org. RAs choose to do this for a variety of reasons, including that although the service is basically a handle client, the domain name associated with the proxy becomes the visible, public location for DOI name resolution. An RA may also want to provide specific services for a particular community where it wouldn't be appropriate to have the services be part of the common proxy; however, RAs should give consideration to having any appropriate functionality in their service replicated in the common proxy (a process enabling this to happen will need to be established).
4. RAs that runs their own proxy-like service agree to also support the common proxy server functionality, and agree to perform a default resolution for all DOI names from any IDF RA (e.g. http://dx.medra.org/10.1000/186 or http://0-doi.org.pugwash.lib.warwick.ac.uk/10.1000/186 will at least resolve a DOI name to the default URL). The DOI system is global and distributed. Avoiding fragmentation of services, wherein DOI name resolution happens in drastically different ways via different proxies, is essential. Quality of service problems with any RA run proxy service will reflect on the DOI system as a whole. Going forward, the IDF will need to further define core functionality for all proxies in the future.
5. RAs who runs a proxy-like service must agree to alias that domain name to doi.org if and when their uniquely named service is no longer maintained. This will enable persistent DOI references to continue to resolve. An RA may choose to move back to using the common proxy and not run its own; however, succession back to the common proxy would need to be carefully managed. Regardless of the number of proxies run by RAs, the IDF will run additional instances of the common proxy, and distribute the load across them.
6. Every RA that runs a proxy-like service agrees to inform the IDF about that service such that the IDF can maintain a list of valid DOI proxy servers.