I have several web sites running Drupal 7. The biggest issue that prevents me from migrating to Drupal 8 is the status of several contributed modules that I depend on. If they don't have a Drupal 8 version available (and there are many that don't), I have to either update them myself or find an alternative. The most common reaction I get from the developers of these modules when asked about their plans for Drupal 8 is silence...
As one of the folks involved in the EPP/BEEP discussions, I can confirm that most of the concerns had to do not only with a lack of experience with current BEEP implementations, but a wealth of experience with streaming data over TCP. Implementers just felt more comfortable working with tried and true technology. It will be nice, though, if we get a chance to implement this draft and see if any of the early performance and complexity concerns were justified.
I don't believe there's any public document that describes a BEEP profile for what NeuStar is calling XRP, but there _is_ one for the Extensible Provisioning Protocol (EPP), a work item of the IETF's provreg working group:
It may be that NeuStar is using XRP as a brand name for their implementation of EPP. FWIW there is an open source implementation of EPP available on SourceForge:
XML is getting noticed by other standards developing organizations, such as the IETF. XML Schema provides features for protocol design, such as strong data typing, that just weren't available with DTDs, giving application layer protocol designers a viable alternative to other specification languages such as ASN.1.
Slashdot Mirror
I have several web sites running Drupal 7. The biggest issue that prevents me from migrating to Drupal 8 is the status of several contributed modules that I depend on. If they don't have a Drupal 8 version available (and there are many that don't), I have to either update them myself or find an alternative. The most common reaction I get from the developers of these modules when asked about their plans for Drupal 8 is silence...
One of the benefits of getting in on the ground floor like that was big blocks of IPv4 addresses - apple.com still controls a /24 block, I think.
...and Xerox has (or maybe had) 13/8.
What we need is a standard format for WHOIS responses. What we don't need is some monopoly gatekeeper.
There's IETF work under way to develop standard formats for whois-like queries and responses: http://datatracker.ietf.org/wg/weirds/charter/
Here's a link to the draft describing EPP transport using BEEP:
p ro vreg-epp-beep-02.txt
http://www.ietf.org/internet-drafts/draft-ietf-
As one of the folks involved in the EPP/BEEP discussions, I can confirm that most of the concerns had to do not only with a lack of experience with current BEEP implementations, but a wealth of experience with streaming data over TCP. Implementers just felt more comfortable working with tried and true technology. It will be nice, though, if we get a chance to implement this draft and see if any of the early performance and complexity concerns were justified.
NeuLevel is a partnership between NeuStar and Melbourne IT of Australia, with NeuStar owning the majority share of the partnership.
EPP BEEP Transport
It may be that NeuStar is using XRP as a brand name for their implementation of EPP. FWIW there is an open source implementation of EPP available on SourceForge:
EPP on SourceForge
XML is getting noticed by other standards developing organizations, such as the IETF. XML Schema provides features for protocol design, such as strong data typing, that just weren't available with DTDs, giving application layer protocol designers a viable alternative to other specification languages such as ASN.1.