Created
June 10, 2016 17:21
-
-
Save kgaughan/f4fe962e38ba0f691328e77578e873a2 to your computer and use it in GitHub Desktop.
EPP mux envelope
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
<?xml version="1.0"?> | |
<mux xmlns="foo"> | |
(<src>...</src>|<dest>...</dest>) | |
<p> | |
<epp xmlns="..."> | |
... | |
</epp> | |
</p> | |
</mux> |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Me noodling how to multiplex EPP requests over a single connection in a way that doesn't cause a layering violation (Unlike the Verisign Namestore extension). It's not specific to EPP though.
The idea is that a client sends a request with
<dest/>
set to the destination server's ID, and the actual EPP XML document is put in the</p>
(payload) element. In the response, the server includes the source server's ID in the<src/>
element so the client can tell where it came from and so demux it.This could be expanded with a status element, and possibly some kind of a service menu response (not dissimilar to the EPP greeting), keep-alive request, and an optional authentication mechanism. I'm not sure how useful an authentication mechanism would be, though.