Registry Service Provider.BR

Question

Registry Service Provider.BR

Navigation

#1 by (2 votes)

5

I want to submit myself as a service provider in the Registro.BR and this requires that a test be done in the homologation environment of them. I am finding the information mismatched, so I had some doubts.

1- They quote an application called shepp. So I understand you send a command passing some parameters and receives an XML as a response. Understanding this shepp is required for the test to take place? What is the advantage of using it? I have read some developer in an email list thread saying that it is totally optional and it encourages the use of the test server

2- To have access to this test server, I need to complete that form, is that it? The same form will generate the test credentials and later I submit to the homologation environment?

3- There is a C ++ library called libepp-nicbr. I understand it is optional. What is not optional is the use of "XML over TLS applied to the EPP protocol", right? Is there any advantage over using the library they provide? I do not have much experience with C ++, except for college time. Would the idea be to use some other language, such as Ruby, PHP or Node to run a command from that library?

This library has no documentation, is it? Examples of answers I can find in this link, do you? ftp://ftp.registro.br/pub/libepp-nicbr/en- policy-restrictions-spec.txt

asked by anonymous 17.06.2015 / 00:19

1 answer

How to inflate a class on Android? Can you calculate the diagonal on Canvas?

score 2 · Answer 1

1 - Shepp is useful for testing since the approval procedure (ftp: // ftp.register.br/pub/libepp-nicbr/pt-epp-accreditation-proc.txt) is described in shepp syntax , but if you are not going to use libepp-nicbr for integration, doing the homologation with the shepp will give you the false impression that everything is ready on your side.

2 - It is necessary to complete the homologation form for access to the test server, but the test server is the same as the approval environment.

3 - If you are going to use another language, what makes the most sense is to use a native EPP library of that language, but you will have to implement the specific extensions of .br (ftp: // ftp registry br / pub / libepp-nicbr / draft-neves-epp-brorg-06.txt and ftp: // ftp registry br / pub / libepp-nicbr / draft-neves-epp-brdomain-05.txt). One possibility would be to get this implementation in PHP that is from a gateway to a billing platform in PHP, and adapt to its use: https: // github com / registry / whmcs-registry-epp

The library has documentation, is a doxygen file for each version that can be consulted in a browser. For example, the most recent version: ftp: // ftp registry br / pub / libepp-nicbr / libepp-nicbr-1.15.tar.gz You have your documentation in this file: ftp: // ftp registration br / pub / libepp-nicbr / libepp-nicbr-1.15-doxygen.tar.gz

My suggestion is to look at what use cases your project requires, and what use cases the approval requires. Those that are necessary for both, to develop and use in both integration and homologation. Those that are only needed for homologation, do with shepp instead of developing, but leave documented how to use shepp for cases not implemented.

(Broken links because of the OS Spam Detector)